
From nobody Wed Mar  1 07:04:47 2017
Return-Path: <mersue@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 1312C129528; Wed,  1 Mar 2017 07:04:46 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NjSozOdDYt86; Wed,  1 Mar 2017 07:04:44 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D081129498; Wed,  1 Mar 2017 07:04:44 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id v186so112518130wmd.0; Wed, 01 Mar 2017 07:04:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=7j9JQoaB1HTSRLfsYeoGsXvKAkoZELCcNyYjoDkvLb0=; b=pSdtp73f3WTuUDknRLSBehVRhc7MU1Bk8hRc12X+TqPJkYlnez+HAOASQMzkZdWqE+ o+0MPipX/bjBNKZn4TXG/mCWco0ds2Zh0RoourmRHZ42p/sOizoJOENWg+JTYmlfzRpV Ksj7dr/Dmqor/IqY4v5XtZyS/Df+AI33ztUCtTVU7xMgsAYXOEBILm7b86H+auAPvYHw VwNzOao+eTu4dI2dLLBCmccxQRmen6jOuazZmKrJEh0qju15mXzbOQHHKZ3vZJ9MUq8j sXJyQkCAptq6OsR++vxS6grKJho8UDefRjJXpOeW98tRL2f8jyzNltrwwICE1CVPhxPK z2Zw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=7j9JQoaB1HTSRLfsYeoGsXvKAkoZELCcNyYjoDkvLb0=; b=WVGVmybTVzWF1F6ho3o2aM6/w2FxBF9JoUibd9K4z3392otaIcXBRD10UCYDPX35Bq Lz29OQglTIJGNy0lpUVJa4Iz9jmS4fvy3p/o9s2OPMOKQnKz4y01nex8c6D+WOxYkoHU 8BGhUXGEwCxj3NheX4zJ2goGYWxJ103T6FeAOSoU0FGkNH/oomGF7tslrHhfQwWnlvEV awve5Z9GV48apnsG12aWmLYDD9g5lW3w1fkG5pUYQMVqZCYzJwVHEWedplDoXr8xpjG6 HrQSLM7N5x6jA2M1q/CUIczXonm+VX62pTERoSHkFgUWytj8ejzupQX4alfLSKGNyAlq hOgA==
X-Gm-Message-State: AMke39kqj+kKJTHomQoI5kotc3vnyB92Hs52z7XPYnCFpHQkzafAa8Z92rR700h6d0lgiA==
X-Received: by 10.28.43.6 with SMTP id r6mr3822215wmr.0.1488380682489; Wed, 01 Mar 2017 07:04:42 -0800 (PST)
Received: from DESKTOPFLHJVQJ (p5B3414C8.dip0.t-ipconnect.de. [91.52.20.200]) by smtp.gmail.com with ESMTPSA id d29sm6996779wrc.34.2017.03.01.07.04.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Mar 2017 07:04:41 -0800 (PST)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'joel jaeggli'" <joelja@bogus.com>, "'IETF Agenda'" <agenda@ietf.org>
References: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com> <005301d28f80$758d5c30$60a81490$@gmail.com> <a7852494-5cd0-1777-176b-399acd6ceecd@bogus.com>
In-Reply-To: <a7852494-5cd0-1777-176b-399acd6ceecd@bogus.com>
Subject: RE: IETF 98 Preliminary Agenda
Date: Wed, 1 Mar 2017 16:04:41 +0100
Message-ID: <013a01d2929d$27840550$768c0ff0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLvBlHc5cYfAkTApDxLlwOHz1YA3gIg9GZmAeavu6qfJu9j8A==
Content-Language: de
X-AVK-Virus-Check: AVA 25.10928;F984776D
X-AVK-Spam-Check: 1; str=0001.0A0C0208.58B6E309.0240,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0; AE713
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jKA4HZffmexfATqmF-A8yHa1ax0>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 15:04:46 -0000

In IETF #98 NMRG happens on Monday during the Afternoon session III.
NETMOD WG session (NETCONF Data Modeling Language) happens at the same time.

The request is to avoid the overlapping between NMRG and NETMOD sessions.

BR,
Mehmet

> -----Original Message-----
> From: joel jaeggli [mailto:joelja@bogus.com]
> Sent: Saturday, February 25, 2017 6:29 PM
> To: Mehmet Ersue <mersue@gmail.com>; 'IETF Agenda' <agenda@ietf.org>
> Cc: ietf@ietf.org
> Subject: Re: IETF 98 Preliminary Agenda
> 
> On 2/25/17 8:01 AM, Mehmet Ersue wrote:
> > Dear Agenda Experts,
> >
> > I would like to ask to avoid an overlapping of nmrg with OPS area WGs.
> > Thank you for your consideration.
> I go to rather a lot of ops area working groups and I'm dubious the NMRG
> colliades will all of them.
> 
> excessive collision lists just make scheduling harder.
> 
> joel
> > Regards,
> > Mehmet
> >
> >> -----Original Message-----
> >> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On
> Behalf
> >> Of IETF Agenda
> >> Sent: Saturday, February 25, 2017 12:00 AM
> >> To: IETF Announcement List <ietf-announce@ietf.org>
> >> Cc: 98all@ietf.org
> >> Subject: IETF 98 Preliminary Agenda
> >>
> >> The IETF 98 Preliminary Agenda has been posted. The final agenda will
> >> be published on Friday, March 3, 2017.
> >>
> >> https://datatracker.ietf.org/meeting/98/agenda.html
> >> https://datatracker.ietf.org/meeting/98/agenda.txt
> >>
> >>
> >> More information regarding IETF 98 in Chicago is located here:
> >> https://www.ietf.org/meeting/98/index.html
> >>
> >> Thank you!
> >>
> >> IETF Secretariat
> >
> 



From nobody Wed Mar  1 07:06:03 2017
Return-Path: <mersue@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 EE2E0129560; Wed,  1 Mar 2017 07:06:01 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2FmJ2Cy72Nzq; Wed,  1 Mar 2017 07:06:00 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6236C12953A; Wed,  1 Mar 2017 07:06:00 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id u199so38689846wmd.1; Wed, 01 Mar 2017 07:06:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=1/6mTjmAiNv9C/y9risrFjsKNTmgPCUL6umDxhay250=; b=XmnFoHLQK1JHgP4cYVcXsTWV+Y9j8/qmNW6rIJzVA0WEZOv92Rm/fQJ/X8kaRj0WDo ouRNzModK0mnL7+rO22hFNgMs4JcY15yaJ1gSzsTo4cDemtUbMJqreRaHwPiI1YyD6VE Qg9yh4wrscSSB4t4KT7gGqR3VaY+TPAuSzKZcdWz4j/IxmZ6Fm47aoBo4c+6rKKq4d6u BaZFum8+6171qNka9sT1z8GGklBm7v3KlKGRjyep1bguztktzJcZqLB5Az5juC7FRn3q kY6UcbM9bE7dEAhyL4LozuZVshi9DjG9J4UwkqWw+I/6ibq6Woyc/4gNWDPEStpydCer SqhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=1/6mTjmAiNv9C/y9risrFjsKNTmgPCUL6umDxhay250=; b=USn2u3yg+hBV10vDL+zOI5VQ0m/0Kk0ALZBZa/f9/QvtEKKNLyPuFLSIkW5NEmd70Q o16qnJI8Y2wYD57yKvP8vS2OJIEMvAN9VYVa9zQnBpF1y+dJd1UbOBlgkzfjythMdvIN CzuSDHr773jj/QyhGou2JzznSycuNSDnMYqrfpKsy77PpuythY2Vbmb8rwRFvZw4UTfS yEGZCWjWxZ7WgR63wWlL05if70t+56wSwuluXbBHqPzdWGe8RhlFkiAQ8me7WF9zQulA 1G8nbXWtwW1tk/p8paXyfr4xt/KAziI6k5KBKffMcFM3CyO52xpy/Zo6xTgUOJ6omIaC Rszg==
X-Gm-Message-State: AMke39mso0tlO1krBB/fZHyrsCTEE5seMGUjBW6YUlNp49x13j6eVREkZsg10TpL9/DMhg==
X-Received: by 10.28.236.209 with SMTP id h78mr3951772wmi.97.1488380758878; Wed, 01 Mar 2017 07:05:58 -0800 (PST)
Received: from DESKTOPFLHJVQJ (p5B3414C8.dip0.t-ipconnect.de. [91.52.20.200]) by smtp.gmail.com with ESMTPSA id v196sm7312436wmv.5.2017.03.01.07.05.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Mar 2017 07:05:58 -0800 (PST)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'Eggert, Lars'" <lars@netapp.com>
References: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com> <005301d28f80$758d5c30$60a81490$@gmail.com> <3C6DF8C5-0F2F-4F81-8478-2451EDD5603C@netapp.com>
In-Reply-To: <3C6DF8C5-0F2F-4F81-8478-2451EDD5603C@netapp.com>
Subject: RE: IETF 98 Preliminary Agenda
Date: Wed, 1 Mar 2017 16:05:57 +0100
Message-ID: <013e01d2929d$55253bf0$ff6fb3d0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLvBlHc5cYfAkTApDxLlwOHz1YA3gIg9GZmAdqe2KefJ1ElEA==
Content-Language: de
X-AVK-Virus-Check: AVA 25.10928;F984776D
X-AVK-Spam-Check: 1; str=0001.0A0C0203.58B6E356.0067,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0; AE713
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BTG_Sp_urzRz3B4yVrrm4UxcBJI>
Cc: 'IETF Agenda' <agenda@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 15:06:02 -0000

Same did NETCONF co-chairs.

Cheers,
Mehmet

> -----Original Message-----
> From: Eggert, Lars [mailto:lars@netapp.com]
> Sent: Monday, February 27, 2017 10:07 AM
> To: Mehmet Ersue <mersue@gmail.com>
> Cc: IETF Agenda <agenda@ietf.org>; ietf@ietf.org
> Subject: Re: IETF 98 Preliminary Agenda
> 
> On 2017-2-25, at 17:01, Mehmet Ersue <mersue@gmail.com> wrote:
> > I would like to ask to avoid an overlapping of nmrg with OPS area WGs.
> 
> Please tell the respective chairs to list those conflicts when requesting
the
> slots. For example, NMRG listed:
> 
> First Priority: sdnrg nfvrg anima opsarea Second Priority: netmod netconf
> nmlrg irtfopen
> 
> Lars


From nobody Wed Mar  1 07:47:08 2017
Return-Path: <laurent.ciavaglia@nokia-bell-labs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EDE5129593; Wed,  1 Mar 2017 07:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnkkfwvzzYLG; Wed,  1 Mar 2017 07:47:04 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C17F1294DA; Wed,  1 Mar 2017 07:47:04 -0800 (PST)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id CC0FFCBC3E7E7; Wed,  1 Mar 2017 15:46:58 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id v21Fl1VC010295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 1 Mar 2017 16:47:02 +0100
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id v21FkTr1027643 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Mar 2017 15:47:00 GMT
Received: from [172.27.205.238] (135.239.27.41) by FR711WXCHHUB02.zeu.alcatel-lucent.com (135.239.2.112) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 1 Mar 2017 16:46:15 +0100
Subject: Re: IETF 98 Preliminary Agenda
To: Mehmet Ersue <mersue@gmail.com>, "'Eggert, Lars'" <lars@netapp.com>
References: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com> <005301d28f80$758d5c30$60a81490$@gmail.com> <3C6DF8C5-0F2F-4F81-8478-2451EDD5603C@netapp.com> <013e01d2929d$55253bf0$ff6fb3d0$@gmail.com>
From: Laurent Ciavaglia <Laurent.Ciavaglia@nokia-bell-labs.com>
Organization: Nokia Bell Labs
Message-ID: <98f09c75-2017-01d1-7de9-4e8bfd0354d3@nokia-bell-labs.com>
Date: Wed, 1 Mar 2017 16:46:14 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <013e01d2929d$55253bf0$ff6fb3d0$@gmail.com>
Content-Type: multipart/alternative; boundary="------------FD8F25DE845093935CC8B7AA"
X-Originating-IP: [135.239.27.41]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HQsaE906nW4B7tgO0m7jkWil1ZU>
Cc: 'IETF Agenda' <agenda@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 15:47:06 -0000

--------------FD8F25DE845093935CC8B7AA
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit

Dear Mehmet,

We've had parallel threads to address this agenda conflict.
GROW and NETMOD chairs kindly accepted to swap their slot (Monday 
afternoon session III / Thursday afternoon session III). Request has 
been handled by the OPS ADs, IETF Secretariat is informed/tasked.

Hope this will address the issue.

Thanks,
Best regards, Laurent.

On 01/03/2017 16:05, Mehmet Ersue wrote:
> Same did NETCONF co-chairs.
>
> Cheers,
> Mehmet
>
>> -----Original Message-----
>> From: Eggert, Lars [mailto:lars@netapp.com]
>> Sent: Monday, February 27, 2017 10:07 AM
>> To: Mehmet Ersue <mersue@gmail.com>
>> Cc: IETF Agenda <agenda@ietf.org>; ietf@ietf.org
>> Subject: Re: IETF 98 Preliminary Agenda
>>
>> On 2017-2-25, at 17:01, Mehmet Ersue <mersue@gmail.com> wrote:
>>> I would like to ask to avoid an overlapping of nmrg with OPS area WGs.
>> Please tell the respective chairs to list those conflicts when requesting
> the
>> slots. For example, NMRG listed:
>>
>> First Priority: sdnrg nfvrg anima opsarea Second Priority: netmod netconf
>> nmlrg irtfopen
>>
>> Lars
>

-- 

Laurent Ciavaglia

Nokia, Bell Labs

+33 160 402 636

route de Villejust - Nozay, France

linkedin.com/in/laurent.ciavaglia


--------------FD8F25DE845093935CC8B7AA
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">
    <font face="Courier New">Dear Mehmet,<br>
      <br>
      We've had parallel threads to address this agenda conflict.<br>
      GROW and NETMOD chairs kindly accepted to swap their slot (Monday
      afternoon session III / Thursday afternoon session III). Request
      has been handled by the OPS ADs, IETF Secretariat is
      informed/tasked.<br>
      <br>
      Hope this will address the issue.<br>
      <br>
      Thanks,<br>
      Best regards, Laurent.<br>
    </font><br>
    <div class="moz-cite-prefix">On 01/03/2017 16:05, Mehmet Ersue
      wrote:<br>
    </div>
    <blockquote cite="mid:013e01d2929d$55253bf0$ff6fb3d0$@gmail.com"
      type="cite">
      <pre wrap="">Same did NETCONF co-chairs.

Cheers,
Mehmet

</pre>
      <blockquote type="cite">
        <pre wrap="">-----Original Message-----
From: Eggert, Lars [<a class="moz-txt-link-freetext" href="mailto:lars@netapp.com">mailto:lars@netapp.com</a>]
Sent: Monday, February 27, 2017 10:07 AM
To: Mehmet Ersue <a class="moz-txt-link-rfc2396E" href="mailto:mersue@gmail.com">&lt;mersue@gmail.com&gt;</a>
Cc: IETF Agenda <a class="moz-txt-link-rfc2396E" href="mailto:agenda@ietf.org">&lt;agenda@ietf.org&gt;</a>; <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>
Subject: Re: IETF 98 Preliminary Agenda

On 2017-2-25, at 17:01, Mehmet Ersue <a class="moz-txt-link-rfc2396E" href="mailto:mersue@gmail.com">&lt;mersue@gmail.com&gt;</a> wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">I would like to ask to avoid an overlapping of nmrg with OPS area WGs.
</pre>
        </blockquote>
        <pre wrap="">
Please tell the respective chairs to list those conflicts when requesting
</pre>
      </blockquote>
      <pre wrap="">the
</pre>
      <blockquote type="cite">
        <pre wrap="">slots. For example, NMRG listed:

First Priority: sdnrg nfvrg anima opsarea Second Priority: netmod netconf
nmlrg irtfopen

Lars
</pre>
      </blockquote>
      <pre wrap="">

</pre>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="ProgId" content="Word.Document">
      <meta name="Generator" content="Microsoft Word 12">
      <meta name="Originator" content="Microsoft Word 12">
      <link rel="File-List"
        href="2016-email-signature-bis_files/filelist.xml">
      <!--[if gte mso 9]><xml>
 <o:DocumentProperties>
  <o:Author>Laurent</o:Author>
  <o:LastAuthor>Laurent</o:LastAuthor>
  <o:Revision>2</o:Revision>
  <o:TotalTime>1</o:TotalTime>
  <o:Created>2016-04-20T22:27:00Z</o:Created>
  <o:LastSaved>2016-04-20T22:27:00Z</o:LastSaved>
  <o:Pages>1</o:Pages>
  <o:Words>18</o:Words>
  <o:Characters>103</o:Characters>
  <o:Company>Alcatel-Lucent</o:Company>
  <o:Lines>1</o:Lines>
  <o:Paragraphs>1</o:Paragraphs>
  <o:CharactersWithSpaces>120</o:CharactersWithSpaces>
  <o:Version>12.00</o:Version>
 </o:DocumentProperties>
</xml><![endif]-->
      <link rel="themeData"
        href="2016-email-signature-bis_files/themedata.thmx">
      <link rel="colorSchemeMapping"
        href="2016-email-signature-bis_files/colorschememapping.xml">
      <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:TrackMoves>false</w:TrackMoves>
  <w:TrackFormatting/>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>FR</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:DontVertAlignCellWithSp/>
   <w:DontBreakConstrainedForcedTables/>
   <w:DontVertAlignInTxbx/>
   <w:Word11KerningPairs/>
   <w:CachedColBalance/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val="Cambria Math"/>
   <m:brkBin m:val="before"/>
   <m:brkBinSub m:val="&#45;-"/>
   <m:smallFrac m:val="off"/>
   <m:dispDef/>
   <m:lMargin m:val="0"/>
   <m:rMargin m:val="0"/>
   <m:defJc m:val="centerGroup"/>
   <m:wrapIndent m:val="1440"/>
   <m:intLim m:val="subSup"/>
   <m:naryLim m:val="undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="267">
  <w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
  <w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 1"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 2"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 3"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 4"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 5"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 6"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 7"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 8"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 9"/>
  <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
  <w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/>
  <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
  <w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
  <w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
  <w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
  <w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
  <w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
  <w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
  <w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
  <w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
  <w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
  <w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
  <w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
  <w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
  <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
  <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]-->
      <style>
<!--
 /* Font Definitions */
 @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:roman;
	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:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-ansi-language:EN-GB;
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-fareast-language:EN-US;}
.MsoPapDefault
	{mso-style-type:export-only;
	margin-bottom:10.0pt;
	line-height:115%;}
@page WordSection1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	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-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin-top:0cm;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:10.0pt;
	mso-para-margin-left:0cm;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-fareast-language:EN-US;}
</style>
<![endif]--><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="3074"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1"/>
 </o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">Laurent
            Ciavaglia<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">Nokia, Bell
            Labs<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR"><o:p> </o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">+33 160 402
            636<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">route de
            Villejust - Nozay, France<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">linkedin.com/in/laurent.ciavaglia<o:p></o:p></span></p>
      </div>
    </div>
  </body>
</html>

--------------FD8F25DE845093935CC8B7AA--


From nobody Wed Mar  1 08:04:35 2017
Return-Path: <mcr+ietf@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 D1A83129567 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 08:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id slYOQpCADCwI for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 08:04:27 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB99D1294ED for <ietf@ietf.org>; Wed,  1 Mar 2017 08:04:27 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 98159E20E for <ietf@ietf.org>; Wed,  1 Mar 2017 11:26:44 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9420A6381A for <ietf@ietf.org>; Wed,  1 Mar 2017 11:04:26 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: RANT: posting IDs more often -- more is better -- why are we so shy?
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 01 Mar 2017 11:04:26 -0500
Message-ID: <14476.1488384266@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ijx-8poZx1cRooCMIXQF6E09Mnk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 16:04:34 -0000

--=-=-=
Content-Type: text/plain


For the third time in two days I find myself, when asking others for opinions
about some text, pointing at github commit logs.  With the beautiful
makefiles we often have, one can't even depend upon having a formatted .txt
version there!

This is not a rant for or against git or github, but rather about what I
perceive as a shyness about posting intermediate versions of Internet Drafts
to the datatracker.

I understand that in academia, they never like letting half-baked ideas out,
and so the -00 that we see from academics are often overdue and overly
polished.  I know I can't fight that, but at least the -01, etc. could be
issued faster?

I've even heard some push back from people along the lines of, "wow, that ID
has 27 revisions, is it really stable?", and my feelings have often been more
along the lines of, "wow, that revision has 27 revisions, the authors are
really keen and responsive".

I appreciate for some reviewers that having more revisions implies that they
think they have to look at the text more often.

But given the diff utilities, it shouldn't matter how many revisions there
were before times you look, as you can just skip the intermediate versions.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAli28P0ACgkQgItw+93Q
3WVbzggAqGFQJOfbwaILGFrOqwzYD/tnaK6fB7JRyIQpf2PRWJqhr7JV4Dya2uSZ
HS8n9p1tYzIJyI/L0v1cV15icyQ2sYM3DM4pqAkn1RFOQj9NOx+qpz/KrJjrBGf8
+DYzrYZzJmG5oUFN029vLTROJWK49rR2HHfYzVKzE9nM4/N9/Llimm3Q8YkPPs8s
6yDVaC7fQ4q6QMiboePxcORZpq0opuV+7rUpqPiOnf9XcBU7kNZ8EqzSHfpPWeL0
14NBe93dB2iAcXTTbompCQCELvCL8/LTp1+qOfJflu3huCkYKTcRIyao2DZY39FU
4uSVJSFcSV6R7l0GaJPp1E39cFSU8A==
=lYqT
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Mar  1 08:09:51 2017
Return-Path: <kathleen.moriarty.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 EED691295A8 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 08:09:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCoZF80ZzOOY for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 08:09:46 -0800 (PST)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EEFF12951A for <ietf@ietf.org>; Wed,  1 Mar 2017 08:09:46 -0800 (PST)
Received: by mail-pf0-x232.google.com with SMTP id j5so12382945pfb.2 for <ietf@ietf.org>; Wed, 01 Mar 2017 08:09:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UAxXi1dKo4lyBITEuCC1cvVT/BgZIizg47Zla0bT7z0=; b=qdV5zLBv8cFS566qSKOJFcJhF8NBlV5MUHYpxFduDsR0AzadcWU8OxyGZiO9YkVGL8 MY1ydk/Qj8ov0erJFGGEZnK+2gWCgfGUmNcoHXzAEafzjzCZaO8PT/gQzHHM3MAD/U81 995UTCBOCTfXDdlbGrwx6tFUuA4JkQxFQOgZUDbZqac2kdmlwJ8ItMezZMeqL+9v6EZ2 kh+p3s5u8JXPukiVsxdKNR5gwi09PMkYnXYytDV04ptNDo397Ytr1PE67x6Ybt35iOMK pqJrwdUZ1SuCsSFFs0oiKxocoxQhyqZXWonJJ1wqJsnPVOFSwS6cYnfvLkrQBx4ILUyx eRKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UAxXi1dKo4lyBITEuCC1cvVT/BgZIizg47Zla0bT7z0=; b=A+TkhfnFpB1QTmzRi2S9V6ToXnw68Fj767L8nLNtNgoTYGsiBjdGL/h7AJ6qqMd/W0 95Otw3UNgbOPqTWAeVr3eX/0jnc24sk/okubcy8//1Rr53EUR5HBycN0r/TxXLiaV3vw QjBAV6+GnRJMJ8seemHs/1SpxtDWd3wFa/nIuEhmd06zjnwLVX3DvAc1ESTOvuHkeYml VvGWk7CfV33fpIDfJDqqg9qcCXrYVQUGPjiXHXj0wlp+IbgGzu2arHU7G8C/xbpE0Kue 9qQDbvlQm5qA8EepmL52Tc6wXrq+JWZvdUfBKQQr1n+ab9jCPJzRnNqDQXgmDNC7E+kh 4Sdw==
X-Gm-Message-State: AMke39n8VdwVAqN0/UkBS61NTYh+VlfAauR7vlCG8dI1WGmHDPO3/3ntJ/AjnIwhUX1cxfHukHGTCJ1ATcFl7w==
X-Received: by 10.98.139.84 with SMTP id j81mr9505061pfe.115.1488384585565; Wed, 01 Mar 2017 08:09:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.186.200 with HTTP; Wed, 1 Mar 2017 08:09:45 -0800 (PST)
In-Reply-To: <14476.1488384266@obiwan.sandelman.ca>
References: <14476.1488384266@obiwan.sandelman.ca>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 1 Mar 2017 11:09:45 -0500
Message-ID: <CAHbuEH6kvDfZvJUJZ0sWWWPibik2sL5mAyBNHsh+jk7onmgRdw@mail.gmail.com>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/adRRPgbZjHYSAA3f7Cunrhoxlrc>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 16:09:48 -0000

On Wed, Mar 1, 2017 at 11:04 AM, Michael Richardson
<mcr+ietf@sandelman.ca> wrote:
>
> For the third time in two days I find myself, when asking others for opinions
> about some text, pointing at github commit logs.  With the beautiful
> makefiles we often have, one can't even depend upon having a formatted .txt
> version there!
>
> This is not a rant for or against git or github, but rather about what I
> perceive as a shyness about posting intermediate versions of Internet Drafts
> to the datatracker.
>
> I understand that in academia, they never like letting half-baked ideas out,
> and so the -00 that we see from academics are often overdue and overly
> polished.  I know I can't fight that, but at least the -01, etc. could be
> issued faster?
>
> I've even heard some push back from people along the lines of, "wow, that ID
> has 27 revisions, is it really stable?", and my feelings have often been more
> along the lines of, "wow, that revision has 27 revisions, the authors are
> really keen and responsive".
>
> I appreciate for some reviewers that having more revisions implies that they
> think they have to look at the text more often.
>
> But given the diff utilities, it shouldn't matter how many revisions there
> were before times you look, as you can just skip the intermediate versions.

+1 and I'd rather save subsequent reviewers from picking up on the
same issues that have already been identified.  I do have WGs post
revisions at several stages once it gets to AD review & IESG
processing for that reason and versions are cheap ;-)

>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>



-- 

Best regards,
Kathleen


From nobody Wed Mar  1 09:13:10 2017
Return-Path: <pmcmanus@mozilla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2EC312962C for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 09:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.734
X-Spam-Level: 
X-Spam-Status: No, score=-0.734 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id txO2VpqLutv9 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 09:13:07 -0800 (PST)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id 79FEF129616 for <ietf@ietf.org>; Wed,  1 Mar 2017 09:07:14 -0800 (PST)
Received: from mail-yw0-f182.google.com (mail-yw0-f182.google.com [209.85.161.182]) by linode64.ducksong.com (Postfix) with ESMTPSA id BC6473A0A1 for <ietf@ietf.org>; Wed,  1 Mar 2017 12:07:12 -0500 (EST)
Received: by mail-yw0-f182.google.com with SMTP id d1so37504952ywd.2 for <ietf@ietf.org>; Wed, 01 Mar 2017 09:07:12 -0800 (PST)
X-Gm-Message-State: AMke39mKMmnB7TL2xzIfR7V9rHIqFFpoXWuN5sT8RbEsopKQQL2EHDavMHmtV+QNe8KXliWJpewmHyMy7q1C3A==
X-Received: by 10.200.42.151 with SMTP id b23mr10893353qta.163.1488388032466;  Wed, 01 Mar 2017 09:07:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.162.65 with HTTP; Wed, 1 Mar 2017 09:07:11 -0800 (PST)
In-Reply-To: <14476.1488384266@obiwan.sandelman.ca>
References: <14476.1488384266@obiwan.sandelman.ca>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Wed, 1 Mar 2017 12:07:11 -0500
X-Gmail-Original-Message-ID: <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com>
Message-ID: <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a1142f5c2f6eaf00549ae5701
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CD4zcm4ztidGynzu4DGIrLfj5OI>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 17:13:09 -0000

--001a1142f5c2f6eaf00549ae5701
Content-Type: text/plain; charset=UTF-8

On Wed, Mar 1, 2017 at 11:04 AM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> For the third time in two days I find myself, when asking others for
> opinions
> about some text, pointing at github commit logs.  With the beautiful
> makefiles we often have, one can't even depend upon having a formatted .txt
> version there!


You can fix this with better tooling within github and travis integration
fwiw. Checkout the httpbis github https://github.com/httpwg/http-extensions
- you'll see the for each adopted draft the README.md has links to the
"editor's draft" in both txt and html as well as the working group draft.
The former is auto-generated on every push to the repo, the latter is a
pointer to datatracker.

I'm not arguing against updating data tracker more often - just saying this
'editor's draft' convention can work very well between official revisions
no matter the cadence a WG chooses.

--001a1142f5c2f6eaf00549ae5701
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Mar 1, 2017 at 11:04 AM, Michael Richardson <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr+ietf@sandelman.ca=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><div class=3D"gmail-adM"><br></div>
For the third time <span class=3D"gmail-aBn" tabindex=3D"0"><span class=3D"=
gmail-aQJ">in two days</span></span> I find myself, when asking others for =
opinions<br>
about some text, pointing at github commit logs.=C2=A0 With the beautiful<b=
r>
makefiles we often have, one can&#39;t even depend upon having a formatted =
.txt<br>
version there!</blockquote></div><br></div><div class=3D"gmail_extra">You c=
an fix this with better tooling within github and travis integration fwiw. =
Checkout the httpbis github <a href=3D"https://github.com/httpwg/http-exten=
sions">https://github.com/httpwg/http-extensions</a> - you&#39;ll see the f=
or each adopted draft the README.md has links to the &quot;editor&#39;s dra=
ft&quot; in both txt and html as well as the working group draft. The forme=
r is auto-generated on every push to the repo, the latter is a pointer to d=
atatracker.<br><br></div><div class=3D"gmail_extra">I&#39;m not arguing aga=
inst updating data tracker more often - just saying this &#39;editor&#39;s =
draft&#39; convention can work very well between official revisions no matt=
er the cadence a WG chooses.<br><br><br></div></div>

--001a1142f5c2f6eaf00549ae5701--


From nobody Wed Mar  1 10:53:39 2017
Return-Path: <ando@bbsec.co.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 7CBBA129642 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 10:53:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bbsec.co.jp
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFfTmK1UZNAX for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 10:53:36 -0800 (PST)
Received: from sproxy40.aams4.jp (sproxy40.aams4.jp [IPv6:2001:278:1047:410::241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7165E129634 for <ietf@ietf.org>; Wed,  1 Mar 2017 10:53:35 -0800 (PST)
Received: from osprey.enkai.tv (27.35.138.210.xn.2iij.net [210.138.35.27]) (authenticated bits=0) by sproxy40.aams4.jp (Sentrion-MTA-4.0.2/Switch-3.3.4) with ESMTP id v21IrV9Q009118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Thu, 2 Mar 2017 03:53:32 +0900
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bbsec.co.jp; s=20150430; t=1488394412; bh=LzPjQvqCDxb75AtMbXyICkVa3Q1lzZPuxRma7SGTT/U=; h=Subject:To:References:From:Date:In-Reply-To; b=fM1AFPPcJxqqhkp1aF7h9+F500twrQWGxKsMsGQ0nOEdwtFVF3VtOUEPVlHHtj+MG bO2n5qiY5IXgvBGaxWWeVkymGQYpv1Hca5IGZ0LSXECE6DaTYwGKhrUuyZ59By/qbo LJ9gUaZTvkZsm3ULmqD9RFceP08/Tuftek7M+Z/o=
Subject: Re: Mailing list membership.
To: ietf@ietf.org
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org>
From: Kazunori ANDO <ando@bbsec.co.jp>
Message-ID: <0295195d-20a6-0099-eef5-115245293047@bbsec.co.jp>
Date: Thu, 2 Mar 2017 03:53:31 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170301044937.v3vhw3eqgqkxpoup@thunk.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AAMS-Virus-Status: clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lXG_WeSZfD37j6JI48Y-wMQudnk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 18:53:38 -0000

Hi, folks

I made note about these conflicts. FYI.

https://www.facebook.com/notes/%E5%AE%89%E8%97%A4-%E4%B8%80%E6%86%B2/memo-about-some-conflicts-between-mailing-lists-and-dmarc/1332635393468971
-- 
Kazunori ANDO / ando@bbsec.co.jp

On 2017/03/01 13:49, Theodore Ts'o wrote:
> On Tue, Feb 28, 2017 at 05:29:24PM -0300, willi uebelherr wrote:
>>
>> related to the problem, what Khaled explained, what is your proposal?
>>
>> What are your "compatible with internet mailing lists" mail systems?
>
> RFC 2821, Simple Mail Transfer Protocol, section 3.10.2
>
>    "To expand a list, the recipient mailer replaces the
>    pseudo-mailbox address in the envelope with all of the expanded
>    addresses.  The return address in the envelope is changed so that all
>    error messages generated by the final deliveries will be returned to
>    a list administrator, not to the message originator, who generally
>    has no control over the contents of the list and will typically find
>    error messages annoying."
>
> This is the SMTP Envelope From field.  The FROM field is not changed,
> but the SMTP return address is changed, so that bounces go to the
> mailing list administrator as opposed to the person who sends mail to
> the mailing list.
>
> Unfortunately, if you are using a system whose domain requests that
> all recipients enforce DMARC alignment, this specifically instructs
> recipients to bounce mail if the SMTP Envelope return address doesn't
> match the FROM field in the header.  This means that they won't see
> mailing list mail as defined by the IETF Standards Track RFC 2821,
> which specifically says that is acceptable (and in fact a good thing)
> to change the SMTP envelope return address so that bounces (caused by
> people changing where they work, etc.) go to an administrator who can
> deal with them.  But if the mailing list administrators gets too may
> bounces, and it's because the sending domain is requesting that mail
> be bounced, the only thing they can do is to unsubscribe the sender or
> the recipient.
>
> Hence mailing list systems that enforce DMARC, or request DMARC
> processing, are fundamentally incompatible with mailing lists as
> defined by section 3.10.2 of RFC 2821.
>
> If you want to participate in such mailing list, one of the best ways
> is to change to a mailing list system that doesn't do DMARC.
>
> Best regards,
>
> 						- Ted
>
>


From nobody Wed Mar  1 10:56:01 2017
Return-Path: <mstjohns@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 772E712966A for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 10:55:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJwiPMn3GYiL for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 10:55:58 -0800 (PST)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16C03129663 for <ietf@ietf.org>; Wed,  1 Mar 2017 10:55:58 -0800 (PST)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-07v.sys.comcast.net with SMTP id j9PXcpaF87NeDj9Ppc6MUx; Wed, 01 Mar 2017 18:55:57 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1488394557; bh=px3XBGK4d/RbqsOu+i2wNadDUay2mH/x9tLLCHJ0/gI=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=mhpkLysgH8Q4x5q4WLY0LX377IvTspXAM7oHW/k/owNUxrTrKC4b+0xYCz3D7js5Z a+6P7kdfTYmzv410gKLqZfwmG+cCWgZqEXJnTSs9oFDYHFR1lHKP3oLksrAKSwVUd5 pLD4nkRRPg/3NcpUfGdYr4cyDIOQKDlsP2iasNKayzGIZ1fF3KrPDATT4qyRGJgnsp X1i2V23oBSpgs6/lOII2/mbya1ELgjD0st7Z7RDdDOw3h7JVJUrVYiV2fE70xvJ84N xpYlKOcbVdipJyFPp4NinhTA4T12zS1r7oewBdPzNx9uTeO5K2dGQstF9lrfzqNG7m RYJQwL0pyJY7w==
Received: from [IPv6:2601:152:4400:9b5f:c8f0:67e5:88b1:2975] ([IPv6:2601:152:4400:9b5f:c8f0:67e5:88b1:2975]) by resomta-ch2-05v.sys.comcast.net with SMTP id j9Poc8G3ge2G0j9PoccRDo; Wed, 01 Mar 2017 18:55:57 +0000
Subject: Re: Mailing list membership.
To: ietf@ietf.org
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net>
Date: Wed, 1 Mar 2017 13:55:59 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170301044937.v3vhw3eqgqkxpoup@thunk.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfAlsjPxsCi/GU92721vASf9KLkcB2QNl7suQ9uFvcuxCY1+AhaLfcz2uXNv0LWExFaKX8Ut2bFs1A9s6Zll+1e5dL2dT5EqCa0hD9Hvm9jT+FmzdbZed avzXVy6BA2c9ksP10sWQlC8wXxJEi5NdqvQMblefBuL6EdIRGdmZsKVlAEeenckDgwx+sxsj1IRRQA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CRAXQMYEMuCQF-ffFEpXOot9VZ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 18:55:59 -0000

Question below

On 2/28/2017 11:49 PM, Theodore Ts'o wrote:
> On Tue, Feb 28, 2017 at 05:29:24PM -0300, willi uebelherr wrote:
>> related to the problem, what Khaled explained, what is your proposal?
>>
>> What are your "compatible with internet mailing lists" mail systems?
> RFC 2821, Simple Mail Transfer Protocol, section 3.10.2
>
>     "To expand a list, the recipient mailer replaces the
>     pseudo-mailbox address in the envelope with all of the expanded
>     addresses.  The return address in the envelope is changed so that all
>     error messages generated by the final deliveries will be returned to
>     a list administrator, not to the message originator, who generally
>     has no control over the contents of the list and will typically find
>     error messages annoying."
>
> This is the SMTP Envelope From field.  The FROM field is not changed,
> but the SMTP return address is changed, so that bounces go to the
> mailing list administrator as opposed to the person who sends mail to
> the mailing list.
>
> Unfortunately, if you are using a system whose domain requests that
> all recipients enforce DMARC alignment, this specifically instructs
> recipients to bounce mail if the SMTP Envelope return address doesn't
> match the FROM field in the header.  This means that they won't see
> mailing list mail as defined by the IETF Standards Track RFC 2821,
> which specifically says that is acceptable (and in fact a good thing)
> to change the SMTP envelope return address so that bounces (caused by
> people changing where they work, etc.) go to an administrator who can
> deal with them.  But if the mailing list administrators gets too may
> bounces, and it's because the sending domain is requesting that mail
> be bounced, the only thing they can do is to unsubscribe the sender or
> the recipient.
>
> Hence mailing list systems that enforce DMARC, or request DMARC
> processing, are fundamentally incompatible with mailing lists as
> defined by section 3.10.2 of RFC 2821.
>
> If you want to participate in such mailing list, one of the best ways
> is to change to a mailing list system that doesn't do DMARC.
>
> Best regards,
>
> 						- Ted
>

Thanks for the clear description of the problem - I admit that I got a 
similar one from folks at the Seoul IETF.

In the short term, one thing I think would be helpful is to identify for 
the IETF participants which email providers are known to use DMARC and 
maybe also a list of providers that are known not to.   Maybe add it to 
the IETF mailing list page at https://www.ietf.org/list/ with an 
explanation of what's been happening.


Mike



From nobody Wed Mar  1 11:14:16 2017
Return-Path: <bob.hinden@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 6B0C9129682 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zdCtIjfag2Xb for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:14:14 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1BF0129679 for <ietf@ietf.org>; Wed,  1 Mar 2017 11:14:13 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id n11so7279146wma.1 for <ietf@ietf.org>; Wed, 01 Mar 2017 11:14:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=/A8A4t+gBZuHw4OmYZFCSA1NHOvszzEWe1xygFFcq7E=; b=bmKDaeVRRbSzCbmBP6FncNujrA8GsNWFCZ9DAzSIUDeVvFJxragbsm2VlR5f5XmWfG y9pjRJQ0/b268KJ85w87z3CiNZasLPeVi9r1HuD8WlLD8vr8u+sngJXgvxNmhW4xVq27 zAgJiRv5X4UdbSM56yaeLs9mquZ24ckNrrNWS7wZ5S98IFVp1I474YE9f9KYBERqi6gs NtL42ZmiZYp4oLsk9xcwgk2NAWVBGA0rhOgABYwj53cIXwJN3FfmqZczgUv1MsEaZHSu OIYmHAAHTfrf2TQoVuTuMyf192aV/H85eFK/iFeWLDL6iDr0RunaPSIRZ7qh3lQG4z9d zEwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=/A8A4t+gBZuHw4OmYZFCSA1NHOvszzEWe1xygFFcq7E=; b=Jj2yZXgoaKdPojYHb2rsRbxhCgBK/bnpDJ4pduibmwg8N2U+Y1VVtFijSMV1y1DDxr pSPmM9AJnsAFq4IfJWlz/1g5aOR0LdCbvYbLGJ3R37LSm7WpB0Xt1cA1+ygIOS5h7asM y6Y0bzTEoIM5j2cDECB66oFlc6DRCbqF3uvtH47JJhKxSmxvmwTx8SQSpPnGwXvMWZud RXZuuMZXG5w995SMQrrlofsgxSE7K3z/YeAMnT5Q4PgYtGLPvv7AJNk+WvRksspvNXqj zvvXB1gCPKjYSPZWH2AWMatEGJfjmbESfONL0WQ1vvFSsDl/rVnS0C8E9mUe8Jhx8UhZ IroQ==
X-Gm-Message-State: AMke39nYM7bw7kPvHU43Gp+Y9d/UKdzWURQi5yfVclHgFZi8b8Bios6WyifZNHRzvvYSWw==
X-Received: by 10.28.181.80 with SMTP id e77mr4735642wmf.57.1488395652255; Wed, 01 Mar 2017 11:14:12 -0800 (PST)
Received: from [172.25.3.15] (rrcs-67-52-140-5.west.biz.rr.com. [67.52.140.5]) by smtp.gmail.com with ESMTPSA id l7sm7722126wrl.59.2017.03.01.11.14.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Mar 2017 11:14:10 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_508CEBD7-F872-4EE1-B90B-1E4732862F6E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Mailing list membership.
Date: Wed, 1 Mar 2017 11:14:05 -0800
In-Reply-To: <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net>
To: Michael StJohns <mstjohns@comcast.net>
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org> <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sPXIqTQSPA4WHV_Eu0rov5sOb-k>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 19:14:15 -0000

--Apple-Mail=_508CEBD7-F872-4EE1-B90B-1E4732862F6E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mike,

> On Mar 1, 2017, at 10:55 AM, Michael StJohns <mstjohns@comcast.net> =
wrote:
>=20
>>=20
>> Hence mailing list systems that enforce DMARC, or request DMARC
>> processing, are fundamentally incompatible with mailing lists as
>> defined by section 3.10.2 of RFC 2821.
>>=20
>> If you want to participate in such mailing list, one of the best ways
>> is to change to a mailing list system that doesn't do DMARC.
>>=20
>> Best regards,
>>=20
>> 						- Ted
>>=20
>=20
> Thanks for the clear description of the problem - I admit that I got a =
similar one from folks at the Seoul IETF.
>=20
> In the short term, one thing I think would be helpful is to identify =
for the IETF participants which email providers are known to use DMARC =
and maybe also a list of providers that are known not to.   Maybe add it =
to the IETF mailing list page at https://www.ietf.org/list/ with an =
explanation of what's been happening.
>=20

This is a good idea.  Taking it a step further, perhaps a warning could =
be included when subscribing to an IETF list from an email provider who =
is known to use DMARC.

Bob



--Apple-Mail=_508CEBD7-F872-4EE1-B90B-1E4732862F6E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYtx1+AAoJEK7rdBF357uowEcIAKe6aHjpd8pwEMPpDkLl3wHd
HixrFRjmzP0z8UcSj1jN2/A3gUh+4KwkGE87rO2Je3Gg0MqEdatV6x6WsJMcCiEB
sy1wWVOMCxXzqonBkdDYBYkzbo/Xld3ApiVxSjo3dJXTfIbARSOnb6KQhowA/bfR
nIVBl9wqpnVKgA31kISmeEIPXjgv9Bqo5OmUAb6R5DlCi13mXi7BoNznte0yNEQF
7wY2/3Oz4qwXfN/gmnmUY1nxLkvXOKlJY7Z+KbUOyH4Pvg6Qtet/zlkf/1Tb0PuC
WzMrGZjntzpBWXvfDaDOJfRuFOfiEESzjQTapQl/8WnoxiVCIkpRTV00vEKDRmM=
=moQp
-----END PGP SIGNATURE-----

--Apple-Mail=_508CEBD7-F872-4EE1-B90B-1E4732862F6E--


From nobody Wed Mar  1 11:18:20 2017
Return-Path: <mstjohns@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 8298E12967A for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:18:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dzLp1fZuKMPt for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:18:18 -0800 (PST)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E650129561 for <ietf@ietf.org>; Wed,  1 Mar 2017 11:18:18 -0800 (PST)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-04v.sys.comcast.net with SMTP id j9lGcwmJ4E5a6j9lRcJaoX; Wed, 01 Mar 2017 19:18:17 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1488395897; bh=6NbguWUGO/IFCyrq4FUZTq0yi1llvXAWovU6uujKpfM=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=ldnpYWV1+MhTWznpxAmAXHKt1BMTz929tTUlaLDODlHXdLSmYsEnZpbAj8hUTCEz1 gls1G4yWFs78YbqdN4IPMFCtRJZxFYOQs6VFsbYK2gduebwJs4K+nUrSZJ8wlYJaC0 +Fc++YBMepo/jW0oPbidL4vBbvxYmXvzP6qimHZI9TGG6fmL7DQfQE0ika+KxcSF+a eccUXiBcCHDyA3M6JToCNfcEaHQtmLFe0hlLx7brMbr2IouGr8rlE90vgQpAmDINlc FqA05y80asdLJ1M9m7BFL/QbcdqEZ5ctxiclOO+FCYhjm0nofaoi0JzOh9ESKPcC/W u3JVQhPw8Kgvw==
Received: from [IPv6:2601:152:4400:9b5f:c8f0:67e5:88b1:2975] ([IPv6:2601:152:4400:9b5f:c8f0:67e5:88b1:2975]) by resomta-ch2-19v.sys.comcast.net with SMTP id j9lQcHy8Y2soIj9lRc6LRL; Wed, 01 Mar 2017 19:18:17 +0000
Subject: Re: Mailing list membership.
To: Bob Hinden <bob.hinden@gmail.com>
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org> <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net> <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net>
Date: Wed, 1 Mar 2017 14:18:19 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com>
Content-Type: multipart/alternative; boundary="------------4563E5A32F7814C7770025BC"
X-CMAE-Envelope: MS4wfH+kmZHqX2KmZqNCpGmLtqrfoHe2MjTImBpae6nKrlfc/BCnIJftRwJaY6xz1WaF1TtYL5LdE5AhIShm/zoTOqA4+9yuXiesoSID33RNmYUvingErdFP hpbo8h/AXxSXpfaMPikhdmyigm1adMgTcm0DbB9dfCMf+Z1BpN42ZKAdrfrBeSrrHY7daDpr5UsQXqQTVxcgol60GCLesRP+j2XaZKLkDydFE8OdN5YegAvg
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9dtkHbtPbpkDl49ef8S8GAJVp_U>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 19:18:19 -0000

This is a multi-part message in MIME format.
--------------4563E5A32F7814C7770025BC
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 3/1/2017 2:14 PM, Bob Hinden wrote:
>> In the short term, one thing I think would be helpful is to identify for the IETF participants which email providers are known to use DMARC and maybe also a list of providers that are known not to.   Maybe add it to the IETF mailing list page athttps://www.ietf.org/list/  with an explanation of what's been happening.
>>
> This is a good idea.  Taking it a step further, perhaps a warning could be included when subscribing to an IETF list from an email provider who is known to use DMARC.
>
> Bob
>
>

I like that.

Actually, split the difference to start with - its probably a coding 
pass to personalize a warning based on provider.  So do a) Add a warning 
to the IETF mailing list page, b) add a warning to the confirm message 
that's sent out when you subscribe that contains the warning regardless 
of provider, and c) eventually customize the confirm message based on 
provider.

Mike



--------------4563E5A32F7814C7770025BC
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 3/1/2017 2:14 PM, Bob Hinden wrote:<br>
    </div>
    <blockquote
      cite="mid:947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com"
      type="cite">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">In the short term, one thing I think would be helpful is to identify for the IETF participants which email providers are known to use DMARC and maybe also a list of providers that are known not to.   Maybe add it to the IETF mailing list page at <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/list/">https://www.ietf.org/list/</a> with an explanation of what's been happening.

</pre>
      </blockquote>
      <pre wrap="">This is a good idea.  Taking it a step further, perhaps a warning could be included when subscribing to an IETF list from an email provider who is known to use DMARC.

Bob


</pre>
    </blockquote>
    <p><br>
    </p>
    <p>I like that.<br>
    </p>
    <p>Actually, split the difference to start with - its probably a
      coding pass to personalize a warning based on provider.  So do a)
      Add a warning to the IETF mailing list page, b) add a warning to
      the confirm message that's sent out when you subscribe that
      contains the warning regardless of provider, and c) eventually
      customize the confirm message based on provider.</p>
    <p>Mike</p>
    <p><br>
    </p>
  </body>
</html>

--------------4563E5A32F7814C7770025BC--


From nobody Wed Mar  1 11:22:12 2017
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 C84F1129874 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kqy35bepe-m for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:22:09 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D761312967D for <ietf@ietf.org>; Wed,  1 Mar 2017 11:22:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v21JLvsS026068; Wed, 1 Mar 2017 20:21:57 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vYQLF2RRTzDHFD; Wed,  1 Mar 2017 20:21:57 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Mailing list membership.
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net>
Date: Wed, 1 Mar 2017 20:21:56 +0100
X-Mao-Original-Outgoing-Id: 510088916.581989-4c24ba2ae3fa6ebef60f10b671a4f8f8
Content-Transfer-Encoding: quoted-printable
Message-Id: <C796CA13-8D43-4423-9559-B1B494AB50BE@tzi.org>
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org> <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net> <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com> <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_cp4NJhXRIxubSuQyj34NATsMYE>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 19:22:11 -0000

On 1 Mar 2017, at 20:18, Michael StJohns <mstjohns@comcast.net> wrote:
>=20
> eventually customize the confirm message based on provider

Better: Send the subscription confirmation message with attributes that =
cause a DMARC-honoring provider to discard it :-)
(No programming required :-)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  1 11:24:43 2017
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 61AE912966C for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:24:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pSThS-9YryRI for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:24:40 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA75C1297F3 for <ietf@ietf.org>; Wed,  1 Mar 2017 11:24:40 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id j5so13818954pfb.2 for <ietf@ietf.org>; Wed, 01 Mar 2017 11:24:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=9t11+KEzMDY5KbiNVQ8I9htBQFt4aHWQlPBzkXUSCkc=; b=J4yEZNp7KHM4/BSY/Hd/HnNNRVVMdntBGGnTm8AEuQowvZIrCz+giu1amLmWBGJp08 y+swB7DFmMuU9SxHy4dn9eLVLSGUl1xLwmclKf9YrLs14Re8t7A/+sqK7O9xURyjZq04 KeBrAxy6QUpGeK4gf9+/NRHqrEbmY2QlxE8lttlJd3IpIrM+D+QrWa789235WgPQP4ph IX3ic4CxgF2jeDBDv4Ueb0idR8OygCsH4AiRIPcXLVRPzyTm3KvZhKdecP2KRTyfr3tO Bm7Gmz/OnG1OlfB+R1n25BbOoFB8KOSoqOuZxn8G80OvITt9uj4546Drn4CEN5XXfTBj E/JQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=9t11+KEzMDY5KbiNVQ8I9htBQFt4aHWQlPBzkXUSCkc=; b=OvUISPc5GUrMYwg5CCz11QPq1JPGVNRjs/rLDobfpMtoUAI7TUCx00zHMF8twvcr/k NaR5nQ8MO9NjctQVWOHZze1wZiYyHdTf3sU9q0vlBHT1zC/y3+Mn6KiGydkE27RGaK1I YhwQs7Gcs5oVhxvbDRIrH88xcYx4AlHvNn/5FllVACVoAS9NWOguzHfS6EQIDYuACgjh 20YizxUePe2i80icEb/az+8/vHoHnh24A6woSOKAeYnX9/Am4Azw6z7OrKvg4FqxLPNz A6tcQR/Gm+khAQZ+f/X9blo5WZoo5vzke7UTdAnPK3Y3wriZ3vlvroLApOvFWTNfCjVa /nlQ==
X-Gm-Message-State: AMke39lk6Dhj8zM/lQepiMlefC7kPpja13mWPbsv+eo89NgAigL/XvO2c/B/JKg3YXwapg==
X-Received: by 10.99.234.83 with SMTP id l19mr10732546pgk.114.1488396280088; Wed, 01 Mar 2017 11:24:40 -0800 (PST)
Received: from ?IPv6:2406:e007:6663:1:28cc:dc4c:9703:6781? ([2406:e007:6663:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id o24sm12123470pfj.78.2017.03.01.11.24.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Mar 2017 11:24:39 -0800 (PST)
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Patrick McManus <pmcmanus@mozilla.com>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com>
Date: Thu, 2 Mar 2017 08:24:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_ugCKC-a29LIGkRTRNtyEg69hDM>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 19:24:42 -0000

On 02/03/2017 06:07, Patrick McManus wrote:
> On Wed, Mar 1, 2017 at 11:04 AM, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
> 
>>
>> For the third time in two days I find myself, when asking others for
>> opinions
>> about some text, pointing at github commit logs.  With the beautiful
>> makefiles we often have, one can't even depend upon having a formatted .txt
>> version there!
> 
> 
> You can fix this with better tooling within github and travis integration
> fwiw. Checkout the httpbis github https://github.com/httpwg/http-extensions
> - you'll see the for each adopted draft the README.md has links to the
> "editor's draft" in both txt and html as well as the working group draft.
> The former is auto-generated on every push to the repo, the latter is a
> pointer to datatracker.
> 
> I'm not arguing against updating data tracker more often - just saying this
> 'editor's draft' convention can work very well between official revisions
> no matter the cadence a WG chooses.

The details of that discussion probably belong on ietf-and-github@ietf.org,
but I must point out that this way of working *excludes* from the 
discussion WG participants who don't grok github. Substantial issues
need to be discussed on the mailing list and substantial (non-typo)
revisions need to be posted as I-Ds.

    Brian


From nobody Wed Mar  1 11:29:40 2017
Return-Path: <willi.uebelherr@riseup.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 9D68C12967A for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:29:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6iaZe9d_0lO for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:29:38 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A39A129682 for <ietf@ietf.org>; Wed,  1 Mar 2017 11:29:38 -0800 (PST)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 993211A04EF for <ietf@ietf.org>; Wed,  1 Mar 2017 19:29:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488396577; bh=nEzjk+Guj6wZ9peD1ZNFTfin3Frjpv05X/P2BiiuqNw=; h=Subject:References:From:To:Date:In-Reply-To:From; b=pLXO99iuWRoq8idHWlZDLlP2vuJdxANasZWiVt0SutkWpezJ2j25Z2CWj7aZaqo9I fhYjNot319jZwzRCK2ldyyrRQ0sCFtzjp/neeajDav9PfhBOz0ubGb8DlIRspb8+Co gr/a7llwca804jL+tFNJorbBkZWvb+kunojer+ZM=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id F37AF1C253D
Subject: Re: Mailing list membership.
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org>
From: willi uebelherr <willi.uebelherr@riseup.net>
To: IETF discussion <ietf@ietf.org>
Message-ID: <6f8f6012-c393-e3d7-f3bc-2d70ef5fe217@riseup.net>
Date: Wed, 1 Mar 2017 16:29:01 -0300
MIME-Version: 1.0
In-Reply-To: <20170301044937.v3vhw3eqgqkxpoup@thunk.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m6mAPncWyl-QZ22KUM2AKhfnPO8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 19:29:39 -0000

Dear Theodore, many thanks for your explanation to the RFC 2821 (SMTP). 
The answer from Khaled i have included, because it goes to me as a 
private message.

Maybe, based on my bad english, i feel some confusion with the terms.

1) Khaled, like i and you, is member of the IETF discussion list. This 
means, he receive all emails that are distributed over the list.

2) Khaled, like i and you, use the maillist server mailman from IETF 
discussion list to distribute his messages to all members in the list.

3) The IETF discussion list don't follow the DMARC processing. This 
means, it act only outside.

4) Khaled, like i and you, use a mail box server system as the 
interconnection point to the list. Khaled use hotmail, you use mit.edu, 
i use riseup.net.

This means, the actors are the mailbox servers with the mailman maillist 
server IETF discuss in both direction.

I understand and agree absolutly, that the maillist server never change 
the From-line in the header. He create the Return-Path-line and/or 
Error-To-line for error response from the receiver mailbox server 
system. The bounce-information.

The mailman maillist server use bounce-counters for every member and 
some limits for this bounce-counter. If the limit exceeds, and the 
admin-group do nothing, then the maillist server mailman disable the 
delivery. It is not an unsubscription.

The admin-group have to follow the incremental increase of the 
bounce-counters to understand, what is the background. Maybe, the 
mailbox is full, or don't exist or is the result of this stupid DMARC 
processing.

The DMARC processing is defined in the DNS info. But we can ignore it, 
or not? The admin-group can inform the member to change her mailbox 
server to "avoid more errors" like Khaled wrote. The IETF discussion 
admin-group can only inform about the error sources. The members have to 
change her mailbox servers, or not?

Based on that process, we can clean all this nonsense in our IETF lists 
environment and work strong based on the RFC 2821, like mailman do it.

What do you think about?

many greetings, willi


On 01/03/2017 07:50, Khaled Omar wrote:
 > Hi Willi,
 >
 >> Mailman never change the "From"-header. Therefore, the From-Header 
always points to the author of the email. What you think, is that the 
correct, compatible way? I think, yes.
 >
 > Such case is out of our hands, other e-mail service providers are 
welcome to be used just if this will add a value and avoid more errors.
 >
 > Best Regards,
 > Khaled

On 01/03/2017 01:49, Theodore Ts'o wrote:
> On Tue, Feb 28, 2017 at 05:29:24PM -0300, willi uebelherr wrote:
>>
>> related to the problem, what Khaled explained, what is your proposal?
>>
>> What are your "compatible with internet mailing lists" mail systems?
>
> RFC 2821, Simple Mail Transfer Protocol, section 3.10.2
>
>    "To expand a list, the recipient mailer replaces the
>    pseudo-mailbox address in the envelope with all of the expanded
>    addresses.  The return address in the envelope is changed so that all
>    error messages generated by the final deliveries will be returned to
>    a list administrator, not to the message originator, who generally
>    has no control over the contents of the list and will typically find
>    error messages annoying."
>
> This is the SMTP Envelope From field.  The FROM field is not changed,
> but the SMTP return address is changed, so that bounces go to the
> mailing list administrator as opposed to the person who sends mail to
> the mailing list.
>
> Unfortunately, if you are using a system whose domain requests that
> all recipients enforce DMARC alignment, this specifically instructs
> recipients to bounce mail if the SMTP Envelope return address doesn't
> match the FROM field in the header.  This means that they won't see
> mailing list mail as defined by the IETF Standards Track RFC 2821,
> which specifically says that is acceptable (and in fact a good thing)
> to change the SMTP envelope return address so that bounces (caused by
> people changing where they work, etc.) go to an administrator who can
> deal with them.  But if the mailing list administrators gets too may
> bounces, and it's because the sending domain is requesting that mail
> be bounced, the only thing they can do is to unsubscribe the sender or
> the recipient.
>
> Hence mailing list systems that enforce DMARC, or request DMARC
> processing, are fundamentally incompatible with mailing lists as
> defined by section 3.10.2 of RFC 2821.
>
> If you want to participate in such mailing list, one of the best ways
> is to change to a mailing list system that doesn't do DMARC.
>
> Best regards,
> -Ted


From nobody Wed Mar  1 11:34:17 2017
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 3D5841298C4 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7naeBgk9YXoC for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 11:34:13 -0800 (PST)
Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A82A01298C2 for <ietf@ietf.org>; Wed,  1 Mar 2017 11:34:13 -0800 (PST)
Received: from pure.maildistiller.com (unknown [10.110.50.25]) by dispatch1-us1.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTP id B447C80168 for <ietf@ietf.org>; Wed,  1 Mar 2017 19:34:13 +0000 (UTC)
X-Virus-Scanned: Proofpoint Essentials engine
Received: from mx1-us4.ppe-hosted.com (unknown [10.110.49.250]) by pure.maildistiller.com (Proofpoint Essentials ESMTP Server) with ESMTPS id A0E0180051 for <ietf@ietf.org>; Wed,  1 Mar 2017 19:34:12 +0000 (UTC)
Received: from xpasc.com (96-82-113-225-static.hfc.comcastbusiness.net [96.82.113.225]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1-us4.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id 8EB1880060 for <ietf@ietf.org>; Wed,  1 Mar 2017 19:34:10 +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 v21JY9Mv007544 for <ietf@ietf.org>; Wed, 1 Mar 2017 11:34:09 -0800
Date: Wed, 1 Mar 2017 11:34:09 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: IETF <ietf@ietf.org>
Subject: Re: Mailing list membership.
In-Reply-To: <C796CA13-8D43-4423-9559-B1B494AB50BE@tzi.org>
Message-ID: <alpine.LRH.2.01.1703011132580.3764@egate.xpasc.com>
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org> <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net> <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com> <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net> <C796CA13-8D43-4423-9559-B1B494AB50BE@tzi.org>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-MDID: 1488396853-Gbu9kU+Neyer
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hwe2gsTQF1yfa92vk_URUHDL4xw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 19:34:16 -0000

On Wed, 1 Mar 2017, Carsten Bormann wrote:

> On 1 Mar 2017, at 20:18, Michael StJohns <mstjohns@comcast.net> wrote:
> >
> > eventually customize the confirm message based on provider
>
> Better: Send the subscription confirmation message with attributes that cause a DMARC-honoring provider to discard it :-)
> (No programming required :-)

No, that is worse as it insures support costs and more noise on this list.


From nobody Wed Mar  1 12:14:44 2017
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 E5E98120724 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 12:14:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eoOzF3AynRqs for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 12:14:42 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4AFF12968A for <ietf@ietf.org>; Wed,  1 Mar 2017 12:14:41 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QBGJ9U1RDS00JWDH@mauve.mrochek.com> for ietf@ietf.org; Wed, 1 Mar 2017 12:09:39 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QBGA77DHM80005AQ@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 01 Mar 2017 12:09:36 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01QBGJ9S1V7C0005AQ@mauve.mrochek.com>
Date: Wed, 01 Mar 2017 12:05:34 -0800 (PST)
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
In-reply-to: "Your message dated Thu, 02 Mar 2017 08:24:41 +1300" <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com> <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aILN4T2KVY8BaYv_1uLvHY42jWo>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 20:14:43 -0000

> > > For the third time in two days I find myself, when asking others for
> > > opinionsabout some text, pointing at github commit logs.  With the beautiful
> > > makefiles we often have, one can't even depend upon having a formatted .txt
> > > version there!

...

> The details of that discussion probably belong on ietf-and-github@ietf.org,
> but I must point out that this way of working *excludes* from the
> discussion WG participants who don't grok github. Substantial issues
> need to be discussed on the mailing list and substantial (non-typo)
> revisions need to be posted as I-Ds.

+1 on all points. Additionally, I've observed a seeming reluctance to update
drafts for small stuff, independent of the use or non-use of github.

Cases where it's actually best to withhold an update are quite rare, so having
this practice as a default really needs to go away.

				Ned


From nobody Wed Mar  1 12:22:29 2017
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 0F4C7129692 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 12:22:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upAQcW1Oc6k5 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 12:22:26 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79B60120724 for <ietf@ietf.org>; Wed,  1 Mar 2017 12:22:26 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cjAlT-000A97-PQ; Wed, 01 Mar 2017 15:22:23 -0500
Date: Wed, 01 Mar 2017 15:22:17 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Patrick McManus <pmcmanus@mozilla.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
Message-ID: <B84F48D5CB1E262E120316CA@PSB>
In-Reply-To: <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com> <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@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
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TrxJYix397ohkWteAlQSt39Y_8Q>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 20:22:28 -0000

--On Thursday, March 2, 2017 08:24 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
>> I'm not arguing against updating data tracker more often -
>> just saying this 'editor's draft' convention can work very
>> well between official revisions no matter the cadence a WG
>> chooses.
> 
> The details of that discussion probably belong on
> ietf-and-github@ietf.org, but I must point out that this way
> of working *excludes* from the  discussion WG participants who
> don't grok github. Substantial issues need to be discussed on
> the mailing list and substantial (non-typo) revisions need to
> be posted as I-Ds.

Brian,

It is a bit more than "not grokking".  For any given WG, or
task/document within a WG, there are three plausible ways to
review an emerging document:

(1) Very active participation, including tracking and
understanding all changes, more or less in real time.  

(2) Intermittent review of snapshots, ones that are generally
believed by their editors to be coherent and self-consistent.
Github revision tracking often makes that approach very
burdensome; change logs in documents and diffs between versions
are often more helpful.

(3) Simply deciding it is all or nothing and waiting until IETF
Last Call.

Only the first really makes effective use of the github style of
doing things.

The recent discussion about comments at Last Call rather than
while the WG was actively developing a document, including the
"don't have time" subthread obviously interact with this.

Also, IANAL, but if a change were contemplated, it might be
useful to ask appropriate ones whether, if questions ever arose
about when particular things happened, it would be easier or
more effective to explain an I-D and related WG consensus
discussions to a judge or jury or whether github editing traces
were easier.  

    john




From nobody Wed Mar  1 13:01:01 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90EDA1296B2 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 13:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level: 
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.08, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RYpaUnvY1S4S for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 13:00:56 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 596EF12967C for <ietf@ietf.org>; Wed,  1 Mar 2017 13:00:56 -0800 (PST)
Received: (qmail 82694 invoked from network); 1 Mar 2017 21:00:55 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 1 Mar 2017 21:00:55 -0000
Date: 1 Mar 2017 21:00:33 -0000
Message-ID: <20170301210033.1672.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: yet more DMARC stuff, was Re: Mailing list membership.
In-Reply-To: <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w-jWe83CRkoxKIeYdtG2h_UTDYc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 21:00:58 -0000

In article <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net> you write:
>> This is a good idea.  Taking it a step further, perhaps a warning could be included when
>subscribing to an IETF list from an email provider who is known to use DMARC.

You can tell who publishes DMARC policies, but without experimentation
you can't tell who follows them on inbound mail.

Of the large public mail providers, only AOL and Yahoo currently
publish DMARC policies, but Gmail certainly looks at DMARC, albeit as
part of the special sauce so a Gmail user might get mail with DMARC
problems or might not.  I'm reasonably sure that Hotmail and Comcast
also look at DMARC on incoming mail.  DMARC is surprisingly useful for
blocking phishes, which is a big issue for consumer mail providers, so
the providers that use it are not going to stop.

R's,
John

PS: I presume you all know that we've been working on workarounds.


From nobody Wed Mar  1 13:41:47 2017
Return-Path: <pmcmanus@mozilla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C4DB12948E for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 13:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.734
X-Spam-Level: 
X-Spam-Status: No, score=-0.734 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ntOZoIBVO90d for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 13:41:43 -0800 (PST)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id 90DE9129539 for <ietf@ietf.org>; Wed,  1 Mar 2017 13:41:43 -0800 (PST)
Received: from mail-qk0-f178.google.com (mail-qk0-f178.google.com [209.85.220.178]) by linode64.ducksong.com (Postfix) with ESMTPSA id F0B4D3A0A3 for <ietf@ietf.org>; Wed,  1 Mar 2017 16:41:42 -0500 (EST)
Received: by mail-qk0-f178.google.com with SMTP id u188so93635964qkc.2 for <ietf@ietf.org>; Wed, 01 Mar 2017 13:41:42 -0800 (PST)
X-Gm-Message-State: AMke39lMAXep6FPTLW7n9qvS3nIpKrY5T12NnBfBDm2wwh21PdK20+Yd10J0E+JOk5xCQy8dZXzKVYiV2PzXQw==
X-Received: by 10.200.34.144 with SMTP id f16mr13575627qta.186.1488404502559;  Wed, 01 Mar 2017 13:41:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.177.130 with HTTP; Wed, 1 Mar 2017 13:41:41 -0800 (PST)
In-Reply-To: <B84F48D5CB1E262E120316CA@PSB>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com> <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com> <B84F48D5CB1E262E120316CA@PSB>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Wed, 1 Mar 2017 16:41:41 -0500
X-Gmail-Original-Message-ID: <CAOdDvNrM7=bmgMxB=0NSOmQf_AxcMisUYYTJwW09K+-x4JnA5g@mail.gmail.com>
Message-ID: <CAOdDvNrM7=bmgMxB=0NSOmQf_AxcMisUYYTJwW09K+-x4JnA5g@mail.gmail.com>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a113f41fea8a5a00549b22d3e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l_g9An8kaD9h2maNHcaXHGCOwQg>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 21:41:45 -0000

--001a113f41fea8a5a00549b22d3e
Content-Type: text/plain; charset=UTF-8

Hi All,

This thread started with a comment that github versions that lived
in-between ID versions did not have plain text representations - and
hopefully that specific misconception has been put to bed with the
counterexample of reasonable tooling mentioned upthread. Apparently this
has unearthed a spirited defense of the old way against a new way. So let
me espouse the virtues of the new way using John's outline for paradigms of
participation in a wg.


> (1) Very active participation, including tracking and
> understanding all changes, more or less in real time.
>
>
what tends to happen for this scenario in a github world is that a lot of
the native-wg-email moves into github-issues-email (you can still subscribe
and reply to these directly from your mailer or via any number of
alternative github interfaces) - with much more disciplined threading than
happens traditionally. A busy document benefits greatly from the tagging
these issues can have - an extra level of metadata and state tracking that
email alone can't give you. Multiple suggestions can be attached as pull
requests to the issues and each can be discussed independently and in
context - again, that discussion can all be gatewayed to email. I promise
you will still send and receive too much email - I have 18 github gatewayed
comments re QUIC in my inbox in the last 24 hours. Each one very specific
and substantive - Its just a better structured wg discussion in my inbox.
But the unstructured list persists for topics that aren't ready a github
issue yet. TBH if I were to only read one of them it would be the github
issue gateway - the signal to noise ratio is better.

have a look at
https://github.com/quicwg/base-drafts/issues?utf8=%E2%9C%93&q=is%3Aissue ..
what I see is essentially a very well threaded mailing list archive plus
some useful metadata (classifications, open-vs-resolved, tags about stuff
that needs more discussion, issues that are basically decided but an editor
needs to propose some text, etc..). And you can consume/contribute with a
mailer if you are happy with the old way.


> (2) Intermittent review of snapshots, ones that are generally
> believed by their editors to be coherent and self-consistent.
> Github revision tracking often makes that approach very
> burdensome; change logs in documents and diffs between versions
> are often more helpful.
>

This seems to suggest that github based drafts go from -00 to WGLC with
interim changes only happening on github. That's not the way it works in my
experience - to me it feels like the same number of drafts are produced
(some data here would be interesting.. http/2 had around 19 revisions at
the end iirc even though we used github extensively.. I believe tls 1.3 is
on draft 19 or 20 and it is also github centric) and they continue to have
changelogs. Git pushes that are not also uploaded to datatracker are simply
a better (more visible) version of the locally saved version an editor has
always done in between updates. Periodically, new datatracker releases are
made to garner wider visibility, test interop, and as a signal that things
are, as you say, internally consistent.

Reviewing these new datatracker revs can be done the same as always (diff
between -N and -N+1, changelogs, etc..), but it can also be *so much more*..
you can git blame your way back to a changeset and probably an issue # from
the commit message.. from there you can read the discussion that went into
the change if you weren't able to tune in in real time. If you're not cool
with the way things stand, you just open a new issue (or send an email to
the list and the editor or chair will open an issue).

If you want to review two non-data tracker revisions (e.g. you normally
track things in real time but you were out of office for a week) you can
use the same tools but with git revisions. version control software is
pretty good at that :)


> (3) Simply deciding it is all or nothing and waiting until IETF
> Last Call.
>
> Only the first really makes effective use of the github style of
> doing things.
>
>
I disagree with this conclusion - the accumulated repo history is most
valuable near the end of the process. We finally have something more than a
messy email database as a record of the process.

This is especially powerful during the last calls, when issues from
some-time-ago can be re-raised (hopefully with new information!).. rather
than everyone spelunking through the archives to remember how it ended up
like that (or simply retorting 'read the archive') there is some structure
to the history of the document - the 'git blame' and the closed issue
threads intersect powerfully for understanding how consensus was reached.

There is also the added bonus of having to close all the open issues before
a document can be published. Stuff doesn't get lost in the shuffle (though
it may be over taken by other changes and closed without action - but at
least it is done with deliberate review). Its better project management.

I freely admit I am discussing what are emerging as best practices and I
hope ietf-and-github@ietf.org helps codify some of this. This system could
certainly be run poorly - but that's not a reason for avoiding well run
ones. The old email and upload XML snapshot approach doesn't live in the
Internet ecosystem that we seek to serve for good reasons.

--001a113f41fea8a5a00549b22d3e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><div>Hi All,<br><br>This thread=20
started with a comment that github versions that lived in-between ID versio=
ns did not have=20
plain text representations - and hopefully that specific misconception has =
been put to bed with=20
the counterexample of reasonable tooling mentioned upthread. Apparently thi=
s has unearthed a spirited defense of the old way against a new way. So let=
 me espouse the virtues of the new way using John&#39;s outline for paradig=
ms of participation in a wg.<br></div>=C2=A0<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">
(1) Very active participation, including tracking and<br>
understanding all changes, more or less in real time.<br>
<br></blockquote><div>=C2=A0</div><div>what tends to happen for this scenar=
io in a github world is that a lot of the native-wg-email moves into github=
-issues-email (you can still subscribe and reply to these directly from you=
r mailer or via any number of alternative github interfaces) - with much mo=
re disciplined threading than happens traditionally. A busy document benefi=
ts greatly from the tagging these issues can have - an extra level of metad=
ata and state tracking that email alone can&#39;t give you. Multiple sugges=
tions can be attached as pull requests to the issues and each can be discus=
sed independently and in context - again, that discussion can all be gatewa=
yed to email. I promise you will still send and receive too much email - I =
have 18 github gatewayed comments re QUIC in my inbox in the last 24 hours.=
 Each one very specific and substantive - Its just a better structured wg d=
iscussion in my inbox. But the unstructured list persists for topics that a=
ren&#39;t ready a github issue yet. TBH if I were to only read one of them =
it would be the github issue gateway - the signal to noise ratio is better.=
<br></div><div><br></div><div>have a look at <a href=3D"https://github.com/=
quicwg/base-drafts/issues?utf8=3D%E2%9C%93&amp;q=3Dis%3Aissue">https://gith=
ub.com/quicwg/base-drafts/issues?utf8=3D%E2%9C%93&amp;q=3Dis%3Aissue</a> ..=
 what I see is essentially a very well threaded mailing list archive plus s=
ome useful metadata (classifications, open-vs-resolved, tags about stuff th=
at needs more discussion, issues that are basically decided but an editor n=
eeds to propose some text, etc..). And you can consume/contribute with a ma=
iler if you are happy with the old way.<br></div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
(2) Intermittent review of snapshots, ones that are generally<br>
believed by their editors to be coherent and self-consistent.<br>
Github revision tracking often makes that approach very<br>
burdensome; change logs in documents and diffs between versions<br>
are often more helpful.<br></blockquote><div><br></div><div>This seems to s=
uggest that github based drafts go from -00 to WGLC with interim changes on=
ly happening on github. That&#39;s not the way it works in my experience - =
to me it feels like the same number of drafts are produced (some data here =
would be interesting.. http/2 had around 19 revisions at the end iirc even =
though we used github extensively.. I believe tls 1.3 is on draft 19 or 20 =
and it is also github centric) and they continue to have changelogs. Git pu=
shes that are not also uploaded to datatracker are simply a better (more vi=
sible) version of the locally saved version an editor has always done in be=
tween updates. Periodically, new datatracker releases are made to garner wi=
der visibility, test interop, and as a signal that things are, as you say, =
internally consistent.<br><br></div><div>Reviewing these new datatracker re=
vs can be done the same as always (diff between -N and -N+1, changelogs, et=
c..), but it can also be <b>so much more</b>.. you can git blame your way b=
ack to a changeset and probably an issue # from the commit message.. from t=
here you can read the discussion that went into the change if you weren&#39=
;t able to tune in in real time. If you&#39;re not cool with the way things=
 stand, you just open a new issue (or send an email to the list and the edi=
tor or chair will open an issue).<br><br></div><div>If you want to review t=
wo non-data tracker revisions (e.g. you normally track things in real time =
but you were out of office for a week) you can use the same tools but with =
git revisions. version control software is pretty good at that :)<br></div>=
<div><br></div><div></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>
<br>
(3) Simply deciding it is all or nothing and waiting until IETF<br>
Last Call.<br>
<br>
Only the first really makes effective use of the github style of<br>
doing things.<br>
<br>
</blockquote><div><br></div><div>I disagree with this conclusion - the accu=
mulated repo history is most valuable near the end of the process. We final=
ly have something more than a messy email database as a record of the proce=
ss.<br><br><div>This is especially powerful during the last calls, when iss=
ues from
 some-time-ago can be re-raised (hopefully with new information!)..=20
rather than everyone spelunking through the archives to remember how it=20
ended up like that (or simply retorting &#39;read the archive&#39;) there i=
s=20
some structure to the history of the document - the &#39;git blame&#39; and=
 the closed issue threads intersect powerfully for understanding how consen=
sus was reached.<br><br></div>There is
 also the added bonus of having to close all the open issues before a
 document can be published. Stuff doesn&#39;t get lost in the shuffle=20
(though it may be over taken by other changes and closed without action -
 but at least it is done with deliberate review). Its better project manage=
ment.<br><br></div><div>I freely admit I am discussing what are emerging as=
 best practices and I hope <a href=3D"mailto:ietf-and-github@ietf.org">ietf=
-and-github@ietf.org</a> helps codify some of this. This system could certa=
inly be run poorly - but that&#39;s not a reason for avoiding well run ones=
. The old email and upload XML snapshot approach doesn&#39;t live in the In=
ternet ecosystem that we seek to serve for good reasons.<br></div></div></d=
iv></div>

--001a113f41fea8a5a00549b22d3e--


From nobody Wed Mar  1 14:48:01 2017
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 3F59E129667 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 14:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sbNK0b3OKyaC for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 14:47:59 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D27C1293D8 for <ietf@ietf.org>; Wed,  1 Mar 2017 14:47:59 -0800 (PST)
Received: from [128.9.184.129] ([128.9.184.129]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v21MlYLi018875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 1 Mar 2017 14:47:35 -0800 (PST)
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
References: <14476.1488384266@obiwan.sandelman.ca>
From: Joe Touch <touch@isi.edu>
Message-ID: <13e5803d-c2f3-7bc8-63c8-2a8311c22fae@isi.edu>
Date: Wed, 1 Mar 2017 14:47:34 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <14476.1488384266@obiwan.sandelman.ca>
Content-Type: multipart/alternative; boundary="------------945CA305A64E9AD02F7AA25D"
X-MailScanner-ID: v21MlYLi018875
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AL6NCCaozY-XeOQrMwtdyAOp7NQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2017 22:48:00 -0000

This is a multi-part message in MIME format.
--------------945CA305A64E9AD02F7AA25D
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit



On 3/1/2017 8:04 AM, Michael Richardson wrote:
> I understand that in academia, they never like letting half-baked ideas out,
> and so the -00 that we see from academics are often overdue and overly
> polished. 
FWIW, industry often doesn't let out ideas until filing preliminary
patents, which has a similar effect.

AFAICT, the speed of an -00 is more tightly correlated to the motivation
for the document.

When a WG has a known need for a particular doc, the -00 comes out
earlier (pull model).

When an idea is driven by the doc itself (push model), it's more useful
to have enough in place to have a useful discussion about.

That said, I really wish that -00s that aren't pull-driven would try to
stay under 5 pages of content. Dumping dozens of pages and asking for
feedback isn't a good way to *_start _*a discussion.

Joe

--------------945CA305A64E9AD02F7AA25D
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 3/1/2017 8:04 AM, Michael Richardson
      wrote:<br>
    </div>
    <blockquote cite="mid:14476.1488384266@obiwan.sandelman.ca"
      type="cite">
      <pre wrap="">I understand that in academia, they never like letting half-baked ideas out,
and so the -00 that we see from academics are often overdue and overly
polished. </pre>
    </blockquote>
    FWIW, industry often doesn't let out ideas until filing preliminary
    patents, which has a similar effect.<br>
    <br>
    AFAICT, the speed of an -00 is more tightly correlated to the
    motivation for the document.<br>
    <br>
    When a WG has a known need for a particular doc, the -00 comes out
    earlier (pull model).<br>
    <br>
    When an idea is driven by the doc itself (push model), it's more
    useful to have enough in place to have a useful discussion about.<br>
    <br>
    That said, I really wish that -00s that aren't pull-driven would try
    to stay under 5 pages of content. Dumping dozens of pages and asking
    for feedback isn't a good way to <b><u>start </u></b>a discussion.<br>
    <br>
    Joe<br>
  </body>
</html>

--------------945CA305A64E9AD02F7AA25D--


From nobody Wed Mar  1 16:14:22 2017
Return-Path: <willi.uebelherr@riseup.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 DB78212945F for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 16:14:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xJTI9STkdLhI for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 16:14:20 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B843129443 for <ietf@ietf.org>; Wed,  1 Mar 2017 16:14:20 -0800 (PST)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id C17B91A1BDE for <ietf@ietf.org>; Thu,  2 Mar 2017 00:14:19 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488413659; bh=QvHP+MbrxDq7Wt4gzbNGu8p6YEpodPyKbGlurNctuhs=; h=Subject:References:From:To:Date:In-Reply-To:From; b=jA3YOwpIKzRPRFf8GLfO0EAVxIpNdyO+fo+mYHGhdzSGJZ4rv4mGVWdlnIxSWT6CN ZiRllxjs3V6G+9+O9YQ8xhQjWe5SMCCVO8VZ4A1X+s6B9a44YCHRjjVTi9pvXN4WUR 3NOMuLqgzvQdVBoHm/eNI39kdGfk02YaXUN2Xupk=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id 2372D1C22F8
Subject: Re: Mailing list membership.
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org> <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net> <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com> <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net> <C796CA13-8D43-4423-9559-B1B494AB50BE@tzi.org>
From: willi uebelherr <willi.uebelherr@riseup.net>
To: IETF <ietf@ietf.org>
Message-ID: <a66339b0-bdb8-c64a-55a5-83ff8cab59f3@riseup.net>
Date: Wed, 1 Mar 2017 21:13:55 -0300
MIME-Version: 1.0
In-Reply-To: <C796CA13-8D43-4423-9559-B1B494AB50BE@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GRH0OUBpg5tLLvKLiYGJC8qbHQU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 00:14:21 -0000

Dear Carsten,

super! But what are this attributes, that brings the "DMARC honoring 
providers" to hiccup? (in german Schluckauf).

many greetings, willi


On 01/03/2017 16:21, Carsten Bormann wrote:
> On 1 Mar 2017, at 20:18, Michael StJohns <mstjohns@comcast.net> wrote:
>>
>> eventually customize the confirm message based on provider
>
> Better: Send the subscription confirmation message with attributes that cause a DMARC-honoring provider to discard it :-)
> (No programming required :-)
>
> Grüße, Carsten
>
>


From nobody Wed Mar  1 16:35:37 2017
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 57AF9129447 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 16:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zT9BeHDWidf0 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 16:35:33 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A279B129478 for <ietf@ietf.org>; Wed,  1 Mar 2017 16:35:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v220ZRMY000466; Thu, 2 Mar 2017 01:35:27 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vYYHy6HWSzDHHx; Thu,  2 Mar 2017 01:35:26 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Mailing list membership.
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <alpine.LRH.2.01.1703011132580.3764@egate.xpasc.com>
Date: Thu, 2 Mar 2017 01:35:25 +0100
X-Mao-Original-Outgoing-Id: 510107725.361913-e980b30861daa40482ae1a8257e7a051
Content-Transfer-Encoding: quoted-printable
Message-Id: <ADF97FF4-F62E-4A2D-A538-84DC69F0DCD0@tzi.org>
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org> <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net> <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com> <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net> <C796CA13-8D43-4423-9559-B1B494AB50BE@tzi.org> <alpine.LRH.2.01.1703011132580.3764@egate.xpasc.com>
To: David Morris <dwm@xpasc.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_R1G5pH_Cwt-gnxBbleEczP3x3Q>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 00:35:36 -0000

> On 1 Mar 2017, at 20:34, David Morris <dwm@xpasc.com> wrote:
>=20
>=20
>=20
> On Wed, 1 Mar 2017, Carsten Bormann wrote:
>=20
>> On 1 Mar 2017, at 20:18, Michael StJohns <mstjohns@comcast.net> =
wrote:
>>>=20
>>> eventually customize the confirm message based on provider
>>=20
>> Better: Send the subscription confirmation message with attributes =
that cause a DMARC-honoring provider to discard it :-)
>> (No programming required :-)
>=20
> No, that is worse as it insures support costs and more noise on this =
list.

I apologize for trying to inject some humor into this serious matter.

Silently dropping subscription requests isn=E2=80=99t very nice.  So =
there probably should be a second (DMARC-unencumbered) message telling =
people to expect the confirmation request message and to use a different =
mail system if it does not arrive.

I do not agree that actively preventing DMARC-honoring addresses from =
subscribing would be worse than the current situation, where the =
subscriber thinks they are on, only to be kicked off after a short while =
(or, worse, simply not receiving some of the messages).

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  1 16:36:42 2017
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 5554412946C for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 16:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.37
X-Spam-Level: 
X-Spam-Status: No, score=-2.37 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id epXqqu6XRq53 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 16:36:38 -0800 (PST)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFE05129696 for <ietf@ietf.org>; Wed,  1 Mar 2017 16:36:38 -0800 (PST)
Received: by mail-io0-x230.google.com with SMTP id l7so43201402ioe.3 for <ietf@ietf.org>; Wed, 01 Mar 2017 16:36:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=H9Pth/Tu8gze+J5nH+WpbMU6jPkE9oiZhzvpihsQ0IY=; b=OJanaVPtuNG6oghp71u1DRWwQkS0R6rnTDkQYvBs1mvdfjW5zuwIGej6tCrqbO609a mXFZG+6Togs8Jij5chgnnRU4p8Jo+YOOcbYS9H5l3XKYKXd/7GgVsfO1yCbGD+4Fa1yg C5tzJ4PYy46KdSBBh2p/OC9ya1x0fs7Tn4JqzUamPsCnoQM34O4enIPwW8k6XVyXVSZf H5PEwqXazmAsnVRRXBnM7mtS9MXtRNn3NCnKNI76vA0q4xXPQWqIJdmNM2xW6Um8y2YE /3YQpEJCjqnczAfElVbTqkjG0dUJDtinIepN6YWbiOSvAKI/5bUhNkBfvsOTcC8HYFwU dk8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=H9Pth/Tu8gze+J5nH+WpbMU6jPkE9oiZhzvpihsQ0IY=; b=uasSagJGht5pcr4nGnW2TwC8c/x8HOrX/bCpZD0YaYu202LUqSg1oHCCVprb7RH+71 DtWaU9O4dyGn1K8TAsGsAWFTJz44BdHOhh2yHjv9fB+2CSUjWG2PFPNCQQywF4wQFw2x 0rQKLA0zoxCdvTvbFvg8TYb7qQbxPsdPlnzXA/k36cwq2bAjwJmgAixAsVGElzlM+zdn 8eK4URSKQPTHBso2MpXJMlQ7ZhlpGOkP5MX+JS2xOSUG8dogBQS+ZdayAGjgUYfChrXH 3rExUmaVD5O9ivYxRriKN4aL4kMv48rVqHTzGTOsLO3ilKEouZWsSU5ufdOdzO843yL4 aPLQ==
X-Gm-Message-State: AMke39lHJALDpvUS5QCld+nbvMBVHqnNFc8ZEAnO0S2Zh3nl0wrCQsT6onJpZYPVaGqX80DdEd6xdVrcHlOP1Q==
X-Received: by 10.107.187.133 with SMTP id l127mr11379953iof.1.1488414998064;  Wed, 01 Mar 2017 16:36:38 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.35.200 with HTTP; Wed, 1 Mar 2017 16:36:37 -0800 (PST)
In-Reply-To: <a66339b0-bdb8-c64a-55a5-83ff8cab59f3@riseup.net>
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org> <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net> <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com> <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net> <C796CA13-8D43-4423-9559-B1B494AB50BE@tzi.org> <a66339b0-bdb8-c64a-55a5-83ff8cab59f3@riseup.net>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 1 Mar 2017 16:36:37 -0800
X-Google-Sender-Auth: ORVonwk-auOcj0Zw4J-H3bFknIo
Message-ID: <CAC4RtVC4YEs-yEK8cuKPxdn0kBwSosh+3K2-AGM3uAx-94U-Bw@mail.gmail.com>
Subject: Re: Mailing list membership.
To: willi uebelherr <willi.uebelherr@riseup.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mEf2N4FjlUnmQ9r2F_0a5_RJj0A>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 00:36:40 -0000

> super! But what are this attributes, that brings the "DMARC honoring
> providers" to hiccup? (in german Schluckauf).

I'm not sure what you're asking, but let me explain "the DMARC
problem", in case that's what you want to know (and for any who aren't
already aware of it):

- Bob posts to a mailing list from <bob@example.com>, and example.com
is a domain that publishes a DMARC record with the "p=reject"
parameter.

- (The example.com domain does this because it doesn't like people to
send mail that says "From: <address@example.com>" when the mail is not
actually from an address at example.com.  It's a brand-protection
issue, to oversimplify a bit.)

- The mailing list prepends "[listname]" to the subject line, and
probably sticks some "from the mailing list" text at the end of the
message... and then sends it on to the subscribers, leaving the
"From:" line unchanged (so it still says <bob@example.com>).

- Carol and Ted and Alice are all mailing list subscribers, so each of
them is sent a copy of the message.

- Alice is <alice@nicedomain.example>, and nicedomain.example looks up
and honours DMARC records.

- The nicedomain.example mail server checks SPF.  It looks up the SPF
record for example.com and it sees that the IP address the mail is
coming from (which belongs to the list sever) is not authorized to
send mail as example.com.  So the SPF check fails.

- The nicedomain.example mail server checks DKIM.  It finds the DKIM
signature in the message and tries to verify it.  But the changes the
list server made to the message (the subject line and the stuff at the
end) broke the DKIM signature.  So the DKIM check fails.

- The nicedomain.example mail server has not been able to authenticate
the message with respect to the domain in the "From" line
(example.com), so it looks up example.com's DMARC record to see what
example.com's policy says.  And it says "p=reject".

- Honouring that, nicedomain.example rejects ("bounces") the message.

- The bounce message goes back to the mailing list server.

- The mailing list server sees that a list message it sent to Alice
bounced, so it increments the bounce count for Alice.

- After a few such messages, Alice's bounce count exceeds the
threshold for the mailing list software, and she is unsubscribed from
the list.

Now, of course, Alice can re-subscribe, but the same thing will
eventually happen again... and again.

Some workarounds include asking Bob to post from an address at a
domain that doesn't publish "p=reject", and/or asking Alice to
subscribe from an address at a domain that doesn't reject messages
based on DMARC policies.  There are also workarounds that can be done
in the list server, each of which creates its own problems.  None of
these workarounds are ideal.

The DMARC working group is working on a protocol called ARC, which is
aimed at fixing some of these issues.

(Hoping this has helped some people to understand what's going on...)

-- 
Barry


From nobody Wed Mar  1 17:04:13 2017
Return-Path: <mfidelman@meetinghouse.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 93F89129445 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 17:04:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G0OpGegsk9Jj for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 17:04:11 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id E58DE129431 for <ietf@ietf.org>; Wed,  1 Mar 2017 17:04:10 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id F04D54F80B9 for <ietf@ietf.org>; Wed,  1 Mar 2017 20:04:09 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id hdyzxndJvOUg for <ietf@ietf.org>; Wed,  1 Mar 2017 20:04:08 -0500 (EST)
Received: from Miless-MacBook-Pro.local (ip98-167-249-95.ph.ph.cox.net [98.167.249.95]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 30E434F80B2 for <ietf@ietf.org>; Wed,  1 Mar 2017 20:04:08 -0500 (EST)
Subject: Re: Mailing list membership.
To: ietf@ietf.org
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org> <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net> <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <a43346b6-82ca-ec59-705a-061940299699@meetinghouse.net>
Date: Wed, 1 Mar 2017 18:04:06 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eJg39f0ZndgK5vzmyVhLVBZl56E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 01:04:12 -0000

On 3/1/17 12:14 PM, Bob Hinden wrote:

> Mike,
>
>> On Mar 1, 2017, at 10:55 AM, Michael StJohns <mstjohns@comcast.net> wrote:
>>
>>> Hence mailing list systems that enforce DMARC, or request DMARC
>>> processing, are fundamentally incompatible with mailing lists as
>>> defined by section 3.10.2 of RFC 2821.
>>>
>>> If you want to participate in such mailing list, one of the best ways
>>> is to change to a mailing list system that doesn't do DMARC.
>>>
>>> Best regards,
>>>
>>> 						- Ted
>>>
>> Thanks for the clear description of the problem - I admit that I got a similar one from folks at the Seoul IETF.
>>
>> In the short term, one thing I think would be helpful is to identify for the IETF participants which email providers are known to use DMARC and maybe also a list of providers that are known not to.   Maybe add it to the IETF mailing list page at https://www.ietf.org/list/ with an explanation of what's been happening.
>>
> This is a good idea.  Taking it a step further, perhaps a warning could be included when subscribing to an IETF list from an email provider who is known to use DMARC.
>
Yes, but that warning should be on the subscription web page, or the 
list manager should be tuned to make sure that the warning notice 
doesn't get rejected by DMARC!

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Wed Mar  1 17:38:47 2017
Return-Path: <willi.uebelherr@riseup.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 3E150129504 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 17:38:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ol_mqFRPXKr for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 17:38:44 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A3011293F2 for <ietf@ietf.org>; Wed,  1 Mar 2017 17:38:44 -0800 (PST)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 8D0F91A196C for <ietf@ietf.org>; Thu,  2 Mar 2017 01:38:43 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488418723; bh=nAX8RUX9ySuo8WnYzV0M+M5ddDwO0a0CcI8TlueFABg=; h=Subject:References:From:To:Date:In-Reply-To:From; b=Teirpssjokq8CVcJv5pfUrdBBL9l/BlbZBHJ+EsoKB8K0mgX3fXN13/xtH9aS3rNK T66g4u24oqIsINJCvCwRRnyl4bKtzPUfRubmSFQjwxgpaPRYOlt7w+Qn4Kgds/WiQq SiWFnq0qaGkfc16loiyJ0OFyIzrOFFmVR59YDEDs=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id D50DA1C0086
Subject: Re: [Mailman-Users] Fwd: Re: Mailing list membership.
References: <CAGfsgR0bCWOr7_fY6ZEVLkvcwV3nf+xTGYvjWd02ryBJtM0FGA@mail.gmail.com>
From: willi uebelherr <willi.uebelherr@riseup.net>
To: IETF discussion <ietf@ietf.org>
X-Forwarded-Message-Id: <CAGfsgR0bCWOr7_fY6ZEVLkvcwV3nf+xTGYvjWd02ryBJtM0FGA@mail.gmail.com>
Message-ID: <e43a2790-d4d6-91cf-f5cc-645581fba973@riseup.net>
Date: Wed, 1 Mar 2017 22:38:19 -0300
MIME-Version: 1.0
In-Reply-To: <CAGfsgR0bCWOr7_fY6ZEVLkvcwV3nf+xTGYvjWd02ryBJtM0FGA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QDeZkwAZWvtDQBrG8hCzy6rwilI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 01:38:45 -0000

Dear friends,

Jim Popowitch from the mailman user list sent this answer. But i wait 
also for an answer from Mark Sapiro. I don't know what the mailman 
developers changed in the newer versions in relation to the DMARC 
processing.

many greetings, willi


-------- Forwarded Message --------
Subject: Re: [Mailman-Users] Fwd: Re: Mailing list membership.
Date: Wed, 1 Mar 2017 19:06:43 -0500
From: Jim Popovitch <jimpop@gmail.com>
To: mailman-users@python.org
CC: willi uebelherr <willi.uebelherr@gmail.com>

On Wed, Mar 1, 2017 at 2:44 PM, willi uebelherr
<willi.uebelherr@gmail.com> wrote:
> What you think about?

IETF is running Mailman v2.1.17, I think you need to upgrade and take
advantage of the DMARC processing in newer versions of Mailman.

-Jim P.


From nobody Wed Mar  1 18:05:46 2017
Return-Path: <mcr+ietf@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 16C4B129646 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 18:05:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4OCRJVKjKzJF for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 18:05:44 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27C021295EB for <ietf@ietf.org>; Wed,  1 Mar 2017 18:05:44 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id D98DE2009E; Wed,  1 Mar 2017 21:28:02 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 692A36381A; Wed,  1 Mar 2017 21:05:43 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Joe Touch <touch@isi.edu>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
In-Reply-To: <13e5803d-c2f3-7bc8-63c8-2a8311c22fae@isi.edu>
References: <14476.1488384266@obiwan.sandelman.ca> <13e5803d-c2f3-7bc8-63c8-2a8311c22fae@isi.edu>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 01 Mar 2017 21:05:43 -0500
Message-ID: <17514.1488420343@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LaFuM85sj6QsjO6YJcKjFpeKblI>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 02:05:45 -0000

--=-=-=
Content-Type: text/plain


Joe Touch <touch@isi.edu> wrote:
    > FWIW, industry often doesn't let out ideas until filing preliminary
    > patents, which has a similar effect.

    > AFAICT, the speed of an -00 is more tightly correlated to the
    > motivation for the document.

Good point, but tell me why -01 and -09 and -17 don't come out faster?
If it's because the authors are busy, and aren't working on that document,
that's fine.  But I'm seeing some kind of shyness to putting new versions out.

Is there a distrust of documents which have "too many" revisions?
I consider that often a good sign!

Should the beautiful history bar in the datatracker, have some measure of
changes?  Would graph of lines changed (in the XML!) per revision be
interesting?   Would that help know how close a document is to being ready?


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAli3ffcACgkQgItw+93Q
3WX34ggAk0O5AFjgcdTV68SojZ7clNd8lkHMlJ37uoijyrnT44Y/fkGYs8K5ahlU
npjY159iK1rjWz6fSnqo8LZeKLynOFQt2WtunYPNy//K29wYklVOlx1vyPapDznP
UsReOzofFeCGxpGpFXqyI5S6HUCZ8ibRKozmxOMCPmaYywor++mJ08Ca6dAPrMxQ
inJm9A4YsnbXFr6UXwAXFbM0UULzqXcJyYBEnNqNWrake3C2spug4gfdYWxNXrpg
VywZUTQgIGDjeaRe7SSrJo97gW/Jxkl8VJCLR/oof96O2hN70GsEfnOECvpcC04O
TnfGiDbZWNS1LQfYwH7IBvrCD4mexA==
=l4tr
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Mar  1 18:09:05 2017
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 542FD12945B for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 18:09:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xvnQMWZAh9V for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 18:09:00 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DAB7129461 for <ietf@ietf.org>; Wed,  1 Mar 2017 18:09:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2228vtJ021744; Thu, 2 Mar 2017 03:08:57 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vYbMs307gzDHKC; Thu,  2 Mar 2017 03:08:57 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <17514.1488420343@obiwan.sandelman.ca>
Date: Thu, 2 Mar 2017 03:08:56 +0100
X-Mao-Original-Outgoing-Id: 510113336.812336-abec62a4fae6f8e04af6ec2c89d177ff
Content-Transfer-Encoding: quoted-printable
Message-Id: <B098D021-3503-4CBF-A422-7B3A58997B81@tzi.org>
References: <14476.1488384266@obiwan.sandelman.ca> <13e5803d-c2f3-7bc8-63c8-2a8311c22fae@isi.edu> <17514.1488420343@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4D17j75xfx8MFnPj1_KBkSejzss>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 02:09:02 -0000

On 2 Mar 2017, at 03:05, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
> Good point, but tell me why -01 and -09 and -17 don't come out faster?

One contributing factor might be that the submission interface is a =
pain.

(I still don=E2=80=99t have a Makefile entry for that.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  1 21:31:41 2017
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 B3F9E1296C8 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 21:31:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=mvyC9h/9; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=2q0C+Fcs
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2MKEcEMbn0k9 for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 21:31:37 -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 C26101293FE for <ietf@ietf.org>; Wed,  1 Mar 2017 21:31:37 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.210.98]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v225VMZr029742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Mar 2017 21:31:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1488432695; x=1488519095; bh=5E6MB+tBCwR051Nplge6f4lxB6tgq1R/H+qMW+wL+Sk=; h=Date:To:From:Subject:In-Reply-To:References; b=mvyC9h/9fnuAcpk6/3FNjSnwNwpZfUGADcrNZ2ukIL9QxJIVmC9kuyKij3mCD/4+F ar68jhqo83Wr/x5eMDDgR7BLMHASEpNr/2VJTwaM93kKNF9+x7CDVNeIe9dJc1x0ro Vsb86nXArAwJLrJFH3LiEOC1d5CxqUH3lwTuP5Nc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1488432695; x=1488519095; i=@elandsys.com; bh=5E6MB+tBCwR051Nplge6f4lxB6tgq1R/H+qMW+wL+Sk=; h=Date:To:From:Subject:In-Reply-To:References; b=2q0C+FcsFUl/o4qfzeaiGtGysqB6sdVtV2AsMXk79yoRteS9wxZrtqxUrMbLqM7oj 4tURQ1W/WnyFafqYAtYYRqD36bdVaSc1uQcX4Bk0kVqZjHvnXBokmEYvFiTWGb6j9X j/ETcGPyshoOg6xrVAuNMhZ8RAXhnVVqUnKMQZ9o=
Message-Id: <6.2.5.6.2.20170301204500.0be7a730@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Mar 2017 21:26:58 -0800
To: willi uebelherr <willi.uebelherr@riseup.net>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [Mailman-Users] Fwd: Re: Mailing list membership.
In-Reply-To: <e43a2790-d4d6-91cf-f5cc-645581fba973@riseup.net>
References: <CAGfsgR0bCWOr7_fY6ZEVLkvcwV3nf+xTGYvjWd02ryBJtM0FGA@mail.gmail.com> <e43a2790-d4d6-91cf-f5cc-645581fba973@riseup.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FNmBMher2gTjPSCkmsLU4XVArxA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 05:31:40 -0000

Hi Willi,
At 17:38 01-03-2017, willi uebelherr wrote:
>Jim Popowitch from the mailman user list sent this answer. But i 
>wait also for an answer from Mark Sapiro. I don't know what the 
>mailman developers changed in the newer versions in relation to the 
>DMARC processing.

Mailman 2.18, which was released in May 2014, has a 
dmarc_moderation_action feature which can be used for messages from a 
domain which publishes a DMARC policy of "reject" or 
"quarantine".  As an example, the message at 
https://www.ietf.org/mail-archive/web/ietf/current/msg101343.html is 
from a domain which has a DMARC policy of "p=reject;"

The possible actions of the dmarc_moderation_action feature for a 
domain which publishes a DMARC policy of "reject" or "quarantine" are:

   1. Accept the message as usual

   2. Rewrite the email address in the RFC5322.From header and set the Reply-To
      address to ietf@itf.org

   3. Wrap the message as a message/rfc822 sub-part in a MIME format 
outer message

   4. Reject the message

   5. Discard the message

Regards,
S. Moonesamy  


From nobody Wed Mar  1 21:51:36 2017
Return-Path: <alex@strugee.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 5A12E12949D for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 21:51:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, TVD_PH_BODY_ACCOUNTS_PRE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfmZdk0Zc9Xa for <ietf@ietfa.amsl.com>; Wed,  1 Mar 2017 21:51:34 -0800 (PST)
Received: from steevie.strugee.net (strugee.net [216.160.72.225]) by ietfa.amsl.com (Postfix) with ESMTP id 678FC1296C8 for <ietf@ietf.org>; Wed,  1 Mar 2017 21:51:34 -0800 (PST)
Received: from localhost (unknown [207.251.103.46]) by steevie.strugee.net (Postfix) with ESMTPSA id 39A4170F24B for <ietf@ietf.org>; Wed,  1 Mar 2017 21:51:30 -0800 (PST)
Date: Thu, 2 Mar 2017 00:51:28 -0500
From: Alex Jordan <alex@strugee.net>
To: ietf@ietf.org
Subject: Interest in a push-based two-factor auth standard?
Message-ID: <20170302055128.GJ12470@Alexs-MacBook-Pro>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UlsYxwg8UDQn+EKZ"
Content-Disposition: inline
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WIU3eOzVPZfTV9QyWESODWr5fKw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 05:51:35 -0000

--UlsYxwg8UDQn+EKZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Heya!

A widely deployed way to do two-factor authentication is
TOTP. However, when used with an Android device Google Accounts have a
really nice flow where Google will send a push notification to the
Android device, which will then prompt the user with a "yes/no"
question as to whether they were trying to log in or not. From a UX
perspective this is much nicer than opening an app, manually typing in
a code, etc.

With WebPush core having been just ratified as RFC 8030, the time
seems ripe for standardizing an authentication scheme like described
above.

I have two questions:

1. Is there interest in creating such a standard at the IETF?

2. If there is, where would be the best place to do that work? I'm
relatively new to the IETF - I poked around Datatracker's list of
Working Groups and there didn't seem to be one that really fit that
well. Did I miss something? Or should this go through the IETF
individual submission track?

Please CC me on replies; I'm not subscribed.

Cheers!

AJ

--UlsYxwg8UDQn+EKZ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJ8BAEBCgBmBQJYt7LgXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRERDMyMDZGODZEQ0VFMjMzQ0MwOUQ3NDgy
Njc5NDAzNDYzM0RCQkMwAAoJECZ5QDRjPbvAbPsQANd1pzDpGStFCFXRGUcv8xpS
5vAlxH+R0rknj3EwtizI1WpAr/QYsRRlxT3rp/fCVgMbUNHGdGFT8Of8oL7QbQBV
T/Sa0HXz9tzq7DB05eKPujCUWAxKxDM41elpYRUnAeqsHpMdqG69+eWsFrh++tdE
yxLatNEN0tb8cliTdI1391+Jxqx+vS9fPh03iTyHLTOPnBOFKJJh88yy88CNzo3x
rcIub0RD09rVybZzTLWRk5xiJkw9dEjzXJRx90Mf3AyOfGaxinqhZch/RfjQ57jM
8Vxo791Oci5sDSNqF0+g2qXYILgVkgXuqx3y2KIHI5eCDQFwg38VI9j3w4k+OmTO
PzK9umOtQySHWgn+9wao1xqZqeujdxp+YdddlPd1sWavKZHYW6tYJz0cYKZsoqYj
Uehj2UVLNe5XO+cuDBp8N2sS0cTPKecJsQ2fuHo4BzABCrfI16wmRzmx/e5j3t3h
CRKEEa8izkcAjOw+RZKqv40GbbxHquBx8ckTW5U2tIR59WwjE1Z8jUdx/N/x+UQ9
TLS+IraW0ZjiVNuguBAZTRrVd91L0yLB02IKYKIZwx5Le+t0rgTarpLHe6fwG/Qg
TosKLomSiS3GOpn4/DsyXPK+rBbnrfRQhEgky8XvN33BjCAVk4IuCgiseb8XzJSa
v66e0Mu2mq0sjvXWTMOj
=lxRr
-----END PGP SIGNATURE-----

--UlsYxwg8UDQn+EKZ--


From nobody Wed Mar  1 22:54:01 2017
Return-Path: <liushucheng@huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 583511293E3; Wed,  1 Mar 2017 22:54:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Shucheng LIU <liushucheng@huawei.com>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-dime-load-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148843764035.7093.4978052381971422851.idtracker@ietfa.amsl.com>
Date: Wed, 01 Mar 2017 22:54:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M7QYXXXHJ50R9asfORU8WYjUWv8>
Cc: draft-ietf-dime-load.all@ietf.org, dime@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 06:54:00 -0000

Reviewer: Shucheng LIU
Review result: Has Nits

Hi all,

I have reviewed draft-ietf-dime-load-07 as part of the Operational
directorate's ongoing effort to review all IETF documents being
processed by the IESG.  These comments were written with the intent of
improving the operational aspects of the IETF drafts. Comments that
are not addressed in last call may be included in AD reviews during
the IESG review.  Document editors and WG chairs should treat these
comments just like any other last call comments.

“This document defines a mechanism for conveying of Diameter load
   information.  RFC7068 describes requirements for Overload Control
in
   Diameter.  This includes a requirement to allow Diameter nodes to
   send "load" information, even when the node is not overloaded.
   RFC7683 (Diameter Overload Information Conveyance (DOIC)) solution
   describes a mechanism meeting most of the requirements, but does
not
   currently include the ability to send load information.”

My overall view of the document is 'Ready with nits' for publication.


** Technical **
No.


** Editorial **

*Section 4, page 4
>That is, the OLR requests that the reacting node reduce the offered
load…….

s/reduce/reduces


* Section 4.1, page 5:

>The fundamental difference is that an overload report requires that
reduction.

What does the second “that” refer to? It may change to “The
fundamental difference is that an overload report requires the
reduction of offered load”or so.

* Section 5, page 10:

>For the PEER load report, C follows the same procedure as A1 for
determining if the Load report was received from the peer from which
the report was sent and, when finding it does, stores the load
information for use when making future routing decisions.

This sentence may need to split for more readable purpose. 


* Section 5:

Full name of *AVP* should be put into Abbreviations before using first
time.




From nobody Thu Mar  2 00:21:50 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B7AE41294AE; Thu,  2 Mar 2017 00:21:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?b?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-jsonbis-rfc7159bis-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148844290474.7037.17466866442603948938.idtracker@ietfa.amsl.com>
Date: Thu, 02 Mar 2017 00:21:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8_G_oC2o-hdxuybxXIbyObtMaRk>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, ietf@ietf.org, json@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 08:21:44 -0000

Reviewer: Jürgen Schönwälder
Review result: Ready

This update is just a collection of clarifications, I do not see any
technical change. I do not expect any impact on operational networks.



From nobody Thu Mar  2 00:30:47 2017
Return-Path: <jari.arkko@piuha.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 383081294AF; Thu,  2 Mar 2017 00:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DGOTvJUgd6FU; Thu,  2 Mar 2017 00:30:39 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id EC6621294A7; Thu,  2 Mar 2017 00:30:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 41DDC2D00A; Thu,  2 Mar 2017 10:30:08 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LckWmSoSkBB0; Thu,  2 Mar 2017 10:30:07 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B8BC72D009; Thu,  2 Mar 2017 10:30:07 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-14
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_0094C1B9-EEA1-47B1-9DE2-F51DBC3E92EC"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148822688424.13746.15775745274859586475.idtracker@ietfa.amsl.com>
Date: Thu, 2 Mar 2017 10:30:08 +0200
Message-Id: <1E8F1C8B-35E2-4A95-94D7-E6E3966DADC9@piuha.net>
References: <148822688424.13746.15775745274859586475.idtracker@ietfa.amsl.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DP3J7zCMdpebi-ABUY08dp1Hias>
Cc: mpls@ietf.org, gen-art@ietf.org, draft-ietf-mpls-residence-time.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 08:30:40 -0000

--Apple-Mail=_0094C1B9-EEA1-47B1-9DE2-F51DBC3E92EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Robert: Thanks for the reviews and re-reviews. I have balloted
no-objection for this document on tonight=92s IESG telechat.

Jari


--Apple-Mail=_0094C1B9-EEA1-47B1-9DE2-F51DBC3E92EC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYt9gQAAoJEM80gCTQU46q37QQAIsSAjaZS7Fab98ZJD0j/Nus
Dk7swIhn3OTE0cyIAHYKeoRh+kNz8wrxgbCkHoKlqOE0MM/jrBMRRGmUOnRMVPfl
B+MfY5+nHBFMca7krFT6OT1lWMgJHVL64BKaSYqZT63YNIXXRJDxej3Zylc8W9wy
uayF2lQW+5IsxUeip5gFstCVCOHMiMrvpZEsMjuJppErCf+6damFaPqPC307S2VP
OULTaOmmSCu2s0UnQbALIJyGNN8ge/SAYdd7ZSol27M2e291t6yKSIkwA9wnyU0t
2tTkrvu07zcs2oCBS/MEAvhYMn4x9WeSnRhRNCYUUGkz8LcOgDvTeqCVcvcoHwRZ
L1M/3AergjX7dyQi19G+bu4d6jK3m/C9uLRNzCHENs5xY4WVIqowCHAt8buem05S
RBezVSWoKwQu97pslZ4EdmowC+7MiZHn+O5Qwv0RUqRVIx2kVpqMtpZYf5Oi3ze2
6WISOFI2Jg1t/ZnKGkFAQGV+3G9tgDbkDdD/z/m6P1mT2Vq12tTx3yRbFpQzjZmP
jTvZ1hmcnPOwHLBSlu8Y2Q9MLmjMjrb5L1yljfgrQsOY1d5Pvoh372NputLirTC4
Pbw9rmPvh68+PFKZIvFOuCY2uff0vU2arxRdcK44VLFL2FhpITC5idxpLLKGxZLG
er7O7wNWm9c08xwjds+v
=/q3D
-----END PGP SIGNATURE-----

--Apple-Mail=_0094C1B9-EEA1-47B1-9DE2-F51DBC3E92EC--


From nobody Thu Mar  2 00:36:47 2017
Return-Path: <liushucheng@huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B485B1299F5; Thu,  2 Mar 2017 00:36:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Shucheng LIU <liushucheng@huawei.com>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-sidr-bgpsec-pki-profiles-21
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148844379373.7077.11693707774114284535.idtracker@ietfa.amsl.com>
Date: Thu, 02 Mar 2017 00:36:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9gwkDoTUYYjYhPE_hAkmYQHDZUc>
Cc: draft-ietf-sidr-bgpsec-pki-profiles.all@ietf.org, ietf@ietf.org, sidr@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 08:36:34 -0000

Reviewer: Shucheng LIU
Review result: Ready

Hi all,

Sorry that it seems I missed this review request. I guess it's the
first one assigned to me via the new review system.

I have reviewed draft-ietf-sidr-bgpsec-pki-profiles-21 as part of the
Operational directorate's ongoing effort to review all IETF documents
being processed by the IESG.  These comments were written with the
intent of improving the operational aspects of the IETF drafts.
Comments that are not addressed in last call may be included in AD
reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

“This document defines a standard profile for X.509 certificates used
   to enable validation of Autonomous System (AS) paths in the Border
   Gateway Protocol (BGP), as part of an extension to that protocol
   known as BGPsec.  BGP is the standard for inter-domain routing in
the
   Internet; it is the "glue" that holds the Internet together.
BGPsec
   is being developed as one component of a solution that addresses
the
   requirement to provide security for BGP.  The goal of BGPsec is to
   provide full AS path validation based on the use of strong
   cryptographic primitives.  The end-entity (EE) certificates
specified
   by this profile are issued to routers within an Autonomous System.

   Each of these certificates is issued under a Resource Public Key
   Infrastructure (RPKI) Certification Authority (CA) certificate. 
   These CA certificates and EE certificates both contain the AS
   Identifier Delegation extension.  An EE certificate of this type
   asserts that the router(s) holding the corresponding private key
are
   authorized to emit secure route advertisements on behalf of the
   AS(es) specified in the certificate.  This document also profiles
the
   format of certification requests, and specifies Relying Party (RP)
   certificate path validation procedures for these EE certificates.
   This document extends the RPKI; therefore, this documents updates
the
   RPKI Resource Certificates Profile (RFC 6487).”

My overall view of the document is 'Ready' for publication.

** Technical **
No.


** Editorial **

*Section 4

>BGPsec Router Certificates always include the BGPsec Rouer EKU
>     value; therefore, request without the value result in
certificates
>     with the value; and,

s/Rouer/Router


From nobody Thu Mar  2 01:17:38 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D95F5129459; Thu,  2 Mar 2017 01:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJvSDDaNW5ic; Thu,  2 Mar 2017 01:17:32 -0800 (PST)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 584561294BB; Thu,  2 Mar 2017 01:17:32 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 9A534C0726; Thu,  2 Mar 2017 10:17:30 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.66]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 60D3C1A0066; Thu,  2 Mar 2017 10:17:30 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA1.corporate.adroot.infra.ftgroup ([fe80::95e2:eb4b:3053:fabf%19]) with mapi id 14.03.0319.002; Thu, 2 Mar 2017 10:17:29 +0100
From: <mohamed.boucadair@orange.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: RE: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Topic: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Index: AQHSjv3ZxPsK2cEBmku3LH3I6PtyiqGBLAkQ
Date: Thu, 2 Mar 2017 09:17:29 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com>
In-Reply-To: <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933009E1B2E6OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aL3Xc5YYWvw1E-fBFGHb2Au6ajE>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 09:17:36 -0000

--_000_787AE7BB302AE849A7480A190F8B933009E1B2E6OPEXCLILMA3corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgVGVkLA0KDQpQbGVhc2Ugc2VlIGlubGluZS4NCg0KQ2hlZXJzLA0KTWVkDQoNCkRlIDogVGVk
IEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbV0NCkVudm95w6kgOiBzYW1lZGkgMjUg
ZsOpdnJpZXIgMjAxNyAwMToyNg0Kw4AgOiBCT1VDQURBSVIgTW9oYW1lZCBJTVQvT0xODQpDYyA6
IGlldGZAaWV0Zi5vcmc7IGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbkBp
ZXRmLm9yZw0KT2JqZXQgOiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0
YWRhdGEtaW5zZXJ0aW9uLTA1LnR4dD4gKERlc2lnbiBjb25zaWRlcmF0aW9ucyBmb3IgTWV0YWRh
dGEgSW5zZXJ0aW9uKSB0byBJbmZvcm1hdGlvbmFsIFJGQw0KDQpIaSBNb2hhbWVkLA0KU29tZSBy
ZXBsaWVzIGluLWxpbmUuDQoNCk9uIEZyaSwgRmViIDI0LCAyMDE3IGF0IDEyOjU1IEFNLCA8bW9o
YW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbTxtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJAb3Jhbmdl
LmNvbT4+IHdyb3RlOg0KSGkgVGVkLA0KDQpQbGVhc2Ugc2VlIGlubGluZS4NCg0KQ2hlZXJzLA0K
TWVkDQoNCkRlIDogVGVkIEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbTxtYWlsdG86
dGVkLmlldGZAZ21haWwuY29tPl0NCkVudm95w6kgOiB2ZW5kcmVkaSAyNCBmw6l2cmllciAyMDE3
IDAwOjQwDQrDgCA6IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE4NCkNjIDogaWV0ZkBpZXRmLm9y
ZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz47IGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWlu
c2VydGlvbkBpZXRmLm9yZzxtYWlsdG86ZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRhdGEtaW5z
ZXJ0aW9uQGlldGYub3JnPg0KT2JqZXQgOiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaGFyZGllLXBy
aXZzZWMtbWV0YWRhdGEtaW5zZXJ0aW9uLTA1LnR4dD4gKERlc2lnbiBjb25zaWRlcmF0aW9ucyBm
b3IgTWV0YWRhdGEgSW5zZXJ0aW9uKSB0byBJbmZvcm1hdGlvbmFsIFJGQw0KDQpISSBNb2hhbWFk
LA0KDQpUaGFua3MgZm9yIHJlY2hlY2tpbmc7IHNvbWUgZnVydGhlciBjb21tZW50cyBpbi1saW5l
Lg0KDQpPbiBXZWQsIEZlYiAyMiwgMjAxNyBhdCAxMToyMSBQTSwgPG1vaGFtZWQuYm91Y2FkYWly
QG9yYW5nZS5jb208bWFpbHRvOm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20+PiB3cm90ZToN
CkhpIFRlZCwNCg0KVGhhbmsgeW91IGZvciB0aGUgcmVwbHkgYW5kIGZvciBpbXBsZW1lbnRpbmcg
dGhlc2UgY2hhbmdlcy4NCg0KSSBjaGVja2VkIHRoZSBkaWZmLCBidXQgSeKAmW0gYWZyYWlkIHRo
ZSAtMDYgdmVyc2lvbiBoYXMgdGhlIHNhbWUgaXNzdWVzIGFzIHRoZSBvbmVzIEkgcmVwb3J0ZWQg
aW4gSmFudWFyeSAzMS4NCg0KDQpJIGRpZCByZXNwb25kIHRvIHRoZSBwYXJ0aWN1bGFyIGNvbW1l
bnRzIGFuZCB0ZXh0IHByb3Bvc2Fscywgc28gSSBhc3N1bWUgdGhpcyBpcyB0aGUgbW9yZSBnZW5l
cmFsIGlzc3VlLiAgSWYgSSB1bmRlcnN0YW5kIGNvcnJlY3RseSwgeW91IHdvdWxkIHByZWZlciB0
aGlzIGRvY3VtZW50IHRvIGJlIHN0cnVjdHVyZWQgYXMgYSByZXZpc2lvbiB0byB0aGUgdGhyZWF0
IG1vZGVsIGRvY3VtZW50IG9yIGNvbm5lY3RlZCB0byBhIGxhcmdlciBjb25zaWRlcmF0aW9uIG9m
IHRoZSBpc3N1ZXMuICBJIHVuZGVyc3RhbmQgdGhhdCwgYW5kIGl0IHdhcyBjb25zaWRlcmVkLCBi
dXQgSSBiZWxpZXZlIHRoYXQgdGhpcyBmb3JtYXQgaXMgc3RpbGwgdGhlIG1vc3QgZWZmZWN0aXZl
IGZvciB0aGUgbmFycm93IGlzc3VlIGl0IGFkZHJlc3Nlcy4NCltNZWRdIFRoYXQgd2FzIG9uZSBv
ZiBteSBjb25jZXJuczsgbm90IHRoZSBvbmx5IG9uZS4gSW4gUGFydGljdWxhciwgSeKAmW0gdHJ5
aW5nIHRvIHVuZGVyc3RhbmQgaG93IHRoaXMgZG9jdW1lbnQgd2lsbCBiZSB1c2VkIGluIHRoZSBm
dXR1cmUgdG8gYmV0dGVyIHN0cmVuZ3RoZW4gZm9ydGhjb21pbmcgc3BlY2lmaWNhdGlvbnMuIEZ1
cnRoZXIsIHRoZSBleHBlcmllbmNlIEkgaGFkIHdoZW4gYWR2YW5jaW5nIHNvbWUgUkZDcyBpcyB0
aGF0IFJGQzcyNTggd29yZGluZyBjYW4gYmUgZnVydGhlciBlbmhhbmNlZCB0byBwcm92aWRlIGNs
ZWFyIGd1aWRhbmNlLiBBbHNvLCBjb25zaWRlcmF0aW9ucyBzdWNoIGFzIHRoZSBmb2xsb3dpbmcg
YXJlIG1pc3NpbmcgZnJvbSB0aGUgZG9jdW1lbnQ6DQpJdCdzIGRpZmZpY3VsdCB0byBzYXkgaG93
IHNvbWV0aGluZyB3aWxsIGJlIHVzZWQgaW4gdGhlIGZ1dHVyZS4NCltNZWRdIEFuIGFkdmljZSB0
aGF0IGlzIG5vdCBpbXBsZW1lbnRhYmxlIG1ha2VzIG1vcmUgdHJvdWJsZXMsIElNSE8uDQpNeSBp
bnRlbnQgKGFuZCB0aGUgdW5kZXJzdGFuZGluZyBvZiBvdGhlciByZXZpZXdlcnMpIGlzIHRvIGhp
Z2hsaWdodCB0aGF0IHRoZXNlIG1lY2hhbmlzbXMgaGF2ZSBhIHByaXZhY3ktZGFtYWdpbmcgcmVz
dWx0IGFuZCB0aGF0IHRoaXMgc2hvdWxkIGJlIGNvbnNpZGVyZWQuDQpbTWVkXSBJIGRvIHRoaW5r
IGV4aXN0aW5nIGRvY3VtZW50cyBhbHJlYWR5IG1ha2UgdGhhdCBqb2IuIEkgZG8gdGhpbmsgd2Ug
bmVlZCBtb3JlLg0KIEluIHBhcnRpY3VsYXJseSwgSSdtIGNvbmNlcm5lZCB0aGF0IHNvbWUgYXBw
bGljYXRpb24gZnVuY3Rpb25zIGluIHRoZSBuZXR3b3JrIChlLmcuIHJlY3Vyc2l2ZSByZXNvbHZl
cnMgb3IgcHJveGllcykgZG8gbm90IGNvbnNpZGVyIHRoZSBwb3N0aXZlIHByaXZhY3kgaW1wbGlj
YXRpb25zIG9mIHRoZWlyIGFnZ3JlZ2F0aW9uIGFuZCBzbyBkbyBub3QgY29uc2lkZXIgYWRkaW5n
IHRoaXMgZGF0YSBiYWNrIGFzIHByb2JsZW1hdGljLg0KW01lZF0gSeKAmW0gYWxzbyBjb25jZXJu
ZWQgd2l0aCB0aGF0LCB0b28gKHNlZSBlLmcuLCBodHRwOi8vd3d3MS5pY3NpLmJlcmtlbGV5LmVk
dS9+bmFyc2VvL3BhcGVycy9ob3RtNDItdmFsbGluYXJvZHJpZ3Vlei5wZGYpLiBJbiB0aGUgbWVh
bnRpbWUsIEnigJltIGFsc28gY29uY2VybmVkIHdpdGggKDEpIHNvbWUgYXBwbGljYXRpb25zIHRo
YXQgbGVhayBwcml2YWN5IGluZm9ybWF0aW9uIHdpdGhvdXQgdGhlIGNvbnNlbnQgb2YgdGhlIHVz
ZXIgYW5kICgyKSBzb21lIGFwcGxpY2F0aW9uIHNlcnZlcnMgdGhhdCBtYXkgY29ycmVsYXRlIHZh
cmlvdXMgaW5mb3JtYXRpb24gc2hhcmVkIGJ5IGFuIGFwcGxpY2F0aW9uIGNsaWVudCB0byB0cmFj
ayB1c2VycyAoZS5nLiwgaHR0cHM6Ly9wYW5vcHRpY2xpY2suZWZmLm9yZy8pLiBCVFcsIEkgc2Vl
IHRoYXQgeW91IGFyZSB1c2luZyDigJxhcHBsaWNhdGlvbiBmdW5jdGlvbuKAnSB3aGljaCBtYXkg
bm90IGhhdmUgdGhlIHNhbWUgbWVhbmluZyBhcyB0aGUgZ2VuZXJhbCDigJxwcm90b2NvbOKAnSB3
b3JkaW5nIHVzZWQgaW4gZHJhZnQtaGFyZGllLSouIERvIHlvdSBjb25zaWRlciBhIERIQ1AgcmVs
YXkgYXMgYW4g4oCcYXBwbGljYXRpb24gZnVuY3Rpb27igJ0/DQogICBIaWdobGlnaHRpbmcgdGhp
cyBlbmFibGVzIHRoZW0gdG8gc2VlIHRoaXMgdHJhZmZpYyBpbiBhIGRpZmZlcmVudCBjb250ZXh0
Lg0KW01lZF0gSXNu4oCZdCB0aGlzIGFscmVhZHkgYXNzdW1lZCBieSBzb21lIHByb3RvY29sIGRl
c2lnbmVycyAoZS5nLiwgUkZDNjk3MywgU0lQKT8gQlRXLCB0aGVyZSBhcmUgc3VidGxldGllcyB3
aGVuIHByb3hpZXMgYXJlIGluIHRoZSBzYW1lIHRydXN0IGRvbWFpbiBvZiB0aGUgY2xpZW50IG9y
IHNlcnZlci4NCg0KKiB0aGF0IGRhdGEgbWF5IG5vdCBiZSBhbHdheXMgYXZhaWxhYmxlIHRvIHRo
ZSBlbmRob3N0DQpVbmRlcnN0b29kLCBidXQgZXZlbiBpbiB0aGlzIGNhc2UsIGl0IGlzIGJldHRl
ciB0byBtYWtlIHRoZSBwZXJtaXNzaW9uIHRvIGFkZCB0aGUgZGF0YSBleHBsaWNpdC4NCltNZWRd
IFRoaXMgbWF5IGJlIGVhc3kgdG8gaW1wbGVtZW50IGZvciBzb21lIGFwcGxpY2F0aW9ucywgYnV0
IHRoaXMgbWF5IG5vdCBiZSBnZW5lcmFsaXplZCB0byAqKiBhbGwgKiogcHJvdG9jb2xzLiBQdXR0
aW5nIGFzaWRlIHRoZSBpbnRlcmFjdGlvbiB3aXRoIGEgdXNlciB0byBnZXQgYSBjb25zZW50IGFu
ZCBob3cgdGhhdCBjb25zZW50IHdpbGwgbmVlZCB0byBiZSBjaGFuZ2VkIHdoZW4gYW5vdGhlciB1
c2VyIHVzZXMgdGhlIHNhbWUgZGV2aWNlIHRvIGNvbm5lY3QgdG8gdGhlIEludGVybmV0LiBDb25z
aWRlciBhIHVzZXIgd2hvIGRvZXMgbm90IHdhbnQgYW4gdXBzdHJlYW0gREhQQyByZWxheSB0byBp
bnNlcnQgdGhlIGxpbmUtaWQgKGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2Nzg4KSB0
byB0aGUgc2VydmVyLCBhbmQgbGV04oCZcyBzdXBwb3NlIHRoZSByZWxheSByZWNlaXZlZCBhIHNp
Z25hbCAoYnkgc29tZSBtZWFucywgdG8gYmUgeWV0IHNwZWNpZmllZCkgdGhhdCBmb3IgdGhpcyBw
YXJ0aWN1bGFyIERIQ1AgY2xpZW50LCB0aGUgbGluZS1pZCBtdXN0IG5vdCBiZSBpbnNlcnRlZC4g
Rm9yIHRoaXMgY2FzZSwgY29ubmVjdGl2aXR5IHdvbuKAmXQgYmUgcHJvdmlkZWQgdG8gdGhhdCB1
c2VyLiBUaGlzIHdvdWxkIG1lYW4gZXh0cmEgY2FsbHMgdG8gdGhlIGhvdGxpbmUgZm9yIHRoYXQg
bmV0d29yayBwcm92aWRlci4gVGhpcyBpcyBub3QgZGVzaXJhYmxlIGZvciBib3RoIGN1c3RvbWVy
cyBhbmQgbmV0d29yayBwcm92aWRlcnMuDQoNCkFub3RoZXIgZXhhbXBsZSBpcyBhZGRyZXNzLXNo
YXJpbmcgKGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2MjY5I3NlY3Rpb24tMTMuMSks
IGEgbWlzYmVoYXZpbmcgdXNlciBtYXkgaW1wYWN0IGFsbCB0aGUgdXNlcnMgdW5kZXIgdGhlIHNh
bWUgYWRkcmVzcy4gSSBiZXQgc3VjaCB1c2VyIHdvbuKAmXQgZ2l2ZSBoaXMvaGVyIHBlcm1pc3Np
b24gc28gdGhhdCBtZWFucyB0byBkZW11eCBpdHMgcGFja2V0cy4NCg0KSXQgaXMgYWxzbyBvZnRl
biBwb3NzaWJsZSBmb3IgdGhlIGVuZCBzeXN0ZW0gdG8gZ2FpbiB0aGlzIGRhdGEgYXQgdGhlIGNv
c3Qgb2Ygb3RoZXIgdHJhZmZpYyhlLmcuIHRoZSBTVFVOIHNlcnZlciByZXF1ZXN0cyBub3RlZCBp
biB0aGUgZG9jdW1lbnQpLg0KW01lZF0gSeKAmW0gbm90IHN1cmUgd2hldGhlciB0aGlzIGlzIOKA
mG9mdGVu4oCZLCBidXQgZm9yIHN1cmUgdGhpcyBpcyBwb3NzaWJsZSBmb3Igc29tZSBjYXNlcy4g
RXh0cmEgcmVxdWVzdHMgbWF5IGJlIG5lZWRlZCwgSW5kZWVkLiBCZXR0ZXIsIHRoZSBpbmZvcm1h
dGlvbiBtYXkgZXZlbiBiZSBldmVuIGF2YWlsYWJsZSBsb2NhbGx5LCBmb3IgZXhhbXBsZSB0aGVy
ZSBpcyBldmVuIG5vIG5lZWQgdG8gcnVuIFNUVU4vUENQIHRvIHByb3ZpZGUgYW4gWEZGIG9yIEZv
cndhcmQtRm9yIGhlYWRlcnMuDQoNCklmIHRoaXMgY2FuIGJlIGRvbmUgaW4gcGFyYWxsZWwgd2l0
aCBvdGhlciBhY3Rpb25zLCB0aGVuIHRoZSBsYXRlbmN5IGltcGFjdCBjYW4gYmUgbWluaW1pemVk
Lg0KW01lZF0gVGhlc2UgYXJlIGFzc3VtcHRpb25zIGFuZCBpbXBsaWNhdGlvbnMgdGhhdCBhcmUg
d29ydGggdG8gYmUgYWRkZWQgdG8gdGhlIGRyYWZ0LiBCVFcsIHRoaXMgZmFsbHMgaW50byB0aGlz
IGdlbmVyYWwgZGlzY3Vzc2lvbiBpbiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjk3
MzoNCg0KICAgYS4gIFRyYWRlLW9mZnMuICBEb2VzIHRoZSBwcm90b2NvbCBtYWtlIHRyYWRlLW9m
ZnMgYmV0d2VlbiBwcml2YWN5DQogICAgICAgYW5kIHVzYWJpbGl0eSwgcHJpdmFjeSBhbmQgZWZm
aWNpZW5jeSwgcHJpdmFjeSBhbmQNCiAgICAgICBpbXBsZW1lbnRhYmlsaXR5LCBvciBwcml2YWN5
IGFuZCBvdGhlciBkZXNpZ24gZ29hbHM/ICBEZXNjcmliZQ0KICAgICAgIHRoZSB0cmFkZS1vZmZz
IGFuZCB0aGUgcmF0aW9uYWxlIGZvciB0aGUgZGVzaWduIGNob3Nlbi4NCiogYSBtaXNiZWhhdmlu
ZyBub2RlIG1heSBiZSB0ZW1wdGVkIHRvIHNwb29mIHRoZSBkYXRhIHRvIGJlIGluamVjdGVkLiBB
IHJlbW90ZSBkZXZpY2UgdGhhdCB3aWxsIHVzZSB0aGF0IGRhdGEgdG8gZW5mb3JjZSBwb2xpY2ll
cyB3aWxsIGJlIGJyb2tlbi4NClRoaXMgcG9pbnQgd2FzIGRpc2N1c3NlZCBleHRlbnNpdmVseSBp
biB0aGUgR0VPUFJJViB3b3JrIGFuZCBlc3NlbnRpYWxseSBhIHNpbmdsZSBjYXJ2ZS1vdXQgd2Fz
IG1hZGU6ICBmb3IgZW1lcmdlbmN5IHNlcnZpY2VzLCB3aGVyZSBmYWxzZWx5IGFzc2VydGVkIGxv
Y2F0aW9uIGRhdGEgY291bGQgYmUgdXNlZCB0byBTV0FUIGluZGl2aWR1YWxzIG9yIGNvbnN1bWUg
c2FmZXR5IHJlc291cmNlcy4gICAgSSBkb24ndCB0aGluayB0aGF0IGZhbGxzIGludG8gdGhpcyBu
YXJyb3cgYWR2aWNlLCBidXQgSSB3b3VsZCBiZSB3aWxsaW5nIHRvIGFkZCBzb21ldGhpbmcgbGlr
ZSB0aGlzIHRvIHRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9uczoNCiJOb3RlIHRoYXQgc29tZSBl
bWVyZ2VuY3kgc2VydmljZSByZWNpcGllbnRzLCBub3RhYmx5IFBTQVBzIChQdWJsaWMgU2FmZXR5
IEFuc3dlcmluZyBQb2ludHMpIG1heSBwcmVmZXIgZGF0YSBwcm92aWRlZCBieSBhIG5ldHdvcmsg
dG8gZGF0YSBwcm92aWRlZCBieSBlbmQgc3lzdGVtLCBiZWNhdXNlIGFuIGVuZCBzeXN0ZW0gY291
bGQgdXNlIGZhbHNlIGRhdGEgdG8gYXR0YWNrIG90aGVycyBvciBjb25zdW1lIHJlc291cmNlcy4g
ICBXaGlsZSB0aGlzIGhhcyB0aGUgY29uc2VxdWVuY2UgdGhhdCB0aGUgZGF0YSBhdmFpbGFibGUg
dG8gdGhlIFBTQVAgaXMgb2Z0ZW4gbW9yZSBjb2Fyc2UgdGhhbiB0aGF0IGF2YWlsYWJsZSB0byB0
aGUgZW5kIHN5c3RlbSwgdGhlIHJpc2sgb2YgZmFsc2UgZGF0YSBiZWluZyBwcm92aWRlZCBpbnZv
bHZlZCBhIHJpc2sgdG8gdGhlIGxpdmVzIG9mIHRob3NlIHRhcmdldGVkLiINCltNZWRdIFRoYW5r
IHlvdS4gUHJvdmlkaW5nIFBTQVAgYXMgYW4gZXhhbXBsZSBpcyBPSywgYnV0IEnigJlkIGxpa2Ug
dGhlIGlzc3VlIHRvIGJlIGNhbGxlZCBvdXQgYXMgYSBnZW5lcmljIG9uZSB3aGlsZSBQU0FQIGlz
IHByb3ZpZGVkIGFzIGFuIGV4YW1wbGUuIFdoYXQgYWJvdXQgdGhlIGZvbGxvd2luZzoNCg0KIk5v
dGUgdGhhdCBzb21lIHNlcnZlcnMgKGUuZy4sIGVtZXJnZW5jeSBzZXJ2aWNlIHJlY2lwaWVudHMs
IG5vdGFibHkgUFNBUHMgKFB1YmxpYyBTYWZldHkgQW5zd2VyaW5nIFBvaW50cykgW1JGQzY0NDNd
KSBtYXkgcHJlZmVyIGRhdGEgcHJvdmlkZWQgYnkgYSBuZXR3b3JrIHRvIGRhdGEgcHJvdmlkZWQg
YnkgdGhlIGVuZCBzeXN0ZW0sIGJlY2F1c2UgYW4gZW5kIHN5c3RlbSBjb3VsZCB1c2UgZmFsc2Ug
ZGF0YSB0byBhdHRhY2sgb3RoZXJzIG9yIGNvbnN1bWUgcmVzb3VyY2VzLiAgV2hpbGUgdGhpcyBo
YXMgdGhlIGNvbnNlcXVlbmNlIHRoYXQgdGhlIGRhdGEgYXZhaWxhYmxlIHRvIHRoZSBzZXJ2ZXIg
aXMgb2Z0ZW4gbW9yZSBjb2Fyc2UgdGhhbiB0aGF0IGF2YWlsYWJsZSB0byB0aGUgZW5kIHN5c3Rl
bSwgdGhlIHJpc2sgb2YgZmFsc2UgZGF0YSBiZWluZyBwcm92aWRlZCBpbnZvbHZlZCBhIHJpc2sg
dG8gdGhlIGxpdmVzIG9mIHRob3NlIHRhcmdldGVkLiINCg0KKiBpdCB3YXMgcmVwb3J0ZWQgaW4g
dGhlIHBhc3QgdGhhdCBzb21lIGJyb3dzZXJzIGxlYWsgdGhlIE1TSVNETiBhbmQgb3RoZXIgc2Vu
c2l0aXZlIGRhdGEuDQpUaGlzIGlzIHRydWUsIGJ1dCBpdCBzZWVtcyB0byBtZSB1bnJlbGF0ZWQg
dG8gdGhlIHBvaW50IG9mIHRoZSBkb2N1bWVudC4NCltNZWRdIEl0IGlzIHJlbGF0ZWQgYmVjYXVz
ZSBibGluZGx5IHRydXN0aW5nIGFuIGFwcGxpY2F0aW9uIGNsaWVudCAoYW5kIHNlcnZlcikgaGFz
IGl0cyBvd24gcHJpdmFjeSByaXNrcy4gVGhpcyBpcyBldmVuIGV4YWNlcmJhdGVkIGdpdmVuIHRo
ZSByaWNoIGRhdGEgdGhhdCBpcyBhdmFpbGFibGUgdG8gYW4gYXBwbGljYXRpb24gY2xpZW50IGFu
ZCBhbHNvIGJlY2F1c2Ugb2YgdGhlIHZpc2liaWxpdHkgb24gdmFyaW91cyBsYXllcnMgYXZhaWxh
YmxlIHRvIGFuIGFwcGxpY2F0aW9uIHNlcnZlci4NCkZyb20gdGhhdCBmbG93IHNvbWUgb2YgeW91
ciBvdGhlciBjb25jZXJucyBhYm91dCBhdWRpZW5jZSwgYXQgbGVhc3QgYXMgSSB1bmRlcnN0YW5k
LiAgQXMgd3JpdHRlbiwgdGhpcyBpcyBuYXJyb3cgYWR2aWNlIGZvciBhIGJyb2FkIGF1ZGllbmNl
OiBiYXNpY2FsbHksIGFueW9uZSB3aG8gd291bGQgY29uc2lkZXIgdGhlIGZvcm0gb2YgbWV0YWRh
dGEgaW5zZXJ0aW9uIGl0IGRlc2NyaWJlcy4gIFlvdSB3b3VsZCwgaWYgSSB1bmRlcnN0YW5kIHlv
dSwgcHJlZmVyIGEgbmFycm93ZXIgZGVzY3JpcHRpb24gb2YgdGhlIGF1ZGllbmNlIGluIGEgbGFy
Z2VyIGNvbnRleHQuDQoNCltNZWRdIFRoZSBrZXkgcG9pbnQgaGVyZSBpcyBhYm91dCB0aGUgcHJh
Y3RpY2FsaXR5IG9mIGltcGxlbWVudGluZyB0aGUgYWR2aWNlIE5PVCBjaGFuZ2luZyB0aGUgc2Nv
cGUuIEZvciBleGFtcGxlLCB0aGUgZG9jdW1lbnQgc2F5cyB0aGF0IGl0IGlzIGJldHRlciB0aGF0
IGEgaG9zdCBpcyBpbmplY3RpbmcgdGhlIGRhdGEgYnV0IHRoZSBkb2N1bWVudCBkb2VzIG5vdCBx
dWVzdGlvbiB3aGV0aGVyIHRoYXQgc3VwcGxpZWQgZGF0YSBjYW4gYmUgdHJ1c3RlZCBvciBub3Qs
IG9yIGhvdyB0aGUgY29uc2VudCB3aWxsIGJlIG9idGFpbmVkIGZyb20gYSB1c2VyLg0KDQpJbiBn
ZW5lcmFsLCB0aGUgcG9pbnQgb2YgdGhlIGRvY3VtZW50IGlzIHRoYXQgdGhlIGhvc3Qgc2hvdWxk
IGJlIGFibGUgdG8gb21pdCB0aGUgZGF0YSB3aXRob3V0IG1pZC1uZXR3b3JrIGRldmljZXMgYWRk
aW5nIGl0IGJhY2suICBUaGF0J3MgdGhlIHBvaW50IG9mIHByb3RlY3RpbmcgdGhlIHRyYWZmaWMg
aW4gdGhlIGZpcnN0IHBsYWNlLCBhZnRlciBhbGwuICBJIGFtIHNheWluZyB0aGF0IGlmIHRoZSBw
cm90b2NvbHMgcmVxdWlyZSB0aGUgZGF0YSwgdGhlbiBnZXR0aW5nIGl0IGZyb20gdGhlIGVuZCBo
b3N0IGhhcyBiZXR0ZXIgcHJpdmFjeSBwcm9wZXJ0aWVzIHRoYW4gZ2V0dGluZyBmcm9tIGl0IGZy
b20gbWlkLW5ldHdvcmsgZW50aXRpZXMuDQpbTWVkXSBJ4oCZbSBub3Qgc3VyZSB3ZSBjYW4gaGF2
ZSBzdWNoIGdlbmVyYWwgc3RhdGVtZW50IGJlY2F1c2UgdGhlIGRhdGEgbWF5IG5vdCBiZSBhdmFp
bGFibGUgKGUuZy4sIERIQ1AgZm9yIGV4YW1wbGUpIHRvIGNsaWVudHMgKyB0aGUgZGF0YSBzdXBw
bGllZCBieSBjbGllbnRzICh3aGVuIHBvc3NpYmxlKSBtYXkgbm90IGJlIHJlbGlhYmxlICsgZW5m
b3JjaW5nIHBvbGljaWVzIGJhc2VkIG9uIGNsaWVudC1zdXBwbGllZCBkYXRhIG1heSBoYXZlIGlt
cGxpY2F0aW9uIG9uIG90aGVyIHVzZXJzIChlLmcuLCBzcG9vZmluZyBYRkYgZm9yIGV4YW1wbGUp
LiBPYnZpb3VzbHksIGdldHRpbmcgc29tZSBvZiB0aGUgaW5mb3JtYXRpb24gZnJvbSBhIGNsaWVu
dCBtYXkgaGF2ZSBpbXBsaWNhdGlvbnMgb24gUW9F4oCmdGhlIHVzZXIgbmVlZHMgdG8gdW5kZXJz
dGFuZCB0aGUgcm9vdCBjYXVzZXMgb2YgYSBkZWdyYWRhdGlvbiBvZiBRb0UuIE9mIGNvdXJzZSwg
dGhlc2UgaW1wbGljYXRpb25zIG1heSBub3QgYmUgbmV3IGZvciB1c2VycyB3aG8gYXJlIGZhbWls
aWFyIHdpdGggZGlzYWJsaW5nIEphdmEgc2NyaXB0cyBhbmQgY2llLg0KDQpGb3IgZXhhbXBsZSwg
dGhlIGRvY3VtZW50IHN0YXRlcyB0aGF0IHRoZSBpbmZvcm1hdGlvbiBpbiBhIEZvcndhcmQtRm9y
IGhlYWRlciBjYW4gYmUgc3VwcGxpZWQgYnkgdGhlIGhvc3QgaXRzZWxmIGFuZCB0aGVuIGNvbW11
bmljYXRlZCB0byBhIHJlbW90ZSBjb25zdW1lci4gVGhpcyBpcyBpbmRlZWQgcG9zc2libGUsIGJ1
dCBiZWNhdXNlIG9mIGFidXNpbmcgaG9zdHMgc29tZSBzZXJ2ZXJzIGltcGxlbWVudCB3aGl0ZWxp
c3RzIHRvIHRydXN0IHByb3hpZXM7IHNlZSBodHRwczovL21ldGEud2lraW1lZGlhLm9yZy93L2V4
dGVuc2lvbnMvVHJ1c3RlZFhGRi90cnVzdGVkLWhvc3RzLnR4dC4NCg0KDQpUaGUgV2lraW1lZGlh
IGNhc2UgaXMgYSB2ZXJ5IGludGVyZXN0aW5nIG9uZSB0byByYWlzZSwgYmVjYXVzZSBpdCBkZXJp
dmVzIGZyb20gYSBzZXQgb2YgYXNzdW1wdGlvbnMgYWJvdXQgdGhlIG5ldHdvcmsgdGhhdCBhcmUg
c29tZXdoYXQgZmxhd2VkIGFuZCB0aGVuIGF0dGVtcHRzIHRvIHBhdGNoIHRob3NlIGZsYXdzIGlu
IHdheXMgdGhhdCBhY3R1YWxseSBkYW1hZ2UgdGhlIG1lY2hhbmlzbXMgb2YgdGhlIHN5c3RlbSB0
aGV5IG9yaWdpbmFsbHkgYnVpbHQuDQpXaWtpbWVkaWEgd2FudHMgdG8gYWxsb3cgZm9sa3MgdG8g
ZWRpdCB3aXRob3V0IGxvZ2luIGNyZWRlbnRpYWxzLiAgVGhpcyBhbGxvd3MgZm9yIGFub255bW91
cyB1c2VycyB0byBtYWtlIGNvcnJlY3Rpb25zIG9yIGFkZGl0aW9uczsgdGhpcyBpcyBhIGdvYWwu
ICBUaGUgY29uc2VxdWVuY2Ugb2YgdGhhdCBnb2FsIGJlaW5nIGFjaGlldmVkIGlzIHRoYXQgdHJv
bGxzIG9yIG1hbGljaW91cyBlZGl0b3JzIGNhbiBoYXZlIGF0IGFueXRoaW5nIHRoZXkgd2FudC4N
ClJhdGhlciB0aGFuIGluc3RpdHV0ZSBjcmVkZW50aWFscyBhbmQgQUNMcywgV2lraW1lZGlhIGF0
dGVtcHRzIHRvIHN1YnN0aXR1dGUgYmxvY2tpbmcgYnkgSVAgZm9yIGJsb2NraW5nIGJ5IGNyZWRl
bnRpYWwuICBUaGUgcHJvcGVydHkgdGhleSBhcmUgbG9va2luZyBmb3IgaW4gSVBzIGlzIG5vdCBy
ZWFsbHkgdGhlcmUsIHRob3VnaDogIHRoZXkgYXJlIG5vdCB1bmlxdWUgdG8gaW5kaXZpZHVhbHMs
IGVzcGVjaWFsbHkgb3ZlciB0aW1lLg0KDQpUaGlzIGRhbWFnZXMgdGhvc2Ugd2hvIHNoYXJlIElQ
IGFkZHJlc3NlcyAoZHVlIHRvIE5BVHMgb3IgcHJveGllcykuICBBcyBmYXIgYXMgSSBjYW4gdGVs
bCwgdGhlIE5BVCBwcm9ibGVtIGlzIHNpbXBseSB0cmVhdGVkIGFzIGNvbGxhdGVyYWwgZGFtYWdl
LiAgRm9yIHRoZSBwcm94aWVzLCB0aGV5IGF0dGVtcHQgdG8gd29yayBhcm91bmQgdGhlIGRhbWFn
ZSB1c2luZyBYRkYuICBUaGF0J3Mgc3Bvb2ZhYmxlLCB0aG91Z2gsIHNvIHRoZXkgYXR0ZW1wdCB0
byBsaW1pdCBpdCB0byBzcGVjaWZpYyBwcm94aWVzIHdob3NlIFhGRiB0aGV5IHRydXN0LS1tYW55
IG9mIHdoaWNoIHJlcXVpcmUgbG9naW5zLiAgVGhhdCBzaGlmdHMgdGhlIGluZm9ybWF0aW9uIGFi
b3V0IHdobyBpcyBlZGl0aW5nIFdpa2lwZWRpYSBvdXQgb2YgdGhlaXIgaGFuZHMsIGJ1dCBsZWF2
ZXMgaXQgaW4gdGhlIG5ldHdvcmsgYW5kIHRodXMgbm90IHRydWx5IGFub255bW91cy4gIEkgdW5k
ZXJzdGFuZCB0aGUgZW5naW5lZXJpbmcgYmFsYW5jZSB0aGV5IGFyZSB0cnlpbmcgdG8gc3RyaWtl
LCBidXQgSSdtIG5vdCBzdXJlIEkgY2FuIHJlY29tbWVuZCB0aGVpciBzb2x1dGlvbi4NCg0KW01l
ZF0gSeKAmW0gbm90IHJlY29tbWVuZGluZyB0aGVpciBzb2x1dGlvbiBlaXRoZXIsIGJ1dCBJ4oCZ
bSB0cnlpbmcgdG8gcmFpc2UgdGhlIHBvaW50IHRoYXQgYW4gZW5naW5lZXJpbmcgYmFsYW5jZSBp
cyBvdXQgdGhlcmUuIEFDS2luZyB0aGF0IGRlcGxveW1lbnQgcmVhbGl0eSBpcyBiZXR0ZXIgdGhh
biBpZ25vcmluZyBpdC4NCg0KSeKAmW0gcmVpdGVyYXRpbmcgdGhhdCBtb3N0IG9mIG15IGNvbW1l
bnRzIGFyZSBzdGlsbCB1bmFkZHJlc3NlZCBpbiAtMDYuDQoNCg0KSSByZWFsaXplIHRoYXQgdGhl
IGRvY3VtZW50IGRpZCBub3QgY2hhbmdlIHRvIGFkZHJlc3MgdGhlIGF1ZGllbmNlIG9yIGRvY3Vt
ZW50IGludGVncmF0aW9uIHlvdSBwcmVmZXJyZWQ7IEkgdGhpbmsgdGhlcmUgd2Ugc2ltcGx5IGRp
c2FncmVlIG9uIGhvdyB0byBtYWtlIHRoaXMgYWR2aWNlIGVmZmVjdGl2ZS4gIEknbSBzb3JyeSB0
aGF0IGZpcnN0IG1lc3NhZ2UgYXBwYXJlbnRseSBkaWQgbm90IGRlc2NyaWJlIHRoZSBkaXNhZ3Jl
ZW1lbnQgZWZmZWN0aXZlbHkuDQpJZiBJIGhhdmUgbWlzdW5kZXJzdG9vZCB5b3VyIGNvbW1lbnRz
LCBwbGVhc2UgYWNjZXB0IG15IGFwb2xvZ2llcy4gSSB3b3VsZCBiZSBoYXBweSBvZiBmdXJ0aGVy
IGNsYXJpZmljYXRpb24gYW5kIHN1Z2dlc3RlZCB0ZXh0IHRvIGlsbHVzdHJhdGUgeW91ciBwcmVm
ZXJlbmNlcyB3b3VsZCBiZSBlc3BlY2lhbGx5IHdlbGNvbWUuDQpbTWVkXSBTdXJlLiBCZWZvcmUg
dGhhdCwgY2FuIHlvdSBwbGVhc2UgY29uc2lkZXIgcmVjaGVja2luZyB0aGUgZGV0YWlsZWQgbGlz
dCBvZiBjb21tZW50cyBhdmFpbGFibGUgYXQ6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWwtYXJj
aGl2ZS93ZWIvaWV0Zi9jdXJyZW50L21zZzEwMTYyOS5odG1sLiBUaGFuayB5b3UuDQoNClRoYW5r
cyBhZ2FpbiBmb3IgeW91ciBlbmdhZ2VtZW50IG9uIHRoaXMsDQpyZWdhcmRzLA0KVGVkDQoNCg0K
dGhhbmtzLA0KVGVkIEhhcmRpZQ0KDQoNCkNoZWVycywNCk1lZA0KDQpEZSA6IFRlZCBIYXJkaWUg
W21haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jbzxtYWlsdG86dGVkLmlldGZAZ21haWwuY28+bV0NCkVu
dm95w6kgOiBtZXJjcmVkaSAyMiBmw6l2cmllciAyMDE3IDIzOjA5DQrDgCA6IEJPVUNBREFJUiBN
b2hhbWVkIElNVC9PTE4NCkNjIDogaWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz47
IGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbkBpZXRmLm9yZzxtYWlsdG86
ZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRhdGEtaW5zZXJ0aW9uQGlldGYub3JnPg0KT2JqZXQg
OiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRhdGEtaW5zZXJ0aW9u
LTA1LnR4dD4gKERlc2lnbiBjb25zaWRlcmF0aW9ucyBmb3IgTWV0YWRhdGEgSW5zZXJ0aW9uKSB0
byBJbmZvcm1hdGlvbmFsIFJGQw0KDQpIaSBNb2hhbWVkLA0KVGhhbmtzIGZvciB5b3VyIHJldmll
dy4gIEkndmUgdXBsb2FkZWQgYSBkcmFmdCAtMDYgd2l0aCB1cGRhdGVzIGZyb20geW91ciBhbmQg
b3RoZXIgcmV2aWV3cy4gIFNvbWUgbm90ZXMgaW4tbGluZS4NCg0KT24gVHVlLCBKYW4gMzEsIDIw
MTcgYXQgMTo0OSBBTSwgPG1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb208bWFpbHRvOm1vaGFt
ZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20+PiB3cm90ZToNCkRlYXIgVGVkLA0KDQpQbGVhc2UgZmlu
ZCBiZWxvdyBteSBnZW5lcmFsIHJldmlldyBvZiB0aGUgZG9jdW1lbnQgYW5kIGFsc28gbXkgZGV0
YWlsZWQgY29tbWVudHMuDQoNCiogT3ZlcmFsbDoNCi0gSSBkb24ndCB0aGluayB0aGUgZG9jdW1l
bnQgaXMgcmVhZHkgdG8gYmUgcHVibGlzaGVkIGFzIGl0IGlzLiBJdCBkb2VzIG5vdCBkaXNjdXNz
IHRoZSB1c2FiaWxpdHkgYW5kIGltcGxpY2F0aW9ucyBvZiB0aGUgYWR2aWNlLiBGdXJ0aGVyLCBp
dCBtYXkgYmUgaW50ZXJwcmV0ZWQgdGhhdCBhIGNsaWVudC9lbmQgc3lzdGVtL3VzZXIgY2FuIGFs
d2F5cyBieSBpdHNlbGYgcG9wdWxhdGUgZGF0YSB0aGF0IGlzIHN1cHBsaWVkIGJ5IG9uLXBhdGgg
bm9kZXMgKGluIGN1cnJlbnQgZGVwbG95bWVudHMpLiBUaGF0J3MgYXNzdW1wdGlvbiBpcyBub3Qg
dHJ1ZSBmb3Igc29tZSBwcm90b2NvbHMuDQotIFRoZSBwdXJwb3NlIG9mIHB1Ymxpc2hpbmcgdGhp
cyBhZHZpY2UgaXMgbm90IGNsZWFyLiBGb3IgZXhhbXBsZSwgaG93IHRoaXMgYWR2aWNlIHdpbGwg
YmUgaW1wbGVtZW50ZWQgaW4gcHJhY3RpY2U/IFdoYXQgaXMgaXRzIHNjb3BlPw0KLSBJIHdvdWxk
IHBlcnNvbmFsbHkgcHJlZmVyIGFuIHVwZGF0ZWQgdmVyc2lvbiBvZiBSRkM3MjU4IHdpdGggbW9y
ZSBzdHJpY3QgbGFuZ3VhZ2Ugb24gdGhlIHByaXZhY3ktcmVsYXRlZCBjb25zaWRlcmF0aW9ucy4g
VGhpcyBpcyBtb3JlIGFjdGlvbmFibGUgd2l0aCBjb25jcmV0ZSBlZmZlY3RzIGluIGRvY3VtZW50
cyB0aGF0IHdpbGwgcmVxdWlyZWQgdG8gaW5jbHVkZSBhIGRpc2N1c3Npb24gb24gcHJpdmFjeSBy
ZWxhdGVkIG1hdHRlcnMuDQoNCkRldGFpbGVkIGNvbW1lbnRzIGFyZSBwcm92aWRlZCBiZWxvdzoN
Cg0KKiBUaGUgYWJzdHJhY3Qgc2F5cyB0aGUgZm9sbG93aW5nOg0KDQogICBUaGUgSUFCIGhhcyBw
dWJsaXNoZWQgW1JGQzc2MjRdIGluIHJlc3BvbnNlIHRvIHNldmVyYWwgcmV2ZWxhdGlvbnMgb2YN
CiAgIHBlcnZhc2l2ZSBhdHRhY2sgb24gSW50ZXJuZXQgY29tbXVuaWNhdGlvbnMuICBUaGlzIGRv
Y3VtZW50IGNvbnNpZGVycw0KICAgdGhlIGltcGxpY2F0aW9ucyBvZiBwcm90b2NvbCBkZXNpZ25z
IHdoaWNoIGFzc29jaWF0ZSBtZXRhZGF0YSB3aXRoDQogICBlbmNyeXB0ZWQgZmxvd3MuICBJbiBw
YXJ0aWN1bGFyLCBpdCBhc3NlcnRzIHRoYXQgZGVzaWducyB3aGljaCBkbyBzbw0KICAgYnkgZXhw
bGljaXQgYWN0aW9ucyBvZiB0aGUgZW5kIHN5c3RlbSBhcmUgcHJlZmVyYWJsZSB0byBkZXNpZ25z
IGluDQogICAgICBeXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eDQogICB3aGljaCBt
aWRkbGVib3hlcyBpbnNlcnQgdGhlbS4NCg0KSSBzdWdnZXN0IHlvdSBleHBsaWNpdCB3aGF0IGlz
IG1lYW50IGJ5ICJ0aGUgZW5kIHN5c3RlbSIuDQoNCkkgaGF2ZSB1cGRhdGVkIHRoaXMgdG8gY2xh
cmlmeSB0aGF0IHRoaXMgaXMgdGhlIGhvc3QvZW5kIHN5c3RlbSBub3QgdGhlIHVzZXIuDQoNCklm
IHlvdSBtZWFuIHRoZSBvd25lci91c2VyLCB0aGVuIHRoZSB0ZXh0IHNob3VsZCBzYXkgc28uIElm
IHlvdSBtZWFuIGEgY2xpZW50IHNvZnR3YXJlIGluc3RhbmNlLCB0aGVuIGJ1Z3MvaW5hcHByb3By
aWF0ZSBkZWZhdWx0IHZhbHVlcyBtYXkgbGVhZCB0byAocHJpdmFjeSBsZWFrKSBzdXJwcmlzZXMg
dG9vLiBJdCB3YXMgcmVwb3J0ZWQgaW4gdGhlIHBhc3QgdGhhdCBzb21lIGJyb3dzZXJzIGluamVj
dCB0aGUgTVNJU0ROIHRvby4NCg0KKiBJbnRyb2R1Y3Rpb246ICJUbyBlbnN1cmUgdGhhdCB0aGUg
SW50ZXJuZXQgY2FuIGJlIHRydXN0ZWQgYnkgdXNlcnMiDQoNClJhdGhlciDCqyBUbyBtaW5pbWl6
ZSB0aGUgcmlzayBvZiBJbnRlcm5ldC1vcmlnaW5hdGVkIGF0dGFja3MgdGFyZ2V0ZWQgYXQgdXNl
cnMgwrsuDQoNCkkndmUgYWRvcHRlZCB0aGlzIGxhbmd1YWdlLg0KDQpJdCdzIHJlYXNvbmFibGUg
dG8gY2xhaW0gdGhlIEludGVybmV0IGNhbiBiZSB0cnVzdGVkIGJ5IHVzZXJzOyBzZWUgaG93IHRo
ZSB1c2FnZSBvZiBzb2NpYWwgbmV0d29ya3MgaGFzIGJlY29tZSBzZXZlcmVseSB0d2lzdGVkIGZv
ciBleGFtcGxlDQoNCkkndmUgYWxzbyBjb25zaWRlcmVkIHlvdXIgcG9pbnQgdGhhdCBhbiB1cGRh
dGVkIHZlcnNpb24gb2YgUkZDNzI1OCBtaWdodCBiZSBhIGJldHRlciBvdXRsZXQgZm9yIGFkdmlj
ZSBsaWtlIHRoaXMuIFdlIGRpZCBjb25zaWRlciBzZXZlcmFsIGFwcHJvYWNoZXMsIGluY2x1ZGlu
ZyBpbmNvcnBvcmF0aW5nIHRoZSB0ZXh0IGluIGFuIHVwZGF0ZSB0byAgUkZDIDM1NTIgb3IgYXMg
cGFydCBvZiBhIGRvY3VtZW50IGRlc2NyaWJpbmcgdGhlIGZ1bGwgc2V0IG9mIGNvbXBhbmlvbiBt
aXRpZ2F0aW9ucyB0byB0aGUgdGhyZWF0cyBpbiBSRkMgNzYyNCAoZHJhZnQtaWFiLXByaXZzZWMt
Y29uZmlkZW50aWFsaXR5LW1pdGlnYXRpb25zIHdvdWxkIGJlIG9uZSBhcHByb2FjaCkuICBUaG9z
ZSBhcmUgYWxsIHZhbGlkIGFwcHJvYWNoZXMsIGJ1dCBpdCBzZWVtZWQgdGhhdCBzaG9ydCwgZWFz
aWx5IHJlYWQgZG9jdW1lbnRzIHRhY2tsaW5nIGEgc2luZ2xlIHBvaW50IG1pZ2h0IGJlIGVhc2ll
ciB0byBwcm9kdWNlIGFuZCBjb25zdW1lLg0KVGhhbmtzIGFnYWluIGZvciB5b3VyIHJldmlldywN
ClRlZCBIYXJkaWUNCg0KDQoNCg==

--_000_787AE7BB302AE849A7480A190F8B933009E1B2E6OPEXCLILMA3corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgltc28tc3R5bGUtbGluazoiUHLDqWZvcm1hdMOpIEhUTUwgQ2FyIjsNCgltYXJnaW46
MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYu
TXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlRl
eHRlIGRlIGJ1bGxlcyBDYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0
Ow0KCWZvbnQtc2l6ZTo4LjBwdDsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7
fQ0Kc3Bhbi5tLTgzNzI4OTk2NjEwNzU0ODQ1NDNtLTI3NDY1OTg4MDQ0ODQ5NDMxODVnbWFpbC0N
Cgl7bXNvLXN0eWxlLW5hbWU6bV8tODM3Mjg5OTY2MTA3NTQ4NDU0M20tMjc0NjU5ODgwNDQ4NDk0
MzE4NWdtYWlsLTt9DQpzcGFuLlRleHRlZGVidWxsZXNDYXINCgl7bXNvLXN0eWxlLW5hbWU6IlRl
eHRlIGRlIGJ1bGxlcyBDYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUt
bGluazoiVGV4dGUgZGUgYnVsbGVzIjsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJp
ZiI7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RlI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsN
Cgljb2xvcjpibGFjazsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7
fQ0Kc3Bhbi5QcmZvcm1hdEhUTUxDYXINCgl7bXNvLXN0eWxlLW5hbWU6IlByw6lmb3JtYXTDqSBI
VE1MIENhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQcsOp
Zm9ybWF0w6kgSFRNTCI7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgltc28tZmFyZWFz
dC1sYW5ndWFnZTpGUjt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQt
b25seTsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcwLjg1cHQgNzAuODVwdCA3MC44NXB0
IDcwLjg1cHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48
L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0i
ZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9
ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8
L2hlYWQ+DQo8Ym9keSBsYW5nPSJGUiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2
IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5IaSBUZWQsDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+UGxlYXNlIHNlZSBpbmxpbmUuDQo8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7
Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Q2hlZXJzLDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
Oztjb2xvcjpibGFjayI+TWVkPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBi
bHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0
IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7Ij5EZSZuYnNwOzo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij4gVGVkIEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbV0NCjxicj4NCjxiPkVudm95
w6kmbmJzcDs6PC9iPiBzYW1lZGkgMjUgZsOpdnJpZXIgMjAxNyAwMToyNjxicj4NCjxiPsOAJm5i
c3A7OjwvYj4gQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09MTjxicj4NCjxiPkNjJm5ic3A7OjwvYj4g
aWV0ZkBpZXRmLm9yZzsgZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRhdGEtaW5zZXJ0aW9uQGll
dGYub3JnPGJyPg0KPGI+T2JqZXQmbmJzcDs6PC9iPiBSZTogTGFzdCBDYWxsOiAmbHQ7ZHJhZnQt
aGFyZGllLXByaXZzZWMtbWV0YWRhdGEtaW5zZXJ0aW9uLTA1LnR4dCZndDsgKERlc2lnbiBjb25z
aWRlcmF0aW9ucyBmb3IgTWV0YWRhdGEgSW5zZXJ0aW9uKSB0byBJbmZvcm1hdGlvbmFsIFJGQzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5IaSBNb2hhbWVkLDxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Tb21lIHJlcGxpZXMgaW4tbGluZS48bzpw
PjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIEZyaSwg
RmViIDI0LCAyMDE3IGF0IDEyOjU1IEFNLCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1vaGFtZWQuYm91
Y2FkYWlyQG9yYW5nZS5jb20iIHRhcmdldD0iX2JsYW5rIj5tb2hhbWVkLmJvdWNhZGFpckBvcmFu
Z2UuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkhpIFRlZCwNCjwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6Ymxh
Y2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDs7Y29sb3I6YmxhY2siPlBsZWFzZSBzZWUgaW5saW5lLg0KPC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Jm5i
c3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
Oztjb2xvcjpibGFjayI+Q2hlZXJzLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPk1lZDwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRp
bmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+RGUmbmJzcDs6PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90OyI+IFRlZCBIYXJkaWUgW21haWx0bzo8YSBocmVmPSJtYWlsdG86dGVkLmlldGZA
Z21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+dGVkLmlldGZAZ21haWwuY29tPC9hPl0NCjxicj4N
CjxiPkVudm95w6kmbmJzcDs6PC9iPiB2ZW5kcmVkaSAyNCBmw6l2cmllciAyMDE3IDAwOjQwPGJy
Pg0KPGI+w4AmbmJzcDs6PC9iPiBCT1VDQURBSVIgTW9oYW1lZCBJTVQvT0xOPGJyPg0KPGI+Q2Mm
bmJzcDs6PC9iPiA8YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsi
PmlldGZAaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaGFyZGllLXByaXZzZWMt
bWV0YWRhdGEtaW5zZXJ0aW9uQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+DQpkcmFmdC1oYXJk
aWUtcHJpdnNlYy1tZXRhZGF0YS1pbnNlcnRpb25AaWV0Zi5vcmc8L2E+PGJyPg0KPGI+T2JqZXQm
bmJzcDs6PC9iPiBSZTogTGFzdCBDYWxsOiAmbHQ7ZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRh
dGEtaW5zZXJ0aW9uLTA1LnR4dCZndDsgKERlc2lnbiBjb25zaWRlcmF0aW9ucyBmb3IgTWV0YWRh
dGEgSW5zZXJ0aW9uKSB0byBJbmZvcm1hdGlvbmFsIFJGQzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SEkgTW9oYW1hZCw8YnI+DQo8YnI+
DQpUaGFua3MgZm9yIHJlY2hlY2tpbmc7IHNvbWUgZnVydGhlciBjb21tZW50cyBpbi1saW5lLjxi
cj4NCjxicj4NCk9uIFdlZCwgRmViIDIyLCAyMDE3IGF0IDExOjIxIFBNLCAmbHQ7PGEgaHJlZj0i
bWFpbHRvOm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20iIHRhcmdldD0iX2JsYW5rIj5tb2hh
bWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8
ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6
NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206NS4w
cHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+SGkgVGVkLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+VGhhbmsgeW91IGZvciB0aGUgcmVwbHkgYW5kIGZv
ciBpbXBsZW1lbnRpbmcgdGhlc2UgY2hhbmdlcy4NCjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4m
bmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+SSBjaGVja2VkIHRoZSBkaWZmLCBidXQgSeKA
mW0gYWZyYWlkIHRoZSAtMDYgdmVyc2lvbiBoYXMgdGhlIHNhbWUgaXNzdWVzIGFzIHRoZSBvbmVz
IEkgcmVwb3J0ZWQgaW4NCiBKYW51YXJ5IDMxLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPkkgZGlkIHJlc3BvbmQgdG8gdGhlIHBhcnRpY3Vs
YXIgY29tbWVudHMgYW5kIHRleHQgcHJvcG9zYWxzLCBzbyBJIGFzc3VtZSB0aGlzIGlzIHRoZSBt
b3JlIGdlbmVyYWwgaXNzdWUuJm5ic3A7IElmIEkgdW5kZXJzdGFuZCBjb3JyZWN0bHksIHlvdSB3
b3VsZCBwcmVmZXIgdGhpcyBkb2N1bWVudCB0byBiZSBzdHJ1Y3R1cmVkIGFzDQogYSByZXZpc2lv
biB0byB0aGUgdGhyZWF0IG1vZGVsIGRvY3VtZW50IG9yIGNvbm5lY3RlZCB0byBhIGxhcmdlciBj
b25zaWRlcmF0aW9uIG9mIHRoZSBpc3N1ZXMuJm5ic3A7IEkgdW5kZXJzdGFuZCB0aGF0LCBhbmQg
aXQgd2FzIGNvbnNpZGVyZWQsIGJ1dCBJIGJlbGlldmUgdGhhdCB0aGlzIGZvcm1hdCBpcyBzdGls
bCB0aGUgbW9zdCBlZmZlY3RpdmUgZm9yIHRoZSBuYXJyb3cgaXNzdWUgaXQgYWRkcmVzc2VzLjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29s
b3I6YmxhY2siPltNZWRdIFRoYXQgd2FzIG9uZSBvZiBteSBjb25jZXJuczsgbm90IHRoZSBvbmx5
IG9uZS4gSW4gUGFydGljdWxhciwgSeKAmW0gdHJ5aW5nIHRvIHVuZGVyc3RhbmQgaG93IHRoaXMN
CiBkb2N1bWVudCB3aWxsIGJlIHVzZWQgaW4gdGhlIGZ1dHVyZSB0byBiZXR0ZXIgc3RyZW5ndGhl
biBmb3J0aGNvbWluZyBzcGVjaWZpY2F0aW9ucy4gRnVydGhlciwgdGhlIGV4cGVyaWVuY2UgSSBo
YWQgd2hlbiBhZHZhbmNpbmcgc29tZSBSRkNzIGlzIHRoYXQgUkZDNzI1OCB3b3JkaW5nIGNhbiBi
ZSBmdXJ0aGVyIGVuaGFuY2VkIHRvIHByb3ZpZGUgY2xlYXIgZ3VpZGFuY2UuIEFsc28sIGNvbnNp
ZGVyYXRpb25zIHN1Y2ggYXMgdGhlIGZvbGxvd2luZw0KIGFyZSBtaXNzaW5nIGZyb20gdGhlIGRv
Y3VtZW50Ojwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SXQncyBkaWZmaWN1bHQgdG8gc2F5IGhvdyBz
b21ldGhpbmcgd2lsbCBiZSB1c2VkIGluIHRoZSBmdXR1cmUuJm5ic3A7PHNwYW4gc3R5bGU9ImNv
bG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+W01lZF0gQW4gYWR2aWNlIHRoYXQgaXMgbm90IGltcGxlbWVudGFibGUgbWFrZXMgbW9y
ZSB0cm91YmxlcywgSU1ITy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5NeSBp
bnRlbnQgKGFuZCB0aGUgdW5kZXJzdGFuZGluZyBvZiBvdGhlciByZXZpZXdlcnMpIGlzIHRvIGhp
Z2hsaWdodCB0aGF0IHRoZXNlIG1lY2hhbmlzbXMgaGF2ZSBhIHByaXZhY3ktZGFtYWdpbmcgcmVz
dWx0IGFuZCB0aGF0IHRoaXMgc2hvdWxkIGJlIGNvbnNpZGVyZWQuJm5ic3A7PHNwYW4gc3R5bGU9
ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPltNZWRdIEkgZG8gdGhpbmsgZXhpc3RpbmcgZG9jdW1lbnRzIGFscmVh
ZHkgbWFrZSB0aGF0IGpvYi4gSSBkbyB0aGluayB3ZSBuZWVkIG1vcmUuICZuYnNwOyZuYnNwOyZu
YnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
YXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwO0luIHBhcnRpY3Vs
YXJseSwgSSdtIGNvbmNlcm5lZCB0aGF0IHNvbWUgYXBwbGljYXRpb24gZnVuY3Rpb25zIGluIHRo
ZSBuZXR3b3JrIChlLmcuIHJlY3Vyc2l2ZSByZXNvbHZlcnMgb3IgcHJveGllcykgZG8gbm90IGNv
bnNpZGVyIHRoZSBwb3N0aXZlIHByaXZhY3kgaW1wbGljYXRpb25zIG9mIHRoZWlyIGFnZ3JlZ2F0
aW9uIGFuZA0KIHNvIGRvIG5vdCBjb25zaWRlciBhZGRpbmcgdGhpcyBkYXRhIGJhY2sgYXMgcHJv
YmxlbWF0aWMuPHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIEnigJltIGFsc28gY29u
Y2VybmVkIHdpdGggdGhhdCwgdG9vIChzZWUgZS5nLiwNCjxhIGhyZWY9Imh0dHA6Ly93d3cxLmlj
c2kuYmVya2VsZXkuZWR1L35uYXJzZW8vcGFwZXJzL2hvdG00Mi12YWxsaW5hcm9kcmlndWV6LnBk
ZiI+DQpodHRwOi8vd3d3MS5pY3NpLmJlcmtlbGV5LmVkdS9+bmFyc2VvL3BhcGVycy9ob3RtNDIt
dmFsbGluYXJvZHJpZ3Vlei5wZGY8L2E+KS4gSW4gdGhlIG1lYW50aW1lLCBJ4oCZbSBhbHNvIGNv
bmNlcm5lZCB3aXRoICgxKSBzb21lIGFwcGxpY2F0aW9ucyB0aGF0IGxlYWsgcHJpdmFjeSBpbmZv
cm1hdGlvbiB3aXRob3V0IHRoZSBjb25zZW50IG9mIHRoZSB1c2VyIGFuZCAoMikgc29tZSBhcHBs
aWNhdGlvbiBzZXJ2ZXJzIHRoYXQgbWF5IGNvcnJlbGF0ZSB2YXJpb3VzDQogaW5mb3JtYXRpb24g
c2hhcmVkIGJ5IGFuIGFwcGxpY2F0aW9uIGNsaWVudCB0byB0cmFjayB1c2VycyAoZS5nLiwgPGEg
aHJlZj0iaHR0cHM6Ly9wYW5vcHRpY2xpY2suZWZmLm9yZy8iPg0KaHR0cHM6Ly9wYW5vcHRpY2xp
Y2suZWZmLm9yZy88L2E+KS4gQlRXLCBJIHNlZSB0aGF0IHlvdSBhcmUgdXNpbmcg4oCcYXBwbGlj
YXRpb24gZnVuY3Rpb27igJ0gd2hpY2ggbWF5IG5vdCBoYXZlIHRoZSBzYW1lIG1lYW5pbmcgYXMg
dGhlIGdlbmVyYWwg4oCccHJvdG9jb2zigJ0gd29yZGluZyB1c2VkIGluIGRyYWZ0LWhhcmRpZS0q
LiBEbyB5b3UgY29uc2lkZXIgYSBESENQIHJlbGF5IGFzIGFuIOKAnGFwcGxpY2F0aW9uIGZ1bmN0
aW9u4oCdPw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7Jm5ic3A7
IEhpZ2hsaWdodGluZyB0aGlzIGVuYWJsZXMgdGhlbSB0byBzZWUgdGhpcyB0cmFmZmljIGluIGEg
ZGlmZmVyZW50IGNvbnRleHQuPHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwv
c3Bhbj48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0
b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIElzbuKA
mXQgdGhpcyBhbHJlYWR5IGFzc3VtZWQgYnkgc29tZSBwcm90b2NvbCBkZXNpZ25lcnMgKGUuZy4s
IFJGQzY5NzMsIFNJUCk/IEJUVywgdGhlcmUgYXJlIHN1YnRsZXRpZXMgd2hlbiBwcm94aWVzIGFy
ZQ0KIGluIHRoZSBzYW1lIHRydXN0IGRvbWFpbiBvZiB0aGUgY2xpZW50IG9yIHNlcnZlci4gJm5i
c3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48YnI+DQo8YnI+DQo8L3NwYW4+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4qIHRoYXQgZGF0YSBtYXkgbm90IGJlIGFsd2F5cyBh
dmFpbGFibGUgdG8gdGhlIGVuZGhvc3Q8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5VbmRlcnN0b29k
LCBidXQgZXZlbiBpbiB0aGlzIGNhc2UsIGl0IGlzIGJldHRlciB0byBtYWtlIHRoZSBwZXJtaXNz
aW9uIHRvIGFkZCB0aGUgZGF0YSBleHBsaWNpdC48L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01l
ZF0gVGhpcyBtYXkgYmUgZWFzeSB0byBpbXBsZW1lbnQgZm9yIHNvbWUgYXBwbGljYXRpb25zLCBi
dXQgdGhpcyBtYXkgbm90IGJlIGdlbmVyYWxpemVkIHRvICoqIGFsbCAqKiBwcm90b2NvbHMuIFB1
dHRpbmcgYXNpZGUgdGhlIGludGVyYWN0aW9uIHdpdGggYSB1c2VyDQogdG8gZ2V0IGEgY29uc2Vu
dCBhbmQgaG93IHRoYXQgY29uc2VudCB3aWxsIG5lZWQgdG8gYmUgY2hhbmdlZCB3aGVuIGFub3Ro
ZXIgdXNlciB1c2VzIHRoZSBzYW1lIGRldmljZSB0byBjb25uZWN0IHRvIHRoZSBJbnRlcm5ldC4g
Q29uc2lkZXIgYSB1c2VyIHdobyBkb2VzIG5vdCB3YW50IGFuIHVwc3RyZWFtIERIUEMgcmVsYXkg
dG8gaW5zZXJ0IHRoZSBsaW5lLWlkICg8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvcmZjNjc4OCI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzY3ODg8L2E+KQ0KIHRv
IHRoZSBzZXJ2ZXIsIGFuZCBsZXTigJlzIHN1cHBvc2UgdGhlIHJlbGF5IHJlY2VpdmVkIGEgc2ln
bmFsIChieSBzb21lIG1lYW5zLCB0byBiZSB5ZXQgc3BlY2lmaWVkKSB0aGF0IGZvciB0aGlzIHBh
cnRpY3VsYXIgREhDUCBjbGllbnQsIHRoZSBsaW5lLWlkIG11c3Qgbm90IGJlIGluc2VydGVkLiBG
b3IgdGhpcyBjYXNlLCBjb25uZWN0aXZpdHkgd29u4oCZdCBiZSBwcm92aWRlZCB0byB0aGF0IHVz
ZXIuIFRoaXMgd291bGQgbWVhbiBleHRyYSBjYWxscw0KIHRvIHRoZSBob3RsaW5lIGZvciB0aGF0
IG5ldHdvcmsgcHJvdmlkZXIuIFRoaXMgaXMgbm90IGRlc2lyYWJsZSBmb3IgYm90aCBjdXN0b21l
cnMgYW5kIG5ldHdvcmsgcHJvdmlkZXJzLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDs7Y29sb3I6YmxhY2siPkFub3RoZXIgZXhhbXBsZSBpcyBhZGRyZXNzLXNoYXJpbmcg
KDxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2MjY5I3NlY3Rpb24tMTMu
MSI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzYyNjkjc2VjdGlvbi0xMy4xPC9hPiks
IGEgbWlzYmVoYXZpbmcNCiB1c2VyIG1heSBpbXBhY3QgYWxsIHRoZSB1c2VycyB1bmRlciB0aGUg
c2FtZSBhZGRyZXNzLiBJIGJldCBzdWNoIHVzZXIgd29u4oCZdCBnaXZlIGhpcy9oZXIgcGVybWlz
c2lvbiBzbyB0aGF0IG1lYW5zIHRvIGRlbXV4IGl0cyBwYWNrZXRzLg0KPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+SXQg
aXMgYWxzbyBvZnRlbiBwb3NzaWJsZSBmb3IgdGhlIGVuZCBzeXN0ZW0gdG8gZ2FpbiB0aGlzIGRh
dGEgYXQgdGhlIGNvc3Qgb2Ygb3RoZXIgdHJhZmZpYyhlLmcuIHRoZSBTVFVOIHNlcnZlciByZXF1
ZXN0cyBub3RlZCBpbiB0aGUgZG9jdW1lbnQpLiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNr
Ij5bTWVkXSBJ4oCZbSBub3Qgc3VyZSB3aGV0aGVyIHRoaXMgaXMg4oCYb2Z0ZW7igJksIGJ1dCBm
b3Igc3VyZSB0aGlzIGlzIHBvc3NpYmxlIGZvciBzb21lIGNhc2VzLiBFeHRyYSByZXF1ZXN0cyBt
YXkgYmUgbmVlZGVkLCBJbmRlZWQuIEJldHRlciwgdGhlIGluZm9ybWF0aW9uIG1heQ0KIGV2ZW4g
YmUgZXZlbiBhdmFpbGFibGUgbG9jYWxseSwgZm9yIGV4YW1wbGUgdGhlcmUgaXMgZXZlbiBubyBu
ZWVkIHRvIHJ1biBTVFVOL1BDUCB0byBwcm92aWRlIGFuIFhGRiBvciBGb3J3YXJkLUZvciBoZWFk
ZXJzLiAmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5JZiB0aGlzIGNhbiBiZSBkb25lIGluIHBhcmFsbGVsIHdp
dGggb3RoZXIgYWN0aW9ucywgdGhlbiB0aGUgbGF0ZW5jeSBpbXBhY3QgY2FuIGJlIG1pbmltaXpl
ZC48L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
Oztjb2xvcjpibGFjayI+W01lZF0gVGhlc2UgYXJlIGFzc3VtcHRpb25zIGFuZCBpbXBsaWNhdGlv
bnMgdGhhdCBhcmUgd29ydGggdG8gYmUgYWRkZWQgdG8gdGhlIGRyYWZ0LiBCVFcsIHRoaXMgZmFs
bHMgaW50byB0aGlzIGdlbmVyYWwgZGlzY3Vzc2lvbiBpbg0KPGEgaHJlZj0iaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL3JmYzY5NzMiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2
OTczPC9hPjoNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJzcDsm
bmJzcDsgYS4mbmJzcDsgVHJhZGUtb2Zmcy4mbmJzcDsgRG9lcyB0aGUgcHJvdG9jb2wgbWFrZSB0
cmFkZS1vZmZzIGJldHdlZW4gcHJpdmFjeTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IGFuZCB1c2FiaWxpdHksIHByaXZhY3kgYW5kIGVmZmljaWVuY3ksIHBy
aXZhY3kgYW5kPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
aW1wbGVtZW50YWJpbGl0eSwgb3IgcHJpdmFjeSBhbmQgb3RoZXIgZGVzaWduIGdvYWxzPyZuYnNw
OyBEZXNjcmliZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IHRoZSB0cmFkZS1vZmZzIGFuZCB0aGUgcmF0aW9uYWxlIGZvciB0aGUgZGVzaWduIGNob3Nlbi48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20g
Ni4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4N
CjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFk
ZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1i
b3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiogYSBtaXNi
ZWhhdmluZyBub2RlIG1heSBiZSB0ZW1wdGVkIHRvIHNwb29mIHRoZSBkYXRhIHRvIGJlIGluamVj
dGVkLiBBIHJlbW90ZSBkZXZpY2UgdGhhdCB3aWxsIHVzZSB0aGF0DQogZGF0YSB0byBlbmZvcmNl
IHBvbGljaWVzIHdpbGwgYmUgYnJva2VuLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1
b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEy
LjBwdCI+VGhpcyBwb2ludCB3YXMgZGlzY3Vzc2VkIGV4dGVuc2l2ZWx5IGluIHRoZSBHRU9QUklW
IHdvcmsgYW5kIGVzc2VudGlhbGx5IGEgc2luZ2xlIGNhcnZlLW91dCB3YXMgbWFkZTombmJzcDsg
Zm9yIGVtZXJnZW5jeSBzZXJ2aWNlcywgd2hlcmUgZmFsc2VseSBhc3NlcnRlZCBsb2NhdGlvbiBk
YXRhIGNvdWxkIGJlIHVzZWQgdG8gU1dBVCBpbmRpdmlkdWFscyBvciBjb25zdW1lDQogc2FmZXR5
IHJlc291cmNlcy4mbmJzcDsmbmJzcDsmbmJzcDsgSSBkb24ndCB0aGluayB0aGF0IGZhbGxzIGlu
dG8gdGhpcyBuYXJyb3cgYWR2aWNlLCBidXQgSSB3b3VsZCBiZSB3aWxsaW5nIHRvIGFkZCBzb21l
dGhpbmcgbGlrZSB0aGlzIHRvIHRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9uczo8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZxdW90O05vdGUgdGhh
dCBzb21lIGVtZXJnZW5jeSBzZXJ2aWNlIHJlY2lwaWVudHMsIG5vdGFibHkgUFNBUHMgKFB1Ymxp
YyBTYWZldHkgQW5zd2VyaW5nIFBvaW50cykgbWF5IHByZWZlciBkYXRhIHByb3ZpZGVkIGJ5IGEg
bmV0d29yayB0byBkYXRhIHByb3ZpZGVkIGJ5IGVuZCBzeXN0ZW0sIGJlY2F1c2UgYW4gZW5kIHN5
c3RlbSBjb3VsZCB1c2UgZmFsc2UgZGF0YSB0byBhdHRhY2sgb3RoZXJzIG9yIGNvbnN1bWUgcmVz
b3VyY2VzLiZuYnNwOyZuYnNwOw0KIFdoaWxlIHRoaXMgaGFzIHRoZSBjb25zZXF1ZW5jZSB0aGF0
IHRoZSBkYXRhIGF2YWlsYWJsZSB0byB0aGUgUFNBUCBpcyBvZnRlbiBtb3JlIGNvYXJzZSB0aGFu
IHRoYXQgYXZhaWxhYmxlIHRvIHRoZSBlbmQgc3lzdGVtLCB0aGUgcmlzayBvZiBmYWxzZSBkYXRh
IGJlaW5nIHByb3ZpZGVkIGludm9sdmVkIGEgcmlzayB0byB0aGUgbGl2ZXMgb2YgdGhvc2UgdGFy
Z2V0ZWQuJnF1b3Q7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291
cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIFRoYW5rIHlvdS4gUHJvdmlkaW5nIFBT
QVAgYXMgYW4gZXhhbXBsZSBpcyBPSywgYnV0IEnigJlkIGxpa2UgdGhlIGlzc3VlIHRvIGJlIGNh
bGxlZCBvdXQgYXMgYSBnZW5lcmljIG9uZSB3aGlsZSBQU0FQIGlzIHByb3ZpZGVkIGFzIGFuIGV4
YW1wbGUuIFdoYXQgYWJvdXQNCiB0aGUgZm9sbG93aW5nOiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIj4mcXVvdDtOb3RlIHRoYXQgc29tZSBzZXJ2ZXJzIChlLmcuLCBlbWVyZ2Vu
Y3kgc2VydmljZSByZWNpcGllbnRzLCBub3RhYmx5IFBTQVBzIChQdWJsaWMgU2FmZXR5IEFuc3dl
cmluZyBQb2ludHMpIFtSRkM2NDQzXSkgbWF5IHByZWZlciBkYXRhIHByb3ZpZGVkIGJ5IGEgbmV0
d29yayB0byBkYXRhIHByb3ZpZGVkIGJ5IHRoZSBlbmQgc3lzdGVtLCBiZWNhdXNlIGFuIGVuZCBz
eXN0ZW0gY291bGQNCiB1c2UgZmFsc2UgZGF0YSB0byBhdHRhY2sgb3RoZXJzIG9yIGNvbnN1bWUg
cmVzb3VyY2VzLiZuYnNwOyBXaGlsZSB0aGlzIGhhcyB0aGUgY29uc2VxdWVuY2UgdGhhdCB0aGUg
ZGF0YSBhdmFpbGFibGUgdG8gdGhlIHNlcnZlciBpcyBvZnRlbiBtb3JlIGNvYXJzZSB0aGFuIHRo
YXQgYXZhaWxhYmxlIHRvIHRoZSBlbmQgc3lzdGVtLCB0aGUgcmlzayBvZiBmYWxzZSBkYXRhIGJl
aW5nIHByb3ZpZGVkIGludm9sdmVkIGEgcmlzayB0byB0aGUgbGl2ZXMgb2YgdGhvc2UNCiB0YXJn
ZXRlZC4mcXVvdDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4NCjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0ND
QyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdp
bi1yaWdodDowY20iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRp
dj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj4qIGl0IHdhcyByZXBvcnRlZCBpbiB0aGUgcGFzdCB0aGF0IHNv
bWUgYnJvd3NlcnMgbGVhayB0aGUgTVNJU0ROIGFuZCBvdGhlciBzZW5zaXRpdmUgZGF0YS48L3Nw
YW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5UaGlzIGlz
IHRydWUsIGJ1dCA8L3NwYW4+aXQgc2VlbXMgdG8gbWUgdW5yZWxhdGVkIHRvIHRoZSBwb2ludCBv
ZiB0aGUgZG9jdW1lbnQuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIEl0IGlz
IHJlbGF0ZWQgYmVjYXVzZSBibGluZGx5IHRydXN0aW5nIGFuIGFwcGxpY2F0aW9uIGNsaWVudCAo
YW5kIHNlcnZlcikgaGFzIGl0cyBvd24gcHJpdmFjeSByaXNrcy4gVGhpcyBpcyBldmVuIGV4YWNl
cmJhdGVkIGdpdmVuIHRoZSByaWNoIGRhdGEgdGhhdA0KIGlzIGF2YWlsYWJsZSB0byBhbiBhcHBs
aWNhdGlvbiBjbGllbnQgYW5kIGFsc28gYmVjYXVzZSBvZiB0aGUgdmlzaWJpbGl0eSBvbiB2YXJp
b3VzIGxheWVycyBhdmFpbGFibGUgdG8gYW4gYXBwbGljYXRpb24gc2VydmVyLg0KPC9zcGFuPjxz
cGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxi
bG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEu
MHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJp
Z2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1s
ZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJF
Ti1VUyI+RnJvbSB0aGF0IGZsb3cgc29tZSBvZiB5b3VyIG90aGVyIGNvbmNlcm5zIGFib3V0IGF1
ZGllbmNlLCBhdCBsZWFzdCBhcyBJIHVuZGVyc3RhbmQuJm5ic3A7IEFzIHdyaXR0ZW48L3NwYW4+
LCB0aGlzIGlzIG5hcnJvdyBhZHZpY2UgZm9yIGEgYnJvYWQgYXVkaWVuY2U6IGJhc2ljYWxseSwN
CiBhbnlvbmUgd2hvIHdvdWxkIGNvbnNpZGVyIHRoZSBmb3JtIG9mIG1ldGFkYXRhIGluc2VydGlv
biBpdCBkZXNjcmliZXMuJm5ic3A7IFlvdSB3b3VsZCwgaWYgSSB1bmRlcnN0YW5kIHlvdSwgcHJl
ZmVyIGEgbmFycm93ZXIgZGVzY3JpcHRpb24gb2YgdGhlIGF1ZGllbmNlIGluIGEgbGFyZ2VyIGNv
bnRleHQuJm5ic3A7DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+W01lZF0gVGhlIGtleSBwb2ludCBoZXJlIGlzIGFib3V0IHRoZSBwcmFjdGljYWxpdHkg
b2YgaW1wbGVtZW50aW5nIHRoZSBhZHZpY2UgTk9UIGNoYW5naW5nIHRoZQ0KIHNjb3BlLiBGb3Ig
ZXhhbXBsZSwgdGhlIGRvY3VtZW50IHNheXMgdGhhdCBpdCBpcyBiZXR0ZXIgdGhhdCBhIGhvc3Qg
aXMgaW5qZWN0aW5nIHRoZSBkYXRhIGJ1dCB0aGUgZG9jdW1lbnQgZG9lcyBub3QgcXVlc3Rpb24g
d2hldGhlciB0aGF0IHN1cHBsaWVkIGRhdGEgY2FuIGJlIHRydXN0ZWQgb3Igbm90LCBvciBob3cg
dGhlIGNvbnNlbnQgd2lsbCBiZSBvYnRhaW5lZCBmcm9tIGEgdXNlci48L3NwYW4+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkluIGdl
bmVyYWwsIHRoZSBwb2ludCBvZiB0aGUgZG9jdW1lbnQgaXMgdGhhdCB0aGUgaG9zdCBzaG91bGQg
YmUgYWJsZSB0byBvbWl0IHRoZSBkYXRhIHdpdGhvdXQgbWlkLW5ldHdvcmsgZGV2aWNlcyBhZGRp
bmcgaXQgYmFjay4mbmJzcDsgVGhhdCdzIHRoZSBwb2ludCBvZiBwcm90ZWN0aW5nIHRoZSB0cmFm
ZmljIGluIHRoZSBmaXJzdCBwbGFjZSwgYWZ0ZXIgYWxsLiZuYnNwOyBJIGFtIHNheWluZyB0aGF0
IGlmIHRoZSBwcm90b2NvbHMNCiByZXF1aXJlIHRoZSBkYXRhLCB0aGVuIGdldHRpbmcgaXQgZnJv
bSB0aGUgZW5kIGhvc3QgaGFzIGJldHRlciBwcml2YWN5IHByb3BlcnRpZXMgdGhhbiBnZXR0aW5n
IGZyb20gaXQgZnJvbSBtaWQtbmV0d29yayBlbnRpdGllcy48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0g
SeKAmW0gbm90IHN1cmUgd2UgY2FuIGhhdmUgc3VjaCBnZW5lcmFsIHN0YXRlbWVudCBiZWNhdXNl
IHRoZSBkYXRhIG1heSBub3QgYmUgYXZhaWxhYmxlIChlLmcuLCBESENQIGZvciBleGFtcGxlKSB0
byBjbGllbnRzICYjNDM7IHRoZSBkYXRhIHN1cHBsaWVkIGJ5IGNsaWVudHMNCiAod2hlbiBwb3Nz
aWJsZSkgbWF5IG5vdCBiZSByZWxpYWJsZSAmIzQzOyBlbmZvcmNpbmcgcG9saWNpZXMgYmFzZWQg
b24gY2xpZW50LXN1cHBsaWVkIGRhdGEgbWF5IGhhdmUgaW1wbGljYXRpb24gb24gb3RoZXIgdXNl
cnMgKGUuZy4sIHNwb29maW5nIFhGRiBmb3IgZXhhbXBsZSkuIE9idmlvdXNseSwgZ2V0dGluZyBz
b21lIG9mIHRoZSBpbmZvcm1hdGlvbiBmcm9tIGEgY2xpZW50IG1heSBoYXZlIGltcGxpY2F0aW9u
cyBvbiBRb0XigKZ0aGUgdXNlciBuZWVkcw0KIHRvIHVuZGVyc3RhbmQgdGhlIHJvb3QgY2F1c2Vz
IG9mIGEgZGVncmFkYXRpb24gb2YgUW9FLiBPZiBjb3Vyc2UsIHRoZXNlIGltcGxpY2F0aW9ucyBt
YXkgbm90IGJlIG5ldyBmb3IgdXNlcnMgd2hvIGFyZSBmYW1pbGlhciB3aXRoIGRpc2FibGluZyBK
YXZhIHNjcmlwdHMgYW5kIGNpZS4gJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpu
b25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2
LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRk
aW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Rm9y
IGV4YW1wbGUsIHRoZSBkb2N1bWVudCBzdGF0ZXMgdGhhdCB0aGUgaW5mb3JtYXRpb24gaW4gYSBG
b3J3YXJkLUZvciBoZWFkZXIgY2FuIGJlIHN1cHBsaWVkIGJ5DQogdGhlIGhvc3QgaXRzZWxmIGFu
ZCB0aGVuIGNvbW11bmljYXRlZCB0byBhIHJlbW90ZSBjb25zdW1lci4gVGhpcyBpcyBpbmRlZWQg
cG9zc2libGUsIGJ1dCBiZWNhdXNlIG9mIGFidXNpbmcgaG9zdHMgc29tZSBzZXJ2ZXJzIGltcGxl
bWVudCB3aGl0ZWxpc3RzIHRvIHRydXN0IHByb3hpZXM7IHNlZQ0KPGEgaHJlZj0iaHR0cHM6Ly9t
ZXRhLndpa2ltZWRpYS5vcmcvdy9leHRlbnNpb25zL1RydXN0ZWRYRkYvdHJ1c3RlZC1ob3N0cy50
eHQiIHRhcmdldD0iX2JsYW5rIj4NCmh0dHBzOi8vbWV0YS53aWtpbWVkaWEub3JnL3cvZXh0ZW5z
aW9ucy9UcnVzdGVkWEZGL3RydXN0ZWQtaG9zdHMudHh0PC9hPi4gJm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPlRoZSBXaWtpbWVkaWEgY2FzZSBpcyBhIHZlcnkgaW50
ZXJlc3Rpbmcgb25lIHRvIHJhaXNlLCBiZWNhdXNlIGl0IGRlcml2ZXMgZnJvbSBhIHNldCBvZiBh
c3N1bXB0aW9ucyBhYm91dCB0aGUgbmV0d29yayB0aGF0IGFyZSBzb21ld2hhdCBmbGF3ZWQgYW5k
IHRoZW4gYXR0ZW1wdHMgdG8gcGF0Y2ggdGhvc2UgZmxhd3MgaW4gd2F5cyB0aGF0IGFjdHVhbGx5
IGRhbWFnZQ0KIHRoZSBtZWNoYW5pc21zIG9mIHRoZSBzeXN0ZW0gdGhleSBvcmlnaW5hbGx5IGJ1
aWx0LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5XaWtpbWVkaWEgd2FudHMgdG8gYWxsb3cgZm9s
a3MgdG8gZWRpdCB3aXRob3V0IGxvZ2luIGNyZWRlbnRpYWxzLiZuYnNwOyBUaGlzIGFsbG93cyBm
b3IgYW5vbnltb3VzIHVzZXJzIHRvIG1ha2UgY29ycmVjdGlvbnMgb3IgYWRkaXRpb25zOyB0aGlz
IGlzIGEgZ29hbC4mbmJzcDsgVGhlIGNvbnNlcXVlbmNlIG9mIHRoYXQgZ29hbCBiZWluZyBhY2hp
ZXZlZCBpcyB0aGF0IHRyb2xscw0KIG9yIG1hbGljaW91cyBlZGl0b3JzIGNhbiBoYXZlIGF0IGFu
eXRoaW5nIHRoZXkgd2FudC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlJhdGhlciB0aGFuIGluc3RpdHV0ZSBjcmVkZW50aWFscyBhbmQgQUNMcywg
V2lraW1lZGlhIGF0dGVtcHRzIHRvIHN1YnN0aXR1dGUgYmxvY2tpbmcgYnkgSVAgZm9yIGJsb2Nr
aW5nIGJ5IGNyZWRlbnRpYWwuJm5ic3A7IFRoZSBwcm9wZXJ0eSB0aGV5IGFyZSBsb29raW5nIGZv
ciBpbiBJUHMgaXMgbm90IHJlYWxseSB0aGVyZSwgdGhvdWdoOiZuYnNwOyB0aGV5IGFyZSBub3Qg
dW5pcXVlIHRvIGluZGl2aWR1YWxzLCBlc3BlY2lhbGx5DQogb3ZlciB0aW1lLiZuYnNwOyA8YnI+
DQo8YnI+DQpUaGlzIGRhbWFnZXMgdGhvc2Ugd2hvIHNoYXJlIElQIGFkZHJlc3NlcyAoZHVlIHRv
IE5BVHMgb3IgcHJveGllcykuJm5ic3A7IEFzIGZhciBhcyBJIGNhbiB0ZWxsLCB0aGUgTkFUIHBy
b2JsZW0gaXMgc2ltcGx5IHRyZWF0ZWQgYXMgY29sbGF0ZXJhbCBkYW1hZ2UuJm5ic3A7IEZvciB0
aGUgcHJveGllcywgdGhleSBhdHRlbXB0IHRvIHdvcmsgYXJvdW5kIHRoZSBkYW1hZ2UgdXNpbmcg
WEZGLiZuYnNwOyBUaGF0J3Mgc3Bvb2ZhYmxlLCB0aG91Z2gsIHNvIHRoZXkgYXR0ZW1wdA0KIHRv
IGxpbWl0IGl0IHRvIHNwZWNpZmljIHByb3hpZXMgd2hvc2UgWEZGIHRoZXkgdHJ1c3QtLW1hbnkg
b2Ygd2hpY2ggcmVxdWlyZSBsb2dpbnMuJm5ic3A7IFRoYXQgc2hpZnRzIHRoZSBpbmZvcm1hdGlv
biBhYm91dCB3aG8gaXMgZWRpdGluZyBXaWtpcGVkaWEgb3V0IG9mIHRoZWlyIGhhbmRzLCBidXQg
bGVhdmVzIGl0IGluIHRoZSBuZXR3b3JrIGFuZCB0aHVzIG5vdCB0cnVseSBhbm9ueW1vdXMuJm5i
c3A7IEkgdW5kZXJzdGFuZCB0aGUgZW5naW5lZXJpbmcgYmFsYW5jZQ0KIHRoZXkgYXJlIHRyeWlu
ZyB0byBzdHJpa2UsIGJ1dCBJJ20gbm90IHN1cmUgSSBjYW4gcmVjb21tZW5kIHRoZWlyIHNvbHV0
aW9uLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gSeKAmW0gbm90IHJlY29t
bWVuZGluZyB0aGVpciBzb2x1dGlvbiBlaXRoZXIsIGJ1dCBJ4oCZbSB0cnlpbmcgdG8gcmFpc2Ug
dGhlIHBvaW50IHRoYXQgYW4gZW5naW5lZXJpbmcgYmFsYW5jZSBpcyBvdXQgdGhlcmUuIEFDS2lu
ZyB0aGF0IGRlcGxveW1lbnQgcmVhbGl0eQ0KIGlzIGJldHRlciB0aGFuIGlnbm9yaW5nIGl0LiA8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0ND
QyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdp
bi1yaWdodDowY20iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRp
dj4NCjxkaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1s
ZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4t
bGVmdDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRv
bTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5J4oCZbSByZWl0ZXJhdGluZyB0aGF0IG1vc3Qgb2Yg
bXkgY29tbWVudHMgYXJlIHN0aWxsIHVuYWRkcmVzc2VkIGluIC0wNi48L3NwYW4+PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
YmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1ib3R0b206MTIuMHB0Ij5JIHJlYWxpemUgdGhhdCB0
aGUgZG9jdW1lbnQgZGlkIG5vdCBjaGFuZ2UgdG8gYWRkcmVzcyB0aGUgYXVkaWVuY2Ugb3IgZG9j
dW1lbnQgaW50ZWdyYXRpb24geW91IHByZWZlcnJlZDsgSSB0aGluayB0aGVyZSB3ZSBzaW1wbHkg
ZGlzYWdyZWUgb24gaG93IHRvIG1ha2UgdGhpcyBhZHZpY2UgZWZmZWN0aXZlLiZuYnNwOyBJJ20g
c29ycnkNCiB0aGF0IGZpcnN0IG1lc3NhZ2UgYXBwYXJlbnRseSBkaWQgbm90IGRlc2NyaWJlIHRo
ZSBkaXNhZ3JlZW1lbnQgZWZmZWN0aXZlbHkuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bWFy
Z2luLWJvdHRvbToxMi4wcHQiPklmIEkgaGF2ZSBtaXN1bmRlcnN0b29kIHlvdXIgY29tbWVudHMs
IHBsZWFzZSBhY2NlcHQgbXkgYXBvbG9naWVzLiBJIHdvdWxkIGJlIGhhcHB5IG9mIGZ1cnRoZXIg
Y2xhcmlmaWNhdGlvbiBhbmQgc3VnZ2VzdGVkIHRleHQgdG8gaWxsdXN0cmF0ZSB5b3VyIHByZWZl
cmVuY2VzIHdvdWxkIGJlIGVzcGVjaWFsbHkgd2VsY29tZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90
dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBTdXJl
LiBCZWZvcmUgdGhhdCwgY2FuIHlvdSBwbGVhc2UgY29uc2lkZXIgcmVjaGVja2luZyB0aGUgZGV0
YWlsZWQgbGlzdCBvZiBjb21tZW50cyBhdmFpbGFibGUgYXQ6DQo8YSBocmVmPSJodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2lldGYvY3VycmVudC9tc2cxMDE2MjkuaHRtbCIg
dGFyZ2V0PSJfYmxhbmsiPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9p
ZXRmL2N1cnJlbnQvbXNnMTAxNjI5Lmh0bWw8L2E+LiBUaGFuayB5b3UuDQo8L3NwYW4+PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5UaGFua3Mg
YWdhaW4gZm9yIHlvdXIgZW5nYWdlbWVudCBvbiB0aGlzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0
Ij5yZWdhcmRzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+VGVkPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48YnI+DQombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzow
Y20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1
ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMi
PnRoYW5rcyw8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj5UZWQgSGFyZGllPC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5n
PSJFTi1VUyI+PGJyPg0KJm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBw
dDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6
NS4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6Ymxh
Y2siPkNoZWVycyw8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+TWVkPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpu
b25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBw
dCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVD
NERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkRlJm5ic3A7
Ojwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gVGVk
DQogSGFyZGllIFttYWlsdG86PGEgaHJlZj0ibWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvIiB0YXJn
ZXQ9Il9ibGFuayI+dGVkLmlldGZAZ21haWwuY288L2E+PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7Ij5tXQ0KPGJyPg0KPGI+RW52b3nDqSZuYnNwOzo8L2I+IG1lcmNyZWRpIDIyIGbD
qXZyaWVyIDIwMTcgMjM6MDk8YnI+DQo8Yj7DgCZuYnNwOzo8L2I+IEJPVUNBREFJUiBNb2hhbWVk
IElNVC9PTE48YnI+DQo8Yj5DYyZuYnNwOzo8L2I+IDxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYu
b3JnIiB0YXJnZXQ9Il9ibGFuayI+aWV0ZkBpZXRmLm9yZzwvYT47IDxhIGhyZWY9Im1haWx0bzpk
cmFmdC1oYXJkaWUtcHJpdnNlYy1tZXRhZGF0YS1pbnNlcnRpb25AaWV0Zi5vcmciIHRhcmdldD0i
X2JsYW5rIj4NCmRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbkBpZXRmLm9y
ZzwvYT48YnI+DQo8Yj5PYmpldCZuYnNwOzo8L2I+IFJlOiBMYXN0IENhbGw6ICZsdDtkcmFmdC1o
YXJkaWUtcHJpdnNlYy1tZXRhZGF0YS1pbnNlcnRpb24tMDUudHh0Jmd0OyAoRGVzaWduIGNvbnNp
ZGVyYXRpb25zIGZvciBNZXRhZGF0YSBJbnNlcnRpb24pIHRvIEluZm9ybWF0aW9uYWwgUkZDPC9z
cGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1i
b3R0b206MTIuMHB0Ij5IaSBNb2hhbWVkLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPlRoYW5rcyBmb3IgeW91ciByZXZpZXcuJm5ic3A7IEkndmUgdXBsb2Fk
ZWQgYSBkcmFmdCAtMDYgd2l0aCB1cGRhdGVzIGZyb20geW91ciBhbmQgb3RoZXIgcmV2aWV3cy4m
bmJzcDsgU29tZSBub3RlcyBpbi1saW5lLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj5PbiBUdWUsIEphbiAzMSwgMjAxNyBhdCAxOjQ5IEFNLCAmbHQ7PGEgaHJlZj0i
bWFpbHRvOm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20iIHRhcmdldD0iX2JsYW5rIj5tb2hh
bWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPkRlYXIgVGVkLDxicj4NCjxicj4NClBsZWFzZSBmaW5kIGJl
bG93IG15IGdlbmVyYWwgcmV2aWV3IG9mIHRoZSBkb2N1bWVudCBhbmQgYWxzbyBteSBkZXRhaWxl
ZCBjb21tZW50cy48YnI+DQo8YnI+DQoqIE92ZXJhbGw6PGJyPg0KLSBJIGRvbid0IHRoaW5rIHRo
ZSBkb2N1bWVudCBpcyByZWFkeSB0byBiZSBwdWJsaXNoZWQgYXMgaXQgaXMuIEl0IGRvZXMgbm90
IGRpc2N1c3MgdGhlIHVzYWJpbGl0eSBhbmQgaW1wbGljYXRpb25zIG9mIHRoZSBhZHZpY2UuIEZ1
cnRoZXIsIGl0IG1heSBiZSBpbnRlcnByZXRlZCB0aGF0IGEgY2xpZW50L2VuZCBzeXN0ZW0vdXNl
ciBjYW4gYWx3YXlzIGJ5IGl0c2VsZiBwb3B1bGF0ZSBkYXRhIHRoYXQgaXMgc3VwcGxpZWQgYnkg
b24tcGF0aCBub2Rlcw0KIChpbiBjdXJyZW50IGRlcGxveW1lbnRzKS4gVGhhdCdzIGFzc3VtcHRp
b24gaXMgbm90IHRydWUgZm9yIHNvbWUgcHJvdG9jb2xzLjxicj4NCi0gVGhlIHB1cnBvc2Ugb2Yg
cHVibGlzaGluZyB0aGlzIGFkdmljZSBpcyBub3QgY2xlYXIuIEZvciBleGFtcGxlLCBob3cgdGhp
cyBhZHZpY2Ugd2lsbCBiZSBpbXBsZW1lbnRlZCBpbiBwcmFjdGljZT8gV2hhdCBpcyBpdHMgc2Nv
cGU/PGJyPg0KLSBJIHdvdWxkIHBlcnNvbmFsbHkgcHJlZmVyIGFuIHVwZGF0ZWQgdmVyc2lvbiBv
ZiBSRkM3MjU4IHdpdGggbW9yZSBzdHJpY3QgbGFuZ3VhZ2Ugb24gdGhlIHByaXZhY3ktcmVsYXRl
ZCBjb25zaWRlcmF0aW9ucy4gVGhpcyBpcyBtb3JlIGFjdGlvbmFibGUgd2l0aCBjb25jcmV0ZSBl
ZmZlY3RzIGluIGRvY3VtZW50cyB0aGF0IHdpbGwgcmVxdWlyZWQgdG8gaW5jbHVkZSBhIGRpc2N1
c3Npb24gb24gcHJpdmFjeSByZWxhdGVkIG1hdHRlcnMuPGJyPg0KPGJyPg0KRGV0YWlsZWQgY29t
bWVudHMgYXJlIHByb3ZpZGVkIGJlbG93Ojxicj4NCjxicj4NCiogVGhlIGFic3RyYWN0IHNheXMg
dGhlIGZvbGxvd2luZzo8YnI+DQo8YnI+DQo8c3BhbiBjbGFzcz0ibS04MzcyODk5NjYxMDc1NDg0
NTQzbS0yNzQ2NTk4ODA0NDg0OTQzMTg1Z21haWwtIj4mbmJzcDsgJm5ic3A7VGhlIElBQiBoYXMg
cHVibGlzaGVkIFtSRkM3NjI0XSBpbiByZXNwb25zZSB0byBzZXZlcmFsIHJldmVsYXRpb25zIG9m
PC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJtLTgzNzI4OTk2NjEwNzU0ODQ1NDNtLTI3NDY1OTg4
MDQ0ODQ5NDMxODVnbWFpbC0iPiZuYnNwOyAmbmJzcDtwZXJ2YXNpdmUgYXR0YWNrIG9uIEludGVy
bmV0IGNvbW11bmljYXRpb25zLiZuYnNwOyBUaGlzIGRvY3VtZW50IGNvbnNpZGVyczwvc3Bhbj48
YnI+DQo8c3BhbiBjbGFzcz0ibS04MzcyODk5NjYxMDc1NDg0NTQzbS0yNzQ2NTk4ODA0NDg0OTQz
MTg1Z21haWwtIj4mbmJzcDsgJm5ic3A7dGhlIGltcGxpY2F0aW9ucyBvZiBwcm90b2NvbCBkZXNp
Z25zIHdoaWNoIGFzc29jaWF0ZSBtZXRhZGF0YSB3aXRoPC9zcGFuPjxicj4NCjxzcGFuIGNsYXNz
PSJtLTgzNzI4OTk2NjEwNzU0ODQ1NDNtLTI3NDY1OTg4MDQ0ODQ5NDMxODVnbWFpbC0iPiZuYnNw
OyAmbmJzcDtlbmNyeXB0ZWQgZmxvd3MuJm5ic3A7IEluIHBhcnRpY3VsYXIsIGl0IGFzc2VydHMg
dGhhdCBkZXNpZ25zIHdoaWNoIGRvIHNvPC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJtLTgzNzI4
OTk2NjEwNzU0ODQ1NDNtLTI3NDY1OTg4MDQ0ODQ5NDMxODVnbWFpbC0iPiZuYnNwOyAmbmJzcDti
eSBleHBsaWNpdCBhY3Rpb25zIG9mIHRoZSBlbmQgc3lzdGVtIGFyZSBwcmVmZXJhYmxlIHRvIGRl
c2lnbnMgaW48L3NwYW4+PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgXl5eXl5eXl5eXl5eXl5e
Xl5eXl5eXl5eXl5eXl5eXl5eXjxicj4NCiZuYnNwOyAmbmJzcDt3aGljaCBtaWRkbGVib3hlcyBp
bnNlcnQgdGhlbS48YnI+DQo8YnI+DQpJIHN1Z2dlc3QgeW91IGV4cGxpY2l0IHdoYXQgaXMgbWVh
bnQgYnkgJnF1b3Q7dGhlIGVuZCBzeXN0ZW0mcXVvdDsuIDxvOnA+PC9vOnA+PC9wPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkkgaGF2ZSB1cGRhdGVkIHRoaXMgdG8gY2xhcmlm
eSB0aGF0IHRoaXMgaXMgdGhlIGhvc3QvZW5kIHN5c3RlbSBub3QgdGhlIHVzZXIuJm5ic3A7DQo8
YnI+DQombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNt
IDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdo
dDowY207bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPklmIHlv
dSBtZWFuIHRoZSBvd25lci91c2VyLCB0aGVuIHRoZSB0ZXh0IHNob3VsZCBzYXkgc28uIElmIHlv
dSBtZWFuIGEgY2xpZW50IHNvZnR3YXJlIGluc3RhbmNlLCB0aGVuIGJ1Z3MvaW5hcHByb3ByaWF0
ZSBkZWZhdWx0IHZhbHVlcyBtYXkgbGVhZCB0byAocHJpdmFjeSBsZWFrKSBzdXJwcmlzZXMgdG9v
Lg0KIEl0IHdhcyByZXBvcnRlZCBpbiB0aGUgcGFzdCB0aGF0IHNvbWUgYnJvd3NlcnMgaW5qZWN0
IHRoZSBNU0lTRE4gdG9vLjxicj4NCjxicj4NCiogSW50cm9kdWN0aW9uOiAmcXVvdDtUbyBlbnN1
cmUgdGhhdCB0aGUgSW50ZXJuZXQgY2FuIGJlIHRydXN0ZWQgYnkgdXNlcnMmcXVvdDs8YnI+DQo8
YnI+DQpSYXRoZXIgwqsgVG8gbWluaW1pemUgdGhlIHJpc2sgb2YgSW50ZXJuZXQtb3JpZ2luYXRl
ZCBhdHRhY2tzIHRhcmdldGVkIGF0IHVzZXJzIMK7Lg0KPG86cD48L286cD48L3A+DQo8L2Jsb2Nr
cXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SSd2ZSBhZG9wdGVkIHRo
aXMgbGFuZ3VhZ2UuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBj
bSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2lu
LXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
SXQncyByZWFzb25hYmxlIHRvIGNsYWltIHRoZSBJbnRlcm5ldCBjYW4gYmUgdHJ1c3RlZCBieSB1
c2Vyczsgc2VlIGhvdyB0aGUgdXNhZ2Ugb2Ygc29jaWFsIG5ldHdvcmtzIGhhcyBiZWNvbWUgc2V2
ZXJlbHkgdHdpc3RlZCBmb3IgZXhhbXBsZTxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21hcmdpbi1ib3R0b206MTIuMHB0Ij5JJ3ZlIGFsc28gY29uc2lkZXJlZCB5b3VyIHBv
aW50IHRoYXQgYW4gdXBkYXRlZCB2ZXJzaW9uIG9mIFJGQzcyNTggbWlnaHQgYmUgYSBiZXR0ZXIg
b3V0bGV0IGZvciBhZHZpY2UgbGlrZSB0aGlzLiBXZSBkaWQgY29uc2lkZXIgc2V2ZXJhbCBhcHBy
b2FjaGVzLCBpbmNsdWRpbmcgaW5jb3Jwb3JhdGluZyB0aGUgdGV4dA0KIGluIGFuIHVwZGF0ZSB0
byZuYnNwOyBSRkMgMzU1MiBvciBhcyBwYXJ0IG9mIGEgZG9jdW1lbnQgZGVzY3JpYmluZyB0aGUg
ZnVsbCBzZXQgb2YgY29tcGFuaW9uIG1pdGlnYXRpb25zIHRvIHRoZSB0aHJlYXRzIGluIFJGQyA3
NjI0IChkcmFmdC1pYWItcHJpdnNlYy1jb25maWRlbnRpYWxpdHktbWl0aWdhdGlvbnMgd291bGQg
YmUgb25lIGFwcHJvYWNoKS4mbmJzcDsgVGhvc2UgYXJlIGFsbCB2YWxpZCBhcHByb2FjaGVzLCBi
dXQgaXQgc2VlbWVkIHRoYXQgc2hvcnQsDQogZWFzaWx5IHJlYWQgZG9jdW1lbnRzIHRhY2tsaW5n
IGEgc2luZ2xlIHBvaW50IG1pZ2h0IGJlIGVhc2llciB0byBwcm9kdWNlIGFuZCBjb25zdW1lLiZu
YnNwOw0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPlRo
YW5rcyBhZ2FpbiBmb3IgeW91ciByZXZpZXcsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlRlZCBIYXJkaWU8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
YmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_787AE7BB302AE849A7480A190F8B933009E1B2E6OPEXCLILMA3corp_--


From nobody Thu Mar  2 06:19:21 2017
Return-Path: <mcr+ietf@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 D4B50129541 for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 06:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5xSX7G6n5hTt for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 06:19:19 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE4BC129531 for <ietf@ietf.org>; Thu,  2 Mar 2017 06:19:19 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 52FBA2009E; Thu,  2 Mar 2017 09:41:40 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 166BC636BB; Thu,  2 Mar 2017 09:19:19 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
In-Reply-To: <B098D021-3503-4CBF-A422-7B3A58997B81@tzi.org>
References: <14476.1488384266@obiwan.sandelman.ca> <13e5803d-c2f3-7bc8-63c8-2a8311c22fae@isi.edu> <17514.1488420343@obiwan.sandelman.ca> <B098D021-3503-4CBF-A422-7B3A58997B81@tzi.org>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 02 Mar 2017 09:19:19 -0500
Message-ID: <15859.1488464359@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8AZlhAwPQG3FgGBkk8NnnEBxKGQ>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 14:19:21 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Carsten Bormann <cabo@tzi.org> wrote:
    >> Good point, but tell me why -01 and -09 and -17 don't come out faste=
r?

    > One contributing factor might be that the submission interface is a p=
ain.

I would like to avoid the confirmation email if I'm logged in, and I'm logg=
ed
in with the email which is an author.  Aside from that, I don't find it a
pain at all.

    > (I still don=E2=80=99t have a Makefile entry for that.)

I agree it would be nice to have a wput script for that. That doesn't
seem that hard to me.


=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAli4KeYACgkQgItw+93Q
3WX48gf+K7yzUkMvaeUadhs92jl5NjrSnkkVJX3PVdqqI0Wm+OXxHLi7pFsnWaDo
dey8AlLdq1sw9+tE3ryp8/8fCl9n4Sy/Tzg+I05k2FHXHjuFoHhOQmtYfE+/zKIs
CU1BakV7guargKfz8JxVHnA//69EMK7+CayrgY+0tTZABaI+44AmaxksCcdmuWM4
BSm6a1xUg3NMR9M1sEgW3t+/Rjm3BQYYjEyNMDuAMXTvZN5pKQqHeozdeWfkXuDK
JFzD+ivVvWGFhf3Ycu/AQZzmI92z2mNHEhYTxY7NA/8BAQAAFk7KQ+XVFpMl7pCe
r2p1ZTEChDai62bw9Vj2rA6sM/ZMCw==
=ShP5
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Mar  2 08:02:59 2017
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 29B031294DA for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 08:02:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y_7N5G8y373c for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 08:02:57 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D06F129505 for <ietf@ietf.org>; Thu,  2 Mar 2017 08:02:57 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v22G2FaL017407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 2 Mar 2017 08:02:17 -0800 (PST)
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <14476.1488384266@obiwan.sandelman.ca> <13e5803d-c2f3-7bc8-63c8-2a8311c22fae@isi.edu> <17514.1488420343@obiwan.sandelman.ca>
From: Joe Touch <touch@isi.edu>
Message-ID: <489dfee3-66d9-03be-2614-4ba0483d0b82@isi.edu>
Date: Thu, 2 Mar 2017 08:02:15 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <17514.1488420343@obiwan.sandelman.ca>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9sjmRs0y6izfXA8-OZRREzdj-ew>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 16:02:58 -0000

Hi, Michael,

On 3/1/2017 6:05 PM, Michael Richardson wrote:
> Joe Touch <touch@isi.edu> wrote:
>     > FWIW, industry often doesn't let out ideas until filing preliminary
>     > patents, which has a similar effect.
>
>     > AFAICT, the speed of an -00 is more tightly correlated to the
>     > motivation for the document.
>
> Good point, but tell me why -01 and -09 and -17 don't come out faster?
> If it's because the authors are busy, and aren't working on that document,
> that's fine.  But I'm seeing some kind of shyness to putting new versions out.

I'm not sure it's easy to determine except on a case-by-case basis.

Other reasons: the community wasn't ready for the doc yet, other docs
took priority (for the author or WG), there might be lots of email list
activity to resolve an issue, etc.

> Is there a distrust of documents which have "too many" revisions?
I'm not sure I'd call it "distrust". But it is hard to keep up with a
constant stream of revisions, esp. for very large docs.

> Should the beautiful history bar in the datatracker, have some measure of
> changes?  Would graph of lines changed (in the XML!) per revision be
> interesting?   Would that help know how close a document is to being ready?
Not necessarily. First, moving sections around can give a false sense of
a major change. And a doc that is only wordsmithed could either be close
to being ready or be an indication of apathy.

There's no substitute for actually tracking what's going on with a
document, and no replacement for a person investing time to figure that out.

Joe


From nobody Thu Mar  2 08:34:26 2017
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 609F61294C0 for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 08:34:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, TVD_PH_BODY_ACCOUNTS_PRE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Aaae7qHhvzD for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 08:34:24 -0800 (PST)
Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCB57129489 for <ietf@ietf.org>; Thu,  2 Mar 2017 08:34:23 -0800 (PST)
Received: by mail-ot0-x231.google.com with SMTP id k4so55722093otc.0 for <ietf@ietf.org>; Thu, 02 Mar 2017 08:34:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4GAvg1UDumyM4OnmsxHglwQuGBz0IMoBKiPEfaQOe1Q=; b=Y+4JPyOrqGhLkRK5ytLKqjX+y/KzNTherWWcF6M7OfBIOK4whxPad/UhulUZC+uChg /Yab3qiv48CFDmCmcenhh+R2ZVgIE3jx7VeV7pQ5OZfWQL/HEkrHpA11F7TXrL6xDrWM zxNsOEbg2UFSi4PSUBQWExhCgq7PVA9NOxcAoWKl8atLwLk14aEJHXx+ax+3a5PL82rY bWe36xIFsKSvbVNLiKSwpKGEsn6KMUqdkGw+yT3Kbmd6jEfsnHLBAJ3lqDlLEE+Mglsu tt71JrYsnoOEZRQpEEmIJPoKyv4lQ6zRpfHMGd0IR7lcKfsIFw4Qud7udWpsadfQtMSL uG4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4GAvg1UDumyM4OnmsxHglwQuGBz0IMoBKiPEfaQOe1Q=; b=mPv46QHwbNaXfdnHQuz4ky7dMefjzHJiHw1gnuY4cvPvz794YA6W77QyLkq86PtKJZ S+9ycHTztZkM4eod/00X91nHobrBtPNjq9irurJEiWtnYfhJ5L9+YEAFEwDDfF1Y7EtE UdfjnIXS6VJL0hJHvDr3kOMUKCIo9SKqZE9mhsVA/ciLOOZGeoUUEonBagwBsQNomtiV 78XWJGHrcroWn4uKmgCDCvoGjo+SVMjJWmd3M1RuZj3G73xn9YV142/w4Lmjg4EDDgMy aD+Fo1vQxzN6/aOL9WU3ElY/k8ni8hLABRvPsWa6fbLsWggOaAamMCidNBTK2yxC0XT6 FXKA==
X-Gm-Message-State: AMke39lbFgWpRBU09jJk5aklRZ1SxjwjTQ7wLU0MHeg2uJquN8BQ0d/x0GHlKWyJQ/1w+aIp4BdH9qV0mrAOMA==
X-Received: by 10.157.63.145 with SMTP id r17mr6966644otc.47.1488472462904; Thu, 02 Mar 2017 08:34:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Thu, 2 Mar 2017 08:33:52 -0800 (PST)
In-Reply-To: <20170302055128.GJ12470@Alexs-MacBook-Pro>
References: <20170302055128.GJ12470@Alexs-MacBook-Pro>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 2 Mar 2017 08:33:52 -0800
Message-ID: <CA+9kkMBdheNCiAAq2xHs5v5UBFErBYhRZ5ksWFq4089ve+NK7g@mail.gmail.com>
Subject: Re: Interest in a push-based two-factor auth standard?
To: Alex Jordan <alex@strugee.net>
Content-Type: multipart/alternative; boundary=001a11c0177068d78c0549c20029
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AVpTB35NaqvNBbT9tyu2GITLdy4>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 16:34:25 -0000

--001a11c0177068d78c0549c20029
Content-Type: text/plain; charset=UTF-8

Hi Alex,

The applications area uses a working group called DISPATCH to answer the
question "where should this work go?", so you might start by writing up the
idea as an Internet draft and submitting to DISPATCH.  The Security area
uses the saag list for similar discussion, if you think it is more of a
security topic than a usage of web push.

regards,

Ted


On Wed, Mar 1, 2017 at 9:51 PM, Alex Jordan <alex@strugee.net> wrote:

> Heya!
>
> A widely deployed way to do two-factor authentication is
> TOTP. However, when used with an Android device Google Accounts have a
> really nice flow where Google will send a push notification to the
> Android device, which will then prompt the user with a "yes/no"
> question as to whether they were trying to log in or not. From a UX
> perspective this is much nicer than opening an app, manually typing in
> a code, etc.
>
> With WebPush core having been just ratified as RFC 8030, the time
> seems ripe for standardizing an authentication scheme like described
> above.
>
> I have two questions:
>
> 1. Is there interest in creating such a standard at the IETF?
>
> 2. If there is, where would be the best place to do that work? I'm
> relatively new to the IETF - I poked around Datatracker's list of
> Working Groups and there didn't seem to be one that really fit that
> well. Did I miss something? Or should this go through the IETF
> individual submission track?
>
> Please CC me on replies; I'm not subscribed.
>
> Cheers!
>
> AJ
>

--001a11c0177068d78c0549c20029
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Alex,<br><br></div>The applications area=
 uses a working group called DISPATCH to answer the question &quot;where sh=
ould this work go?&quot;, so you might start by writing up the idea as an I=
nternet draft and submitting to DISPATCH.=C2=A0 The Security area uses the =
saag list for similar discussion, if you think it is more of a security top=
ic than a usage of web push.<br><br></div>regards,<br><br></div>Ted<br><br>=
</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Mar=
 1, 2017 at 9:51 PM, Alex Jordan <span dir=3D"ltr">&lt;<a href=3D"mailto:al=
ex@strugee.net" target=3D"_blank">alex@strugee.net</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Heya!<br>
<br>
A widely deployed way to do two-factor authentication is<br>
TOTP. However, when used with an Android device Google Accounts have a<br>
really nice flow where Google will send a push notification to the<br>
Android device, which will then prompt the user with a &quot;yes/no&quot;<b=
r>
question as to whether they were trying to log in or not. From a UX<br>
perspective this is much nicer than opening an app, manually typing in<br>
a code, etc.<br>
<br>
With WebPush core having been just ratified as RFC 8030, the time<br>
seems ripe for standardizing an authentication scheme like described<br>
above.<br>
<br>
I have two questions:<br>
<br>
1. Is there interest in creating such a standard at the IETF?<br>
<br>
2. If there is, where would be the best place to do that work? I&#39;m<br>
relatively new to the IETF - I poked around Datatracker&#39;s list of<br>
Working Groups and there didn&#39;t seem to be one that really fit that<br>
well. Did I miss something? Or should this go through the IETF<br>
individual submission track?<br>
<br>
Please CC me on replies; I&#39;m not subscribed.<br>
<br>
Cheers!<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
AJ<br>
</font></span></blockquote></div><br></div>

--001a11c0177068d78c0549c20029--


From nobody Thu Mar  2 10:02:41 2017
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 9E24E1295A9; Thu,  2 Mar 2017 10:02:39 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lvC_AZW8blfD; Thu,  2 Mar 2017 10:02:37 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E8851295A8; Thu,  2 Mar 2017 10:02:37 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id i1so57749259ota.3; Thu, 02 Mar 2017 10:02:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/PwEi0pgrHRolw8ymj9DEE31KYUKF+XI3OArsTw7mQk=; b=INQQ6zfh4t0mC8cFUxmEUU4FppmJ5XH19IErS2AxbGT1wAWUK97AAWjcnAZ2xI3B/d m4aa4hUPC9SrpJoNH26ZYSTl0hL3XWzyzInWw3IPUD0Ycs704hSpztLobjZzd9WlBhWJ NU27L3E62NpSeLGMNaxT98KqnrItXF1Mrqp/ldW1XfWQ4cuOVwH5p842iIAiQacY1VgW snLdQsG33L5KMvtH4VrbDVJnN0fA7Xxrg1zRHgNMKSbLRCoFpJdIQLLrfH8YkGJicuv4 hVBtO0nfw6/hMaiL9/14dQxWOVYTCDlcOvENPT3lGeXEnfaUGQ8jg3syC/kbsisY9lGg 8/3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/PwEi0pgrHRolw8ymj9DEE31KYUKF+XI3OArsTw7mQk=; b=LTi9rJSOP03r+EY+yHq04M54f0uK28c7FWLi/PUNq0fn1nC2RdSVhvjOUhSkFicqs6 yKovoAPHCeUbObxnTtexUC0YWELocA7jF5lgnfucKkkQX8Yh8ICtu+QHw8/dwTAjxRib sLZezyNlTDwp/0eWd1a1nC+DLHkIXYcTOj3CzWMxKUGv/Ln7BXiffzOJnQR3BP+NqYE/ PYWJ9zpsftksUCk/35Q/adiYDd9fs9AT1CKmQOxgetC4nAhEsY6zURp5QkoR7R/enbRS eBdp/apCY6TCCywzHCGWi4eXkJj1QiapMean3SsbqMWPHVyDQ1wtIVtSjpK5CtZeKxNr 4rVg==
X-Gm-Message-State: AMke39lvkDs8DqgqEQgqyK6bcdhWGnhhQH7FW7xFmeYkO5kgrofMXsWWdC8pcycWQzepY8a8DDQrKLfRk2CbgA==
X-Received: by 10.157.21.82 with SMTP id z18mr8955262otz.29.1488477755903; Thu, 02 Mar 2017 10:02:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Thu, 2 Mar 2017 10:02:05 -0800 (PST)
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 2 Mar 2017 10:02:05 -0800
Message-ID: <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com>
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Content-Type: multipart/alternative; boundary=94eb2c1917a2e59ea90549c33b12
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KUeAeVZ7Rb93CQR6agFsBE7Nf8s>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 18:02:40 -0000

--94eb2c1917a2e59ea90549c33b12
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

wing are missing from the document:

> It's difficult to say how something will be used in the future.
>
> [Med] An advice that is not implementable makes more troubles, IMHO.
>
Sorry, I thought you were asking what wgs or protocols planned to reference
this.  For that, I don't know.  The intent is that it is information useful
to those considering whether restoring metadata lost to encryption in
mid-network is the right way to go.


> My intent (and the understanding of other reviewers) is to highlight that
> these mechanisms have a privacy-damaging result and that this should be
> considered.
>
> [Med] I do think existing documents already make that job. I do think we
> need more.
>
>
Sorry, did you mean "do not think we need more"?  If so, I obviously
disagree.  This design pattern is used uncritically enough that a brief
document describing why it isn't safe still seems to me useful.  Were it
incorporated into a more general document (as noted before), that would
also work.  If it later is, that more general work could obsolete this
(though that's a bid for an informational document).


>  In particularly, I'm concerned that some application functions in the
> network (e.g. recursive resolvers or proxies) do not consider the postive
> privacy implications of their aggregation and so do not consider adding
> this data back as problematic.
>
> [Med] I=E2=80=99m also concerned with that, too (see e.g.,
> http://www1.icsi.berkeley.edu/~narseo/papers/hotm42-vallinarodriguez.pdf)=
.
> In the meantime, I=E2=80=99m also concerned with (1) some applications th=
at leak
> privacy information without the consent of the user and (2) some
> application servers that may correlate various information shared by an
> application client to track users (e.g., https://panopticlick.eff.org/).
> BTW, I see that you are using =E2=80=9Capplication function=E2=80=9D whic=
h may not have the
> same meaning as the general =E2=80=9Cprotocol=E2=80=9D wording used in dr=
aft-hardie-*. Do
> you consider a DHCP relay as an =E2=80=9Capplication function=E2=80=9D?
>
>    Highlighting this enables them to see this traffic in a different
> context.
>
> [Med] Isn=E2=80=99t this already assumed by some protocol designers (e.g.=
,
> RFC6973, SIP)? BTW, there are subtleties when proxies are in the same tru=
st
> domain of the client or server.
>
> There are certainly some protocol designers that have internalized this,
but my experience has been that this is not always the case.  In a fair few
cases, folks deploy  methods like this because they see encryption of
metadata in data integrity terms or see aggregation only in terms of data
usage minimization.  They restore the metadata mid-network because it is
the quickest solution for them to get back to the status quo ante for their
understanding of the system.




> * that data may not be always available to the endhost
>
> Understood, but even in this case, it is better to make the permission to
> add the data explicit.
>
> [Med] This may be easy to implement for some applications, but this may
> not be generalized to ** all ** protocols.
>

You are certainly correct that many deployed protocols would find it hard
to retrofit this consent model into their existing flows.    This is,
however, advice for folks at the design phase.  If RFC 6788 were being
written after the publication of this document, its authors might well have
looked at the protocol mechanics in section 5.2:

   The AN
   intercepts and then tunnels the received Router Solicitation in a
   newly created IPv6 datagram with the Line-Identification Option
   (LIO).  The AN forms a new IPv6 datagram whose payload is the
   received Router Solicitation message as described in [RFC2473
<https://tools.ietf.org/html/rfc2473>],
   except that the Hop Limit field of the Router Solicitation message
   MUST NOT be decremented.

and asked whether the circuit identifier corresponding to the logical
access loop port of the AN from which the RS was initiated PII.  If so, thi=
s
document would have them consider whether transparent interception
is the appropriate choice if it is.  There clearly are flows in which
the AN's role
would be explicit.

I don't know, frankly, which choice is right in this case, but I would
prefer that
the choice be made with an easy reference to the implications of
inserting metadata
at hand.

Putting aside the interaction with a user to get a consent and how that
> consent will need to be changed when another user uses the same device to
> connect to the Internet. Consider a user who does not want an upstream DH=
PC
> relay to insert the line-id (https://tools.ietf.org/html/rfc6788) to the
> server, and let=E2=80=99s suppose the relay received a signal (by some me=
ans, to be
> yet specified) that for this particular DHCP client, the line-id must not
> be inserted. For this case, connectivity won=E2=80=99t be provided to tha=
t user.
> This would mean extra calls to the hotline for that network provider. Thi=
s
> is not desirable for both customers and network providers.
>
> I
>


> f this can be done in parallel with other actions, then the latency impac=
t
> can be minimized.
>
> [Med] These are assumptions and implications that are worth to be added t=
o
> the draft.
>

Okay, how about the following text being added to section 5.

There also tensions with latency of operation. For example, where the end
system does not initially know the information which would be added by
on-path devices, it must engage the protocol mechanisms to determine it.
Determining a public IP address to include in a locally supplied header
might require a STUN exchange, and the additional latency of this exchange
discourages deployment of host-based solutions.  To minimize this latency,
engaging those mechanisms may need to be done in parallel with or in
advance of the core protocol exchanges with which this metadata would be
supplied.



> BTW, this falls into this general discussion in
> https://tools.ietf.org/html/rfc6973:
>
>
>
>    a.  Trade-offs.  Does the protocol make trade-offs between privacy
>
>        and usability, privacy and efficiency, privacy and
>
>        implementability, or privacy and other design goals?  Describe
>
>        the trade-offs and the rationale for the design chosen.
>
> * a misbehaving node may be tempted to spoof the data to be injected. A
> remote device that will use that data to enforce policies will be broken.
>
> This point was discussed extensively in the GEOPRIV work and essentially =
a
> single carve-out was made:  for emergency services, where falsely asserte=
d
> location data could be used to SWAT individuals or consume safety
> resources.    I don't think that falls into this narrow advice, but I wou=
ld
> be willing to add something like this to the security considerations:
>
> "Note that some emergency service recipients, notably PSAPs (Public Safet=
y
> Answering Points) may prefer data provided by a network to data provided =
by
> end system, because an end system could use false data to attack others o=
r
> consume resources.   While this has the consequence that the data availab=
le
> to the PSAP is often more coarse than that available to the end system, t=
he
> risk of false data being provided involved a risk to the lives of those
> targeted."
>
> [Med] Thank you. Providing PSAP as an example is OK, but I=E2=80=99d like=
 the
> issue to be called out as a generic one while PSAP is provided as an
> example. What about the following:
>
>
>
> "Note that some servers (e.g., emergency service recipients, notably PSAP=
s
> (Public Safety Answering Points) [RFC6443]) may prefer data provided by a
> network to data provided by the end system, because an end system could u=
se
> false data to attack others or consume resources.  While this has the
> consequence that the data available to the server is often more coarse th=
an
> that available to the end system, the risk of false data being provided
> involved a risk to the lives of those targeted."
>
>
>

I don't think that emergency service recipients shifting to an example
works here, because it broadens the carve out.  In the emergency services
case, the resources consumed are fire trucks, ambulances, and swat teams.
For other servers, resources consumed could simply be  CPU cycles or disk;
that's really not the same.  Balancing location consent requirements
against one was agreed; balancing it against the other was not.



> * it was reported in the past that some browsers leak the MSISDN and othe=
r
> sensitive data.
>
> This is true, but it seems to me unrelated to the point of the document.
>
> [Med] It is related because blindly trusting an application client (and
> server) has its own privacy risks. This is even exacerbated given the ric=
h
> data that is available to an application client and also because of the
> visibility on various layers available to an application server.
>

I agree that it has its own privacy risks, but I don't think this is the
document that should explore them.

> From that flow some of your other concerns about audience, at least as I
> understand.  As written, this is narrow advice for a broad audience:
> basically, anyone who would consider the form of metadata insertion it
> describes.  You would, if I understand you, prefer a narrower description
> of the audience in a larger context.
>
>
>
> [Med] The key point here is about the practicality of implementing the
> advice NOT changing the scope. For example, the document says that it is
> better that a host is injecting the data but the document does not questi=
on
> whether that supplied data can be trusted or not,
>
>
Broadening this a bit, you're looking at two cases: one in which the data
the host has is wrong and one in which there is an adversarial
relationship.  For the first case, we can add text saying that when an end
system supplies data it is the end system's responsibility to ensure that
it is correct; don't use a STUN result from last week as fresh, for
example.   For the second case,  in which the server treats user supplied
data as potentially misleading because the user may wish to circumvent
restrictions, I'll point out the Wikimedia example demonstrates that simply
shifting the trust to a mid-point entity doesn't work; it has to be shifted
to an entity within the trust domain of the server.  So the question isn't
really "end-user system supplied data can be trusted or not", the same
question applies to whomever supplies the data.

or how the consent will be obtained from a user.

You're right that I'm leaving aside the question of how the user sets the
policies, because it may vary by protocol and type of device too much to
make general advice useful.  If you would like me to add an explicit
statement to that effect, I am happy to note that it is not covered.


>
>
> In general, the point of the document is that the host should be able to
> omit the data without mid-network devices adding it back.  That's the poi=
nt
> of protecting the traffic in the first place, after all.  I am saying tha=
t
> if the protocols require the data, then getting it from the end host has
> better privacy properties than getting from it from mid-network entities.
>
> [Med] I=E2=80=99m not sure we can have such general statement because the=
 data may
> not be available (e.g., DHCP for example) to clients + the data supplied =
by
> clients (when possible) may not be reliable + enforcing policies based on
> client-supplied data may have implication on other users (e.g., spoofing
> XFF for example). Obviously, getting some of the information from a clien=
t
> may have implications on QoE=E2=80=A6the user needs to understand the roo=
t causes
> of a degradation of QoE. Of course, these implications may not be new for
> users who are familiar with disabling Java scripts and cie.
>
>
>
> For example, the document states that the information in a Forward-For
> header can be supplied by the host itself and then communicated to a remo=
te
> consumer. This is indeed possible, but because of abusing hosts some
> servers implement whitelists to trust proxies; see
> https://meta.wikimedia.org/w/extensions/TrustedXFF/trusted-hosts.txt.
>
>
>
>
>
>
> The Wikimedia case is a very interesting one to raise, because it derives
> from a set of assumptions about the network that are somewhat flawed and
> then attempts to patch those flaws in ways that actually damage the
> mechanisms of the system they originally built.
>
> Wikimedia wants to allow folks to edit without login credentials.  This
> allows for anonymous users to make corrections or additions; this is a
> goal.  The consequence of that goal being achieved is that trolls or
> malicious editors can have at anything they want.
>
> Rather than institute credentials and ACLs, Wikimedia attempts to
> substitute blocking by IP for blocking by credential.  The property they
> are looking for in IPs is not really there, though:  they are not unique =
to
> individuals, especially over time.
>
> This damages those who share IP addresses (due to NATs or proxies).  As
> far as I can tell, the NAT problem is simply treated as collateral damage=
.
> For the proxies, they attempt to work around the damage using XFF.  That'=
s
> spoofable, though, so they attempt to limit it to specific proxies whose
> XFF they trust--many of which require logins.  That shifts the informatio=
n
> about who is editing Wikipedia out of their hands, but leaves it in the
> network and thus not truly anonymous.  I understand the engineering balan=
ce
> they are trying to strike, but I'm not sure I can recommend their solutio=
n.
>
>
>
> [Med] I=E2=80=99m not recommending their solution either, but I=E2=80=99m=
 trying to raise
> the point that an engineering balance is out there. ACKing that deploymen=
t
> reality is better than ignoring it.
>
>
>

The deployment considerations text is meant to point out the engineering
balance.  I'm happy to add the text noted above (on latency, the end user
responsibility for correct data, the PSAP carve out, and the explicit note
that the document does not treat how to obtain consent from a user so that
an end system can supply data).

I'm less happy to add language on adversarial treatment of client-supplied
data.  This is partly because many of the systems which use
network-supplied data are based on a misunderstanding of the properties of
the data being added.  It is partly because the adversarial relationship
can extend to network-supplied data.  It is also because a fair few of them
are simply security theater.  If you have a specific edit you would like to
propose, though, I will consider it.

Thanks again,

Ted

--94eb2c1917a2e59ea90549c33b12
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-size:10pt;font-family:&quot;courier ne=
w&quot;;color:black" lang=3D"EN-US">wing
 are missing from the document:</span><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lan=
g=3D"FR"><div class=3D"gmail-m_-2100246472788786888WordSection1"><div style=
=3D"border-width:medium medium medium 1.5pt;border-style:none none none sol=
id;border-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color=
 blue;padding:0cm 0cm 0cm 4pt"><div><div><div><div><div><span class=3D"gmai=
l-"><div><div><div style=3D"border-width:medium medium medium 1.5pt;border-=
style:none none none solid;border-color:-moz-use-text-color -moz-use-text-c=
olor -moz-use-text-color blue;padding:0cm 0cm 0cm 4pt"><div><div><div><div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span><div><span class=3D"gmail-">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">It&#39;s difficult to s=
ay how something will be used in the future.=C2=A0<span style=3D"color:blac=
k"><u></u><u></u></span></p>
</span><p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><span style=3D"f=
ont-size:10pt;font-family:&quot;courier new&quot;;color:black" lang=3D"EN-U=
S">[Med] An advice that is not implementable makes more troubles, IMHO.</sp=
an></p></div></div></div></div></div></div></div></div></div></blockquote><=
div>Sorry, I thought you were asking what wgs or protocols planned to refer=
ence this.=C2=A0 For that, I don&#39;t know.=C2=A0 The intent is that it is=
 information useful to those considering whether restoring metadata lost to=
 encryption in mid-network is the right way to go.<br></div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"FR"><div c=
lass=3D"gmail-m_-2100246472788786888WordSection1"><div style=3D"border-widt=
h:medium medium medium 1.5pt;border-style:none none none solid;border-color=
:-moz-use-text-color -moz-use-text-color -moz-use-text-color blue;padding:0=
cm 0cm 0cm 4pt"><div><div><div><div><div><div><span class=3D"gmail-">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><span lang=3D"EN-US">My=
 intent (and the understanding of other reviewers) is to highlight that the=
se mechanisms have a privacy-damaging result and that this should be consid=
ered.=C2=A0<span style=3D"color:black"><u></u><u></u></span></span></p>
</span><p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><span style=3D"f=
ont-size:10pt;font-family:&quot;courier new&quot;;color:black" lang=3D"EN-U=
S">[Med] I do think existing documents already make that job. I do think we=
 need more. =C2=A0=C2=A0=C2=A0<u></u><u></u></span></p><span class=3D"gmail=
-">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><span lang=3D"EN-US"></=
span></p></span></div></div></div></div></div></div></div></div></div></blo=
ckquote><div><br></div><div>Sorry, did you mean &quot;do not think we need =
more&quot;?=C2=A0 If so, I obviously disagree.=C2=A0 This design pattern is=
 used uncritically enough that a brief document describing why it isn&#39;t=
 safe still seems to me useful.=C2=A0 Were it incorporated into a more gene=
ral document (as noted before), that would also work.=C2=A0 If it later is,=
 that more general work could obsolete this (though that&#39;s a bid for an=
 informational document).<br></div><div>=C2=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div lang=3D"FR"><div class=3D"gmail-m_-21002464=
72788786888WordSection1"><div style=3D"border-width:medium medium medium 1.=
5pt;border-style:none none none solid;border-color:-moz-use-text-color -moz=
-use-text-color -moz-use-text-color blue;padding:0cm 0cm 0cm 4pt"><div><div=
><div><div><div><div><span class=3D"gmail-"><p class=3D"MsoNormal" style=3D=
"margin-bottom:12pt"><span lang=3D"EN-US">=C2=A0In particularly, I&#39;m co=
ncerned that some application functions in the network (e.g. recursive reso=
lvers or proxies) do not consider the postive privacy implications of their=
 aggregation and
 so do not consider adding this data back as problematic.<span style=3D"col=
or:black"><u></u><u></u></span></span></p>
</span><p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><span style=3D"f=
ont-size:10pt;font-family:&quot;courier new&quot;;color:black" lang=3D"EN-U=
S">[Med] I=E2=80=99m also concerned with that, too (see e.g.,
<a href=3D"http://www1.icsi.berkeley.edu/%7Enarseo/papers/hotm42-vallinarod=
riguez.pdf" target=3D"_blank">
http://www1.icsi.berkeley.edu/<wbr>~narseo/papers/hotm42-<wbr>vallinarodrig=
uez.pdf</a>). In the meantime, I=E2=80=99m also concerned with (1) some app=
lications that leak privacy information without the consent of the user and=
 (2) some application servers that may correlate various
 information shared by an application client to track users (e.g., <a href=
=3D"https://panopticlick.eff.org/" target=3D"_blank">
https://panopticlick.eff.org/</a>)<wbr>. BTW, I see that you are using =E2=
=80=9Capplication function=E2=80=9D which may not have the same meaning as =
the general =E2=80=9Cprotocol=E2=80=9D wording used in draft-hardie-*. Do y=
ou consider a DHCP relay as an =E2=80=9Capplication function=E2=80=9D?
<u></u><u></u></span></p><span class=3D"gmail-">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><span lang=3D"EN-US">=
=C2=A0=C2=A0 Highlighting this enables them to see this traffic in a differ=
ent context.<span style=3D"color:black"><u></u><u></u></span></span></p>
</span><p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><span style=3D"f=
ont-size:10pt;font-family:&quot;courier new&quot;;color:black" lang=3D"EN-U=
S">[Med] Isn=E2=80=99t this already assumed by some protocol designers (e.g=
., RFC6973, SIP)? BTW, there are subtleties when proxies are
 in the same trust domain of the client or server. =C2=A0</span><span class=
=3D"gmail-"><span lang=3D"EN-US"><br>
<br></span></span></p></div></div></div></div></div></div></div></div></div=
></blockquote><div>There are certainly some protocol designers that have in=
ternalized this, but my experience has been that this is not always the cas=
e.=C2=A0 In a fair few cases, folks deploy=C2=A0 methods like this because =
they see encryption of metadata in data integrity terms or see aggregation =
only in terms of data usage minimization.=C2=A0 They restore the metadata m=
id-network because it is the quickest solution for them to get back to the =
status quo ante for their understanding of the system.=C2=A0 <br></div><div=
><br><br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 lang=3D"FR"><div class=3D"gmail-m_-2100246472788786888WordSection1"><div s=
tyle=3D"border-width:medium medium medium 1.5pt;border-style:none none none=
 solid;border-color:-moz-use-text-color -moz-use-text-color -moz-use-text-c=
olor blue;padding:0cm 0cm 0cm 4pt"><div><div><div><div><div><div><p class=
=3D"MsoNormal" style=3D"margin-bottom:12pt"><span class=3D"gmail-"><span la=
ng=3D"EN-US">
</span><span style=3D"font-size:10pt;font-family:&quot;courier new&quot;;co=
lor:black" lang=3D"EN-US">* that data may not be always available to the en=
dhost</span><span lang=3D"EN-US"><u></u><u></u></span></span></p>
</div>
<div><span class=3D"gmail-">
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;aria=
l&quot;,&quot;sans-serif&quot;;color:black" lang=3D"EN-US">Understood, but =
even in this case, it is better to make the permission to add the data expl=
icit.</span><span style=3D"font-size:10pt;font-family:&quot;arial&quot;,&qu=
ot;sans-serif&quot;;color:black" lang=3D"EN-US"><u></u><u></u></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&qu=
ot;courier new&quot;;color:black" lang=3D"EN-US">[Med] This may be easy to =
implement for some applications, but this may not be generalized to ** all =
** protocols. </span></p></div></div></div></div></div></div></div></div></=
div></blockquote><div><br></div><div>You are certainly correct that many de=
ployed protocols would find it hard to retrofit this consent model into the=
ir existing flows.=C2=A0=C2=A0=C2=A0 This is, however, advice for folks at =
the design phase.=C2=A0 If RFC 6788 were being written after the publicatio=
n of this document, its authors might well have looked at the protocol mech=
anics in section 5.2:<br><br><pre class=3D"gmail-newpage">   The AN
   intercepts and then tunnels the received Router Solicitation in a
   newly created IPv6 datagram with the Line-Identification Option
   (LIO).  The AN forms a new IPv6 datagram whose payload is the
   received Router Solicitation message as described in [<a href=3D"https:/=
/tools.ietf.org/html/rfc2473" title=3D"&quot;Generic Packet Tunneling in IP=
v6 Specification&quot;">RFC2473</a>],
   except that the Hop Limit field of the Router Solicitation message
   MUST NOT be decremented.<br><br></pre><pre class=3D"gmail-newpage">and a=
sked whether the circuit identifier corresponding to the logical <br>access=
 loop port of the AN from which the RS was initiated PII.  If so, this<br>d=
ocument would have them consider whether transparent interception <br>is th=
e appropriate choice if it is.  There clearly are flows in which the AN&#39=
;s role <br>would be explicit.<br><br></pre><pre class=3D"gmail-newpage">I =
don&#39;t know, frankly, which choice is right in this case, but I would pr=
efer that<br>the choice be made with an easy reference to the implications =
of inserting metadata<br>at hand. <br></pre></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div lang=3D"FR"><div class=3D"gmail-m_-2100246472=
788786888WordSection1"><div style=3D"border-width:medium medium medium 1.5p=
t;border-style:none none none solid;border-color:-moz-use-text-color -moz-u=
se-text-color -moz-use-text-color blue;padding:0cm 0cm 0cm 4pt"><div><div><=
div><div><div><div><p class=3D"MsoNormal"><span style=3D"font-size:10pt;fon=
t-family:&quot;courier new&quot;;color:black" lang=3D"EN-US">Putting aside =
the interaction with a user
 to get a consent and how that consent will need to be changed when another=
 user uses the same device to connect to the Internet. Consider a user who =
does not want an upstream DHPC relay to insert the line-id (<a href=3D"http=
s://tools.ietf.org/html/rfc6788" target=3D"_blank">https://tools.ietf.org/h=
tml/<wbr>rfc6788</a>)
 to the server, and let=E2=80=99s suppose the relay received a signal (by s=
ome means, to be yet specified) that for this particular DHCP client, the l=
ine-id must not be inserted. For this case, connectivity won=E2=80=99t be p=
rovided to that user. This would mean extra calls
 to the hotline for that network provider. This is not desirable for both c=
ustomers and network providers.
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black" lang=3D"EN-US"></span></p><p class=3D"MsoNormal"=
><span style=3D"font-size:10pt;font-family:&quot;courier new&quot;;color:bl=
ack" lang=3D"EN-US"></span></p><span class=3D"gmail-">
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;aria=
l&quot;,&quot;sans-serif&quot;;color:black" lang=3D"EN-US">I</span></p></sp=
an></div></div></div></div></div></div></div></div></div></blockquote><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"=
FR"><div class=3D"gmail-m_-2100246472788786888WordSection1"><div style=3D"b=
order-width:medium medium medium 1.5pt;border-style:none none none solid;bo=
rder-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color blue=
;padding:0cm 0cm 0cm 4pt"><div><div><div><div><div><div><span class=3D"gmai=
l-"><p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;=
arial&quot;,&quot;sans-serif&quot;;color:black" lang=3D"EN-US">f this can b=
e done in parallel with other actions, then the latency impact can be minim=
ized.</span><span style=3D"font-size:10pt;font-family:&quot;arial&quot;,&qu=
ot;sans-serif&quot;" lang=3D"EN-US"><u></u><u></u></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&qu=
ot;courier new&quot;;color:black" lang=3D"EN-US">[Med] These are assumption=
s and implications that are worth to be added to the draft.</span></p></div=
></div></div></div></div></div></div></div></div></blockquote><div><br></di=
v><div>Okay, how about the following text being added to section 5.<br><br>=
</div><div>There also tensions with latency of operation. For example, wher=
e the end system does not initially know the information which would be add=
ed by on-path devices, it must engage the protocol mechanisms to determine =
it.=C2=A0 Determining a public IP address to include in a locally supplied =
header might require a STUN exchange, and the additional latency of this ex=
change discourages deployment of host-based solutions.=C2=A0 To minimize th=
is latency, engaging those mechanisms may need to be done in parallel with =
or in advance of the core protocol exchanges with which this metadata would=
 be supplied.<br><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div lang=3D"FR"><div class=3D"gmail-m_-2100246472788786=
888WordSection1"><div style=3D"border-width:medium medium medium 1.5pt;bord=
er-style:none none none solid;border-color:-moz-use-text-color -moz-use-tex=
t-color -moz-use-text-color blue;padding:0cm 0cm 0cm 4pt"><div><div><div><d=
iv><div><div><p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-fami=
ly:&quot;courier new&quot;;color:black" lang=3D"EN-US"> BTW, this falls int=
o this general discussion in
<a href=3D"https://tools.ietf.org/html/rfc6973" target=3D"_blank">https://t=
ools.ietf.org/html/<wbr>rfc6973</a>:
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;" lang=3D"EN-US">=C2=A0=C2=A0 a.=C2=A0 Trade-offs.=C2=A0 Does =
the protocol make trade-offs between privacy<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;" lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and usab=
ility, privacy and efficiency, privacy and<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;" lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 implemen=
tability, or privacy and other design goals?=C2=A0 Describe<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;" lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the trad=
e-offs and the rationale for the design chosen.<u></u><u></u></span></p>
</div><span class=3D"gmail-">
<blockquote style=3D"border-width:medium medium medium 1pt;border-style:non=
e none none solid;border-color:-moz-use-text-color -moz-use-text-color -moz=
-use-text-color rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;=
margin-right:0cm">
<div>
<div>
<div style=3D"border-width:medium medium medium 1.5pt;border-style:none non=
e none solid;border-color:-moz-use-text-color -moz-use-text-color -moz-use-=
text-color blue;padding:0cm 0cm 0cm 4pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><span style=3D"font-siz=
e:10pt;font-family:&quot;courier new&quot;;color:black" lang=3D"EN-US">* a =
misbehaving node may be tempted to spoof the data to be injected. A remote =
device that will use that
 data to enforce policies will be broken.</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">This point was discusse=
d extensively in the GEOPRIV work and essentially a single carve-out was ma=
de:=C2=A0 for emergency services, where falsely asserted location data coul=
d be used to SWAT individuals or consume
 safety resources.=C2=A0=C2=A0=C2=A0 I don&#39;t think that falls into this=
 narrow advice, but I would be willing to add something like this to the se=
curity considerations:<u></u><u></u></p>
</div>
</span><div><span class=3D"gmail-">
<p class=3D"MsoNormal">&quot;Note that some emergency service recipients, n=
otably PSAPs (Public Safety Answering Points) may prefer data provided by a=
 network to data provided by end system, because an end system could use fa=
lse data to attack others or consume resources.=C2=A0=C2=A0
 While this has the consequence that the data available to the PSAP is ofte=
n more coarse than that available to the end system, the risk of false data=
 being provided involved a risk to the lives of those targeted.&quot;<u></u=
><u></u></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&qu=
ot;courier new&quot;;color:black" lang=3D"EN-US">[Med] Thank you. Providing=
 PSAP as an example is OK, but I=E2=80=99d like the issue to be called out =
as a generic one while PSAP is provided as an example. What about
 the following: <u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&quot;Note that some servers (e=
.g., emergency service recipients, notably PSAPs (Public Safety Answering P=
oints) [RFC6443]) may prefer data provided by a network to data provided by=
 the end system, because an end system could
 use false data to attack others or consume resources.=C2=A0 While this has=
 the consequence that the data available to the server is often more coarse=
 than that available to the end system, the risk of false data being provid=
ed involved a risk to the lives of those
 targeted.&quot;</span><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black" lang=3D"EN-US">
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0</span></p></div></d=
iv></div></div></div></div></div></div></div></blockquote><div><br></div><d=
iv>I don&#39;t think that emergency service recipients shifting to an examp=
le works here, because it broadens the carve out.=C2=A0 In the emergency se=
rvices case, the resources consumed are fire trucks, ambulances, and swat t=
eams.=C2=A0 For other servers, resources consumed could simply be=C2=A0 CPU=
 cycles or disk; that&#39;s really not the same.=C2=A0 Balancing location c=
onsent requirements against one was agreed; balancing it against the other =
was not.<br><br>=C2=A0 <br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div lang=3D"FR"><div class=3D"gmail-m_-2100246472788786888WordSect=
ion1"><div style=3D"border-width:medium medium medium 1.5pt;border-style:no=
ne none none solid;border-color:-moz-use-text-color -moz-use-text-color -mo=
z-use-text-color blue;padding:0cm 0cm 0cm 4pt"><div><div><div><div><div><di=
v><p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;co=
urier new&quot;;color:black" lang=3D"EN-US"><u></u></span></p>
</div><span class=3D"gmail-">
<blockquote style=3D"border-width:medium medium medium 1pt;border-style:non=
e none none solid;border-color:-moz-use-text-color -moz-use-text-color -moz=
-use-text-color rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;=
margin-right:0cm">
<div>
<div>
<div style=3D"border-width:medium medium medium 1.5pt;border-style:none non=
e none solid;border-color:-moz-use-text-color -moz-use-text-color -moz-use-=
text-color blue;padding:0cm 0cm 0cm 4pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><span style=3D"font-siz=
e:10pt;font-family:&quot;courier new&quot;;color:black" lang=3D"EN-US">* it=
 was reported in the past that some browsers leak the MSISDN and other sens=
itive data.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">This is true, but </span>it see=
ms to me unrelated to the point of the document.<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black" lang=3D"EN-US">[Med] It is related because blind=
ly trusting an application client (and server) has its own privacy risks. T=
his is even exacerbated given the rich data that
 is available to an application client and also because of the visibility o=
n various layers available to an application server.
</span><span lang=3D"EN-US">=C2=A0</span></p></div></div></div></div></div>=
</div></div></div></div></blockquote><div><br></div><div>I agree that it ha=
s its own privacy risks, but I don&#39;t think this is the document that sh=
ould explore them. <br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div lang=3D"FR"><div class=3D"gmail-m_-2100246472788786888WordSection1=
"><div style=3D"border-width:medium medium medium 1.5pt;border-style:none n=
one none solid;border-color:-moz-use-text-color -moz-use-text-color -moz-us=
e-text-color blue;padding:0cm 0cm 0cm 4pt"><div><div><div><div><div><div><p=
 class=3D"MsoNormal"><span lang=3D"EN-US"><u></u><u></u></span></p>
</div><span class=3D"gmail-">
<blockquote style=3D"border-width:medium medium medium 1pt;border-style:non=
e none none solid;border-color:-moz-use-text-color -moz-use-text-color -moz=
-use-text-color rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;=
margin-right:0cm">
<div>
<div>
<div style=3D"border-width:medium medium medium 1.5pt;border-style:none non=
e none solid;border-color:-moz-use-text-color -moz-use-text-color -moz-use-=
text-color blue;padding:0cm 0cm 0cm 4pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">From that flow some of your oth=
er concerns about audience, at least as I understand.=C2=A0 As written</spa=
n>, this is narrow advice for a broad audience: basically,
 anyone who would consider the form of metadata insertion it describes.=C2=
=A0 You would, if I understand you, prefer a narrower description of the au=
dience in a larger context.=C2=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black" lang=3D"EN-US">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black" lang=3D"EN-US">[Med] The key point here is about=
 the practicality of implementing the advice NOT changing the
 scope. For example, the document says that it is better that a host is inj=
ecting the data but the document does not question whether that supplied da=
ta can be trusted or not,</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u></p></div></span></div></div></div></div></di=
v></div></div></div></blockquote><div><br></div><div>Broadening this a bit,=
 you&#39;re looking at two cases: one in which the data the host has is wro=
ng and one in which there is an adversarial relationship.=C2=A0 For the fir=
st case, we can add text saying that when an end system supplies data it is=
 the end system&#39;s responsibility to ensure that it is correct; don&#39;=
t use a STUN result from last week as fresh, for example.=C2=A0=C2=A0 For t=
he second case,=C2=A0 in which the server treats user supplied data as pote=
ntially misleading because the user may wish to circumvent restrictions, I&=
#39;ll point out the Wikimedia example demonstrates that simply shifting th=
e trust to a mid-point entity doesn&#39;t work; it has to be shifted to an =
entity within the trust domain of the server.=C2=A0 So the question isn&#39=
;t really &quot;end-user system supplied data can be trusted or not&quot;, =
the same question applies to whomever supplies the data.<br><br><span class=
=3D"gmail-"><span style=3D"font-size:10pt;font-family:&quot;courier new&quo=
t;;color:black" lang=3D"EN-US"> or how the consent will be obtained from a =
user.</span></span><br><br>You&#39;re right that I&#39;m leaving aside the =
question of how the user sets the policies, because it may vary by protocol=
 and type of device too much to make general advice useful.=C2=A0 If you wo=
uld like me to add an explicit statement to that effect, I am happy to note=
 that it is not covered. =C2=A0 <br></div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div lang=3D"FR"><div class=3D"gmail-m_-2=
100246472788786888WordSection1"><div style=3D"border-width:medium medium me=
dium 1.5pt;border-style:none none none solid;border-color:-moz-use-text-col=
or -moz-use-text-color -moz-use-text-color blue;padding:0cm 0cm 0cm 4pt"><d=
iv><div><div><div><div><span class=3D"gmail-"><div><p class=3D"MsoNormal">=
=C2=A0<u></u></p>
</div>
</span><div><span class=3D"gmail-">
<p class=3D"MsoNormal">In general, the point of the document is that the ho=
st should be able to omit the data without mid-network devices adding it ba=
ck.=C2=A0 That&#39;s the point of protecting the traffic in the first place=
, after all.=C2=A0 I am saying that if the protocols
 require the data, then getting it from the end host has better privacy pro=
perties than getting from it from mid-network entities.<u></u><u></u></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&qu=
ot;courier new&quot;;color:black" lang=3D"EN-US">[Med] I=E2=80=99m not sure=
 we can have such general statement because the data may not be available (=
e.g., DHCP for example) to clients + the data supplied by clients
 (when possible) may not be reliable + enforcing policies based on client-s=
upplied data may have implication on other users (e.g., spoofing XFF for ex=
ample). Obviously, getting some of the information from a client may have i=
mplications on QoE=E2=80=A6the user needs
 to understand the root causes of a degradation of QoE. Of course, these im=
plications may not be new for users who are familiar with disabling Java sc=
ripts and cie. =C2=A0<u></u><u></u></span></p>
</div><span class=3D"gmail-">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<blockquote style=3D"border-width:medium medium medium 1pt;border-style:non=
e none none solid;border-color:-moz-use-text-color -moz-use-text-color -moz=
-use-text-color rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;=
margin-right:0cm">
<div>
<div>
<div style=3D"border-width:medium medium medium 1.5pt;border-style:none non=
e none solid;border-color:-moz-use-text-color -moz-use-text-color -moz-use-=
text-color blue;padding:0cm 0cm 0cm 4pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black" lang=3D"EN-US">For example, the document states =
that the information in a Forward-For header can be supplied by
 the host itself and then communicated to a remote consumer. This is indeed=
 possible, but because of abusing hosts some servers implement whitelists t=
o trust proxies; see
<a href=3D"https://meta.wikimedia.org/w/extensions/TrustedXFF/trusted-hosts=
.txt" target=3D"_blank">
https://meta.wikimedia.org/w/<wbr>extensions/TrustedXFF/trusted-<wbr>hosts.=
txt</a>. =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">The Wikimedia case is a=
 very interesting one to raise, because it derives from a set of assumption=
s about the network that are somewhat flawed and then attempts to patch tho=
se flaws in ways that actually damage
 the mechanisms of the system they originally built.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">Wikimedia wants to allo=
w folks to edit without login credentials.=C2=A0 This allows for anonymous =
users to make corrections or additions; this is a goal.=C2=A0 The consequen=
ce of that goal being achieved is that trolls
 or malicious editors can have at anything they want.<u></u><u></u></p>
</div>
</span><div><span class=3D"gmail-">
<p class=3D"MsoNormal">Rather than institute credentials and ACLs, Wikimedi=
a attempts to substitute blocking by IP for blocking by credential.=C2=A0 T=
he property they are looking for in IPs is not really there, though:=C2=A0 =
they are not unique to individuals, especially
 over time.=C2=A0 <br>
<br>
This damages those who share IP addresses (due to NATs or proxies).=C2=A0 A=
s far as I can tell, the NAT problem is simply treated as collateral damage=
.=C2=A0 For the proxies, they attempt to work around the damage using XFF.=
=C2=A0 That&#39;s spoofable, though, so they attempt
 to limit it to specific proxies whose XFF they trust--many of which requir=
e logins.=C2=A0 That shifts the information about who is editing Wikipedia =
out of their hands, but leaves it in the network and thus not truly anonymo=
us.=C2=A0 I understand the engineering balance
 they are trying to strike, but I&#39;m not sure I can recommend their solu=
tion.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;cour=
ier new&quot;;color:black"><u></u>=C2=A0<u></u></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&qu=
ot;courier new&quot;;color:black" lang=3D"EN-US">[Med] I=E2=80=99m not reco=
mmending their solution either, but I=E2=80=99m trying to raise the point t=
hat an engineering balance is out there. ACKing that deployment reality
 is better than ignoring it. <u></u><u></u></span></p>
</div><div><div class=3D"gmail-h5">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span><br></p></div></di=
v></div></div></div></div></div></div></div></div></div></blockquote></div>=
<br></div><div class=3D"gmail_extra">The deployment considerations text is =
meant to point out the engineering balance.=C2=A0 I&#39;m happy to add the =
text noted above (on latency, the end user responsibility for correct data,=
 the PSAP carve out, and the explicit note that the document does not treat=
 how to obtain consent from a user so that an end system can supply data).=
=C2=A0 <br><br></div><div class=3D"gmail_extra">I&#39;m less happy to add l=
anguage on adversarial treatment of client-supplied data.=C2=A0 This is par=
tly because many of the systems which use network-supplied data are based o=
n a misunderstanding of the properties of the data being added.=C2=A0 It is=
 partly because the adversarial relationship can extend to network-supplied=
 data.=C2=A0 It is also because a fair few of them are simply security thea=
ter.=C2=A0 If you have a specific edit you would like to propose, though, I=
 will consider it.<br><br></div><div class=3D"gmail_extra">Thanks again,<br=
><br></div><div class=3D"gmail_extra">Ted<br></div></div>

--94eb2c1917a2e59ea90549c33b12--


From nobody Thu Mar  2 11:03:36 2017
Return-Path: <willi.uebelherr@riseup.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 AA7B91295D2 for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 11:03:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEslPHkGzV7q for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 11:03:33 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 848401295FC for <ietf@ietf.org>; Thu,  2 Mar 2017 11:03:33 -0800 (PST)
Received: from cotinga.riseup.net (unknown [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id B5C281A260B; Thu,  2 Mar 2017 19:03:31 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488481412; bh=YFvp4ymG1sGJiRClHgt802D5Cut22BWYfpj7bi7LP2M=; h=Subject:References:From:To:Cc:Date:In-Reply-To:From; b=n8FKyJ4j6sNapToqB+1zi1v+cEO71MySmsr7MtgpiKOl4oebzIzI4HCjB/N2h5eJu dlV91r+o5d5aVeL+2me88kqRCBB+6eyFmznGvujtIo7nQkemF0Ew+DVfHNUQpQwmJr Uq3jy9uXYe+Bfx+lb9yypojROlf/RnCMu6kGAsRo=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id A15FC41B3C
Subject: Re: [Mailman-Users] Fwd: Re: Mailing list membership.
References: <22711.59414.243751.688266@turnbull.sk.tsukuba.ac.jp>
From: willi uebelherr <willi.uebelherr@riseup.net>
To: IETF discussion <ietf@ietf.org>
X-Forwarded-Message-Id: <22711.59414.243751.688266@turnbull.sk.tsukuba.ac.jp>
Message-ID: <6f6dffc4-6a6b-210f-a20f-22ebb4e14c45@riseup.net>
Date: Thu, 2 Mar 2017 16:03:02 -0300
MIME-Version: 1.0
In-Reply-To: <22711.59414.243751.688266@turnbull.sk.tsukuba.ac.jp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/V-trL0quzNMEUHFkAitKqJzQETg>
Cc: "Stephen J. Turnbull" <turnbull.stephen.fw@u.tsukuba.ac.jp>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 19:03:35 -0000

Dear friends,

this is the answer from Stephen J. Turnbull from the Tsukuba University 
in Japan. A very detailed contribution to our DMARC discussion.

many thanks to all and greetings, willi


-------- Forwarded Message --------
Subject: [Mailman-Users] Fwd: Re: Mailing list membership.
Date: Thu, 2 Mar 2017 18:38:30 +0900
From: Stephen J. Turnbull <turnbull.stephen.fw@u.tsukuba.ac.jp>
To: willi uebelherr <willi.uebelherr@gmail.com>
CC: mailman-users@python.org

willi uebelherr writes:

  > Dear friends of Mailman,

Thanks for getting in touch!

  > in the IETF discussion list we have a discussion about the bounces, 
that  > are created based on the DMARC processing.
  >  > I know, from a discussion in this mailman list, that mailman 
follow  > strong the RFC 2821 (SMTP) and reject this DMARC nonsense.

RFC 2821 has little practical significance for DMARC.  DMARC
processing itself has very little to do with SMTP (except for the
indirect relation through SPF -- more about that below).  I have all
the respect in the world for Ted T'so, but he seems to be not very
familiar with DMARC, DKIM, and SPF.

Mailman can not and does not "reject" DMARC in any way (although some
Mailman developers are pretty unhappy about it ;-).  DMARC is a fact
of life for mailing lists now.

First, the good news:
I (as a representative of the GNU Mailman project, as well as for
personal interest) have been participating in the DMARC discussions as
well as in development of the new "Authenticated Received Chain" (ARC)
protocol.  ARC allows an intermediate site to cryptographically sign
its authentication results, which (we hope) will allow end receivers
to trust those for DMARC purposes.  However widespread implementation
is at least a year off (theoretically possible as the DMARC
Consortium, Google, Yahoo!, and AOL are all participating in ARC
discussions, but you know how the Internet moves).

Mailman 3 itself will be ARC-capable in limited ways in that time
frame, and we expect Postfix, Exim, and Sendmail to implement it as
well.  (The "big guys" use MTAs developed in-house.)

Now, the bad news.

  > The consequence should be, that the members in the list should 
change  > her mailbox servers to avoid this "bounce errors", based on 
DMARC  > processing, or not?

>From the list owner's point of view, "it would be nice if" posters
would post from DMARC "p=none" domains.  ("p=none" includes sites
which have no DMARC DNS record at all; it is the implicit default that
DMARC receivers must assume.)  However, in the great majority of
cases, users get very upset about being asked to use "p=none"
mailboxes if that means changing their workflows.  IETF mailing lists
*may* be an exception, but I suspect there are a lot of people using
Yahoo! and other DMARC-protected addresses in the IETF subscriber base.

  > For me, i don't like any form of work arounds. We need a clear
  > base. And this can only be the standard RFCs.

Unfortunately, there are no RFCs that help here.  DMARC is *intended*
to prevent "unwanted" indirect mail flows, and unfortunately the
heuristic chosen also will interdict mailing lists.  What the DMARC
RFC *should* say is "if your mailbox provider posts a DMARC policy
other than 'p=none', that is automatically a policy of prohibiting
posting to mailing lists".  And that is precisely why the DMARC RFC is
"Informative", rather than "Standards Track", as you would expect with
an RFC with so much promise for reducing phishing and other mail
abuse.  The DMARC Consortium really wanted to avoid any language that
would implicate DMARC users is negative effects of the standard, and
an informative RFC allowed the Consortium members to retain control.

The only RFC-conforming option that allows you to avoid triggering
DMARC backscatter is to turn off ALL message-modifying options:
subject tags and serial numbers, and body headers and footers.  (I
believe that is currently the complete list of Mailman features that
invalidate common DKIM signatures.)

Other than that, your choice is to turn your "p!=none" posters into
backscatter bombs, or use of one of the options that Mailman provides
to avoid triggering DMARC.  There are more, and more attractive,
options in the most recent Mailman 2 versions (at least 2.1.20), as
Jim Popovich mentioned.

I hope this helps.

Below some comments on technical aspects of the appended
correspondence.


  > 3) The IETF discussion list don't follow the DMARC processing. This 
 > means, it act only outside.

DMARC processing, by which I mean the protocols defined in RFC 7489,
is in no way done by mailing lists.  Anything that a mailing list or
its MTA does to handle DMARC is a "workaround".  (This will change
with ARC, but ARC will provide no guarantees -- use of ARC is entirely
optional for the receivers.)

  > I understand and agree absolutly, that the maillist server never 
change  > the From-line in the header.

Changing the From field in the RFC 2822 header is the most popular
workaround by far.  This is not a denial of your position, it's a
statement of current common practice.

  > The mailman maillist server use bounce-counters for every member and 
  > some limits for this bounce-counter. If the limit exceeds, and the 
 > admin-group do nothing, then the maillist server mailman disable the 
 > delivery. It is not an unsubscription.

Under some setting of the bounce processing in Mailman, it *can*
result in unsubscription.

  > The DMARC processing is defined in the DNS info. But we can ignore 
it,  > or not?

If you ignore it, your list(s) will be subject to adverse consequences
based on DMARC processing at poster and subscriber addresses.  That's
your choice, of course.

  > Based on that process, we can clean all this nonsense in our IETF
  > lists environment and work strong based on the RFC 2821, like
  > mailman do it.

As Jim Popovich mentioned, the IETF lists are handled by GNU Mailman.
According to the most recent message I received it is Mailman 2.1.18.

Ted T'so writes:

  > > RFC 2821, Simple Mail Transfer Protocol, section 3.10.2
  > >
  > >    "To expand a list, the recipient mailer replaces the
  > >    pseudo-mailbox address in the envelope with all of the expanded
  > >    addresses.  The return address in the envelope is changed so 
that all
  > >    error messages generated by the final deliveries will be 
returned to
  > >    a list administrator, not to the message originator, who generally
  > >    has no control over the contents of the list and will typically 
find
  > >    error messages annoying."
  > >
  > > This is the SMTP Envelope From field.  The FROM field is not changed,
  > > but the SMTP return address is changed, so that bounces go to the
  > > mailing list administrator as opposed to the person who sends mail to
  > > the mailing list.

This is true, but it is not part of the definition of mailing list,
nor is there any popular mailing list software left that doesn't give
you the option of fiddling with the FROM field (for several reasons
such as anonymization, as well as working around DMARC).

  > > Unfortunately, if you are using a system whose domain requests that
  > > all recipients enforce DMARC alignment, this specifically instructs
  > > recipients to bounce mail if the SMTP Envelope return address doesn't
  > > match the FROM field in the header.

This is a misunderstanding of the DMARC protocol.  I won't go into
details, but in practice the vast majority of originating domains use
DKIM as well as, or instead of, SPF.[1]  In the case of DKIM
verification, the authorizing domain is the one claimed in the
DKIM-Signature field, not the Envelope From.

  > > Hence mailing list systems that enforce DMARC, or request DMARC
  > > processing, are fundamentally incompatible with mailing lists as
  > > defined by section 3.10.2 of RFC 2821.

This is false.  In practice, a mailing list that does not alter the
From, Subject, Date, and Message-ID header fields and does not alter
the body is compatible with DMARC originators which provide DKIM
signatures.  That's pretty much all of them, as mentioned above.

As I mention above, Mailman can be configured that way, but it rarely
is.  A few list-owners run into legal issues where the list must
provide visible legal disclaimers or unsubscription instructions,
which typically occur in footers appended to the message body,
invalidating the DKIM signature.  I doubt such a legal requirement
applies to the IETF lists, however.

Hope this helps.

Steve


Footnotes: [1]  According to a source at DMARC Consortium, their analysis
shows that nearly 100% (I forget the exact figure) of p=reject
traffic is DKIM-signed.  Of course that's heavily weighted by Yahoo!
and AOL, the two biggest sources of p=reject traffic.

-- 
Associate Professor              Division of Policy and Planning Science
http://turnbull/sk.tsukuba.ac.jp/     Faculty of Systems and Information
Email: turnbull@sk.tsukuba.ac.jp                   University of Tsukuba
Tel: 029-853-5175                 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN


From nobody Thu Mar  2 11:40:46 2017
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 38B681295C1 for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 11:40:44 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBhpDrlT2H2w for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 11:40:42 -0800 (PST)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C18DE1295A8 for <ietf@ietf.org>; Thu,  2 Mar 2017 11:40:42 -0800 (PST)
Received: by mail-qk0-x22a.google.com with SMTP id s186so140869976qkb.1 for <ietf@ietf.org>; Thu, 02 Mar 2017 11:40:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sni67oynTKVx4hgpOCaTStZ/eElA+sBXYMDjtoLxDH4=; b=agP+ja4mvFiVwk9Hx0h6lOxr2YmW3Ih6ln/Ojod1JciVSxQqLF7dANrPdjCtAbhVsa ucbqV156LtqM57WpS6e6OMweTU7m+mHqTVOiZC+Arh7DDPw9E0qfvn4x3miezvIVASuF iAdi5E3AmbL4SkFIqLlRmqsELtl7wPeWOpePB/EM4L2SW/45Yy4MBDYxuYxDL+EsVciD AyiHgl1+n68cfK4+ExDeEOX5NzL4xJdIrg1C0v5Ul7gHrgof/MQqs1VgiS4/6S5SGvA+ v0m7/VngHr81ENbsMCrmPtEoik26B7Au9WFJaJVT5BKfcei9R52CDvdG7IxcaFFA1LLC ngVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sni67oynTKVx4hgpOCaTStZ/eElA+sBXYMDjtoLxDH4=; b=PNr4gQCtABJmLmb7qJTXUeil1SCdVLSsiXswgXjvWGZNLlhLfd/gm4a55L7eehK4bj 38P/fG9PSEyJfvcSVISdv6cDax9LwlwachZAhihyE+EoLiqepYY+m/yVQAdUn46w28jr Vs5Gm8ULK8NcTmTYSm7JsWnC12S+xBtYPdS+/FgReV7HkSFoSWQAPKf8J69SKQ5Oo3I1 QBtsPYQNY0b7toVnPoLVRVcA1anrwetCZC8ZgNZXFh5dQdm+RPmzvIF3hj5JZfnvyW94 9qcbe7plzvtV/xc1H3rcfU3gk5Bv7He0r0MK5L96FbKiD9fa+splZ/dREgeH8lgH4ttz W5yQ==
X-Gm-Message-State: AMke39nXyvdyAgeU3RzsVSvIXlMJJky2vrgogd+XUeRAnNcw172SCjztY4XgT3OmWDx/aBHwLLCAQF7W9xPOntY+
X-Received: by 10.237.34.212 with SMTP id q20mr19525101qtc.5.1488483641415; Thu, 02 Mar 2017 11:40:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.169.4 with HTTP; Thu, 2 Mar 2017 11:40:10 -0800 (PST)
In-Reply-To: <14476.1488384266@obiwan.sandelman.ca>
References: <14476.1488384266@obiwan.sandelman.ca>
From: Warren Kumari <warren@kumari.net>
Date: Thu, 2 Mar 2017 14:40:10 -0500
Message-ID: <CAHw9_iKuZrxD=51QadPPnuofUdAeaHPQ4JvONz5Bno3HTAi71A@mail.gmail.com>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3q_9NDSa7mCNUJoogSGdEBd70yo>
Cc: "ietf@ietf.org Disgust" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 19:40:44 -0000

I've worked with a number of different authors, and there does seem to
be a wide range of preferences.

I personally like to publish early, and often; I'll often publish a
new version integrating just one persons comments (or, of they are
nits, batch up a few sets into one version). If there are lots of
comments going back and forth, I don't think it is easy for WG
participants to mentally keep track of all the different comments, how
they interrelate, and what the final text will look like. I also think
that it is politer to respond to feedback by integrating and
publishing a new version, instead of just saying "Thanks, I'll get to
them sometime....".
Committing to GitHub kinda accomplishes this, but a: it's harder for
participants to find, and b: the github version is a second class
citizen.

But, other authors seem to have a different view -- they'd much rather
get everything fully squared away, all comments addressed, all 't's
crossed and 'i's dotted.


One of the stickier points is what to do during WGLC -- unfortunately,
in many groups this is where the majority of the review and feedback
happens, and it is often viewed as poor form to revise during WGLC.
It's often hard for the *authors* to keep track of what the consensus
is when there are lots of comments, what the new text would look like,
etc -- expecting random WG participants to do so is (IMO) unreasonable
and leads to frustration and overlapping comments. I'd personally
rather publish new versions *during WGLC* saying "This is what this
looks like now, does this address your issues?" than trying to explain
that we will move text from Section 3.2.5.4.3 bullet 9 to Section
1.7.4 to address Mike's comment, but that will mean that Billy's
comments no longer apply because it removes the text that he's
commenting on, other than the nits about the case of the acronym,
which we agreed to change globally, except in section 8, because it is
quoting from another RFC. Confused yet?

W

On Wed, Mar 1, 2017 at 11:04 AM, Michael Richardson
<mcr+ietf@sandelman.ca> wrote:
>
> For the third time in two days I find myself, when asking others for opinions
> about some text, pointing at github commit logs.  With the beautiful
> makefiles we often have, one can't even depend upon having a formatted .txt
> version there!
>
> This is not a rant for or against git or github, but rather about what I
> perceive as a shyness about posting intermediate versions of Internet Drafts
> to the datatracker.
>
> I understand that in academia, they never like letting half-baked ideas out,
> and so the -00 that we see from academics are often overdue and overly
> polished.  I know I can't fight that, but at least the -01, etc. could be
> issued faster?
>
> I've even heard some push back from people along the lines of, "wow, that ID
> has 27 revisions, is it really stable?", and my feelings have often been more
> along the lines of, "wow, that revision has 27 revisions, the authors are
> really keen and responsive".
>
> I appreciate for some reviewers that having more revisions implies that they
> think they have to look at the text more often.
>
> But given the diff utilities, it shouldn't matter how many revisions there
> were before times you look, as you can just skip the intermediate versions.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Thu Mar  2 12:09:26 2017
Return-Path: <willi.uebelherr@riseup.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 12C561295C1 for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 12:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y90BgoKEMZXn for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 12:09:24 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43DEA1295A9 for <ietf@ietf.org>; Thu,  2 Mar 2017 12:09:24 -0800 (PST)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id DA75A1A26FC for <ietf@ietf.org>; Thu,  2 Mar 2017 20:09:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488485363; bh=h0nMPFBu+SfTv1ds/KmxiTPtZbrFaEva4t0BhhdK0c8=; h=Subject:To:References:From:Date:In-Reply-To:From; b=cdncg81gQK2Sw+t1IwKxGqs/l/zQTf2PBMBy5jNZup8eBtujULfj6o10K2U+dmwrM 3Cb71koeH7HW8+UdYQCa5J6zeGOYQ/QwCSuClLm8WPqnZfRChD2wtSBCscVA2NNYSv YCe4FIbduWSefX+QA+gvGIjx8liPMdQNlNYjOZX0=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id 30B7E1C00AD
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
To: ietf@ietf.org
References: <20170301210033.1672.qmail@ary.lan>
From: willi uebelherr <willi.uebelherr@riseup.net>
Message-ID: <1628e89a-349c-6fd9-f267-31a08d652811@riseup.net>
Date: Thu, 2 Mar 2017 17:08:55 -0300
MIME-Version: 1.0
In-Reply-To: <20170301210033.1672.qmail@ary.lan>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C-KEB1ypVuBC1nulskRnbWm5vks>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 20:09:25 -0000

Dear John,

"PS: I presume you all know that we've been working on workarounds."

Please John, explain your results or understanding in the IETF list, 
that all members in the list know, for what you work and what problems 
exist for you.

many thanks and greetings, willi


On 01/03/2017 18:00, John Levine wrote:
> In article <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net> you write:
>>> This is a good idea.  Taking it a step further, perhaps a warning could be included when
>> subscribing to an IETF list from an email provider who is known to use DMARC.
>
> You can tell who publishes DMARC policies, but without experimentation
> you can't tell who follows them on inbound mail.
>
> Of the large public mail providers, only AOL and Yahoo currently
> publish DMARC policies, but Gmail certainly looks at DMARC, albeit as
> part of the special sauce so a Gmail user might get mail with DMARC
> problems or might not.  I'm reasonably sure that Hotmail and Comcast
> also look at DMARC on incoming mail.  DMARC is surprisingly useful for
> blocking phishes, which is a big issue for consumer mail providers, so
> the providers that use it are not going to stop.
>
> R's,
> John
>
> PS: I presume you all know that we've been working on workarounds.
>
>


From nobody Thu Mar  2 13:52:38 2017
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 7148E129672; Thu,  2 Mar 2017 13:52:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIhId226hP8I; Thu,  2 Mar 2017 13:52:36 -0800 (PST)
Received: from dmcq982s684j8g-f84z-4.rev.dnainternet.fi (dmcq982s684j8g-f84z-4.rev.dnainternet.fi [IPv6:2001:14bb:50:9bde:59fa:e60f:c2fc:9cc5]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id CAEF5126BF7; Thu,  2 Mar 2017 13:52:30 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Subject: Remote hubs for IETF 98: Zurich
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: IETF Chair <chair@ietf.org>
Date: Thu, 2 Mar 2017 23:52:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5CF1470-86C8-405B-A5D3-37055441F77E@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m2Oy5yGbZiloo20Iy4GMQVYO5gI>
Cc: Warren Kumari <wkumari@google.com>, Ted Hardie <ted.ietf@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF <ietf@ietf.org>, chair@ietf.org, Ted Hardie <ted.ietf@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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Mar 2017 21:52:37 -0000

This is a follow-up about Google=92s offer to host hubs for the IETF
98 participants who cannot travel to Chicago because of
the recent U.S. travel ban.

Thank you Ted and Warren, and Google!

Please see the details below; they are planning to host a hub
in Zurich, Switzerland, for the duration of the meeting. If you
are interested in joining IETF-98 via this hub, you need
to register as described below.

Jari Arkko, IETF Chair

---

> Hi Jari, Alissa, =20
>=20
> Google will be hosting a remote hub in Z=FCrich, Switzerland for
> IETF 98 participants who cannot travel to Chicago because of
> the recent U.S. travel ban.=20
>=20
> As it turns out, only one person wanted to meet in any of the
> cities we suggested as near the Chicago time zone, so we have
> reduced down to one remote hub, close to the affected folks.
> Zurich appears to be the best Google office for this, as it is in the
> Schengen area and is within a short distance of the largest group
> of affected travelers.   As noted before, we'll provide network,
> rooms, and snacks
>=20
> In order to prepare badges, arrange the appropriate number of
> conference rooms, and get meals lined up, we'd like to ask folks
> to pre-register to use the remote hub facilities by March 24th.  A
> form for doing so is at: https://goo.gl/forms/tEvn68rk5FvSfAxs1
>=20
> If you could share the information with the community, we'd be
> grateful.
>=20
> thanks,
>=20
> Ted Hardie
> Warren Kumari


From nobody Thu Mar  2 20:45:04 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 002701295D9; Thu,  2 Mar 2017 20:45:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-ippm-twamp-time-format-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148851630299.30809.13198180923270314805.idtracker@ietfa.amsl.com>
Date: Thu, 02 Mar 2017 20:45:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-hKRo8TncldTrwVKNaxdMKyl-2c>
Cc: draft-ietf-ippm-twamp-time-format.all@ietf.org, ietf@ietf.org, ippm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 04:45:03 -0000

Reviewer: Joel Halpern
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ippm-twamp-time-format-??
Reviewer: Joel Halpern
Review Date: 2017-03-02
IETF LC End Date: 2017-03-15
IESG Telechat date: Not scheduled for a telechat

Summary:

Major issues:

Minor issues:
    The wording of the behavioral requirements for signaling in
section 2.1 is atypical for IETF documents (and in my view makes it
harder for the reader to follow.)  The rules are listed as separate
rules, but they are actually sequential steps that must be test in
order, exiting the process if the condition for each step is met.  But
it does not actually say that.  

Nits/editorial comments: 
    Section 2.3 refers to this as a proposal.  It is a specification,
not a proposal.  Please reword.



From nobody Thu Mar  2 21:27:53 2017
Return-Path: <suresh.krishnan@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 6A8E5129663 for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 21:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7eUvs1oLtjC6 for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 21:27:50 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7803412948B for <ietf@ietf.org>; Thu,  2 Mar 2017 21:27:50 -0800 (PST)
X-AuditID: c618062d-d5fff700000009d8-d0-58b90f6d07bc
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by  (Symantec Mail Security) with SMTP id 8A.DB.02520.D6F09B85; Fri,  3 Mar 2017 07:38:41 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0319.002; Fri, 3 Mar 2017 00:27:44 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Conclusion of last calls for RFC2460bis, RFC4291bis, and RFC1981bis
Thread-Topic: Conclusion of last calls for RFC2460bis, RFC4291bis, and RFC1981bis
Thread-Index: AQHSk97hobOkCrKftk+HVG0JRUsb1A==
Date: Fri, 3 Mar 2017 05:27:42 +0000
Message-ID: <D5DD1ADB-8B5A-49DA-9250-0FF601A690BF@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_65D0B9EE-EC01-4701-B405-A675E047D732"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyuXRPoG4h/84IgxOKFs82zmdxYPRYsuQn UwBjFJdNSmpOZllqkb5dAlfGoYYDzAUdRhXd/5sYGxg/6XcxcnJICJhIzL/UxtrFyMUhJLCe UeLW3Y2MEM4yRom3rZ+ZQKrYgKo27ISwRQSUJQ7MvMEKYgsL+Ej8mzOFDSIeLHHw9FZ2CFtP oqf1OVicRUBF4vOGSWD1vAL2Es09/WBzGAXEJL6fWgNmMwuIS9x6Mp8J4iIRiYcXT7NB2KIS Lx//Y4WwlSTmvL7GDHIcs8AURon7rQfZIIYKSpyc+YRlAqPgLCSzZiGrm4WkDqJIW2LZwtfM sxg5gGwdickLGSHCphKvj36Esq0lZvyCaGUWUJSY0v2QfQEjxypGjtLigpzcdCODTYzA0D8m waa7g/H+dM9DjAIcjEo8vBuyd0QIsSaWFVfmHmJUAWp9tGH1BUYplrz8vFQlEd60vUBp3pTE yqrUovz4otKc1OJDjNIcLErivHGr74cLCaQnlqRmp6YWpBbBZJk4OKUaGJOKHjHcK2Jg2xyw 9Mua2UHSzeF61rzT+nbrbNor11fDqGPjJXp2Tu+UiSePuL9dVtG0RDHdwMmwVdbnpN7bD26/ xH5JcV1jjuCVPNrJph0kY+T22Hv/jO+q6jOKKkuTms4LBKr1SQote/mv2fXNk6u+r+cGlgeo cUcYMYTFsCWHOC74f+yhEktxRqKhFnNRcSIAy1PUU4UCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rBU7xBtGFmCLQvJd98eWTwnDoWo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 05:27:51 -0000

--Apple-Mail=_65D0B9EE-EC01-4701-B405-A675E047D732
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all,
  The IETF Last Calls on these following documents

draft-ietf-6man-rfc2460bis-08
draft-ietf-6man-rfc4291bis-07
draft-ietf-6man-rfc1981bis-04

have concluded. The last calls resulted in extensive and lively =
discussion that has raised several important points (and the discussion =
on the 4291bis document is still ongoing). I am working with the =
document shepherd and the editor to summarize the discussions and to =
propose a way forward for each of these documents. We expect to do this =
within a few days.

Regards
Suresh


--Apple-Mail=_65D0B9EE-EC01-4701-B405-A675E047D732
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzAzMDUyNzQyWjAjBgkqhkiG9w0B
CQQxFgQUrWPH2BpvzsKbBjBuFGgqW4yEC3UwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQB5XGvctLnUSxbMPIr8dKe7d0jsg+Lp98tnYmmzSF3T6mhpfn4GXfCQQWLabR/G
lswopP5x7nCVEwMnAAFtzN9EFzG5OSSIbeGZ0hA1ohxKxH8tWLpmWftAeg1JGJ0vdsoheNfp4Jp7
elx5rKB2KLtJPArk0QJYuNZd0X4Xjy6XGdu442Bcu4KfqaBUq8arINJjmUxA+tZ5i4zjJus9urV/
Dk/cs0Wy/AVMhJ2fCkw6UqLkyY0kVtGDxEJ5k8BMaatwUH1yi9kTCQq+P38ZKY2bMANWOTfK6whJ
dTvBknZg8klAu/ioQd+69fB/uv8vPICyfjn+DyGjxwVS3I3CnfCDAAAAAAAA

--Apple-Mail=_65D0B9EE-EC01-4701-B405-A675E047D732--


From nobody Thu Mar  2 21:53:16 2017
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 B808D1296CA for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 21:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.52
X-Spam-Level: 
X-Spam-Status: No, score=-1.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.08, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V6kMd2xU9sxr for <ietf@ietfa.amsl.com>; Thu,  2 Mar 2017 21:53:14 -0800 (PST)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A24312940A for <ietf@ietf.org>; Thu,  2 Mar 2017 21:53:14 -0800 (PST)
Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v235hadj022808 for <ietf@ietf.org>; Fri, 3 Mar 2017 00:53:13 -0500
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by mx0b-001b2d01.pphosted.com with ESMTP id 28xs8cp2vw-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 03 Mar 2017 00:53:12 -0500
Received: from localhost by e37.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, 2 Mar 2017 22:53:12 -0700
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e37.co.us.ibm.com (192.168.1.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 2 Mar 2017 22:53:10 -0700
Received: from b01cxnp23032.gho.pok.ibm.com (b01cxnp23032.gho.pok.ibm.com [9.57.198.27]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 33DA83E4003F for <ietf@ietf.org>; Thu,  2 Mar 2017 22:53:10 -0700 (MST)
Received: from b01ledav004.gho.pok.ibm.com (b01ledav004.gho.pok.ibm.com [9.57.199.109]) by b01cxnp23032.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v235r9Qc38600712 for <ietf@ietf.org>; Fri, 3 Mar 2017 05:53:09 GMT
Received: from b01ledav004.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D8BFD11204B for <ietf@ietf.org>; Fri,  3 Mar 2017 00:53:08 -0500 (EST)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav004.gho.pok.ibm.com (Postfix) with ESMTPS id BB8AE112040 for <ietf@ietf.org>; Fri,  3 Mar 2017 00:53:08 -0500 (EST)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v235r8Lw008926 for <ietf@ietf.org>; Fri, 3 Mar 2017 00:53:08 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v235r86b008909 for ietf@ietf.org; Fri, 3 Mar 2017 00:53:08 -0500
From: narten@us.ibm.com
Date: Fri, 03 Mar 2017 00:53:08 -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-TM-AS-GCONF: 00
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 17030305-0024-0000-0000-000016099FA4
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006713; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000206; SDB=6.00829377; UDB=6.00406598; IPR=6.00606874;  BA=6.00005186; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014503; XFM=3.00000012; UTC=2017-03-03 05:53:11
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17030305-0025-0000-0000-00004933B90E
Message-Id: <201703030553.v235r86b008909@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-03_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=89 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703030055
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pz8434M3WJKwYq5eItHPxHmJrvA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 05:53:16 -0000

Total of 147 messages in the last 7 days.
 
script run at: Fri Mar  3 00:53:02 EST 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  2.04% |    3 | 12.93% |   276352 | shitanshu_shah@hotmail.com
  6.80% |   10 |  4.99% |   106626 | alexandre.petrescu@gmail.com
  1.36% |    2 | 10.12% |   216294 | david.black@dell.com
  6.80% |   10 |  4.46% |    95395 | willi.uebelherr@riseup.net
  2.72% |    4 |  5.58% |   119190 | ted.ietf@gmail.com
  1.36% |    2 |  5.92% |   126475 | mohamed.boucadair@orange.com
  3.40% |    5 |  3.44% |    73536 | morrowc.lists@gmail.com
  3.40% |    5 |  1.99% |    42545 | fgont@si6networks.com
  2.04% |    3 |  2.53% |    54145 | farmer@umn.edu
  2.72% |    4 |  1.71% |    36501 | worley@ariadne.com
  2.72% |    4 |  1.67% |    35621 | gert@space.net
  2.72% |    4 |  1.43% |    30558 | sm+ietf@elandsys.com
  2.72% |    4 |  1.28% |    27288 | johnl@taugh.com
  2.04% |    3 |  1.41% |    30026 | sander@steffann.nl
  2.04% |    3 |  1.25% |    26647 | mersue@gmail.com
  1.36% |    2 |  1.86% |    39708 | ek@google.com
  2.04% |    3 |  1.08% |    23100 | mcr+ietf@sandelman.ca
  2.04% |    3 |  1.06% |    22571 | cabo@tzi.org
  1.36% |    2 |  1.64% |    34990 | daedulus@btconnect.com
  2.04% |    3 |  0.94% |    20139 | chair@ietf.org
  1.36% |    2 |  1.39% |    29754 | pierre.pfister@darou.fr
  1.36% |    2 |  1.29% |    27616 | pmcmanus@mozilla.com
  1.36% |    2 |  1.07% |    22931 | xing@cernet.edu.cn
  1.36% |    2 |  1.00% |    21453 | stephen.farrell@cs.tcd.ie
  1.36% |    2 |  0.97% |    20812 | mstjohns@comcast.net
  0.68% |    1 |  1.57% |    33601 | laurent.ciavaglia@nokia-bell-labs.com
  1.36% |    2 |  0.88% |    18885 | barryleiba@computer.org
  1.36% |    2 |  0.88% |    18796 | brian.e.carpenter@gmail.com
  0.68% |    1 |  1.50% |    32157 | kerlyn@ieee.org
  1.36% |    2 |  0.80% |    17012 | tytso@mit.edu
  1.36% |    2 |  0.75% |    16106 | touch@isi.edu
  1.36% |    2 |  0.73% |    15553 | swmike@swm.pp.se
  1.36% |    2 |  0.65% |    13833 | liushucheng@huawei.com
  1.36% |    2 |  0.64% |    13626 | pch-ietf-6@u-1.phicoh.com
  1.36% |    2 |  0.63% |    13464 | jmh@joelhalpern.com
  0.68% |    1 |  1.09% |    23342 | stewart.bryant@gmail.com
  0.68% |    1 |  0.96% |    20484 | weihaw@google.com
  0.68% |    1 |  0.71% |    15272 | alexandre.petrescu@cea.fr
  0.68% |    1 |  0.65% |    13839 | eng.khaled.omar@hotmail.com
  0.68% |    1 |  0.61% |    13124 | narten@us.ibm.com
  0.68% |    1 |  0.55% |    11667 | jinmei@wide.ad.jp
  0.68% |    1 |  0.54% |    11552 | lars@netapp.com
  0.68% |    1 |  0.53% |    11418 | agmalis@gmail.com
  0.68% |    1 |  0.53% |    11387 | wangjohnny721@gmail.com
  0.68% |    1 |  0.52% |    11006 | aaron.falk@gmail.com
  0.68% |    1 |  0.51% |    10969 | warren@kumari.net
  0.68% |    1 |  0.50% |    10761 | jordi.palet@consulintel.es
  0.68% |    1 |  0.48% |    10327 | lorenzo@google.com
  0.68% |    1 |  0.48% |    10263 | bob.hinden@gmail.com
  0.68% |    1 |  0.47% |    10056 | ynir.ietf@gmail.com
  0.68% |    1 |  0.44% |     9327 | ando@bbsec.co.jp
  0.68% |    1 |  0.43% |     9221 | tte@cs.fau.de
  0.68% |    1 |  0.42% |     9054 | kathleen.moriarty.ietf@gmail.com
  0.68% |    1 |  0.39% |     8432 | joelja@bogus.com
  0.68% |    1 |  0.39% |     8401 | peter@akayla.com
  0.68% |    1 |  0.39% |     8299 | mfidelman@meetinghouse.net
  0.68% |    1 |  0.39% |     8274 | peter@filament.com
  0.68% |    1 |  0.38% |     8161 | nick@foobar.org
  0.68% |    1 |  0.38% |     8023 | john-ietf@jck.com
  0.68% |    1 |  0.37% |     7847 | stewart@g3ysx.org.uk
  0.68% |    1 |  0.37% |     7803 | ietf-dane@dukhovni.org
  0.68% |    1 |  0.36% |     7740 | dwm@xpasc.com
  0.68% |    1 |  0.36% |     7716 | rsk@gsp.org
  0.68% |    1 |  0.36% |     7674 | alex@strugee.net
  0.68% |    1 |  0.36% |     7663 | jari.arkko@piuha.net
  0.68% |    1 |  0.35% |     7428 | rg+ietf@randy.pensive.org
  0.68% |    1 |  0.34% |     7324 | chopps@chopps.org
  0.68% |    1 |  0.34% |     7162 | ned+ietf@mauve.mrochek.com
  0.68% |    1 |  0.33% |     7101 | gunnar.hellstrom@omnitor.se
  0.68% |    1 |  0.32% |     6913 | heas@shrubbery.net
  0.68% |    1 |  0.31% |     6541 | housley@vigilsec.com
  0.68% |    1 |  0.27% |     5815 | iad@ietf.org
  0.68% |    1 |  0.26% |     5548 | rjsparks@nostrum.com
  0.68% |    1 |  0.26% |     5507 | roni.even@mail01.huawei.com
  0.68% |    1 |  0.23% |     4998 | j.schoenwaelder@jacobs-university.de
--------+------+--------+----------+------------------------
100.00% |  147 |100.00% |  2136745 | Total


From nobody Fri Mar  3 01:23:42 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99AA91293F4; Fri,  3 Mar 2017 01:23:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level: 
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OjuBplA-Ecz2; Fri,  3 Mar 2017 01:23:38 -0800 (PST)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7201F1297B8; Fri,  3 Mar 2017 01:23:31 -0800 (PST)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id C4D1E120674; Fri,  3 Mar 2017 10:23:29 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.58]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 9FE0740064; Fri,  3 Mar 2017 10:23:29 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0319.002; Fri, 3 Mar 2017 10:23:29 +0100
From: <mohamed.boucadair@orange.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: RE: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Topic: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Index: AQHSk38u0WZKyRemRkqdonYieFTtfKGCtXIw
Date: Fri, 3 Mar 2017 09:23:28 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com>
In-Reply-To: <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933009E1BDA0OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nq1lz5B3X8wp2zaZyKRpOF7PJJo>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 09:23:41 -0000

--_000_787AE7BB302AE849A7480A190F8B933009E1BDA0OPEXCLILMA3corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgVGVkLA0KDQpQbGVhc2Ugc2VlIGlubGluZS4NCg0KQ2hlZXJzLA0KTWVkDQoNCkRlIDogVGVk
IEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbV0NCkVudm95w6kgOiBqZXVkaSAyIG1h
cnMgMjAxNyAxOTowMg0Kw4AgOiBCT1VDQURBSVIgTW9oYW1lZCBJTVQvT0xODQpDYyA6IGlldGZA
aWV0Zi5vcmc7IGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbkBpZXRmLm9y
Zw0KT2JqZXQgOiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRhdGEt
aW5zZXJ0aW9uLTA1LnR4dD4gKERlc2lnbiBjb25zaWRlcmF0aW9ucyBmb3IgTWV0YWRhdGEgSW5z
ZXJ0aW9uKSB0byBJbmZvcm1hdGlvbmFsIFJGQw0KDQp3aW5nIGFyZSBtaXNzaW5nIGZyb20gdGhl
IGRvY3VtZW50Og0KSXQncyBkaWZmaWN1bHQgdG8gc2F5IGhvdyBzb21ldGhpbmcgd2lsbCBiZSB1
c2VkIGluIHRoZSBmdXR1cmUuDQpbTWVkXSBBbiBhZHZpY2UgdGhhdCBpcyBub3QgaW1wbGVtZW50
YWJsZSBtYWtlcyBtb3JlIHRyb3VibGVzLCBJTUhPLg0KU29ycnksIEkgdGhvdWdodCB5b3Ugd2Vy
ZSBhc2tpbmcgd2hhdCB3Z3Mgb3IgcHJvdG9jb2xzIHBsYW5uZWQgdG8gcmVmZXJlbmNlIHRoaXMu
ICBGb3IgdGhhdCwgSSBkb24ndCBrbm93Lg0KW01lZF0gT0suIElNSE8gbGFja2luZyBzdWNoIGNv
bnNpZGVyYXRpb25zLCB0aGVyZSBpcyBhIGhpZ2ggcmlzayB0aGF0IHRoZSBhZHZpY2Ugd2lsbCBi
ZSBsb3N0IG9yIHRoYXQgaXQgY2FuIGJlIHVzZWQgYXMgYSBwZXJtYW5lbnQgRElTQ1VTUyBwb2lu
dCBpbiBsYXRlciBzdGFnZXMgb2YgcHJlcGFyaW5nIGRvY3VtZW50cy4gSeKAmWQgcHJlZmVyIGlm
IGFjdGlvbmFibGUgcG9pbnRzIHRvIGJlIGNvbnNpZGVyZWQgYnkgV0dzIGFuZCBkb2N1bWVudCBh
dXRob3JzIGluIGVhcmx5IHN0YWdlcy4NCg0KVGhlIGludGVudCBpcyB0aGF0IGl0IGlzIGluZm9y
bWF0aW9uIHVzZWZ1bCB0byB0aG9zZSBjb25zaWRlcmluZyB3aGV0aGVyIHJlc3RvcmluZyBtZXRh
ZGF0YSBsb3N0IHRvIGVuY3J5cHRpb24gaW4gbWlkLW5ldHdvcmsgaXMgdGhlIHJpZ2h0IHdheSB0
byBnby4NCltNZWRdIFRoaXMgaXMgYW5vdGhlciBhc3N1bXB0aW9uIGluIHRoZSBkb2N1bWVudCB0
aGF0IEkgZGlzYWdyZWUgd2l0aDogSXQgc2VlbXMgdGhhdCB5b3UgYXNzdW1lIHRoYXQgYW4gb24t
cGF0aCBkZXZpY2UsIHRoYXQgaW5zZXJ0cyBtZXRhZGF0YSwgaXMgbmVjZXNzYXJpbHkgUkVTVE9S
SU5HIGJhY2sgdGhhdCBpbmZvcm1hdGlvbi4gVGhpcyBpcyBub3QgdHJ1ZSBmb3IgbWFueSBlZmZv
cnRzOg0KDQrCtyAgICAgICAgIEEgRm9yd2FyZC1Gb3IgaGVhZGVyIGluc2VydGVkIGJ5IGEgcHJv
eHkgZG9lcyBub3QgcmVzdG9yZSBhbnkgZGF0YTsgaXQgZG9lcyBvbmx5IHJldmVhbCBkYXRhIHRo
YXQgaXMgYWxyZWFkeSBwcmVzZW50IGluIHRoZSBwYWNrZXQgaXNzdWVkIGJ5IHRoZSBjbGllbnQg
aXRzZWxmLg0KDQrCtyAgICAgICAgIEFuIGFkZHJlc3Mgc2hhcmluZyBkZXZpY2UsIHVuZGVyIGZv
ciBleGFtcGxlIERTLUxpdGUgKFJGQzYzMzMpLCB0aGF0IGluc2VydHMgdGhlIHNvdXJjZSBJUHY2
IHByZWZpeCBpbiB0aGUgVENQIEhPU1RfSUQgb3B0aW9uIChSRkM3OTc0KSBpcyBub3QgUkVTVE9S
SU5HIGFueSBkYXRhLiBUaGUgY29udGVudCBvZiB0aGF0IFRDUCBvcHRpb24gaXMgYWxyZWFkeSB2
aXNpYmxlIGluIHRoZSBwYWNrZXQgc2VudCBieSB0aGUgaG9zdC4NCg0KwrcgICAgICAgICBTZXJ2
aWNlIEZ1bmN0aW9uIENoYWluaW5nIFdHIChodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL3dn
L3NmYy9hYm91dC8pIGlzIGRlZmluaW5nIGFuIGFyY2hpdGVjdHVyZSB0byBjb21tdW5pY2F0ZSBt
ZXRhZGF0YSBieSBvbi1wYXRoIGRldmljZXM7IHRoYXQgbWV0YWRhdGEgaXMgaW5zZXJ0ZWQgYXQg
dGhlIG5ldHdvcmsgc2lkZS4gQm9yZGVyIG5vZGVzIHdpbGwgbWFrZSBzdXJlIHRoYXQgZGF0YSBp
cyBzdHJpcHBlZCBiZWZvcmUgZm9yd2FyZGluZyBwYWNrZXRzIHRvIHRoZSB1bHRpbWF0ZSBkZXN0
aW5hdGlvbnMuIFRoZSBtZXRhZGF0YSBjYW4gYmUgYSBzdWJzY3JpYmVyLWlkLCBhIHBvbGljeS1p
ZCwgZXRjLg0KDQoNClNvIHdoZW4gZHJhZnQtaGFyZGllLSogc2F5czog4oCcRG8gbm90IGFkZCBt
ZXRhZGF0YSB0byBmbG93cyBhdCBpbnRlcm1lZGlhcnkgZGV2aWNlcyB1bmxlc3MNCiAgIGEgcG9z
aXRpdmUgYWZmaXJtYXRpb24gb2YgYXBwcm92YWwgZm9yIHJlc3RvcmF0aW9uIGhhcyBiZWVuIHJl
Y2VpdmVkDQogICBmcm9tIHRoZSBhY3RvciB3aG9zZSBkYXRhIHdpbGwgYmUgYWRkZWQu4oCdDQoN
CigxKSBEbyB5b3UgYXNzdW1lIHRoYXQgdGhlIHNhbXBsZSBleGFtcGxlcyBJIGxpc3RlZCBhYm92
ZSBmYWxsIHVuZGVyIHlvdXIgYWR2aWNlPw0KKDIpIEhvdyBhbiBvbi1wYXRoIGRldmljZSB3aWxs
IGtub3cgdGhlIGRhdGEgaXQgaW50ZW5kcyB0byBpbnNlcnQgaXMgYSDigJxyZXN0b3JhdGlvbuKA
nT8NCigzKSBEb2VzIGl0IG1lYW4gdGhhdCBmb3IgbmV3IGRhdGEgKGkuZS4sIHRoYXQgYXJlIG5v
dCByZXN0b3JhdGlvbiksIG9uLXBhdGggZGV2aWNlcyBhcmUgZnJlZSB0byBkbyB3aGF0ZXZlciB0
aGV5IHdhbnQ/IEZvciBtZSwgdGhpcyBpcyB1bmRlc2lyYWJsZS4gVGhlcmUgaXMgYSB2b2lkIHRo
ZXJlLiBBIHN0YXRlbWVudCB0byByZXF1aXJlIHRob3NlIG5ldHdvcmtzIHRvIGF2b2lkIGxlYWtp
bmcgcHJpdmFjeSBpbmZvcm1hdGlvbiBtdXN0IGJlIGluY2x1ZGVkLg0KDQpBbm90aGVyIGFzc3Vt
cHRpb24gaXMgbWFkZSBoZXJlOg0KDQogICBJbnN0ZWFkLCBkZXNpZ24gdGhlIHByb3RvY29sIHNv
IHRoYXQgdGhlIGFjdG9yIGNhbiBhZGQgc3VjaCBtZXRhZGF0YQ0KICAgdGhlbXNlbHZlcyBzbyB0
aGF0IGl0IGZsb3dzIGVuZC10by1lbmQsIHJhdGhlciB0aGFuIHJlcXVpcmluZyB0aGUNCiAgIGFj
dGlvbiBvZiBvdGhlciBwYXJ0aWVzLiAgSW4gYWRkaXRpb24gdG8gaW1wcm92aW5nIHByaXZhY3ks
IHRoaXMNCiAgIGFwcHJvYWNoIGVuc3VyZXMgY29uc2lzdGVudCBhdmFpbGFiaWxpdHkgYmV0d2Vl
biB0aGUgY29tbXVuaWNhdGluZw0KICAgcGFydGllcywgbm8gbWF0dGVyIHdoYXQgcGF0aCBpcyB0
YWtlbi4NCg0KVGhpcyB0ZXh0IGNsYWltcyB0aGF0IHByb3ZpZGluZyBkYXRhIGJ5IHRoZSBlbmRw
b2ludCBlbnN1cmVzIGEg4oCcY29uc2lzdGVudCBhdmFpbGFiaWxpdHnigJ0gb2YgdGhhdCBpbmZv
cm1hdGlvbi4gVGhpcyBpcyBicm9rZW4gZm9yIGEgbXVsdGktaG9tZWQgaG9zdCB0aGF0IHVzZXMg
Zm9yIGV4YW1wbGUgRm9yd2FyZC1Gb3IgaGVhZGVyOiBPYnZpb3VzbHksIHRoZSBjb250ZW50IG9m
IHRoZSBoZWFkZXIgaWYgaW5qZWN0ZWQgYnkgdGhlIGVuZHBvaW50IHdpbGwgZGVwZW5kIG9uIHRo
ZSBwYXRoLiBBIHdheSB0byBlbnN1cmUgYSDigJxjb25zaXN0ZW50IGF2YWlsYWJpbGl0eeKAnSBp
cyB0byBpbnNlcnQgbWFueSBGb3J3YXJkLUZvciBoZWFkZXJzOyBlYWNoIGVuY2xvc2luZyB0aGUg
Y29udGVudCB0aGF0IGlzIHNwZWNpZmljIHRvIGEgZ2l2ZW4gbmV0d29yayBhdHRhY2htZW50LiBC
dXQgZG9pbmcgdGhhdCByYWlzZXMgYSBwcml2YWN5IGNvbmNlcm4gYmVjYXVzZSB0aGUgcmVtb3Rl
IHNlcnZlciBjYW4gdHJhY2sgY2xpZW50cy4NCk15IGludGVudCAoYW5kIHRoZSB1bmRlcnN0YW5k
aW5nIG9mIG90aGVyIHJldmlld2VycykgaXMgdG8gaGlnaGxpZ2h0IHRoYXQgdGhlc2UgbWVjaGFu
aXNtcyBoYXZlIGEgcHJpdmFjeS1kYW1hZ2luZyByZXN1bHQgYW5kIHRoYXQgdGhpcyBzaG91bGQg
YmUgY29uc2lkZXJlZC4NCltNZWRdIEkgZG8gdGhpbmsgZXhpc3RpbmcgZG9jdW1lbnRzIGFscmVh
ZHkgbWFrZSB0aGF0IGpvYi4gSSBkbyB0aGluayB3ZSBuZWVkIG1vcmUuDQoNClNvcnJ5LCBkaWQg
eW91IG1lYW4gImRvIG5vdCB0aGluayB3ZSBuZWVkIG1vcmUiPw0KW01lZF0gSSBtZWFudCB3ZSBu
ZWVkIG1vcmUgdGhhbiBvbmx5IGhpZ2hsaWdodGluZyB0aGUgaXNzdWUuIFdlIG5lZWQgc29tZXRo
aW5nIHdoaWNoIGlzIGFjdGlvbmFibGUuIFJlcXVpcmluZyBhIFByaXZhY3kgU2VjdGlvbiBpbiBl
dmVyeSBSRkMgbWF5IGEgZGlyZWN0aW9uIHRvIGNvbnNpZGVyLg0KDQogIElmIHNvLCBJIG9idmlv
dXNseSBkaXNhZ3JlZS4gIFRoaXMgZGVzaWduIHBhdHRlcm4gaXMgdXNlZCB1bmNyaXRpY2FsbHkg
ZW5vdWdoIHRoYXQgYSBicmllZiBkb2N1bWVudCBkZXNjcmliaW5nIHdoeSBpdCBpc24ndCBzYWZl
IHN0aWxsIHNlZW1zIHRvIG1lIHVzZWZ1bC4gIFdlcmUgaXQgaW5jb3Jwb3JhdGVkIGludG8gYSBt
b3JlIGdlbmVyYWwgZG9jdW1lbnQgKGFzIG5vdGVkIGJlZm9yZSksIHRoYXQgd291bGQgYWxzbyB3
b3JrLiAgSWYgaXQgbGF0ZXIgaXMsIHRoYXQgbW9yZSBnZW5lcmFsIHdvcmsgY291bGQgb2Jzb2xl
dGUgdGhpcyAodGhvdWdoIHRoYXQncyBhIGJpZCBmb3IgYW4gaW5mb3JtYXRpb25hbCBkb2N1bWVu
dCkuDQoNCiBJbiBwYXJ0aWN1bGFybHksIEknbSBjb25jZXJuZWQgdGhhdCBzb21lIGFwcGxpY2F0
aW9uIGZ1bmN0aW9ucyBpbiB0aGUgbmV0d29yayAoZS5nLiByZWN1cnNpdmUgcmVzb2x2ZXJzIG9y
IHByb3hpZXMpIGRvIG5vdCBjb25zaWRlciB0aGUgcG9zdGl2ZSBwcml2YWN5IGltcGxpY2F0aW9u
cyBvZiB0aGVpciBhZ2dyZWdhdGlvbiBhbmQgc28gZG8gbm90IGNvbnNpZGVyIGFkZGluZyB0aGlz
IGRhdGEgYmFjayBhcyBwcm9ibGVtYXRpYy4NCltNZWRdIEnigJltIGFsc28gY29uY2VybmVkIHdp
dGggdGhhdCwgdG9vIChzZWUgZS5nLiwgaHR0cDovL3d3dzEuaWNzaS5iZXJrZWxleS5lZHUvfm5h
cnNlby9wYXBlcnMvaG90bTQyLXZhbGxpbmFyb2RyaWd1ZXoucGRmPGh0dHA6Ly93d3cxLmljc2ku
YmVya2VsZXkuZWR1LyU3RW5hcnNlby9wYXBlcnMvaG90bTQyLXZhbGxpbmFyb2RyaWd1ZXoucGRm
PikuIEluIHRoZSBtZWFudGltZSwgSeKAmW0gYWxzbyBjb25jZXJuZWQgd2l0aCAoMSkgc29tZSBh
cHBsaWNhdGlvbnMgdGhhdCBsZWFrIHByaXZhY3kgaW5mb3JtYXRpb24gd2l0aG91dCB0aGUgY29u
c2VudCBvZiB0aGUgdXNlciBhbmQgKDIpIHNvbWUgYXBwbGljYXRpb24gc2VydmVycyB0aGF0IG1h
eSBjb3JyZWxhdGUgdmFyaW91cyBpbmZvcm1hdGlvbiBzaGFyZWQgYnkgYW4gYXBwbGljYXRpb24g
Y2xpZW50IHRvIHRyYWNrIHVzZXJzIChlLmcuLCBodHRwczovL3Bhbm9wdGljbGljay5lZmYub3Jn
LykuIEJUVywgSSBzZWUgdGhhdCB5b3UgYXJlIHVzaW5nIOKAnGFwcGxpY2F0aW9uIGZ1bmN0aW9u
4oCdIHdoaWNoIG1heSBub3QgaGF2ZSB0aGUgc2FtZSBtZWFuaW5nIGFzIHRoZSBnZW5lcmFsIOKA
nHByb3RvY29s4oCdIHdvcmRpbmcgdXNlZCBpbiBkcmFmdC1oYXJkaWUtKi4gRG8geW91IGNvbnNp
ZGVyIGEgREhDUCByZWxheSBhcyBhbiDigJxhcHBsaWNhdGlvbiBmdW5jdGlvbuKAnT8NCiAgIEhp
Z2hsaWdodGluZyB0aGlzIGVuYWJsZXMgdGhlbSB0byBzZWUgdGhpcyB0cmFmZmljIGluIGEgZGlm
ZmVyZW50IGNvbnRleHQuDQpbTWVkXSBJc27igJl0IHRoaXMgYWxyZWFkeSBhc3N1bWVkIGJ5IHNv
bWUgcHJvdG9jb2wgZGVzaWduZXJzIChlLmcuLCBSRkM2OTczLCBTSVApPyBCVFcsIHRoZXJlIGFy
ZSBzdWJ0bGV0aWVzIHdoZW4gcHJveGllcyBhcmUgaW4gdGhlIHNhbWUgdHJ1c3QgZG9tYWluIG9m
IHRoZSBjbGllbnQgb3Igc2VydmVyLg0KVGhlcmUgYXJlIGNlcnRhaW5seSBzb21lIHByb3RvY29s
IGRlc2lnbmVycyB0aGF0IGhhdmUgaW50ZXJuYWxpemVkIHRoaXMsIGJ1dCBteSBleHBlcmllbmNl
IGhhcyBiZWVuIHRoYXQgdGhpcyBpcyBub3QgYWx3YXlzIHRoZSBjYXNlLiAgSW4gYSBmYWlyIGZl
dyBjYXNlcywgZm9sa3MgZGVwbG95ICBtZXRob2RzIGxpa2UgdGhpcyBiZWNhdXNlIHRoZXkgc2Vl
IGVuY3J5cHRpb24gb2YgbWV0YWRhdGEgaW4gZGF0YSBpbnRlZ3JpdHkgdGVybXMgb3Igc2VlIGFn
Z3JlZ2F0aW9uIG9ubHkgaW4gdGVybXMgb2YgZGF0YSB1c2FnZSBtaW5pbWl6YXRpb24uICBUaGV5
IHJlc3RvcmUgdGhlIG1ldGFkYXRhIG1pZC1uZXR3b3JrIGJlY2F1c2UgaXQgaXMgdGhlIHF1aWNr
ZXN0IHNvbHV0aW9uIGZvciB0aGVtIHRvIGdldCBiYWNrIHRvIHRoZSBzdGF0dXMgcXVvIGFudGUg
Zm9yIHRoZWlyIHVuZGVyc3RhbmRpbmcgb2YgdGhlIHN5c3RlbS4NCg0KW01lZF0gSSBoZWFyIHlv
dS4gV2hhdCB3b3VsZCBiZSB0aGUgaGFybSBpZiB0aG9zZSBzb2x1dGlvbnMgc3RyaXAgdGhhdCBp
bmZvcm1hdGlvbiBiZWZvcmUgc2VuZGluZyBpdCB0byB0aGUgc2VydmVyPyBJZiB0aGV5IGRvbuKA
mXQgc3RyaXAgaXQsIHRoaXMgbWVhbnMgdGhhdCBlaXRoZXIgdGhlIGluZm9ybWF0aW9uIGNhbiBi
ZSBwYXJzZWQgYW5kIHVzZWQgYnkgdGhlIHNlcnZlciwgb3IgYXQgbGVhc3QgaXRzIHByZXNlbmNl
IGRvZXMgbm90IGxlYWQgdG8gc2Vzc2lvbiBmYWlsdXJlcy4gSW4gdGhlIGNhc2UgdGhlIHNlcnZl
ciBwYXJzZXMgYW5kIHVzZXMgdGhhdCBpbmZvcm1hdGlvbiwgdGhpcyBtZWFucyB0aGF0IHRoZSBw
cmVzZW5jZSBvZiB0aGF0IGluZm9ybWF0aW9uIGlzIGltcG9ydGFudCBmb3IgdGhlIHNlcnZpY2Ug
dG8gZGVsaXZlci4gSW4gdGhhdCBjYXNlLCB0aGUgcXVlc3Rpb24gaXMgd2h5IHRoZSBjbGllbnQg
ZG9lcyBub3Qgc3VwcGx5IHRoYXQgaW5mb3JtYXRpb24gYXQgdGhlIGZpcnN0IHBsYWNlLg0KKiB0
aGF0IGRhdGEgbWF5IG5vdCBiZSBhbHdheXMgYXZhaWxhYmxlIHRvIHRoZSBlbmRob3N0DQpVbmRl
cnN0b29kLCBidXQgZXZlbiBpbiB0aGlzIGNhc2UsIGl0IGlzIGJldHRlciB0byBtYWtlIHRoZSBw
ZXJtaXNzaW9uIHRvIGFkZCB0aGUgZGF0YSBleHBsaWNpdC4NCltNZWRdIFRoaXMgbWF5IGJlIGVh
c3kgdG8gaW1wbGVtZW50IGZvciBzb21lIGFwcGxpY2F0aW9ucywgYnV0IHRoaXMgbWF5IG5vdCBi
ZSBnZW5lcmFsaXplZCB0byAqKiBhbGwgKiogcHJvdG9jb2xzLg0KDQpZb3UgYXJlIGNlcnRhaW5s
eSBjb3JyZWN0IHRoYXQgbWFueSBkZXBsb3llZCBwcm90b2NvbHMgd291bGQgZmluZCBpdCBoYXJk
IHRvIHJldHJvZml0IHRoaXMgY29uc2VudCBtb2RlbCBpbnRvIHRoZWlyIGV4aXN0aW5nIGZsb3dz
LiAgICBUaGlzIGlzLCBob3dldmVyLCBhZHZpY2UgZm9yIGZvbGtzIGF0IHRoZSBkZXNpZ24gcGhh
c2UuICBJZiBSRkMgNjc4OCB3ZXJlIGJlaW5nIHdyaXR0ZW4gYWZ0ZXIgdGhlIHB1YmxpY2F0aW9u
IG9mIHRoaXMgZG9jdW1lbnQsIGl0cyBhdXRob3JzIG1pZ2h0IHdlbGwgaGF2ZSBsb29rZWQgYXQg
dGhlIHByb3RvY29sIG1lY2hhbmljcyBpbiBzZWN0aW9uIDUuMjoNCg0KICAgVGhlIEFODQoNCiAg
IGludGVyY2VwdHMgYW5kIHRoZW4gdHVubmVscyB0aGUgcmVjZWl2ZWQgUm91dGVyIFNvbGljaXRh
dGlvbiBpbiBhDQoNCiAgIG5ld2x5IGNyZWF0ZWQgSVB2NiBkYXRhZ3JhbSB3aXRoIHRoZSBMaW5l
LUlkZW50aWZpY2F0aW9uIE9wdGlvbg0KDQogICAoTElPKS4gIFRoZSBBTiBmb3JtcyBhIG5ldyBJ
UHY2IGRhdGFncmFtIHdob3NlIHBheWxvYWQgaXMgdGhlDQoNCiAgIHJlY2VpdmVkIFJvdXRlciBT
b2xpY2l0YXRpb24gbWVzc2FnZSBhcyBkZXNjcmliZWQgaW4gW1JGQzI0NzM8aHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL3JmYzI0NzM+XSwNCg0KICAgZXhjZXB0IHRoYXQgdGhlIEhvcCBMaW1p
dCBmaWVsZCBvZiB0aGUgUm91dGVyIFNvbGljaXRhdGlvbiBtZXNzYWdlDQoNCiAgIE1VU1QgTk9U
IGJlIGRlY3JlbWVudGVkLg0KDQphbmQgYXNrZWQgd2hldGhlciB0aGUgY2lyY3VpdCBpZGVudGlm
aWVyIGNvcnJlc3BvbmRpbmcgdG8gdGhlIGxvZ2ljYWwNCmFjY2VzcyBsb29wIHBvcnQgb2YgdGhl
IEFOIGZyb20gd2hpY2ggdGhlIFJTIHdhcyBpbml0aWF0ZWQgUElJLiAgSWYgc28sIHRoaXMNCmRv
Y3VtZW50IHdvdWxkIGhhdmUgdGhlbSBjb25zaWRlciB3aGV0aGVyIHRyYW5zcGFyZW50IGludGVy
Y2VwdGlvbg0KaXMgdGhlIGFwcHJvcHJpYXRlIGNob2ljZSBpZiBpdCBpcy4gIFRoZXJlIGNsZWFy
bHkgYXJlIGZsb3dzIGluIHdoaWNoIHRoZSBBTidzIHJvbGUNCndvdWxkIGJlIGV4cGxpY2l0Lg0K
DQpJIGRvbid0IGtub3csIGZyYW5rbHksIHdoaWNoIGNob2ljZSBpcyByaWdodCBpbiB0aGlzIGNh
c2UsIGJ1dCBJIHdvdWxkIHByZWZlciB0aGF0DQp0aGUgY2hvaWNlIGJlIG1hZGUgd2l0aCBhbiBl
YXN5IHJlZmVyZW5jZSB0byB0aGUgaW1wbGljYXRpb25zIG9mIGluc2VydGluZyBtZXRhZGF0YQ0K
YXQgaGFuZC4NClB1dHRpbmcgYXNpZGUgdGhlIGludGVyYWN0aW9uIHdpdGggYSB1c2VyIHRvIGdl
dCBhIGNvbnNlbnQgYW5kIGhvdyB0aGF0IGNvbnNlbnQgd2lsbCBuZWVkIHRvIGJlIGNoYW5nZWQg
d2hlbiBhbm90aGVyIHVzZXIgdXNlcyB0aGUgc2FtZSBkZXZpY2UgdG8gY29ubmVjdCB0byB0aGUg
SW50ZXJuZXQuIENvbnNpZGVyIGEgdXNlciB3aG8gZG9lcyBub3Qgd2FudCBhbiB1cHN0cmVhbSBE
SFBDIHJlbGF5IHRvIGluc2VydCB0aGUgbGluZS1pZCAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9o
dG1sL3JmYzY3ODgpIHRvIHRoZSBzZXJ2ZXIsIGFuZCBsZXTigJlzIHN1cHBvc2UgdGhlIHJlbGF5
IHJlY2VpdmVkIGEgc2lnbmFsIChieSBzb21lIG1lYW5zLCB0byBiZSB5ZXQgc3BlY2lmaWVkKSB0
aGF0IGZvciB0aGlzIHBhcnRpY3VsYXIgREhDUCBjbGllbnQsIHRoZSBsaW5lLWlkIG11c3Qgbm90
IGJlIGluc2VydGVkLiBGb3IgdGhpcyBjYXNlLCBjb25uZWN0aXZpdHkgd29u4oCZdCBiZSBwcm92
aWRlZCB0byB0aGF0IHVzZXIuIFRoaXMgd291bGQgbWVhbiBleHRyYSBjYWxscyB0byB0aGUgaG90
bGluZSBmb3IgdGhhdCBuZXR3b3JrIHByb3ZpZGVyLiBUaGlzIGlzIG5vdCBkZXNpcmFibGUgZm9y
IGJvdGggY3VzdG9tZXJzIGFuZCBuZXR3b3JrIHByb3ZpZGVycy4NCkkNCg0KZiB0aGlzIGNhbiBi
ZSBkb25lIGluIHBhcmFsbGVsIHdpdGggb3RoZXIgYWN0aW9ucywgdGhlbiB0aGUgbGF0ZW5jeSBp
bXBhY3QgY2FuIGJlIG1pbmltaXplZC4NCltNZWRdIFRoZXNlIGFyZSBhc3N1bXB0aW9ucyBhbmQg
aW1wbGljYXRpb25zIHRoYXQgYXJlIHdvcnRoIHRvIGJlIGFkZGVkIHRvIHRoZSBkcmFmdC4NCg0K
T2theSwgaG93IGFib3V0IHRoZSBmb2xsb3dpbmcgdGV4dCBiZWluZyBhZGRlZCB0byBzZWN0aW9u
IDUuDQpUaGVyZSBhbHNvIHRlbnNpb25zIHdpdGggbGF0ZW5jeSBvZiBvcGVyYXRpb24uIEZvciBl
eGFtcGxlLCB3aGVyZSB0aGUgZW5kIHN5c3RlbSBkb2VzIG5vdCBpbml0aWFsbHkga25vdyB0aGUg
aW5mb3JtYXRpb24gd2hpY2ggd291bGQgYmUgYWRkZWQgYnkgb24tcGF0aCBkZXZpY2VzLCBpdCBt
dXN0IGVuZ2FnZSB0aGUgcHJvdG9jb2wgbWVjaGFuaXNtcyB0byBkZXRlcm1pbmUgaXQuICBEZXRl
cm1pbmluZyBhIHB1YmxpYyBJUCBhZGRyZXNzIHRvIGluY2x1ZGUgaW4gYSBsb2NhbGx5IHN1cHBs
aWVkIGhlYWRlciBtaWdodCByZXF1aXJlIGEgU1RVTiBleGNoYW5nZSwgYW5kIHRoZSBhZGRpdGlv
bmFsIGxhdGVuY3kgb2YgdGhpcyBleGNoYW5nZSBkaXNjb3VyYWdlcyBkZXBsb3ltZW50IG9mIGhv
c3QtYmFzZWQgc29sdXRpb25zLiAgVG8gbWluaW1pemUgdGhpcyBsYXRlbmN5LCBlbmdhZ2luZyB0
aG9zZSBtZWNoYW5pc21zIG1heSBuZWVkIHRvIGJlIGRvbmUgaW4gcGFyYWxsZWwgd2l0aCBvciBp
biBhZHZhbmNlIG9mIHRoZSBjb3JlIHByb3RvY29sIGV4Y2hhbmdlcyB3aXRoIHdoaWNoIHRoaXMg
bWV0YWRhdGEgd291bGQgYmUgc3VwcGxpZWQuDQpbTWVkXSBMb29rcyBnb29kIHRvIG1lLiBUaGFu
a3MuDQoNCkJUVywgdGhpcyBmYWxscyBpbnRvIHRoaXMgZ2VuZXJhbCBkaXNjdXNzaW9uIGluIGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2OTczOg0KDQogICBhLiAgVHJhZGUtb2Zmcy4g
IERvZXMgdGhlIHByb3RvY29sIG1ha2UgdHJhZGUtb2ZmcyBiZXR3ZWVuIHByaXZhY3kNCiAgICAg
ICBhbmQgdXNhYmlsaXR5LCBwcml2YWN5IGFuZCBlZmZpY2llbmN5LCBwcml2YWN5IGFuZA0KICAg
ICAgIGltcGxlbWVudGFiaWxpdHksIG9yIHByaXZhY3kgYW5kIG90aGVyIGRlc2lnbiBnb2Fscz8g
IERlc2NyaWJlDQogICAgICAgdGhlIHRyYWRlLW9mZnMgYW5kIHRoZSByYXRpb25hbGUgZm9yIHRo
ZSBkZXNpZ24gY2hvc2VuLg0KKiBhIG1pc2JlaGF2aW5nIG5vZGUgbWF5IGJlIHRlbXB0ZWQgdG8g
c3Bvb2YgdGhlIGRhdGEgdG8gYmUgaW5qZWN0ZWQuIEEgcmVtb3RlIGRldmljZSB0aGF0IHdpbGwg
dXNlIHRoYXQgZGF0YSB0byBlbmZvcmNlIHBvbGljaWVzIHdpbGwgYmUgYnJva2VuLg0KVGhpcyBw
b2ludCB3YXMgZGlzY3Vzc2VkIGV4dGVuc2l2ZWx5IGluIHRoZSBHRU9QUklWIHdvcmsgYW5kIGVz
c2VudGlhbGx5IGEgc2luZ2xlIGNhcnZlLW91dCB3YXMgbWFkZTogIGZvciBlbWVyZ2VuY3kgc2Vy
dmljZXMsIHdoZXJlIGZhbHNlbHkgYXNzZXJ0ZWQgbG9jYXRpb24gZGF0YSBjb3VsZCBiZSB1c2Vk
IHRvIFNXQVQgaW5kaXZpZHVhbHMgb3IgY29uc3VtZSBzYWZldHkgcmVzb3VyY2VzLiAgICBJIGRv
bid0IHRoaW5rIHRoYXQgZmFsbHMgaW50byB0aGlzIG5hcnJvdyBhZHZpY2UsIGJ1dCBJIHdvdWxk
IGJlIHdpbGxpbmcgdG8gYWRkIHNvbWV0aGluZyBsaWtlIHRoaXMgdG8gdGhlIHNlY3VyaXR5IGNv
bnNpZGVyYXRpb25zOg0KIk5vdGUgdGhhdCBzb21lIGVtZXJnZW5jeSBzZXJ2aWNlIHJlY2lwaWVu
dHMsIG5vdGFibHkgUFNBUHMgKFB1YmxpYyBTYWZldHkgQW5zd2VyaW5nIFBvaW50cykgbWF5IHBy
ZWZlciBkYXRhIHByb3ZpZGVkIGJ5IGEgbmV0d29yayB0byBkYXRhIHByb3ZpZGVkIGJ5IGVuZCBz
eXN0ZW0sIGJlY2F1c2UgYW4gZW5kIHN5c3RlbSBjb3VsZCB1c2UgZmFsc2UgZGF0YSB0byBhdHRh
Y2sgb3RoZXJzIG9yIGNvbnN1bWUgcmVzb3VyY2VzLiAgIFdoaWxlIHRoaXMgaGFzIHRoZSBjb25z
ZXF1ZW5jZSB0aGF0IHRoZSBkYXRhIGF2YWlsYWJsZSB0byB0aGUgUFNBUCBpcyBvZnRlbiBtb3Jl
IGNvYXJzZSB0aGFuIHRoYXQgYXZhaWxhYmxlIHRvIHRoZSBlbmQgc3lzdGVtLCB0aGUgcmlzayBv
ZiBmYWxzZSBkYXRhIGJlaW5nIHByb3ZpZGVkIGludm9sdmVkIGEgcmlzayB0byB0aGUgbGl2ZXMg
b2YgdGhvc2UgdGFyZ2V0ZWQuIg0KW01lZF0gVGhhbmsgeW91LiBQcm92aWRpbmcgUFNBUCBhcyBh
biBleGFtcGxlIGlzIE9LLCBidXQgSeKAmWQgbGlrZSB0aGUgaXNzdWUgdG8gYmUgY2FsbGVkIG91
dCBhcyBhIGdlbmVyaWMgb25lIHdoaWxlIFBTQVAgaXMgcHJvdmlkZWQgYXMgYW4gZXhhbXBsZS4g
V2hhdCBhYm91dCB0aGUgZm9sbG93aW5nOg0KDQoiTm90ZSB0aGF0IHNvbWUgc2VydmVycyAoZS5n
LiwgZW1lcmdlbmN5IHNlcnZpY2UgcmVjaXBpZW50cywgbm90YWJseSBQU0FQcyAoUHVibGljIFNh
ZmV0eSBBbnN3ZXJpbmcgUG9pbnRzKSBbUkZDNjQ0M10pIG1heSBwcmVmZXIgZGF0YSBwcm92aWRl
ZCBieSBhIG5ldHdvcmsgdG8gZGF0YSBwcm92aWRlZCBieSB0aGUgZW5kIHN5c3RlbSwgYmVjYXVz
ZSBhbiBlbmQgc3lzdGVtIGNvdWxkIHVzZSBmYWxzZSBkYXRhIHRvIGF0dGFjayBvdGhlcnMgb3Ig
Y29uc3VtZSByZXNvdXJjZXMuICBXaGlsZSB0aGlzIGhhcyB0aGUgY29uc2VxdWVuY2UgdGhhdCB0
aGUgZGF0YSBhdmFpbGFibGUgdG8gdGhlIHNlcnZlciBpcyBvZnRlbiBtb3JlIGNvYXJzZSB0aGFu
IHRoYXQgYXZhaWxhYmxlIHRvIHRoZSBlbmQgc3lzdGVtLCB0aGUgcmlzayBvZiBmYWxzZSBkYXRh
IGJlaW5nIHByb3ZpZGVkIGludm9sdmVkIGEgcmlzayB0byB0aGUgbGl2ZXMgb2YgdGhvc2UgdGFy
Z2V0ZWQuIg0KDQoNCkkgZG9uJ3QgdGhpbmsgdGhhdCBlbWVyZ2VuY3kgc2VydmljZSByZWNpcGll
bnRzIHNoaWZ0aW5nIHRvIGFuIGV4YW1wbGUgd29ya3MgaGVyZSwgYmVjYXVzZSBpdCBicm9hZGVu
cyB0aGUgY2FydmUgb3V0LiAgSW4gdGhlIGVtZXJnZW5jeSBzZXJ2aWNlcyBjYXNlLCB0aGUgcmVz
b3VyY2VzIGNvbnN1bWVkIGFyZSBmaXJlIHRydWNrcywgYW1idWxhbmNlcywgYW5kIHN3YXQgdGVh
bXMuICBGb3Igb3RoZXIgc2VydmVycywgcmVzb3VyY2VzIGNvbnN1bWVkIGNvdWxkIHNpbXBseSBi
ZSAgQ1BVIGN5Y2xlcyBvciBkaXNrOyB0aGF0J3MgcmVhbGx5IG5vdCB0aGUgc2FtZS4gIEJhbGFu
Y2luZyBsb2NhdGlvbiBjb25zZW50IHJlcXVpcmVtZW50cyBhZ2FpbnN0IG9uZSB3YXMgYWdyZWVk
OyBiYWxhbmNpbmcgaXQgYWdhaW5zdCB0aGUgb3RoZXIgd2FzIG5vdC4NCg0KW01lZF0gUmVzb3Vy
Y2VzIG1heSBub3QgYmUgcmVzdHJpY3RlZCB0byBDUFUgb3IgZGlzayBidXQgbWF5IGJlIGdyYW50
aW5nIGFjY2VzcyB0byB0aGUgc2VydmljZSAoZS5nLiwgZG93bmxvYWQgYSBmaWxlIHdoZW4gYSBx
dW90YSBwZXIgc291cmNlIGFkZHJlc3MgaXMgZW5mb3JjZWQpLiBJdCBjYW4gYmUgd2hhdGV2ZXIg
dGhlIHNlcnZlcnMgY29uc2lkZXIgdG8gYmUgY3JpdGljYWwgZm9yIHRoZW07IGl0IGlzIHVwIHRv
IHRoZSB0YXN0ZSBvZiB0aGUgc2VydmljZSBkZXNpZ24gdG8gY2hhcmFjdGVyaXplIGl0LiBUaGUg
TkVXIHdvcmRpbmcgcHJvcG9zZWQgYWJvdmUgaXMgdGVjaG5pY2FsbHkgY29ycmVjdC4gUGxlYXNl
IHJlY29uc2lkZXIgYWRkaW5nIGl0IHRvIHRoZSBkcmFmdC4NCg0KDQoqIGl0IHdhcyByZXBvcnRl
ZCBpbiB0aGUgcGFzdCB0aGF0IHNvbWUgYnJvd3NlcnMgbGVhayB0aGUgTVNJU0ROIGFuZCBvdGhl
ciBzZW5zaXRpdmUgZGF0YS4NClRoaXMgaXMgdHJ1ZSwgYnV0IGl0IHNlZW1zIHRvIG1lIHVucmVs
YXRlZCB0byB0aGUgcG9pbnQgb2YgdGhlIGRvY3VtZW50Lg0KW01lZF0gSXQgaXMgcmVsYXRlZCBi
ZWNhdXNlIGJsaW5kbHkgdHJ1c3RpbmcgYW4gYXBwbGljYXRpb24gY2xpZW50IChhbmQgc2VydmVy
KSBoYXMgaXRzIG93biBwcml2YWN5IHJpc2tzLiBUaGlzIGlzIGV2ZW4gZXhhY2VyYmF0ZWQgZ2l2
ZW4gdGhlIHJpY2ggZGF0YSB0aGF0IGlzIGF2YWlsYWJsZSB0byBhbiBhcHBsaWNhdGlvbiBjbGll
bnQgYW5kIGFsc28gYmVjYXVzZSBvZiB0aGUgdmlzaWJpbGl0eSBvbiB2YXJpb3VzIGxheWVycyBh
dmFpbGFibGUgdG8gYW4gYXBwbGljYXRpb24gc2VydmVyLg0KDQpJIGFncmVlIHRoYXQgaXQgaGFz
IGl0cyBvd24gcHJpdmFjeSByaXNrcywgYnV0IEkgZG9uJ3QgdGhpbmsgdGhpcyBpcyB0aGUgZG9j
dW1lbnQgdGhhdCBzaG91bGQgZXhwbG9yZSB0aGVtLg0KW01lZF0gWW91IGRvbuKAmXQgbmVlZCB0
byBleHBsb3JlIHRoZW0sIGJ1dCB0byBhZGQgb25lIG9yIHR3byBzZW50ZW5jZXMgdG8gcmVtaW5k
IHRoYXQgcHJpdmFjeSBsZWFrcyBhcmUgc3RpbGwgYSB2YWxpZCBjb25jZXJuIGV2ZW4gaWYgb25s
eSBjbGllbnRzIGFyZSBzdXBwbHlpbmcgZGF0YSB3aXRob3V0IHRoZSBoZWxwIG9mIGFuIG9uLXBh
dGggbmV0d29yayBkZXZpY2UuDQpGcm9tIHRoYXQgZmxvdyBzb21lIG9mIHlvdXIgb3RoZXIgY29u
Y2VybnMgYWJvdXQgYXVkaWVuY2UsIGF0IGxlYXN0IGFzIEkgdW5kZXJzdGFuZC4gIEFzIHdyaXR0
ZW4sIHRoaXMgaXMgbmFycm93IGFkdmljZSBmb3IgYSBicm9hZCBhdWRpZW5jZTogYmFzaWNhbGx5
LCBhbnlvbmUgd2hvIHdvdWxkIGNvbnNpZGVyIHRoZSBmb3JtIG9mIG1ldGFkYXRhIGluc2VydGlv
biBpdCBkZXNjcmliZXMuICBZb3Ugd291bGQsIGlmIEkgdW5kZXJzdGFuZCB5b3UsIHByZWZlciBh
IG5hcnJvd2VyIGRlc2NyaXB0aW9uIG9mIHRoZSBhdWRpZW5jZSBpbiBhIGxhcmdlciBjb250ZXh0
Lg0KDQpbTWVkXSBUaGUga2V5IHBvaW50IGhlcmUgaXMgYWJvdXQgdGhlIHByYWN0aWNhbGl0eSBv
ZiBpbXBsZW1lbnRpbmcgdGhlIGFkdmljZSBOT1QgY2hhbmdpbmcgdGhlIHNjb3BlLiBGb3IgZXhh
bXBsZSwgdGhlIGRvY3VtZW50IHNheXMgdGhhdCBpdCBpcyBiZXR0ZXIgdGhhdCBhIGhvc3QgaXMg
aW5qZWN0aW5nIHRoZSBkYXRhIGJ1dCB0aGUgZG9jdW1lbnQgZG9lcyBub3QgcXVlc3Rpb24gd2hl
dGhlciB0aGF0IHN1cHBsaWVkIGRhdGEgY2FuIGJlIHRydXN0ZWQgb3Igbm90LA0KDQpCcm9hZGVu
aW5nIHRoaXMgYSBiaXQsIHlvdSdyZSBsb29raW5nIGF0IHR3byBjYXNlczogb25lIGluIHdoaWNo
IHRoZSBkYXRhIHRoZSBob3N0IGhhcyBpcyB3cm9uZyBhbmQgb25lIGluIHdoaWNoIHRoZXJlIGlz
IGFuIGFkdmVyc2FyaWFsIHJlbGF0aW9uc2hpcC4gIEZvciB0aGUgZmlyc3QgY2FzZSwgd2UgY2Fu
IGFkZCB0ZXh0IHNheWluZyB0aGF0IHdoZW4gYW4gZW5kIHN5c3RlbSBzdXBwbGllcyBkYXRhIGl0
IGlzIHRoZSBlbmQgc3lzdGVtJ3MgcmVzcG9uc2liaWxpdHkgdG8gZW5zdXJlIHRoYXQgaXQgaXMg
Y29ycmVjdDsgZG9uJ3QgdXNlIGEgU1RVTiByZXN1bHQgZnJvbSBsYXN0IHdlZWsgYXMgZnJlc2gs
IGZvciBleGFtcGxlLg0KW01lZF0gT0suDQoNCiAgRm9yIHRoZSBzZWNvbmQgY2FzZSwgIGluIHdo
aWNoIHRoZSBzZXJ2ZXIgdHJlYXRzIHVzZXIgc3VwcGxpZWQgZGF0YSBhcyBwb3RlbnRpYWxseSBt
aXNsZWFkaW5nIGJlY2F1c2UgdGhlIHVzZXIgbWF5IHdpc2ggdG8gY2lyY3VtdmVudCByZXN0cmlj
dGlvbnMsIEknbGwgcG9pbnQgb3V0IHRoZSBXaWtpbWVkaWEgZXhhbXBsZSBkZW1vbnN0cmF0ZXMg
dGhhdCBzaW1wbHkgc2hpZnRpbmcgdGhlIHRydXN0IHRvIGEgbWlkLXBvaW50IGVudGl0eSBkb2Vz
bid0IHdvcms7IGl0IGhhcyB0byBiZSBzaGlmdGVkIHRvIGFuIGVudGl0eSB3aXRoaW4gdGhlIHRy
dXN0IGRvbWFpbiBvZiB0aGUgc2VydmVyLiAgU28gdGhlIHF1ZXN0aW9uIGlzbid0IHJlYWxseSAi
ZW5kLXVzZXIgc3lzdGVtIHN1cHBsaWVkIGRhdGEgY2FuIGJlIHRydXN0ZWQgb3Igbm90IiwgdGhl
IHNhbWUgcXVlc3Rpb24gYXBwbGllcyB0byB3aG9tZXZlciBzdXBwbGllcyB0aGUgZGF0YS4NCltN
ZWRdIEZ1bGx5IGFncmVlLiBIYXZpbmcgc29tZSB0ZXh0IHRvIHJlY29yZCB0aGF0IHRoZSBjb25j
ZXJuIGFwcGxpZXMsIGluY2x1ZGluZyBmb3IgY2xpZW50IHN1cHBsaWVkIGRhdGEuDQoNCg0Kb3Ig
aG93IHRoZSBjb25zZW50IHdpbGwgYmUgb2J0YWluZWQgZnJvbSBhIHVzZXIuDQoNCllvdSdyZSBy
aWdodCB0aGF0IEknbSBsZWF2aW5nIGFzaWRlIHRoZSBxdWVzdGlvbiBvZiBob3cgdGhlIHVzZXIg
c2V0cyB0aGUgcG9saWNpZXMsIGJlY2F1c2UgaXQgbWF5IHZhcnkgYnkgcHJvdG9jb2wgYW5kIHR5
cGUgb2YgZGV2aWNlIHRvbyBtdWNoIHRvIG1ha2UgZ2VuZXJhbCBhZHZpY2UgdXNlZnVsLiAgSWYg
eW91IHdvdWxkIGxpa2UgbWUgdG8gYWRkIGFuIGV4cGxpY2l0IHN0YXRlbWVudCB0byB0aGF0IGVm
ZmVjdCwgSSBhbSBoYXBweSB0byBub3RlIHRoYXQgaXQgaXMgbm90IGNvdmVyZWQuDQpbTWVkXSBQ
bGVhc2UgYWRkIHNvbWUgdGV4dCBhYm91dCB0aGlzIHBvaW50LiBUaGFuayB5b3UuDQoNCg0KSW4g
Z2VuZXJhbCwgdGhlIHBvaW50IG9mIHRoZSBkb2N1bWVudCBpcyB0aGF0IHRoZSBob3N0IHNob3Vs
ZCBiZSBhYmxlIHRvIG9taXQgdGhlIGRhdGEgd2l0aG91dCBtaWQtbmV0d29yayBkZXZpY2VzIGFk
ZGluZyBpdCBiYWNrLiAgVGhhdCdzIHRoZSBwb2ludCBvZiBwcm90ZWN0aW5nIHRoZSB0cmFmZmlj
IGluIHRoZSBmaXJzdCBwbGFjZSwgYWZ0ZXIgYWxsLiAgSSBhbSBzYXlpbmcgdGhhdCBpZiB0aGUg
cHJvdG9jb2xzIHJlcXVpcmUgdGhlIGRhdGEsIHRoZW4gZ2V0dGluZyBpdCBmcm9tIHRoZSBlbmQg
aG9zdCBoYXMgYmV0dGVyIHByaXZhY3kgcHJvcGVydGllcyB0aGFuIGdldHRpbmcgZnJvbSBpdCBm
cm9tIG1pZC1uZXR3b3JrIGVudGl0aWVzLg0KW01lZF0gSeKAmW0gbm90IHN1cmUgd2UgY2FuIGhh
dmUgc3VjaCBnZW5lcmFsIHN0YXRlbWVudCBiZWNhdXNlIHRoZSBkYXRhIG1heSBub3QgYmUgYXZh
aWxhYmxlIChlLmcuLCBESENQIGZvciBleGFtcGxlKSB0byBjbGllbnRzICsgdGhlIGRhdGEgc3Vw
cGxpZWQgYnkgY2xpZW50cyAod2hlbiBwb3NzaWJsZSkgbWF5IG5vdCBiZSByZWxpYWJsZSArIGVu
Zm9yY2luZyBwb2xpY2llcyBiYXNlZCBvbiBjbGllbnQtc3VwcGxpZWQgZGF0YSBtYXkgaGF2ZSBp
bXBsaWNhdGlvbiBvbiBvdGhlciB1c2VycyAoZS5nLiwgc3Bvb2ZpbmcgWEZGIGZvciBleGFtcGxl
KS4gT2J2aW91c2x5LCBnZXR0aW5nIHNvbWUgb2YgdGhlIGluZm9ybWF0aW9uIGZyb20gYSBjbGll
bnQgbWF5IGhhdmUgaW1wbGljYXRpb25zIG9uIFFvReKApnRoZSB1c2VyIG5lZWRzIHRvIHVuZGVy
c3RhbmQgdGhlIHJvb3QgY2F1c2VzIG9mIGEgZGVncmFkYXRpb24gb2YgUW9FLiBPZiBjb3Vyc2Us
IHRoZXNlIGltcGxpY2F0aW9ucyBtYXkgbm90IGJlIG5ldyBmb3IgdXNlcnMgd2hvIGFyZSBmYW1p
bGlhciB3aXRoIGRpc2FibGluZyBKYXZhIHNjcmlwdHMgYW5kIGNpZS4NCg0KRm9yIGV4YW1wbGUs
IHRoZSBkb2N1bWVudCBzdGF0ZXMgdGhhdCB0aGUgaW5mb3JtYXRpb24gaW4gYSBGb3J3YXJkLUZv
ciBoZWFkZXIgY2FuIGJlIHN1cHBsaWVkIGJ5IHRoZSBob3N0IGl0c2VsZiBhbmQgdGhlbiBjb21t
dW5pY2F0ZWQgdG8gYSByZW1vdGUgY29uc3VtZXIuIFRoaXMgaXMgaW5kZWVkIHBvc3NpYmxlLCBi
dXQgYmVjYXVzZSBvZiBhYnVzaW5nIGhvc3RzIHNvbWUgc2VydmVycyBpbXBsZW1lbnQgd2hpdGVs
aXN0cyB0byB0cnVzdCBwcm94aWVzOyBzZWUgaHR0cHM6Ly9tZXRhLndpa2ltZWRpYS5vcmcvdy9l
eHRlbnNpb25zL1RydXN0ZWRYRkYvdHJ1c3RlZC1ob3N0cy50eHQuDQoNCg0KVGhlIFdpa2ltZWRp
YSBjYXNlIGlzIGEgdmVyeSBpbnRlcmVzdGluZyBvbmUgdG8gcmFpc2UsIGJlY2F1c2UgaXQgZGVy
aXZlcyBmcm9tIGEgc2V0IG9mIGFzc3VtcHRpb25zIGFib3V0IHRoZSBuZXR3b3JrIHRoYXQgYXJl
IHNvbWV3aGF0IGZsYXdlZCBhbmQgdGhlbiBhdHRlbXB0cyB0byBwYXRjaCB0aG9zZSBmbGF3cyBp
biB3YXlzIHRoYXQgYWN0dWFsbHkgZGFtYWdlIHRoZSBtZWNoYW5pc21zIG9mIHRoZSBzeXN0ZW0g
dGhleSBvcmlnaW5hbGx5IGJ1aWx0Lg0KV2lraW1lZGlhIHdhbnRzIHRvIGFsbG93IGZvbGtzIHRv
IGVkaXQgd2l0aG91dCBsb2dpbiBjcmVkZW50aWFscy4gIFRoaXMgYWxsb3dzIGZvciBhbm9ueW1v
dXMgdXNlcnMgdG8gbWFrZSBjb3JyZWN0aW9ucyBvciBhZGRpdGlvbnM7IHRoaXMgaXMgYSBnb2Fs
LiAgVGhlIGNvbnNlcXVlbmNlIG9mIHRoYXQgZ29hbCBiZWluZyBhY2hpZXZlZCBpcyB0aGF0IHRy
b2xscyBvciBtYWxpY2lvdXMgZWRpdG9ycyBjYW4gaGF2ZSBhdCBhbnl0aGluZyB0aGV5IHdhbnQu
DQpSYXRoZXIgdGhhbiBpbnN0aXR1dGUgY3JlZGVudGlhbHMgYW5kIEFDTHMsIFdpa2ltZWRpYSBh
dHRlbXB0cyB0byBzdWJzdGl0dXRlIGJsb2NraW5nIGJ5IElQIGZvciBibG9ja2luZyBieSBjcmVk
ZW50aWFsLiAgVGhlIHByb3BlcnR5IHRoZXkgYXJlIGxvb2tpbmcgZm9yIGluIElQcyBpcyBub3Qg
cmVhbGx5IHRoZXJlLCB0aG91Z2g6ICB0aGV5IGFyZSBub3QgdW5pcXVlIHRvIGluZGl2aWR1YWxz
LCBlc3BlY2lhbGx5IG92ZXIgdGltZS4NCg0KVGhpcyBkYW1hZ2VzIHRob3NlIHdobyBzaGFyZSBJ
UCBhZGRyZXNzZXMgKGR1ZSB0byBOQVRzIG9yIHByb3hpZXMpLiAgQXMgZmFyIGFzIEkgY2FuIHRl
bGwsIHRoZSBOQVQgcHJvYmxlbSBpcyBzaW1wbHkgdHJlYXRlZCBhcyBjb2xsYXRlcmFsIGRhbWFn
ZS4gIEZvciB0aGUgcHJveGllcywgdGhleSBhdHRlbXB0IHRvIHdvcmsgYXJvdW5kIHRoZSBkYW1h
Z2UgdXNpbmcgWEZGLiAgVGhhdCdzIHNwb29mYWJsZSwgdGhvdWdoLCBzbyB0aGV5IGF0dGVtcHQg
dG8gbGltaXQgaXQgdG8gc3BlY2lmaWMgcHJveGllcyB3aG9zZSBYRkYgdGhleSB0cnVzdC0tbWFu
eSBvZiB3aGljaCByZXF1aXJlIGxvZ2lucy4gIFRoYXQgc2hpZnRzIHRoZSBpbmZvcm1hdGlvbiBh
Ym91dCB3aG8gaXMgZWRpdGluZyBXaWtpcGVkaWEgb3V0IG9mIHRoZWlyIGhhbmRzLCBidXQgbGVh
dmVzIGl0IGluIHRoZSBuZXR3b3JrIGFuZCB0aHVzIG5vdCB0cnVseSBhbm9ueW1vdXMuICBJIHVu
ZGVyc3RhbmQgdGhlIGVuZ2luZWVyaW5nIGJhbGFuY2UgdGhleSBhcmUgdHJ5aW5nIHRvIHN0cmlr
ZSwgYnV0IEknbSBub3Qgc3VyZSBJIGNhbiByZWNvbW1lbmQgdGhlaXIgc29sdXRpb24uDQoNCltN
ZWRdIEnigJltIG5vdCByZWNvbW1lbmRpbmcgdGhlaXIgc29sdXRpb24gZWl0aGVyLCBidXQgSeKA
mW0gdHJ5aW5nIHRvIHJhaXNlIHRoZSBwb2ludCB0aGF0IGFuIGVuZ2luZWVyaW5nIGJhbGFuY2Ug
aXMgb3V0IHRoZXJlLiBBQ0tpbmcgdGhhdCBkZXBsb3ltZW50IHJlYWxpdHkgaXMgYmV0dGVyIHRo
YW4gaWdub3JpbmcgaXQuDQoNCg0KVGhlIGRlcGxveW1lbnQgY29uc2lkZXJhdGlvbnMgdGV4dCBp
cyBtZWFudCB0byBwb2ludCBvdXQgdGhlIGVuZ2luZWVyaW5nIGJhbGFuY2UuICBJJ20gaGFwcHkg
dG8gYWRkIHRoZSB0ZXh0IG5vdGVkIGFib3ZlIChvbiBsYXRlbmN5LCB0aGUgZW5kIHVzZXIgcmVz
cG9uc2liaWxpdHkgZm9yIGNvcnJlY3QgZGF0YSwgdGhlIFBTQVAgY2FydmUgb3V0LCBhbmQgdGhl
IGV4cGxpY2l0IG5vdGUgdGhhdCB0aGUgZG9jdW1lbnQgZG9lcyBub3QgdHJlYXQgaG93IHRvIG9i
dGFpbiBjb25zZW50IGZyb20gYSB1c2VyIHNvIHRoYXQgYW4gZW5kIHN5c3RlbSBjYW4gc3VwcGx5
IGRhdGEpLg0KW01lZF0gT2ssIHRoYW5rcy4NCkknbSBsZXNzIGhhcHB5IHRvIGFkZCBsYW5ndWFn
ZSBvbiBhZHZlcnNhcmlhbCB0cmVhdG1lbnQgb2YgY2xpZW50LXN1cHBsaWVkIGRhdGEuICBUaGlz
IGlzIHBhcnRseSBiZWNhdXNlIG1hbnkgb2YgdGhlIHN5c3RlbXMgd2hpY2ggdXNlIG5ldHdvcmst
c3VwcGxpZWQgZGF0YSBhcmUgYmFzZWQgb24gYSBtaXN1bmRlcnN0YW5kaW5nIG9mIHRoZSBwcm9w
ZXJ0aWVzIG9mIHRoZSBkYXRhIGJlaW5nIGFkZGVkLg0KW01lZF0gSSBhZ3JlZSB0aGlzIG1heSBi
ZSB0aGUgY2FzZSBmb3Igc29tZSBvZiB0aGVtLCBidXQgbm90IGFsbC4NCiAgSXQgaXMgcGFydGx5
IGJlY2F1c2UgdGhlIGFkdmVyc2FyaWFsIHJlbGF0aW9uc2hpcCBjYW4gZXh0ZW5kIHRvIG5ldHdv
cmstc3VwcGxpZWQgZGF0YS4gIEl0IGlzIGFsc28gYmVjYXVzZSBhIGZhaXIgZmV3IG9mIHRoZW0g
YXJlIHNpbXBseSBzZWN1cml0eSB0aGVhdGVyLiAgSWYgeW91IGhhdmUgYSBzcGVjaWZpYyBlZGl0
IHlvdSB3b3VsZCBsaWtlIHRvIHByb3Bvc2UsIHRob3VnaCwgSSB3aWxsIGNvbnNpZGVyIGl0Lg0K
VGhhbmtzIGFnYWluLA0KVGVkDQo=

--_000_787AE7BB302AE849A7480A190F8B933009E1BDA0OPEXCLILMA3corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIg
MiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3Nl
LTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25z
b2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0
aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJn
aW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dl
ZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5
bGUtbGluazoiUHLDqWZvcm1hdMOpIEhUTUwgQ2FyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVy
IE5ldyI7fQ0KcC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5Nc29MaXN0UGFyYWdyYXBoLCBkaXYuTXNv
TGlzdFBhcmFncmFwaA0KCXttc28tc3R5bGUtcHJpb3JpdHk6MzQ7DQoJbWFyZ2luLXRvcDowY207
DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltYXJnaW4tYm90dG9tOjBjbTsNCgltYXJnaW4tbGVmdDoz
Ni4wcHQ7DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9u
dC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpzcGFuLmdtYWlsLQ0KCXttc28t
c3R5bGUtbmFtZTpnbWFpbC07fQ0Kc3Bhbi5QcmZvcm1hdEhUTUxDYXINCgl7bXNvLXN0eWxlLW5h
bWU6IlByw6lmb3JtYXTDqSBIVE1MIENhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJQcsOpZm9ybWF0w6kgSFRNTCI7DQoJZm9udC1mYW1pbHk6IkNvbnNvbGFz
Iiwic2VyaWYiOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkZSO30NCnNwYW4uRW1haWxTdHlsZTIw
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVy
IE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6
bm9ybWFsO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0K
CW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2VjdGlv
bjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZpbml0aW9ucyAqLw0KQGxpc3Qg
bDANCgl7bXNvLWxpc3QtaWQ6MjA0NzY3NDEyMjsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCglt
c28tbGlzdC10ZW1wbGF0ZS1pZHM6LTgzNTQ3MTYgNjg1NjQ4NzAwIDY3ODk1Mjk5IDY3ODk1MzAx
IDY3ODk1Mjk3IDY3ODk1Mjk5IDY3ODk1MzAxIDY3ODk1Mjk3IDY3ODk1Mjk5IDY3ODk1MzAxO30N
CkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNv
LWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1u
dW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5
OlN5bWJvbDsNCgltc28tZmFyZWFzdC1mb250LWZhbWlseTpDYWxpYnJpOw0KCW1zby1iaWRpLWZv
bnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCkBsaXN0IGwwOmxldmVsMg0KCXttc28tbGV2
ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxl
dmVsMw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
74KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9
DQpAbGlzdCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1z
by1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWls
eTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNw0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0K
CW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBs
MDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIg
TmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28t
bGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250
LWZhbWlseTpXaW5nZGluZ3M7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowY207fQ0KdWwNCgl7bWFy
Z2luLWJvdHRvbTowY207fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtl
bmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJl
ZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0
PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRlIiIGxpbms9ImJsdWUi
IHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+SGkgVGVkLA0KPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPlBsZWFzZSBz
ZWUgaW5saW5lLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPkNoZWVycyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPk1lZDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0
Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0
REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhv
bWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RGUmbmJzcDs6PC9zcGFuPjwvYj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IFRlZCBIYXJkaWUgW21haWx0bzp0ZWQuaWV0ZkBnbWFp
bC5jb21dDQo8YnI+DQo8Yj5FbnZvecOpJm5ic3A7OjwvYj4gamV1ZGkgMiBtYXJzIDIwMTcgMTk6
MDI8YnI+DQo8Yj7DgCZuYnNwOzo8L2I+IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE48YnI+DQo8
Yj5DYyZuYnNwOzo8L2I+IGlldGZAaWV0Zi5vcmc7IGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFk
YXRhLWluc2VydGlvbkBpZXRmLm9yZzxicj4NCjxiPk9iamV0Jm5ic3A7OjwvYj4gUmU6IExhc3Qg
Q2FsbDogJmx0O2RyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbi0wNS50eHQm
Z3Q7IChEZXNpZ24gY29uc2lkZXJhdGlvbnMgZm9yIE1ldGFkYXRhIEluc2VydGlvbikgdG8gSW5m
b3JtYXRpb25hbCBSRkM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj53aW5nIGFyZSBt
aXNzaW5nIGZyb20gdGhlIGRvY3VtZW50Ojwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICND
Q0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDtt
YXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgd2luZG93dGV4dCAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQu
MHB0O2JvcmRlci1jb2xvcjotbW96LXVzZS10ZXh0LWNvbG9yIC1tb3otdXNlLXRleHQtY29sb3Ig
LW1vei11c2UtdGV4dC1jb2xvciBibHVlIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+SXQncyBkaWZmaWN1bHQgdG8gc2F5IGhvdyBz
b21ldGhpbmcgd2lsbCBiZSB1c2VkIGluIHRoZSBmdXR1cmUuJm5ic3A7PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bWFy
Z2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01l
ZF0gQW4gYWR2aWNlIHRoYXQgaXMgbm90IGltcGxlbWVudGFibGUgbWFrZXMgbW9yZSB0cm91Ymxl
cywgSU1ITy48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U29ycnksIEkgdGhvdWdodCB5b3Ugd2Vy
ZSBhc2tpbmcgd2hhdCB3Z3Mgb3IgcHJvdG9jb2xzIHBsYW5uZWQgdG8gcmVmZXJlbmNlIHRoaXMu
Jm5ic3A7IEZvciB0aGF0LCBJIGRvbid0IGtub3cuJm5ic3A7PHNwYW4gc3R5bGU9ImNvbG9yOmJs
YWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291
cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIE9LLiBJTUhPIGxhY2tpbmcgc3VjaCBj
b25zaWRlcmF0aW9ucywgdGhlcmUgaXMgYSBoaWdoIHJpc2sgdGhhdCB0aGUgYWR2aWNlIHdpbGwg
YmUgbG9zdCBvciB0aGF0IGl0IGNhbiBiZSB1c2VkIGFzIGEgcGVybWFuZW50IERJU0NVU1MgcG9p
bnQgaW4gbGF0ZXINCiBzdGFnZXMgb2YgcHJlcGFyaW5nIGRvY3VtZW50cy4gSeKAmWQgcHJlZmVy
IGlmIGFjdGlvbmFibGUgcG9pbnRzIHRvIGJlIGNvbnNpZGVyZWQgYnkgV0dzIGFuZCBkb2N1bWVu
dCBhdXRob3JzIGluIGVhcmx5IHN0YWdlcy4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiPlRoZSBpbnRlbnQgaXMgdGhhdCBpdCBpcyBpbmZvcm1hdGlvbiB1c2VmdWwgdG8gdGhv
c2UgY29uc2lkZXJpbmcgd2hldGhlciByZXN0b3JpbmcgbWV0YWRhdGEgbG9zdCB0byBlbmNyeXB0
aW9uIGluIG1pZC1uZXR3b3JrIGlzIHRoZSByaWdodCB3YXkgdG8gZ28uPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OmJsYWNrIj5bTWVkXSBUaGlzIGlzIGFub3RoZXIgYXNzdW1wdGlvbiBpbiB0aGUgZG9jdW1lbnQg
dGhhdCBJIGRpc2FncmVlIHdpdGg6IEl0IHNlZW1zIHRoYXQgeW91IGFzc3VtZSB0aGF0IGFuIG9u
LXBhdGggZGV2aWNlLCB0aGF0IGluc2VydHMgbWV0YWRhdGEsIGlzIG5lY2Vzc2FyaWx5DQogUkVT
VE9SSU5HIGJhY2sgdGhhdCBpbmZvcm1hdGlvbi4gVGhpcyBpcyBub3QgdHJ1ZSBmb3IgbWFueSBl
ZmZvcnRzOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBo
IiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+PCFb
aWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OlN5bWJvbDtjb2xvcjpibGFjayI+PHNwYW4gc3R5bGU9Im1zby1saXN0
Oklnbm9yZSI+wrc8c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4m
cXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0K
PC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+QSBGb3J3YXJkLUZvciBoZWFkZXIgaW5zZXJ0ZWQgYnkgYSBwcm94eSBkb2VzIG5v
dCByZXN0b3JlIGFueSBkYXRhOyBpdCBkb2VzIG9ubHkgcmV2ZWFsIGRhdGEgdGhhdCBpcyBhbHJl
YWR5IHByZXNlbnQgaW4gdGhlIHBhY2tldCBpc3N1ZWQgYnkgdGhlDQogY2xpZW50IGl0c2VsZi48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9
InRleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPjwhW2lmICFzdXBw
b3J0TGlzdHNdPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTpTeW1ib2w7Y29sb3I6YmxhY2siPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUi
PsK3PHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48
L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PkFuIGFkZHJlc3Mgc2hhcmluZyBkZXZpY2UsIHVuZGVyIGZvciBleGFtcGxlIERTLUxpdGUgKFJG
QzYzMzMpLCB0aGF0IGluc2VydHMgdGhlIHNvdXJjZSBJUHY2IHByZWZpeCBpbiB0aGUgVENQIEhP
U1RfSUQgb3B0aW9uIChSRkM3OTc0KSBpcyBub3QgUkVTVE9SSU5HDQogYW55IGRhdGEuIFRoZSBj
b250ZW50IG9mIHRoYXQgVENQIG9wdGlvbiBpcyBhbHJlYWR5IHZpc2libGUgaW4gdGhlIHBhY2tl
dCBzZW50IGJ5IHRoZSBob3N0Lg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJ0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxl
dmVsMSBsZm8xIj48IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6U3ltYm9sO2NvbG9yOmJsYWNrIj48c3BhbiBz
dHlsZT0ibXNvLWxpc3Q6SWdub3JlIj7CtzxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1Rp
bWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5TZXJ2aWNlIEZ1bmN0aW9uIENoYWluaW5nIFdHICg8YSBo
cmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL3dnL3NmYy9hYm91dC8iPmh0dHBzOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvd2cvc2ZjL2Fib3V0LzwvYT4pIGlzIGRlZmluaW5nIGFuDQog
YXJjaGl0ZWN0dXJlIHRvIGNvbW11bmljYXRlIG1ldGFkYXRhIGJ5IG9uLXBhdGggZGV2aWNlczsg
dGhhdCBtZXRhZGF0YSBpcyBpbnNlcnRlZCBhdCB0aGUgbmV0d29yayBzaWRlLiBCb3JkZXIgbm9k
ZXMgd2lsbCBtYWtlIHN1cmUgdGhhdCBkYXRhIGlzIHN0cmlwcGVkIGJlZm9yZSBmb3J3YXJkaW5n
IHBhY2tldHMgdG8gdGhlIHVsdGltYXRlIGRlc3RpbmF0aW9ucy4gVGhlIG1ldGFkYXRhIGNhbiBi
ZSBhIHN1YnNjcmliZXItaWQsIGEgcG9saWN5LWlkLA0KIGV0Yy48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MTYuOHB0Ij48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+U28gd2hlbiBk
cmFmdC1oYXJkaWUtKiBzYXlzOiDigJw8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPkRvIG5vdCBh
ZGQgbWV0YWRhdGEgdG8gZmxvd3MgYXQgaW50ZXJtZWRpYXJ5IGRldmljZXMgdW5sZXNzPG86cD48
L286cD48L3NwYW4+PC9wcmU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiPiZuYnNwOyZuYnNwOyBhIHBvc2l0aXZlIGFmZmlybWF0aW9uIG9mIGFwcHJvdmFsIGZv
ciByZXN0b3JhdGlvbiBoYXMgYmVlbiByZWNlaXZlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7IGZy
b20gdGhlIGFjdG9yIHdob3NlIGRhdGEgd2lsbCBiZSBhZGRlZC48L3NwYW4+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj7igJ08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
bGVmdDoxNi44cHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+KDEpIERvIHlv
dSBhc3N1bWUgdGhhdCB0aGUgc2FtcGxlIGV4YW1wbGVzIEkgbGlzdGVkIGFib3ZlIGZhbGwgdW5k
ZXIgeW91ciBhZHZpY2U/PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjE2LjhwdCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OmJsYWNrIj4oMikgSG93IGFuIG9uLXBhdGggZGV2aWNlIHdpbGwga25vdyB0aGUgZGF0YSBpdCBp
bnRlbmRzIHRvIGluc2VydCBpcyBhIOKAnHJlc3RvcmF0aW9u4oCdPzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
bGVmdDoxNi44cHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+KDMpIERvZXMg
aXQgbWVhbiB0aGF0IGZvciBuZXcgZGF0YSAoaS5lLiwgdGhhdCBhcmUgbm90IHJlc3RvcmF0aW9u
KSwgb24tcGF0aCBkZXZpY2VzIGFyZSBmcmVlIHRvIGRvIHdoYXRldmVyIHRoZXkgd2FudD8gRm9y
IG1lLA0KIHRoaXMgaXMgdW5kZXNpcmFibGUuIFRoZXJlIGlzIGEgdm9pZCB0aGVyZS4gQSBzdGF0
ZW1lbnQgdG8gcmVxdWlyZSB0aG9zZSBuZXR3b3JrcyB0byBhdm9pZCBsZWFraW5nIHByaXZhY3kg
aW5mb3JtYXRpb24gbXVzdCBiZSBpbmNsdWRlZC4NCjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+
Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PkFub3RoZXIgYXNzdW1wdGlvbiBpcyBtYWRlIGhlcmU6DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7IEluc3RlYWQsIGRlc2lnbiB0aGUgcHJvdG9j
b2wgc28gdGhhdCB0aGUgYWN0b3IgY2FuIGFkZCBzdWNoIG1ldGFkYXRhPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJz
cDsmbmJzcDsgdGhlbXNlbHZlcyBzbyB0aGF0IGl0IGZsb3dzIGVuZC10by1lbmQsIHJhdGhlciB0
aGFuIHJlcXVpcmluZyB0aGU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyBhY3Rpb24gb2Ygb3RoZXIg
cGFydGllcy4mbmJzcDsgSW4gYWRkaXRpb24gdG8gaW1wcm92aW5nIHByaXZhY3ksIHRoaXM8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiPiZuYnNwOyZuYnNwOyBhcHByb2FjaCBlbnN1cmVzIGNvbnNpc3RlbnQgYXZhaWxhYmls
aXR5IGJldHdlZW4gdGhlIGNvbW11bmljYXRpbmc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyBwYXJ0
aWVzLCBubyBtYXR0ZXIgd2hhdCBwYXRoIGlzIHRha2VuLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1
b3Q7Ij5UaGlzIHRleHQgY2xhaW1zIHRoYXQgcHJvdmlkaW5nIGRhdGEgYnkgdGhlIGVuZHBvaW50
IGVuc3VyZXMgYSDigJxjb25zaXN0ZW50IGF2YWlsYWJpbGl0eeKAnSBvZiB0aGF0IGluZm9ybWF0
aW9uLiBUaGlzIGlzIGJyb2tlbiBmb3IgYSBtdWx0aS1ob21lZCBob3N0IHRoYXQgdXNlcyBmb3Ig
ZXhhbXBsZQ0KIEZvcndhcmQtRm9yIGhlYWRlcjogT2J2aW91c2x5LCB0aGUgY29udGVudCBvZiB0
aGUgaGVhZGVyIGlmIGluamVjdGVkIGJ5IHRoZSBlbmRwb2ludCB3aWxsIGRlcGVuZCBvbiB0aGUg
cGF0aC4gQSB3YXkgdG8gZW5zdXJlIGEg4oCcY29uc2lzdGVudCBhdmFpbGFiaWxpdHnigJ0gaXMg
dG8gaW5zZXJ0IG1hbnkgRm9yd2FyZC1Gb3IgaGVhZGVyczsgZWFjaCBlbmNsb3NpbmcgdGhlIGNv
bnRlbnQgdGhhdCBpcyBzcGVjaWZpYyB0byBhIGdpdmVuIG5ldHdvcmsNCiBhdHRhY2htZW50LiBC
dXQgZG9pbmcgdGhhdCByYWlzZXMgYSBwcml2YWN5IGNvbmNlcm4gYmVjYXVzZSB0aGUgcmVtb3Rl
IHNlcnZlciBjYW4gdHJhY2sgY2xpZW50cy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDtt
YXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgd2luZG93dGV4dCAxLjVwdDtwYWRk
aW5nOjBjbSAwY20gMGNtIDQuMHB0O2JvcmRlci1jb2xvcjotbW96LXVzZS10ZXh0LWNvbG9yIC1t
b3otdXNlLXRleHQtY29sb3IgLW1vei11c2UtdGV4dC1jb2xvciBibHVlIj4NCjxkaXY+DQo8ZGl2
Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPk15IGludGVudCAoYW5kIHRoZSB1bmRlcnN0YW5kaW5nIG9mIG90aGVyIHJldmll
d2VycykgaXMgdG8gaGlnaGxpZ2h0IHRoYXQgdGhlc2UgbWVjaGFuaXNtcyBoYXZlIGEgcHJpdmFj
eS1kYW1hZ2luZyByZXN1bHQgYW5kIHRoYXQgdGhpcyBzaG91bGQgYmUgY29uc2lkZXJlZC4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gSSBkbyB0aGluayBleGlzdGluZyBkb2N1bWVudHMg
YWxyZWFkeSBtYWtlIHRoYXQgam9iLiBJIGRvIHRoaW5rIHdlIG5lZWQgbW9yZS4gJm5ic3A7Jm5i
c3A7Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1
b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U29ycnksIGRpZCB5b3UgbWVhbiAm
cXVvdDtkbyBub3QgdGhpbmsgd2UgbmVlZCBtb3JlJnF1b3Q7PzxzcGFuIHN0eWxlPSJjb2xvcjpi
bGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBJIG1lYW50IHdlIG5lZWQgbW9yZSB0
aGFuIG9ubHkgaGlnaGxpZ2h0aW5nIHRoZSBpc3N1ZS4gV2UgbmVlZCBzb21ldGhpbmcgd2hpY2gg
aXMgYWN0aW9uYWJsZS4gUmVxdWlyaW5nIGEgUHJpdmFjeSBTZWN0aW9uIGluIGV2ZXJ5IFJGQyBt
YXkgYSBkaXJlY3Rpb24NCiB0byBjb25zaWRlci4gPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyI+Jm5ic3A7IElmIHNvLCBJIG9idmlvdXNseSBkaXNhZ3JlZS4mbmJzcDsgPC9zcGFu
PlRoaXMgZGVzaWduIHBhdHRlcm4gaXMgdXNlZCB1bmNyaXRpY2FsbHkgZW5vdWdoIHRoYXQgYSBi
cmllZiBkb2N1bWVudCBkZXNjcmliaW5nIHdoeSBpdCBpc24ndCBzYWZlIHN0aWxsIHNlZW1zIHRv
IG1lIHVzZWZ1bC4mbmJzcDsgV2VyZSBpdCBpbmNvcnBvcmF0ZWQgaW50byBhIG1vcmUgZ2VuZXJh
bCBkb2N1bWVudCAoYXMNCiBub3RlZCBiZWZvcmUpLCB0aGF0IHdvdWxkIGFsc28gd29yay4mbmJz
cDsgSWYgaXQgbGF0ZXIgaXMsIHRoYXQgbW9yZSBnZW5lcmFsIHdvcmsgY291bGQgb2Jzb2xldGUg
dGhpcyAodGhvdWdoIHRoYXQncyBhIGJpZCBmb3IgYW4gaW5mb3JtYXRpb25hbCBkb2N1bWVudCku
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBw
dDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgd2luZG93dGV4dCAxLjVwdDtw
YWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0O2JvcmRlci1jb2xvcjotbW96LXVzZS10ZXh0LWNvbG9y
IC1tb3otdXNlLXRleHQtY29sb3IgLW1vei11c2UtdGV4dC1jb2xvciBibHVlIj4NCjxkaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4g
bGFuZz0iRU4tVVMiPiZuYnNwO0luIHBhcnRpY3VsYXJseSwgSSdtIGNvbmNlcm5lZCB0aGF0IHNv
bWUgYXBwbGljYXRpb24gZnVuY3Rpb25zIGluIHRoZSBuZXR3b3JrIChlLmcuIHJlY3Vyc2l2ZSBy
ZXNvbHZlcnMgb3IgcHJveGllcykgZG8gbm90IGNvbnNpZGVyIHRoZSBwb3N0aXZlIHByaXZhY3kg
aW1wbGljYXRpb25zDQogb2YgdGhlaXIgYWdncmVnYXRpb24gYW5kIHNvIGRvIG5vdCBjb25zaWRl
ciBhZGRpbmcgdGhpcyBkYXRhIGJhY2sgYXMgcHJvYmxlbWF0aWMuPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PltNZWRdIEnigJltIGFsc28gY29uY2VybmVkIHdpdGggdGhhdCwgdG9vIChzZWUgZS5nLiwNCjxh
IGhyZWY9Imh0dHA6Ly93d3cxLmljc2kuYmVya2VsZXkuZWR1LyU3RW5hcnNlby9wYXBlcnMvaG90
bTQyLXZhbGxpbmFyb2RyaWd1ZXoucGRmIiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwOi8vd3d3MS5p
Y3NpLmJlcmtlbGV5LmVkdS9+bmFyc2VvL3BhcGVycy9ob3RtNDItdmFsbGluYXJvZHJpZ3Vlei5w
ZGY8L2E+KS4gSW4gdGhlIG1lYW50aW1lLCBJ4oCZbSBhbHNvIGNvbmNlcm5lZCB3aXRoICgxKSBz
b21lIGFwcGxpY2F0aW9ucyB0aGF0IGxlYWsgcHJpdmFjeSBpbmZvcm1hdGlvbiB3aXRob3V0IHRo
ZSBjb25zZW50IG9mIHRoZSB1c2VyIGFuZCAoMikgc29tZSBhcHBsaWNhdGlvbiBzZXJ2ZXJzIHRo
YXQgbWF5IGNvcnJlbGF0ZSB2YXJpb3VzDQogaW5mb3JtYXRpb24gc2hhcmVkIGJ5IGFuIGFwcGxp
Y2F0aW9uIGNsaWVudCB0byB0cmFjayB1c2VycyAoZS5nLiwgPGEgaHJlZj0iaHR0cHM6Ly9wYW5v
cHRpY2xpY2suZWZmLm9yZy8iIHRhcmdldD0iX2JsYW5rIj4NCmh0dHBzOi8vcGFub3B0aWNsaWNr
LmVmZi5vcmcvPC9hPikuIEJUVywgSSBzZWUgdGhhdCB5b3UgYXJlIHVzaW5nIOKAnGFwcGxpY2F0
aW9uIGZ1bmN0aW9u4oCdIHdoaWNoIG1heSBub3QgaGF2ZSB0aGUgc2FtZSBtZWFuaW5nIGFzIHRo
ZSBnZW5lcmFsIOKAnHByb3RvY29s4oCdIHdvcmRpbmcgdXNlZCBpbiBkcmFmdC1oYXJkaWUtKi4g
RG8geW91IGNvbnNpZGVyIGEgREhDUCByZWxheSBhcyBhbiDigJxhcHBsaWNhdGlvbiBmdW5jdGlv
buKAnT8NCjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPiZuYnNwOyZuYnNwOyBIaWdobGlnaHRpbmcgdGhpcyBlbmFibGVzIHRoZW0gdG8g
c2VlIHRoaXMgdHJhZmZpYyBpbiBhIGRpZmZlcmVudCBjb250ZXh0Ljwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNr
Ij5bTWVkXSBJc27igJl0IHRoaXMgYWxyZWFkeSBhc3N1bWVkIGJ5IHNvbWUgcHJvdG9jb2wgZGVz
aWduZXJzIChlLmcuLCBSRkM2OTczLCBTSVApPyBCVFcsIHRoZXJlIGFyZSBzdWJ0bGV0aWVzDQog
d2hlbiBwcm94aWVzIGFyZSBpbiB0aGUgc2FtZSB0cnVzdCBkb21haW4gb2YgdGhlIGNsaWVudCBv
ciBzZXJ2ZXIuICZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
YmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGVyZSBhcmUgY2VydGFp
bmx5IHNvbWUgcHJvdG9jb2wgZGVzaWduZXJzIHRoYXQgaGF2ZSBpbnRlcm5hbGl6ZWQgdGhpcywg
YnV0IG15IGV4cGVyaWVuY2UgaGFzIGJlZW4gdGhhdCB0aGlzIGlzIG5vdCBhbHdheXMgdGhlIGNh
c2UuJm5ic3A7IEluIGEgZmFpciBmZXcgY2FzZXMsIGZvbGtzIGRlcGxveSZuYnNwOyBtZXRob2Rz
IGxpa2UgdGhpcyBiZWNhdXNlIHRoZXkgc2VlIGVuY3J5cHRpb24gb2YgbWV0YWRhdGEgaW4gZGF0
YQ0KIGludGVncml0eSB0ZXJtcyBvciBzZWUgYWdncmVnYXRpb24gb25seSBpbiB0ZXJtcyBvZiBk
YXRhIHVzYWdlIG1pbmltaXphdGlvbi4mbmJzcDsgVGhleSByZXN0b3JlIHRoZSBtZXRhZGF0YSBt
aWQtbmV0d29yayBiZWNhdXNlIGl0IGlzIHRoZSBxdWlja2VzdCBzb2x1dGlvbiBmb3IgdGhlbSB0
byBnZXQgYmFjayB0byB0aGUgc3RhdHVzIHF1byBhbnRlIGZvciB0aGVpciB1bmRlcnN0YW5kaW5n
IG9mIHRoZSBzeXN0ZW0uPHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0g
SSBoZWFyIHlvdS4gV2hhdCB3b3VsZCBiZSB0aGUgaGFybSBpZiB0aG9zZSBzb2x1dGlvbnMgc3Ry
aXAgdGhhdCBpbmZvcm1hdGlvbiBiZWZvcmUgc2VuZGluZyBpdCB0byB0aGUgc2VydmVyPyBJZiB0
aGV5IGRvbuKAmXQgc3RyaXAgaXQsIHRoaXMgbWVhbnMgdGhhdA0KIGVpdGhlciB0aGUgaW5mb3Jt
YXRpb24gY2FuIGJlIHBhcnNlZCBhbmQgdXNlZCBieSB0aGUgc2VydmVyLCBvciBhdCBsZWFzdCBp
dHMgcHJlc2VuY2UgZG9lcyBub3QgbGVhZCB0byBzZXNzaW9uIGZhaWx1cmVzLiBJbiB0aGUgY2Fz
ZSB0aGUgc2VydmVyIHBhcnNlcyBhbmQgdXNlcyB0aGF0IGluZm9ybWF0aW9uLCB0aGlzIG1lYW5z
IHRoYXQgdGhlIHByZXNlbmNlIG9mIHRoYXQgaW5mb3JtYXRpb24gaXMgaW1wb3J0YW50IGZvciB0
aGUgc2VydmljZQ0KIHRvIGRlbGl2ZXIuIEluIHRoYXQgY2FzZSwgdGhlIHF1ZXN0aW9uIGlzIHdo
eSB0aGUgY2xpZW50IGRvZXMgbm90IHN1cHBseSB0aGF0IGluZm9ybWF0aW9uIGF0IHRoZSBmaXJz
dCBwbGFjZS48L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0Ljhw
dDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgd2luZG93dGV4dCAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNt
IDQuMHB0O2JvcmRlci1jb2xvcjotbW96LXVzZS10ZXh0LWNvbG9yIC1tb3otdXNlLXRleHQtY29s
b3IgLW1vei11c2UtdGV4dC1jb2xvciBibHVlIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gY2xhc3M9ImdtYWlsLSI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4qIHRoYXQgZGF0YSBtYXkgbm90IGJlIGFs
d2F5cyBhdmFpbGFibGUgdG8gdGhlIGVuZGhvc3Q8L3NwYW4+PC9zcGFuPjxzcGFuIGxhbmc9IkVO
LVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJs
YWNrIj5VbmRlcnN0b29kLCBidXQgZXZlbiBpbiB0aGlzIGNhc2UsIGl0IGlzIGJldHRlciB0byBt
YWtlIHRoZSBwZXJtaXNzaW9uIHRvIGFkZCB0aGUgZGF0YSBleHBsaWNpdC48L3NwYW4+PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjpibGFjayI+W01lZF0gVGhpcyBtYXkgYmUgZWFzeSB0byBpbXBsZW1lbnQgZm9yIHNvbWUg
YXBwbGljYXRpb25zLCBidXQgdGhpcyBtYXkgbm90IGJlIGdlbmVyYWxpemVkIHRvICoqDQogYWxs
ICoqIHByb3RvY29scy4gPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9i
bG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1i
b3R0b206MTIuMHB0Ij5Zb3UgYXJlIGNlcnRhaW5seSBjb3JyZWN0IHRoYXQgbWFueSBkZXBsb3ll
ZCBwcm90b2NvbHMgd291bGQgZmluZCBpdCBoYXJkIHRvIHJldHJvZml0IHRoaXMgY29uc2VudCBt
b2RlbCBpbnRvIHRoZWlyIGV4aXN0aW5nIGZsb3dzLiZuYnNwOyZuYnNwOyZuYnNwOyBUaGlzIGlz
LCBob3dldmVyLCBhZHZpY2UgZm9yIGZvbGtzIGF0IHRoZSBkZXNpZ24gcGhhc2UuJm5ic3A7IElm
IFJGQyA2Nzg4IHdlcmUNCiBiZWluZyB3cml0dGVuIGFmdGVyIHRoZSBwdWJsaWNhdGlvbiBvZiB0
aGlzIGRvY3VtZW50LCBpdHMgYXV0aG9ycyBtaWdodCB3ZWxsIGhhdmUgbG9va2VkIGF0IHRoZSBw
cm90b2NvbCBtZWNoYW5pY3MgaW4gc2VjdGlvbiA1LjI6PG86cD48L286cD48L3A+DQo8cHJlPiZu
YnNwOyZuYnNwOyBUaGUgQU48bzpwPjwvbzpwPjwvcHJlPg0KPHByZT4mbmJzcDsmbmJzcDsgaW50
ZXJjZXB0cyBhbmQgdGhlbiB0dW5uZWxzIHRoZSByZWNlaXZlZCBSb3V0ZXIgU29saWNpdGF0aW9u
IGluIGE8bzpwPjwvbzpwPjwvcHJlPg0KPHByZT4mbmJzcDsmbmJzcDsgbmV3bHkgY3JlYXRlZCBJ
UHY2IGRhdGFncmFtIHdpdGggdGhlIExpbmUtSWRlbnRpZmljYXRpb24gT3B0aW9uPG86cD48L286
cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7IChMSU8pLiZuYnNwOyBUaGUgQU4gZm9ybXMgYSBu
ZXcgSVB2NiBkYXRhZ3JhbSB3aG9zZSBwYXlsb2FkIGlzIHRoZTxvOnA+PC9vOnA+PC9wcmU+DQo8
cHJlPiZuYnNwOyZuYnNwOyByZWNlaXZlZCBSb3V0ZXIgU29saWNpdGF0aW9uIG1lc3NhZ2UgYXMg
ZGVzY3JpYmVkIGluIFs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjMjQ3
MyIgdGl0bGU9IiZxdW90O0dlbmVyaWMgUGFja2V0IFR1bm5lbGluZyBpbiBJUHY2IFNwZWNpZmlj
YXRpb24mcXVvdDsiPlJGQzI0NzM8L2E+XSw8bzpwPjwvbzpwPjwvcHJlPg0KPHByZT4mbmJzcDsm
bmJzcDsgZXhjZXB0IHRoYXQgdGhlIEhvcCBMaW1pdCBmaWVsZCBvZiB0aGUgUm91dGVyIFNvbGlj
aXRhdGlvbiBtZXNzYWdlPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9Im1hcmdpbi1ib3R0
b206MTIuMHB0Ij4mbmJzcDsmbmJzcDsgTVVTVCBOT1QgYmUgZGVjcmVtZW50ZWQuPG86cD48L286
cD48L3ByZT4NCjxwcmUgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5hbmQgYXNrZWQgd2hl
dGhlciB0aGUgY2lyY3VpdCBpZGVudGlmaWVyIGNvcnJlc3BvbmRpbmcgdG8gdGhlIGxvZ2ljYWwg
PGJyPmFjY2VzcyBsb29wIHBvcnQgb2YgdGhlIEFOIGZyb20gd2hpY2ggdGhlIFJTIHdhcyBpbml0
aWF0ZWQgUElJLiZuYnNwOyBJZiBzbywgdGhpczxicj5kb2N1bWVudCB3b3VsZCBoYXZlIHRoZW0g
Y29uc2lkZXIgd2hldGhlciB0cmFuc3BhcmVudCBpbnRlcmNlcHRpb24gPGJyPmlzIHRoZSBhcHBy
b3ByaWF0ZSBjaG9pY2UgaWYgaXQgaXMuJm5ic3A7IFRoZXJlIGNsZWFybHkgYXJlIGZsb3dzIGlu
IHdoaWNoIHRoZSBBTidzIHJvbGUgPGJyPndvdWxkIGJlIGV4cGxpY2l0LjxvOnA+PC9vOnA+PC9w
cmU+DQo8cHJlPkkgZG9uJ3Qga25vdywgZnJhbmtseSwgd2hpY2ggY2hvaWNlIGlzIHJpZ2h0IGlu
IHRoaXMgY2FzZSwgYnV0IEkgd291bGQgcHJlZmVyIHRoYXQ8YnI+dGhlIGNob2ljZSBiZSBtYWRl
IHdpdGggYW4gZWFzeSByZWZlcmVuY2UgdG8gdGhlIGltcGxpY2F0aW9ucyBvZiBpbnNlcnRpbmcg
bWV0YWRhdGE8YnI+YXQgaGFuZC4gPG86cD48L286cD48L3ByZT4NCjwvZGl2Pg0KPGJsb2NrcXVv
dGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFk
ZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNt
Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29s
aWQgd2luZG93dGV4dCAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0O2JvcmRlci1jb2xv
cjotbW96LXVzZS10ZXh0LWNvbG9yIC1tb3otdXNlLXRleHQtY29sb3IgLW1vei11c2UtdGV4dC1j
b2xvciBibHVlIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5Q
dXR0aW5nIGFzaWRlIHRoZSBpbnRlcmFjdGlvbiB3aXRoIGEgdXNlciB0byBnZXQgYSBjb25zZW50
IGFuZCBob3cgdGhhdCBjb25zZW50IHdpbGwgbmVlZCB0byBiZQ0KIGNoYW5nZWQgd2hlbiBhbm90
aGVyIHVzZXIgdXNlcyB0aGUgc2FtZSBkZXZpY2UgdG8gY29ubmVjdCB0byB0aGUgSW50ZXJuZXQu
IENvbnNpZGVyIGEgdXNlciB3aG8gZG9lcyBub3Qgd2FudCBhbiB1cHN0cmVhbSBESFBDIHJlbGF5
IHRvIGluc2VydCB0aGUgbGluZS1pZCAoPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9o
dG1sL3JmYzY3ODgiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
cmZjNjc4ODwvYT4pDQogdG8gdGhlIHNlcnZlciwgYW5kIGxldOKAmXMgc3VwcG9zZSB0aGUgcmVs
YXkgcmVjZWl2ZWQgYSBzaWduYWwgKGJ5IHNvbWUgbWVhbnMsIHRvIGJlIHlldCBzcGVjaWZpZWQp
IHRoYXQgZm9yIHRoaXMgcGFydGljdWxhciBESENQIGNsaWVudCwgdGhlIGxpbmUtaWQgbXVzdCBu
b3QgYmUgaW5zZXJ0ZWQuIEZvciB0aGlzIGNhc2UsIGNvbm5lY3Rpdml0eSB3b27igJl0IGJlIHBy
b3ZpZGVkIHRvIHRoYXQgdXNlci4gVGhpcyB3b3VsZCBtZWFuIGV4dHJhIGNhbGxzDQogdG8gdGhl
IGhvdGxpbmUgZm9yIHRoYXQgbmV0d29yayBwcm92aWRlci4gVGhpcyBpcyBub3QgZGVzaXJhYmxl
IGZvciBib3RoIGN1c3RvbWVycyBhbmQgbmV0d29yayBwcm92aWRlcnMuDQo8L3NwYW4+PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5JPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYu
MHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4NCjxkaXY+DQo8
ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCB3aW5kb3d0ZXh0IDEuNXB0
O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7Ym9yZGVyLWNvbG9yOi1tb3otdXNlLXRleHQtY29s
b3IgLW1vei11c2UtdGV4dC1jb2xvciAtbW96LXVzZS10ZXh0LWNvbG9yIGJsdWUiPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+ZiB0
aGlzIGNhbiBiZSBkb25lIGluIHBhcmFsbGVsIHdpdGggb3RoZXIgYWN0aW9ucywgdGhlbiB0aGUg
bGF0ZW5jeSBpbXBhY3QgY2FuIGJlIG1pbmltaXplZC48L3NwYW4+PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+
W01lZF0gVGhlc2UgYXJlIGFzc3VtcHRpb25zIGFuZCBpbXBsaWNhdGlvbnMgdGhhdCBhcmUgd29y
dGggdG8gYmUgYWRkZWQgdG8gdGhlIGRyYWZ0Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+T2theSwgaG93IGFib3V0IHRoZSBmb2xsb3dpbmcg
dGV4dCBiZWluZyBhZGRlZCB0byBzZWN0aW9uIDUuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPlRo
ZXJlIGFsc28gdGVuc2lvbnMgd2l0aCBsYXRlbmN5IG9mIG9wZXJhdGlvbi4gRm9yIGV4YW1wbGUs
IHdoZXJlIHRoZSBlbmQgc3lzdGVtIGRvZXMgbm90IGluaXRpYWxseSBrbm93IHRoZSBpbmZvcm1h
dGlvbiB3aGljaCB3b3VsZCBiZSBhZGRlZCBieSBvbi1wYXRoIGRldmljZXMsIGl0IG11c3QgZW5n
YWdlIHRoZSBwcm90b2NvbCBtZWNoYW5pc21zIHRvIGRldGVybWluZQ0KIGl0LiZuYnNwOyBEZXRl
cm1pbmluZyBhIHB1YmxpYyBJUCBhZGRyZXNzIHRvIGluY2x1ZGUgaW4gYSBsb2NhbGx5IHN1cHBs
aWVkIGhlYWRlciBtaWdodCByZXF1aXJlIGEgU1RVTiBleGNoYW5nZSwgYW5kIHRoZSBhZGRpdGlv
bmFsIGxhdGVuY3kgb2YgdGhpcyBleGNoYW5nZSBkaXNjb3VyYWdlcyBkZXBsb3ltZW50IG9mIGhv
c3QtYmFzZWQgc29sdXRpb25zLiZuYnNwOyBUbyBtaW5pbWl6ZSB0aGlzIGxhdGVuY3ksIGVuZ2Fn
aW5nIHRob3NlIG1lY2hhbmlzbXMgbWF5DQogbmVlZCB0byBiZSBkb25lIGluIHBhcmFsbGVsIHdp
dGggb3IgaW4gYWR2YW5jZSBvZiB0aGUgY29yZSBwcm90b2NvbCBleGNoYW5nZXMgd2l0aCB3aGlj
aCB0aGlzIG1ldGFkYXRhIHdvdWxkIGJlIHN1cHBsaWVkLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIExvb2tzIGdvb2QgdG8gbWUuIFRoYW5rcy48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAx
LjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1y
aWdodDowY20iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
bGVmdDpzb2xpZCB3aW5kb3d0ZXh0IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7Ym9y
ZGVyLWNvbG9yOi1tb3otdXNlLXRleHQtY29sb3IgLW1vei11c2UtdGV4dC1jb2xvciAtbW96LXVz
ZS10ZXh0LWNvbG9yIGJsdWUiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPkJUVywgdGhpcyBmYWxscyBpbnRvIHRoaXMgZ2VuZXJhbCBkaXNjdXNzaW9uIGluDQo8
YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjk3MyIgdGFyZ2V0PSJfYmxh
bmsiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2OTczPC9hPjoNCjwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
O2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7IGEuJm5ic3A7IFRy
YWRlLW9mZnMuJm5ic3A7IERvZXMgdGhlIHByb3RvY29sIG1ha2UgdHJhZGUtb2ZmcyBiZXR3ZWVu
IHByaXZhY3k8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IGFuZCB1c2FiaWxpdHksIHByaXZhY3kgYW5kIGVmZmljaWVuY3ksIHByaXZhY3kgYW5kPC9zcGFu
PjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBpbXBsZW1lbnRhYmls
aXR5LCBvciBwcml2YWN5IGFuZCBvdGhlciBkZXNpZ24gZ29hbHM/Jm5ic3A7IERlc2NyaWJlPC9z
cGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0aGUgdHJhZGUt
b2ZmcyBhbmQgdGhlIHJhdGlvbmFsZSBmb3IgdGhlIGRlc2lnbiBjaG9zZW4uPC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgd2luZG93dGV4dCAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21h
cmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4t
Ym90dG9tOjUuMHB0O2JvcmRlci1jb2xvcjotbW96LXVzZS10ZXh0LWNvbG9yIC1tb3otdXNlLXRl
eHQtY29sb3IgLW1vei11c2UtdGV4dC1jb2xvciByZ2IoMjA0LDIwNCwyMDQpIj4NCjxkaXY+DQo8
ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgd2luZG93dGV4
dCAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0O2JvcmRlci1jb2xvcjotbW96LXVzZS10
ZXh0LWNvbG9yIC1tb3otdXNlLXRleHQtY29sb3IgLW1vei11c2UtdGV4dC1jb2xvciBibHVlIj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+KiBhIG1pc2JlaGF2aW5nIG5vZGUgbWF5IGJlIHRlbXB0
ZWQgdG8gc3Bvb2YgdGhlIGRhdGEgdG8gYmUgaW5qZWN0ZWQuIEEgcmVtb3RlIGRldmljZSB0aGF0
IHdpbGwgdXNlIHRoYXQNCiBkYXRhIHRvIGVuZm9yY2UgcG9saWNpZXMgd2lsbCBiZSBicm9rZW4u
PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1ib3R0b206MTIu
MHB0Ij5UaGlzIHBvaW50IHdhcyBkaXNjdXNzZWQgZXh0ZW5zaXZlbHkgaW4gdGhlIEdFT1BSSVYg
d29yayBhbmQgZXNzZW50aWFsbHkgYSBzaW5nbGUgY2FydmUtb3V0IHdhcyBtYWRlOiZuYnNwOyBm
b3IgZW1lcmdlbmN5IHNlcnZpY2VzLCB3aGVyZSBmYWxzZWx5IGFzc2VydGVkIGxvY2F0aW9uIGRh
dGEgY291bGQgYmUgdXNlZCB0byBTV0FUDQogaW5kaXZpZHVhbHMgb3IgY29uc3VtZSBzYWZldHkg
cmVzb3VyY2VzLiZuYnNwOyZuYnNwOyZuYnNwOyBJIGRvbid0IHRoaW5rIHRoYXQgZmFsbHMgaW50
byB0aGlzIG5hcnJvdyBhZHZpY2UsIGJ1dCBJIHdvdWxkIGJlIHdpbGxpbmcgdG8gYWRkIHNvbWV0
aGluZyBsaWtlIHRoaXMgdG8gdGhlIHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zOjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mcXVvdDtOb3RlIHRo
YXQgc29tZSBlbWVyZ2VuY3kgc2VydmljZSByZWNpcGllbnRzLCBub3RhYmx5IFBTQVBzIChQdWJs
aWMgU2FmZXR5IEFuc3dlcmluZyBQb2ludHMpIG1heSBwcmVmZXIgZGF0YSBwcm92aWRlZCBieSBh
IG5ldHdvcmsgdG8gZGF0YSBwcm92aWRlZCBieSBlbmQgc3lzdGVtLCBiZWNhdXNlIGFuIGVuZA0K
IHN5c3RlbSBjb3VsZCB1c2UgZmFsc2UgZGF0YSB0byBhdHRhY2sgb3RoZXJzIG9yIGNvbnN1bWUg
cmVzb3VyY2VzLiZuYnNwOyZuYnNwOyBXaGlsZSB0aGlzIGhhcyB0aGUgY29uc2VxdWVuY2UgdGhh
dCB0aGUgZGF0YSBhdmFpbGFibGUgdG8gdGhlIFBTQVAgaXMgb2Z0ZW4gbW9yZSBjb2Fyc2UgdGhh
biB0aGF0IGF2YWlsYWJsZSB0byB0aGUgZW5kIHN5c3RlbSwgdGhlIHJpc2sgb2YgZmFsc2UgZGF0
YSBiZWluZyBwcm92aWRlZCBpbnZvbHZlZCBhIHJpc2sgdG8gdGhlDQogbGl2ZXMgb2YgdGhvc2Ug
dGFyZ2V0ZWQuJnF1b3Q7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gVGhhbmsgeW91LiBQcm92aWRp
bmcgUFNBUCBhcyBhbiBleGFtcGxlIGlzIE9LLCBidXQgSeKAmWQgbGlrZSB0aGUgaXNzdWUgdG8g
YmUgY2FsbGVkIG91dCBhcw0KIGEgZ2VuZXJpYyBvbmUgd2hpbGUgUFNBUCBpcyBwcm92aWRlZCBh
cyBhbiBleGFtcGxlLiBXaGF0IGFib3V0IHRoZSBmb2xsb3dpbmc6IDwvc3Bhbj4NCjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29s
b3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPiZxdW90O05vdGUgdGhhdCBzb21lIHNlcnZlcnMgKGUu
Zy4sIGVtZXJnZW5jeSBzZXJ2aWNlIHJlY2lwaWVudHMsIG5vdGFibHkgUFNBUHMgKFB1YmxpYyBT
YWZldHkgQW5zd2VyaW5nIFBvaW50cykgW1JGQzY0NDNdKSBtYXkgcHJlZmVyIGRhdGEgcHJvdmlk
ZWQgYnkgYSBuZXR3b3JrIHRvDQogZGF0YSBwcm92aWRlZCBieSB0aGUgZW5kIHN5c3RlbSwgYmVj
YXVzZSBhbiBlbmQgc3lzdGVtIGNvdWxkIHVzZSBmYWxzZSBkYXRhIHRvIGF0dGFjayBvdGhlcnMg
b3IgY29uc3VtZSByZXNvdXJjZXMuJm5ic3A7IFdoaWxlIHRoaXMgaGFzIHRoZSBjb25zZXF1ZW5j
ZSB0aGF0IHRoZSBkYXRhIGF2YWlsYWJsZSB0byB0aGUgc2VydmVyIGlzIG9mdGVuIG1vcmUgY29h
cnNlIHRoYW4gdGhhdCBhdmFpbGFibGUgdG8gdGhlIGVuZCBzeXN0ZW0sIHRoZSByaXNrIG9mDQog
ZmFsc2UgZGF0YSBiZWluZyBwcm92aWRlZCBpbnZvbHZlZCBhIHJpc2sgdG8gdGhlIGxpdmVzIG9m
IHRob3NlIHRhcmdldGVkLiZxdW90Ozwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPg0KPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5JIGRvbid0IHRoaW5rIHRoYXQgZW1lcmdlbmN5
IHNlcnZpY2UgcmVjaXBpZW50cyBzaGlmdGluZyB0byBhbiBleGFtcGxlIHdvcmtzIGhlcmUsIGJl
Y2F1c2UgaXQgYnJvYWRlbnMgdGhlIGNhcnZlIG91dC4mbmJzcDsgSW4gdGhlIGVtZXJnZW5jeSBz
ZXJ2aWNlcyBjYXNlLCB0aGUgcmVzb3VyY2VzIGNvbnN1bWVkIGFyZSBmaXJlIHRydWNrcywgYW1i
dWxhbmNlcywgYW5kIHN3YXQgdGVhbXMuJm5ic3A7DQo8L3NwYW4+Rm9yIG90aGVyIHNlcnZlcnMs
IHJlc291cmNlcyBjb25zdW1lZCBjb3VsZCBzaW1wbHkgYmUmbmJzcDsgQ1BVIGN5Y2xlcyBvciBk
aXNrOyB0aGF0J3MgcmVhbGx5IG5vdCB0aGUgc2FtZS4mbmJzcDsgQmFsYW5jaW5nIGxvY2F0aW9u
IGNvbnNlbnQgcmVxdWlyZW1lbnRzIGFnYWluc3Qgb25lIHdhcyBhZ3JlZWQ7IGJhbGFuY2luZyBp
dCBhZ2FpbnN0IHRoZSBvdGhlciB3YXMgbm90LjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gUmVzb3VyY2VzIG1heSBu
b3QgYmUgcmVzdHJpY3RlZCB0byBDUFUgb3IgZGlzayBidXQgbWF5IGJlIGdyYW50aW5nIGFjY2Vz
cyB0byB0aGUgc2VydmljZSAoZS5nLiwgZG93bmxvYWQgYSBmaWxlIHdoZW4gYSBxdW90YSBwZXIg
c291cmNlIGFkZHJlc3MgaXMgZW5mb3JjZWQpLg0KIEl0IGNhbiBiZSB3aGF0ZXZlciB0aGUgc2Vy
dmVycyBjb25zaWRlciB0byBiZSBjcml0aWNhbCBmb3IgdGhlbTsgaXQgaXMgdXAgdG8gdGhlIHRh
c3RlIG9mIHRoZSBzZXJ2aWNlIGRlc2lnbiB0byBjaGFyYWN0ZXJpemUgaXQuIFRoZSBORVcgd29y
ZGluZyBwcm9wb3NlZCBhYm92ZSBpcyB0ZWNobmljYWxseSBjb3JyZWN0LiBQbGVhc2UgcmVjb25z
aWRlciBhZGRpbmcgaXQgdG8gdGhlIGRyYWZ0Lg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48
YnI+DQo8YnI+DQombmJzcDsgPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8YmxvY2tx
dW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtw
YWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDow
Y207Ym9yZGVyLWNvbG9yOi1tb3otdXNlLXRleHQtY29sb3IgLW1vei11c2UtdGV4dC1jb2xvciAt
bW96LXVzZS10ZXh0LWNvbG9yIHJnYigyMDQsMjA0LDIwNCkiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCB3aW5kb3d0ZXh0IDEuNXB0O3Bh
ZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7Ym9yZGVyLWNvbG9yOi1tb3otdXNlLXRleHQtY29sb3Ig
LW1vei11c2UtdGV4dC1jb2xvciAtbW96LXVzZS10ZXh0LWNvbG9yIGJsdWUiPg0KPGRpdj4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgd2luZG93dGV4dCAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYu
MHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTtt
YXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgd2luZG93dGV4dCAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNt
IDQuMHB0O2JvcmRlci1jb2xvcjotbW96LXVzZS10ZXh0LWNvbG9yIC1tb3otdXNlLXRleHQtY29s
b3IgLW1vei11c2UtdGV4dC1jb2xvciBibHVlIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bWFy
Z2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+KiBp
dCB3YXMgcmVwb3J0ZWQgaW4gdGhlIHBhc3QgdGhhdCBzb21lIGJyb3dzZXJzIGxlYWsgdGhlIE1T
SVNETiBhbmQgb3RoZXIgc2Vuc2l0aXZlIGRhdGEuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj5UaGlzIGlzIHRydWUsIGJ1dCBpdCBzZWVtcyB0
byBtZSB1bnJlPC9zcGFuPmxhdGVkIHRvIHRoZSBwb2ludCBvZiB0aGUgZG9jdW1lbnQuPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gSXQgaXMgcmVsYXRlZCBiZWNhdXNlIGJs
aW5kbHkgdHJ1c3RpbmcgYW4gYXBwbGljYXRpb24gY2xpZW50IChhbmQgc2VydmVyKSBoYXMgaXRz
IG93biBwcml2YWN5DQogcmlza3MuIFRoaXMgaXMgZXZlbiBleGFjZXJiYXRlZCBnaXZlbiB0aGUg
cmljaCBkYXRhIHRoYXQgaXMgYXZhaWxhYmxlIHRvIGFuIGFwcGxpY2F0aW9uIGNsaWVudCBhbmQg
YWxzbyBiZWNhdXNlIG9mIHRoZSB2aXNpYmlsaXR5IG9uIHZhcmlvdXMgbGF5ZXJzIGF2YWlsYWJs
ZSB0byBhbiBhcHBsaWNhdGlvbiBzZXJ2ZXIuDQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPiZu
YnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgYWdyZWUgdGhhdCBpdCBoYXMgaXRzIG93
biBwcml2YWN5IHJpc2tzLCBidXQgSSBkb24ndCB0aGluayB0aGlzIGlzIHRoZSBkb2N1bWVudCB0
aGF0IHNob3VsZCBleHBsb3JlIHRoZW0uDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gWW91IGRvbuKA
mXQgbmVlZCB0byBleHBsb3JlIHRoZW0sIGJ1dCB0byBhZGQgb25lIG9yIHR3byBzZW50ZW5jZXMg
dG8gcmVtaW5kIHRoYXQgcHJpdmFjeSBsZWFrcyBhcmUgc3RpbGwgYSB2YWxpZCBjb25jZXJuIGV2
ZW4gaWYgb25seSBjbGllbnRzIGFyZSBzdXBwbHlpbmcNCiBkYXRhIHdpdGhvdXQgdGhlIGhlbHAg
b2YgYW4gb24tcGF0aCBuZXR3b3JrIGRldmljZS4gPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0ND
Q0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21h
cmdpbi1yaWdodDowY207Ym9yZGVyLWNvbG9yOi1tb3otdXNlLXRleHQtY29sb3IgLW1vei11c2Ut
dGV4dC1jb2xvciAtbW96LXVzZS10ZXh0LWNvbG9yIHJnYigyMDQsMjA0LDIwNCkiPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCB3aW5kb3d0
ZXh0IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7Ym9yZGVyLWNvbG9yOi1tb3otdXNl
LXRleHQtY29sb3IgLW1vei11c2UtdGV4dC1jb2xvciAtbW96LXVzZS10ZXh0LWNvbG9yIGJsdWUi
Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgd2luZG93dGV4dCAxLjBwdDtwYWRkaW5nOjBj
bSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2lu
LXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgd2luZG93dGV4dCAxLjVwdDtwYWRkaW5n
OjBjbSAwY20gMGNtIDQuMHB0O2JvcmRlci1jb2xvcjotbW96LXVzZS10ZXh0LWNvbG9yIC1tb3ot
dXNlLXRleHQtY29sb3IgLW1vei11c2UtdGV4dC1jb2xvciBibHVlIj4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj5G
cm9tIHRoYXQgZmxvdyBzb21lIG9mIHlvdXIgb3RoZXIgY29uY2VybnMgYWJvdXQgYXVkaWVuY2Us
IGF0IGxlYXN0IGFzIEkgdW5kZXJzdGFuZC4mbmJzcDsgQXMgd3JpdHRlbjwvc3Bhbj4sIHRoaXMg
aXMgbmFycm93IGFkdmljZSBmb3IgYSBicm9hZCBhdWRpZW5jZTogYmFzaWNhbGx5LA0KIGFueW9u
ZSB3aG8gd291bGQgY29uc2lkZXIgdGhlIGZvcm0gb2YgbWV0YWRhdGEgaW5zZXJ0aW9uIGl0IGRl
c2NyaWJlcy4mbmJzcDsgWW91IHdvdWxkLCBpZiBJIHVuZGVyc3RhbmQgeW91LCBwcmVmZXIgYSBu
YXJyb3dlciBkZXNjcmlwdGlvbiBvZiB0aGUgYXVkaWVuY2UgaW4gYSBsYXJnZXIgY29udGV4dC4m
bmJzcDsNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmll
ciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5b
TWVkXSBUaGUga2V5IHBvaW50IGhlcmUgaXMgYWJvdXQgdGhlIHByYWN0aWNhbGl0eSBvZiBpbXBs
ZW1lbnRpbmcgdGhlIGFkdmljZSBOT1QgY2hhbmdpbmcgdGhlDQogc2NvcGUuIEZvciBleGFtcGxl
LCB0aGUgZG9jdW1lbnQgc2F5cyB0aGF0IGl0IGlzIGJldHRlciB0aGF0IGEgaG9zdCBpcyBpbmpl
Y3RpbmcgdGhlIGRhdGEgYnV0IHRoZSBkb2N1bWVudCBkb2VzIG5vdCBxdWVzdGlvbiB3aGV0aGVy
IHRoYXQgc3VwcGxpZWQgZGF0YSBjYW4gYmUgdHJ1c3RlZCBvciBub3QsPC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+QnJvYWRlbmluZyB0aGlzIGEgYml0LCB5b3UncmUgbG9va2luZyBh
dCB0d28gY2FzZXM6IG9uZSBpbiB3aGljaCB0aGUgZGF0YSB0aGUgaG9zdCBoYXMgaXMgd3Jvbmcg
YW5kIG9uZSBpbiB3aGljaCB0aGVyZSBpcyBhbiBhZHZlcnNhcmlhbCByZWxhdGlvbnNoaXAuJm5i
c3A7IEZvciB0aGUgZmlyc3QgY2FzZSwgd2UgY2FuIGFkZCB0ZXh0IHNheWluZyB0aGF0IHdoZW4g
YW4gZW5kIHN5c3RlbSBzdXBwbGllcyBkYXRhIGl0DQogaXMgdGhlIGVuZCBzeXN0ZW0ncyByZXNw
b25zaWJpbGl0eSB0byBlbnN1cmUgdGhhdCBpdCBpcyBjb3JyZWN0OyBkb24ndCB1c2UgYSBTVFVO
IHJlc3VsdCBmcm9tIGxhc3Qgd2VlayBhcyBmcmVzaCwgZm9yIGV4YW1wbGUuJm5ic3A7PHNwYW4g
c3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIE9LLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZx
dW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyBGb3IgdGhlIHNlY29uZCBjYXNl
LCZuYnNwOyBpbiB3aGljaCB0aGUgc2VydmVyIHRyZWF0cyB1c2VyIHN1cHBsaWVkIGRhdGEgYXMg
cG90ZW50aWFsbHkgbWlzbGVhZGluZyBiZWNhdXNlIHRoZSB1c2VyIG1heSB3aXNoIHRvIGNpcmN1
bXZlbnQgcmVzdHJpY3Rpb25zLCBJJ2xsIHBvaW50IG91dCB0aGUgV2lraW1lZGlhIGV4YW1wbGUg
ZGVtb25zdHJhdGVzIHRoYXQgc2ltcGx5IHNoaWZ0aW5nDQogdGhlIHRydXN0IHRvIGEgbWlkLXBv
aW50IGVudGl0eSBkb2Vzbid0IHdvcms7IGl0IGhhcyB0byBiZSBzaGlmdGVkIHRvIGFuIGVudGl0
eSB3aXRoaW4gdGhlIHRydXN0IGRvbWFpbiBvZiB0aGUgc2VydmVyLiZuYnNwOw0KPC9zcGFuPlNv
IHRoZSBxdWVzdGlvbiBpc24ndCByZWFsbHkgJnF1b3Q7ZW5kLXVzZXIgc3lzdGVtIHN1cHBsaWVk
IGRhdGEgY2FuIGJlIHRydXN0ZWQgb3Igbm90JnF1b3Q7LCB0aGUgc2FtZSBxdWVzdGlvbiBhcHBs
aWVzIHRvIHdob21ldmVyIHN1cHBsaWVzIHRoZSBkYXRhLjxzcGFuIHN0eWxlPSJjb2xvcjpibGFj
ayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBGdWxseSBhZ3JlZS4gSGF2aW5nIHNvbWUg
dGV4dCB0byByZWNvcmQgdGhhdCB0aGUgY29uY2VybiBhcHBsaWVzLCBpbmNsdWRpbmcgZm9yIGNs
aWVudCBzdXBwbGllZCBkYXRhLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxicj4NCjxicj4NCjwvc3Bhbj48c3BhbiBjbGFz
cz0iZ21haWwtIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPm9yIGhvdyB0aGUg
Y29uc2VudCB3aWxsIGJlIG9idGFpbmVkIGZyb20gYSB1c2VyLjwvc3Bhbj48L3NwYW4+PGJyPg0K
PGJyPg0KWW91J3JlIHJpZ2h0IHRoYXQgSSdtIGxlYXZpbmcgYXNpZGUgdGhlIHF1ZXN0aW9uIG9m
IGhvdyB0aGUgdXNlciBzZXRzIHRoZSBwb2xpY2llcywgYmVjYXVzZSBpdCBtYXkgdmFyeSBieSBw
cm90b2NvbCBhbmQgdHlwZSBvZiBkZXZpY2UgdG9vIG11Y2ggdG8gbWFrZSBnZW5lcmFsIGFkdmlj
ZSB1c2VmdWwuJm5ic3A7IElmIHlvdSB3b3VsZCBsaWtlIG1lIHRvIGFkZCBhbiBleHBsaWNpdCBz
dGF0ZW1lbnQgdG8gdGhhdCBlZmZlY3QsIEkgYW0gaGFwcHkgdG8gbm90ZQ0KIHRoYXQgaXQgaXMg
bm90IGNvdmVyZWQuICZuYnNwOzxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2Nv
bG9yOmJsYWNrIj5bTWVkXSBQbGVhc2UgYWRkIHNvbWUgdGV4dCBhYm91dCB0aGlzIHBvaW50LiBU
aGFuayB5b3UuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj4NCjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNt
IDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2
Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIHdpbmRv
d3RleHQgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDtib3JkZXItY29sb3I6LW1vei11
c2UtdGV4dC1jb2xvciAtbW96LXVzZS10ZXh0LWNvbG9yIC1tb3otdXNlLXRleHQtY29sb3IgYmx1
ZSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkluIGdlbmVyYWwsIHRo
ZSBwb2ludCBvZiB0aGUgZG9jdW1lbnQgaXMgdGhhdCB0aGUgaG9zdCBzaG91bGQgYmUgYWJsZSB0
byBvbWl0IHRoZSBkYXRhIHdpdGhvdXQgbWlkLW5ldHdvcmsgZGV2aWNlcyBhZGRpbmcgaXQgYmFj
ay4mbmJzcDsgVGhhdCdzIHRoZSBwb2ludCBvZiBwcm90ZWN0aW5nIHRoZSB0cmFmZmljIGluDQog
dGhlIGZpcnN0IHBsYWNlLCBhZnRlciBhbGwuJm5ic3A7IEkgYW0gc2F5aW5nIHRoYXQgaWYgdGhl
IHByb3RvY29scyByZXF1aXJlIHRoZSBkYXRhLCB0aGVuIGdldHRpbmcgaXQgZnJvbSB0aGUgZW5k
IGhvc3QgaGFzIGJldHRlciBwcml2YWN5IHByb3BlcnRpZXMgdGhhbiBnZXR0aW5nIGZyb20gaXQg
ZnJvbSBtaWQtbmV0d29yayBlbnRpdGllcy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBJ4oCZbSBu
b3Qgc3VyZSB3ZSBjYW4gaGF2ZSBzdWNoIGdlbmVyYWwgc3RhdGVtZW50IGJlY2F1c2UgdGhlIGRh
dGEgbWF5IG5vdCBiZSBhdmFpbGFibGUgKGUuZy4sDQogREhDUCBmb3IgZXhhbXBsZSkgdG8gY2xp
ZW50cyAmIzQzOyB0aGUgZGF0YSBzdXBwbGllZCBieSBjbGllbnRzICh3aGVuIHBvc3NpYmxlKSBt
YXkgbm90IGJlIHJlbGlhYmxlICYjNDM7IGVuZm9yY2luZyBwb2xpY2llcyBiYXNlZCBvbiBjbGll
bnQtc3VwcGxpZWQgZGF0YSBtYXkgaGF2ZSBpbXBsaWNhdGlvbiBvbiBvdGhlciB1c2VycyAoZS5n
Liwgc3Bvb2ZpbmcgWEZGIGZvciBleGFtcGxlKS4gT2J2aW91c2x5LCBnZXR0aW5nIHNvbWUgb2Yg
dGhlIGluZm9ybWF0aW9uDQogZnJvbSBhIGNsaWVudCBtYXkgaGF2ZSBpbXBsaWNhdGlvbnMgb24g
UW9F4oCmdGhlIHVzZXIgbmVlZHMgdG8gdW5kZXJzdGFuZCB0aGUgcm9vdCBjYXVzZXMgb2YgYSBk
ZWdyYWRhdGlvbiBvZiBRb0UuIE9mIGNvdXJzZSwgdGhlc2UgaW1wbGljYXRpb25zIG1heSBub3Qg
YmUgbmV3IGZvciB1c2VycyB3aG8gYXJlIGZhbWlsaWFyIHdpdGggZGlzYWJsaW5nIEphdmEgc2Ny
aXB0cyBhbmQgY2llLiAmbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCB3aW5kb3d0ZXh0IDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4w
cHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGNtO21h
cmdpbi1ib3R0b206NS4wcHQ7Ym9yZGVyLWNvbG9yOi1tb3otdXNlLXRleHQtY29sb3IgLW1vei11
c2UtdGV4dC1jb2xvciAtbW96LXVzZS10ZXh0LWNvbG9yIHJnYigyMDQsMjA0LDIwNCkiPg0KPGRp
dj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCB3aW5k
b3d0ZXh0IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7Ym9yZGVyLWNvbG9yOi1tb3ot
dXNlLXRleHQtY29sb3IgLW1vei11c2UtdGV4dC1jb2xvciAtbW96LXVzZS10ZXh0LWNvbG9yIGJs
dWUiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5Gb3IgZXhhbXBsZSwgdGhlIGRvY3Vt
ZW50IHN0YXRlcyB0aGF0IHRoZSBpbmZvcm1hdGlvbiBpbiBhIEZvcndhcmQtRm9yIGhlYWRlciBj
YW4gYmUgc3VwcGxpZWQgYnkNCiB0aGUgaG9zdCBpdHNlbGYgYW5kIHRoZW4gY29tbXVuaWNhdGVk
IHRvIGEgcmVtb3RlIGNvbnN1bWVyLiBUaGlzIGlzIGluZGVlZCBwb3NzaWJsZSwgYnV0IGJlY2F1
c2Ugb2YgYWJ1c2luZyBob3N0cyBzb21lIHNlcnZlcnMgaW1wbGVtZW50IHdoaXRlbGlzdHMgdG8g
dHJ1c3QgcHJveGllczsgc2VlDQo8YSBocmVmPSJodHRwczovL21ldGEud2lraW1lZGlhLm9yZy93
L2V4dGVuc2lvbnMvVHJ1c3RlZFhGRi90cnVzdGVkLWhvc3RzLnR4dCIgdGFyZ2V0PSJfYmxhbmsi
Pg0KaHR0cHM6Ly9tZXRhLndpa2ltZWRpYS5vcmcvdy9leHRlbnNpb25zL1RydXN0ZWRYRkYvdHJ1
c3RlZC1ob3N0cy50eHQ8L2E+LiAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90
ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21hcmdpbi1ib3R0b206MTIuMHB0Ij5UaGUgV2lraW1lZGlhIGNhc2UgaXMgYSB2
ZXJ5IGludGVyZXN0aW5nIG9uZSB0byByYWlzZSwgYmVjYXVzZSBpdCBkZXJpdmVzIGZyb20gYSBz
ZXQgb2YgYXNzdW1wdGlvbnMgYWJvdXQgdGhlIG5ldHdvcmsgdGhhdCBhcmUgc29tZXdoYXQgZmxh
d2VkIGFuZCB0aGVuIGF0dGVtcHRzIHRvIHBhdGNoIHRob3NlIGZsYXdzIGluDQogd2F5cyB0aGF0
IGFjdHVhbGx5IGRhbWFnZSB0aGUgbWVjaGFuaXNtcyBvZiB0aGUgc3lzdGVtIHRoZXkgb3JpZ2lu
YWxseSBidWlsdC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBw
dCI+V2lraW1lZGlhIHdhbnRzIHRvIGFsbG93IGZvbGtzIHRvIGVkaXQgd2l0aG91dCBsb2dpbiBj
cmVkZW50aWFscy4mbmJzcDsgVGhpcyBhbGxvd3MgZm9yIGFub255bW91cyB1c2VycyB0byBtYWtl
IGNvcnJlY3Rpb25zIG9yIGFkZGl0aW9uczsgdGhpcyBpcyBhIGdvYWwuJm5ic3A7IFRoZSBjb25z
ZXF1ZW5jZSBvZiB0aGF0IGdvYWwgYmVpbmcNCiBhY2hpZXZlZCBpcyB0aGF0IHRyb2xscyBvciBt
YWxpY2lvdXMgZWRpdG9ycyBjYW4gaGF2ZSBhdCBhbnl0aGluZyB0aGV5IHdhbnQuPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlJhdGhlciB0aGFu
IGluc3RpdHV0ZSBjcmVkZW50aWFscyBhbmQgQUNMcywgV2lraW1lZGlhIGF0dGVtcHRzIHRvIHN1
YnN0aXR1dGUgYmxvY2tpbmcgYnkgSVAgZm9yIGJsb2NraW5nIGJ5IGNyZWRlbnRpYWwuJm5ic3A7
IFRoZSBwcm9wZXJ0eSB0aGV5IGFyZSBsb29raW5nIGZvciBpbiBJUHMgaXMgbm90IHJlYWxseSB0
aGVyZSwNCiB0aG91Z2g6Jm5ic3A7IHRoZXkgYXJlIG5vdCB1bmlxdWUgdG8gaW5kaXZpZHVhbHMs
IGVzcGVjaWFsbHkgb3ZlciB0aW1lLiZuYnNwOyA8YnI+DQo8YnI+DQpUaGlzIGRhbWFnZXMgdGhv
c2Ugd2hvIHNoYXJlIElQIGFkZHJlc3NlcyAoZHVlIHRvIE5BVHMgb3IgcHJveGllcykuJm5ic3A7
IEFzIGZhciBhcyBJIGNhbiB0ZWxsLCB0aGUgTkFUIHByb2JsZW0gaXMgc2ltcGx5IHRyZWF0ZWQg
YXMgY29sbGF0ZXJhbCBkYW1hZ2UuJm5ic3A7IEZvciB0aGUgcHJveGllcywgdGhleSBhdHRlbXB0
IHRvIHdvcmsgYXJvdW5kIHRoZSBkYW1hZ2UgdXNpbmcgWEZGLiZuYnNwOyBUaGF0J3Mgc3Bvb2Zh
YmxlLCB0aG91Z2gsIHNvIHRoZXkgYXR0ZW1wdA0KIHRvIGxpbWl0IGl0IHRvIHNwZWNpZmljIHBy
b3hpZXMgd2hvc2UgWEZGIHRoZXkgdHJ1c3QtLW1hbnkgb2Ygd2hpY2ggcmVxdWlyZSBsb2dpbnMu
Jm5ic3A7IFRoYXQgc2hpZnRzIHRoZSBpbmZvcm1hdGlvbiBhYm91dCB3aG8gaXMgZWRpdGluZyBX
aWtpcGVkaWEgb3V0IG9mIHRoZWlyIGhhbmRzLCBidXQgbGVhdmVzIGl0IGluIHRoZSBuZXR3b3Jr
IGFuZCB0aHVzIG5vdCB0cnVseSBhbm9ueW1vdXMuJm5ic3A7IEkgdW5kZXJzdGFuZCB0aGUgZW5n
aW5lZXJpbmcgYmFsYW5jZQ0KIHRoZXkgYXJlIHRyeWluZyB0byBzdHJpa2UsIGJ1dCBJJ20gbm90
IHN1cmUgSSBjYW4gcmVjb21tZW5kIHRoZWlyIHNvbHV0aW9uLjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPltNZWRdIEnigJltIG5vdCByZWNvbW1lbmRpbmcgdGhlaXIgc29sdXRp
b24gZWl0aGVyLCBidXQgSeKAmW0gdHJ5aW5nIHRvIHJhaXNlIHRoZSBwb2ludCB0aGF0IGFuIGVu
Z2luZWVyaW5nDQogYmFsYW5jZSBpcyBvdXQgdGhlcmUuIEFDS2luZyB0aGF0IGRlcGxveW1lbnQg
cmVhbGl0eSBpcyBiZXR0ZXIgdGhhbiBpZ25vcmluZyBpdC4NCjwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48
c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPlRoZSBkZXBsb3ltZW50IGNv
bnNpZGVyYXRpb25zIHRleHQgaXMgbWVhbnQgdG8gcG9pbnQgb3V0IHRoZSBlbmdpbmVlcmluZyBi
YWxhbmNlLiZuYnNwOyBJJ20gaGFwcHkgdG8gYWRkIHRoZSB0ZXh0IG5vdGVkIGFib3ZlIChvbiBs
YXRlbmN5LCB0aGUgZW5kIHVzZXIgcmVzcG9uc2liaWxpdHkgZm9yIGNvcnJlY3QgZGF0YSwgdGhl
IFBTQVAgY2FydmUgb3V0LCBhbmQgdGhlDQogZXhwbGljaXQgbm90ZSB0aGF0IHRoZSBkb2N1bWVu
dCBkb2VzIG5vdCB0cmVhdCBob3cgdG8gb2J0YWluIGNvbnNlbnQgZnJvbSBhIHVzZXIgc28gdGhh
dCBhbiBlbmQgc3lzdGVtIGNhbiBzdXBwbHkgZGF0YSkuJm5ic3A7DQo8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPltNZWRdIE9rLCB0aGFua3MuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206
MTIuMHB0Ij5JJ20gbGVzcyBoYXBweSB0byBhZGQgbGFuZ3VhZ2Ugb24gYWR2ZXJzYXJpYWwgdHJl
YXRtZW50IG9mIGNsaWVudC1zdXBwbGllZCBkYXRhLiZuYnNwOyBUaGlzIGlzIHBhcnRseSBiZWNh
dXNlIG1hbnkgb2YgdGhlIHN5c3RlbXMgd2hpY2ggdXNlIG5ldHdvcmstc3VwcGxpZWQgZGF0YSBh
cmUgYmFzZWQgb24gYSBtaXN1bmRlcnN0YW5kaW5nIG9mIHRoZSBwcm9wZXJ0aWVzDQogb2YgdGhl
IGRhdGEgYmVpbmcgYWRkZWQuPHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4w
cHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gSSBhZ3JlZSB0aGlz
IG1heSBiZSB0aGUgY2FzZSBmb3Igc29tZSBvZiB0aGVtLCBidXQgbm90IGFsbC4NCjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9t
OjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyBJdCBpcyBwYXJ0bHkgYmVjYXVzZSB0
aGUgYWR2ZXJzYXJpYWwgcmVsYXRpb25zaGlwIGNhbiBleHRlbmQgdG8gbmV0d29yay1zdXBwbGll
ZCBkYXRhLiZuYnNwOw0KPC9zcGFuPkl0IGlzIGFsc28gYmVjYXVzZSBhIGZhaXIgZmV3IG9mIHRo
ZW0gYXJlIHNpbXBseSBzZWN1cml0eSB0aGVhdGVyLiZuYnNwOyBJZiB5b3UgaGF2ZSBhIHNwZWNp
ZmljIGVkaXQgeW91IHdvdWxkIGxpa2UgdG8gcHJvcG9zZSwgdGhvdWdoLCBJIHdpbGwgY29uc2lk
ZXIgaXQuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPlRoYW5rcyBhZ2Fpbiw8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRlZDxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_787AE7BB302AE849A7480A190F8B933009E1BDA0OPEXCLILMA3corp_--


From nobody Fri Mar  3 03:14:51 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BECE129687; Fri,  3 Mar 2017 03:14:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-hardie-privsec-metadata-insertion-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148853969059.10129.17212682561343470544.idtracker@ietfa.amsl.com>
Date: Fri, 03 Mar 2017 03:14:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B_cavt4xB2qBpzyEs3CrcMLKT18>
Cc: ietf@ietf.org, draft-hardie-privsec-metadata-insertion.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 11:14:50 -0000

Reviewer: Stewart Bryant
Review result: Ready with Nits

Reviewer: Stewart Bryant
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-hardie-privsec-metadata-insertion-06
Reviewer: Stewart Bryant
Review Date: 2017-03-03
IETF LC End Date: 2017-02-21
IESG Telechat date: 2017-03-16

Summary:  This is a well written document with two very minor nits.

Major issues: None

Minor issues: None

Nits/editorial comments: 

1.  Introduction
....
   exploited in the attacks document in [RFC7258] and the threats
s/document/documented/

=======

EDNS0 ought to be expanded.


From nobody Fri Mar  3 03:20:19 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE7E1294AD; Fri,  3 Mar 2017 03:20:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-lamps-eai-addresses-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148854001916.10113.3160004873362723901.idtracker@ietfa.amsl.com>
Date: Fri, 03 Mar 2017 03:20:19 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/z-j7eX_t18e2F9oMaMS6esWXluo>
Cc: spasm@ietf.org, ietf@ietf.org, draft-ietf-lamps-eai-addresses.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 11:20:19 -0000

Reviewer: Stewart Bryant
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-lamps-eai-addresses-??
Reviewer: Stewart Bryant
Review Date: 2017-03-03
IETF LC End Date: 2017-01-30
IESG Telechat date: 2017-03-16

Summary: Ready for Publication

Major issues: None

Minor issues: None 

Nits/editorial comments: None



From nobody Fri Mar  3 04:39:46 2017
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 829F9129862 for <ietf@ietfa.amsl.com>; Fri,  3 Mar 2017 04:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rSyaVwRHaJP9 for <ietf@ietfa.amsl.com>; Fri,  3 Mar 2017 04:39:42 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0109.outbound.protection.outlook.com [104.47.2.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D09A1297CD for <ietf@ietf.org>; Fri,  3 Mar 2017 04:39:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=0eBUvaCjWg3salZ0DnoHXVYHrSnPHH5YzQz8qGWiUAg=; b=If4Vcu5lqYukNWEVOXy/0zAPiCRZtq2zSRZbCC+LlEQauO6Xk2lCzIr54uneJxDRQZXOZ6qfbdgfzy2OoFOC8xrwcFr7N5TiZV5dLt57dMUb9AVEwaBVwaEwfIyQDAoE3uZx6gnuN1M5oww9HNZpKNKDYqOa+ktT9MvY7llS6hM=
Authentication-Results: kumari.net; dkim=none (message not signed) header.d=none;kumari.net; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.185.203.75) by VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.961.8; Fri, 3 Mar 2017 12:39:38 +0000
Message-ID: <05c101d2941a$cf8005a0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: Warren Kumari <warren@kumari.net>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <14476.1488384266@obiwan.sandelman.ca> <CAHw9_iKuZrxD=51QadPPnuofUdAeaHPQ4JvONz5Bno3HTAi71A@mail.gmail.com>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
Date: Fri, 3 Mar 2017 12:36:03 +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: [86.185.203.75]
X-ClientProxiedBy: DB6PR0601CA0043.eurprd06.prod.outlook.com (10.169.209.29) To VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13)
X-MS-Office365-Filtering-Correlation-Id: 86fbacbf-c1b0-4875-181f-08d462325b5c
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:VI1PR07MB1567;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 3:inUUc3rYjh3qykq5xhot2N9IrLXaRVghqZpnWK5EYkuGs3sNlucBT13RWp7eSAHxtah1zu+BStvI8d6NELdA8AjSD+UptFT1s8tClaKRgPjVv5NgeKAMXgVlrG67v6Y4XpEqo7nC3Mrb7lF1SEAVYgc3H+PuIZ+xDb/7xZ/dl6n6Jx/zqT4O7fRKsGqr29GM7U9f0j00zjpAfGiXf9++Wn9j94WRj/sI89iOBebQerl9awUWPLEHy9rg78rzKMOtgw9PJP+UaHhFznu4P9Td/w==; 25:+G8K7xFTojM7wV7fWI+4R9gkndAaivpQzQYu9WX1ZXxad32FiSGvg1J5/tAu0SCzeishILkkRcCbUR2PQjOQbmcAEmiqrbQj1B3PTWPxP5Mr9yubKtXWX8hJyvghd+7EE/hLR2SADKoO2J3Lyn7FB0zZWg0Bv8e8yxXtD+3nYqSAba4nbIykrt5rSXcRiPxpe9qIKcrpajgsZXaRj962T0s20h0B1/dlNvpOKEQYAEyYMbzGZFyN21CillSDgO5cRhkHYjMCLPOZ94/lW5O+4wpfKn8GbyMXYOg65FxRpugxAWeXvB8ppzLO5oa63iHJJYvP4McBCeBd4gJhJfSlLTpPCx4zxP9WRJ72qLv8VzC3C6mTn90efD53AilEzzAv9bLHZArMSXD6fqi1rWq8MKdHfEK0MGsn7rMdS5LwaCf4b8+RNpDznvikAo7p/fPL7S4wwX9bL1wKi0moEVTr1A==
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 31:7QMaaAdWPinoJlpv+qb2QBvxw2YpB7jGXdKVwxAtvLvLx4PCzU0vA8/w/m5jgmuUyNT+P3Czoe3yfWy9aachJVv8i545Srw0ykjvrWi62zHVXjlMumVe7EK7cfCJteMGXnqXljbemMUhgTYYi+EYqAuZjPji6l74w3MJmQm1YntYdX12SLci7bgSTkQYX+JhiyorLrvmyyXbwTk1uLcygpIawjjLAEzjg25NSSOy7gONRiLaLvzB5I2dbQga/5ETh5yA0y/bEhkMLEWcrV2fng7U87D/ChabDIChr40vEQA=
X-Microsoft-Antispam-PRVS: <VI1PR07MB1567262AEE270B9B6655BF34C62B0@VI1PR07MB1567.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(100405760836317);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123564025)(20161123555025)(20161123558025)(20161123562025)(20161123560025)(6072148); SRVR:VI1PR07MB1567; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1567; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 4:pRRrczSp7TbtkhkAHjjU7fOBqKfQZejfd75zpUfBHCk5f79995Z4btldszcgXipwZ8czN5iyW8ITiSX9PVWjJv3oQMzBJFZUpUwiSFUuk38ldv7M/fiE1Hc/wUHzKxFCPujd5N7NJbJkvNLHHZr5BqChIDG4cgjuxkXVZ+qhKjgo2AbTT0wybqywJomlaHzS0nXkdH+pNWDMy2KMOvB53yHPjoMnD0cs3A6cQwwmE2EUOBdCttAkOhwJ7oHKUN+NX+3RTt1+/MDQixDBm3aSGCFWDIaE2oLQprrneWFaR5l3vwy1GtuYhkmcL32sY2IHyitvUzXQfbpEyXLYU/UELnbapodpwYGmEj7gi6x7SUDeCksbweiq6PxJ2hOHxfZds2zZfCJFFaiVAYn6tAltRcmcDbXMHbGG5z++s/VOk27tEmu37puUlTlG1wZTIhVFeoippngSg3PC+Abe5YwnxOEIoCsYLQxD0chiJ87t4KIrlI9lRQ65bu7UssARerzowVxTBGMzVyP8Cb7hMkD3U4CVP/H03HPihUY0SU4E7dzeArU829rFvaJVueaRgRDEMafCKUkpjpJ0PIZHso2vUhkeuiBsgBn99nABVXIjP4I+swkdz6MEIB2Xf8vhMcS041V1hE47DISsre51pCgaMg==
X-Forefront-PRVS: 0235CBE7D0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(13464003)(24454002)(377454003)(38730400002)(62236002)(4326008)(44716002)(6496005)(61296003)(53936002)(189998001)(33646002)(53546006)(23676002)(3846002)(6116002)(42186005)(6246003)(14496001)(8676002)(76176999)(50226002)(1556002)(81686999)(81816999)(92566002)(50986999)(86362001)(50466002)(81166006)(1456003)(47776003)(230700001)(2906002)(66066001)(7736002)(305945005)(5820100001)(9686003)(229853002)(6486002)(25786008)(44736005)(84392002)(5660300001)(4720700003)(6666003)(116806002)(372894003)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB1567; H:pc6; FPR:; SPF:None; MLV:nov;  PTR:InfoNoRecords; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtWSTFQUjA3TUIxNTY3OzIzOlMxKzNpNlJNUTZucTJwWTI4bDhHWlZYdXpC?= =?utf-8?B?SzlzVmc0clIxSGZvRHhpcmg1d3VoeXpMOUloT2RzTE5NcUh2V083ZUpFei95?= =?utf-8?B?VVBsL1RyQ2lZUDFGUTVPWVh1dG9jOE5YYUJtUmdFTXhhOEZIM3ZqUjVUNmhB?= =?utf-8?B?ektzUURrZld2dVd4VjE4ZWhVV2wvRTRLdWxvQUdPSTA3STBnd1hXdE51MFRD?= =?utf-8?B?eW40Y2o0RFp4Z242Nkc4V2xCdlVLMUYzR0FrdU5MNGdneHdIY2JaQW80TjQ2?= =?utf-8?B?ak5vMmIwMXJ4S0s5dDNBaTJ5ODJtVE1WS3F0NGhENVU0bE0yWE1FRitYS200?= =?utf-8?B?WUhoMGtOanBoVG5adm9CeE1lTG5lai85SHRJOHIvZjNuTU5JbzMrU2lCd3pF?= =?utf-8?B?ZzZWbVIwTTcyM3V3TDBVdWNzdFRNM3c5eVFocGlaWmZHYmJIY0s2cnJCOGQv?= =?utf-8?B?QTRhUDRrNEFFM2RNeFRYa1lGeWJxMjA0RXVNRWZSUFRodXF4M1ZVWU9wdlU1?= =?utf-8?B?bWc5QVEwVkV0b2VtbWZvVHZ6RUNLRlhJU2dmKzd1RnV0c1QzUEpOUms2Sjg2?= =?utf-8?B?T2JOVDFUVjVWNXdienpGT2RhTWQ1b3Q5OWFyTEZhbC92cjU2MVRsUVh6aWQx?= =?utf-8?B?aGQ2Y3RzQ29OcXgwVWdYWjRyRW91TStPelZVaU4yZU5WcFdzY0tBWXNneVlT?= =?utf-8?B?WjJyM3JDbkcvU1R4SS9BSGhtTTg5OUxYQ2dOZVZ3R21TNmU1eDdtMThQMUVY?= =?utf-8?B?bkNrVzhjSUxxUnR6azhWTDN1bnB1WUVnU3NwRkxKT2hNbXFwQmZPTk1kTElI?= =?utf-8?B?eU1uZ3daVVp4Wnp5RmtOM1dMSEc4bGV6ZXlzMm1aaU9jUmpldkJFd0Jpa2pr?= =?utf-8?B?d1FoNXJ5SWFGZ0RSWVZLY0xncFdwZ2tHRXRHMzZhM0w4Rll0dVBiU1M4MUIy?= =?utf-8?B?ZkJYY1Zlbm1Nbmx0WXkwbjQ4akNRcmtZTXg3cUZYVmR0QnB5ZmxzcTY5b1dZ?= =?utf-8?B?Y093VzZJcThEaDdKTjRXU0pndTZLSUIzR2FWVHpnNzdkZUZWOG0zbHl5Rmpk?= =?utf-8?B?YXg2eGNiUTBrZWY1c29qK1ZYT0lBaXp5QjFGS1lMUHRWZ1V1SEszbm5DMkJw?= =?utf-8?B?VnJwTGtuclRDYnhQL0ZHSWdacFJLQjZVZEN4TEw0UkpVd2pzOThEQk5uMEhZ?= =?utf-8?B?Y25ORTVKVlVKYTQzRkVSLzFSMXpSaXd1Q3d0UzdZUE9TR0RJOWMxZEpTM2dx?= =?utf-8?B?dkNTdlZZRXJHVGZkcGtnb0VHME5KMmthT1A0S3ZJSHE0aWdiTjhXM1BkYklP?= =?utf-8?B?bGtXWE5EbnZXMHUyT1Z3YU5qdmVMWElDRVdTNytnRTVxUUh6YlZsQjV2K0RZ?= =?utf-8?B?NVV2aGU1SWtLczRPTFFGZk8wRksrQndKdFVlU2V0aXdVdklGU2o3ZXBtOUl5?= =?utf-8?B?UlR5dlZSZUdLdHlIMk84TFVmWnZSUi9XRlI0Tk9SWEQ4N1VVMHBlM2NFOERo?= =?utf-8?B?OUhpZ2pNbTRzdFJFWFp4ZFZ3TVN0bDI1aVJuTWpQNVFTOWVYRVBBRTMwKzZK?= =?utf-8?B?ZXRwSm9GOXNxV2JibE1Zb3FVNkE0MmxrMFhhRVc5dlgvc2JuWlN1ZFVSSERQ?= =?utf-8?B?WGxHSkE1bnRHSkZFbWY2M0hNc0pFb1JTNDhhK3ZaTit5UE4vUkRGUnYxQjVw?= =?utf-8?B?NCtYL3luaGwvTmRNVDVkMnNVVlRFTHVtaHBnVVdMM0ZueWVzajFrK3dUcWUw?= =?utf-8?Q?4+U9CE5KObp3W/olvPRz/tKIFwnMHX5iCQvzs=3D?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 6:f9dmFXTjvAXFVTzf4N6aL99T4dA8VAnoKfdWFaIovgKCoqDBRff50lzqm1wYx55K42LazOpqas87PO4Yu3xN5qjRMqvxYGpVEmmxJgYCSxYsyqsDN/bUj03CfvdWu72LMtWbdIP1SCcqw0TgqBu+8SOdD8cJfP84K2d+ZcoHYQT2Kw7gwOhEH41XrwLjSkIZI7JbJPFkXAoAuvpVx7hQa6yJyUArz9x2KEENF/bt5Go6zngWr4SXxTMKkYiKvcnt1zptvojtj5b+l9v++rscdX4I4oFw1SWfFDUhpHtLfPzV0627bt/WUnZTnDt25awpIDojvdADkFwSitSunJk2C7LZBy3KFW28jLZhBq3pnLNAAppe8wZpSW3yYLf0MEbQriTrXTkQf3zqFhPsMAnpEw==; 5:FKA+PkLpQ/l5XSiRbXNKzUGYyew87iXrPgKEXVtD66SDsrjbaqxNw/fc1X0V7zGI0o49GgJv7wocbfJdVLVDYMU399tHuypJcHgAEXqNffqlpQUwqgWgv6l0TXhK3jzhydt4MBRKNiH9bW9lyroEqAOuVEu/QmHPofLrIVJE5B8=; 24:5bDOPWSUuicEyXLhYYD/OkAbtstF7fy6c8PP5UDXB86P6RFM1lf8D0NVuZ58lhraQroBtESvP8pL2f27eIl1KclIccyI7H76wKLlRYupLjo=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 7:zGEvqOiuse/Yleg5OMHTSMIuleV2I5YtS0JrvPA+2MJmB7+SCIonp22pE5NYiNNP8rkV2yA7DBeOkwufehNronwKHQArXSEHvp5jB7cot2QRQofgx/lv0+6oxgIQMDVRDX5ktAZ+XvnSb0Hl7CMGeVBCs2e/8GUqBTGulk0SrrQcNZuTeZ9NfNQjKn3yAPzhyZ2JRv+nkIRIT4iXexbZJzkWcoK6sRjKp5hPN8/zzwDvNsbn73R/21CwUxGFZALN0btl0e+7YTBO1K91xG1JK6AiVPOK57X/7gPsDgqYGYmK9mmXma/sSRnVSztcqI89tKPL6/BcibZq6ru/en5yOA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Mar 2017 12:39:38.1887 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1567
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/beNb7swPQCVlZYk6JrpQvW1dN-c>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 12:39:44 -0000

----- Original Message -----
From: "Warren Kumari" <warren@kumari.net>
To: "Michael Richardson" <mcr+ietf@sandelman.ca>
Cc: <ietf@ietf.org>
Sent: Thursday, March 02, 2017 7:40 PM

> I've worked with a number of different authors, and there does seem to
> be a wide range of preferences.
>
> I personally like to publish early, and often; I'll often publish a
> new version integrating just one persons comments (or, of they are
> nits, batch up a few sets into one version). If there are lots of
> comments going back and forth, I don't think it is easy for WG
> participants to mentally keep track of all the different comments, how
> they interrelate, and what the final text will look like. I also think
> that it is politer to respond to feedback by integrating and
> publishing a new version, instead of just saying "Thanks, I'll get to
> them sometime....".
> Committing to GitHub kinda accomplishes this, but a: it's harder for
> participants to find, and b: the github version is a second class
> citizen.
>
> But, other authors seem to have a different view -- they'd much rather
> get everything fully squared away, all comments addressed, all 't's
> crossed and 'i's dotted.

How sensible other authors are!

A number of I-Ds I have seen in the recent past got a comment from one
experienced in the field which led the author to issue a revised
version, which prompted a comment from another experienced in the field
contradicting the first comment which led the author to ..

I give up and await IETF Last Call, or if it is an I-D where my interest
is not major, give up altogether; life's too short to track a series of
somersaults.

The IETF proceeds at a leisurely pace, taking a week or two or more for
comments to appear, so updating more often than that is
counter-productive.

Tom Petch

> One of the stickier points is what to do during WGLC -- unfortunately,
> in many groups this is where the majority of the review and feedback
> happens, and it is often viewed as poor form to revise during WGLC.
> It's often hard for the *authors* to keep track of what the consensus
> is when there are lots of comments, what the new text would look like,
> etc -- expecting random WG participants to do so is (IMO) unreasonable
> and leads to frustration and overlapping comments. I'd personally
> rather publish new versions *during WGLC* saying "This is what this
> looks like now, does this address your issues?" than trying to explain
> that we will move text from Section 3.2.5.4.3 bullet 9 to Section
> 1.7.4 to address Mike's comment, but that will mean that Billy's
> comments no longer apply because it removes the text that he's
> commenting on, other than the nits about the case of the acronym,
> which we agreed to change globally, except in section 8, because it is
> quoting from another RFC. Confused yet?
>
> W
>
> On Wed, Mar 1, 2017 at 11:04 AM, Michael Richardson
> <mcr+ietf@sandelman.ca> wrote:
> >
> > For the third time in two days I find myself, when asking others for
opinions
> > about some text, pointing at github commit logs.  With the beautiful
> > makefiles we often have, one can't even depend upon having a
formatted .txt
> > version there!
> >
> > This is not a rant for or against git or github, but rather about
what I
> > perceive as a shyness about posting intermediate versions of
Internet Drafts
> > to the datatracker.
> >
> > I understand that in academia, they never like letting half-baked
ideas out,
> > and so the -00 that we see from academics are often overdue and
overly
> > polished.  I know I can't fight that, but at least the -01, etc.
could be
> > issued faster?
> >
> > I've even heard some push back from people along the lines of, "wow,
that ID
> > has 27 revisions, is it really stable?", and my feelings have often
been more
> > along the lines of, "wow, that revision has 27 revisions, the
authors are
> > really keen and responsive".
> >
> > I appreciate for some reviewers that having more revisions implies
that they
> > think they have to look at the text more often.
> >
> > But given the diff utilities, it shouldn't matter how many revisions
there
> > were before times you look, as you can just skip the intermediate
versions.
> >
> > --
> > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> >  -= IPv6 IoT consulting =-
> >
> >
> >
>
>
>
> --
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>    ---maf
>


From nobody Fri Mar  3 04:51:52 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 608BF129876 for <ietf@ietfa.amsl.com>; Fri,  3 Mar 2017 04:51:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZbGWx4yJsXeT for <ietf@ietfa.amsl.com>; Fri,  3 Mar 2017 04:51:46 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D0C412986C for <ietf@ietf.org>; Fri,  3 Mar 2017 04:51:45 -0800 (PST)
Received: from [192.168.1.34] ([5.10.171.186]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ld3t6-1c1tE308lU-00iFzl; Fri, 03 Mar 2017 13:51:39 +0100
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Warren Kumari <warren@kumari.net>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <14476.1488384266@obiwan.sandelman.ca> <CAHw9_iKuZrxD=51QadPPnuofUdAeaHPQ4JvONz5Bno3HTAi71A@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <434ad124-e46c-fab9-9859-78ac34621096@gmx.de>
Date: Fri, 3 Mar 2017 13:51:38 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAHw9_iKuZrxD=51QadPPnuofUdAeaHPQ4JvONz5Bno3HTAi71A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:dqcHVnvHh82yFat7B1an1opOVnuguvp7QWQ2PfF7XUSk8kv7cz6 G7hsbaxSWzUexjkTtL9Q5c7azbVgpWh95vi4mialfAAc5UejzCcqbuNOyND0lOX9BuhYjaF IMcseAz509tYFu7XiAvKp7RtONPXx0pzvpJsFzaI0vvxErnSL8IPI35O48qNmCeU2u4825m 13smH/9o7fKcCfKGh8A4Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:GcoQpVa0fq0=:fLJARqKid+xVSGU6czysLH XuNTAgKM3x84e7y2OfLvd8Z6Ry2flLy4ajnVbpoZmgbDSGFI+x1jHkDiw95YijjPVkbxnyefA F8wyFRh8z1FiwEW9Wg8U46Lil1v7oWZciucSa40Tez5MIUa2oj2mu2powDyGPg4cF/wgyvEuE hAD6smmt6wTv6s2QiCR49jM1X5C/hbKzcFSRMjNBIDmUG8PfuxvpMDbxP6O3K5YQJ5S6yrrZC FXPwFBLRxlwc562qfwTHo7qoGPneegDannN37RA9qyLziX2XMzbw+zoRBVHW+KsSUy0NDb8EP AwNfnNpFvtYnmh/XEgUscCLZZ0Kx6DqKtJaCh5Lsq4Jr+TYCPA+lunvTADQXqDqrU3LDUM9EF XnuyK0M8Z3P7sH/9Ey9rbBYwRJ3pVdIC+FCbUo+ig+kaRdn+Yc3YViQux1/of/Qnp+69iglmF NBHwwyk/2QGu08HDYVe7uJJ0nDJcGK9Wh9XNO90r0aU0llheRt1+/VcBZe+KuixNeV5kDCxkM 5gX3b39AlEEiQbOOPn2YlLVPn3GDNyo4MGb4JARJJ7oNZUEfChVUmLpAv1PYvGzxMY02ugZWD aTnEPltHpErtafW8Nrk4GT9V4eieZ6v60Iqlu9NYjnAYbMix+VBsGf4NGKIW3NjKWkni2Adlz pYSkGhIXGzHsEFif2HoSBIcKjQhahtweIsg/tVuPgfQtvnMiENiH9ewsxwrQLbKXmJuEUyG0k N4GLTEFkEpjsoANerJdLnzsiDQjRhhqlMtdOG4aAd3vgPNY1bWgiqcPpQun+kCCt32XkkG7fe zpib5fg
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Uba7boaiVDWcKH-R3O_6E1u5sYw>
Cc: "ietf@ietf.org Disgust" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 12:51:50 -0000

On 2017-03-02 20:40, Warren Kumari wrote:
> ...
> Committing to GitHub kinda accomplishes this, but a: it's harder for
> participants to find, and b: the github version is a second class
> citizen.
> ...

And because of that, the boilerplate of an internet draft always should 
point out where to send feedback, look for issue trackers, etc.

Best regards, Julian


From nobody Fri Mar  3 06:23:23 2017
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 18C59129583 for <ietf@ietfa.amsl.com>; Fri,  3 Mar 2017 06:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i3ebWRlPds6Q for <ietf@ietfa.amsl.com>; Fri,  3 Mar 2017 06:23:20 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 266A7129547 for <ietf@ietf.org>; Fri,  3 Mar 2017 06:23:19 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cjo73-000FWt-VD for ietf@ietf.org; Fri, 03 Mar 2017 09:23:17 -0500
Date: Fri, 03 Mar 2017 09:23:10 -0500
From: John C Klensin <john-ietf@jck.com>
To: "ietf@ietf.org Disgust" <ietf@ietf.org>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
Message-ID: <ED57F388B27F7F5D5EC87B3A@PSB>
In-Reply-To: <434ad124-e46c-fab9-9859-78ac34621096@gmx.de>
References: <14476.1488384266@obiwan.sandelman.ca> <CAHw9_iKuZrxD=51QadPPnuofUdAeaHPQ4JvONz5Bno3HTAi71A@mail.gmail.com> <434ad124-e46c-fab9-9859-78ac34621096@gmx.de>
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-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FXSEChdNi0yjVixWvtizo7mCxtU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 14:23:21 -0000

An observation on part of this thread, stimulated by some recent
experiences...

As people think about what should go where and how rapidly, it
is easy to forget two things about working group documents.  

First, the people we call authors are supposed to be reflecting
WG decisions and preferences, not their own, and are accountable
to WG chairs in the latter's capacity as interpreters of WG
consensus.  Situations and preferences differ as do WG styles of
operation, but, for some situations, that responsibility may
justify semi-private "did I get this right?" checking and/or
wanting a draft to reflect all of the conclusions from a given
WG meeting or email thread rather than having those changes
posted incrementally and without context.

Second, we often end up with co-authors (or co-editors) on a
given document and do so for a wide variety of different
reasons.  For example, when a document is a revision of an
earlier RFC, authors of the previous version may be listed as
authors on the new one as a courtesy even if they are not
actively participating editing the revision or even in the WG
(whether that is appropriate is another discussion).  However,
there are also cases in which two or more author-editors are
active at the same time, passing the virtual pen back and forth
or otherwise collaborating in a fairly dynamic way.  For those
cases, "are these changes ok with you?" and "did I miss anything
important?" checks are appropriate and often result in document
improvements and saved WG time.

Either of those situations can justify a delay of some days in
getting an I-D posted -- longer than pushing micro-changes to
github or equivalent.  They also provide further justification
for  a snapshot-based model.   I would suggest that, if delays
for these reasons are weeks (or longer) rather then days, the WG
may have a management problem, but that, too, is a almost
entirely a separate issue.

    john






From nobody Fri Mar  3 09:06:12 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0716A12956A; Fri,  3 Mar 2017 09:06:11 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Elwyn Davies <elwynd@dial.pipex.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-jsonbis-rfc7159bis-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148856077102.10101.1427521970215789689.idtracker@ietfa.amsl.com>
Date: Fri, 03 Mar 2017 09:06:11 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5UA8ZPNRh_GBwyKv09mN2Zj_TKU>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, ietf@ietf.org, json@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 17:06:11 -0000

Reviewer: Elwyn Davies
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-jsonbis-rfc7159bis-??
Reviewer: Elwyn Davies
Review Date: 2017-03-03
IETF LC End Date: 2017-03-07
IESG Telechat date: 2017-03-16

Summary: Ready for IESG.  I checked through the varous errata cited
and it seems these are all covered as specified.  Thanks.




From nobody Fri Mar  3 09:37:15 2017
Return-Path: <csp@csperkins.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7681E129967; Fri,  3 Mar 2017 09:37:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Colin Perkins <csp@csperkins.org>
To: <tsv-art@ietf.org>
Subject: Review of draft-ietf-dprive-dtls-and-tls-profiles-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148856263248.10117.15594191397352700006.idtracker@ietfa.amsl.com>
Date: Fri, 03 Mar 2017 09:37:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3-m_v6mhgTTkC1bXHr9T6yiSjyM>
Cc: dns-privacy@ietf.org, ietf@ietf.org, draft-ietf-dprive-dtls-and-tls-profiles.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 17:37:12 -0000

Reviewer: Colin Perkins
Review result: Ready with Nits

I've reviewed this document as part of TSV-ART'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.
When done at the time of IETF Last Call, the authors should consider
this review together with any other last-call comments they receive.
Please always CC tsv-art@ietf.org if you reply to or forward this
review.

Summary: Ready with nits

The draft describe authentication mechanisms for DNS servers accessed
via TLS and DTLS, and defines profiles for DNS clients and servers
implementing DNS-over-TLS and DTLS. There seems little of transport
concern here, since the draft refers to RFC 7858 and
draft-ietf-dprive-dnsodtls to specify DNS over TLS and DTLS, and
doesn't define such mechanisms itself, Similarly, the (D)TLS profile
is a security profile, rather than transport-related changes.

I just had a couple of nits:

- The short title at the top of each page is “(D)TLS Authentication”.
If there’s space, it'd be clearer if this was “(D)TLS Authentication
for DNS”, or similar, to avoid confusion about what is being
authenticated. 

- Section 9 mandates implementation of TLS session resumption without
server-side state [RFC5077], TLS False Start, and the TLS Cached
Information Extension. I can’t comment on the security implications,
if any, but these extensions seem appropriate for reducing transport
overheads. However, the recommendations in this draft seem
inconsistent with those in RFC 7858 (e.g., RFC 7858 says "DNS servers
SHOULD enable fast TLS session resumption [RFC5077], and this SHOULD
be used when reestablishing connections" but this draft is "MUST
implement"). It would help to align these, or mark this draft as
updating the RFC. 

Colin


From nobody Fri Mar  3 13:23:27 2017
Return-Path: <alex@strugee.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 3A39E129598 for <ietf@ietfa.amsl.com>; Fri,  3 Mar 2017 13:23:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.882
X-Spam-Level: 
X-Spam-Status: No, score=-0.882 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khOA1_dLv6Oy for <ietf@ietfa.amsl.com>; Fri,  3 Mar 2017 13:23:25 -0800 (PST)
Received: from steevie.strugee.net (strugee.net [216.160.72.225]) by ietfa.amsl.com (Postfix) with ESMTP id B6741126579 for <ietf@ietf.org>; Fri,  3 Mar 2017 13:23:25 -0800 (PST)
Received: from localhost (unknown [207.251.103.46]) by steevie.strugee.net (Postfix) with ESMTPSA id 4546572E977 for <ietf@ietf.org>; Fri,  3 Mar 2017 13:23:24 -0800 (PST)
Date: Fri, 3 Mar 2017 16:23:21 -0500
From: Alex Jordan <alex@strugee.net>
Cc: IETF <ietf@ietf.org>
Subject: Re: Interest in a push-based two-factor auth standard?
Message-ID: <20170303212321.GB52509@Alexs-MacBook-Pro>
References: <20170302055128.GJ12470@Alexs-MacBook-Pro> <CA+9kkMBdheNCiAAq2xHs5v5UBFErBYhRZ5ksWFq4089ve+NK7g@mail.gmail.com> <20170303212035.GA52509@Alexs-MacBook-Pro>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6sX45UoQRIJXqkqR"
Content-Disposition: inline
In-Reply-To: <20170303212035.GA52509@Alexs-MacBook-Pro>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kGZFUC_R4hVI6os7CJWjxG0_g0A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 21:23:26 -0000

--6sX45UoQRIJXqkqR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

*sigh* CC'ing the list, which I forgot to do...

On Fri, Mar 03, 2017 at 04:20:35PM -0500, Alex Jordan wrote:
> On Thu, Mar 02, 2017 at 08:33:52AM -0800, Ted Hardie wrote:
>=20
> > The applications area uses a working group called DISPATCH to answer the
> > question "where should this work go?", so you might start by writing up=
 the
> > idea as an Internet draft and submitting to DISPATCH.  The Security area
> > uses the saag list for similar discussion, if you think it is more of a
> > security topic than a usage of web push.
>=20
> Thanks, that's very helpful. I'll take discussion there when I have an
> Internet-Draft ready.



--6sX45UoQRIJXqkqR
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJ8BAEBCgBmBQJYud7JXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRERDMyMDZGODZEQ0VFMjMzQ0MwOUQ3NDgy
Njc5NDAzNDYzM0RCQkMwAAoJECZ5QDRjPbvAyosP/RbHDXtuUF7R8aifyZIlyu8E
Uw7OdRhzK7nRS9GJ9P7qhNt796EAzOpbVS/awl1RhBxoyLpgiJA7sJA6kKzBddLf
QI8UdWEzPO+pcxu4oQY2X2WK5CTpkwwJbS84mw4v3MvFAsZfX6v6h7ikV+UUj58V
QoND86oQNGyZZ5anir4ZT9i+LQORJO4yYmmdCfE0T+K1D0v6SSkmCz+UMWihROaT
n5i4vSkeplxvbtWa9aqE76c3VSr53Xd8IOOD/lwJYEqtb4ACGeBTtSwpnmL6/EEs
15d2pCjVx1WnX77xEFpW34nn3gdLsfS7lUGWRX+7SNynpESlREqIxHmFwnqsmAMC
bzwDZ4urx0orh4nr6ZfF0YZUHCGq1cU1MAt0F2PBAI47ShKYvKqqeWVcCPgvq6iN
3oULynCUUmhexgGctkZrsMe6H3wTdv+RrUmcinSLwx1o5Nr8k26g5u0IsGjo7Hwz
rl4dwxEYDs/S7GfgG9PmJHFsE0TxwNVOQJO18cZw5PtOF/kROlmpgIIS0rkszrH2
iW6NLh+Qs0AIuCo+J+a3RXn1kjxeRJ2UnZWyWFAhDWgSW5QIm48hm61UmeoH9/fB
xrzqwZ7L2oa8Hzudl/vk4bx9rO116JGFg6+s625EIV56M9j95om/63e2uXiSDFNj
vkKhO6UOGBJRJKfL69gn
=c/3V
-----END PGP SIGNATURE-----

--6sX45UoQRIJXqkqR--


From nobody Fri Mar  3 14:46:44 2017
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 074751295C8; Fri,  3 Mar 2017 14:46:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id suwA9YakIThs; Fri,  3 Mar 2017 14:46:37 -0800 (PST)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 715C4127076; Fri,  3 Mar 2017 14:46:34 -0800 (PST)
Received: by mail-oi0-x22f.google.com with SMTP id 126so11415932oig.3; Fri, 03 Mar 2017 14:46:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mKezgPwA2bhG+GhU2xZiUlem0a0e2rz0W5CD/eUh5Ws=; b=EA1AsieYIhLH/2XSIRgh05a4sjnRFWwFP1eux07Bn9J/09VfrB5u8dXJcKxN8Ejl0k KMkGlqK8a9iw8vNbb84ABBvaNjBzfVRWeQ6mlLpLexQ9bre5gA+puWwXeLkdjDyTK8g2 hjmJJhy896kX5+X3+kHQ58BF99U4Vcza35LLJbwT0HAfd7UxIsMpwJzBQk2Dd2HmnAbK oFAzgcQ28JRX9nAHtWOwY0GBAu374fdB3cNLRCjlnTWz9RIaN5WzM6A1WWsyyHlFiKq8 wjPe0zab7CCGlp20Mr/YhVu06b8b3jkJg9HDEt9j5TGgKMlo5DR6Jrm7Y9E1txXXuCGr 03DA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mKezgPwA2bhG+GhU2xZiUlem0a0e2rz0W5CD/eUh5Ws=; b=RcKN58zgeQZSFEVRtWixy+8sT3a5SK5kIovVLps2JhxmtHsios+5slsTU7REEgxugd Sd98JMqiPrEfddQXM2cNzGslRaKysHDvtHiKWceOxkSchbSN4ItdMq9YgghtddbE87P+ dQlqZZwYhZnNGge0jMQO/cb4L4yvz7jyuRGmca/eyj9bUaAr6fIseLTckN0gq81lZySi a4xEgj2Z2OklY/jQH78owwhHc2lnWJ7yIlVNvXzVBoXo0EP8oNlG4rBDcNaNmHxx15+n 55XbgoTaYCebRf6kVSsWZtjfqM1Jq7+nukouCvx66865Ez90dusYHi0gF2MhDc+7ERyR cKzg==
X-Gm-Message-State: AMke39nvRefIHCbyRYGbbb2CoTV4Er5IiWihilH0qDLbbEhod0W/jQ39ywUJunMFY6O5ffUCTMlJ88dvAhFb4Q==
X-Received: by 10.202.236.140 with SMTP id k134mr2517654oih.123.1488581193726;  Fri, 03 Mar 2017 14:46:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.21.21 with HTTP; Fri, 3 Mar 2017 14:46:33 -0800 (PST)
In-Reply-To: <148851630299.30809.13198180923270314805.idtracker@ietfa.amsl.com>
References: <148851630299.30809.13198180923270314805.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 3 Mar 2017 14:46:33 -0800
Message-ID: <CA+RyBmXvAG0t1pXqr7TK9gySB+Wsptiq0NLZy8nHySRBh2fq4w@mail.gmail.com>
Subject: Re: Review of draft-ietf-ippm-twamp-time-format-03
To: Joel Halpern <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=001a1134fc3e4583370549db51c7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MvyBuxtU8g3eO-OpRqWe7mxaJ1c>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, draft-ietf-ippm-twamp-time-format.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 22:46:39 -0000

--001a1134fc3e4583370549db51c7
Content-Type: text/plain; charset=UTF-8

Hi Joel,
thank you for your thorough review and the most helpful comments. I've did
s/proposal/specification/ through the document. As for the section 2.1
would the following text be clearer:

The rules of setting timestamp flags in
   Modes field in server greeting and Set-Up-Response messages and
   interpreting them are as follows:

   o  If the Session-Receiver supports this extension, then the Server
      that establishes test sessions on its behalf MUST set PTPv2
      Timestamp flag to 1 in the server greeting message per the
      requirement listed in Section 2.  Otherwise, the PTPv2 Timestamp
      flag will be set to 0 to indicate that the Session-Reciever
      interprets only NTP format.

   o  If the Control-Client receives greeting message with the PTPv2
      Timestamp flag set to 0, then the Session-Sender MUST use NTP
      format for timestamp in the test session and Control-Client SHOULD
      set PTPv2 Timestamp flag to 0 in accordance with [RFC4656].  If
      the Session-Sender cannot use NTP timestamps, then the Control-
      Client SHOULD close the TCP connection associated with the OWAMP-
      Control session.

   o  If the Control-Client receives greeting message with the PTPv2
      Timestamp flag set to 1 and the Session-Sender can set timestamp
      in PTPv2 format, then the Control-Client MUST set the PTPv2
      Timestamp flag to 1 in Modes field in the Set-Up-Response message
      and the Session-Sender MUST use PTPv2 timestamp format.

   o  If the Session-Sender doesn't support this extension and can set
      timestamp only in NTP format, then the PTPv2 Timestamp flag in
      Modes field in the Set-Up-Response message will be set to 0 as
      part of Must Be Zero and the Session-Sender use NTP format.


Regards,

Greg


On Thu, Mar 2, 2017 at 8:45 PM, Joel Halpern <jmh@joelhalpern.com> wrote:

> Reviewer: Joel Halpern
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-ippm-twamp-time-format-??
> Reviewer: Joel Halpern
> Review Date: 2017-03-02
> IETF LC End Date: 2017-03-15
> IESG Telechat date: Not scheduled for a telechat
>
> Summary:
>
> Major issues:
>
> Minor issues:
>     The wording of the behavioral requirements for signaling in
> section 2.1 is atypical for IETF documents (and in my view makes it
> harder for the reader to follow.)  The rules are listed as separate
> rules, but they are actually sequential steps that must be test in
> order, exiting the process if the condition for each step is met.  But
> it does not actually say that.
>
> Nits/editorial comments:
>     Section 2.3 refers to this as a proposal.  It is a specification,
> not a proposal.  Please reword.
>
>
>

--001a1134fc3e4583370549db51c7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Joel,<div>thank you for your thorough review and the mo=
st helpful comments. I&#39;ve did s/proposal/specification/ through the doc=
ument. As for the section 2.1 would the following text be clearer:</div><di=
v><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"=
>The rules of setting timestamp flags in
   Modes field in server greeting and Set-Up-Response messages and
   interpreting them are as follows:

   o  If the Session-Receiver supports this extension, then the Server
      that establishes test sessions on its behalf MUST set PTPv2
      Timestamp flag to 1 in the server greeting message per the
      requirement listed in Section 2.  Otherwise, the PTPv2 Timestamp
      flag will be set to 0 to indicate that the Session-Reciever
      interprets only NTP format.

   o  If the Control-Client receives greeting message with the PTPv2
      Timestamp flag set to 0, then the Session-Sender MUST use NTP
      format for timestamp in the test session and Control-Client SHOULD
      set PTPv2 Timestamp flag to 0 in accordance with [RFC4656].  If
      the Session-Sender cannot use NTP timestamps, then the Control-
      Client SHOULD close the TCP connection associated with the OWAMP-
      Control session.

   o  If the Control-Client receives greeting message with the PTPv2
      Timestamp flag set to 1 and the Session-Sender can set timestamp
      in PTPv2 format, then the Control-Client MUST set the PTPv2
      Timestamp flag to 1 in Modes field in the Set-Up-Response message
      and the Session-Sender MUST use PTPv2 timestamp format.

   o  If the Session-Sender doesn&#39;t support this extension and can set
      timestamp only in NTP format, then the PTPv2 Timestamp flag in
      Modes field in the Set-Up-Response message will be set to 0 as
      part of Must Be Zero and the Session-Sender use NTP format.

</pre><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-w=
rap"><font face=3D"arial, helvetica, sans-serif">Regards,</font></pre><pre =
style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"><font =
face=3D"arial, helvetica, sans-serif">Greg</font></pre></div></div><div cla=
ss=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Mar 2, 2017 at 8:=
45 PM, Joel Halpern <span dir=3D"ltr">&lt;<a href=3D"mailto:jmh@joelhalpern=
.com" target=3D"_blank">jmh@joelhalpern.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">Reviewer: Joel Halpern<br>
Review result: Ready with Nits<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-ippm-twamp-time-<wbr>format-??<br>
Reviewer: Joel Halpern<br>
Review Date: 2017-03-02<br>
IETF LC End Date: 2017-03-15<br>
IESG Telechat date: Not scheduled for a telechat<br>
<br>
Summary:<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
=C2=A0 =C2=A0 The wording of the behavioral requirements for signaling in<b=
r>
section 2.1 is atypical for IETF documents (and in my view makes it<br>
harder for the reader to follow.)=C2=A0 The rules are listed as separate<br=
>
rules, but they are actually sequential steps that must be test in<br>
order, exiting the process if the condition for each step is met.=C2=A0 But=
<br>
it does not actually say that.<br>
<br>
Nits/editorial comments:<br>
=C2=A0 =C2=A0 Section 2.3 refers to this as a proposal.=C2=A0 It is a speci=
fication,<br>
not a proposal.=C2=A0 Please reword.<br>
<br>
<br>
</blockquote></div><br></div>

--001a1134fc3e4583370549db51c7--


From nobody Fri Mar  3 15:13:27 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C914129631; Fri,  3 Mar 2017 15:13:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0x2qRqygP8FU; Fri,  3 Mar 2017 15:13:17 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A770D1293DB; Fri,  3 Mar 2017 15:13:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 9036E240367; Fri,  3 Mar 2017 15:13:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1488582797; bh=4Fk+hOh4pyp+khVzK6zqLOmdAjdqsyL2k8RqQC+iYi4=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=U5kJP22xKhjr5QLV4drtMsGqiZAj5Pgqde2dCc3d4bBNgU7rLRdD1892TRbddxXTG oAn/t48wd534Q2PjCg2EZw9X0DxDUawQSfMyOTQb52isMBc1bZnxm3o8TEFr3EJrRJ fgCw9/QinluyxBEJWSo12qUtA54bJpMOKJ6Xmo/I=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 81047243330; Fri,  3 Mar 2017 15:12:46 -0800 (PST)
Subject: Re: Review of draft-ietf-ippm-twamp-time-format-03
To: Greg Mirsky <gregimirsky@gmail.com>
References: <148851630299.30809.13198180923270314805.idtracker@ietfa.amsl.com> <CA+RyBmXvAG0t1pXqr7TK9gySB+Wsptiq0NLZy8nHySRBh2fq4w@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <eb6f4608-71d0-0572-7f49-cc06740b647f@joelhalpern.com>
Date: Fri, 3 Mar 2017 18:12:42 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CA+RyBmXvAG0t1pXqr7TK9gySB+Wsptiq0NLZy8nHySRBh2fq4w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l2XcE_8Rk7oVtrHFhO9-ayBDfKM>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, draft-ietf-ippm-twamp-time-format.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 23:13:19 -0000

Yes, that makes the relationship of the conditions significantly clearer.
Thank you,
Joel

On 3/3/17 5:46 PM, Greg Mirsky wrote:
> Hi Joel,
> thank you for your thorough review and the most helpful comments. I've
> did s/proposal/specification/ through the document. As for the section
> 2.1 would the following text be clearer:
>
> The rules of setting timestamp flags in
>    Modes field in server greeting and Set-Up-Response messages and
>    interpreting them are as follows:
>
>    o  If the Session-Receiver supports this extension, then the Server
>       that establishes test sessions on its behalf MUST set PTPv2
>       Timestamp flag to 1 in the server greeting message per the
>       requirement listed in Section 2.  Otherwise, the PTPv2 Timestamp
>       flag will be set to 0 to indicate that the Session-Reciever
>       interprets only NTP format.
>
>    o  If the Control-Client receives greeting message with the PTPv2
>       Timestamp flag set to 0, then the Session-Sender MUST use NTP
>       format for timestamp in the test session and Control-Client SHOULD
>       set PTPv2 Timestamp flag to 0 in accordance with [RFC4656].  If
>       the Session-Sender cannot use NTP timestamps, then the Control-
>       Client SHOULD close the TCP connection associated with the OWAMP-
>       Control session.
>
>    o  If the Control-Client receives greeting message with the PTPv2
>       Timestamp flag set to 1 and the Session-Sender can set timestamp
>       in PTPv2 format, then the Control-Client MUST set the PTPv2
>       Timestamp flag to 1 in Modes field in the Set-Up-Response message
>       and the Session-Sender MUST use PTPv2 timestamp format.
>
>    o  If the Session-Sender doesn't support this extension and can set
>       timestamp only in NTP format, then the PTPv2 Timestamp flag in
>       Modes field in the Set-Up-Response message will be set to 0 as
>       part of Must Be Zero and the Session-Sender use NTP format.
>
> Regards,
>
> Greg
>
>
> On Thu, Mar 2, 2017 at 8:45 PM, Joel Halpern <jmh@joelhalpern.com
> <mailto:jmh@joelhalpern.com>> wrote:
>
>     Reviewer: Joel Halpern
>     Review result: Ready with Nits
>
>     I am the assigned Gen-ART reviewer for this draft. The General Area
>     Review Team (Gen-ART) reviews all IETF documents being processed
>     by the IESG for the IETF Chair.  Please treat these comments just
>     like any other last call comments.
>
>     For more information, please see the FAQ at
>
>     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq
>     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>
>     Document: draft-ietf-ippm-twamp-time-format-??
>     Reviewer: Joel Halpern
>     Review Date: 2017-03-02
>     IETF LC End Date: 2017-03-15
>     IESG Telechat date: Not scheduled for a telechat
>
>     Summary:
>
>     Major issues:
>
>     Minor issues:
>         The wording of the behavioral requirements for signaling in
>     section 2.1 is atypical for IETF documents (and in my view makes it
>     harder for the reader to follow.)  The rules are listed as separate
>     rules, but they are actually sequential steps that must be test in
>     order, exiting the process if the condition for each step is met.  But
>     it does not actually say that.
>
>     Nits/editorial comments:
>         Section 2.3 refers to this as a proposal.  It is a specification,
>     not a proposal.  Please reword.
>
>
>


From nobody Fri Mar  3 15:49:23 2017
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 6814B127071; Fri,  3 Mar 2017 15:49:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sqjS9Ltk3mSR; Fri,  3 Mar 2017 15:49:20 -0800 (PST)
Received: from mail-ot0-x229.google.com (mail-ot0-x229.google.com [IPv6:2607:f8b0:4003:c0f::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D271126D73; Fri,  3 Mar 2017 15:49:20 -0800 (PST)
Received: by mail-ot0-x229.google.com with SMTP id x37so39388133ota.2; Fri, 03 Mar 2017 15:49:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kaW2VGy8CCwf9Z3GdFzN+eSg9HwxBL/fZNKOkuNa9k0=; b=P/QwJ4zuBrH8OH4K3ZqDzDJK4WWrOCj9NGBoMFpu9Cwsyyt9oLTbmbNKChoWuB/MrL UqGWGogQrTbkurMJBEZZGUrJf9cPtLpoBj6hRkgek44LvmtCZ/e2epX+6TE1UhtEYJVo FR76lHbIUoikBf5pppFZNTgymE1NVKXaUHafA77aE46wOiA1Qv0284Vj60VyFEL8KnbD bZZiJj4gCVQp3xHTfa+ytS/6N+57npqObeJni0qdzzToCE7JbVJaKM1YKOppLw9Y2XBN HotifeO8V8HOARo6Ht/WclVOVNcGAGgkoXEsA2iWRqI0fKMCFbmXzp/NcrWTlpF+ti/O gcPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kaW2VGy8CCwf9Z3GdFzN+eSg9HwxBL/fZNKOkuNa9k0=; b=OfLiLJR3Fz/+dsuWv77stf+zX9o0Xd3pea348vFeXApviGnpqpfjODHbxKhg5Gvh3H VWyVKjENlfbFyTeU/f8whXgPSXl443/dxLb8m1AmBrOoM9kmnA7IFHEtxW/V5yQGUpiY q6e5motHV1dlQG978kQ3r4/wgRInf41ij29uDv1EFQ6D6PJlpHN15wOU5I6mmSKoYKpa lXxxnXsoWNDMcJSu+0RSuGBlwVfqKO71E6R3UYriMAdbvsshb9lYsPoPMWTnIb0L8Yka +a9GA9rPtYafLwrtJsLuTV5NXKiaXq9GewxA4Ytr/gYQ9oDuu2brZ7WT2qqqfM5IZfRU rljw==
X-Gm-Message-State: AMke39kx3r+fr0Jv04G6xGiMBjZfjFbfwGRy8YYocdrt7puJVZT28Pwv73YOkx++yGe8JsLTbZh5qHoLhQGcfQ==
X-Received: by 10.157.63.145 with SMTP id r17mr2546566otc.47.1488584959356; Fri, 03 Mar 2017 15:49:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Fri, 3 Mar 2017 15:48:48 -0800 (PST)
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Fri, 3 Mar 2017 15:48:48 -0800
Message-ID: <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com>
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Content-Type: multipart/alternative; boundary=001a11c01770b875ee0549dc31ca
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mR0JADFGAgq2IYxW_8NNd1Kf9_0>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Mar 2017 23:49:22 -0000

--001a11c01770b875ee0549dc31ca
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Mohamed,

I've updated the draft and posted -07.  I believe it includes all of the
elements on which we have already agreed.  Some additional comments
in-line, once again with some snippage for readability.

On Fri, Mar 3, 2017 at 1:23 AM, <mohamed.boucadair@orange.com> wrote:

>
>
>
> The intent is that it is information useful to those considering whether
> restoring metadata lost to encryption in mid-network is the right way to =
go.
>
> [Med] This is another assumption in the document that I disagree with: It
> seems that you assume that an on-path device, that inserts metadata, is
> necessarily RESTORING back that information. This is not true for many
> efforts:
>
=C2=B7         A Forward-For header inserted by a proxy does not restore an=
y
> data; it does only reveal data that is already present in the packet issu=
ed
> by the client itself.
>
That's what restore means here.  If the information is present as metadata
in the packet sent to the proxy but would be absent as metadata under
normal operation of the proxy, adding it back in somewhere else restores
the metadata.  So origin IP address starts out in the IP header of the
original packet but gets pushed from that slot when the proxy constructs
the onward IP packet to the server.  For it to reach the server, it has to
be placed somewhere else in the onward packet, restoring the lost metadata.

Had it been present in the packet as header value in the HTTP exchange, it
would not have been stripped by normal operation.  There proxy operation
forwarding it on would be simply preserving it.




> =C2=B7         An address sharing device, under for example DS-Lite (RFC6=
333),
> that inserts the source IPv6 prefix in the TCP HOST_ID option (RFC7974) i=
s
> not RESTORING any data. The content of that TCP option is already visible
> in the packet sent by the host.
>
I agree with the IESG analysis of RFC7974.  It does restore information by
taking information which normal operation would have elided and restores it=
.


> =C2=B7         Service Function Chaining WG (https://datatracker.ietf.org=
/
> wg/sfc/about/) is defining an architecture to communicate metadata by
> on-path devices; that metadata is inserted at the network side. Border
> nodes will make sure that data is stripped before forwarding packets to t=
he
> ultimate destinations. The metadata can be a subscriber-id, a policy-id,
> etc.
>
>
>

I'm afraid I don't have enough context to know what border node operations
are here, so this is difficult for me to comment on, but I hope the two
examples above clarify my thinking.

> So when draft-hardie-* says: =E2=80=9CDo not add metadata to flows at int=
ermediary devices unless
>
>    a positive affirmation of approval for restoration has been received
>
>    from the actor whose data will be added.=E2=80=9D
>
>
>
> (1) Do you assume that the sample examples I listed above fall under your
> advice?
>
> (2) How an on-path device will know the data it intends to insert is a
> =E2=80=9Crestoration=E2=80=9D?
>

If the data is taken from a portion of the packet that would not normally
be forwarded to an upstream host and added to a portion that is forwarded
to an upstream host, then the device adding the data back in should know it
is a restoration.



> (3) Does it mean that for new data (i.e., that are not restoration),
> on-path devices are free to do whatever they want? For me, this is
> undesirable. There is a void there. A statement to require those networks
> to avoid leaking privacy information must be included.
>
>
Brian Trammell has an ever growing list of side channels attacks, and this
document doesn't mean to cover that entire ground.  It's advice for
protocol designers on what the privacy implications are of making the
choice to use network elements to carry this data.



>
>
> Another assumption is made here:
>
>
>
>    Instead, design the protocol so that the actor can add such metadata
>
>    themselves so that it flows end-to-end, rather than requiring the
>
>    action of other parties.  In addition to improving privacy, this
>
>    approach ensures consistent availability between the communicating
>
>    parties, no matter what path is taken.
>
>
>
> This text claims that providing data by the endpoint ensures a =E2=80=9Cc=
onsistent
> availability=E2=80=9D of that information. This is broken for a multi-hom=
ed host
> that uses for example Forward-For header: Obviously, the content of the
> header if injected by the endpoint will depend on the path.
>

If the endpoint sends the data, data will be consistently available in that
header.  The data changes, of course.



>
> [Med] Resources may not be restricted to CPU or disk but may be granting
> access to the service (e.g., download a file when a quota per source
> address is enforced). It can be whatever the servers consider to be
> critical for them; it is up to the taste of the service design to
> characterize it. The NEW wording proposed above is technically correct.
> Please reconsider adding it to the draft.
>
>
>

I did consider it, but I continue to believe that it moves the needle too
far into simple server preference.  I retained the original PSAP language
in -07 as a result.

I also added a note about your extensive review.  While you and I clearly
have some differences of view, the document has gotten better from your
engagement with it, and I appreciate your efforts.

regards,

Ted

--001a11c01770b875ee0549dc31ca
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Mohamed,<br><br></div>I&#39;ve updated the draft a=
nd posted -07.=C2=A0 I believe it includes all of the elements on which we =
have already agreed.=C2=A0 Some additional comments in-line, once again wit=
h some snippage for readability.<br><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Fri, Mar 3, 2017 at 1:23 AM,  <span dir=3D"ltr">&lt;<=
a href=3D"mailto:mohamed.boucadair@orange.com" target=3D"_blank">mohamed.bo=
ucadair@orange.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"FR">
<br><div class=3D"m_7770722288423157249WordSection1"><span class=3D""></spa=
n><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color=
:black" lang=3D"EN-US"></span><div style=3D"border:none;border-left:solid b=
lue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div><span class=3D"">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The intent is that it is inform=
ation useful to those considering whether restoring metadata lost to encryp=
tion in mid-network is the right way to go.<u></u><u></u></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] This is another as=
sumption in the document that I disagree with: It seems that you assume tha=
t an on-path device, that inserts metadata, is necessarily
 RESTORING back that information. This is not true for many efforts:</span>=
 <br></p></div></div></div></div></div></div></div></blockquote><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><div cl=
ass=3D"m_7770722288423157249WordSection1"><div style=3D"border:none;border-=
left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div><p cla=
ss=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;;color:black" lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"m_7770722288423157249MsoListParagraph"><span style=3D"font-size=
:10.0pt;font-family:Symbol;color:black" lang=3D"EN-US"><span>=C2=B7<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><span style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;;color:black" lang=3D"EN-US">A Forward-For header inserted by =
a proxy does not restore any data; it does only reveal data that is already=
 present in the packet issued by the
 client itself.</span></p></div></div></div></div></div></div></div></block=
quote><div>That&#39;s what restore means here.=C2=A0 If the information is =
present as metadata in the packet sent to the proxy but would be absent as =
metadata under normal operation of the proxy, adding it back in somewhere e=
lse restores the metadata.=C2=A0 So origin IP address starts out in the IP =
header of the original packet but gets pushed from that slot when the proxy=
 constructs the onward IP packet to the server.=C2=A0 For it to reach the s=
erver, it has to be placed somewhere else in the onward packet, restoring t=
he lost metadata.<br></div><div><br></div><div>Had it been present in the p=
acket as header value in the HTTP exchange, it would not have been stripped=
 by normal operation.=C2=A0 There proxy operation forwarding it on would be=
 simply preserving it.<br><br><br>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><div class=3D"m_777072228=
8423157249WordSection1"><div style=3D"border:none;border-left:solid blue 1.=
5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div>
<p class=3D"m_7770722288423157249MsoListParagraph"><u></u><span style=3D"fo=
nt-size:10.0pt;font-family:Symbol;color:black" lang=3D"EN-US"><span>=C2=B7<=
span style=3D"font:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;;color:black" lang=3D"EN-US">An address sharing device,=
 under for example DS-Lite (RFC6333), that inserts the source IPv6 prefix i=
n the TCP HOST_ID option (RFC7974) is not RESTORING
 any data. The content of that TCP option is already visible in the packet =
sent by the host.
</span></p></div></div></div></div></div></div></div></blockquote><div>I ag=
ree with the IESG analysis of RFC7974.=C2=A0 It does restore information by=
 taking information which normal operation would have elided and restores i=
t.<br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=
=3D"purple" lang=3D"FR"><div class=3D"m_7770722288423157249WordSection1"><d=
iv style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.=
0pt"><div><div><div><div><p class=3D"m_7770722288423157249MsoListParagraph"=
><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:=
black" lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"m_7770722288423157249MsoListParagraph"><u></u><span style=3D"fo=
nt-size:10.0pt;font-family:Symbol;color:black" lang=3D"EN-US"><span>=C2=B7<=
span style=3D"font:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;;color:black" lang=3D"EN-US">Service Function Chaining =
WG (<a href=3D"https://datatracker.ietf.org/wg/sfc/about/" target=3D"_blank=
">https://datatracker.ietf.org/<wbr>wg/sfc/about/</a>) is defining an
 architecture to communicate metadata by on-path devices; that metadata is =
inserted at the network side. Border nodes will make sure that data is stri=
pped before forwarding packets to the ultimate destinations. The metadata c=
an be a subscriber-id, a policy-id,
 etc.<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:16.8pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"EN-US"><u=
></u>=C2=A0</span></p></div></div></div></div></div></div></div></blockquot=
e><div><br></div><div>I&#39;m afraid I don&#39;t have enough context to kno=
w what border node operations are here, so this is difficult for me to comm=
ent on, but I hope the two examples above clarify my thinking. <br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR=
"><div class=3D"m_7770722288423157249WordSection1"><div style=3D"border:non=
e;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><d=
iv><p class=3D"MsoNormal" style=3D"margin-left:16.8pt"><span style=3D"font-=
size:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"EN-US"=
><u></u></span></p>
<pre><span style=3D"color:black" lang=3D"EN-US">So when draft-hardie-* says=
: =E2=80=9C</span><span lang=3D"EN-US">Do not add metadata to flows at inte=
rmediary devices unless<u></u><u></u></span></pre>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;" lang=3D"EN-US">=C2=A0=C2=A0 a positive affirmation of appr=
oval for restoration has been received<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;" lang=3D"EN-US">=C2=A0=C2=A0 from the actor whose data will=
 be added.</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;;color:black" lang=3D"EN-US">=E2=80=9D<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:16.8pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"EN-US">(1=
) Do you assume that the sample examples I listed above fall under your adv=
ice?<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:16.8pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"EN-US">(2=
) How an on-path device will know the data it intends to insert is a =E2=80=
=9Crestoration=E2=80=9D?</span></p></div></div></div></div></div></div></di=
v></blockquote><div><br></div><div>If the data is taken from a portion of t=
he packet that would not normally be forwarded to an upstream host and adde=
d to a portion that is forwarded to an upstream host, then the device addin=
g the data back in should know it is a restoration.<br><br></div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple"=
 lang=3D"FR"><div class=3D"m_7770722288423157249WordSection1"><div style=3D=
"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><=
div><div><div><p class=3D"MsoNormal" style=3D"margin-left:16.8pt"><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black" lan=
g=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:16.8pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"EN-US">(3=
) Does it mean that for new data (i.e., that are not restoration), on-path =
devices are free to do whatever they want? For me,
 this is undesirable. There is a void there. A statement to require those n=
etworks to avoid leaking privacy information must be included.
</span><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u></span></p></div></div><=
/div></div></div></div></div></blockquote><div><br></div><div>Brian Trammel=
l has an ever growing list of side channels attacks, and this document does=
n&#39;t mean to cover that entire ground.=C2=A0 It&#39;s advice for protoco=
l designers on what the privacy implications are of making the choice to us=
e network elements to carry this data.<br></div><div><br>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><d=
iv class=3D"m_7770722288423157249WordSection1"><div style=3D"border:none;bo=
rder-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div><=
p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Cou=
rier New&quot;;color:black" lang=3D"EN-US">=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">Another assumption is made here=
:
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;" lang=3D"EN-US">=C2=A0=C2=A0 Instead, design the protocol s=
o that the actor can add such metadata<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;" lang=3D"EN-US">=C2=A0=C2=A0 themselves so that it flows en=
d-to-end, rather than requiring the<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;" lang=3D"EN-US">=C2=A0=C2=A0 action of other parties.=C2=A0=
 In addition to improving privacy, this<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;" lang=3D"EN-US">=C2=A0=C2=A0 approach ensures consistent av=
ailability between the communicating<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;" lang=3D"EN-US">=C2=A0=C2=A0 parties, no matter what path i=
s taken.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;" lang=3D"EN-US">This text claims that providing data by the=
 endpoint ensures a =E2=80=9Cconsistent availability=E2=80=9D of that infor=
mation. This is broken for a multi-homed host that uses for example
 Forward-For header: Obviously, the content of the header if injected by th=
e endpoint will depend on the path. </span></p></div></div></div></div></di=
v></div></div></blockquote><div><br></div><div>If the endpoint sends the da=
ta, data will be consistently available in that header.=C2=A0 The data chan=
ges, of cou<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&qu=
ot;;color:black" lang=3D"EN-US">rse.<br></span><span class=3D""><p class=3D=
"MsoNormal"><br><span style=3D"color:black"></span></p></span></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><di=
v class=3D"m_7770722288423157249WordSection1"><div style=3D"border:none;bor=
der-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div><s=
pan class=3D"">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><u></u>=C2=A0<u></u></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] Resources may not =
be restricted to CPU or disk but may be granting access to the service (e.g=
., download a file when a quota per source address is enforced).
 It can be whatever the servers consider to be critical for them; it is up =
to the taste of the service design to characterize it. The NEW wording prop=
osed above is technically correct. Please reconsider adding it to the draft=
.
</span><span lang=3D"EN-US"><br>
<br>
=C2=A0 </span></p></div></div></div></div></div></div></div></blockquote><d=
iv><br></div><div>I did consider it, but I continue to believe that it move=
s the needle too far into simple server preference.=C2=A0 I retained the or=
iginal PSAP language in -07 as a result.<br></div><div>=C2=A0<br></div><div=
>I also added a note about your extensive review.=C2=A0 While you and I cle=
arly have some differences of view, the document has gotten better from you=
r engagement with it, and I appreciate your efforts.<br><br></div><div>rega=
rds,<br><br></div><div>Ted<br></div></div></div></div>

--001a11c01770b875ee0549dc31ca--


From nobody Fri Mar  3 16:38:35 2017
Return-Path: <David.Black@dell.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C788E1293E4; Fri,  3 Mar 2017 16:38:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.com header.b=csPdz4Bc; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=rXp6Ltg/
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K_41bx9moLZL; Fri,  3 Mar 2017 16:38:27 -0800 (PST)
Received: from esa6.dell-outbound.iphmx.com (esa6.dell-outbound.iphmx.com [68.232.149.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53B5D12706D; Fri,  3 Mar 2017 16:38:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1488587907; x=1520123907; h=from:cc:to:subject:date:message-id:references: in-reply-to:mime-version; bh=q7PW85yL+GbZtd7O6fYi9MTQIV+2QzGTVM/stRaOk/Y=; b=csPdz4Bcq5aPmmM8rPkzinnAjXUS7tGTXDYy0iGbwz2oEt6fkMeBWyz2 VMC68JXTs4m1dvieZk/BRRbMqjZwFMolgSo9zxuPpB3lx12nH2JFc3Ref LGJrzuUlCsieZjbMFAH78m+yAkPAy7ANE9QBvIWm87TgKOhgn/0K5Epy/ I=;
Received: from esa3.dell-outbound2.iphmx.com ([68.232.154.63]) by esa6.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Mar 2017 18:38:26 -0600
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwdur.emc.com ([128.221.224.79]) by esa3.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Mar 2017 06:37:21 +0600
Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v240cN3O019994 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 3 Mar 2017 19:38:24 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com v240cN3O019994
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1488587904; bh=N+E+HZVZ5jwA77wVi+Ooc8rq/eM=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=rXp6Ltg/sA1Fo+tPP5Eek4Id+vf5ZHl3dHqWKNF5KVq70uwXPtr4JZQnyhGewH/OT UYiIOiKlPEpLEyi1zub1rtkfkGLR3PNrqzAL9yvhhdW/Mor1JZp/zHuhdV73te0xAH Vxnlz9Ww40ylmv+30KciJQaX0j49uYu01LCmuXIE=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com v240cN3O019994
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd51.lss.emc.com (RSA Interceptor); Fri, 3 Mar 2017 19:37:00 -0500
Received: from MXHUB310.corp.emc.com (MXHUB310.corp.emc.com [10.146.3.36]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v240c5hd012718 (version=TLSv1.2 cipher=AES128-SHA256 bits=128 verify=FAIL); Fri, 3 Mar 2017 19:38:06 -0500
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB310.corp.emc.com ([10.146.3.36]) with mapi id 14.03.0266.001; Fri, 3 Mar 2017 19:38:05 -0500
To: Shitanshu Shah <shitanshu_shah@hotmail.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
Subject: RE: Review of draft-ietf-idr-sla-exchange-10
Thread-Topic: Review of draft-ietf-idr-sla-exchange-10
Thread-Index: AQHSjn2hotpFQg8pf0qPmuGxW7GZeaF4QrTwgACFLACABFiS0IAB9hiAgATKWFA=
Date: Sat, 4 Mar 2017 00:38:05 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362F8DD70A@MX307CL04.corp.emc.com>
References: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com> <DM3PR13MB0604160394059613AD0331AFE5520@DM3PR13MB0604.namprd13.prod.outlook.com>, <CE03DB3D7B45C245BCA0D243277949362F8C4510@MX307CL04.corp.emc.com> <DM3PR13MB0604865EC77A246609544830E5520@DM3PR13MB0604.namprd13.prod.outlook.com>, <CE03DB3D7B45C245BCA0D243277949362F8D16F3@MX307CL04.corp.emc.com> <DM3PR13MB0604AF5667DD40C1C569422AE5560@DM3PR13MB0604.namprd13.prod.outlook.com>
In-Reply-To: <DM3PR13MB0604AF5667DD40C1C569422AE5560@DM3PR13MB0604.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.62]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949362F8DD70AMX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QAYqrWy8hAjwpxsfGrRSKw2_XI0>
Cc: "idr@ietf.org" <idr@ietf.org>, "Black, David" <David.Black@dell.com>, "draft-ietf-idr-sla-exchange.all@ietf.org" <draft-ietf-idr-sla-exchange.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Mar 2017 00:38:32 -0000

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

Embedded in my question about VPNs is an implicit suggestion (which I'll no=
w make explicit ...) -- this L2 overhead parameter would be more robust if =
it were defined as the number of octets difference between the full frame t=
hat is sent on the wire and the size of the IP packet to which  the token b=
uckets apply.  Even if there are no known current needs to account for anyt=
hing other than L2 framing, this approach is robust to future network engin=
eering encapsulation "creativity" ;-).

Thanks, --David

From: Tsv-art [mailto:tsv-art-bounces@ietf.org] On Behalf Of Shitanshu Shah
Sent: Tuesday, February 28, 2017 1:24 PM
To: Black, David; tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org
Subject: Re: [Tsv-art] Review of draft-ietf-idr-sla-exchange-10




Hi David,



We will add more text to clarify rationale for L2_OVERHEAD.



Do you have a preference or suggest a way to specify L2 rates? We will work=
 on defining 2 TSpecs to specify two rates (min and max).

As far as VPN terminating between Consumer and Producer, I am not aware of =
use-cases, at least in the context of the deployment scenario considered fo=
r the draft.

Regards,
Shitanshu
________________________________
From: Black, David <David.Black@dell.com<mailto:David.Black@dell.com>>
Sent: Monday, February 27, 2017 10:42 AM
To: Shitanshu Shah; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>; Black, David
Subject: RE: Review of draft-ietf-idr-sla-exchange-10

Ok, please make that rationale for the L2_OVERHEAD parameter clear in the d=
raft:
> Though for the cases where physical links are not to be over-run, and/or,=
 sla defined are based on l2 rates, the Consumer would
> need to know l2 overhead from the Producer. Otherwise 10 byes of l2 overh=
ead difference on 64 bytes packets can be significant
> compare to on 1400 bytes packets, and thus the Producer does not have a w=
ay to convert rates to ip based (this can cause
> functional issue), since this has to be per packet consideration.
It looks like the result is that if the Producer's L2 overhead is larger th=
an the Consumer's, and the token buckets are specified in IP octets, the co=
nsumer has to calculate a per-packet charge of the L2 overhead difference a=
gainst the IP token bucket (and in the opposite case, there may be a per-pa=
cket credit).   Are there cases where the overhead is not all L2, e.g., SLA=
/TCA Consumer is using a VPN that terminates between Consumer and Producer?

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 1:05 PM
To: Black, David; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



One response inline ##svshah2

________________________________
From: Black, David <David.Black@dell.com<mailto:David.Black@dell.com>>
Sent: Friday, February 24, 2017 8:53 AM
To: Shitanshu Shah; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>; Black, David
Subject: RE: Review of draft-ietf-idr-sla-exchange-10

David> Inline ...

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 4:09 AM
To: Black, David; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



Thank you for taking time for the review..



Please find our response inline ##svshah and [Med]


Regards,
Shitanshu
________________________________
From: David Black <david.black@emc.com<mailto:david.black@emc.com>>
Sent: Tuesday, February 21, 2017 3:31 PM
To: tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Review of draft-ietf-idr-sla-exchange-10

Reviewer: David Black
Review result: Not Ready

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. When done at the time of IETF
Last Call, the authors should consider this review together with any
other last-call comments they receive. Please always CC
tsv-art@ietf.org<mailto:tsv-art@ietf.org> if you reply to or forward this r=
eview.

Document: draft-ietf-idr-sla-10
Reviewer: David Black
Review Date: February 21, 2017

Review result: Not Ready

This is an early TSV-ART review of a working group draft, requested by
the IDR Working Group.

This draft defines an extension to BGP to allow exchange of traffic
handling parameters (e.g., configured rates, burst sizes, drop
thresholds).  While this is a useful area of technology to standardize
across network operators, this draft has significant problems, and
parts of it could use some serious rethought.

This reviewer has discussed small portions of this draft with some of
the authors in the past, but this is his first comprehensive reading
and review of the draft.

Major Issues:

[1] The draft is misnamed.  This is not an SLA (Service Level
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -
see the definition of TCA in RFC 2475.  This draft should start from
that definition and generalize the applicability of TCA beyond
Diffserv.  Large areas of SLA content are not covered by this draft -
for more details, see the Wikipedia article on SLA:
https://en.wikipedia.org/wiki/Service-level_agreement .

##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.


David> That would be good, thanks.

[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to
specify a token bucket is a good idea, but it's not a good idea to
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)
octets, as the RFC 2115 TSpec is specified in terms of IP octets.
This change to specification in terms of L2 octets results in needing
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)
framing overhead at sender and receiver of this information.  The
TSpec should be respecified at the IP layer, with L2 framing overhead
left to the Producer and Consumer to factor into their calculations
based on each's direct knowledge of L2 functionality and configuration
in the local AS.  That ought to enable elimination of the L2_OVERHEAD
TLV, thereby reducing complexity.
##svshah, the purpose for advertising L2 overhead, from the Producer to the=
 Consumer, is to make sure traffic is well conditioned, at the egress of th=
e Consumer, to avoid possible indiscriminate drops at the ingress of the Pr=
oducer. In another words, the Producer is telling the Consumer to ignore it=
s own link level overhead, instead use Producer's provided link level overh=
ead while running frames through QoS functions (this is relevant in use-cas=
es where l2 overhead of the egress link on Consumer and of ingress link on =
the Producer are of different size, e.g., in the vpn/tunnel connection betw=
een two peer nodes which physically may be multiple hops away).
I understand your comments regarding re-using TSpec without any modificatio=
n. Do you agree with the use-case of l2 differences? If yes, any suggestion=
 how to accommodate that?

David> Specifying this in terms of IP octets implies that L2 overhead is to=
 be ignored on both links.  That's simpler, and a few sentences of discussi=
on about possible L2 framing differences should cover what needs to be done=
 (e.g., if traffic rates are configured in terms of L2 octets, then explain=
 how each entity converts between IP traffic and L2 traffic - the draft alr=
eady effectively contains that explanation).

##svshah2, just to make sure that some of the real use are not left out..

For the traffic conditioning where sla established is for the ip based rate=
s only, it suffices for the Producer to send rates only IP based ignoring a=
ny specific of l2 overheads.

Though for the cases where physical links are not to be over-run, and/or, s=
la defined are based on l2 rates, the Consumer would need to know l2 overhe=
ad from the Producer. Otherwise 10 byes of l2 overhead difference on 64 byt=
es packets can be significant compare to on 1400 bytes packets, and thus th=
e Producer does not have a way to convert rates to ip based (this can cause=
 functional issue), since this has to be per packet consideration.

Regards,
Shitanshu




[3] A token bucket should have two rate-related marking parameters
based on its token fill rate, i.e., min-rate, not the four
rate-related marking parameters in this draft.  The max-rate
parameters in sections 3.3.2.5-6 ought to be specified against a
second token bucket.  In addition, the handling precedence algorithm
in section 3.3.2.7 is an overly complex way to specify the
relationship of two token buckets.  All of this is even more
important, because max-rate, as defined in RFC 2115, is only
applicable to bursting - that max-rate for bursting often turns out to
be an interface line rate, which is not generally useful for the
traffic provisioning purposes of this draft.

##svshah, what you describe below conceptually very much makes sense and th=
at is what we attempt to achieve. What is unclear though how to capture tha=
t using TSpec definition specified in RFC2215. Since that TSpec definition =
has both minimum-rate and maximum-rate, but no in/out profile marking param=
eters.

Is your proposal below to define two TSpecs using the same definition from =
RFC2215? Wouldn't in that case we have min/max specified twice? min/max in =
each TSpec? and thus confusing to represent one min and one max through two=
 TSpecs?

David> See RFC 2698 for the desired behavior and the parameters needed to s=
pecify it.  The current idr-sla draft is not able to represent the traffic =
conditioning mechanisms specified in both RFC 2698 and RFC 2697, as each me=
chanism requires two token buckets (e.g., there are two burst sizes, but th=
e idr-sla draft TSpec only contains one).  This deficiency needs to be deal=
t with.  One possibility for simplification is to drop the max-rate from th=
e RFC 2115 TSpec and assume that the max-rate for bursting is the effective=
 line rate.

The following should be done instead:
        - Define TSpecs for two token buckets, a primary/committed token bu=
cket
                and a secondary/peak token bucket that MUST be nested, i.e.=
, traffic
                that is in-profile for the secondary/peak token bucket is a=
lways
                in-profile for the primary/committed token bucket.  Some of=
 the details
                of how to specify this are subtle, see RFC 2698 for a worke=
d example.
                Use of a secondary/peak token bucket requires use of the pr=
imary/
                committed token bucket, but a primary/committed token bucke=
t can be used
                without a secondary/peak token bucket.
        - For a single token bucket, define two handling TLVs, Committed (i=
n profile) and
                Excess (out of profile).
        - For two token buckets, define three handling TLVs, Committed (in =
profile for both
                token buckets), Peak (out of profile for primary/committed =
token bucket, but in
                profile for secondary/peak token bucket) and Excess (out of=
 profile for both
                token buckets).
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess
terms.

[4] The drop threshold TLV in section 3.3.2.8 is not specified
sufficiently to be implemented interoperably.  For example, I don't
understand what an implementation is supposed to do when it receives 3
drop thresholds.
##svshah, It is around the semantics of a single queue with a different thr=
eshold for a set of code-points, where packet for a specific code-point is =
to be tail dropped if overall queue-depth hits code-point specific threshol=
d at the arrival of that packet.
We will add appropriate clarification for this semantics.

David> Will look at revision

[5] The relative priority TLV in section 3.3.2.9 has the same
insufficient specification problem as the drop threshold TLV,
compounded by a functional incompleteness problem - if the recipient
is using a weighted packet transmission scheduler (e.g., WRR),
priorities cannot be used to configure that scheduler.  Hence, some
specification of weights and scheduling algorithms that use weights
needs to be added.
##svshah, Sure. Is following clarification okay? (some of the wordings take=
n from RFC2598)

"
A higher priority class of traffic to be served without pre-empted by lower=
 priority class of traffic for more than a packet time at the configured ra=
te.

In the system that implements WRR, the use of relative priority may get res=
tricted where a single queue may be used for a higher priority traffic clas=
s where that queue  is configured for the full share of the output bandwidt=
h.
"

David> Last sentence basically says that WRR weights are out-of-scope.  Tha=
t seems wrong.  Will look at revision.

[6] I have no idea what the sub-traffic classes TLV in section
3.3.2.10 is supposed to do, as that TLV is specified based on "Traffic
Class TLVs" which is an undefined term in this draft (e.g., that term
is not used outside of section 3.3.2.10.
##svshah, They are to facilitate hierarchy. A specific Traffic Class, can f=
urther be divided in a multiple  subset of Traffic Classes, with their own =
Traffic Class Elements and Traffic Class Services.

Will correct the wording to remove your this specific concern.

David> Will look at revision

[7] This draft's QoS contents need to be functionally aligned with
work-in-progress on YANG QoS models, in order to provide some
assurance that that this draft is implementable for actual network
switch/router data paths.  The current acknowledgement of the
existence of YANG, NETCONF and RESTConf at the end of Section 1 does
not suffice.
##svshah, While eventually "Traffic Conditioning Agreement" should be trans=
lated to the actual forwarding qos policy on any vendor specific device, TC=
A exchange largely carries concepts/semantics that is either standard based=
 or well understood.

While we are not aware of any working group document of QoS Yang Model, we =
think that  concepts of Traffic Conditioning should be easily adaptable to =
any QoS Yang Models since they also have to be defined to support those con=
cepts.


David> Still want to see cross-check with implementations here.


[8] There are significant complexity and correctness problems caused
by the option to not specify the Source AS - e.g., Section 3.2 defines
an SLA ID as an "identifier which is unique in the scope of Source AS"
which is meaningless if there is no Source AS.  It would be simpler to
always specify Source AS, even in the point-to-point case.

##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in cases.=
 Given specification of Source AS always is more clearer in multiple feed-b=
ack we have gotten so far, we can modify the specification to incorporate t=
hat over the simplicity of implementation for certain cases.

David> OK, thanks.

[9] In section 3.2, the "intended for the peer receiver of the BGP
UPDATE message" text in the specification of bit 0 of the SLA Subtype
flags is unclear.  I suspect that this is intended to differentiate
the two usages described in sections 4.1.1 (Point-to-Point) and 4.1.2
(Multiple Hops), in which case the parenthesized terms (or similar
terminology) should be used with cross-references to those two
sections.
##svshah, sure will make necessary changes, also in the context of earlier =
comment.


[10] There needs to be a coherent discussion in one place about how
SLA advertisement, update and withdrawal work.  A single ADVERTISE
method may suffice on the wire, but the details on how initial
advertisement, subsequent advertisement (update) and withdrawal work
need to be specified in one place.  The third paragraph of Section 4
is a start on this material, but it's too terse;

[Med] That text is terse because we are reusing the BGP machinery for adver=
tising/withdrawing; we only augment it with triggers that are linked to the=
 SLA information. A new SLA will lead to an update message with ADVERTISE, =
an update of an existing SLA will trigger an update message. We do think th=
is information is already present in the document.

David>This is hard to understand it, as there is no statement that the BGP =
machinery is being used, and the material on SLA usage is spread in differe=
nt places.  I suggest starting section 3 with a discussion of advertisement=
/update/withdrawal, and how all three are realized via a single ADVERTISE m=
ethod via BGP UPDATE - this was difficult to figure out in reading the curr=
ent draft.

it should be expanded
into its own subsection, and moved earlier to come before the
ADVERTISE method in Section 3.2.  This text from Section 3.2 should be
moved into that new subsection and likewise expanded:

[Med] Another option is to move it Section 4. From our standpoint, we do th=
ink it is straightforward to describe the behavior once the attributes form=
at are defined.

David> Ok, that's an editorial choice - I prefer to explain how something w=
orks before defining its on-the-wire data format.

      If an advertised SLA ID is different from earlier advertised one,
      for the same prefix and from the same Source AS, indicates Source
      AS is advertising new SLA Content to replace the previous one
      advertised with the same SLA ID.

In addition, I wonder whether functionality should be added to allow
withdrawal of an advertisement by specifying its SLA ID, although that
was not part of the original design.


[Med] The reason we didn't adopted that design is that we don't want to mak=
e assumptions on which data the remote peer will be used for enforcing loca=
l actions and also because of this text:

      The SLA ID applies to aggregate traffic to prefixes for a given

      AFI/SAFI that share the same Source AS and SLA ID.

David> That's fine, I wanted to ensure that this had been considered.  The =
discussion of BGP mechanism reuse will probably help here.

[11] Notions of context for interpretation of all the IPFIX parameters
in 3.3.1 need to be added, e.g.:
        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.
        - The IP address parameters are rather likely to be VPN-specific wh=
en there's more
                than one BGP/MPLS VPN that spans or transits the ASs involv=
ed.
        - The transport port parameters need specification of which transpo=
rt header and where it
                is located (e.g., for TCP traffic carried by in VXLAN, is t=
his the inner TCP header
                or the outer UDP header in VXLAN).
There are probably simple approaches to specifying context in all
cases, but that context does need to be specified ... in all cases.

[Med] We dind't include a context field because we thought that the definit=
ion of the IPFIX attributes is sufficient by itself, but if you do think it=
 is helpful to have such information, we can update the table.
David>  Really???  Please reread the first comment above:

        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.

David>  Taking just DSCP, it can change on a per-link basis, so something h=
as to specify which link (between the SLA Producer and SLA Consumer?) is in=
volved.  It probably suffices to say that it's the link that crosses the re=
levant AS boundary, but that does have to be stated, as it's nowhere to be =
found in the far more general IPFIX registry.

[12] The security considerations (section 10) are severely incomplete
and insufficient:

David> I stand by this statement and recommend a complete rewrite of the se=
curity considerations.

        - Discussion of possible abuse of this BGP option for denial-of-ser=
vice and theft-of-service,
                needs to be added, including possible countermeasures and m=
itigations.

[Med] This attack vector is not specific to this attribute; this is valid f=
or BGP in general.

David> There are additional attacks enabled by this attribute.

        - This sentence at the end of the second paragraph in Section 10 is=
 content-free:

                   It is NOT RECOMMENDED to enable this attribute at the
                   scale of the Internet unless if means to prevent leaking=
 sensitive
                   information are enforced.

                What exactly is an implementer or admin supposed to do?

[Med] An example of what an admin needs to check if this information can be=
 sent to a given peer or not. Some of the content of the attribute contains=
 some sensitive information such as contract Id, classes, etc.

How does one
                figure out whether an implementation or deployment is  "at =
the scale
                of the Internet" ??

[Med] The idea here is to avoid leaking such data in to the global routing =
table. Only entitled peers need receive such information with controlled sc=
ope.

David> I understand the idea - the problem is that I don't see specificatio=
n of what has to be implemented in either the text in the draft or the abov=
e explanations.
        - The next to last paragraph in section 10 is almost content-free, =
as it leaves
                decisions on implementation and deployment of key security =
functionality as
                "an exercise for the reader" - that's not acceptable.

[Med] I guess you are referring to the following text. Validation checks ar=
e really deployment-specific. The text calls out the issue and recommends a=
n action; how to translate this action into detailed actions is realty loca=
l to a domain

   The attribute may be advertised by a misbehaving node to communicate

   SLA parameters that are not aligned with the SLA agreements.  Though

   the enforcement of SLA parameters is outside the scope of this

   document, it is RECOMMENDED that the SLA Consumer to enforce a set of

   validation checks before translating the SLA parameters conveyed in

   the QoS attributes into provisioning actions.  Such validations MAY

   rely on SLA parameters like the origin AS or SLA ID, like generating

   SLA ID using pseudo-random schemes [RFC4086<https://tools.ietf.org/html/=
rfc4086>].

David> I stand by the "exercise to the reader"  criticism - one way to be h=
onest about this would be to change the paragraph to:



        The attribute may be advertised by a misbehaving node to communicat=
e

   SLA parameters that are not aligned with the SLA agreements.  The

   enforcement of SLA parameters is outside the scope of this document.



David> That does not change any normative content of the original paragraph=
.  My view is that the "outside the scope of this document" statement is wr=
ong because all of these parameters are being defined in this draft.

        - Last, but not least, the final paragraph in Section 10 is a joke =
that will
                be lost on a security directorate reviewer - to understand =
why, see
                Section 2 of RFC 6919, and take note of the publication dat=
e of RFC 6919.

David> For anyone who didn't catch the reference, RFC 6919 is an April 1 RF=
C ... and the "SHOULD BE considered" language used in the last security con=
siderations paragraph of this draft is accurately characterized as vague in=
 Section 2 of RFC 6919:
   The phrase "SHOULD CONSIDER" indicates that the authors of the
   specification think that implementations should do something, but
   they're not sure quite what.
------------------------

Having noted a dozen major issues, I'll end the review here for now,
as I believe a serious revision of the draft is called for, which
would be a better starting point to review for minor issues and
editorial items.

--------------------------------------------------------
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com<mailto:David.Black@dell.com>  <=3D=3D=3D NEW =3D=3D=3D
--------------------------------------------------------

--_000_CE03DB3D7B45C245BCA0D243277949362F8DD70AMX307CL04corpem_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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
	{mso-style-priority:99;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.xmsonormal, li.xmsonormal, div.xmsonormal
	{mso-style-name:xmsonormal;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Embedded in my question a=
bout VPNs is an implicit suggestion (which I&#8217;ll now make explicit ...=
) -- this L2 overhead parameter would be more robust if it were
 defined as the number of octets difference between the full frame that is =
sent on the wire and the size of the IP packet to which &nbsp;the token buc=
kets apply.&nbsp; Even if there are no known current needs to account for a=
nything other than L2 framing, this approach
 is robust to future network engineering encapsulation &#8220;creativity&#8=
221; ;-).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks, --David<o:p></o:p=
></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tsv-art =
[mailto:tsv-art-bounces@ietf.org]
<b>On Behalf Of </b>Shitanshu Shah<br>
<b>Sent:</b> Tuesday, February 28, 2017 1:24 PM<br>
<b>To:</b> Black, David; tsv-art@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org<br>
<b>Subject:</b> Re: [Tsv-art] Review of draft-ietf-idr-sla-exchange-10<o:p>=
</o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi&nbsp;David,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">We will add more text to clarify rationale for L2_OVERHEAD.<o:p>=
</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Do you have a preference or suggest a way to specify L2 rates? W=
e will work on defining 2 TSpecs to specify two rates (min and max).&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><br>
As far as VPN terminating between Consumer and Producer, I am not aware of =
use-cases, at least in the context of the deployment scenario considered fo=
r the draft.
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">Shitanshu<o:p></o:p></span></p>
</div>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" align=3D"center">
</span></div>
<div id=3D"divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"> Black, David &lt;<a href=3D"mailto:David.Black@dell.com">=
David.Black@dell.com</a>&gt;<br>
<b>Sent:</b> Monday, February 27, 2017 10:42 AM<br>
<b>To:</b> Shitanshu Shah; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf=
.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a>; Black, David<br>
<b>Subject:</b> RE: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Ok, please make that rationale for the =
L2_OVERHEAD parameter clear in the draft:</span><span style=3D"color:black"=
><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&gt; Though for the cases where&nbsp;phys=
ical&nbsp;links are not to be&nbsp;over-run, and/or,&nbsp;sla defined are b=
ased on
 l2 rates, the&nbsp;Consumer would<br>
&gt; need to know l2 overhead from the Producer. Otherwise 10 byes of l2 ov=
erhead difference on 64 bytes packets can be significant<br>
&gt; compare to on 1400 bytes packets, and thus the Producer does not have =
a way to convert rates to&nbsp;ip based (this can cause<br>
&gt; functional issue), since this has to be per packet consideration.</spa=
n><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">It looks like the result is that if the=
 Producer&#8217;s L2 overhead is larger than the Consumer&#8217;s, and
 the token buckets are specified in IP octets, the consumer has to calculat=
e a per-packet charge of the L2 overhead difference against the IP token bu=
cket (and in the opposite case, there may be a per-packet credit).&nbsp;&nb=
sp; Are there cases where the overhead is
 not all L2, e.g., SLA/TCA Consumer is using a VPN that terminates between =
Consumer and Producer?</span><span style=3D"color:black"><o:p></o:p></span>=
</p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Thanks, --David</span><span style=3D"co=
lor:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
> Shitanshu
 Shah [<a href=3D"mailto:shitanshu_shah@hotmail.com">mailto:shitanshu_shah@=
hotmail.com</a>]
<br>
<b>Sent:</b> Friday, February 24, 2017 1:05 PM<br>
<b>To:</b> Black, David; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.o=
rg</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi David,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">One response inline ##svshah2<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" noshade=3D"" style=3D"color:black" align=3D"ce=
nter">
</span></div>
<div id=3D"divRplyFwdMsg">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k"> Black,
 David &lt;<a href=3D"mailto:David.Black@dell.com">David.Black@dell.com</a>=
&gt;<br>
<b>Sent:</b> Friday, February 24, 2017 8:53 AM<br>
<b>To:</b> Shitanshu Shah; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf=
.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a>; Black, David<br>
<b>Subject:</b> RE: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Inline ...</span><span style=
=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Thanks, --David</span><span style=3D"co=
lor:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
> Shitanshu
 Shah [<a href=3D"mailto:shitanshu_shah@hotmail.com">mailto:shitanshu_shah@=
hotmail.com</a>]
<br>
<b>Sent:</b> Friday, February 24, 2017 4:09 AM<br>
<b>To:</b> Black, David; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.o=
rg</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi David,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Thank you for taking time for the review..<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Please find our response inline ##svshah and [Med]<o:p></o:p></s=
pan></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">Regards,
</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Shitanshu</span><span style=3D"color:black"><o:p></o:p></span></=
p>
<div>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" align=3D"center">
</span></div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k"> David
 Black &lt;<a href=3D"mailto:david.black@emc.com">david.black@emc.com</a>&g=
t;<br>
<b>Sent:</b> Tuesday, February 21, 2017 3:31 PM<br>
<b>To:</b> <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Review of draft-ietf-idr-sla-exchange-10</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Reviewer: David Black<br>
Review result: Not Ready<br>
<br>
I've reviewed this document as part of the transport area<br>
directorate's ongoing effort to review key IETF documents. These<br>
comments were written primarily for the transport area directors, but<br>
are copied to the document's authors for their information and to<br>
allow them to address any issues raised. When done at the time of IETF<br>
Last Call, the authors should consider this review together with any<br>
other last-call comments they receive. Please always CC<br>
<a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a> if you reply to or=
 forward this review.<br>
<br>
Document: draft-ietf-idr-sla-10<br>
Reviewer: David Black<br>
Review Date: February 21, 2017<br>
<br>
Review result: Not Ready<br>
<br>
This is an early TSV-ART review of a working group draft, requested by<br>
the IDR Working Group.<br>
<br>
This draft defines an extension to BGP to allow exchange of traffic<br>
handling parameters (e.g., configured rates, burst sizes, drop<br>
thresholds).&nbsp; While this is a useful area of technology to standardize=
<br>
across network operators, this draft has significant problems, and<br>
parts of it could use some serious rethought.<br>
<br>
This reviewer has discussed small portions of this draft with some of<br>
the authors in the past, but this is his first comprehensive reading<br>
and review of the draft.<br>
<br>
Major Issues:<br>
<br>
[1] The draft is misnamed.&nbsp; This is not an SLA (Service Level<br>
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -<br>
see the definition of TCA in RFC 2475.&nbsp; This draft should start from<b=
r>
that definition and generalize the applicability of TCA beyond<br>
Diffserv.&nbsp; Large areas of SLA content are not covered by this draft -<=
br>
for more details, see the Wikipedia article on SLA:<br>
<a href=3D"https://en.wikipedia.org/wiki/Service-level_agreement" id=3D"LPl=
nk481142">https://en.wikipedia.org/wiki/Service-level_agreement</a> .<br>
<br>
##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">David&gt; That would be good, thanks.</sp=
an><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
<br>
[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to<br>
specify a token bucket is a good idea, but it's not a good idea to<br>
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)<br>
octets, as the RFC 2115 TSpec is specified in terms of IP octets. <br>
This change to specification in terms of L2 octets results in needing<br>
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)<br>
framing overhead at sender and receiver of this information.&nbsp; The<br>
TSpec should be respecified at the IP layer, with L2 framing overhead<br>
left to the Producer and Consumer to factor into their calculations<br>
based on each's direct knowledge of L2 functionality and configuration<br>
in the local AS.&nbsp; That ought to enable elimination of the L2_OVERHEAD<=
br>
TLV, thereby reducing complexity.</span><span style=3D"color:black"><o:p></=
o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, the purpose for advertising L2 =
overhead, from the Producer to the Consumer,&nbsp;is to make sure
 traffic is well conditioned, at the egress of the&nbsp;Consumer, to avoid =
possible indiscriminate drops at the ingress of the Producer. In another wo=
rds, the&nbsp;Producer is telling the&nbsp;Consumer to ignore its own link =
level overhead, instead use Producer's provided
 link level overhead while running frames through QoS functions (this is&nb=
sp;relevant in use-cases where l2 overhead of the&nbsp;egress link on Consu=
mer and of ingress link on the Producer are of different size, e.g., in the=
&nbsp;vpn/tunnel connection between two peer&nbsp;nodes
 which physically may be multiple hops away).</span><span style=3D"color:bl=
ack"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">I understand your comments regarding re-u=
sing TSpec without any modification.&nbsp;Do you agree with the
 use-case of l2 differences? If yes, any suggestion how to accommodate that=
?</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Specifying this in terms of I=
P octets implies that L2 overhead is to be ignored on both links.&nbsp;
 That&#8217;s simpler, and a few sentences of discussion about possible L2 =
framing differences should cover what needs to be done (e.g., if traffic ra=
tes are configured in terms of L2 octets, then explain how each entity conv=
erts between IP traffic and L2 traffic
 - the draft already effectively contains that explanation).</span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah2, just to make sure that some of=
 the real use are not left out..</span><span style=3D"color:black"><o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">For the traffic conditioning where sla es=
tablished is for the ip based rates only, it suffices for
 the Producer to&nbsp;send rates only IP based ignoring any specific of l2 =
overheads.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Though for the cases where&nbsp;physical&=
nbsp;links are not to be&nbsp;over-run, and/or,&nbsp;sla defined are based =
on
 l2 rates, the&nbsp;Consumer would need to know l2 overhead from the Produc=
er. Otherwise 10 byes of l2 overhead difference on 64 bytes packets can be =
significant compare to on 1400 bytes packets, and thus the Producer does no=
t have a way to convert rates to&nbsp;ip based
 (this can cause functional issue), since this has to be per packet conside=
ration.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Regards,</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Shitanshu</span><span style=3D"color:blac=
k"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
[3] A token bucket should have two rate-related marking parameters<br>
based on its token fill rate, i.e., min-rate, not the four<br>
rate-related marking parameters in this draft.&nbsp; The max-rate<br>
parameters in sections 3.3.2.5-6 ought to be specified against a<br>
second token bucket.&nbsp; In addition, the handling precedence algorithm<b=
r>
in section 3.3.2.7 is an overly complex way to specify the<br>
relationship of two token buckets.&nbsp; All of this is even more<br>
important, because max-rate, as defined in RFC 2115, is only<br>
applicable to bursting - that max-rate for bursting often turns out to<br>
be an interface line rate, which is not generally useful for the<br>
traffic provisioning purposes of this draft.</span><span style=3D"color:bla=
ck"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, what you describe below concept=
ually very much makes sense and that is what we attempt to
 achieve. What is unclear though how to capture that using TSpec definition=
 specified in RFC2215. Since that TSpec definition has both minimum-rate an=
d maximum-rate, but no in/out profile marking parameters.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Is your proposal below to define two TSpe=
cs using the same&nbsp;definition from RFC2215? Wouldn't in that
 case we have min/max specified twice? min/max in each TSpec? and thus conf=
using to represent one min and one max through two TSpecs?</span><span styl=
e=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; See RFC 2698 for the desired =
behavior and the parameters needed to specify it.&nbsp; The current
 idr-sla draft is not able to represent the traffic conditioning mechanisms=
 specified in both RFC 2698 and RFC 2697, as each mechanism requires two to=
ken buckets (e.g., there are two burst sizes, but the idr-sla draft TSpec o=
nly contains one).&nbsp; This deficiency
 needs to be dealt with.&nbsp; One possibility for simplification is to dro=
p the max-rate from the RFC 2115 TSpec and assume that the max-rate for bur=
sting is the effective line rate.</span><span style=3D"color:black"><o:p></=
o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
The following should be done instead:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Define TSpecs for two token bu=
ckets, a primary/committed token</span><span style=3D"font-size:10.0pt;font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">bucket<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; and a secondary/peak token bucket that MUST be nested, i.e.=
,</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">traffic<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; that is in-profile for the secondary/peak token bucket is a=
lways<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; in-profile for the primary/committed token bucket.&nbsp; So=
me of the</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">details<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; of how to specify this are subtle, see RFC 2698 for a worke=
d</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">example.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Use of a secondary/peak token bucket requires use of the pr=
imary/<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; committed token bucket, but a primary/committed token bucke=
t can be</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">used<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; without a secondary/peak token bucket.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For a single token bucket, def=
ine two handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">profile) and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Excess (out of profile).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For two token buckets, define =
three handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">profile for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets), Peak (out of profile for primary/committed =
token</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">bucket, but in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; profile for secondary/peak token bucket) and Excess (out of=
 profile</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets).<br>
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess<br>
terms.<br>
<br>
[4] The drop threshold TLV in section 3.3.2.8 is not specified<br>
sufficiently to be implemented interoperably.&nbsp; For example, I don't<br=
>
understand what an implementation is supposed to do when it receives 3<br>
drop thresholds.</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah,&nbsp;It is around the semantics=
 of&nbsp;a single queue with a different threshold for a set of code-points=
,
 where packet for a specific code-point is to be tail dropped if overall qu=
eue-depth hits code-point specific threshold at the arrival of that packet.=
</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">We will add appropriate clarification for=
 this semantics.</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; Will look at revision
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
[5] The relative priority TLV in section 3.3.2.9 has the same<br>
insufficient specification problem as the drop threshold TLV,<br>
compounded by a functional incompleteness problem - if the recipient<br>
is using a weighted packet transmission scheduler (e.g., WRR),<br>
priorities cannot be used to configure that scheduler.&nbsp; Hence, some<br=
>
specification of weights and scheduling algorithms that use weights<br>
needs to be added.</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, Sure. Is following clarificatio=
n okay? (some of the wordings taken from RFC2598)</span><span style=3D"colo=
r:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&quot;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">A higher priority class of traffic&nbsp;t=
o be served without pre-empted by lower priority&nbsp;class of traffic&nbsp=
;for
 more than a packet time at the configured rate.</span><span style=3D"color=
:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">In the system that implements WRR, the us=
e of relative priority may get restricted where a single queue
 may be used for a&nbsp;higher priority traffic class where that queue &nbs=
p;is configured for the full share of the output bandwidth.</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&quot;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; Last sentence basically says that W=
RR weights are out-of-scope.&nbsp; That seems wrong.&nbsp; Will look at
 revision.</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
[6] I have no idea what the sub-traffic classes TLV in section<br>
3.3.2.10 is supposed to do, as that TLV is specified based on &quot;Traffic=
<br>
Class TLVs&quot; which is an undefined term in this draft (e.g., that term<=
br>
is not used outside of section 3.3.2.10.</span><span style=3D"color:black">=
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, They are to facilitate hierarch=
y. A specific Traffic Class, can further be divided in a multiple
 &nbsp;subset of&nbsp;Traffic Classes, with their own Traffic Class Element=
s and Traffic Class Services.</span><span style=3D"color:black"><o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Will correct the wording to remove your t=
his specific concern.</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">David&gt; Will look at revision
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
[7] This draft's QoS contents need to be functionally aligned with<br>
work-in-progress on YANG QoS models, in order to provide some<br>
assurance that that this draft is implementable for actual network<br>
switch/router data paths.&nbsp; The current acknowledgement of the<br>
existence of YANG, NETCONF and RESTConf at the end of Section 1 does<br>
not suffice.</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, While&nbsp;eventually &quot;Tra=
ffic Conditioning Agreement&quot; should be translated to the actual forwar=
ding
 qos policy on any vendor specific device, TCA exchange largely carries con=
cepts/semantics that is either standard based or&nbsp;well understood.</spa=
n><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">While we are not aware of any working gro=
up document of QoS Yang Model, we think that &nbsp;concepts of
 Traffic Conditioning should be easily adaptable to any QoS Yang Models sin=
ce they also have to be defined to support those concepts.</span><span styl=
e=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Still want to see cross-check=
 with implementations here.</span><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
<br>
[8] There are significant complexity and correctness problems caused<br>
by the option to not specify the Source AS - e.g., Section 3.2 defines<br>
an SLA ID as an &quot;identifier which is unique in the scope of Source AS&=
quot;<br>
which is meaningless if there is no Source AS.&nbsp; It would be simpler to=
<br>
always specify Source AS, even in the point-to-point case.<br>
<br>
##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in&nbsp;c=
ases. Given specification of Source AS always is more clearer in multiple f=
eed-back we have gotten so far, we can
 modify the specification to incorporate that over the simplicity of implem=
entation for certain cases.</span><span style=3D"color:black"><o:p></o:p></=
span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; OK, thanks.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[9] In section 3.2, the &quot;intended for =
the peer receiver of the BGP</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">UPDATE message&quot; text in the specificat=
ion of bit 0 of the SLA Subtype</span><span style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">flags is unclear.&nbsp; I suspect that this=
 is intended to differentiate</span><span style=3D"font-family:&quot;Calibr=
i&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">the two usages described in sections 4.1.1 =
(Point-to-Point) and 4.1.2</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">(Multiple Hops), in which case the parenthe=
sized terms (or similar</span><span style=3D"font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">terminology) should be used with cross-refe=
rences to those two</span><span style=3D"font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">sections.</span><span style=3D"color:black"=
><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, sure will make necessary change=
s, also in the context of earlier comment.</span><span style=3D"color:black=
"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[10] There needs to be a coherent discussio=
n in one place about how</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">SLA advertisement, update and withdrawal wo=
rk.&nbsp; A single ADVERTISE</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">method may suffice on the wire, but the det=
ails on how initial</span><span style=3D"font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">advertisement, subsequent advertisement (up=
date) and withdrawal work</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">need to be specified in one place.&nbsp; Th=
e third paragraph of Section 4</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">is a start on this material, but it's too t=
erse;&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">[Med] That text is terse because we are reusing the BGP mach=
inery for advertising/withdrawing; we only augment
 it with triggers that are linked to the SLA information. A new SLA will le=
ad to an update message with ADVERTISE, an update of an existing SLA will t=
rigger an update message. We do think this information is already present i=
n the document.
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt;This is hard to understand it,=
 as there is no statement that the BGP machinery is being used,
 and the material on SLA usage is spread in different places.&nbsp; I sugge=
st starting section 3 with a discussion of advertisement/update/withdrawal,=
 and how all three are realized via a single ADVERTISE method via BGP UPDAT=
E - this was difficult to figure out
 in reading the current draft.</span><span style=3D"color:black"><o:p></o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">it should be expanded</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br=
>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">into its own subsection, and moved earlier =
to come before the</span><span style=3D"font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">ADVERTISE method in Section 3.2.&nbsp; This=
 text from Section 3.2 should be</span><span style=3D"font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">moved into that new subsection and likewise=
 expanded:</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] Another option is to move it Section 4. From our standpo=
int, we do think it is straightforward to describe the behavior once the at=
tributes format are defined.&nbsp;</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Ok, that&#8217;s an editorial=
 choice - I prefer to explain how something works before defining its
 on-the-wire data format.</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If an adve=
rtised SLA ID is different from earlier advertised</span><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:=
#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">one,</span><span style=3D"font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the same=
 prefix and from the same Source AS, indicates</span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F4=
97D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Source</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AS is advert=
ising new SLA Content to replace the previous one</span><span style=3D"font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; advertised w=
ith the same SLA ID.</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">In addition, I wonder whether functionality=
 should be added to allow</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">withdrawal of an advertisement by specifyin=
g its SLA ID, although that</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">was not part of the original design.</span>=
<span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt;orphans:2;widows:2"><=
span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:bl=
ack">[Med] The reason we didn&#8217;t adopted that design is that we don&#8=
217;t want to make assumptions on which data the remote peer
 will be used for enforcing local actions and also because of this text:</s=
pan><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;c=
olor:black"><o:p></o:p></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2;widows:2"><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Courier New&quot;;color:#212121">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; The SLA ID applies to aggregate traffic to prefixes for a =
given</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2;widows:2"><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Courier New&quot;;color:#212121">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; AFI/SAFI that share the same Source AS and SLA ID.</span><=
span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:=
black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; That&#8217;s fine, I wanted to ensu=
re that this had been considered.&nbsp; The discussion of BGP mechanism
 reuse will probably help here.</span><span style=3D"font-size:10.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[11] Notions of context for interpretation =
of all the IPFIX parameters</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">in 3.3.1 need to be added, e.g.:</span><spa=
n style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The first three parameters (DSCP, MPLS EXP field in top label,</span><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-seri=
f&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">802.1q priority) can</span><span style=3D"f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-li=
nk or LSP-by-LSP basis along a traffic's</span><span style=3D"font-size:10.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">network path.</span><span style=3D"font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The IP address parameters are rather likely to be VPN-specific when</span=
><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">there's more</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; than one BGP/MPLS VPN that =
spans or transits the ASs involved.</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The transport port parameters need specification of which transport</span=
><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">header and where it</span><span style=3D"fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is located (e.g., for TCP t=
raffic carried by in VXLAN, is this the</span><span style=3D"font-size:10.0=
pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">inner TCP header</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or the outer UDP header in =
VXLAN).</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">There are probably simple approaches to spe=
cifying context in all</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">cases, but that context does need to be spe=
cified ... in all cases.</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] We dind&#8217;t include a context field because we thoug=
ht that the definition of the IPFIX attributes is sufficient by itself, but=
 if you do think it is helpful to have such information,
 we can update the table.</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt;&nbsp; Really???&nbsp; Please =
reread the first comment above:</span><span style=3D"color:black"><o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - The first three parameters (DSCP, MPLS EXP field in top label, 802.1q p=
riority) can</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-li=
nk or LSP-by-LSP basis along a traffic's network path.</span><span style=3D=
"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt;&nbsp; Taking just DSCP, it ca=
n change on a per-link basis, so something has to specify which link
 (between the SLA Producer and SLA Consumer?) is involved.&nbsp; It probabl=
y suffices to say that it&#8217;s the link that crosses the relevant AS bou=
ndary, but that does have to be stated, as it&#8217;s nowhere to be found i=
n the far more general IPFIX registry.</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[12] The security considerations (section 1=
0) are severely incomplete</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">and insufficient:</span><span style=3D"colo=
r:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; I stand by this statement and=
 recommend a complete rewrite of the security considerations.</span><span s=
tyle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Discussion of possible abuse of this BGP option for</span><span style=3D"=
font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">denial-of-service and theft-of-service,</sp=
an><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to be added, includin=
g possible countermeasures and</span><span style=3D"font-size:10.0pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">mitigations.</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] This attack vector is not specific to this attribute; th=
is is valid for BGP in general.</span><span style=3D"color:black"><o:p></o:=
p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; There are additional attacks =
enabled by this attribute.</span><span style=3D"color:black"><o:p></o:p></s=
pan></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- This sentence at the end of the second paragraph in Section 10 is</span><=
span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">content-free:</span><span style=3D"font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is NOT=
 RECOMMENDED to enable this attribute at the</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scale of =
the Internet unless if means to prevent leaking</span><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F=
497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">sensitive</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; informati=
on are enforced.</span><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What exactly is an implemen=
ter or admin supposed to do?&nbsp;</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">[Med] An example of what an admin needs to check if this inf=
ormation can be sent to a given peer or not. Some
 of the content of the attribute contains some sensitive information such a=
s contract Id, classes, etc.</span><span style=3D"color:black"><o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:5.25pt;text-indent:30.75pt">
<span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:black">How does</span><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">one</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; figure out whether an imple=
mentation or deployment is&nbsp; &quot;at the</span><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F49=
7D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">scale</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the Internet&quot; ??</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">[Med] The idea here is to avoid leaking such data in to the =
global routing table. Only entitled peers need receive
 such information with controlled scope.</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; I understand the idea - the problem=
 is that I don&#8217;t see specification of what has to be implemented
 in either the text in the draft or the above explanations.</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Th=
e next to last paragraph in section 10 is almost content-free, as</span><sp=
an style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">it leaves</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decisions on implementation=
 and deployment of key security</span><span style=3D"font-size:10.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">functionality as</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;an exercise for the r=
eader&quot; - that's not acceptable.</span><span style=3D"color:black"><o:p=
></o:p></span></p>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-=
size:10.0pt;font-family:&quot;Courier New&quot;;color:black">[Med] I guess =
you are referring to the following text. Validation checks are really deplo=
yment-specific. The text calls out the issue and
 recommends an action; how to translate this action into detailed actions i=
s realty local to a domain</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; The attribute may be advertised by a misbehaving node to communicate</spa=
n><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; SLA parameters that are not aligned with the SLA agreements.&nbsp; Though=
</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; the enforcement of SLA parameters is outside the scope of this</span><spa=
n style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; document, it is RECOMMENDED that the SLA Consumer to enforce a set of</sp=
an><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; validation checks before translating the SLA parameters conveyed in</span=
><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; the QoS attributes into provisioning actions.&nbsp; Such validations MAY<=
/span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; rely on SLA parameters like the origin AS or SLA ID, like generating</spa=
n><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; SLA ID using pseudo-random schemes [<a href=3D"https://tools.ietf.org/htm=
l/rfc4086" target=3D"_blank" title=3D"&quot;Randomness Requirements for Sec=
urity&quot;">RFC4086</a>].</span><span style=3D"color:black"><o:p></o:p></s=
pan></pre>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; I stand by the &#8220;exercis=
e to the reader&#8221; &nbsp;criticism - one way to be honest about this wo=
uld
 be to change the paragraph to:</span><span style=3D"color:black"><o:p></o:=
p></span></p>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o=
:p></o:p></span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span><span style=3D"color:#212121">The attribute may be advertised by a m=
isbehaving node to communicate</span><span style=3D"color:black"><o:p></o:p=
></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; SLA parameters that are not aligned with the SLA agreements.&nbsp; The</s=
pan><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span style=3D"color:#212121">&nbsp;&nbsp; enforcement of SLA paramete=
rs is outside the scope of this document.</span><span style=3D"color:black"=
><o:p></o:p></span></pre>
<pre><span style=3D"color:#212121">&nbsp;</span><span style=3D"color:black"=
><o:p></o:p></span></pre>
<pre><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;=
color:#1F497D">David&gt; That does not change any normative content of the =
original paragraph.&nbsp; My view is that the &#8220;outside the scope of t=
his document&#8221; statement is wrong because all of these parameters are =
being defined in this draft.</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Last, but not least, the final paragraph in Section 10 is a joke</span><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">that will</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be lost on a security direc=
torate reviewer - to understand why, see</span><span style=3D"font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 2 of RFC 6919, and =
take note of the publication date of RFC</span><span style=3D"font-size:10.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">6919.</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D"><br>
David&gt; For anyone who didn&#8217;t catch the reference, RFC 6919 is an A=
pril 1 RFC ... and the &#8220;SHOULD BE considered&#8221; language used in =
the last security considerations paragraph of this draft is accurately char=
acterized as vague in Section 2 of RFC 6919:</span><span style=3D"color:bla=
ck"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;text-autospace:none">
<span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot;;color:b=
lack">&nbsp;&nbsp; The phrase &quot;SHOULD CONSIDER&quot; indicates that th=
e authors of the</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;text-autospace:none">
<span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot;;color:b=
lack">&nbsp;&nbsp; specification think that implementations should do somet=
hing, but</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot;;colo=
r:black">&nbsp;&nbsp; they're not sure quite what.</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black">------------------------</span><span style=3D"f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Having noted a dozen major issues, I'll end=
 the review here for now,</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">as I believe a serious revision of the draf=
t is called for, which</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">would be a better starting point to review =
for minor issues and</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">editorial items.</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">-------------------------------------------=
-------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">David L. Black, Distinguished Engineer</spa=
n><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Dell EMC, 176 South St., Hopkinton, MA&nbsp=
; 01748</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&#43;1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbs=
p; Cell: &#43;1 (978) 394-7754</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black"><a href=3D"mailto:David.Black@dell.com">Dav=
id.Black@dell.com</a>&nbsp; &lt;=3D=3D=3D NEW =3D=3D=3D</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br=
>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">-------------------------------------------=
-------------</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_CE03DB3D7B45C245BCA0D243277949362F8DD70AMX307CL04corpem_--


From nobody Fri Mar  3 16:57:09 2017
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 54FA21294AB; Fri,  3 Mar 2017 16:57:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lbc3fTUuMbS5; Fri,  3 Mar 2017 16:57:07 -0800 (PST)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B03212940B; Fri,  3 Mar 2017 16:57:07 -0800 (PST)
Received: by mail-oi0-x235.google.com with SMTP id 126so12371790oig.3; Fri, 03 Mar 2017 16:57:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=9bIhzpk8dJUmgMLHGCzfQgvrWR2vTtPDX2zSSvOoifs=; b=M+VDp+HwQlWMO2+H6CtBWOhKwVauz28fq9fPMO7v6bRyaMRgfWZGYrvEcdlB5raYk1 9/bBnMfw8UGaxjjRXAIaD0Btda2ibfXg1l7F4jipErm59r/PP3WoG5stteSNMrbZ/HgV UdCxeuAlaN8W9Ejtd76xcZ5nmq97vtHNRZTHCXYDb4DxQ/qlDw6cBZYGWisqaapv8bg+ Rd459pPdSOsDRNCA02zaG84vAWkn4DN19+vHv+6dKjQI40pCMaFfPkhM/T1ovoBLDyrC 4aSWlLj1Aqv38uRspEOy2h7jX9hEwTX3EEZuwa2XiHIXUpf/L0T94ces1xKatlhkR5Z/ yyww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=9bIhzpk8dJUmgMLHGCzfQgvrWR2vTtPDX2zSSvOoifs=; b=lZDNvCwP8Vf+1+S5qqRZzSg3dGfr67diPYdJyFmApleq9KBYWi1n4C1PyocRkwTnYm HFY45V7WeI+/KpQlJWlqgkDUBkCoHRvlMo/tvRVPligABhc9inNdksuKzio+W2F5Y1vv ZBQYXvkv6M/6Ogrq7AuyebzL4otsrvQoElAlDlYahQAQrWVpqgLdRQWpKZHjbWL+YKad QT6C+kBEn8eb037m7KVVpzIAaWN8+8JGadYoyd6NPanRqe7KlwnNClEGmLTYgyY/aRnQ Zp8RxX2tiGN0W1ohJRfTJZ2wrUYs+U/nsKpKvK3oZgOyo3YQdrQMl01LVMqHQ5l+CQ9J /CGw==
X-Gm-Message-State: AMke39lnPFOhcUPQc54fX6WNcasOF3g6OIWM8ddDPY/+3v3NaKFYxQPhLM3GjZqeDkUohQ6Or22y3kclAccRTA==
X-Received: by 10.202.236.140 with SMTP id k134mr2726190oih.123.1488589026390;  Fri, 03 Mar 2017 16:57:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.21.21 with HTTP; Fri, 3 Mar 2017 16:57:06 -0800 (PST)
In-Reply-To: <148858887501.15874.15239074428793785070.idtracker@ietfa.amsl.com>
References: <148858887501.15874.15239074428793785070.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 3 Mar 2017 16:57:06 -0800
Message-ID: <CA+RyBmU0W8m73FDdLDcVYjuXGQipi2nG2ROsQ+5vLdCcUGWFbQ@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-ietf-ippm-twamp-time-format-04.txt
To: Joel Halpern <jmh@joelhalpern.com>, "ippm@ietf.org" <ippm@ietf.org>,  "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1134fc3e227b7c0549dd24f8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w9WOuHTKCKZrvXPcVonMoeJE3qk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Mar 2017 00:57:08 -0000

--001a1134fc3e227b7c0549dd24f8
Content-Type: text/plain; charset=UTF-8

Dear All,
changes are to address comments by Joel Halpern.

Regards,
Greg
---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Fri, Mar 3, 2017 at 4:54 PM
Subject: New Version Notification for
draft-ietf-ippm-twamp-time-format-04.txt
To: Gregory Mirsky <gregimirsky@gmail.com>, ippm-chairs@ietf.org, Israel
Meilik <israel@broadcom.com>



A new version of I-D, draft-ietf-ippm-twamp-time-format-04.txt
has been successfully submitted by Greg Mirsky and posted to the
IETF repository.

Name:           draft-ietf-ippm-twamp-time-format
Revision:       04
Title:          Support of IEEE-1588 time stamp format in Two-Way Active
Measurement Protocol (TWAMP)
Document date:  2017-03-03
Group:          ippm
Pages:          8
URL:            https://www.ietf.org/internet-drafts/draft-ietf-ippm-twamp-
time-format-04.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-ippm-twamp-
time-format/
Htmlized:       https://tools.ietf.org/html/draft-ietf-ippm-twamp-time-
format-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-ippm-twamp-
time-format-04

Abstract:
   This document describes an OPTIONAL feature for active performance
   measurement protocols allowing use of the Precision Time Protocol
   time stamp format defined in IEEE-1588v2-2008, as an alternative to
   the Network Time Protocol that is currently used.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--001a1134fc3e227b7c0549dd24f8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear All,<div>changes are to address comments by Joel Halp=
ern.</div><div><br></div><div>Regards,</div><div>Greg<br><div class=3D"gmai=
l_quote">---------- Forwarded message ----------<br>From: <b class=3D"gmail=
_sendername"></b> <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@i=
etf.org">internet-drafts@ietf.org</a>&gt;</span><br>Date: Fri, Mar 3, 2017 =
at 4:54 PM<br>Subject: New Version Notification for draft-ietf-ippm-twamp-t=
ime-format-04.txt<br>To: Gregory Mirsky &lt;<a href=3D"mailto:gregimirsky@g=
mail.com">gregimirsky@gmail.com</a>&gt;, <a href=3D"mailto:ippm-chairs@ietf=
.org">ippm-chairs@ietf.org</a>, Israel Meilik &lt;<a href=3D"mailto:israel@=
broadcom.com">israel@broadcom.com</a>&gt;<br><br><br><br>
A new version of I-D, draft-ietf-ippm-twamp-time-<wbr>format-04.txt<br>
has been successfully submitted by Greg Mirsky and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ietf-ippm-twamp-time-<w=
br>format<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A004<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Support of IEEE-1588 time stamp fo=
rmat in Two-Way Active Measurement Protocol (TWAMP)<br>
Document date:=C2=A0 2017-03-03<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ippm<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-ietf-ippm-twamp-time-format-04.txt" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/internet-<wbr>drafts/draft-ietf=
-ippm-twamp-<wbr>time-format-04.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-ietf-ippm-twamp-time-format/" rel=3D"noreferrer" target=3D"=
_blank">https://datatracker.ietf.org/<wbr>doc/draft-ietf-ippm-twamp-<wbr>ti=
me-format/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-ietf-ippm-twamp-time-format-04" rel=3D"noreferrer" target=3D"_blank">=
https://tools.ietf.org/html/<wbr>draft-ietf-ippm-twamp-time-<wbr>format-04<=
/a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.o=
rg/rfcdiff?url2=3Ddraft-ietf-ippm-twamp-time-format-04" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/rfcdiff?<wbr>url2=3Ddraft-ietf-ippm-=
twamp-<wbr>time-format-04</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes an OPTIONAL feature for active perform=
ance<br>
=C2=A0 =C2=A0measurement protocols allowing use of the Precision Time Proto=
col<br>
=C2=A0 =C2=A0time stamp format defined in IEEE-1588v2-2008, as an alternati=
ve to<br>
=C2=A0 =C2=A0the Network Time Protocol that is currently used.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br></div></div>

--001a1134fc3e227b7c0549dd24f8--


From nobody Sat Mar  4 09:14:52 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C51A1294E8; Sat,  4 Mar 2017 09:14:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Susan Hares <shares@ndzh.com>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-6man-rfc1981bis-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148864769030.23464.9110014115039938058.idtracker@ietfa.amsl.com>
Date: Sat, 04 Mar 2017 09:14:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yPgMa-zyFJdPNIgILGZT9YR5YXc>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Mar 2017 17:14:50 -0000

Reviewer: Susan Hares
Review result: Has Issues

ack, Steve,Jeffrey, and Bob: 

Thank you for taking on this important revision to the document.  I
hope my comments help to improve the document so this important change
can ge deployed. 

I have reviewed this as part of the routing directorate review.  This
review should be treated as any IETF LC comments.  

Sue Hares 

RTG-DIR Review 

Status: I have three concern plus editorial nits. 

#1 - Concern 1 is technical regarding the interaction with the MTU
option in ND/SEND plus 
 ditorial nits.  See the comments below.  I am not an ND/SEND Expert,
please have an imoplementer look at the requirements. 

Concern: I cannot tell how this interacts with the ND/SEND protocol in
the following areas below. 
 1) Neighbor Unreachability Detection is used for all paths between
hosts
   and neighboring nodes, including host-to-host, host-to-router, and
   router-to-host communication.
   
   If the source node is on the link and the destination node
available
   through the router, and the router is in the process of sending a 
   MTU option to increase the size?  How does your algorithm work? 
   
   Are the packetization layer notified? 
   Is the original value a stale notification over time?  
   You indicate it MUST NOT be done in less than 5 minutes, and that 
   10 minutes is the norm. 
   
   Is 10 minutes really the best response time for this particular
case?    
   Or did I miss something in your draft? 
     
   
2) Assume the same situation as #1, but the 
   router sends an MTU option to decrease the size. 
   
   In this case, the router is sending information that 
   the MTU has changed, but the first indication for the 
   end system is based on a Packet-too-Big Message after sending. 
   

3) For a multicast packet (3000 bytes), assume that 
the multicast path reaches two different routers (router-a 
and router-b).  Assume the on-link MTU is 3500 bytes, but the 
previous router-A and router-B MTU is 2500 bytes.  

Router-a responds to the packet with 10ms sending a 
MTU option that changes the MTU to support this packet. Router-B sends
a redirect 
for multicast address to Router-A after 30 ms.  

What happens to your path calculation?  
Is this again, the 5 minutes (minimum) and 10 minute normal to 
reset this value. 

4) What happens if the ND process is instantiated by
SEND protocol, and the host does not contain the appropriate 
certification information to timely updates? 

Again, the host guessing at the appropriate value? 


#2 - Concern 2 - How does SEND's implementation of MTU option. 
mitigate or have no effect on this MTU.  Is there a recommendation 
that should be made in section 6.  Again, please ask a SEND expert 
for review. 

#3 - Concern 3 - content of document 
 
This document has two parts: protocol requirements and implementation
requirements. 
8 paragraphs (1 page) indicates the IPv6 specification and 6 pages
gives the implementation? 

Why did this get split in to 2 documents?  Even if this was a bis,
document would it not 
be better to provide minimal specification for the protocol change and
a larger document 
with implementation information. 

I'm fine with the WG/ADs deciding, this is the way the document has to
go forward -- but the question should be asked. 

Editorial nits:  
#1 nit - section 5.2 page 8, paragraph beginning 

Old /Note: if the /
New/Note: If the/ 

#2 nit - section 5.2 page 9 paragraph begin 

Old /Note: even if/ 
New /Note: Even if/ 

#3 nit - section 5.3 page 10 paragraph beginning 

Old /Note: an implementation/
New/Note: An implementation/
   


From nobody Sun Mar  5 04:51:30 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9070F1294BF for <ietf@ietfa.amsl.com>; Sun,  5 Mar 2017 04:51:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8oClscHWeQSf for <ietf@ietfa.amsl.com>; Sun,  5 Mar 2017 04:51:28 -0800 (PST)
Received: from nm17.bullet.mail.gq1.yahoo.com (nm17.bullet.mail.gq1.yahoo.com [98.137.176.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB0D512946A for <ietf@ietf.org>; Sun,  5 Mar 2017 04:51:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1488718288; bh=rNqF1iDp9M3syF0gP/QWCbqw/Qnn2gsnIF0KsCA/GsM=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=K6lvzSgkbxwaOrG3yA1KOG9JsLOIhcvlFuFcSnKQuMdRsHKCOwpSn9ecqCwNDi7fG4ck7AHYWkegHIJscykWYKJ9aBP5vvZKUTXPKfYDIR68WG0uw68nr37A9A2WbTUe+UEkuFJfPSmVMD0AU8eHPhlIAcyOnv5YdCNYLZ1+O8JoInJqnZ8xA3veCNd2fAmoixdVI2qzmBm69vw18RAHXFKPb7peZcjcQ4MDHLYAN3RmOIknMNnmGeAg2bhHdgnTzp3MqAlowCLH0Uo9w9aidBZKaZ3qPkg5BJv9MAC87XCdLBvNbPRlVUHJJMRAzk7/rwwJirBi+4Z1ctxyF06LRg==
Received: from [98.137.12.57] by nm17.bullet.mail.gq1.yahoo.com with NNFMP; 05 Mar 2017 12:51:28 -0000
Received: from [98.137.12.235] by tm2.bullet.mail.gq1.yahoo.com with NNFMP; 05 Mar 2017 12:51:28 -0000
Received: from [127.0.0.1] by omp1043.mail.gq1.yahoo.com with NNFMP; 05 Mar 2017 12:51:28 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 324168.46437.bm@omp1043.mail.gq1.yahoo.com
X-YMail-OSG: FOs6nqkVM1mYFQ65W9oihKIGkt4ludMLSW.lt7MBmkdv5twKpGnOHmuCybHCSYZ 9jNk2ggr42LRbyEc8wbQeONKW4pfO2M4TZAL_RnoKKp8m.8Td1xwNJ3fq.q7tQ4zhKy.Pd7ry3Iu 4EpDuYNljop7nIdfrASRWMw.MqmLS7X8DXDLM0BKSNLhuZ.8yLjFmt8cTLViblSrCeKL1VqD.DrU X4l.P.xqs42vFngqXV3daGtGfwXX0xaLtQ1z6Rl2RcKCCj0nYQZvKi1j0Z0r8Km6l6wGxJLqdGau TX3JbTcDG8D46UOPpGeMNiCOQFY.yFcwuwWAlWU0rWK7plcWxDa5VKeGurYDd2mvk4nokZ3QHz7P _6f3vnq35UuoKVWE.taXtyqN0fS5hooInp07FSVvaKrFUB7GnSw_HTFAWBB_DGHT1Q0lfcsVhZ_D QG9Zx_6wUOi70xmd7i1NMhRlOOjfqoobA8.l7ARSDq5ZWqUbjWKowhzUNN30TPLm1T_7oXo9eBNo 2ynOcU2Fuff_8DGkLrOEvEkqmp.KWtoE3fUzVWEH_14UbbZPX1lk-
Received: from jws300064.mail.gq1.yahoo.com by sendmailws121.mail.gq1.yahoo.com; Sun, 05 Mar 2017 12:51:27 +0000; 1488718287.970
Date: Sun, 5 Mar 2017 12:51:16 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: IETF-Discussion Discussion <ietf@ietf.org>
Message-ID: <1033583681.2631578.1488718276235@mail.yahoo.com>
Subject: Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <1033583681.2631578.1488718276235.ref@mail.yahoo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pubcUbazVTSPnsLGOCiQEG9hNzo>
Cc: Amelia Yeo <yeo@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Mar 2017 12:51:29 -0000

All,

Please contact Amelia Yao (copied) if you are able to help with this.  ISOC needs two remote mentors to help with an ISOC project to build IETF capacity in Sri Lanka, Pakistan and Bangladesh.    It will run from May to December and they will need about 2 mentors per country.   So, they need 6 mentors all together.
 
The first mentor is to spend 1 hour per month talking to people who are following email lists on how to contribute to email lists, what to do, what not to do, motivate them to contribute to the list, answer their questions etc.  ISOC needs a short report what people are following, who are attending the calls, quantity of post and, quality of post.  They will provide a volunteer to help do the report.   
 
The second mentor will be to help the people that show potential to write drafts with their draft writing.   ISOC doesn't know which area they will be interested in and, will have to play it by ear when these people surface out.  So, they may be looking for more than one mentor here.  The deliverable is by November for IETF 100 Singapore.  Again, a short report has to be written out monthly about people being mentored, what area, the progress, the number of drafts and quality etc.   ISOC will provide a volunteer to help with the reporting.
 
The reason behind the monitoring is that ISOC needs to report monthly on progress and also they are offering 2 fellowships per country for IETF Singapore. 
 
The report written will feed into a bigger report on work being carried out in the country and they will be selecting the cream of the elist contributors/draft writers to attend IETF100.

Thanks,

Nalini Elkins

IETF Mentoring Program

Inside Products, Inc.www.insidethestack.com
(831) 659-8360


From nobody Mon Mar  6 01:06:04 2017
Return-Path: <sankalp@cdac.in>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E4CA12955D for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 01:06:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AQk2iUjMBaWz for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 01:06:00 -0800 (PST)
Received: from mailsender.cdac.in (mailsender.cdac.in [196.1.113.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C01FF126BF6 for <ietf@ietf.org>; Mon,  6 Mar 2017 01:05:59 -0800 (PST)
Received: from ims.pune.cdac.in (ims.pune.cdac.in [10.208.1.15]) by mailsender.cdac.in (8.14.2/8.14.2) with ESMTP id v2695swU008376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 6 Mar 2017 14:35:54 +0530
Received: from mailgw.pune.cdac.in ([10.208.1.4]) by ims.pune.cdac.in (8.14.4/8.14.4) with ESMTP id v2695MWO020785 for <ietf@ietf.org>; Mon, 6 Mar 2017 14:35:24 +0530
Received: from webmail.cdac.in (wbms.pune.cdac.in [10.208.1.9]) by mailgw.pune.cdac.in (8.14.2/8.13.8) with ESMTP id v2695JMx027935 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Mon, 6 Mar 2017 14:35:22 +0530
Date: Mon, 6 Mar 2017 14:35:15 +0530 (IST)
From: Sankalp Bagaria <sankalp@cdac.in>
To: ietf@ietf.org
Message-ID: <77303779.6635.1488791115274.JavaMail.open-xchange@webmail.cdac.in>
In-Reply-To: <mailman.33.1488744007.31098.ietf@ietf.org>
References: <mailman.33.1488744007.31098.ietf@ietf.org>
Subject: Re: Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_6634_61719040.1488791115212"
X-Priority: 3
Importance: Medium
X-Mailer: Open-Xchange Mailer v6.20.7-Rev15
X-CDAC-PUNE-MailScanner-ID: v2695MWO020785
X-CDAC-PUNE-MailScanner: Found to be clean, Found to be clean
X-CDAC-PUNE-MailScanner-MCPCheck-IMS: MCP-Clean, MCP-Checker (score=0, required 1)
X-CDAC-PUNE-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00, BAYES_40 -0.00, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -0.00, URIBL_BLOCKED 0.00), not spam, SpamAssassin (not cached, score=-5.299, required 6, autolearn=disabled, ALL_TRUSTED -1.80, BAYES_00 -3.50, HTML_MESSAGE 0.00)
X-CDAC-PUNE-MailScanner-Information: Please contact npsfhelp@cdac.in/mailadmin@cdac.in for more information
X-MailScanner-ID: v2695swU008376
X-CDAC-PUNE-MailScanner-From: sankalp@cdac.in
X-CDAC-MailScanner-Spam-Status: No
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bLfwXxU_CtG7TNNUXRssXgIwEIU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Sankalp Bagaria <sankalp@cdac.in>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 09:06:02 -0000

------=_Part_6634_61719040.1488791115212
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hello,

We are working on TLS and related fields for last one and
half year in Bangalore, India. We can benefit from a little
guidance. Can you tell us who is the mentor for India ?

Thanks and Regards,
Sankalp Bagaria.

On March 6, 2017 at 1:30 AM ietf-request@ietf.org wrote:
> Send ietf mailing list submissions to
> ietf@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.ietf.org/mailman/listinfo/ietf
> or, via email, send a message with subject or body 'help' to
> ietf-request@ietf.org
>
> You can reach the person managing the list at
> ietf-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ietf digest..."
>
>
> Today's Topics:
>
> 1. Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh
> (nalini.elkins@insidethestack.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 5 Mar 2017 12:51:16 +0000 (UTC)
> From: <nalini.elkins@insidethestack.com>
> To: IETF-Discussion Discussion <ietf@ietf.org>
> Cc: Amelia Yeo <yeo@isoc.org>
> Subject: Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh
> Message-ID: <1033583681.2631578.1488718276235@mail.yahoo.com>
> Content-Type: text/plain; charset=UTF-8
>
> All,
>
> Please contact Amelia Yao (copied) if you are able to help with this. ISOC
> needs two remote mentors to help with an ISOC project to build IETF capacity
> in Sri Lanka, Pakistan and Bangladesh. It will run from May to December and
> they will need about 2 mentors per country. So, they need 6 mentors all
> together.
>
> The first mentor is to spend 1 hour per month talking to people who are
> following email lists on how to contribute to email lists, what to do, what
> not to do, motivate them to contribute to the list, answer their questions
> etc. ISOC needs a short report what people are following, who are attending
> the calls, quantity of post and, quality of post. They will provide a
> volunteer to help do the report.
>
> The second mentor will be to help the people that show potential to write
> drafts with their draft writing. ISOC doesn't know which area they will be
> interested in and, will have to play it by ear when these people surface out.
> So, they may be looking for more than one mentor here. The deliverable is by
> November for IETF 100 Singapore. Again, a short report has to be written out
> monthly about people being mentored, what area, the progress, the number of
> drafts and quality etc. ISOC will provide a volunteer to help with the
> reporting.
>
> The reason behind the monitoring is that ISOC needs to report monthly on
> progress and also they are offering 2 fellowships per country for IETF
> Singapore.
>
> The report written will feed into a bigger report on work being carried out in
> the country and they will be selecting the cream of the elist
> contributors/draft writers to attend IETF100.
>
> Thanks,
>
> Nalini Elkins
>
> IETF Mentoring Program
>
> Inside Products, Inc.www.insidethestack.com
> (831) 659-8360
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> ietf mailing list
> ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> ------------------------------
>
> End of ietf Digest, Vol 106, Issue 14
> *************************************
-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------


------=_Part_6634_61719040.1488791115212
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
 </head><body style="">
 
 
  <div>
   Hello,
  </div> 
  <div>
   &#160;
  </div> 
  <div>
   We are working on TLS and related fields for last one and
  </div> 
  <div>
   half year in Bangalore, India. We can benefit from a little
  </div> 
  <div>
   guidance. Can you tell us who is the mentor for India ?
  </div> 
  <div>
   &#160;
  </div> 
  <div>
   Thanks and Regards,
  </div> 
  <div>
   Sankalp Bagaria.
  </div> 
  <div>
   <br/>On March 6, 2017 at 1:30 AM ietf-request@ietf.org wrote:
   <br/>&#62; Send ietf mailing list submissions to
   <br/>&#62; ietf@ietf.org
   <br/>&#62; 
   <br/>&#62; To subscribe or unsubscribe via the World Wide Web, visit
   <br/>&#62; https://www.ietf.org/mailman/listinfo/ietf
   <br/>&#62; or, via email, send a message with subject or body &#39;help&#39; to
   <br/>&#62; ietf-request@ietf.org
   <br/>&#62; 
   <br/>&#62; You can reach the person managing the list at
   <br/>&#62; ietf-owner@ietf.org
   <br/>&#62; 
   <br/>&#62; When replying, please edit your Subject line so it is more specific
   <br/>&#62; than &#34;Re: Contents of ietf digest...&#34;
   <br/>&#62; 
   <br/>&#62; 
   <br/>&#62; Today&#39;s Topics:
   <br/>&#62; 
   <br/>&#62; 1. Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh
   <br/>&#62; (nalini.elkins@insidethestack.com)
   <br/>&#62; 
   <br/>&#62; 
   <br/>&#62; ----------------------------------------------------------------------
   <br/>&#62; 
   <br/>&#62; Message: 1
   <br/>&#62; Date: Sun, 5 Mar 2017 12:51:16 +0000 (UTC)
   <br/>&#62; From: &#60;nalini.elkins@insidethestack.com&#62;
   <br/>&#62; To: IETF-Discussion Discussion &#60;ietf@ietf.org&#62;
   <br/>&#62; Cc: Amelia Yeo &#60;yeo@isoc.org&#62;
   <br/>&#62; Subject: Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh
   <br/>&#62; Message-ID: &#60;1033583681.2631578.1488718276235@mail.yahoo.com&#62;
   <br/>&#62; Content-Type: text/plain; charset=UTF-8
   <br/>&#62; 
   <br/>&#62; All,
   <br/>&#62; 
   <br/>&#62; Please contact Amelia Yao (copied) if you are able to help with this. ISOC needs two remote mentors to help with an ISOC project to build IETF capacity in Sri Lanka, Pakistan and Bangladesh. It will run from May to December and they will need about 2 mentors per country. So, they need 6 mentors all together.
   <br/>&#62; 
   <br/>&#62; The first mentor is to spend 1 hour per month talking to people who are following email lists on how to contribute to email lists, what to do, what not to do, motivate them to contribute to the list, answer their questions etc. ISOC needs a short report what people are following, who are attending the calls, quantity of post and, quality of post. They will provide a volunteer to help do the report. 
   <br/>&#62; 
   <br/>&#62; The second mentor will be to help the people that show potential to write drafts with their draft writing. ISOC doesn&#39;t know which area they will be interested in and, will have to play it by ear when these people surface out. So, they may be looking for more than one mentor here. The deliverable is by November for IETF 100 Singapore. Again, a short report has to be written out monthly about people being mentored, what area, the progress, the number of drafts and quality etc. ISOC will provide a volunteer to help with the reporting.
   <br/>&#62; 
   <br/>&#62; The reason behind the monitoring is that ISOC needs to report monthly on progress and also they are offering 2 fellowships per country for IETF Singapore. 
   <br/>&#62; 
   <br/>&#62; The report written will feed into a bigger report on work being carried out in the country and they will be selecting the cream of the elist contributors/draft writers to attend IETF100.
   <br/>&#62; 
   <br/>&#62; Thanks,
   <br/>&#62; 
   <br/>&#62; Nalini Elkins
   <br/>&#62; 
   <br/>&#62; IETF Mentoring Program
   <br/>&#62; 
   <br/>&#62; Inside Products, Inc.www.insidethestack.com
   <br/>&#62; (831) 659-8360
   <br/>&#62; 
   <br/>&#62; 
   <br/>&#62; 
   <br/>&#62; ------------------------------
   <br/>&#62; 
   <br/>&#62; Subject: Digest Footer
   <br/>&#62; 
   <br/>&#62; _______________________________________________
   <br/>&#62; ietf mailing list
   <br/>&#62; ietf@ietf.org
   <br/>&#62; https://www.ietf.org/mailman/listinfo/ietf
   <br/>&#62; 
   <br/>&#62; 
   <br/>&#62; ------------------------------
   <br/>&#62; 
   <br/>&#62; End of ietf Digest, Vol 106, Issue 14
   <br/>&#62; *************************************
  </div>
 
<br />-------------------------------------------------------------------------------------------------------------------------------
<br />[ C-DAC is on Social-Media too. Kindly follow us at: 
<br />Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
<br />
<br />This e-mail is for the sole use of the intended recipient(s) and may
<br />contain confidential and privileged information. If you are not the
<br />intended recipient, please contact the sender by reply e-mail and destroy
<br />all copies and the original message. Any unauthorized review, use,
<br />disclosure, dissemination, forwarding, printing or copying of this email
<br />is strictly prohibited and appropriate legal action will be taken.
<br />-------------------------------------------------------------------------------------------------------------------------------
</body></html>

------=_Part_6634_61719040.1488791115212--


From nobody Mon Mar  6 01:46:34 2017
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F28A129634; Mon,  6 Mar 2017 01:46:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-bess-evpn-vpws-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148879358351.15077.6765347397744562494.idtracker@ietfa.amsl.com>
Date: Mon, 06 Mar 2017 01:46:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2yUYuXtQjfk_t9RBJY569eAqoRs>
Cc: draft-ietf-bess-evpn-vpws.all@ietf.org, ietf@ietf.org, bess@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 09:46:23 -0000

Reviewer: Roni Even
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-bess-evpn-vpws-??
Reviewer: Roni Even
Review Date: 2017-03-06
IETF LC End Date: 2017-03-10
IESG Telechat date: 2017-04-13

Summary: The document is ready for publication as Standard track RFC

Major issues:

Minor issues:

Nits/editorial comments: 
In general lack some abbreviations expansions. just a few

1. In the abstract EVPN and PW
2. ASBR
3. In section 2 the reference to RFC7432 is not a link in the HTML and
PDF. The link is working in the other places the reference appears.





From nobody Mon Mar  6 01:48:12 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF64612961F; Mon,  6 Mar 2017 01:48:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level: 
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JtYuyC4lamZ9; Mon,  6 Mar 2017 01:48:10 -0800 (PST)
Received: from relais-inet.orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CBDD12941C; Mon,  6 Mar 2017 01:48:10 -0800 (PST)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 71456C01DF; Mon,  6 Mar 2017 10:48:08 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.33]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 3291B1C008A; Mon,  6 Mar 2017 10:48:08 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM42.corporate.adroot.infra.ftgroup ([fe80::d5fd:9c7d:2ee3:39d9%19]) with mapi id 14.03.0319.002; Mon, 6 Mar 2017 10:48:05 +0100
From: <mohamed.boucadair@orange.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: RE: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Topic: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Index: AQHSlHjIW16HGO4+t0uTj3JDzcmOe6GHjPnw
Date: Mon, 6 Mar 2017 09:48:05 +0000
Message-ID: <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com>
In-Reply-To: <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_68cef6cef5174b36ae91cc82c6fa4465OPEXCLILM42corporateadr_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bX-M9Uz_o8lWRUaw8IjQmE1wN54>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 09:48:11 -0000

--_000_68cef6cef5174b36ae91cc82c6fa4465OPEXCLILM42corporateadr_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgVGVkLA0KDQpQbGVhc2Ugc2VlIGlubGluZS4NCg0KQ2hlZXJzLA0KTWVkDQoNCkRlIDogVGVk
IEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbV0NCkVudm95w6kgOiBzYW1lZGkgNCBt
YXJzIDIwMTcgMDA6NDkNCsOAIDogQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09MTg0KQ2MgOiBpZXRm
QGlldGYub3JnOyBkcmFmdC1oYXJkaWUtcHJpdnNlYy1tZXRhZGF0YS1pbnNlcnRpb25AaWV0Zi5v
cmcNCk9iamV0IDogUmU6IExhc3QgQ2FsbDogPGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRh
LWluc2VydGlvbi0wNS50eHQ+IChEZXNpZ24gY29uc2lkZXJhdGlvbnMgZm9yIE1ldGFkYXRhIElu
c2VydGlvbikgdG8gSW5mb3JtYXRpb25hbCBSRkMNCg0KSGkgTW9oYW1lZCwNCkkndmUgdXBkYXRl
ZCB0aGUgZHJhZnQgYW5kIHBvc3RlZCAtMDcuICBJIGJlbGlldmUgaXQgaW5jbHVkZXMgYWxsIG9m
IHRoZSBlbGVtZW50cyBvbiB3aGljaCB3ZSBoYXZlIGFscmVhZHkgYWdyZWVkLiBTb21lIGFkZGl0
aW9uYWwgY29tbWVudHMgaW4tbGluZSwgb25jZSBhZ2FpbiB3aXRoIHNvbWUgc25pcHBhZ2UgZm9y
IHJlYWRhYmlsaXR5Lg0KDQpPbiBGcmksIE1hciAzLCAyMDE3IGF0IDE6MjMgQU0sIDxtb2hhbWVk
LmJvdWNhZGFpckBvcmFuZ2UuY29tPG1haWx0bzptb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29t
Pj4gd3JvdGU6DQoNCg0KVGhlIGludGVudCBpcyB0aGF0IGl0IGlzIGluZm9ybWF0aW9uIHVzZWZ1
bCB0byB0aG9zZSBjb25zaWRlcmluZyB3aGV0aGVyIHJlc3RvcmluZyBtZXRhZGF0YSBsb3N0IHRv
IGVuY3J5cHRpb24gaW4gbWlkLW5ldHdvcmsgaXMgdGhlIHJpZ2h0IHdheSB0byBnby4NCltNZWRd
IFRoaXMgaXMgYW5vdGhlciBhc3N1bXB0aW9uIGluIHRoZSBkb2N1bWVudCB0aGF0IEkgZGlzYWdy
ZWUgd2l0aDogSXQgc2VlbXMgdGhhdCB5b3UgYXNzdW1lIHRoYXQgYW4gb24tcGF0aCBkZXZpY2Us
IHRoYXQgaW5zZXJ0cyBtZXRhZGF0YSwgaXMgbmVjZXNzYXJpbHkgUkVTVE9SSU5HIGJhY2sgdGhh
dCBpbmZvcm1hdGlvbi4gVGhpcyBpcyBub3QgdHJ1ZSBmb3IgbWFueSBlZmZvcnRzOg0KDQrigKIg
ICAgICAgICBBIEZvcndhcmQtRm9yIGhlYWRlciBpbnNlcnRlZCBieSBhIHByb3h5IGRvZXMgbm90
IHJlc3RvcmUgYW55IGRhdGE7IGl0IGRvZXMgb25seSByZXZlYWwgZGF0YSB0aGF0IGlzIGFscmVh
ZHkgcHJlc2VudCBpbiB0aGUgcGFja2V0IGlzc3VlZCBieSB0aGUgY2xpZW50IGl0c2VsZi4NClRo
YXQncyB3aGF0IHJlc3RvcmUgbWVhbnMgaGVyZS4NCltNZWRdIFRoZW4sIHRoaXMgbmVlZHMgdG8g
YmUgZGVmaW5lZCBpbiB0aGUgZG9jdW1lbnQuIEkgbmFpdmVseSBhc3N1bWVkIHRoYXQg4oCccmVz
dG9yZWTigJ0gaXMgdXNlZCB0byBtZWFuIGFueSBwaWVjZSBvZiBpbmZvcm1hdGlvbiB0aGF0IHRo
ZSBjbGllbnQgZG9lcyBub3Qgd2FudCB0byBpbnNlcnQgaW4gYSBwYWNrZXQsIGJ1dCBhbiBvbi1w
YXRoIGRldmljZSBkZWNpZGVzIHRvIGluamVjdCBpdCBkZXNwaXRlIHRoZXJlIGlzIG5vIGNvbnNl
bnQgZnJvbSB0aGUgY2xpZW50LiBXaGF0IHlvdSBhcmUgZGVzY3JpYmluZyBpcyBtb3JlIGFib3V0
IOKAnG1haW50YWluaW5n4oCdIG9yIOKAnHByZXNlcnZpbmfigJ0gaW5mb3JtYXRpb24gbm90IHJl
c3RvcmluZyBpdC4NCg0KICBJZiB0aGUgaW5mb3JtYXRpb24gaXMgcHJlc2VudCBhcyBtZXRhZGF0
YSBpbiB0aGUgcGFja2V0IHNlbnQgdG8gdGhlIHByb3h5IGJ1dCB3b3VsZCBiZSBhYnNlbnQgYXMg
bWV0YWRhdGEgdW5kZXIgbm9ybWFsIG9wZXJhdGlvbiBvZiB0aGUgcHJveHksIGFkZGluZyBpdCBi
YWNrIGluIHNvbWV3aGVyZSBlbHNlIHJlc3RvcmVzIHRoZSBtZXRhZGF0YS4NCltNZWRdIOKAnG5v
cm1hbCBvcGVyYXRpb24gb2YgcHJveHnigJ0gaXMgbm90IGEgc3RhbmRhcmQuIEEg4oCcbm9ybWFs
IG9wZXJhdGlvbiBvZiBwcm94eeKAnSB3b3VsZCBiZSB0byBtYWludGFpbiB0aGUgaW5mb3JtYXRp
b24gc2VudCBieSB0aGUgY2xpZW50IHdoZW4gcmVsYXlpbmcgaXQgdG8gdGhlIHNlcnZlci4gSeKA
mW0gc3VyZSB5b3Uga25vdyBmb3IgaW5zdGFuY2UgdGhhdCBTSVAgQjJCVUFzIGNhbiBkbyB3aGF0
ZXZlciB0aGV5IHdhbnQhDQoNClNvIG9yaWdpbiBJUCBhZGRyZXNzIHN0YXJ0cyBvdXQgaW4gdGhl
IElQIGhlYWRlciBvZiB0aGUgb3JpZ2luYWwgcGFja2V0IGJ1dCBnZXRzIHB1c2hlZCBmcm9tIHRo
YXQgc2xvdCB3aGVuIHRoZSBwcm94eSBjb25zdHJ1Y3RzIHRoZSBvbndhcmQgSVAgcGFja2V0IHRv
IHRoZSBzZXJ2ZXIuICBGb3IgaXQgdG8gcmVhY2ggdGhlIHNlcnZlciwgaXQgaGFzIHRvIGJlIHBs
YWNlZCBzb21ld2hlcmUgZWxzZSBpbiB0aGUgb253YXJkIHBhY2tldCwgcmVzdG9yaW5nIHRoZSBs
b3N0IG1ldGFkYXRhLg0KW01lZF0gVGhlIGNsaWVudCBhZ3JlZWQgdG8gc2VuZCBwYWNrZXRzIHdp
dGggaXRzIHNvdXJjZSBJUCBhZGRyZXNzICh3aGljaCBtZWFuIGNvbnNlbnQpLiBXaHkgdGhlIHBy
b3h5IHdvdWxkIG5lZWQgdG8gYW4gZXh0cmEgY2hhbm5lbCB0byBnZXQgY29uc2VudCBmb3IgcmVs
YXlpbmcgdGhlIHNvdXJjZSBJUCBhZGRyZXNzIHRvIGEgc2VydmVyPw0KDQpIYWQgaXQgYmVlbiBw
cmVzZW50IGluIHRoZSBwYWNrZXQgYXMgaGVhZGVyIHZhbHVlIGluIHRoZSBIVFRQIGV4Y2hhbmdl
LCBpdCB3b3VsZCBub3QgaGF2ZSBiZWVuIHN0cmlwcGVkIGJ5IG5vcm1hbCBvcGVyYXRpb24uICBU
aGVyZSBwcm94eSBvcGVyYXRpb24gZm9yd2FyZGluZyBpdCBvbiB3b3VsZCBiZSBzaW1wbHkgcHJl
c2VydmluZyBpdC4NCltNZWRdIFRoaXMgaXMgYW5vdGhlciBxdWVzdGlvbjogd2hldGhlciB0aGUg
c2FtZSBvciBkaXN0aW5jdCBjaGFubmVsIGNhbiBiZSB1c2VkIHRvIGNvbW11bmljYXRlIHRoZSBT
QU1FIGRhdGEgdGhhdCB3YXMgcHJlc2VudCBpbiB0aGUgaW5pdGlhbCBwYWNrZXQgaXNzdWVkIGJ5
IGEgaG9zdC4NCg0KDQrigKIgICAgICAgICBBbiBhZGRyZXNzIHNoYXJpbmcgZGV2aWNlLCB1bmRl
ciBmb3IgZXhhbXBsZSBEUy1MaXRlIChSRkM2MzMzKSwgdGhhdCBpbnNlcnRzIHRoZSBzb3VyY2Ug
SVB2NiBwcmVmaXggaW4gdGhlIFRDUCBIT1NUX0lEIG9wdGlvbiAoUkZDNzk3NCkgaXMgbm90IFJF
U1RPUklORyBhbnkgZGF0YS4gVGhlIGNvbnRlbnQgb2YgdGhhdCBUQ1Agb3B0aW9uIGlzIGFscmVh
ZHkgdmlzaWJsZSBpbiB0aGUgcGFja2V0IHNlbnQgYnkgdGhlIGhvc3QuDQpJIGFncmVlIHdpdGgg
dGhlIElFU0cgYW5hbHlzaXMgb2YgUkZDNzk3NC4gIEl0IGRvZXMgcmVzdG9yZSBpbmZvcm1hdGlv
biBieSB0YWtpbmcgaW5mb3JtYXRpb24gd2hpY2ggbm9ybWFsIG9wZXJhdGlvbiB3b3VsZCBoYXZl
IGVsaWRlZCBhbmQgcmVzdG9yZXMgaXQuDQpbTWVkXSBUaGUgIGltcGxpY2F0aW9uIG9mIHdoYXQg
eW91IGFyZSBzYXlpbmcgaGVyZSBpcyB0aGF0IHByb3hpZXMgYXJlIGdvb2QgYmVjYXVzZSB0aGV5
IGhpZGUgdGhlIHNvdXJjZSBJUCBhZGRyZXNzZXMgb2YgaG9zdCENCg0KDQoNCuKAoiAgICAgICAg
IFNlcnZpY2UgRnVuY3Rpb24gQ2hhaW5pbmcgV0cgKGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvd2cvc2ZjL2Fib3V0LykgaXMgZGVmaW5pbmcgYW4gYXJjaGl0ZWN0dXJlIHRvIGNvbW11bmlj
YXRlIG1ldGFkYXRhIGJ5IG9uLXBhdGggZGV2aWNlczsgdGhhdCBtZXRhZGF0YSBpcyBpbnNlcnRl
ZCBhdCB0aGUgbmV0d29yayBzaWRlLiBCb3JkZXIgbm9kZXMgd2lsbCBtYWtlIHN1cmUgdGhhdCBk
YXRhIGlzIHN0cmlwcGVkIGJlZm9yZSBmb3J3YXJkaW5nIHBhY2tldHMgdG8gdGhlIHVsdGltYXRl
IGRlc3RpbmF0aW9ucy4gVGhlIG1ldGFkYXRhIGNhbiBiZSBhIHN1YnNjcmliZXItaWQsIGEgcG9s
aWN5LWlkLCBldGMuDQoNCg0KSSdtIGFmcmFpZCBJIGRvbid0IGhhdmUgZW5vdWdoIGNvbnRleHQg
dG8ga25vdyB3aGF0IGJvcmRlciBub2RlIG9wZXJhdGlvbnMgYXJlIGhlcmUsIHNvIHRoaXMgaXMg
ZGlmZmljdWx0IGZvciBtZSB0byBjb21tZW50IG9uLCBidXQgSSBob3BlIHRoZSB0d28gZXhhbXBs
ZXMgYWJvdmUgY2xhcmlmeSBteSB0aGlua2luZy4NCltNZWRdIEEgQk4gaXMgZGVmaW5lZCBoZXJl
IDogaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzc2NjUjc2VjdGlvbi00LjQNCg0KDQpT
byB3aGVuIGRyYWZ0LWhhcmRpZS0qIHNheXM6IOKAnERvIG5vdCBhZGQgbWV0YWRhdGEgdG8gZmxv
d3MgYXQgaW50ZXJtZWRpYXJ5IGRldmljZXMgdW5sZXNzDQogICBhIHBvc2l0aXZlIGFmZmlybWF0
aW9uIG9mIGFwcHJvdmFsIGZvciByZXN0b3JhdGlvbiBoYXMgYmVlbiByZWNlaXZlZA0KICAgZnJv
bSB0aGUgYWN0b3Igd2hvc2UgZGF0YSB3aWxsIGJlIGFkZGVkLuKAnQ0KDQooMSkgRG8geW91IGFz
c3VtZSB0aGF0IHRoZSBzYW1wbGUgZXhhbXBsZXMgSSBsaXN0ZWQgYWJvdmUgZmFsbCB1bmRlciB5
b3VyIGFkdmljZT8NCigyKSBIb3cgYW4gb24tcGF0aCBkZXZpY2Ugd2lsbCBrbm93IHRoZSBkYXRh
IGl0IGludGVuZHMgdG8gaW5zZXJ0IGlzIGEg4oCccmVzdG9yYXRpb27igJ0/DQoNCklmIHRoZSBk
YXRhIGlzIHRha2VuIGZyb20gYSBwb3J0aW9uIG9mIHRoZSBwYWNrZXQgdGhhdCB3b3VsZCBub3Qg
bm9ybWFsbHkgYmUgZm9yd2FyZGVkIHRvIGFuIHVwc3RyZWFtIGhvc3QgYW5kIGFkZGVkIHRvIGEg
cG9ydGlvbiB0aGF0IGlzIGZvcndhcmRlZCB0byBhbiB1cHN0cmVhbSBob3N0LCB0aGVuIHRoZSBk
ZXZpY2UgYWRkaW5nIHRoZSBkYXRhIGJhY2sgaW4gc2hvdWxkIGtub3cgaXQgaXMgYSByZXN0b3Jh
dGlvbi4NCltNZWRdIFRoYXQgZGVmaW5pdGlvbiBpcyBub3QgdHJpdmlhbCBhcyBtZW50aW9uZWQg
YWJvdmUuIEkgd291bGQgdXNlIOKAnHByZXNlcnZl4oCdIG9yIOKAnG1haW50YWlu4oCdIHJhdGhl
ciB0aGFuIOKAnHJlc3RvcmXigJ0uDQoNCigzKSBEb2VzIGl0IG1lYW4gdGhhdCBmb3IgbmV3IGRh
dGEgKGkuZS4sIHRoYXQgYXJlIG5vdCByZXN0b3JhdGlvbiksIG9uLXBhdGggZGV2aWNlcyBhcmUg
ZnJlZSB0byBkbyB3aGF0ZXZlciB0aGV5IHdhbnQ/IEZvciBtZSwgdGhpcyBpcyB1bmRlc2lyYWJs
ZS4gVGhlcmUgaXMgYSB2b2lkIHRoZXJlLiBBIHN0YXRlbWVudCB0byByZXF1aXJlIHRob3NlIG5l
dHdvcmtzIHRvIGF2b2lkIGxlYWtpbmcgcHJpdmFjeSBpbmZvcm1hdGlvbiBtdXN0IGJlIGluY2x1
ZGVkLg0KDQpCcmlhbiBUcmFtbWVsbCBoYXMgYW4gZXZlciBncm93aW5nIGxpc3Qgb2Ygc2lkZSBj
aGFubmVscyBhdHRhY2tzLCBhbmQgdGhpcyBkb2N1bWVudCBkb2Vzbid0IG1lYW4gdG8gY292ZXIg
dGhhdCBlbnRpcmUgZ3JvdW5kLiAgSXQncyBhZHZpY2UgZm9yIHByb3RvY29sIGRlc2lnbmVycyBv
biB3aGF0IHRoZSBwcml2YWN5IGltcGxpY2F0aW9ucyBhcmUgb2YgbWFraW5nIHRoZSBjaG9pY2Ug
dG8gdXNlIG5ldHdvcmsgZWxlbWVudHMgdG8gY2FycnkgdGhpcyBkYXRhLg0KDQoNCkFub3RoZXIg
YXNzdW1wdGlvbiBpcyBtYWRlIGhlcmU6DQoNCiAgIEluc3RlYWQsIGRlc2lnbiB0aGUgcHJvdG9j
b2wgc28gdGhhdCB0aGUgYWN0b3IgY2FuIGFkZCBzdWNoIG1ldGFkYXRhDQogICB0aGVtc2VsdmVz
IHNvIHRoYXQgaXQgZmxvd3MgZW5kLXRvLWVuZCwgcmF0aGVyIHRoYW4gcmVxdWlyaW5nIHRoZQ0K
ICAgYWN0aW9uIG9mIG90aGVyIHBhcnRpZXMuICBJbiBhZGRpdGlvbiB0byBpbXByb3ZpbmcgcHJp
dmFjeSwgdGhpcw0KICAgYXBwcm9hY2ggZW5zdXJlcyBjb25zaXN0ZW50IGF2YWlsYWJpbGl0eSBi
ZXR3ZWVuIHRoZSBjb21tdW5pY2F0aW5nDQogICBwYXJ0aWVzLCBubyBtYXR0ZXIgd2hhdCBwYXRo
IGlzIHRha2VuLg0KDQpUaGlzIHRleHQgY2xhaW1zIHRoYXQgcHJvdmlkaW5nIGRhdGEgYnkgdGhl
IGVuZHBvaW50IGVuc3VyZXMgYSDigJxjb25zaXN0ZW50IGF2YWlsYWJpbGl0eeKAnSBvZiB0aGF0
IGluZm9ybWF0aW9uLiBUaGlzIGlzIGJyb2tlbiBmb3IgYSBtdWx0aS1ob21lZCBob3N0IHRoYXQg
dXNlcyBmb3IgZXhhbXBsZSBGb3J3YXJkLUZvciBoZWFkZXI6IE9idmlvdXNseSwgdGhlIGNvbnRl
bnQgb2YgdGhlIGhlYWRlciBpZiBpbmplY3RlZCBieSB0aGUgZW5kcG9pbnQgd2lsbCBkZXBlbmQg
b24gdGhlIHBhdGguDQoNCklmIHRoZSBlbmRwb2ludCBzZW5kcyB0aGUgZGF0YSwgZGF0YSB3aWxs
IGJlIGNvbnNpc3RlbnRseSBhdmFpbGFibGUgaW4gdGhhdCBoZWFkZXIuICBUaGUgZGF0YSBjaGFu
Z2VzLCBvZiBjb3Vyc2UuDQpbTWVkXSBJ4oCZbSBub3Qgc3VyZSB0byBmb2xsb3cgeW91IGhlcmUu
IFdoYXQgaXMgbWVhbnQgYnkg4oCcY29uc2lzdGVudCBhdmFpbGFiaWxpdHnigJ0gdGhlbj8gRG8g
eW91IG1lYW4gdGhlIHNhbWUgY2hhbm5lbC9wcm9jZWR1cmUgdG8gY29tbXVuaWNhdGUgdGhlIGlu
Zm9ybWF0aW9uPyBPciDigJxjb25zaXN0ZW50IGRhdGHigJ0/DQoNCg0KW01lZF0gUmVzb3VyY2Vz
IG1heSBub3QgYmUgcmVzdHJpY3RlZCB0byBDUFUgb3IgZGlzayBidXQgbWF5IGJlIGdyYW50aW5n
IGFjY2VzcyB0byB0aGUgc2VydmljZSAoZS5nLiwgZG93bmxvYWQgYSBmaWxlIHdoZW4gYSBxdW90
YSBwZXIgc291cmNlIGFkZHJlc3MgaXMgZW5mb3JjZWQpLiBJdCBjYW4gYmUgd2hhdGV2ZXIgdGhl
IHNlcnZlcnMgY29uc2lkZXIgdG8gYmUgY3JpdGljYWwgZm9yIHRoZW07IGl0IGlzIHVwIHRvIHRo
ZSB0YXN0ZSBvZiB0aGUgc2VydmljZSBkZXNpZ24gdG8gY2hhcmFjdGVyaXplIGl0LiBUaGUgTkVX
IHdvcmRpbmcgcHJvcG9zZWQgYWJvdmUgaXMgdGVjaG5pY2FsbHkgY29ycmVjdC4gUGxlYXNlIHJl
Y29uc2lkZXIgYWRkaW5nIGl0IHRvIHRoZSBkcmFmdC4NCg0KDQoNCkkgZGlkIGNvbnNpZGVyIGl0
LCBidXQgSSBjb250aW51ZSB0byBiZWxpZXZlIHRoYXQgaXQgbW92ZXMgdGhlIG5lZWRsZSB0b28g
ZmFyIGludG8gc2ltcGxlIHNlcnZlciBwcmVmZXJlbmNlLiAgSSByZXRhaW5lZCB0aGUgb3JpZ2lu
YWwgUFNBUCBsYW5ndWFnZSBpbiAtMDcgYXMgYSByZXN1bHQuDQpbTWVkXSBlbWVyZ2VuY3kgaXMg
b25seSBhbiBleGFtcGxlIDsgb3RoZXIgc2VydmljZXMgbWF5IGV4aXN0IHRoYXQgaW1wb3NlIHRo
ZSBzYW1lIHRydXN0IG1vZGVsLg0KDQpJIGFsc28gYWRkZWQgYSBub3RlIGFib3V0IHlvdXIgZXh0
ZW5zaXZlIHJldmlldy4gIFdoaWxlIHlvdSBhbmQgSSBjbGVhcmx5IGhhdmUgc29tZSBkaWZmZXJl
bmNlcyBvZiB2aWV3LCB0aGUgZG9jdW1lbnQgaGFzIGdvdHRlbiBiZXR0ZXIgZnJvbSB5b3VyIGVu
Z2FnZW1lbnQgd2l0aCBpdCwgYW5kIEkgYXBwcmVjaWF0ZSB5b3VyIGVmZm9ydHMuDQpbTWVkXSBJ
IHJldmlld2VkIHRoZSAtMDcuIEFsdGhvdWdoIGl0IGlzIGJldHRlciBjb21wYXJlZCB0byAtMDUs
IEkgc3RpbGwgZG9u4oCZdCB0aGluayBpdCBpcyByZWFkeSB0byBiZSBwdWJsaXNoZWQgYXMgaXQg
aXMuIFRoYW5rIHlvdSBmb3IgeW91ciBlZmZvcnQuDQpyZWdhcmRzLA0KVGVkDQo=

--_000_68cef6cef5174b36ae91cc82c6fa4465OPEXCLILM42corporateadr_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIg
MiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNv
Tm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAw
MXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIs
InNlcmlmIjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNp
dGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQcsOpZm9ybWF0w6kgSFRNTCBD
YXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTox
MC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpwLm03NzcwNzIyMjg4NDIzMTU3
MjQ5bXNvbGlzdHBhcmFncmFwaCwgbGkubTc3NzA3MjIyODg0MjMxNTcyNDltc29saXN0cGFyYWdy
YXBoLCBkaXYubTc3NzA3MjIyODg0MjMxNTcyNDltc29saXN0cGFyYWdyYXBoDQoJe21zby1zdHls
ZS1uYW1lOm1fNzc3MDcyMjI4ODQyMzE1NzI0OW1zb2xpc3RwYXJhZ3JhcGg7DQoJbXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowY207DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZh
bWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uUHJmb3JtYXRIVE1MQ2FyDQoJ
e21zby1zdHlsZS1uYW1lOiJQcsOpZm9ybWF0w6kgSFRNTCBDYXIiOw0KCW1zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUHLDqWZvcm1hdMOpIEhUTUwiOw0KCWZvbnQtZmFt
aWx5OkNvbnNvbGFzOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkZSO30NCnNwYW4uRW1haWxTdHls
ZTIwDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDb3Vy
aWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5
bGU6bm9ybWFsO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0
Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2Vj
dGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+
DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5
b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9v
OnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRlIi
IGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5IaSBUZWQsDQo8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5QbGVhc2Ugc2VlIGlubGluZS48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Q2hlZXJzLDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+TWVkPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5n
OjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij5EZSZuYnNwOzo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij4gVGVkIEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbV0NCjxicj4NCjxi
PkVudm95w6kmbmJzcDs6PC9iPiBzYW1lZGkgNCBtYXJzIDIwMTcgMDA6NDk8YnI+DQo8Yj7DgCZu
YnNwOzo8L2I+IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE48YnI+DQo8Yj5DYyZuYnNwOzo8L2I+
IGlldGZAaWV0Zi5vcmc7IGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbkBp
ZXRmLm9yZzxicj4NCjxiPk9iamV0Jm5ic3A7OjwvYj4gUmU6IExhc3QgQ2FsbDogJmx0O2RyYWZ0
LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbi0wNS50eHQmZ3Q7IChEZXNpZ24gY29u
c2lkZXJhdGlvbnMgZm9yIE1ldGFkYXRhIEluc2VydGlvbikgdG8gSW5mb3JtYXRpb25hbCBSRkM8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SGkgTW9oYW1lZCw8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSd2ZSB1cGRhdGVkIHRoZSBkcmFmdCBh
bmQgcG9zdGVkIC0wNy4mbmJzcDsgPHNwYW4gbGFuZz0iRU4tVVMiPkkgYmVsaWV2ZSBpdCBpbmNs
dWRlcyBhbGwgb2YgdGhlIGVsZW1lbnRzIG9uIHdoaWNoIHdlIGhhdmUgYWxyZWFkeSBhZ3JlZWQu
Jm5ic3A7U29tZSBhZGRpdGlvbmFsIGNvbW1lbnRzIGluLWxpbmUsIG9uY2UgYWdhaW4gd2l0aCBz
b21lIHNuaXBwYWdlIGZvciByZWFkYWJpbGl0eS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+T24gRnJpLCBNYXIgMywgMjAxNyBhdCAxOjIzIEFNLCAmbHQ7PC9zcGFuPjxhIGhyZWY9
Im1haWx0bzptb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tIiB0YXJnZXQ9Il9ibGFuayI+bW9o
YW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4N
CjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFk
ZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZu
YnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4g
bGFuZz0iRU4tVVMiPlRoZSBpbnRlbnQgaXMgdGhhdCBpdCBpcyBpbmZvcm1hdGlvbiB1c2VmdWwg
dG8gdGhvc2UgY29uc2lkZXJpbmcgd2hldGhlciByZXN0b3JpbmcgbWV0YWRhdGEgbG9zdCB0byBl
bmNyeXB0aW9uIGluIG1pZC1uZXR3b3JrIGlzIHRoZSByaWdodCB3YXkgdG8gZ28uPC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPltNZWRdIFRoaXMgaXMgYW5vdGhlciBhc3N1bXB0aW9uIGluIHRoZSBk
b2N1bWVudCB0aGF0IEkgZGlzYWdyZWUgd2l0aDogSXQgc2VlbXMgdGhhdCB5b3UgYXNzdW1lDQog
dGhhdCBhbiBvbi1wYXRoIGRldmljZSwgdGhhdCBpbnNlcnRzIG1ldGFkYXRhLCBpcyBuZWNlc3Nh
cmlseSBSRVNUT1JJTkcgYmFjayB0aGF0IGluZm9ybWF0aW9uLiBUaGlzIGlzIG5vdCB0cnVlIGZv
ciBtYW55IGVmZm9ydHM6PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj4NCjwvc3Bhbj48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0Ljhw
dDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0
Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0ibTc3NzA3MjIyODg0MjMx
NTcyNDltc29saXN0cGFyYWdyYXBoIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6U3ltYm9sO2NvbG9yOmJsYWNrIj7Ctzwvc3Bhbj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTo3LjBwdDtjb2xvcjpibGFjayI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5BIEZvcndhcmQtRm9yIGhlYWRlciBpbnNlcnRlZCBi
eSBhIHByb3h5IGRvZXMgbm90IHJlc3RvcmUgYW55IGRhdGE7IGl0IGRvZXMgb25seSByZXZlYWwg
ZGF0YSB0aGF0IGlzIGFscmVhZHkgcHJlc2VudCBpbiB0aGUgcGFja2V0IGlzc3VlZCBieSB0aGUg
Y2xpZW50IGl0c2VsZi48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGF0J3Mgd2hhdCByZXN0b3JlIG1lYW5zIGhlcmUuPHNw
YW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIFRoZW4s
IHRoaXMgbmVlZHMgdG8gYmUgZGVmaW5lZCBpbiB0aGUgZG9jdW1lbnQuIEkgbmFpdmVseSBhc3N1
bWVkIHRoYXQg4oCccmVzdG9yZWTigJ0gaXMgdXNlZCB0byBtZWFuIGFueSBwaWVjZSBvZiBpbmZv
cm1hdGlvbiB0aGF0IHRoZSBjbGllbnQgZG9lcyBub3QNCiB3YW50IHRvIGluc2VydCBpbiBhIHBh
Y2tldCwgYnV0IGFuIG9uLXBhdGggZGV2aWNlIGRlY2lkZXMgdG8gaW5qZWN0IGl0IGRlc3BpdGUg
dGhlcmUgaXMgbm8gY29uc2VudCBmcm9tIHRoZSBjbGllbnQuIFdoYXQgeW91IGFyZSBkZXNjcmli
aW5nIGlzIG1vcmUgYWJvdXQg4oCcbWFpbnRhaW5pbmfigJ0gb3Ig4oCccHJlc2VydmluZ+KAnSBp
bmZvcm1hdGlvbiBub3QgcmVzdG9yaW5nIGl0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiPiZuYnNwOyBJZiB0aGUgaW5mb3JtYXRpb24gaXMgcHJlc2VudCBhcyBtZXRhZGF0YSBp
biB0aGUgcGFja2V0IHNlbnQgdG8gdGhlIHByb3h5IGJ1dCB3b3VsZCBiZSBhYnNlbnQgYXMgbWV0
YWRhdGEgdW5kZXIgbm9ybWFsIG9wZXJhdGlvbiBvZiB0aGUgcHJveHksIGFkZGluZyBpdCBiYWNr
IGluIHNvbWV3aGVyZSBlbHNlIHJlc3RvcmVzIHRoZSBtZXRhZGF0YS4mbmJzcDs8c3BhbiBzdHls
ZT0iY29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIOKAnG5v
cm1hbCBvcGVyYXRpb24gb2YgcHJveHnigJ0gaXMgbm90IGEgc3RhbmRhcmQuIEEg4oCcbm9ybWFs
IG9wZXJhdGlvbiBvZiBwcm94eeKAnSB3b3VsZCBiZSB0byBtYWludGFpbiB0aGUgaW5mb3JtYXRp
b24gc2VudCBieSB0aGUgY2xpZW50IHdoZW4gcmVsYXlpbmcgaXQNCiB0byB0aGUgc2VydmVyLiBJ
4oCZbSBzdXJlIHlvdSBrbm93IGZvciBpbnN0YW5jZSB0aGF0IFNJUCBCMkJVQXMgY2FuIGRvIHdo
YXRldmVyIHRoZXkgd2FudCEgJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+U28gb3JpZ2luIElQIGFkZHJlc3Mgc3RhcnRzIG91dCBpbiB0aGUgSVAgaGVhZGVyIG9mIHRo
ZSBvcmlnaW5hbCBwYWNrZXQgYnV0IGdldHMgcHVzaGVkIGZyb20gdGhhdCBzbG90IHdoZW4gdGhl
IHByb3h5IGNvbnN0cnVjdHMgdGhlIG9ud2FyZCBJUCBwYWNrZXQgdG8gdGhlIHNlcnZlci4mbmJz
cDsgRm9yIGl0IHRvIHJlYWNoIHRoZSBzZXJ2ZXIsIGl0IGhhcyB0byBiZSBwbGFjZWQgc29tZXdo
ZXJlDQogZWxzZSBpbiB0aGUgb253YXJkIHBhY2tldCwgcmVzdG9yaW5nIHRoZSBsb3N0IG1ldGFk
YXRhLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gVGhlIGNsaWVudCBhZ3JlZWQgdG8gc2Vu
ZCBwYWNrZXRzIHdpdGggaXRzIHNvdXJjZSBJUCBhZGRyZXNzICh3aGljaCBtZWFuIGNvbnNlbnQp
LiBXaHkgdGhlIHByb3h5IHdvdWxkIG5lZWQgdG8gYW4gZXh0cmEgY2hhbm5lbCB0byBnZXQgY29u
c2VudCBmb3IgcmVsYXlpbmcNCiB0aGUgc291cmNlIElQIGFkZHJlc3MgdG8gYSBzZXJ2ZXI/ICZu
YnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IYWQgaXQgYmVlbiBwcmVzZW50IGlu
IHRoZSBwYWNrZXQgYXMgaGVhZGVyIHZhbHVlIGluIHRoZSBIVFRQIGV4Y2hhbmdlLCBpdCB3b3Vs
ZCBub3QgaGF2ZSBiZWVuIHN0cmlwcGVkIGJ5IG5vcm1hbCBvcGVyYXRpb24uJm5ic3A7IFRoZXJl
IHByb3h5IG9wZXJhdGlvbiBmb3J3YXJkaW5nIGl0IG9uIHdvdWxkIGJlIHNpbXBseSBwcmVzZXJ2
aW5nIGl0LjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5b
TWVkXSBUaGlzIGlzIGFub3RoZXIgcXVlc3Rpb246IHdoZXRoZXIgdGhlIHNhbWUgb3IgZGlzdGlu
Y3QgY2hhbm5lbCBjYW4gYmUgdXNlZCB0byBjb21tdW5pY2F0ZSB0aGUgU0FNRSBkYXRhIHRoYXQg
d2FzIHByZXNlbnQgaW4gdGhlIGluaXRpYWwgcGFja2V0IGlzc3VlZA0KIGJ5IGEgaG9zdC48L3Nw
YW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxicj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0Ljhw
dDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0
Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0ibTc3NzA3MjIyODg0MjMx
NTcyNDltc29saXN0cGFyYWdyYXBoIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6U3ltYm9sO2NvbG9yOmJsYWNrIj7Ctzwvc3Bhbj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTo3LjBwdDtjb2xvcjpibGFjayI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5BbiBhZGRyZXNzIHNoYXJpbmcgZGV2aWNlLCB1bmRl
ciBmb3IgZXhhbXBsZSBEUy1MaXRlIChSRkM2MzMzKSwgdGhhdCBpbnNlcnRzIHRoZSBzb3VyY2Ug
SVB2NiBwcmVmaXggaW4gdGhlIFRDUCBIT1NUX0lEIG9wdGlvbiAoUkZDNzk3NCkgaXMgbm90IFJF
U1RPUklORyBhbnkgZGF0YS4gVGhlIGNvbnRlbnQNCiBvZiB0aGF0IFRDUCBvcHRpb24gaXMgYWxy
ZWFkeSB2aXNpYmxlIGluIHRoZSBwYWNrZXQgc2VudCBieSB0aGUgaG9zdC4gPC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBh
Z3JlZSB3aXRoIHRoZSBJRVNHIGFuYWx5c2lzIG9mIFJGQzc5NzQuJm5ic3A7IEl0IGRvZXMgcmVz
dG9yZSBpbmZvcm1hdGlvbiBieSB0YWtpbmcgaW5mb3JtYXRpb24gd2hpY2ggbm9ybWFsIG9wZXJh
dGlvbiB3b3VsZCBoYXZlIGVsaWRlZCBhbmQgcmVzdG9yZXMgaXQuPHNwYW4gc3R5bGU9ImNvbG9y
OmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIFRoZSZuYnNwOyBpbXBsaWNhdGlv
biBvZiB3aGF0IHlvdSBhcmUgc2F5aW5nIGhlcmUgaXMgdGhhdCBwcm94aWVzIGFyZSBnb29kIGJl
Y2F1c2UgdGhleSBoaWRlIHRoZSBzb3VyY2UgSVAgYWRkcmVzc2VzIG9mIGhvc3QhICZuYnNwOzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIj48YnI+DQombmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1
b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3Bh
ZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBj
bSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Im03NzcwNzIyMjg4NDIzMTU3MjQ5bXNvbGlzdHBhcmFn
cmFwaCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OlN5bWJvbDtjb2xvcjpibGFjayI+wrc8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6Ny4wcHQ7Y29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+U2VydmljZSBGdW5jdGlvbiBDaGFpbmluZyBXRyAoPGEgaHJlZj0iaHR0cHM6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy93Zy9zZmMvYWJvdXQvIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy93Zy9zZmMvYWJvdXQvPC9hPikgaXMgZGVmaW5pbmcgYW4g
YXJjaGl0ZWN0dXJlDQogdG8gY29tbXVuaWNhdGUgbWV0YWRhdGEgYnkgb24tcGF0aCBkZXZpY2Vz
OyB0aGF0IG1ldGFkYXRhIGlzIGluc2VydGVkIGF0IHRoZSBuZXR3b3JrIHNpZGUuIEJvcmRlciBu
b2RlcyB3aWxsIG1ha2Ugc3VyZSB0aGF0IGRhdGEgaXMgc3RyaXBwZWQgYmVmb3JlIGZvcndhcmRp
bmcgcGFja2V0cyB0byB0aGUgdWx0aW1hdGUgZGVzdGluYXRpb25zLiBUaGUgbWV0YWRhdGEgY2Fu
IGJlIGEgc3Vic2NyaWJlci1pZCwgYSBwb2xpY3ktaWQsIGV0Yy48L3NwYW4+PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bWFyZ2luLWxlZnQ6MTYuOHB0Ij4NCjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JJ20gYWZyYWlkIEkg
ZG9uJ3QgaGF2ZSBlbm91Z2ggY29udGV4dCB0byBrbm93IHdoYXQgYm9yZGVyIG5vZGUgb3BlcmF0
aW9ucyBhcmUgaGVyZSwgc28gdGhpcyBpcyBkaWZmaWN1bHQgZm9yIG1lIHRvIGNvbW1lbnQgb24s
IGJ1dCBJIGhvcGUgdGhlIHR3byBleGFtcGxlcyBhYm92ZSBjbGFyaWZ5IG15IHRoaW5raW5nLg0K
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPltNZWRdIEEgQk4gaXMgZGVmaW5lZCBoZXJlJm5ic3A7Og0KPGEgaHJl
Zj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzc2NjUjc2VjdGlvbi00LjQiPmh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM3NjY1I3NlY3Rpb24tNC40PC9hPiAmbmJzcDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0Mg
MS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4t
cmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29s
b3I6YmxhY2siPlNvIHdoZW4gZHJhZnQtaGFyZGllLSogc2F5czog4oCcPC9zcGFuPjxzcGFuIGxh
bmc9IkVOLVVTIj5EbyBub3QgYWRkIG1ldGFkYXRhIHRvIGZsb3dzIGF0IGludGVybWVkaWFyeSBk
ZXZpY2VzIHVubGVzczwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyBhIHBvc2l0aXZlIGFmZmly
bWF0aW9uIG9mIGFwcHJvdmFsIGZvciByZXN0b3JhdGlvbiBoYXMgYmVlbiByZWNlaXZlZDwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7Ij4mbmJzcDsmbmJzcDsgZnJvbSB0aGUgYWN0b3Igd2hvc2UgZGF0YSB3aWxsIGJlIGFk
ZGVkLjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+4oCdPC9zcGFuPjwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG87bWFyZ2luLWxlZnQ6MTYuOHB0Ij4NCjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFj
ayI+KDEpIERvIHlvdSBhc3N1bWUgdGhhdCB0aGUgc2FtcGxlIGV4YW1wbGVzIEkgbGlzdGVkIGFi
b3ZlIGZhbGwgdW5kZXIgeW91ciBhZHZpY2U/PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjE2LjhwdCI+DQo8c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPigyKSBIb3cgYW4gb24tcGF0aCBkZXZpY2Ugd2lsbCBrbm93IHRoZSBk
YXRhIGl0IGludGVuZHMgdG8gaW5zZXJ0IGlzIGEg4oCccmVzdG9yYXRpb27igJ0/PC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPklmIHRoZSBkYXRhIGlzIHRha2VuIGZyb20g
YSBwb3J0aW9uIG9mIHRoZSBwYWNrZXQgdGhhdCB3b3VsZCBub3Qgbm9ybWFsbHkgYmUgZm9yd2Fy
ZGVkIHRvIGFuIHVwc3RyZWFtIGhvc3QgYW5kIGFkZGVkIHRvIGEgcG9ydGlvbiB0aGF0IGlzIGZv
cndhcmRlZCB0byBhbiB1cHN0cmVhbSBob3N0LCB0aGVuIHRoZSBkZXZpY2UgYWRkaW5nIHRoZSBk
YXRhIGJhY2sgaW4NCiBzaG91bGQga25vdyBpdCBpcyBhIHJlc3RvcmF0aW9uLjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIFRoYXQgZGVmaW5pdGlvbiBp
cyBub3QgdHJpdmlhbCBhcyBtZW50aW9uZWQgYWJvdmUuIEkgd291bGQgdXNlIOKAnHByZXNlcnZl
4oCdIG9yIOKAnG1haW50YWlu4oCdIHJhdGhlciB0aGFuIOKAnHJlc3RvcmXigJ0uDQo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBw
dDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdo
dDowY20iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVmdDoxNi44
cHQiPg0KPHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4oMykgRG9lcyBpdCBtZWFu
IHRoYXQgZm9yIG5ldyBkYXRhIChpLmUuLCB0aGF0IGFyZSBub3QgcmVzdG9yYXRpb24pLCBvbi1w
YXRoIGRldmljZXMgYXJlIGZyZWUgdG8gZG8gd2hhdGV2ZXIgdGhleSB3YW50PyBGb3IgbWUsIHRo
aXMgaXMgdW5kZXNpcmFibGUuIFRoZXJlIGlzIGEgdm9pZCB0aGVyZS4gQSBzdGF0ZW1lbnQNCiB0
byByZXF1aXJlIHRob3NlIG5ldHdvcmtzIHRvIGF2b2lkIGxlYWtpbmcgcHJpdmFjeSBpbmZvcm1h
dGlvbiBtdXN0IGJlIGluY2x1ZGVkLg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8
L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkJyaWFuIFRyYW1tZWxsIGhhcyBhbiBldmVyIGdyb3dpbmcgbGlzdCBvZiBzaWRl
IGNoYW5uZWxzIGF0dGFja3MsIGFuZCB0aGlzIGRvY3VtZW50IGRvZXNuJ3QgbWVhbiB0byBjb3Zl
ciB0aGF0IGVudGlyZSBncm91bmQuJm5ic3A7DQo8c3BhbiBsYW5nPSJFTi1VUyI+SXQncyBhZHZp
Y2UgZm9yIHByb3RvY29sIGRlc2lnbmVycyBvbiB3aGF0IHRoZSBwcml2YWN5IGltcGxpY2F0aW9u
cyBhcmUgb2YgbWFraW5nIHRoZSBjaG9pY2UgdG8gdXNlIG5ldHdvcmsgZWxlbWVudHMgdG8gY2Fy
cnkgdGhpcyBkYXRhLjxicj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0Mg
MS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4t
cmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+QW5vdGhlciBhc3N1bXB0aW9uIGlzIG1hZGUgaGVyZToN
Cjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7
IEluc3RlYWQsIGRlc2lnbiB0aGUgcHJvdG9jb2wgc28gdGhhdCB0aGUgYWN0b3IgY2FuIGFkZCBz
dWNoIG1ldGFkYXRhPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyB0aGVtc2VsdmVzIHNvIHRoYXQg
aXQgZmxvd3MgZW5kLXRvLWVuZCwgcmF0aGVyIHRoYW4gcmVxdWlyaW5nIHRoZTwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
Ij4mbmJzcDsmbmJzcDsgYWN0aW9uIG9mIG90aGVyIHBhcnRpZXMuJm5ic3A7IEluIGFkZGl0aW9u
IHRvIGltcHJvdmluZyBwcml2YWN5LCB0aGlzPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyBhcHBy
b2FjaCBlbnN1cmVzIGNvbnNpc3RlbnQgYXZhaWxhYmlsaXR5IGJldHdlZW4gdGhlIGNvbW11bmlj
YXRpbmc8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7IHBhcnRpZXMsIG5vIG1hdHRlciB3aGF0IHBh
dGggaXMgdGFrZW4uPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij5UaGlzIHRleHQgY2xh
aW1zIHRoYXQgcHJvdmlkaW5nIGRhdGEgYnkgdGhlIGVuZHBvaW50IGVuc3VyZXMgYSDigJxjb25z
aXN0ZW50IGF2YWlsYWJpbGl0eeKAnSBvZiB0aGF0IGluZm9ybWF0aW9uLg0KIFRoaXMgaXMgYnJv
a2VuIGZvciBhIG11bHRpLWhvbWVkIGhvc3QgdGhhdCB1c2VzIGZvciBleGFtcGxlIEZvcndhcmQt
Rm9yIGhlYWRlcjogT2J2aW91c2x5LCB0aGUgY29udGVudCBvZiB0aGUgaGVhZGVyIGlmIGluamVj
dGVkIGJ5IHRoZSBlbmRwb2ludCB3aWxsIGRlcGVuZCBvbiB0aGUgcGF0aC4NCjwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SWYgdGhlIGVuZHBvaW50IHNlbmRzIHRoZSBkYXRhLCBkYXRhIHdpbGwgYmUgY29uc2lzdGVudGx5
IGF2YWlsYWJsZSBpbiB0aGF0IGhlYWRlci4mbmJzcDsgVGhlIGRhdGEgY2hhbmdlcywgb2YgY291
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5yc2UuPC9zcGFuPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBJ4oCZbSBub3Qgc3VyZSB0
byBmb2xsb3cgeW91IGhlcmUuIFdoYXQgaXMgbWVhbnQgYnkg4oCcPC9zcGFuPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90OyI+Y29uc2lzdGVudCBhdmFpbGFiaWxpdHnigJ0NCiB0aGVuPC9zcGFuPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PyBEbyB5b3UgbWVhbiB0aGUgc2FtZSBjaGFu
bmVsL3Byb2NlZHVyZSB0byBjb21tdW5pY2F0ZSB0aGUgaW5mb3JtYXRpb24/IE9yIOKAnGNvbnNp
c3RlbnQgZGF0YeKAnT88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0ND
Q0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFy
Z2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8
ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291
cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291
cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIFJlc291cmNlcyBtYXkgbm90IGJlIHJl
c3RyaWN0ZWQgdG8gQ1BVIG9yIGRpc2sgYnV0IG1heSBiZSBncmFudGluZyBhY2Nlc3MgdG8gdGhl
IHNlcnZpY2UNCiAoZS5nLiwgZG93bmxvYWQgYSBmaWxlIHdoZW4gYSBxdW90YSBwZXIgc291cmNl
IGFkZHJlc3MgaXMgZW5mb3JjZWQpLiBJdCBjYW4gYmUgd2hhdGV2ZXIgdGhlIHNlcnZlcnMgY29u
c2lkZXIgdG8gYmUgY3JpdGljYWwgZm9yIHRoZW07IGl0IGlzIHVwIHRvIHRoZSB0YXN0ZSBvZiB0
aGUgc2VydmljZSBkZXNpZ24gdG8gY2hhcmFjdGVyaXplIGl0LiBUaGUgTkVXIHdvcmRpbmcgcHJv
cG9zZWQgYWJvdmUgaXMgdGVjaG5pY2FsbHkgY29ycmVjdC4gUGxlYXNlDQogcmVjb25zaWRlciBh
ZGRpbmcgaXQgdG8gdGhlIGRyYWZ0LiA8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxicj4NCjxi
cj4NCiZuYnNwOyA8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgZGlkIGNvbnNpZGVyIGl0LCBidXQgSSBjb250aW51ZSB0
byBiZWxpZXZlIHRoYXQgaXQgbW92ZXMgdGhlIG5lZWRsZSB0b28gZmFyIGludG8gc2ltcGxlIHNl
cnZlciBwcmVmZXJlbmNlLiZuYnNwOyBJIHJldGFpbmVkIHRoZSBvcmlnaW5hbCBQU0FQIGxhbmd1
YWdlIGluIC0wNyBhcyBhIHJlc3VsdC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gZW1lcmdlbmN5IGlz
IG9ubHkgYW4gZXhhbXBsZSZuYnNwOzsgb3RoZXIgc2VydmljZXMgbWF5IGV4aXN0IHRoYXQgaW1w
b3NlIHRoZSBzYW1lIHRydXN0IG1vZGVsLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SSBhbHNvIGFkZGVkIGEgbm90ZSBhYm91dCB5
b3VyIGV4dGVuc2l2ZSByZXZpZXcuJm5ic3A7IFdoaWxlIHlvdSBhbmQgSSBjbGVhcmx5IGhhdmUg
c29tZSBkaWZmZXJlbmNlcyBvZiB2aWV3LCB0aGUgZG9jdW1lbnQgaGFzIGdvdHRlbiBiZXR0ZXIg
ZnJvbSB5b3VyIGVuZ2FnZW1lbnQgd2l0aCBpdCwgYW5kIEkgYXBwcmVjaWF0ZSB5b3VyIGVmZm9y
dHMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJv
dHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gSSBy
ZXZpZXdlZCB0aGUgLTA3LiBBbHRob3VnaCBpdCBpcyBiZXR0ZXIgY29tcGFyZWQgdG8gLTA1LCBJ
IHN0aWxsIGRvbuKAmXQgdGhpbmsgaXQgaXMgcmVhZHkgdG8gYmUgcHVibGlzaGVkIGFzIGl0IGlz
LiBUaGFuaw0KIHlvdSBmb3IgeW91ciBlZmZvcnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIu
MHB0Ij5yZWdhcmRzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+VGVkPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_68cef6cef5174b36ae91cc82c6fa4465OPEXCLILM42corporateadr_--


From nobody Mon Mar  6 05:05:16 2017
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 BC3491294D2 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 05:05:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, TVD_PH_BODY_ACCOUNTS_PRE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7d64Z_-oaRiI for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 05:05:13 -0800 (PST)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A64D12943E for <ietf@ietf.org>; Mon,  6 Mar 2017 05:05:13 -0800 (PST)
Received: by mail-yw0-x231.google.com with SMTP id o4so56742922ywd.3 for <ietf@ietf.org>; Mon, 06 Mar 2017 05:05:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=YXPfYJxN4WEC5Ao0cI0ldpGmLaQvXaGWu7Y0xHRlTV4=; b=Mqd7krpxUbfsdXU52MA8wHgPQ2aWOnKpua6X77eSidYkY0OyaEG9M6Vy12ZTTXuN4h ZetBzl3hqco4pe9HTcSJBN9w1GtMIO864G39e18rGfkWplPIL4jqNqMY8LX8zHnjVyO5 rZ8y3x5V9FkWrsyF3Qf9CFbrFqlvMyvq4uL8mTqd30i0syNLTbmARwRHgeL9ySsISjS3 XnY+L6+YI3QCFP66zdvKkApxJwbtveBl7Apr1RAr3mZYWNk8CGpT84CPlPuIHW1m8Nag ziaLYbDlXw/6co+rtF7AZSE6QBcM6o6HKMTbyWaIF66z2/Xc+Zbb3VNRd1qb2sG9vPy9 jsYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=YXPfYJxN4WEC5Ao0cI0ldpGmLaQvXaGWu7Y0xHRlTV4=; b=a8EOGC5Ho/8jdjsHSiuWCCe2nSGfqx+UedX/oLFClDfZ9TIALgQPQYUTrDZY7kXsco ke9QY54fx9/2AQ1sW29NuNTOXWfLzoIHwqFMwA8NBBEgxOai71mziU7Bmjctut8px029 FZyb0w8wZLOwz9Qam66RqRr4t0Zda0cujLSUP5zZvnywZYIkRlvL2G6/dR/uRUHhBbol Mn/zIWKdoHL00xcHCxgqL6jgb9zH7hNNurGPcGFPQmiLWogmRbBSAU/gmM4cViGRcjGo KbqJRfl4k3AfO3/lKxWniWRmhBg2p26Qf9/Y60rz3nU593gI62cuy3THJahJUjIC7M1B awGA==
X-Gm-Message-State: AMke39lgtySuDHtAlBVn31GF3n231iA95QKmpqrJc3HnF9h9sZUiqnevRnLka25+O/9dluGHu0KKdL+BvxOovw==
X-Received: by 10.129.97.214 with SMTP id v205mr10598757ywb.237.1488805512225;  Mon, 06 Mar 2017 05:05:12 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Mon, 6 Mar 2017 05:05:11 -0800 (PST)
In-Reply-To: <20170302055128.GJ12470@Alexs-MacBook-Pro>
References: <20170302055128.GJ12470@Alexs-MacBook-Pro>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 6 Mar 2017 08:05:11 -0500
X-Google-Sender-Auth: gYlUsj-R_j0fo5KFfeM2Nhr4d50
Message-ID: <CAMm+Lwg_kAtYUGivYSF5ZzF5nfywS4rzYG88UEzxgjRL2_=83Q@mail.gmail.com>
Subject: Re: Interest in a push-based two-factor auth standard?
To: Alex Jordan <alex@strugee.net>
Content-Type: multipart/alternative; boundary=001a11490cd8b22fbd054a0f8bf4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oE9zSmATm_ekojdl85jQ8ac92vM>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 13:05:14 -0000

--001a11490cd8b22fbd054a0f8bf4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 2, 2017 at 12:51 AM, Alex Jordan <alex@strugee.net> wrote:

> Heya!
>
> A widely deployed way to do two-factor authentication is
> TOTP. However, when used with an Android device Google Accounts have a
> really nice flow where Google will send a push notification to the
> Android device, which will then prompt the user with a "yes/no"
> question as to whether they were trying to log in or not. From a UX
> perspective this is much nicer than opening an app, manually typing in
> a code, etc.
>
> With WebPush core having been just ratified as RFC 8030, the time
> seems ripe for standardizing an authentication scheme like described
> above.
>
> I have two questions:
>
> 1. Is there interest in creating such a standard at the IETF?
>
> 2. If there is, where would be the best place to do that work? I'm
> relatively new to the IETF - I poked around Datatracker's list of
> Working Groups and there didn't seem to be one that really fit that
> well. Did I miss something? Or should this go through the IETF
> individual submission track?
>
> Please CC me on replies; I'm not subscribed.
>

=E2=80=8Bi am interested and have developed several protocols of this type =
using
JSON. My work provides prior art back to 2010 at the very least.

What we are discussing goes beyond two factor auth. If you have a cell
phone with a device specific signature key, it can sign the response which
means that you automatically collect up a non repudiable audit log of the
user's actions. This is beyond anything possible with OTP number sequences
or USB dongles.

=E2=80=8B

--001a11490cd8b22fbd054a0f8bf4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Ma=
r 2, 2017 at 12:51 AM, Alex Jordan <span dir=3D"ltr">&lt;<a href=3D"mailto:=
alex@strugee.net" target=3D"_blank">alex@strugee.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">Heya!<br>
<br>
A widely deployed way to do two-factor authentication is<br>
TOTP. However, when used with an Android device Google Accounts have a<br>
really nice flow where Google will send a push notification to the<br>
Android device, which will then prompt the user with a &quot;yes/no&quot;<b=
r>
question as to whether they were trying to log in or not. From a UX<br>
perspective this is much nicer than opening an app, manually typing in<br>
a code, etc.<br>
<br>
With WebPush core having been just ratified as RFC 8030, the time<br>
seems ripe for standardizing an authentication scheme like described<br>
above.<br>
<br>
I have two questions:<br>
<br>
1. Is there interest in creating such a standard at the IETF?<br>
<br>
2. If there is, where would be the best place to do that work? I&#39;m<br>
relatively new to the IETF - I poked around Datatracker&#39;s list of<br>
Working Groups and there didn&#39;t seem to be one that really fit that<br>
well. Did I miss something? Or should this go through the IETF<br>
individual submission track?<br>
<br>
Please CC me on replies; I&#39;m not subscribed.<br></blockquote><div><br><=
/div><div><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8Bi=
 am interested and have developed several protocols of this type using JSON=
. My work provides prior art back to 2010 at the very least.</div><div clas=
s=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail=
_default" style=3D"font-size:small">What we are discussing goes beyond two =
factor auth. If you have a cell phone with a device specific signature key,=
 it can sign the response which means that you automatically collect up a n=
on repudiable audit log of the user&#39;s actions. This is beyond anything =
possible with OTP number sequences or USB dongles.</div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small">=E2=80=8B</div></div></div></div></div>

--001a11490cd8b22fbd054a0f8bf4--


From nobody Mon Mar  6 06:36:48 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A21851297C2 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 06:36:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IfXmvF5sTMoN for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 06:36:46 -0800 (PST)
Received: from nm8-vm1.bullet.mail.gq1.yahoo.com (nm8-vm1.bullet.mail.gq1.yahoo.com [98.136.218.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F5A11294A8 for <ietf@ietf.org>; Mon,  6 Mar 2017 06:36:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1488811005; bh=+Na3ZuQ/lQYNCmrEGuk1F4+yDBfJbH0vx7OQf9nSgl4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=KRRTIwpCTg+k7JKjwVU0EuoeUk6G/aUHWMBQyPMklER+KIQyMvZiawpysSJXWqHH3nMf3OrCAV0TrJsJGKYi0EVppoePYrDepxBAZBrWbINxktYKKM75/C3bUYVHzBQ9nPJLdQo+l7pd7BuEwmQq0zht9L5fcJGfC1wNmYd10OSUXQwtB3c0MdVjPKHTVexC5BFk31iy75XUGYO0BdJ36JBk8g/H6gEkngW7PYy0DqlrzdsRXNFKKwb1UNNl7fCLtg14uhy2Yszfs9DxQ9CttuQwbWReVrmvPP3imkb50Exu7/flDIvovq9VnWehw+hOgJJbECmv5vImesKMo2k5nA==
Received: from [98.137.12.188] by nm8.bullet.mail.gq1.yahoo.com with NNFMP; 06 Mar 2017 14:36:45 -0000
Received: from [98.137.12.214] by tm9.bullet.mail.gq1.yahoo.com with NNFMP; 06 Mar 2017 14:36:45 -0000
Received: from [127.0.0.1] by omp1022.mail.gq1.yahoo.com with NNFMP; 06 Mar 2017 14:36:45 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 694901.9540.bm@omp1022.mail.gq1.yahoo.com
X-YMail-OSG: fZKf2GsVM1nXcwVYd0X0TJGgYNrz5vJqYNLQFc9kmpBQvnFQn9Fbq7269HiwsIZ 5m3VxKQ9Wkxh16T6TAnaZnEkraKTFUwe91SgG7HUIXA7bGC1mx23TOzribLW1lq_4MymYfkRheQd bqpTjuXJ3WFOH7DcR_V0a4HBgKcOQ_keWVviC0JO_IqONHjYqE5ma6zQnkZUsr_vORaIgx_ha4R9 iKZKg6XHz_1D2UEFJp12hgZYhdLnX_U7jKpowp2Le_81HlL4aQiJ5s8hkHVyzewrH95dQQgIDxFr QIUYEL10t9GujeYIJYVMRL7XZvStDsbEdFM1bFqSsXwxFL0wVetUbQiGv9mLp5xuaJKqBVSfMjqv 8vwztbWDmKs_bqf5zHWhBC2mKVcc6KIbIL_37jmLC6iOL6rhjAwhK6hb1OonCZiqDQ6lRbNhNdpB dRLydmt6Vy8aiT15e0eTJ303gS1jSxpA555NISAYZ3BYzOOy8uXttdu57c08qEnEkuKzOkwn8Pd. VCF.NKMFcXVRz0leeM6hM66N9P2M2pUEbxc1aNQ--
Received: from jws300030.mail.gq1.yahoo.com by sendmailws108.mail.gq1.yahoo.com; Mon, 06 Mar 2017 14:36:45 +0000; 1488811005.201
Date: Mon, 6 Mar 2017 14:36:44 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: Sankalp Bagaria <sankalp@cdac.in>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <1569729034.3345578.1488811004912@mail.yahoo.com>
In-Reply-To: <77303779.6635.1488791115274.JavaMail.open-xchange@webmail.cdac.in>
References: <mailman.33.1488744007.31098.ietf@ietf.org> <77303779.6635.1488791115274.JavaMail.open-xchange@webmail.cdac.in>
Subject: Re: Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_3345577_1337389354.1488811004907"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/55MVPbLdMuC2jZypWMKeEvbh8yQ>
Cc: Harish Chowdhary <harish@nixi.in>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 14:36:47 -0000

------=_Part_3345577_1337389354.1488811004907
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Sankalp,
I am starting a private discussion with some of us who have been working to=
 build IETF capacity in India.

I am copying some of the people involved. =C2=A0 There are quite a few IETF=
ers in Bangalore. =C2=A0 Please start the discussion and we will be able to=
 guide you.
Please drop the ietf@ietf.org email list from the email chain.=C2=A0Thanks,
Nalini ElkinsInside Products, Inc.www.insidethestack.com(831) 659-8360

      From: Sankalp Bagaria <sankalp@cdac.in>
 To: ietf@ietf.org=20
 Sent: Monday, March 6, 2017 1:05 AM
 Subject: Re: Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh
  =20
   Hello,   =C2=A0   We are working on TLS and related fields for last one =
and   half year in Bangalore, India. We can benefit from a little   guidanc=
e. Can you tell us who is the mentor for India ?   =C2=A0   Thanks and Rega=
rds,   Sankalp Bagaria.  =20
On March 6, 2017 at 1:30 AM ietf-request@ietf.org wrote:=20
> Send ietf mailing list submissions to=20
> ietf@ietf.org=20
>=20
> To subscribe or unsubscribe via the World Wide Web, visit=20
> https://www.ietf.org/mailman/listinfo/ietf=20
> or, via email, send a message with subject or body 'help' to=20
> ietf-request@ietf.org=20
>=20
> You can reach the person managing the list at=20
> ietf-owner@ietf.org=20
>=20
> When replying, please edit your Subject line so it is more specific=20
> than "Re: Contents of ietf digest..."=20
>=20
>=20
> Today's Topics:=20
>=20
> 1. Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh=20
> (nalini.elkins@insidethestack.com)=20
>=20
>=20
> ----------------------------------------------------------------------=20
>=20
> Message: 1=20
> Date: Sun, 5 Mar 2017 12:51:16 +0000 (UTC)=20
> From: <nalini.elkins@insidethestack.com>=20
> To: IETF-Discussion Discussion <ietf@ietf.org>=20
> Cc: Amelia Yeo <yeo@isoc.org>=20
> Subject: Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh=20
> Message-ID: <1033583681.2631578.1488718276235@mail.yahoo.com>=20
> Content-Type: text/plain; charset=3DUTF-8=20
>=20
> All,=20
>=20
> Please contact Amelia Yao (copied) if you are able to help with this. ISO=
C needs two remote mentors to help with an ISOC project to build IETF capac=
ity in Sri Lanka, Pakistan and Bangladesh. It will run from May to December=
 and they will need about 2 mentors per country. So, they need 6 mentors al=
l together.=20
>=20
> The first mentor is to spend 1 hour per month talking to people who are f=
ollowing email lists on how to contribute to email lists, what to do, what =
not to do, motivate them to contribute to the list, answer their questions =
etc. ISOC needs a short report what people are following, who are attending=
 the calls, quantity of post and, quality of post. They will provide a volu=
nteer to help do the report.=20
>=20
> The second mentor will be to help the people that show potential to write=
 drafts with their draft writing. ISOC doesn't know which area they will be=
 interested in and, will have to play it by ear when these people surface o=
ut. So, they may be looking for more than one mentor here. The deliverable =
is by November for IETF 100 Singapore. Again, a short report has to be writ=
ten out monthly about people being mentored, what area, the progress, the n=
umber of drafts and quality etc. ISOC will provide a volunteer to help with=
 the reporting.=20
>=20
> The reason behind the monitoring is that ISOC needs to report monthly on =
progress and also they are offering 2 fellowships per country for IETF Sing=
apore.=20
>=20
> The report written will feed into a bigger report on work being carried o=
ut in the country and they will be selecting the cream of the elist contrib=
utors/draft writers to attend IETF100.=20
>=20
> Thanks,=20
>=20
> Nalini Elkins=20
>=20
> IETF Mentoring Program=20
>=20
> Inside Products, Inc.www.insidethestack.com=20
> (831) 659-8360=20
>=20
>=20
>=20
> ------------------------------=20
>=20
> Subject: Digest Footer=20
>=20
> _______________________________________________=20
> ietf mailing list=20
> ietf@ietf.org=20
> https://www.ietf.org/mailman/listinfo/ietf=20
>=20
>=20
> ------------------------------=20
>=20
> End of ietf Digest, Vol 106, Issue 14=20
> ************************************* =20
---------------------------------------------------------------------------=
----------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:=20
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
---------------------------------------------------------------------------=
----------------------------------------------------

  =20
------=_Part_3345577_1337389354.1488811004907
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id=3D"yui_3_16_=
0_ym19_1_1488810772133_7011"><span>Sankalp,</span></div><div id=3D"yui_3_16=
_0_ym19_1_1488810772133_7011"><span><br></span></div><div id=3D"yui_3_16_0_=
ym19_1_1488810772133_7011">I am starting a private discussion with some of =
us who have been working to build IETF capacity in India.<br></div><div></d=
iv><div id=3D"yui_3_16_0_ym19_1_1488810772133_7179"><br></div><div id=3D"yu=
i_3_16_0_ym19_1_1488810772133_7180" dir=3D"ltr">I am copying some of the pe=
ople involved. &nbsp; There are quite a few IETFers in Bangalore. &nbsp; Pl=
ease start the discussion and we will be able to guide you.</div><div id=3D=
"yui_3_16_0_ym19_1_1488810772133_7180" dir=3D"ltr"><br></div><div id=3D"yui=
_3_16_0_ym19_1_1488810772133_7180" dir=3D"ltr">Please drop the ietf@ietf.or=
g email list from the email chain.</div><div id=3D"yui_3_16_0_ym19_1_148881=
0772133_7181">&nbsp;</div><div class=3D"signature" id=3D"yui_3_16_0_ym19_1_=
1488810772133_7182">Thanks,<div id=3D"yui_3_16_0_ym19_1_1488810772133_7183"=
><br></div><div id=3D"yui_3_16_0_ym19_1_1488810772133_7199">Nalini Elkins</=
div><div id=3D"yui_3_16_0_ym19_1_1488810772133_7200">Inside Products, Inc.<=
/div><div id=3D"yui_3_16_0_ym19_1_1488810772133_7251">www.insidethestack.co=
m</div><div id=3D"yui_3_16_0_ym19_1_1488810772133_7252">(831) 659-8360</div=
></div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_1488810772133_7=
253"><br><br></div><div class=3D"yahoo_quoted" style=3D"display: block;">  =
<div style=3D"font-family: HelveticaNeue-Light, Helvetica Neue Light, Helve=
tica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> =
<div style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, sans-serif; font-size: 16px;"> <div dir=3D"ltr"> <font size=
=3D"2" face=3D"Arial"> <hr size=3D"1"> <b><span style=3D"font-weight:bold;"=
>From:</span></b> Sankalp Bagaria &lt;sankalp@cdac.in&gt;<br> <b><span styl=
e=3D"font-weight: bold;">To:</span></b> ietf@ietf.org <br> <b><span style=
=3D"font-weight: bold;">Sent:</span></b> Monday, March 6, 2017 1:05 AM<br> =
<b><span style=3D"font-weight: bold;">Subject:</span></b> Re: Remote Mentor=
s Needed for Sri Lanka, Pakistan and Bangladesh<br> </font> </div> <div cla=
ss=3D"y_msg_container"><br><div id=3D"yiv6892497623">
   =20
 <div>
=20
=20
  <div>
   Hello,
  </div>=20
  <div>
   &nbsp;
  </div>=20
  <div>
   We are working on TLS and related fields for last one and
  </div>=20
  <div>
   half year in Bangalore, India. We can benefit from a little
  </div>=20
  <div>
   guidance. Can you tell us who is the mentor for India ?
  </div>=20
  <div>
   &nbsp;
  </div>=20
  <div>
   Thanks and Regards,
  </div>=20
  <div>
   Sankalp Bagaria.
  </div>=20
  <div>
   <br>On March 6, 2017 at 1:30 AM ietf-request@ietf.org wrote:
   <br>&gt; Send ietf mailing list submissions to
   <br>&gt; ietf@ietf.org
   <br>&gt;=20
   <br>&gt; To subscribe or unsubscribe via the World Wide Web, visit
   <br>&gt; https://www.ietf.org/mailman/listinfo/ietf
   <br>&gt; or, via email, send a message with subject or body 'help' to
   <br>&gt; ietf-request@ietf.org
   <br>&gt;=20
   <br>&gt; You can reach the person managing the list at
   <br>&gt; ietf-owner@ietf.org
   <br>&gt;=20
   <br>&gt; When replying, please edit your Subject line so it is more spec=
ific
   <br>&gt; than "Re: Contents of ietf digest..."
   <br>&gt;=20
   <br>&gt;=20
   <br>&gt; Today's Topics:
   <br>&gt;=20
   <br>&gt; 1. Remote Mentors Needed for Sri Lanka, Pakistan and Bangladesh
   <br>&gt; (nalini.elkins@insidethestack.com)
   <br>&gt;=20
   <br>&gt;=20
   <br>&gt; ---------------------------------------------------------------=
-------
   <br>&gt;=20
   <br>&gt; Message: 1
   <br>&gt; Date: Sun, 5 Mar 2017 12:51:16 +0000 (UTC)
   <br>&gt; From: &lt;nalini.elkins@insidethestack.com&gt;
   <br>&gt; To: IETF-Discussion Discussion &lt;ietf@ietf.org&gt;
   <br>&gt; Cc: Amelia Yeo &lt;yeo@isoc.org&gt;
   <br>&gt; Subject: Remote Mentors Needed for Sri Lanka, Pakistan and Bang=
ladesh
   <br>&gt; Message-ID: &lt;1033583681.2631578.1488718276235@mail.yahoo.com=
&gt;
   <br>&gt; Content-Type: text/plain; charset=3DUTF-8
   <br>&gt;=20
   <br>&gt; All,
   <br>&gt;=20
   <br>&gt; Please contact Amelia Yao (copied) if you are able to help with=
 this. ISOC needs two remote mentors to help with an ISOC project to build =
IETF capacity in Sri Lanka, Pakistan and Bangladesh. It will run from May t=
o December and they will need about 2 mentors per country. So, they need 6 =
mentors all together.
   <br>&gt;=20
   <br>&gt; The first mentor is to spend 1 hour per month talking to people=
 who are following email lists on how to contribute to email lists, what to=
 do, what not to do, motivate them to contribute to the list, answer their =
questions etc. ISOC needs a short report what people are following, who are=
 attending the calls, quantity of post and, quality of post. They will prov=
ide a volunteer to help do the report.=20
   <br>&gt;=20
   <br>&gt; The second mentor will be to help the people that show potentia=
l to write drafts with their draft writing. ISOC doesn't know which area th=
ey will be interested in and, will have to play it by ear when these people=
 surface out. So, they may be looking for more than one mentor here. The de=
liverable is by November for IETF 100 Singapore. Again, a short report has =
to be written out monthly about people being mentored, what area, the progr=
ess, the number of drafts and quality etc. ISOC will provide a volunteer to=
 help with the reporting.
   <br>&gt;=20
   <br>&gt; The reason behind the monitoring is that ISOC needs to report m=
onthly on progress and also they are offering 2 fellowships per country for=
 IETF Singapore.=20
   <br>&gt;=20
   <br>&gt; The report written will feed into a bigger report on work being=
 carried out in the country and they will be selecting the cream of the eli=
st contributors/draft writers to attend IETF100.
   <br>&gt;=20
   <br>&gt; Thanks,
   <br>&gt;=20
   <br>&gt; Nalini Elkins
   <br>&gt;=20
   <br>&gt; IETF Mentoring Program
   <br>&gt;=20
   <br>&gt; Inside Products, Inc.www.insidethestack.com
   <br>&gt; (831) 659-8360
   <br>&gt;=20
   <br>&gt;=20
   <br>&gt;=20
   <br>&gt; ------------------------------
   <br>&gt;=20
   <br>&gt; Subject: Digest Footer
   <br>&gt;=20
   <br>&gt; _______________________________________________
   <br>&gt; ietf mailing list
   <br>&gt; ietf@ietf.org
   <br>&gt; https://www.ietf.org/mailman/listinfo/ietf
   <br>&gt;=20
   <br>&gt;=20
   <br>&gt; ------------------------------
   <br>&gt;=20
   <br>&gt; End of ietf Digest, Vol 106, Issue 14
   <br>&gt; *************************************
  </div>
=20
<br>-----------------------------------------------------------------------=
--------------------------------------------------------
<br>[ C-DAC is on Social-Media too. Kindly follow us at:=20
<br>Facebook: https://www.facebook.com/CDACINDIA &amp; Twitter: @cdacindia =
]
<br>
<br>This e-mail is for the sole use of the intended recipient(s) and may
<br>contain confidential and privileged information. If you are not the
<br>intended recipient, please contact the sender by reply e-mail and destr=
oy
<br>all copies and the original message. Any unauthorized review, use,
<br>disclosure, dissemination, forwarding, printing or copying of this emai=
l
<br>is strictly prohibited and appropriate legal action will be taken.
<br>-----------------------------------------------------------------------=
--------------------------------------------------------
</div>
</div><br><br></div> </div> </div>  </div></div></body></html>
------=_Part_3345577_1337389354.1488811004907--


From nobody Mon Mar  6 08:25:35 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9102C129568; Mon,  6 Mar 2017 08:25:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Susan Hares <shares@ndzh.com>
To: <rtg-dir@ietf.org>
Subject: Review of draft-ietf-spring-segment-routing-msdc-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148881752958.15101.3565092696759250024.idtracker@ietfa.amsl.com>
Date: Mon, 06 Mar 2017 08:25:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/drp7ExEci585neLA5wXskP1l0yU>
Cc: draft-ietf-spring-segment-routing-msdc.all@ietf.org, spring@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 16:25:29 -0000

Reviewer: Susan Hares
Review result: Has Issues

The RTG-DIR has the categories:  minor concerns or major concerns
regarding "issues", I wil differentiate my issues by this quality. 
I also have editorial nits regardign under specified text. 

Major concerns: 
1) The security section is not sufficient for any review by the
Security area 

This draft depends on IDR WG draft (ietf-idr-bgp-prefix-sid) that
defines the BGP Segment attribute.  If this attribute is used with
IPv6, this simply gives more infromation about a link to a next. 
However, the combination of this information with the information
passed using draft-ietf-idr-bgpls-segment-routing-epe-09 that utilizes
BGP to pass BGP topologies in BGP - requires a better security
section.  BGP-LS was described to be an "information gathering"
function handled by a few routers on the edge of the network to obtain
link-state topology information.  The BGP peers would carry this
information in a separate informational stream.  With this constraint,
it was approved by the IESG.   
draft-ietf-idr-bgpls-segment-routing-epe  expands the initial concept
of BGP-LS from "information gathering" to a full-routing scheme of BGP
within BGP for data centers and for data center interconnection to the
network.   This extension takes it out of the approved range of the
BGP-LS.  Therefore, the security sections in both the IDR WG drafts
and this draft need to describe the new threat scenarios and describe
threat mitigation strategies for deployments.  

In addition, the information by BGP-LS
(draft-ietf-idr-bgpls-segment-routing-epe) or in draft-ietf-bgp-sid
may have privacy issues - so these need to be described the security
section. 

2) through-out the text you use words such as "ebgp3107" or BGP 3107
updates"

This phrase is inaccurate.  The base RFC3107 support will not provide
BGP-Prefix support (as supported in bgp-idr-bgp-prefix.   Some texts
goes on to clarify the addition of the BGP SID Prefix attribute.  It
would be better to invent a new phrase or term.  

In section 8.1, the authors state:
"The Prefix Segement is a lightweight extension to the BGP Labelled
Unicast".  As noted in my #1 major concern, this "hand-waving"
description either needs to be refined to be accurate.  If the MPLS
usage only uses the BGP-Prefix label and does not extend to the
Egress, it is simplier.  However, it is not clear that is what section
8.1 is about.   If 8.1 includes the
draft-ietf-idr-bgpls-segment-routing-epe, then BGP-LS addition does
have a number of prefixes and rules.   The trade-off between BGP-LS +
BGP-LS SID (draft-ietf-idr-bgp-sid) handling + BGP LS egress peer
engineering draft (draft-ietf-idr-bgp-segment-routing-epe) and a
signalling protocol is more complex than the hand-wave.  It may be the
right choice based on current implementations and management issues,
but these need to be laid specifically. 

3) Why are you defining 2-byte Private Use AS when there are plenty of
4-Byte Private Use AS (p. 5). 

This usage increases the confusion regarding 2-byte/4-byte ASN.  IDR
specifically worked on 4 byte ASN. 

Minor concerns  
1) It is not clear what happens in section 4.2.2 and figure 3-5

What happens if the traffic goes to node 3 instead of node 4 on the
ECMP path? 
What happens if the traffic goes to node 8 instead of node 7 on the
ECMP Path? 

Is there something missing in the stroy? 

2) section 4.3 - IBGP Labeled Unicast. 

The phrase "iBGP3107 reflection with nhop-self" needs to be explicitly
spelled out as IBGP Route-Reflection with next-hop self.  If that is
not what the authors mean, then it needs to be further spelled out. 
It is unclear where the central IBGP nodes are that share fully the
information learned from the three clusters. (nodes:5-8 cluster 1,
nodes 3-4 cluster 2, nodes 9-10 cluster 3).  

This section has hints of a solution, but it is miss a great deal. 
Please upgrade to specific solution.  A diagram might help. 

3) Load Sharing hints (Section 7.1) 

Elephant flow and mice flows are good descriptions.  Flowlets and VL2
should either warrant a 1 sentence explanation that actually describes
these features in a 22 page draft, or be removed.  

4)  The lack of a manageability or operations section (TBD in version
-02) - concerns me.  The operational issues may be well known to the
data centers and devices manufacturers who have implement this
specification, but this is an interoperability specification for IETF.
 Some manageabilty comments should be included or a BCP pointed to. 

Editorial issues: 

#1 - The following 4 abbrevitions need to be initially expanded when
first used:  CLOs (p.3),  SRGB(p.6), flowlets (p. 14), and VL2 (p.
14). 

#2 - page 7, section 4.2 last paragraph 
Old/: assuming the IP Addresses, AS and label-index allocation
previously described, the"
New/: assuming the IP address with the AS and label-index allocation
previously described, the" 
[Comma is optional]

#3 - page 14, section 7.1 paragraph 4,  /(e.g. spine switch Node1)/  -
by the diagram it should be node 5-8 or an error.  Please check the
number 

#4 - page 17, section 8.2 paragraph 2. 

Old/
This is easily accomplished by encapsulating the trafffic either 
directly at the host or the source ToR node by pushing the BGP-
Prefix-SID of the destination ToR for intra-DC traffic, or border 
node for inter-DC or DC-to-outside-world traffic./

New/
This is easily accomplished by encapsulating the trafffic either 
directly at the host or the source ToR node  by pushing  the BGP-
Prefix-SID of the destination ToR for intra-DC traffic, or
the BGP-Prefix-SID for the the border node for inter-DC or
DC-to-outside-world traffic./
 
If this is not the correct logic, then you can reword this further. 
I read it 4 or 5 times. 

#5 - Adding a diagram to section 4.3 might help your description. 



From nobody Mon Mar  6 08:27:31 2017
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 74E741297CE for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 08:27:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0yquRdZnto2I for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 08:27:29 -0800 (PST)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C860E129540 for <ietf@ietf.org>; Mon,  6 Mar 2017 08:27:28 -0800 (PST)
Received: by mail-yw0-x232.google.com with SMTP id p77so124374794ywg.1 for <ietf@ietf.org>; Mon, 06 Mar 2017 08:27:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:from:date:message-id:subject:to; bh=MWMBfFWkgVbw5+mI44Fgw2JGEB/EonQRudsa5sxXFds=; b=OajLqIFqh3DhCGJkRlzqsBoZ3cRt8Tn+7gzotHZ4kgmXuLpYHl0bHiB7c33LRPs9Pu Y2kCLTxSGivjJsExOiNk3lTYFO9uIGnQOLb6lz2rAOCKVYvQYcyBKEkXgoTgC2lNiBIa ygqTbsl3j0syRDR119WZ60BAnecabqHAZMtlltT7Dm/yJvQzmdKFezcuPLOeq4mxjMzH h4HQU64Zae8YHa5NbffnsoM9Hv195Tg7XdACn+jY5/EYeCL6nsmMQKPTTcVt5r8MmRyy Xvd8SVk+nhVeRW1rqdxHMCVl/MROjLnwfw/rzjkPEUxP4PiTamEsV2+Siyo/D07iXOZf /H/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=MWMBfFWkgVbw5+mI44Fgw2JGEB/EonQRudsa5sxXFds=; b=OkU4hKN7aGbqRZCemsk4e9PQfhGoo5Sk/W6BHSY+PnGZBAiJHI8eNNLwCJP0lZDOj9 +PlxgEpvlvu/gk/SeriLBxiDM9bYS18+R1OcX5Fcv7dqBxGSooXO0CAM+QRxN7KOfCnL P9c6j7sCjIo8YBp1YTvgB0lr9Q4/LRU8qddLJeq4SGUq7uI/NdU0+x6CFgZk+KUyeH/c AFm00S/neowp3e59G0+7/1BMvriEBLt0FK0EdgtCTtHv5PZPvRRzahuUBEhzSQDAp3L5 nYmybpYW3GIEIHqx9ff+1E0eMFBVJnzKhZj1prVLBvMAkEa2SdMWRjsyj/t19NcX30nU 0hqA==
X-Gm-Message-State: AMke39nBfLU8i1aww892nHXYDWBz0bFxveqs/aZfqcNL7sOsUsNtW0Dk97Q5MgkCMF7AcqWl8dboSjtgp27yJw==
X-Received: by 10.129.172.25 with SMTP id k25mr11766366ywh.165.1488817647873;  Mon, 06 Mar 2017 08:27:27 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Mon, 6 Mar 2017 08:27:27 -0800 (PST)
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 6 Mar 2017 11:27:27 -0500
X-Google-Sender-Auth: H3axGI5X-E2tDdkuc8haw503GFM
Message-ID: <CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com>
Subject: More haste, less speed.
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c1badfc097287054a125fab
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2dz58rAAm7-r07JvhvP3W7XantI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 16:27:30 -0000

--94eb2c1badfc097287054a125fab
Content-Type: text/plain; charset=UTF-8

Specifications are moving through IETF faster than ever. Rarely is the
question asked, is this actually a good thing.

The specific reason for raising this topic is a complaint on the DNSops
list about large public resolvers failing to support DPRIV. But that is not
the only example of what I see as an anti-pattern for standards development.

1) A group identifies a security need

2) Asserting that the need is urgent and the very most important thing is
speed, a draft is cobbled together that meets the functional requirements
the group has identified.

3) Deployment stakeholders point out the practical problems they would face
implementing the draft in the current form.

4) The objections are brushed aside because of the urgent need for speed.

5) A couple of years later the draft is published as an RFC

6) A couple of years later, it is noticed than none of the essential
stakeholders have deployed.

7) Attacks on the stakeholders' lack of interest in security, gaslighting
of the individuals who raised the blocking deployment issues.

8) Further attempts to address the issue are blocked because 'what needs to
happen' is deployment of 'the standard'

9) Those people who point out that this behavior is problematic are cast
out from the tribe.

This isn't just one isolated incident. It is now a firmly established
pattern. I have seen it happen on three separate projects in the DNS area
alone. First with DNSSEC, then with DANE and now with DPRIV. And there are
real costs.

DNSSEC was deployed in .com for almost a decade late because of the refusal
to fix the NXT record issue. As a result, we lost a critical window where
deployment would have been a lot easier than it became.

DANE conflates publication of security policy with public key validation
and distribution.

And now we have DPRIV which is built with no regard for the architectural
constraints of running the large public DNS resolvers whose adoption is
essential for success.

Every time I point out that the same group of individuals are engaging in
the same behavior that caused their last proposal to fail, I am accused of
trying to re-fight old battles and what we all need to do is to ram this
next RFC through the process as fast as we possibly can because this time
we really need to do it fast.


What concerns me here is not so much the waste of time but the fact that as
long as there is a purported standard meeting some need, its existence and
failure to achieve adopted blocks attempts to solve the problem in ways
that could be acceptable to the deployment stakeholders.

So what I propose is a mechanism to formalize the raising of deployment
objections. The basic idea being that is a group decides to behave this way
and the IESG decides to let them, the fact that their proposed solution
fails to meet what key stakeholders assert are show stopper deployment
issues is noted. If the WG then produces a specification that fails to
achieve deployment, the existence of the objections can then be taken into
account when considering chartering a new group.

--94eb2c1badfc097287054a125fab
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Spe=
cifications are moving through IETF faster than ever. Rarely is the questio=
n asked, is this actually a good thing.</div><div class=3D"gmail_default" s=
tyle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">The specific reason for raising this topic is a complaint on=
 the DNSops list about large public resolvers failing to support DPRIV. But=
 that is not the only example of what I see as an anti-pattern for standard=
s development.</div><div class=3D"gmail_default" style=3D"font-size:small">=
<br></div><div class=3D"gmail_default" style=3D"font-size:small">1) A group=
 identifies a security need</div><div class=3D"gmail_default" style=3D"font=
-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:smal=
l">2) Asserting that the need is urgent and the very most important thing i=
s speed, a draft is cobbled together that meets the functional requirements=
 the group has identified.</div><div class=3D"gmail_default" style=3D"font-=
size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small=
">3) Deployment stakeholders point out the practical problems they would fa=
ce implementing the draft in the current form.</div><div class=3D"gmail_def=
ault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" styl=
e=3D"font-size:small">4) The objections are brushed aside because of the ur=
gent need for speed.</div><div class=3D"gmail_default" style=3D"font-size:s=
mall"><br></div><div class=3D"gmail_default" style=3D"font-size:small">5) A=
 couple of years later the draft is published as an RFC</div><div class=3D"=
gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-size:small">6) A couple of years later, it is noticed th=
an none of the essential stakeholders have deployed.</div><div class=3D"gma=
il_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default=
" style=3D"font-size:small">7) Attacks on the stakeholders&#39; lack of int=
erest in security, gaslighting of the individuals who raised the blocking d=
eployment issues.</div><div class=3D"gmail_default" style=3D"font-size:smal=
l"><br></div><div class=3D"gmail_default" style=3D"font-size:small">8) Furt=
her attempts to address the issue are blocked because &#39;what needs to ha=
ppen&#39; is deployment of &#39;the standard&#39;</div><div class=3D"gmail_=
default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-size:small">9) Those people who point out that this behavior i=
s problematic are cast out from the tribe.</div><div class=3D"gmail_default=
" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D=
"font-size:small">This isn&#39;t just one isolated incident. It is now a fi=
rmly established pattern. I have seen it happen on three separate projects =
in the DNS area alone. First with DNSSEC, then with DANE and now with DPRIV=
. And there are real costs.</div><div class=3D"gmail_default" style=3D"font=
-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:smal=
l">DNSSEC was deployed in .com for almost a decade late because of the refu=
sal to fix the NXT record issue. As a result, we lost a critical window whe=
re deployment would have been a lot easier than it became.</div><div class=
=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_=
default" style=3D"font-size:small">DANE conflates publication of security p=
olicy with public key validation and distribution.=C2=A0</div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">And now we have DPRIV which is built with n=
o regard for the architectural constraints of running the large public DNS =
resolvers whose adoption is essential for success.</div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small">Every time I point out that the same group of ind=
ividuals are engaging in the same behavior that caused their last proposal =
to fail, I am accused of trying to re-fight old battles and what we all nee=
d to do is to ram this next RFC through the process as fast as we possibly =
can because this time we really need to do it fast.</div><div class=3D"gmai=
l_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default"=
 style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"=
font-size:small">What concerns me here is not so much the waste of time but=
 the fact that as long as there is a purported standard meeting some need, =
its existence and failure to achieve adopted blocks attempts to solve the p=
roblem in ways that could be acceptable to the deployment stakeholders.</di=
v><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div cla=
ss=3D"gmail_default" style=3D"font-size:small">So what I propose is a mecha=
nism to formalize the raising of deployment objections. The basic idea bein=
g that is a group decides to behave this way and the IESG decides to let th=
em, the fact that their proposed solution fails to meet what key stakeholde=
rs assert are show stopper deployment issues is noted. If the WG then produ=
ces a specification that fails to achieve deployment, the existence of the =
objections can then be taken into account when considering chartering a new=
 group.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></d=
iv></div>

--94eb2c1badfc097287054a125fab--


From nobody Mon Mar  6 08:29:56 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD74129623; Mon,  6 Mar 2017 08:29:55 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-curdle-cms-chacha20-poly1305-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148881779563.15035.3355290317294020544.idtracker@ietfa.amsl.com>
Date: Mon, 06 Mar 2017 08:29:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/09s3jyy5yKTTbaMAq4dIJBB-IPo>
Cc: curdle@ietf.org, draft-ietf-curdle-cms-chacha20-poly1305.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 16:29:55 -0000

Reviewer: Matthew Miller
Review result: Ready

[ re-posting to get it onto the mailing list archives; some bugs
prevented it the first time ]

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq >.

Document: draft-ietf-curdle-cms-chacha20-poly1305-04
Reviewer: Matthew A. Miller
Review Date: 2016-12-16
IETF LC End Date: 2016-12-16
IESG Telechat date: N/A

Summary:

Ready to be published as a Proposed Standards document.

Major issues:  NONE

Minor issues:  NONE

Nits/editorial comments:  NONE

Non-issues:

Nits is reporting a downref to RFC 7539 (ChaCha20 and Poly1035).
However it is standard practice for cryptographic algorithm
documents to be Informational rather than Standards Track,
therefore I don't think there's a real concern here.

Nits is also reporting downrefs for X680 and X690, but I believe
these are acceptable as they define ASN.1.


From nobody Mon Mar  6 08:32:37 2017
Return-Path: <eng.khaled.omar@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 494EC129623 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 08:32:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1qZQBKDE9tU for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 08:32:34 -0800 (PST)
Received: from SNT004-OMC3S43.hotmail.com (snt004-omc3s43.hotmail.com [65.54.51.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7107129871 for <ietf@ietf.org>; Mon,  6 Mar 2017 08:32:33 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com ([65.55.90.136]) by SNT004-OMC3S43.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 6 Mar 2017 08:32:33 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=L6NFa1+a/+34+8CLNagU131m9YgFpN/K6qFwbwez23Q=; b=aQ88AqBMTcud/euWWGZ39PXvWEitTQ4g5vZ0ixiBLmYCVepCHzn6clR8yuA7YHspUMiWoi6m1XafRmJYJegRLOhob6pIyZlgaL2hKgVabGhsWCDcOGKiKJImXf5r8PFXslMYMXziaS/grVcdQVNDOGN221g0NG0bxylUP186VkHGpfYZvVcWoOQpR3VDxz9NxY2JLJPrrqGoNRoFPndF1wnX6Sc0PCss6gZhT4SGBHlFPteDq5MPUIG72Bztb3HuWf2fRXHGASUlTBO0hGhcInAjpJgJFF/WWCbSG1brVMJnlD6b2aWpv635S9KzqARCACPNSS44RJKuHk4I1XNDEA==
Received: from VE1EUR01FT022.eop-EUR01.prod.protection.outlook.com (10.152.2.56) by VE1EUR01HT245.eop-EUR01.prod.protection.outlook.com (10.152.2.185) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.11; Mon, 6 Mar 2017 16:32:31 +0000
Received: from HE1PR04MB1449.eurprd04.prod.outlook.com (10.152.2.57) by VE1EUR01FT022.mail.protection.outlook.com (10.152.2.233) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.11 via Frontend Transport; Mon, 6 Mar 2017 16:32:31 +0000
Received: from HE1PR04MB1449.eurprd04.prod.outlook.com ([10.163.176.11]) by HE1PR04MB1449.eurprd04.prod.outlook.com ([10.163.176.11]) with mapi id 15.01.0947.018; Mon, 6 Mar 2017 16:32:31 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Adding IPv10 to the IETF 98 Agenda.
Thread-Topic: Adding IPv10 to the IETF 98 Agenda.
Thread-Index: AdKWlqLdtyszclGLR5SGi7x/Xokz2w==
Date: Mon, 6 Mar 2017 16:32:31 +0000
Message-ID: <HE1PR04MB14494F944755BE4630D615D7BD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:90DB938E5E03958198EED6D2733A99495D7C6DF6CB070EF0D7234654C2AFD429; UpperCasedChecksum:F3AD4A335F3D0BFF0AC46B019B7C3BAD5BAD3DC2EDE8E7052E1168CAA42BF0EA; SizeAsReceived:7538; Count:36
x-tmn: [x3fVXmEwoaAxm1NR0/wPu03iDD6jeMsV]
x-incomingheadercount: 36
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; VE1EUR01HT245; 5:xFQF6xfpeSNNRhKtxgIS7w5B0F4yNzQLWaJZWBHmrznoHVBbtryBBSQ8jyTwJRfNWSng04pbS90Gd3v7KeT/Oc4YoqgofegzqNYzaD+bS7ttBEWeCV4SGEo8YBzw9AsKkPTku4xaXwvK6fQRaqH4nA==; 24:SAkBRMRcTjC8xblbI8raTaIR34kFoca7I8i9cAHYRZjEyR3rhCn2uzyDXwrc4csoRwjgK7RS+HTwfWH2L5BRX23+lO+yyS9esKqI1v3PcNg=; 7:CK2YWf5X7y6AntyPcYa+td6XUKiviMS5I+q/lyCX+/sPoWFUMCTeOEJxR3JRqka5RZ73dwWiiuOGLQRv1OsNTKex4cdzP6EooKUbXwW8f1sifUHgtZspww2zIdneE7FlvRx9qfQocnZN7xUwxeMB277Ns7jcnytZF1f/IsolnGvtFjfoxCQxw1YrTgOaOf0lf5qeBequVwnA5HEGk2B+dMyLR5tl5vAU3CtivZSgjyiWb6CaGnvwe7CHRl59ezPK9YBCY3PAnMIoKpmj/byY5DI97bLyRTRdQjNPjR6VP3s3xF8zTHLbv1BX8Gb53SuY
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900016); DIR:OUT; SFP:1102; SCL:1; SRVR:VE1EUR01HT245; H:HE1PR04MB1449.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 11cab895-4c51-4959-8d25-08d464ae62e7
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(1601125254)(1603101448)(1701031045); SRVR:VE1EUR01HT245; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:VE1EUR01HT245; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR01HT245; 
x-forefront-prvs: 0238AEEDB0
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR04MB14494F944755BE4630D615D7BD2C0HE1PR04MB1449eurp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2017 16:32:31.1886 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR01HT245
X-OriginalArrivalTime: 06 Mar 2017 16:32:33.0122 (UTC) FILETIME=[418E0420:01D29697]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n6sabWKkpMH01d7vIizdUWIFsiw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 16:32:36 -0000

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

Hi all,

I've made a request to add the IPv10 I-D to the IETF 98 agenda to be discus=
sed during that meeting but as usual I got no response, does this means tha=
t the discussion stopped at this point or there is something that can be do=
ne?

If someone can provide me with details regarding this issue and how and for=
 whom to make that request it will be appreciated.

Best regards,

Khaled

--_000_HE1PR04MB14494F944755BE4630D615D7BD2C0HE1PR04MB1449eurp_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I&#8217;ve made a request to add the IPv10 I-D to th=
e IETF 98 agenda to be discussed during that meeting but as usual I got no =
response, does this means that the discussion stopped at this point or ther=
e is something that can be done?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If someone can provide me with details regarding thi=
s issue and how and for whom to make that request it will be appreciated.<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Khaled<o:p></o:p></p>
</div>
</body>
</html>

--_000_HE1PR04MB14494F944755BE4630D615D7BD2C0HE1PR04MB1449eurp_--


From nobody Mon Mar  6 08:37:03 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E728D12987A; Mon,  6 Mar 2017 08:36:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-lisp-type-iana-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148881821294.15051.6686658710973159407.idtracker@ietfa.amsl.com>
Date: Mon, 06 Mar 2017 08:36:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kUUthByvCk1TB9JwFfBklSVZ6gI>
Cc: draft-ietf-lisp-type-iana.all@ietf.org, ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 16:36:53 -0000

Reviewer: Matthew Miller
Review result: Ready

[ re-posting to get it onto the mailing list archives; some bugs
prevented it the first time ]

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-lisp-type-iana-04
Reviewer: Matthew Miller
Review Date: 2017-01-17
IETF LC End Date: 2017-01-17
IESG Telechat date: 2017-02-02

Summary:

This document is ready to publish as an Experimental document.

Major issues: NONE

Minor issues: NONE

Nits/editorial comments: NONE


From nobody Mon Mar  6 08:39:44 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE9312986C; Mon,  6 Mar 2017 08:39:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <secdir@ietf.org>
Subject: Review of draft-harkins-owe-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148881837990.15039.4330298821291699213.idtracker@ietfa.amsl.com>
Date: Mon, 06 Mar 2017 08:39:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0E6aleg9xy7PkaCYYZTrNpQYh-4>
Cc: ietf@ietf.org, draft-harkins-owe.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 16:39:40 -0000

Reviewer: Matthew Miller
Review result: Has Nits

[ re-posting old review to get it onto the mailing list archives; some
bugs prevented it the first time ]

I have reviewed this document as part of the security directorate's 
ongoing effort to review all IETF documents being processed by the 
IESG.  These comments were written primarily for the benefit of the 
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

Document: draft-harkins-owe-05
Reviewer: Matthew A. Miller
Review Date: 2016-01-13
IETF LC End Date: 2016-01-13
IESG Telechat date: N/A

Summary:

This document describes an extension to 802.11 to perform
opportunistic unauthenticated encryption of wireless connections.

This document is ready, but has nits that ought to be addressed
before publication.

Major issues: NONE

Minor issues:

In Section 4.3 "OWE Association", the fifth paragraph states that a
client "MUST include a Diffie-Hellman Parameter element ...", yet
further in the the same paragraph it states that if PMK Caching is
not performed, then the same element MUST be included.  This seems
redundant, or that there are cases where OWE can be used but the
Diffie-Hellman Parameter element is not required.

This might be more obvious to one that has read the 802.11 suite
(which I admittedly have not), but I think it would be beneficial if
this document could better clarify when the Diffie-Hellman Element
parameter is needed.  For instance, if it is always expected to be
present whenever OWE is desired, then removing the following
sentence would help:

    """
    If "PMK caching" (see Section 4.5) is not performed, it MUST also
    include a Diffie-Hellman Parameter element.
    """

Nits/editorial comments:

* Throughout, the spacing of "--" is consistent, but not expected;
there is never a leading space but there is always a trailing space.

* In Section 3. "802.11 Network Access", a quote is missing after
Open Authentication.


From nobody Mon Mar  6 08:41:31 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C51881298A5; Mon,  6 Mar 2017 08:41:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <secdir@ietf.org>
Subject: Review of draft-ietf-sidr-rpki-rtr-rfc6810-bis-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148881846080.15058.7367435968376657921.idtracker@ietfa.amsl.com>
Date: Mon, 06 Mar 2017 08:41:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wU8Xru_XUzpe9lZq0y6Hz6sF-o4>
Cc: draft-ietf-sidr-rpki-rtr-rfc6810-bis.all@ietf.org, ietf@ietf.org, sidr@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 16:41:01 -0000

Reviewer: Matthew Miller
Review result: Has Nits

[ re-posting old review to get it onto the mailing list archives; some
bugs prevented it the first time ]

I have reviewed this document as part of the security directorate's 
ongoing effort to review all IETF documents being processed by the 
IESG.  These comments were written primarily for the benefit of the 
security area directors.  Document editors and WG chairs should treat

these comments just like any other last call comments.

Document:
Reviewer: Matthew A. Miller
Review Date: 2017-02-14
IETF LC End Date: 2017-01-30
IESG Telechat date: 2017-02-16

Summary:

This document is ready for publication as a Proposed Standard, but
has
a minor concern that should be addressed.

This document describes a protocol for distributing RPKI information
to routers from trusted caches.

Major issues:  NONE

Minor issues:

* In Section 5.1. "Fields of a PDU", for the Flags: definition, it
states that:

    """
    The remaining bits in the flags field are reserved for future
use.
    In protocol version 1, they MUST be 0 on transmission and SHOULD
    be ignored on receipt.
    """

However, this seems backwards to me.  Would it seem safer that the
reserved flags "MUST be ignored on receipt".


Nits/editorial comments: NONE



From nobody Mon Mar  6 08:43:09 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC7912945A for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 08:43:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0VfB4rTOOec for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 08:43:06 -0800 (PST)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08BB3129891 for <ietf@ietf.org>; Mon,  6 Mar 2017 08:43:06 -0800 (PST)
Received: by mail-qk0-x22b.google.com with SMTP id y76so31489154qkb.0 for <ietf@ietf.org>; Mon, 06 Mar 2017 08:43:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=orlppNliu8M0qtDLjqe1tmmGT9po7KYftgxmEL3/Fpc=; b=mfDSmdGRjZkDrpHN9u63gue+2HdSN5BTbggs1555G1qNNbtSNI6fyaX9ETNDlkqQHh SIWTVXrJgKwS4DJbONFbvY+BA7B5qPmWzW/7HxuSVVFf2StEIYmNNuPE/pHqyEnlufoN jCv+MzxoYMdl1HEFAXrqlX6eswLFi0b3+LeBNiMTQC1xJKMeholB+dfJkaxUbzBkbDkw pVXNMuvd6ZuEe5/X+smZbHTdaN/9D2/yLu5VdMMLf+4aFyltzc8A44tJUlP+xCzQpqmG hYCviJZs90vWphh7ADCx6TxO0Wy+uQ4vE2vIcQofau7MT1014k2eyt+NxPaVu/L6QD5C cHuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=orlppNliu8M0qtDLjqe1tmmGT9po7KYftgxmEL3/Fpc=; b=BkyTE0HzBt9MZszmoc9LKKe9PuTc6y8Yc26LBiDkbjSM3IWY7bVLrl5AmrAgFpyUdQ Qsaj7LogzaijAxed61d+ZD3v4DzLRXLbV7YsE5fTzSOf9u5kQ0pky/9vIoFnyAM+G1p6 yM5pFfX5Z1g1XjIsjifQvEq2+hQXEDnlPHXEbiULmNYQ6xMitqqHScQ9ie6rtMZhpDWQ MRkUvq0Hr4+lnRnPaliZfHxrWOmittGhZKN5KUybU7H6em472Q/WlvdqDKhJE7767SHD PMIz+fU1Dpq2uyF23k71jVVdIwJ7b8NZl1uG1oPNB+iSOdE3Kp+unB4hUU6Bq3q7Wntl LxCQ==
X-Gm-Message-State: AMke39knUPNUqkKncj+pV1TY5Ahn1tApVgIly2xk4q/O4Kjg6Kn4DzqMqpsqBz9vyDfJKQ==
X-Received: by 10.237.35.138 with SMTP id j10mr17960519qtc.255.1488818585107;  Mon, 06 Mar 2017 08:43:05 -0800 (PST)
Received: from [10.0.20.202] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id j35sm1679144qtc.63.2017.03.06.08.43.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Mar 2017 08:43:04 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Adding IPv10 to the IETF 98 Agenda.
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <HE1PR04MB14494F944755BE4630D615D7BD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com>
Date: Mon, 6 Mar 2017 11:43:02 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <4D7CABE0-AA69-4DF0-998A-6E7C5B72FCE3@fugue.com>
References: <HE1PR04MB14494F944755BE4630D615D7BD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k3NpeZJw3SzuUGTbJ4HHMgJBUlI>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 16:43:07 -0000

To which working group chair did you make this request?


From nobody Mon Mar  6 08:56:24 2017
Return-Path: <rraszuk@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 3CFE91298AB; Mon,  6 Mar 2017 08:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AeAidZryGLVF; Mon,  6 Mar 2017 08:56:11 -0800 (PST)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 811FA12945A; Mon,  6 Mar 2017 08:56:08 -0800 (PST)
Received: by mail-qk0-x235.google.com with SMTP id v125so101449166qkh.2; Mon, 06 Mar 2017 08:56:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=7kc2EZtj+yn/+ohsLYCM6KqBZjr4W+qHfdZppmkmuQk=; b=tL/0ilinredX0avBjHsNco/HUDnKmjYSI2FRfyjn8oop80d5nd1a6Z3B4oBk+Q24gO i8M8C8kpdt6fJYWXA9O8/SK4YlofudM9eGVsfkTQse9/3fdPefUP/CunkF+Ha9NMQyVm l7LSv7FupiLPWWJoKwAzUOvE2NTKGNvg7o8LWNOAw1abU0nENH0J33BLjufLuQPp+cnn k44DzqM+FJVT7l12L/RhP5GGSB/tC6uHoxiJ10x0i90Yf/xNDK912NzaJdFiVPhrZpBU gOD3eJRdWFZWefKG3xcrjHxXuD3eNEWWnqa6RJFL5SGJpCI/uKBVajQWrP4kSevnjiSO Wh0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=7kc2EZtj+yn/+ohsLYCM6KqBZjr4W+qHfdZppmkmuQk=; b=oCxVZRGwORG3Wlgthmh0yVFmjr3x2y2EU8OxREHCK+tZNTXH4z3wN+g89amie7yklH UUWI3IKv74PihwuIJh0lTubs2OV79DHBNhNTaxBiBzuMOfM1sFppj84dw82iobtsg+B3 VaRjX8ucvOSgx6A1PGR3lEgVYjKioDUYRAv0Ghoqx5SI6gQ5cAFktb543z0pRFkfq8zH xu77fBFTfdsms8y5VKIFiqHY1OG5x5Gft9lvUNfnpo372gFHNfKrHeUKhIIFGrLUnKty 97wDjEcgt7WqEDCp3ipw2KBNo+BDzWfmD1wTjoSSfzkS6LeajjHNqh9c9zrAc8KYHYE+ y+BQ==
X-Gm-Message-State: AMke39nutbg/8srcMTcwJns7RBl/MOn5ay/THQWndYYoZtPRYP/WMBCRf8Odz3hD4YuLQGBQxs3Io2nTFVxVDQ==
X-Received: by 10.200.55.152 with SMTP id d24mr16255270qtc.1.1488819367441; Mon, 06 Mar 2017 08:56:07 -0800 (PST)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.140.42.181 with HTTP; Mon, 6 Mar 2017 08:56:06 -0800 (PST)
In-Reply-To: <148881752958.15101.3565092696759250024.idtracker@ietfa.amsl.com>
References: <148881752958.15101.3565092696759250024.idtracker@ietfa.amsl.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 6 Mar 2017 17:56:06 +0100
X-Google-Sender-Auth: dnIT7xJ2bsz3TUnc2lagUEI893s
Message-ID: <CA+b+ER=XFzbi_JKE=VQqe4M5OJcqWB6MibQWFSiau2YZcp9jBA@mail.gmail.com>
Subject: Re: [spring] Review of draft-ietf-spring-segment-routing-msdc-03
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary=001a113c5e7287fe75054a12c560
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l-31Fc8grzXqkK5WiD9cQ5hwnHE>
Cc: rtg-dir@ietf.org, "spring@ietf.org" <spring@ietf.org>, IETF Discussion <ietf@ietf.org>, draft-ietf-spring-segment-routing-msdc.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 16:56:15 -0000

--001a113c5e7287fe75054a12c560
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Sue,

Please kindly allow me to clarify two points here ...

Point 1:

You said:

"The BGP peers would carry this information in a separate informational
stream.  With this constraint,
it was approved by the IESG.
=E2=80=8B"

=E2=80=8BHowever looking at RFC7752 at most it lightly says three times tha=
t
dedicated RRs may be used to disseminate collected information. =E2=80=8BSo=
 while I
do recall how this extension was "sold" I am afraid in no way this has any
bearing on how it will be used now or in the future deployments.

=E2=80=8BPoint 2:

In your comment I see major concerns with security .. Well let's keep in
mind that this proposal is specific to MSDC. As such by design it is all
under single administrative domain .. hence I think non of the security
points really apply.

Cheers,
R.


On Mon, Mar 6, 2017 at 5:25 PM, Susan Hares <shares@ndzh.com> wrote:

> Reviewer: Susan Hares
> Review result: Has Issues
>
> The RTG-DIR has the categories:  minor concerns or major concerns
> regarding "issues", I wil differentiate my issues by this quality.
> I also have editorial nits regardign under specified text.
>
> Major concerns:
> 1) The security section is not sufficient for any review by the
> Security area
>
> This draft depends on IDR WG draft (ietf-idr-bgp-prefix-sid) that
> defines the BGP Segment attribute.  If this attribute is used with
> IPv6, this simply gives more infromation about a link to a next.
> However, the combination of this information with the information
> passed using draft-ietf-idr-bgpls-segment-routing-epe-09 that utilizes
> BGP to pass BGP topologies in BGP - requires a better security
> section.  BGP-LS was described to be an "information gathering"
> function handled by a few routers on the edge of the network to obtain
> link-state topology information.  The BGP peers would carry this
> information in a separate informational stream.  With this constraint,
> it was approved by the IESG.
> draft-ietf-idr-bgpls-segment-routing-epe  expands the initial concept
> of BGP-LS from "information gathering" to a full-routing scheme of BGP
> within BGP for data centers and for data center interconnection to the
> network.   This extension takes it out of the approved range of the
> BGP-LS.  Therefore, the security sections in both the IDR WG drafts
> and this draft need to describe the new threat scenarios and describe
> threat mitigation strategies for deployments.
>
> In addition, the information by BGP-LS
> (draft-ietf-idr-bgpls-segment-routing-epe) or in draft-ietf-bgp-sid
> may have privacy issues - so these need to be described the security
> section.
>
> 2) through-out the text you use words such as "ebgp3107" or BGP 3107
> updates"
>
> This phrase is inaccurate.  The base RFC3107 support will not provide
> BGP-Prefix support (as supported in bgp-idr-bgp-prefix.   Some texts
> goes on to clarify the addition of the BGP SID Prefix attribute.  It
> would be better to invent a new phrase or term.
>
> In section 8.1, the authors state:
> "The Prefix Segement is a lightweight extension to the BGP Labelled
> Unicast".  As noted in my #1 major concern, this "hand-waving"
> description either needs to be refined to be accurate.  If the MPLS
> usage only uses the BGP-Prefix label and does not extend to the
> Egress, it is simplier.  However, it is not clear that is what section
> 8.1 is about.   If 8.1 includes the
> draft-ietf-idr-bgpls-segment-routing-epe, then BGP-LS addition does
> have a number of prefixes and rules.   The trade-off between BGP-LS +
> BGP-LS SID (draft-ietf-idr-bgp-sid) handling + BGP LS egress peer
> engineering draft (draft-ietf-idr-bgp-segment-routing-epe) and a
> signalling protocol is more complex than the hand-wave.  It may be the
> right choice based on current implementations and management issues,
> but these need to be laid specifically.
>
> 3) Why are you defining 2-byte Private Use AS when there are plenty of
> 4-Byte Private Use AS (p. 5).
>
> This usage increases the confusion regarding 2-byte/4-byte ASN.  IDR
> specifically worked on 4 byte ASN.
>
> Minor concerns
> 1) It is not clear what happens in section 4.2.2 and figure 3-5
>
> What happens if the traffic goes to node 3 instead of node 4 on the
> ECMP path?
> What happens if the traffic goes to node 8 instead of node 7 on the
> ECMP Path?
>
> Is there something missing in the stroy?
>
> 2) section 4.3 - IBGP Labeled Unicast.
>
> The phrase "iBGP3107 reflection with nhop-self" needs to be explicitly
> spelled out as IBGP Route-Reflection with next-hop self.  If that is
> not what the authors mean, then it needs to be further spelled out.
> It is unclear where the central IBGP nodes are that share fully the
> information learned from the three clusters. (nodes:5-8 cluster 1,
> nodes 3-4 cluster 2, nodes 9-10 cluster 3).
>
> This section has hints of a solution, but it is miss a great deal.
> Please upgrade to specific solution.  A diagram might help.
>
> 3) Load Sharing hints (Section 7.1)
>
> Elephant flow and mice flows are good descriptions.  Flowlets and VL2
> should either warrant a 1 sentence explanation that actually describes
> these features in a 22 page draft, or be removed.
>
> 4)  The lack of a manageability or operations section (TBD in version
> -02) - concerns me.  The operational issues may be well known to the
> data centers and devices manufacturers who have implement this
> specification, but this is an interoperability specification for IETF.
>  Some manageabilty comments should be included or a BCP pointed to.
>
> Editorial issues:
>
> #1 - The following 4 abbrevitions need to be initially expanded when
> first used:  CLOs (p.3),  SRGB(p.6), flowlets (p. 14), and VL2 (p.
> 14).
>
> #2 - page 7, section 4.2 last paragraph
> Old/: assuming the IP Addresses, AS and label-index allocation
> previously described, the"
> New/: assuming the IP address with the AS and label-index allocation
> previously described, the"
> [Comma is optional]
>
> #3 - page 14, section 7.1 paragraph 4,  /(e.g. spine switch Node1)/  -
> by the diagram it should be node 5-8 or an error.  Please check the
> number
>
> #4 - page 17, section 8.2 paragraph 2.
>
> Old/
> This is easily accomplished by encapsulating the trafffic either
> directly at the host or the source ToR node by pushing the BGP-
> Prefix-SID of the destination ToR for intra-DC traffic, or border
> node for inter-DC or DC-to-outside-world traffic./
>
> New/
> This is easily accomplished by encapsulating the trafffic either
> directly at the host or the source ToR node  by pushing  the BGP-
> Prefix-SID of the destination ToR for intra-DC traffic, or
> the BGP-Prefix-SID for the the border node for inter-DC or
> DC-to-outside-world traffic./
>
> If this is not the correct logic, then you can reword this further.
> I read it 4 or 5 times.
>
> #5 - Adding a diagram to section 4.3 might help your description.
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>

--001a113c5e7287fe75054a12c560
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">Hi Sue,</div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif;font-size:small">Please kindly allow me to clarify two points here ...=
=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:arial,helveti=
ca,sans-serif;font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small">Point 1:</div><=
div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif=
;font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-fami=
ly:arial,helvetica,sans-serif;font-size:small">You said:=C2=A0</div><div cl=
ass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-=
size:small"><br></div><div class=3D"gmail_default" style=3D"font-family:ari=
al,helvetica,sans-serif;font-size:small">&quot;<span style=3D"font-size:12.=
8px;font-family:arial,sans-serif">The BGP peers would carry this=C2=A0</spa=
n><span style=3D"font-size:12.8px;font-family:arial,sans-serif">information=
 in a separate informational stream.=C2=A0 With this constraint,</span></di=
v><span style=3D"font-size:12.8px">it was approved by the IESG.<div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small;display:inline">=E2=80=8B&quot;</div></span><div><span style=3D"fon=
t-size:12.8px"><div class=3D"gmail_default" style=3D"font-family:arial,helv=
etica,sans-serif;font-size:small;display:inline"><br></div></span></div><di=
v><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-se=
rif;font-size:small">=E2=80=8BHowever looking at RFC7752 at most it lightly=
 says three times that dedicated RRs may be used to disseminate collected i=
nformation. =E2=80=8BSo while I do recall how this extension was &quot;sold=
&quot; I am afraid in no way this has any bearing on how it will be used no=
w or in the future deployments.</div><br></div><div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">=E2=
=80=8BPoint 2:</div><div class=3D"gmail_default" style=3D"font-family:arial=
,helvetica,sans-serif;font-size:small"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">In your=
 comment I see major concerns with security .. Well let&#39;s keep in mind =
that this proposal is specific to MSDC. As such by design it is all under s=
ingle administrative domain .. hence I think non of the security points rea=
lly apply.=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:ari=
al,helvetica,sans-serif;font-size:small"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">Cheer=
s,<br>R.</div></div><div><br></div></div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Mon, Mar 6, 2017 at 5:25 PM, Susan Hares <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:shares@ndzh.com" target=3D"_blank">shares@=
ndzh.com</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">Reviewer=
: Susan Hares<br>
Review result: Has Issues<br>
<br>
The RTG-DIR has the categories:=C2=A0 minor concerns or major concerns<br>
regarding &quot;issues&quot;, I wil differentiate my issues by this quality=
.<br>
I also have editorial nits regardign under specified text.<br>
<br>
Major concerns:<br>
1) The security section is not sufficient for any review by the<br>
Security area<br>
<br>
This draft depends on IDR WG draft (ietf-idr-bgp-prefix-sid) that<br>
defines the BGP Segment attribute.=C2=A0 If this attribute is used with<br>
IPv6, this simply gives more infromation about a link to a next.<br>
However, the combination of this information with the information<br>
passed using draft-ietf-idr-bgpls-segment-<wbr>routing-epe-09 that utilizes=
<br>
BGP to pass BGP topologies in BGP - requires a better security<br>
section.=C2=A0 BGP-LS was described to be an &quot;information gathering&qu=
ot;<br>
function handled by a few routers on the edge of the network to obtain<br>
link-state topology information.=C2=A0 The BGP peers would carry this<br>
information in a separate informational stream.=C2=A0 With this constraint,=
<br>
it was approved by the IESG.<br>
draft-ietf-idr-bgpls-segment-<wbr>routing-epe=C2=A0 expands the initial con=
cept<br>
of BGP-LS from &quot;information gathering&quot; to a full-routing scheme o=
f BGP<br>
within BGP for data centers and for data center interconnection to the<br>
network.=C2=A0 =C2=A0This extension takes it out of the approved range of t=
he<br>
BGP-LS.=C2=A0 Therefore, the security sections in both the IDR WG drafts<br=
>
and this draft need to describe the new threat scenarios and describe<br>
threat mitigation strategies for deployments.<br>
<br>
In addition, the information by BGP-LS<br>
(draft-ietf-idr-bgpls-segment-<wbr>routing-epe) or in draft-ietf-bgp-sid<br=
>
may have privacy issues - so these need to be described the security<br>
section.<br>
<br>
2) through-out the text you use words such as &quot;ebgp3107&quot; or BGP 3=
107<br>
updates&quot;<br>
<br>
This phrase is inaccurate.=C2=A0 The base RFC3107 support will not provide<=
br>
BGP-Prefix support (as supported in bgp-idr-bgp-prefix.=C2=A0 =C2=A0Some te=
xts<br>
goes on to clarify the addition of the BGP SID Prefix attribute.=C2=A0 It<b=
r>
would be better to invent a new phrase or term.<br>
<br>
In section 8.1, the authors state:<br>
&quot;The Prefix Segement is a lightweight extension to the BGP Labelled<br=
>
Unicast&quot;.=C2=A0 As noted in my #1 major concern, this &quot;hand-wavin=
g&quot;<br>
description either needs to be refined to be accurate.=C2=A0 If the MPLS<br=
>
usage only uses the BGP-Prefix label and does not extend to the<br>
Egress, it is simplier.=C2=A0 However, it is not clear that is what section=
<br>
8.1 is about.=C2=A0 =C2=A0If 8.1 includes the<br>
draft-ietf-idr-bgpls-segment-<wbr>routing-epe, then BGP-LS addition does<br=
>
have a number of prefixes and rules.=C2=A0 =C2=A0The trade-off between BGP-=
LS +<br>
BGP-LS SID (draft-ietf-idr-bgp-sid) handling + BGP LS egress peer<br>
engineering draft (draft-ietf-idr-bgp-segment-<wbr>routing-epe) and a<br>
signalling protocol is more complex than the hand-wave.=C2=A0 It may be the=
<br>
right choice based on current implementations and management issues,<br>
but these need to be laid specifically.<br>
<br>
3) Why are you defining 2-byte Private Use AS when there are plenty of<br>
4-Byte Private Use AS (p. 5).<br>
<br>
This usage increases the confusion regarding 2-byte/4-byte ASN.=C2=A0 IDR<b=
r>
specifically worked on 4 byte ASN.<br>
<br>
Minor concerns<br>
1) It is not clear what happens in section 4.2.2 and figure 3-5<br>
<br>
What happens if the traffic goes to node 3 instead of node 4 on the<br>
ECMP path?<br>
What happens if the traffic goes to node 8 instead of node 7 on the<br>
ECMP Path?<br>
<br>
Is there something missing in the stroy?<br>
<br>
2) section 4.3 - IBGP Labeled Unicast.<br>
<br>
The phrase &quot;iBGP3107 reflection with nhop-self&quot; needs to be expli=
citly<br>
spelled out as IBGP Route-Reflection with next-hop self.=C2=A0 If that is<b=
r>
not what the authors mean, then it needs to be further spelled out.<br>
It is unclear where the central IBGP nodes are that share fully the<br>
information learned from the three clusters. (nodes:5-8 cluster 1,<br>
nodes 3-4 cluster 2, nodes 9-10 cluster 3).<br>
<br>
This section has hints of a solution, but it is miss a great deal.<br>
Please upgrade to specific solution.=C2=A0 A diagram might help.<br>
<br>
3) Load Sharing hints (Section 7.1)<br>
<br>
Elephant flow and mice flows are good descriptions.=C2=A0 Flowlets and VL2<=
br>
should either warrant a 1 sentence explanation that actually describes<br>
these features in a 22 page draft, or be removed.<br>
<br>
4)=C2=A0 The lack of a manageability or operations section (TBD in version<=
br>
-02) - concerns me.=C2=A0 The operational issues may be well known to the<b=
r>
data centers and devices manufacturers who have implement this<br>
specification, but this is an interoperability specification for IETF.<br>
=C2=A0Some manageabilty comments should be included or a BCP pointed to.<br=
>
<br>
Editorial issues:<br>
<br>
#1 - The following 4 abbrevitions need to be initially expanded when<br>
first used:=C2=A0 CLOs (p.3),=C2=A0 SRGB(p.6), flowlets (p. 14), and VL2 (p=
.<br>
14).<br>
<br>
#2 - page 7, section 4.2 last paragraph<br>
Old/: assuming the IP Addresses, AS and label-index allocation<br>
previously described, the&quot;<br>
New/: assuming the IP address with the AS and label-index allocation<br>
previously described, the&quot;<br>
[Comma is optional]<br>
<br>
#3 - page 14, section 7.1 paragraph 4,=C2=A0 /(e.g. spine switch Node1)/=C2=
=A0 -<br>
by the diagram it should be node 5-8 or an error.=C2=A0 Please check the<br=
>
number<br>
<br>
#4 - page 17, section 8.2 paragraph 2.<br>
<br>
Old/<br>
This is easily accomplished by encapsulating the trafffic either<br>
directly at the host or the source ToR node by pushing the BGP-<br>
Prefix-SID of the destination ToR for intra-DC traffic, or border<br>
node for inter-DC or DC-to-outside-world traffic./<br>
<br>
New/<br>
This is easily accomplished by encapsulating the trafffic either<br>
directly at the host or the source ToR node=C2=A0 by pushing=C2=A0 the BGP-=
<br>
Prefix-SID of the destination ToR for intra-DC traffic, or<br>
the BGP-Prefix-SID for the the border node for inter-DC or<br>
DC-to-outside-world traffic./<br>
<br>
If this is not the correct logic, then you can reword this further.<br>
I read it 4 or 5 times.<br>
<br>
#5 - Adding a diagram to section 4.3 might help your description.<br>
<br>
<br>
______________________________<wbr>_________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org">spring@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/spring</a><br=
>
</blockquote></div><br></div>

--001a113c5e7287fe75054a12c560--


From nobody Mon Mar  6 09:02:44 2017
Return-Path: <eng.khaled.omar@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 A4F501298A6 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 09:02:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level: 
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id acNv5ldIIAl2 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 09:02:41 -0800 (PST)
Received: from SNT004-OMC2S47.hotmail.com (snt004-omc2s47.hotmail.com [65.54.61.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58D8512989C for <ietf@ietf.org>; Mon,  6 Mar 2017 09:02:41 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com ([65.55.90.73]) by SNT004-OMC2S47.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 6 Mar 2017 09:02:40 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=9oGWiRXi/igo3uAh8AkkEjqvIVCLPV7JpV0N9H409tY=; b=kyRiA9usomZl+VR351DBDCU7dzIcDu5NagETN84k13km1pSQQwrj4/OBaRzRxLVEKKUYNxxIZvJS6OH50w3thNOLCXTtsfcWCPDzpz0NKcxPWWbjoSltzgKnlkIYBT/Qpt0nxUpT7Kycup8hD99MzG3JHg2jfSenGnyYr/b+67xcBwKFl3K6i/MBkYKFadr+hAAj2tb3wfTTaua326awwV1nHjmDsOBWRHg5Otq/lGjQYccbizejc7DnLPCkS09iTMHuvXXbqkd/mEIpqEeWs+kTv8TLcTHzu/yBl3ukaddo3gUB/167zHZJ4wXNmcvHZCzx32BlMwjqSAMhnOUtMA==
Received: from DB5EUR03FT046.eop-EUR03.prod.protection.outlook.com (10.152.20.58) by DB5EUR03HT033.eop-EUR03.prod.protection.outlook.com (10.152.21.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.7; Mon, 6 Mar 2017 17:02:38 +0000
Received: from HE1PR04MB1449.eurprd04.prod.outlook.com (10.152.20.58) by DB5EUR03FT046.mail.protection.outlook.com (10.152.21.230) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.7 via Frontend Transport; Mon, 6 Mar 2017 17:02:38 +0000
Received: from HE1PR04MB1449.eurprd04.prod.outlook.com ([10.163.176.11]) by HE1PR04MB1449.eurprd04.prod.outlook.com ([10.163.176.11]) with mapi id 15.01.0947.018; Mon, 6 Mar 2017 17:02:38 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Adding IPv10 to the IETF 98 Agenda.
Thread-Topic: Re: Adding IPv10 to the IETF 98 Agenda.
Thread-Index: AdKWmuU11NZpSf4rTyKm+K8iJLh5LQ==
Date: Mon, 6 Mar 2017 17:02:38 +0000
Message-ID: <HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:0ED3A75DEFB98B45D15C60E8D05BA226327FF22596BD38077A1C31E00E3979EB; UpperCasedChecksum:ED78C7816EC6828146B15A732BF373B6D4909631BDE38851D0F8918ADD743AED; SizeAsReceived:7547; Count:36
x-tmn: [4+AzYnk7Uiv0JhtCxPQi8myyice2TDTa]
x-incomingheadercount: 36
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; DB5EUR03HT033; 5:E9hMnSW3aRjKi8licV3jds3IhlJvgaTaODp1OnQeo3OD2lzFaJd8/zS2V1BYMt7QA9ZRS18s9A/DJEapfTNEztXlNoLzJp+SPsUIGoe7MVhsR2PA0o84ggy/FOf1HZJURr36Ue5yHzur7xR9QgVPNA==; 24:FbPZ0xoZssWnPv7h7J+3ZFHRHgYsD3Ls6FcLYRGM2G6K1saW6nFADoozSqLje/d+1IG9JO7QA/4sd9irSia7zgE2fOKsFilfDQ04GEFw1nY=; 7:QTsUen9F7xPaHo4+Y+pWuyFRxk0q0l9gm1xxoPsPhvd+pqmVOdwtSH9ZCtcoI1iX6zh+/cRGy5nE2oWnO6XXZk2cCtoDaVzuTyB/JU/5v7rZxssIfAWTL0fhr43pRl6UoQtIUAAjljwUQWhK9ijg9U8PyohOxdiRhbHwN/uDwznw2t+GMUoethOMWLdf/SZPU62LLWuKMdgwEUJLhU4zG3V1roeosLT/v5XqGRUNA+6X9UhzQsJD+JHkukU3m62p6L3DifGuOynMCE78R1yGZ/7wc0TrRIAKipeVLV8+8/058ONtDmqkPUga+upxqUcD
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900016); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5EUR03HT033; H:HE1PR04MB1449.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 90139692-aa50-4528-b62a-08d464b29836
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(1601125254)(1603101448)(1701031045); SRVR:DB5EUR03HT033; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:DB5EUR03HT033; BCL:0; PCL:0; RULEID:; SRVR:DB5EUR03HT033; 
x-forefront-prvs: 0238AEEDB0
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0HE1PR04MB1449eurp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2017 17:02:38.5354 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5EUR03HT033
X-OriginalArrivalTime: 06 Mar 2017 17:02:40.0896 (UTC) FILETIME=[77127000:01D2969B]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1rbM0nC9GMbAHyPzStBhaN-EUGc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 17:02:42 -0000

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

Hi all,

Thanks for your responses ... finally I got a positive response from one of=
 the Internet Area Chairs and will be waiting for that discussion during th=
e IETF 98 meeting.

Best Regards,

Khaled

--_000_HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0HE1PR04MB1449eurp_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks for your responses &#8230; finally I got a po=
sitive response from one of the Internet Area Chairs and will be waiting fo=
r that discussion during the IETF 98 meeting.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Khaled<o:p></o:p></p>
</div>
</body>
</html>

--_000_HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0HE1PR04MB1449eurp_--


From nobody Mon Mar  6 09:15:04 2017
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 D0DC0129634; Mon,  6 Mar 2017 09:15:02 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e5tGcs3whLKK; Mon,  6 Mar 2017 09:15:00 -0800 (PST)
Received: from mail-ot0-x22f.google.com (mail-ot0-x22f.google.com [IPv6:2607:f8b0:4003:c0f::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75D44129626; Mon,  6 Mar 2017 09:15:00 -0800 (PST)
Received: by mail-ot0-x22f.google.com with SMTP id 19so46721300oti.0; Mon, 06 Mar 2017 09:15:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n56/94pezOe7CfyX0rG4OuSx+0TOxuza6MdZhMPm4Mw=; b=XoahB4jC25vKgJG67PJJePx9Av6yQXKfDGNsAUiJ/VNm5oS1joEwBMX9X+rye82orV fqSkjo7/avjGF/LqLiaY1+7FZhxZ/CuwsriZ8HFlol4EoW2mPuYqdSROppwdxfZY0RzB PjjseHYHvFwX41GPt+QhFOaRgt466dX/HS3JiMTw6OxHeohZc3XkQiLPJDwSXlDjNboo SWUxYZZDaXleDLCeb0XHix56BPl71+TrZoaKU3AVoksSbppV02mvqAW/GyiyJs4f9j5d kDMPU9TJmSTYgxr8H7CfKFFx18q1fuprZFow6aPVDcehuWoTrU0RYZv5DiILVmS6Cw+K DXgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=n56/94pezOe7CfyX0rG4OuSx+0TOxuza6MdZhMPm4Mw=; b=Tzr6+s4qsPnTQ9CKC+V2EZ5D5Bh0HK9wSD/+E6z8UzIwL/NmtRLLKYvePx9l8aPJ57 xNcYvW1mAZYsZGS34xDnD8kJpXX3/HgReOT2mvxow+TtWJLaOM6QFi6Pg/dkEKiNzHAX AUO/POvv7ZGG2wDOAeCdFzYfcFDoziF4GtN5Fw7/Kl7D68F6ZNBNJFeMvemVmsB1OSDT NSiTZ0023VOw2tEHSKtjgzQG31c/bQgstXfQQFz349ugl6ZYMDuj9iQAp2uT/85VnNx1 /0rKqbeFqXq/PrTvxbX3bFwRqpbMABUknpoW4DYEIqncE+YC3Khs5FjH3ycbhnvpxAwP CqxQ==
X-Gm-Message-State: AMke39k94tfeQzuZcEDu6MvYmIP9OHq4+y8LC/9OGwidAfpc7G+0nDCRxCd1LRjaaHQl/pSK5DdwZ0t2ksLS7g==
X-Received: by 10.157.51.61 with SMTP id f58mr9350332otc.18.1488820499492; Mon, 06 Mar 2017 09:14:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.42.10 with HTTP; Mon, 6 Mar 2017 09:14:29 -0800 (PST)
In-Reply-To: <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com> <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 6 Mar 2017 09:14:29 -0800
Message-ID: <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com>
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Content-Type: multipart/alternative; boundary=001a113e2d2801b740054a1309d7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kahn1Kr7JzcEgHtFbiWlnBRQdLE>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 17:15:03 -0000

--001a113e2d2801b740054a1309d7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Mohamed,

Replies in-line.



On Mon, Mar 6, 2017 at 1:48 AM, <mohamed.boucadair@orange.com> wrote:

>
> =C2=B7         A Forward-For header inserted by a proxy does not restore =
any
> data; it does only reveal data that is already present in the packet issu=
ed
> by the client itself.
>
> That's what restore means here.
>
> [Med] Then, this needs to be defined in the document. I naively assumed
> that =E2=80=9Crestored=E2=80=9D is used to mean any piece of information =
that the client
> does not want to insert in a packet, but an on-path device decides to
> inject it despite there is no consent from the client.
>
What you are describing is more about =E2=80=9Cmaintaining=E2=80=9D or =E2=
=80=9Cpreserving=E2=80=9D
> information not restoring it.
>
>
>
The common uses of restore in English all focus on putting something back
that has been lost, so I believe restore is better than "maintain" or
"preserve", which imply something is being carried forward as-is, rather
than being put back after loss.



>   If the information is present as metadata in the packet sent to the
> proxy but would be absent as metadata under normal operation of the proxy=
,
> adding it back in somewhere else restores the metadata.
>
> [Med] =E2=80=9Cnormal operation of proxy=E2=80=9D is not a standard. A =
=E2=80=9Cnormal operation
> of proxy=E2=80=9D would be to maintain the information sent by the client=
 when
> relaying it to the server. I=E2=80=99m sure you know for instance that SI=
P B2BUAs
> can do whatever they want!
>

You're right that the normal operation of a proxy is not a standard, and I
should have said "the normal operation of the protocols used by a proxy".
If the action of the proxy is to start a new TCP connection to an origin
server, for example, the normal operation of TCP is to use the initiator's
IP address.  The loses the IP address of the querying host is implied by
that normal operation(in other words, it elides metadata about any client
that caused this new TCP connection to be createD).


>
>
> So origin IP address starts out in the IP header of the original packet
> but gets pushed from that slot when the proxy constructs the onward IP
> packet to the server.  For it to reach the server, it has to be placed
> somewhere else in the onward packet, restoring the lost metadata.
>
> [Med] The client agreed to send packets with its source IP address (which
> mean consent). Why the proxy would need to an extra channel to get consen=
t
> for relaying the source IP address to a server?
>
>
>

Because the client agreed to send packets to the proxy by putting it in the
destination, and did not agree to general disclosure; you can't infer
onward consent.



> Had it been present in the packet as header value in the HTTP exchange, i=
t
> would not have been stripped by normal operation.  There proxy operation
> forwarding it on would be simply preserving it.
>
> [Med] This is another question: whether the same or distinct channel can
> be used to communicate the SAME data that was present in the initial pack=
et
> issued by a host.
>
>

That depends on the nature of the channel.  Obviously, if you set the
origin clients IP address as the source address, you're going to get a
different result from that spoofing than putting it in a client subnet EDNS
option or forwarded-for header.

=C2=B7         An address sharing device, under for example DS-Lite (RFC633=
3),
> that inserts the source IPv6 prefix in the TCP HOST_ID option (RFC7974) i=
s
> not RESTORING any data. The content of that TCP option is already visible
> in the packet sent by the host.
>
> I agree with the IESG analysis of RFC7974.  It does restore information b=
y
> taking information which normal operation would have elided and restores =
it.
>
> [Med] The  implication of what you are saying here is that proxies are
> good because they hide the source IP addresses of host!
>
>
>
Aggregating proxies can have a positive privacy impact, yes.  An observer
seeing traffic from an aggregating proxy to sensitive-topic.example.com
knows only that some user behind that proxy is looking for information on
sensitive-topic.  To know which user, the observer must have either
suborned the proxy or have a way of observing traffic between hosts and the
proxy.  Both are more expensive and at higher risk of discovery than a
simple tap near sensitive-topic.example.com.


>
>
>
> If the data is taken from a portion of the packet that would not normally
> be forwarded to an upstream host and added to a portion that is forwarded
> to an upstream host, then the device adding the data back in should know =
it
> is a restoration.
>
> [Med] That definition is not trivial as mentioned above. I would use
> =E2=80=9Cpreserve=E2=80=9D or =E2=80=9Cmaintain=E2=80=9D rather than =E2=
=80=9Crestore=E2=80=9D.
>
> Please see above.  "Restore" is closer, in my opinion, than either
preserve or maintain.



>
>
> If the endpoint sends the data, data will be consistently available in
> that header.  The data changes, of course.
>
> [Med] I=E2=80=99m not sure to follow you here. What is meant by =E2=80=9C=
consistent
> availability=E2=80=9D then? Do you mean the same channel/procedure to com=
municate
> the information? Or =E2=80=9Cconsistent data=E2=80=9D?
>
>

I mean that if you define a protocol such that a well-formed message from
the client has the data the server needs, it will be consistently
available.  If you rely on intermediate network devices to add the data, it
may not be available if there is not cooperating network device on path
(e.g. if the DNS resolver does not support the relevant EDNS0 option).


>
>
>
>
> [Med] Resources may not be restricted to CPU or disk but may be granting
> access to the service (e.g., download a file when a quota per source
> address is enforced). It can be whatever the servers consider to be
> critical for them; it is up to the taste of the service design to
> characterize it. The NEW wording proposed above is technically correct.
> Please reconsider adding it to the draft.
>
>
>
>
>
> I did consider it, but I continue to believe that it moves the needle too
> far into simple server preference.  I retained the original PSAP language
> in -07 as a result.
>
> [Med] emergency is only an example ; other services may exist that impose
> the same trust model.
>
>
>

I think there is a qualitative difference between situations in which the
resources at risk are human lives and those where they are host resources.
That's why the carve out was limited in the GEOPRIV case.



> I also added a note about your extensive review.  While you and I clearly
> have some differences of view, the document has gotten better from your
> engagement with it, and I appreciate your efforts.
>
> [Med] I reviewed the -07. Although it is better compared to -05, I still
> don=E2=80=99t think it is ready to be published as it is. Thank you for y=
our effort.
>
And thank you for yours,

regards,

Ted


> regards,
>
> Ted
>

--001a113e2d2801b740054a1309d7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi Mohamed,<br><br></div>Replies in-line.<br><br=
></div><br><div><div><div><br>On Mon, Mar 6, 2017 at 1:48 AM,  <span dir=3D=
"ltr">&lt;<a href=3D"mailto:mohamed.boucadair@orange.com" target=3D"_blank"=
>mohamed.boucadair@orange.com</a>&gt;</span> wrote:<br><div class=3D"gmail_=
extra"><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 link=3D"blue" vlink=3D"purple" lang=3D"FR">
<br><div class=3D"m_-6194685057534319269WordSection1"><span class=3D"">
<p class=3D"MsoNormal"><span lang=3D"EN-US"></span></p></span><span class=
=3D""><blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padd=
ing:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div>
<div>
<div>
<p class=3D"m_-6194685057534319269m7770722288423157249msolistparagraph"><sp=
an style=3D"font-size:10.0pt;font-family:Symbol;color:black" lang=3D"EN-US"=
>=C2=B7</span><span style=3D"font-size:7.0pt;color:black" lang=3D"EN-US">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black" lang=3D"EN-US">A Forward-For header inserted by a proxy does n=
ot restore any data; it does only reveal data that is already present in th=
e packet issued by the client itself.</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</span><div><span class=3D"">
<p class=3D"MsoNormal">That&#39;s what restore means here.<span style=3D"co=
lor:black"></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] Then, this needs t=
o be defined in the document. I naively assumed that =E2=80=9Crestored=E2=
=80=9D is used to mean any piece of information that the client does not
 want to insert in a packet, but an on-path device decides to inject it des=
pite there is no consent from the client.</span>=C2=A0</p></div></div></div=
></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"pu=
rple" lang=3D"FR"><div class=3D"m_-6194685057534319269WordSection1"><div><p=
 class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;;color:black" lang=3D"EN-US"> What you are describing is more =
about =E2=80=9Cmaintaining=E2=80=9D or =E2=80=9Cpreserving=E2=80=9D informa=
tion not restoring it.</span></p><span class=3D"">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">=C2=A0</span></p></span></div><=
/div></div></blockquote><div>The common uses of restore in English all focu=
s on putting something back that has been lost, so I believe restore is bet=
ter than &quot;maintain&quot; or &quot;preserve&quot;, which imply somethin=
g is being carried forward as-is, rather than being put back after loss.<br=
></div><div><br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"blu=
e" vlink=3D"purple" lang=3D"FR"><div class=3D"m_-6194685057534319269WordSec=
tion1"><div><span class=3D"">
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0 If the information is pr=
esent as metadata in the packet sent to the proxy but would be absent as me=
tadata under normal operation of the proxy, adding it back in somewhere els=
e restores the metadata.=C2=A0<span style=3D"color:black"></span></span></p=
>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] =E2=80=9Cnormal op=
eration of proxy=E2=80=9D is not a standard. A =E2=80=9Cnormal operation of=
 proxy=E2=80=9D would be to maintain the information sent by the client whe=
n relaying it
 to the server. I=E2=80=99m sure you know for instance that SIP B2BUAs can =
do whatever they want! =C2=A0</span></p></div></div></div></blockquote><div=
><br></div><div>You&#39;re right that the normal operation of a proxy is no=
t a standard, and I should have said &quot;the normal operation of the prot=
ocols used by a proxy&quot;.=C2=A0 If the action of the proxy is to start a=
 new TCP connection to an origin server, for example, the normal operation =
of TCP is to use the initiator&#39;s IP address.=C2=A0 The loses the IP add=
ress of the querying host is implied by that normal operation(in other word=
s, it elides metadata about any client that caused this new TCP connection =
to be createD).<br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"=
blue" vlink=3D"purple" lang=3D"FR"><div class=3D"m_-6194685057534319269Word=
Section1"><div><span class=3D"">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">=C2=A0</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">So origin IP address starts out=
 in the IP header of the original packet but gets pushed from that slot whe=
n the proxy constructs the onward IP packet to the server.=C2=A0 For it to =
reach the server, it has to be placed somewhere
 else in the onward packet, restoring the lost metadata.</span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] The client agreed =
to send packets with its source IP address (which mean consent). Why the pr=
oxy would need to an extra channel to get consent for relaying
 the source IP address to a server? =C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p></div></div></=
div></blockquote><div><br></div><div>Because the client agreed to send pack=
ets to the proxy by putting it in the destination, and did not agree to gen=
eral disclosure; you can&#39;t infer onward consent.<br></div><div><br>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple"=
 lang=3D"FR"><div class=3D"m_-6194685057534319269WordSection1"><div>
</div>
<div><span class=3D"">
<p class=3D"MsoNormal">Had it been present in the packet as header value in=
 the HTTP exchange, it would not have been stripped by normal operation.=C2=
=A0 There proxy operation forwarding it on would be simply preserving it.<s=
pan style=3D"color:black"></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] This is another qu=
estion: whether the same or distinct channel can be used to communicate the=
 SAME data that was present in the initial packet issued
 by a host.</span><span lang=3D"EN-US"><br>
=C2=A0</span></p></div></div></div></blockquote><div><br></div><div>That de=
pends on the nature of the channel.=C2=A0 Obviously, if you set the origin =
clients IP address as the source address, you&#39;re going to get a differe=
nt result from that spoofing than putting it in a client subnet EDNS option=
 or forwarded-for header. <br><br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div=
 link=3D"blue" vlink=3D"purple" lang=3D"FR"><div class=3D"m_-61946850575343=
19269WordSection1"><div>
</div><span class=3D"">
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div>
<div>
<div>
<p class=3D"m_-6194685057534319269m7770722288423157249msolistparagraph"><sp=
an style=3D"font-size:10.0pt;font-family:Symbol;color:black" lang=3D"EN-US"=
>=C2=B7</span><span style=3D"font-size:7.0pt;color:black" lang=3D"EN-US">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black" lang=3D"EN-US">An address sharing device, under for example DS=
-Lite (RFC6333), that inserts the source IPv6 prefix in the TCP HOST_ID opt=
ion (RFC7974) is not RESTORING any data. The content
 of that TCP option is already visible in the packet sent by the host. </sp=
an></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</span><div><span class=3D"">
<p class=3D"MsoNormal">I agree with the IESG analysis of RFC7974.=C2=A0 It =
does restore information by taking information which normal operation would=
 have elided and restores it.<span style=3D"color:black"></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] The=C2=A0 implicat=
ion of what you are saying here is that proxies are good because they hide =
the source IP addresses of host! =C2=A0</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
</span></p></div></div></div></blockquote><div><br></div><div>Aggregating p=
roxies can have a positive privacy impact, yes.=C2=A0 An observer seeing tr=
affic from an aggregating proxy to <a href=3D"http://sensitive-topic.exampl=
e.com">sensitive-topic.example.com</a> knows only that some user behind tha=
t proxy is looking for information on sensitive-topic.=C2=A0 To know which =
user, the observer must have either suborned the proxy or have a way of obs=
erving traffic between hosts and the proxy.=C2=A0 Both are more expensive a=
nd at higher risk of discovery than a simple tap near <a href=3D"http://sen=
sitive-topic.example.com">sensitive-topic.example.com</a>.=C2=A0 <br></div>=
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D=
"purple" lang=3D"FR"><div class=3D"m_-6194685057534319269WordSection1"><br>=
<span class=3D""><blockquote style=3D"border:none;border-left:solid #cccccc=
 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><div><=
div><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt"><div><div><div><div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0</p>
</div>
</span><div><span class=3D"">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">If the data is taken =
from a portion of the packet that would not normally be forwarded to an ups=
tream host and added to a portion that is forwarded to an upstream host, th=
en the device adding the data back in
 should know it is a restoration.</p>
</span><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D=
"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"=
EN-US">[Med] That definition is not trivial as mentioned above. I would use=
 =E2=80=9Cpreserve=E2=80=9D or =E2=80=9Cmaintain=E2=80=9D rather than =E2=
=80=9Crestore=E2=80=9D.
</span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"></span></p></div></span></div><=
/div></blockquote><div>Please see above.=C2=A0 &quot;Restore&quot; is close=
r, in my opinion, than either preserve or maintain.<br></div><div><br>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple"=
 lang=3D"FR"><div class=3D"m_-6194685057534319269WordSection1">=C2=A0<span =
class=3D""><div>
</div>
</span><div><span class=3D"">
<p class=3D"MsoNormal">If the endpoint sends the data, data will be consist=
ently available in that header.=C2=A0 The data changes, of cou<span style=
=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=
=3D"EN-US">rse.</span><span style=3D"font-size:10.0pt;font-family:&quot;Cou=
rier New&quot;" lang=3D"EN-US"></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] I=E2=80=99m not su=
re to follow you here. What is meant by =E2=80=9C</span><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;" lang=3D"EN-US">consistent=
 availability=E2=80=9D
 then</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&q=
uot;;color:black" lang=3D"EN-US">? Do you mean the same channel/procedure t=
o communicate the information? Or =E2=80=9Cconsistent data=E2=80=9D?</span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"></span></p></div></div></div></=
blockquote><div><br><br></div><div>I mean that if you define a protocol suc=
h that a well-formed message from the client has the data the server needs,=
 it will be consistently available.=C2=A0 If you rely on intermediate netwo=
rk devices to add the data, it may not be available if there is not coopera=
ting network device on path (e.g. if the DNS resolver does not support the =
relevant EDNS0 option).<br></div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><div class=3D"m_-6194=
685057534319269WordSection1"><div><p class=3D"MsoNormal"><span lang=3D"EN-U=
S">=C2=A0</span></p>
</div><span class=3D"">
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">=C2=A0</span><span lang=3D"EN-U=
S"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">[Med] Resources may not be rest=
ricted to CPU or disk but may be granting access to the service
 (e.g., download a file when a quota per source address is enforced). It ca=
n be whatever the servers consider to be critical for them; it is up to the=
 taste of the service design to characterize it. The NEW wording proposed a=
bove is technically correct. Please
 reconsider adding it to the draft. </span><span lang=3D"EN-US"><br>
<br>
=C2=A0 </span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0</p>
</div>
</span><div><span class=3D"">
<p class=3D"MsoNormal">I did consider it, but I continue to believe that it=
 moves the needle too far into simple server preference.=C2=A0 I retained t=
he original PSAP language in -07 as a result.</p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] emergency is only =
an example=C2=A0; other services may exist that impose the same trust model=
.
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p></div></div></=
div></blockquote><div><br></div><div>I think there is a qualitative differe=
nce between situations in which the resources at risk are human lives and t=
hose where they are host resources.=C2=A0 That&#39;s why the carve out was =
limited in the GEOPRIV case.=C2=A0 <br></div><div><br>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><div =
class=3D"m_-6194685057534319269WordSection1"><div>
</div>
<div><span class=3D"">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I also added a note a=
bout your extensive review.=C2=A0 While you and I clearly have some differe=
nces of view, the document has gotten better from your engagement with it, =
and I appreciate your efforts.</p>
</span><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D=
"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"=
EN-US">[Med] I reviewed the -07. Although it is better compared to -05, I s=
till don=E2=80=99t think it is ready to be published as it is. Thank
 you for your effort.</span></p></div></div></div></blockquote><div>And tha=
nk you for yours,<br><br></div><div>regards,<br><br></div><div>Ted<br></div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=
=3D"purple" lang=3D"FR"><div class=3D"m_-6194685057534319269WordSection1"><=
div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">regards,</p>
</div>
<div>
<p class=3D"MsoNormal">Ted</p>
</div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt"><div><div>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div></div></div></div></div>

--001a113e2d2801b740054a1309d7--


From nobody Mon Mar  6 10:11:32 2017
Return-Path: <ietf-dane@dukhovni.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 2A8581294CC for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 10:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OcJaDlVbmhzH for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 10:11:29 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEEFD1294B4 for <ietf@ietf.org>; Mon,  6 Mar 2017 10:11:29 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id E3D237A32D8 for <ietf@ietf.org>; Mon,  6 Mar 2017 18:11:28 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: More haste, less speed.
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com>
Date: Mon, 6 Mar 2017 13:11:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF91F5B4-D8A0-4569-9011-3C3E38C71F07@dukhovni.org>
References: <CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pQHVdYP_jB3axMjLMLzw7JKH294>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 18:11:31 -0000

> On Mar 6, 2017, at 11:27 AM, Phillip Hallam-Baker =
<phill@hallambaker.com> wrote:
>=20
> DANE conflates publication of security policy with public key =
validation and distribution.

Well, by far the main obstacle to DANE deployment is not this, but =
comparatively low
(~0.6%) DNSSEC adoption.  Of approximately 1.5 million domains with =
DNSSEC for both
the domain and one of the primary MX hosts, 110 thousand (and steadily =
growing) have
DANE TLSA records (7% of those who can deploy, given DNSSEC constraints, =
have deployed).

The conflation of security policy and key distribution is a late =
addition to DANE in
RFC 7672.  The base specification in RFC 6698 is rather policy neutral.  =
So perhaps
tying the two together is in good part my fault.  And yet, despite that, =
there is
considerably more deployment of RFC 7672 (in SMTP) than of RFC 6698 (in =
HTTP, which
was its unstated primary focus).

If you feel strongly that publishing TLSA records should not imply =
security policy,
it is not too late to introduce a new policy specification protocol =
(that would
still require DNSSEC) to decouple existence of DANE TLSA records from =
the desired
security policy.  We could then retrofit MTAs to use the policy records =
when
present.  This would then require two DNS lookups where one suffices, =
but might
provide useful flexibility.

Do you have use-cases in which publication of DANE-EE(3) or DANE-TA(2) =
TLSA
records should not imply a request that sending domains use said =
records?

My impression is that the adoption obstacle remains operational =
difficulties
around DNSSEC and not missing policy hooks.

--=20
	Viktor.


From nobody Mon Mar  6 12:12:20 2017
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 E18EF1299E6 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 12:12:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srV8C7rs2L3q for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 12:12:17 -0800 (PST)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 309DF1299DC for <ietf@ietf.org>; Mon,  6 Mar 2017 12:12:17 -0800 (PST)
Received: by mail-yw0-x22d.google.com with SMTP id v198so44579071ywc.2 for <ietf@ietf.org>; Mon, 06 Mar 2017 12:12:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=/mBKUZ3/HeIpPxA4pqT+/VOdhZUfXegmenxiOm9udeg=; b=a6Rwj3k18gcuuCmtUvdZ3ZiuCaI7hMFOwOfX8biaI68CLu+wssL2kkkmdpXzrtEwu7 2PGg3wWMxR0dHetAM9BTnQLnBiijotaPnyCuahD9paqD3MwtRW30MN9LN1BqGLRFNkTk xFq8zbxWw7x0C54h1w1OR87GZuU+DyNPuVz1I5bKF8DnRJiGsJ0TXBBvHb+0C1Br0GX7 EfPo6Rd+OMdMSIoIIYsaiiWrQoeBs/ZRZ4zqhaOr6fnvVSvJG2WxQRWPp5dypmeqmNNq ZKXFYT2FwyXJnyoZ8/JEcZ6ifzJ1PREOxJorn4WAluPUjof7MZTdXg9M8RQerEZPCHjS ih/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=/mBKUZ3/HeIpPxA4pqT+/VOdhZUfXegmenxiOm9udeg=; b=Rjmt8XvWnH5TMwX2F/YXb/IrAdBGKeToUq2AaRIUkpAdtqSnAj/1Ogy6YcWPpeCgRN crQuuCde0BVdCSeMKWlFQo4atbW59Yq4u5LvQH1r+BExpUfzwRH2VtBuB07FujjQtXeK QxS3tVYdBY4bOqc34gmA6bEekv+EUVUekj6DoWl9EJoc9qtnKcuPkQUQC598C8KlW8pj idOPg9T0E4Q53P/qEJaoqxr9sZEQUd0HmNalEFeQyKNfz1YEG+JBksdFS7z+LiiA+lcf 0/+7hGi3MZOTqx2b9tUG8L0vYaS2Aelu9aov0i10N7ed7Vz5r8+ts2IaKWcQRqk0M8Lo DsJg==
X-Gm-Message-State: AMke39nwRmJicxeHX0sXGYlehIibyh4Zx+65L5eMmghPn/DrvAwKSbrwj2Oyt7mXG9vn1tYYdAxJUTlfxOlJsw==
X-Received: by 10.37.43.135 with SMTP id r129mr12889361ybr.126.1488831136137;  Mon, 06 Mar 2017 12:12:16 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Mon, 6 Mar 2017 12:12:15 -0800 (PST)
In-Reply-To: <DF91F5B4-D8A0-4569-9011-3C3E38C71F07@dukhovni.org>
References: <CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com> <DF91F5B4-D8A0-4569-9011-3C3E38C71F07@dukhovni.org>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 6 Mar 2017 15:12:15 -0500
X-Google-Sender-Auth: bS0dW6RTPSXG88h73OW5zgWG37o
Message-ID: <CAMm+LwjWqXg_EA7_0aT5DagZv4YirreUv1wKGAtBir01WwMT5Q@mail.gmail.com>
Subject: Re: More haste, less speed.
To: IETF general list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c13587c004bc5054a1583d9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w2cFPcwwG2cswtaT3JOSW_9Zm2g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 20:12:19 -0000

--94eb2c13587c004bc5054a1583d9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 6, 2017 at 1:11 PM, Viktor Dukhovni <ietf-dane@dukhovni.org>
wrote:

>
> > On Mar 6, 2017, at 11:27 AM, Phillip Hallam-Baker <phill@hallambaker.co=
m>
> wrote:
> >
> > DANE conflates publication of security policy with public key validatio=
n
> and distribution.
>
> Well, by far the main obstacle to DANE deployment is not this, but
> comparatively low
> (~0.6%) DNSSEC adoption.  Of approximately 1.5 million domains with DNSSE=
C
> for both
> the domain and one of the primary MX hosts, 110 thousand (and steadily
> growing) have
> DANE TLSA records (7% of those who can deploy, given DNSSEC constraints,
> have deployed).
>
> The conflation of security policy and key distribution is a late addition
> to DANE in
> RFC 7672.  The base specification in RFC 6698 is rather policy neutral.
> So perhaps
> tying the two together is in good part my fault.  And yet, despite that,
> there is
> considerably more deployment of RFC 7672 (in SMTP) than of RFC 6698 (in
> HTTP, which
> was its unstated primary focus).
>
> If you feel strongly that publishing TLSA records should not imply
> security policy,
> it is not too late to introduce a new policy specification protocol (that
> would
> still require DNSSEC) to decouple existence of DANE TLSA records from the
> desired
> security policy.  We could then retrofit MTAs to use the policy records
> when
> present.  This would then require two DNS lookups where one suffices, but
> might
> provide useful flexibility.
>
> Do you have use-cases in which publication of DANE-EE(3) or DANE-TA(2) TL=
SA
> records should not imply a request that sending domains use said records?
>
> My impression is that the adoption obstacle remains operational
> difficulties
> around DNSSEC and not missing policy hooks.
>

=E2=80=8BAgain, you are mistaken.=E2=80=8B

=E2=80=8BSecurity Policy can benefit from DNSSEC but it absolutely does not=
 require
DNSSEC to provide value. Since the current Internet security policy is to
require no security, any policy publication mechanism adds value over the
baseline.

The reason DANE cannot progress is precisely that it is tied to DNSSEC in
such a way that instead of DANE getting itself widely deployed and becoming
a =E2=80=8Breason to deploy DNSSEC infrastructure, it is instead dependent =
on prior
deployment of DNSSEC so that it cannot succeed until after DNSSEC has been
deployed.

These arguments are not new, they have been rehearsed repeatedly and are
one of the main reasons for not tying policy to key validation. The other
being that the DNS registrars critical to deployment of DNSSEC sell DNS at
a loss and make their profit on the item DANE tries to make free of charge.
Its called a channel conflict and yes, they are show stoppers.

--94eb2c13587c004bc5054a1583d9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Ma=
r 6, 2017 at 1:11 PM, Viktor Dukhovni <span dir=3D"ltr">&lt;<a href=3D"mail=
to:ietf-dane@dukhovni.org" target=3D"_blank">ietf-dane@dukhovni.org</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"><span class=3D""><br>
&gt; On Mar 6, 2017, at 11:27 AM, Phillip Hallam-Baker &lt;<a href=3D"mailt=
o:phill@hallambaker.com">phill@hallambaker.com</a>&gt; wrote:<br>
&gt;<br>
&gt; DANE conflates publication of security policy with public key validati=
on and distribution.<br>
<br>
</span>Well, by far the main obstacle to DANE deployment is not this, but c=
omparatively low<br>
(~0.6%) DNSSEC adoption.=C2=A0 Of approximately 1.5 million domains with DN=
SSEC for both<br>
the domain and one of the primary MX hosts, 110 thousand (and steadily grow=
ing) have<br>
DANE TLSA records (7% of those who can deploy, given DNSSEC constraints, ha=
ve deployed).<br>
<br>
The conflation of security policy and key distribution is a late addition t=
o DANE in<br>
RFC 7672.=C2=A0 The base specification in RFC 6698 is rather policy neutral=
.=C2=A0 So perhaps<br>
tying the two together is in good part my fault.=C2=A0 And yet, despite tha=
t, there is<br>
considerably more deployment of RFC 7672 (in SMTP) than of RFC 6698 (in HTT=
P, which<br>
was its unstated primary focus).<br>
<br>
If you feel strongly that publishing TLSA records should not imply security=
 policy,<br>
it is not too late to introduce a new policy specification protocol (that w=
ould<br>
still require DNSSEC) to decouple existence of DANE TLSA records from the d=
esired<br>
security policy.=C2=A0 We could then retrofit MTAs to use the policy record=
s when<br>
present.=C2=A0 This would then require two DNS lookups where one suffices, =
but might<br>
provide useful flexibility.<br>
<br>
Do you have use-cases in which publication of DANE-EE(3) or DANE-TA(2) TLSA=
<br>
records should not imply a request that sending domains use said records?<b=
r>
<br>
My impression is that the adoption obstacle remains operational difficultie=
s<br>
around DNSSEC and not missing policy hooks.<br></blockquote><div><br></div>=
<div><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8BAgain,=
 you are mistaken.=E2=80=8B</div><br></div><div><div class=3D"gmail_default=
" style=3D"font-size:small">=E2=80=8BSecurity Policy can benefit from DNSSE=
C but it absolutely does not require DNSSEC to provide value. Since the cur=
rent Internet security policy is to require no security, any policy publica=
tion mechanism adds value over the baseline.</div><div class=3D"gmail_defau=
lt" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">The reason DANE cannot progress is precisely that it i=
s tied to DNSSEC in such a way that instead of DANE getting itself widely d=
eployed and becoming a =E2=80=8Breason to deploy DNSSEC infrastructure, it =
is instead dependent on prior deployment of DNSSEC so that it cannot succee=
d until after DNSSEC has been deployed.</div><div class=3D"gmail_default" s=
tyle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">These arguments are not new, they have been rehearsed repeat=
edly and are one of the main reasons for not tying policy to key validation=
. The other being that the DNS registrars critical to deployment of DNSSEC =
sell DNS at a loss and make their profit on the item DANE tries to make fre=
e of charge. Its called a channel conflict and yes, they are show stoppers.=
</div><br></div><div><br></div><div><br></div><div>=C2=A0</div></div></div>=
</div>

--94eb2c13587c004bc5054a1583d9--


From nobody Mon Mar  6 13:30:34 2017
Return-Path: <ietf-dane@dukhovni.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 36D45129A34 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 13:30:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HifCOWxK-qF2 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 13:30:32 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04BB2129A29 for <ietf@ietf.org>; Mon,  6 Mar 2017 13:30:31 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id D7B0F7A32D8 for <ietf@ietf.org>; Mon,  6 Mar 2017 21:30:30 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: More haste, less speed.
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CAMm+LwjWqXg_EA7_0aT5DagZv4YirreUv1wKGAtBir01WwMT5Q@mail.gmail.com>
Date: Mon, 6 Mar 2017 16:30:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <205292A2-2134-4DAA-BE0E-E76487A615E4@dukhovni.org>
References: <CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com> <DF91F5B4-D8A0-4569-9011-3C3E38C71F07@dukhovni.org> <CAMm+LwjWqXg_EA7_0aT5DagZv4YirreUv1wKGAtBir01WwMT5Q@mail.gmail.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EqKg9lN_M2GnJJw8UoDoG5joJp8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 21:30:33 -0000

> On Mar 6, 2017, at 3:12 PM, Phillip Hallam-Baker =
<phill@hallambaker.com> wrote:
>=20
> =E2=80=8BAgain, you are mistaken.=E2=80=8B

I think you meant to say, that you disagree, at least in general, but =
that your
experience in the SMTP space is more limited, so I might be right in the =
SMTP case.

> =E2=80=8BSecurity Policy can benefit from DNSSEC but it absolutely =
does not require DNSSEC
> to provide value.

This is not true for SMTP, which is vulnerable to downgrade attacks if =
the security
policy is not made tamper-resistant.

> Since the current Internet security policy is to require no security, =
any policy
> publication mechanism adds value over the baseline.

Yes, against passive attacks, but STARTTLS is already sufficient for =
that.

--=20
	Viktor.


From nobody Mon Mar  6 13:40:25 2017
Return-Path: <gem@rellim.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68F76129A4A for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 13:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.208
X-Spam-Level: 
X-Spam-Status: No, score=-1.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=rellim.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFD5gnIRU12x for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 13:40:23 -0800 (PST)
Received: from spidey.rellim.com (unknown [IPv6:2001:470:e815::19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EA941294A9 for <ietf@ietf.org>; Mon,  6 Mar 2017 13:40:23 -0800 (PST)
Received: from spidey.rellim.com (rellim.com [IPv6:2001:470:e815:0:0:0:0:19]) (authenticated bits=0) by spidey.rellim.com (8.15.2/8.15.2) with ESMTPSA id v26LeHSF002035 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <ietf@ietf.org>; Mon, 6 Mar 2017 13:40:22 -0800
DKIM-Filter: OpenDKIM Filter v2.10.3 spidey.rellim.com v26LeHSF002035
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=kong; t=1488836422; bh=w4LF6sEogS+p58d2cp9lfZiLyASGZZcFyOtPUFOwoSU=; h=Date:From:To:Subject:In-Reply-To:References; b=NEeF/Z9Ea5G4oRyVRBC70QGm2naxoFwnsRg7n05n7jQZWsYPJqlxOOKUzp5VC16dC JIIPAikOTL2mMqj7ti1MNt97kiMCRPYa00ZBx48/IgsXF22dj9R4Ad85y8ZvRtDr6O S4X+xUOwFzEWqjtJ7j/nNv5gMaARGdRfwFXItpnI=
Date: Mon, 6 Mar 2017 13:40:17 -0800
From: "Gary E. Miller" <gem@rellim.com>
To: IETF general list <ietf@ietf.org>
Subject: Re: More haste, less speed.
Message-ID: <20170306134017.29d2290c@spidey.rellim.com>
In-Reply-To: <205292A2-2134-4DAA-BE0E-E76487A615E4@dukhovni.org>
References: <CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com> <DF91F5B4-D8A0-4569-9011-3C3E38C71F07@dukhovni.org> <CAMm+LwjWqXg_EA7_0aT5DagZv4YirreUv1wKGAtBir01WwMT5Q@mail.gmail.com> <205292A2-2134-4DAA-BE0E-E76487A615E4@dukhovni.org>
Organization: Rellim
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/LmrMR8nho.4jwZaZ+nf8EKr"; protocol="application/pgp-signature"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6rc1 (spidey.rellim.com [IPv6:2001:470:e815:0:0:0:0:19]); Mon, 06 Mar 2017 13:40:22 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fL5XIinfsJ5kG17G7H7U12oWToo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 21:40:24 -0000

--Sig_/LmrMR8nho.4jwZaZ+nf8EKr
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yo Viktor!

On Mon, 6 Mar 2017 16:30:30 -0500
Viktor Dukhovni <ietf-dane@dukhovni.org> wrote:

> > Security Policy can benefit from DNSSEC but it absolutely does not
> > require DNSSEC to provide value. =20
>=20
> This is not true for SMTP, which is vulnerable to downgrade attacks
> if the security policy is not made tamper-resistant.

Please do not make the best the enemy of the merely better.  Often a
little better is good enough for now.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can=E2=80=99t measure it, you can=E2=80=99t improve it." - Lord=
 Kelvin

--Sig_/LmrMR8nho.4jwZaZ+nf8EKr
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENqCjEoytAEAuFCk8DQ7ZSUHRedgFAli910EACgkQDQ7ZSUHR
edg4Hwf+PvFeTCoT2T1YlvbpNRM8bOyexUJjQhPFvQML5EMuc9HnQX0Px4HHIRZI
4uZh/+JrcqbwYsVMs3h6VUKT14zRBk13H7c1BRILf/KEXo2gy0wkuhwSahXVZfNp
RedNAQyyr/nSemBOeZNfkQ+6wwLMPnhuS1H+RiySX+GxSP1I1rkRb094GhgyD+eP
5q43UUXNuKMPGAxsVFJtZFkyAbgDyekpP+395YJMf1e2qhi1fZ2ySxa0bR5XQysN
kdEcLty8FuOWLPbB3BymuMtwRMZlSo3EFh1979FNpe5/eMpBuP71K1V7oF38ZdTL
asink4KCfwFc7J5F/cGmFr86TbrmOQ==
=qjx5
-----END PGP SIGNATURE-----

--Sig_/LmrMR8nho.4jwZaZ+nf8EKr--


From nobody Mon Mar  6 14:01:16 2017
Return-Path: <ietf-dane@dukhovni.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 47D3B1294CF for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 14:01:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-Iym8lq10rF for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 14:01:13 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C09A812949B for <ietf@ietf.org>; Mon,  6 Mar 2017 14:01:13 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id A1E337A32D8 for <ietf@ietf.org>; Mon,  6 Mar 2017 22:01:12 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: More haste, less speed.
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <20170306134017.29d2290c@spidey.rellim.com>
Date: Mon, 6 Mar 2017 17:01:11 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <207B0EDA-4CF8-4665-974F-4CD159BCF89A@dukhovni.org>
References: <CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com> <DF91F5B4-D8A0-4569-9011-3C3E38C71F07@dukhovni.org> <CAMm+LwjWqXg_EA7_0aT5DagZv4YirreUv1wKGAtBir01WwMT5Q@mail.gmail.com> <205292A2-2134-4DAA-BE0E-E76487A615E4@dukhovni.org> <20170306134017.29d2290c@spidey.rellim.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fk4_wN6TMjZffRjRUtL0AfYMyRc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Mar 2017 22:01:15 -0000

> On Mar 6, 2017, at 4:40 PM, Gary E. Miller <gem@rellim.com> wrote:
> 
>> This is not true for SMTP, which is vulnerable to downgrade attacks
>> if the security policy is not made tamper-resistant.
> 
> Please do not make the best the enemy of the merely better.  Often a
> little better is good enough for now.

No need to convince me, see RFC7435.  That said, the current STARTTLS is
quite sufficient for best-effort security and is quite effective at that:

   https://www.google.com/transparencyreport/saferemail/

Roughly 84% of email to/from gmail is TLS protected, which beats the
recent milestone (IIRC reported from Mozilla HTTP telemetry) of 50%
of web traffic using TLS.

The goal of DANE TLS for SMTP is to opportunistically provide downgrade
resistance for TLS to domains that deploy DANE TLSA records for SMTP.
It is up to each domain whether to publish TLSA records for SMTP or not.
If they do, MTA-to-MTA SMTP from a DANE-enabled MTA to the destination
becomes downgrade-resistant and authenticated.

Notable early adopters in include gmx.de, web.de, posteo.de, mailbox.org,
transip.nl, domeneshop.no, comcast.net, ...

-- 
	Viktor.


From nobody Mon Mar  6 17:38:51 2017
Return-Path: <bob.hinden@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 25AB6129A80; Mon,  6 Mar 2017 17:38:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7A8wqTqxGT6I; Mon,  6 Mar 2017 17:38:43 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DACD5129860; Mon,  6 Mar 2017 17:38:42 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id n11so78064479wma.1; Mon, 06 Mar 2017 17:38:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=oB/79nhduDwV115IhdiiKWmzAQ9yKp4XgoyRrPkHMKc=; b=iBW6rik3k6kEnWd5lzYvPZ2MkAR/SFKAdB1TVask6nMLGofCdtsZ97iRz3i8LV4r2y 3MN5+fes4M142dtg4EvVBTsionqXRaAQOou1ZfbxmZQRBMVNRRkZeoWQVcFwjA0oRK0D RQDumnAW4QbsjOwxyLz3+zTThzxjMUhPwSrEiepJq0djcxkbP7zqoq2Rlg6JdOuZNrOr NAufZ8c0Scc+6Vyc1d+GNSf3BdaXXSnCJ1x4gIGGhGHeeylsxYtt+EBleHNjHA4RdUma 6AX0CkKKbRld+miXw4tUyvj2eNNhh+77XQnMCZPnVkuENSpGYfWrbckpfeQWNG2Owh7W Clsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=oB/79nhduDwV115IhdiiKWmzAQ9yKp4XgoyRrPkHMKc=; b=cK8WAylRgvjwFrZ8XUlCODTPQ7y89KK+hzFzioW/goRe/uuCEWgPgqLIdpjUu4kmmT dPqi1NugQMvo+0k8t2QgQtJmZ0Yc7QP4RffTG6C8T87K1MTlPh1A3Uf01ge4B/de412D 5dJvpWS1twHNnaz+ozUWAk/Fw5jjyxVmbE7A7mlTdWEdJyDKtGgwN3/4kTleQZfBILHQ og/Z8jrmMdhlTdrF1hyBC0gL8DjV7MaoIPltxZhPb1XCHVE46f9mfxAYHIpjkqjbhypf ohcF+RZ2Pc0e6XulmhCshdtd8e1dBvmJqmctN9C1ntmHFJbFfu6f+FQd2jGRHhCuMwMm Y54Q==
X-Gm-Message-State: AMke39mTCktvfhYYBQ+hCRPpl33m7m+zG9chng6vaFkmIJ07RbQl/bFNxY+0Kud5oXqUUg==
X-Received: by 10.28.129.212 with SMTP id c203mr15194567wmd.19.1488850721378;  Mon, 06 Mar 2017 17:38:41 -0800 (PST)
Received: from ?IPv6:2601:647:4d01:db10:f96e:fb7:ae30:96cb? ([2601:647:4d01:db10:f96e:fb7:ae30:96cb]) by smtp.gmail.com with ESMTPSA id 40sm29025664wry.22.2017.03.06.17.38.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Mar 2017 17:38:40 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <FD5C174D-080B-4D59-88EB-ADE08AAA2D73@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6B728FC0-4A7A-4D8D-BCC1-5F5BCA1AE842"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Review of draft-ietf-6man-rfc1981bis-04
Date: Mon, 6 Mar 2017 17:38:33 -0800
In-Reply-To: <148864769030.23464.9110014115039938058.idtracker@ietfa.amsl.com>
To: Susan Hares <shares@ndzh.com>
References: <148864769030.23464.9110014115039938058.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WBaJ4RZU7uKpLplInDs6R3XlYNI>
Cc: IPv6 List <ipv6@ietf.org>, ops-dir@ietf.org, Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 01:38:46 -0000

--Apple-Mail=_6B728FC0-4A7A-4D8D-BCC1-5F5BCA1AE842
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Sue,

Thanks for the review, comments below.

Bob


> Reviewer: Susan Hares
> Review result: Has Issues
>=20
> ack, Steve,Jeffrey, and Bob:
>=20
> Thank you for taking on this important revision to the document.  I
> hope my comments help to improve the document so this important change
> can ge deployed.

Thanks

>=20
> I have reviewed this as part of the routing directorate review.  This
> review should be treated as any IETF LC comments.
>=20
> Sue Hares
>=20
> RTG-DIR Review
>=20
> Status: I have three concern plus editorial nits.
>=20
> #1 - Concern 1 is technical regarding the interaction with the MTU
> option in ND/SEND plus
> ditorial nits.  See the comments below.  I am not an ND/SEND Expert,
> please have an imoplementer look at the requirements.
>=20
> Concern: I cannot tell how this interacts with the ND/SEND protocol in
> the following areas below.
> 1) Neighbor Unreachability Detection is used for all paths between
> hosts
>   and neighboring nodes, including host-to-host, host-to-router, and
>   router-to-host communication.
>=20
>   If the source node is on the link and the destination node
> available
>   through the router, and the router is in the process of sending a
>   MTU option to increase the size?  How does your algorithm work?

I believe what will happen is that the host will use the new MTU in any =
new connections it establishes.   Existing connections will continue =
with preview MTU.

I also note, that this would be a very rare event as most LANs do not =
dynamically change their MTU.

>=20
>   Are the packetization layer notified?
>   Is the original value a stale notification over time?
>   You indicate it MUST NOT be done in less than 5 minutes, and that
>   10 minutes is the norm.
>=20
>   Is 10 minutes really the best response time for this particular
> case?
>   Or did I miss something in your draft?

See above.

>=20
>=20
> 2) Assume the same situation as #1, but the
>   router sends an MTU option to decrease the size.
>=20
>   In this case, the router is sending information that
>   the MTU has changed, but the first indication for the
>   end system is based on a Packet-too-Big Message after sending.

I think receiving PTB messages would be the likely result for existing =
connections.  The host would respond by reducing it=E2=80=99s packet =
size.  New connections would use the new MTU.

As above, this should be a very rare occurrence.

>=20
>=20
> 3) For a multicast packet (3000 bytes), assume that
> the multicast path reaches two different routers (router-a
> and router-b).  Assume the on-link MTU is 3500 bytes, but the
> previous router-A and router-B MTU is 2500 bytes.
>=20
> Router-a responds to the packet with 10ms sending a
> MTU option that changes the MTU to support this packet. Router-B sends
> a redirect
> for multicast address to Router-A after 30 ms.
>=20
> What happens to your path calculation?
> Is this again, the 5 minutes (minimum) and 10 minute normal to
> reset this value.

The host would use the lowest MTU it received and act accordingly.  This =
is described in the fifth paragraph of Section 3.


>=20
> 4) What happens if the ND process is instantiated by
> SEND protocol, and the host does not contain the appropriate
> certification information to timely updates?
>=20
> Again, the host guessing at the appropriate value?


I don=E2=80=99t follow this?  Please explain.  This seems more about a =
question about SEND, and not rfc1981bis.


>=20
>=20
> #2 - Concern 2 - How does SEND's implementation of MTU option.
> mitigate or have no effect on this MTU.  Is there a recommendation
> that should be made in section 6.  Again, please ask a SEND expert
> for review.

It works the same.  SEND secures ND, it still uses ND.   The SEND RFC =
doesn=E2=80=99t even reference RFC1981.

>=20
> #3 - Concern 3 - content of document
>=20
> This document has two parts: protocol requirements and implementation
> requirements.
> 8 paragraphs (1 page) indicates the IPv6 specification and 6 pages
> gives the implementation?
>=20
> Why did this get split in to 2 documents?  Even if this was a bis,
> document would it not
> be better to provide minimal specification for the protocol change and
> a larger document
> with implementation information.
>=20
> I'm fine with the WG/ADs deciding, this is the way the document has to
> go forward -- but the question should be asked.

The working groups intent in doing this bis document was to make a few =
changes to fix a problem related to a change in RFC2460bis, remove =
mention of RH0 because it was deprecated earlier, and a few other small =
changes.  It was not to do a major rewrite of the document (or as you =
suggest, split it into two documents).  The alternative was just to file =
an errata on RFC1981.

This document is very widely implemented.  I don=E2=80=99t think =
splitting the document into two would improve anything, and very likely =
create confusion for the current implementations.

>=20
> Editorial nits:
> #1 nit - section 5.2 page 8, paragraph beginning
>=20
> Old /Note: if the /
> New/Note: If the/
>=20
> #2 nit - section 5.2 page 9 paragraph begin
>=20
> Old /Note: even if/
> New /Note: Even if/
>=20
> #3 nit - section 5.3 page 10 paragraph beginning
>=20
> Old /Note: an implementation/
> New/Note: An implementation/
>=20
>=20

Noted.  Thanks.



--Apple-Mail=_6B728FC0-4A7A-4D8D-BCC1-5F5BCA1AE842
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYvg8aAAoJEK7rdBF357uoB4gIAIoJRdewJbpUW76Pt4jlgE2e
8y9YcTzuqenSjj8gr+f5EM3Rvux1xpiqb9/zdwUTCaQ/YxXdrKNWZcxdqp7G0MjU
SwwKUHc0D1iCaZYASiClqnuV1SudiWI37xsuVFWd3gM3usL/h0CIx9/ZCzsiunvQ
F/gjSvmuBGRQoAFczAm6JdNZv8qk2sUGL8Hp6+YEm0DI0NSlyjISXQmJW36UZrFI
MPbE40LQqDnth2OG90WVMckWQcRFHl+oCXBbncTESgMCIl4Y2IyLMidbBW5I3VxC
r35TfYZiFSRWe+1gIn/l5Wx/WdR+qBuif5iWfG6lEuQOmdIgaQJynVf74K9aV0g=
=GkvY
-----END PGP SIGNATURE-----

--Apple-Mail=_6B728FC0-4A7A-4D8D-BCC1-5F5BCA1AE842--


From nobody Mon Mar  6 18:47:36 2017
Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 801BB129A99; Mon,  6 Mar 2017 18:47:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mahesh Jethanandani <mjethanandani@gmail.com>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-slim-negotiating-human-language-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148885485450.15073.6095850267163523164.idtracker@ietfa.amsl.com>
Date: Mon, 06 Mar 2017 18:47:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xFA0bQHwl2BfuEs_EKHuaPunQFE>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 02:47:34 -0000

Reviewer: Mahesh Jethanandani
Review result: Has Nits

I have reviewed this document as part of the Operational
directorate’s ongoing effort to review all IETF documents being
processed by the IESG.  These comments were written with the intent of
improving the operational aspects of the IETF drafts. Comments that
are not addressed in last call may be
included in AD reviews during the IESG review.  Document editors
and WG chairs should treat these comments just like any other last
call comments.

Document reviewed:  draft-ietf-slim-negotiating-human-language-08

Status:

Ready with comments.

Summary: 

This document adds new SDP media-level attributes so that when
establishing interactive communication sessions ("calls"), it is
possible to negotiate (communicate and match) the caller's language
and media needs with the capabilities of the called party.

The document is short and easy to read. And it seems to have
considered many aspects of trying to negotiate a common human language
or capability. This review looks at the document more from a operator
or management perspective. 

Operational considerations:

>From a operations perspective, there may be a need to troubleshoot the
interface that sets up the negotiated human language. Identifying
consistent methods of information that should be counted by both
parties will go a long way in debugging a problem. For example, in
this case, it would be helpful to start by collecting how many
requests were made, how many found a language or medium in common and
how many were rejected because a common match was not found.

Management considerations:

The old adage says, “Anything that can be configured, can also be
misconfigured”, unless that is somehow made less possible by providing
default values, modes or parameters. This can be something that can be
defined using a data model in YANG.

I assume that the default behavior of receiving a SDP attribute that
one does not support, results in a throw away of that particular
attribute, and not the whole message, if combined with other
attributes. Is this documented somewhere? If not, what does the
deployment scenario look like, particularly with existing solutions?

What is the impact on network operations if for example either the
translator or relay agent fails? How would that impact the
negotiation?

Also, what is the test, both active and passive for the correct
operation? Is there a counter being maintained for both correct and
incorrect negotiation. Goes back to the question of what counters are
being maintained. Such counters should include values that enable
isolation of faults. For example, if negotiation fails, what are the
more specific counters that isolate what within the negotiation
failed?

Fault Management:

In addition to collection information on how the negotiation is
working, it is important to be able to propagate both fault and health
indicators to a management application. Such information needs to be
documented.

Accounting Management:

Finally, it is always helpful to collect information on utilization
from capacity, trend analysis, cost allocation, auditing and billing
perspective.

Idnits:

A run of idnits came out clean.




From nobody Mon Mar  6 19:33:41 2017
Return-Path: <mcr+ietf@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 9DEC812965A for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 19:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id em0FxaiFM1-T for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 19:33:38 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6A1F12956B for <ietf@ietf.org>; Mon,  6 Mar 2017 19:33:37 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id EAAC6E22D; Mon,  6 Mar 2017 22:56:13 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EBED9636BB; Mon,  6 Mar 2017 22:33:36 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf\@ietf.org Disgust" <ietf@ietf.org>, Lloyd Wood <l.wood@society.surrey.ac.uk>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
In-Reply-To: <1446835575.4118830.1488776805137@mail.yahoo.com>
References: <14476.1488384266@obiwan.sandelman.ca> <CAHw9_iKuZrxD=51QadPPnuofUdAeaHPQ4JvONz5Bno3HTAi71A@mail.gmail.com> <1446835575.4118830.1488776805137@mail.yahoo.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 06 Mar 2017 22:33:36 -0500
Message-ID: <21082.1488857616@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QLRLipNbzGy0FY8Je8tgw-6dsag>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 03:33:39 -0000

--=-=-=
Content-Type: text/plain


Lloyd Wood <L.Wood@society.surrey.ac.uk> wrote:
    > Those advocating 'early and often' might consider the case of
    > WhatWG, hybi, Ian Hickson, and his working style, as shown by
    > https://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-76

    > where it became impossible to figure out what had changed,
    > whether it was important, or really, anything other than the
    > way Hixie wanted to work, and that the WG really didn't like
    > how they were expected to run.

    > Diffs aren't useful unless they're of source.

Agreed: too many revisions is also a problem.
I think that the WG can push back.

Was it useful to diff version 60 against version 76?


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAli+KhAACgkQgItw+93Q
3WWHIwgAgjlGzHE9V2ykMU4CirPlUI7dFXJ3L2vJTCE3Hmt5xR/4m6AhMTvNjdPY
cgG45qGUuf0WgXcYtguoVYj0ZxHUUo9HY2EprnWhFZlpjGNAhG65PqqtohnZ3mlZ
KbrXON6zf7eBUwBbizW6ShbtgrFiolCmwiuJdWYVoXHveYApZjIWrsJdFrJ8Phv+
6I0Uhr5wyZeoOo2fpauyohfEzRzKHxYZ3HTgrHPxPW3Ds/MMzgU/WMd/iMxGhtzt
VLjFYWDBiQtq6XtzXxKBc1WMegOt4NsEOCIXf4E3ayM24K48k5zeUVCEV7VzlhA/
Jra3fAliWGGDz+L15o6wotKDZXUX3Q==
=XA85
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar  6 19:52:26 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54BD0129ADD; Mon,  6 Mar 2017 19:52:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w-vLfF71xDNU; Mon,  6 Mar 2017 19:52:18 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29F43129ADB; Mon,  6 Mar 2017 19:52:18 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.16.251; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Bob Hinden'" <bob.hinden@gmail.com>
References: <148864769030.23464.9110014115039938058.idtracker@ietfa.amsl.com> <FD5C174D-080B-4D59-88EB-ADE08AAA2D73@gmail.com>
In-Reply-To: <FD5C174D-080B-4D59-88EB-ADE08AAA2D73@gmail.com>
Subject: RE: Review of draft-ietf-6man-rfc1981bis-04
Date: Mon, 6 Mar 2017 22:47:19 -0500
Message-ID: <00fb01d296f5$85c57570$91506050$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEbJyWFeA8M+EN5czpk+ggCsNrULQJJzOZWouVKWPA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jQA5O-ClKfmCZIJ0FdV3aZURXvc>
Cc: ops-dir@ietf.org, 'IPv6 List' <ipv6@ietf.org>, 'IETF' <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 03:52:19 -0000

Bob:=20

Thank you for your response.    I'm pulling up the remaining questions =
to the top here.  All my questions were about corner cases and "what =
ifs" - which is just the result of being a reviewer of a =
long-implemented specification.=20

1) I thought the IPv6 LAN was targeted for new mobile networks or sensor =
networks.   If so, it may be in the future that the wireless connections =
would want to change the MTU on a network to increase the ability to =
change the MTU.   If you're answer is, we'll make the timer adjustment =
when these technology use it in this way, this is a fine answer.=20

2) On, your comment:=20
> I believe what will happen is that the host will use the new MTU in =
any new connections it establishes.   Existing connections will continue =
with preview MTU.=20
Did I miss this in the draft?   Just to sharpen my knowledge of this =
draft. =20

3) The question #4 - I was trying to determine what the interaction =
between the SEND with an MTU size option, and this update to RFC1918.   =
It appears in the specification these two functions are interacting.   =
Is this my imagination?  If not, just for my own information - where do =
I find this in the specification.  =20

Thanks,=20

Sue=20


-----Original Message-----
From: Bob Hinden [mailto:bob.hinden@gmail.com]=20
Sent: Monday, March 6, 2017 8:39 PM
To: Susan Hares
Cc: Bob Hinden; ops-dir@ietf.org; IPv6 List; IETF; =
draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: Review of draft-ietf-6man-rfc1981bis-04

Hi Sue,

Thanks for the review, comments below.

Bob


> Reviewer: Susan Hares
> Review result: Has Issues
>=20
> ack, Steve,Jeffrey, and Bob:
>=20
> Thank you for taking on this important revision to the document.  I=20
> hope my comments help to improve the document so this important change =

> can ge deployed.

Thanks

>=20
> I have reviewed this as part of the routing directorate review.  This=20
> review should be treated as any IETF LC comments.
>=20
> Sue Hares
>=20
> RTG-DIR Review
>=20
> Status: I have three concern plus editorial nits.
>=20
> #1 - Concern 1 is technical regarding the interaction with the MTU=20
> option in ND/SEND plus ditorial nits.  See the comments below.  I am=20
> not an ND/SEND Expert, please have an imoplementer look at the=20
> requirements.
>=20
> Concern: I cannot tell how this interacts with the ND/SEND protocol in =

> the following areas below.
> 1) Neighbor Unreachability Detection is used for all paths between=20
> hosts
>   and neighboring nodes, including host-to-host, host-to-router, and
>   router-to-host communication.
>=20
>   If the source node is on the link and the destination node available
>   through the router, and the router is in the process of sending a
>   MTU option to increase the size?  How does your algorithm work?

I believe what will happen is that the host will use the new MTU in any =
new connections it establishes.   Existing connections will continue =
with preview MTU.

I also note, that this would be a very rare event as most LANs do not =
dynamically change their MTU.

>=20
>   Are the packetization layer notified?
>   Is the original value a stale notification over time?
>   You indicate it MUST NOT be done in less than 5 minutes, and that
>   10 minutes is the norm.
>=20
>   Is 10 minutes really the best response time for this particular=20
> case?
>   Or did I miss something in your draft?

See above.

>=20
>=20
> 2) Assume the same situation as #1, but the
>   router sends an MTU option to decrease the size.
>=20
>   In this case, the router is sending information that
>   the MTU has changed, but the first indication for the
>   end system is based on a Packet-too-Big Message after sending.

I think receiving PTB messages would be the likely result for existing =
connections.  The host would respond by reducing it=E2=80=99s packet =
size.  New connections would use the new MTU.

As above, this should be a very rare occurrence.

>=20
>=20
> 3) For a multicast packet (3000 bytes), assume that the multicast path =

> reaches two different routers (router-a and router-b).  Assume the=20
> on-link MTU is 3500 bytes, but the previous router-A and router-B MTU=20
> is 2500 bytes.
>=20
> Router-a responds to the packet with 10ms sending a MTU option that=20
> changes the MTU to support this packet. Router-B sends a redirect for=20
> multicast address to Router-A after 30 ms.
>=20
> What happens to your path calculation?
> Is this again, the 5 minutes (minimum) and 10 minute normal to reset=20
> this value.

The host would use the lowest MTU it received and act accordingly.  This =
is described in the fifth paragraph of Section 3.


>=20
> 4) What happens if the ND process is instantiated by SEND protocol,=20
> and the host does not contain the appropriate certification=20
> information to timely updates?
>=20
> Again, the host guessing at the appropriate value?


I don=E2=80=99t follow this?  Please explain.  This seems more about a =
question about SEND, and not rfc1981bis.


>=20
>=20
> #2 - Concern 2 - How does SEND's implementation of MTU option.
> mitigate or have no effect on this MTU.  Is there a recommendation=20
> that should be made in section 6.  Again, please ask a SEND expert for =

> review.

It works the same.  SEND secures ND, it still uses ND.   The SEND RFC =
doesn=E2=80=99t even reference RFC1981.

>=20
> #3 - Concern 3 - content of document
>=20
> This document has two parts: protocol requirements and implementation=20
> requirements.
> 8 paragraphs (1 page) indicates the IPv6 specification and 6 pages=20
> gives the implementation?
>=20
> Why did this get split in to 2 documents?  Even if this was a bis,=20
> document would it not be better to provide minimal specification for=20
> the protocol change and a larger document with implementation=20
> information.
>=20
> I'm fine with the WG/ADs deciding, this is the way the document has to =

> go forward -- but the question should be asked.

The working groups intent in doing this bis document was to make a few =
changes to fix a problem related to a change in RFC2460bis, remove =
mention of RH0 because it was deprecated earlier, and a few other small =
changes.  It was not to do a major rewrite of the document (or as you =
suggest, split it into two documents).  The alternative was just to file =
an errata on RFC1981.

This document is very widely implemented.  I don=E2=80=99t think =
splitting the document into two would improve anything, and very likely =
create confusion for the current implementations.

>=20
> Editorial nits:
> #1 nit - section 5.2 page 8, paragraph beginning
>=20
> Old /Note: if the /
> New/Note: If the/
>=20
> #2 nit - section 5.2 page 9 paragraph begin
>=20
> Old /Note: even if/
> New /Note: Even if/
>=20
> #3 nit - section 5.3 page 10 paragraph beginning
>=20
> Old /Note: an implementation/
> New/Note: An implementation/
>=20
>=20

Noted.  Thanks.




From nobody Mon Mar  6 20:02:22 2017
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACA80129AE0 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 20:02:21 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GFyfOg78yZLw for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 20:02:19 -0800 (PST)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDD6A129409 for <ietf@ietf.org>; Mon,  6 Mar 2017 20:02:19 -0800 (PST)
Received: by mail-yw0-x232.google.com with SMTP id p77so136675201ywg.1 for <ietf@ietf.org>; Mon, 06 Mar 2017 20:02:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AJDu+DBgB9HI+X4kFJ6NnSDNcAyi7U+mXuqZvVDS8GQ=; b=NDL9emDt5UqD99su7OrlU9Y/JhANcC1CHYbolk8NNLfPm2zxjCx2inOID1VawMhqIP 040y5Ts6tIa5+4jZBTCnwhzUX3nicLMXs0je349vbdG8krWk591EWHEB7naUO/ZjNxOs kpXart4s5CiDlNQ1NV5ckbyqH1iCqgE5mCFX1gURUFnS74Dul7vfq1RF7LmcD40igdbm wM5B22dHwtFFVBx7+WW+QLbkP+wHpeu4c2zy+YUyFCLjwykx62rBAmr+ziDkReqxZyah FokzF4ow4gdtrS7nZXTnqGpixhJhJFDsnwVU2fOj8j3SNHO42888i3yCP42+UGw4n1mB HywA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AJDu+DBgB9HI+X4kFJ6NnSDNcAyi7U+mXuqZvVDS8GQ=; b=Mzh+sKBMeL3UUqp8pFbLAFi1aaOG9UgFgrZv25BBaKfVB/tXJJ9W4sqTVZCzUzjXHU zMEAoEXTAdgGFPlPaLF7XADw5sxAFvRXqGwaZwoiXoC1/rdPotSttvQT4xrYATO7c/Ro NiRl6KmQNi2+JJ9/1XDTJFIrkkM8JsYKvFEGu0sfC9iNPlm1j9lfwmb/JI6GFVNcRh3U Xrfy7o10LPBi5i0Qzw7vFZuXV/ffk5ifa3YWQ+JLiQEOlVWCzFwKty4uCq2juuYaeywA qQDJ6GxNwlzezcy26nLc30eFtuLJRgRIvnzUiay1B7+IquRQJZ2su9i412lKeJcPhruK Z4Mw==
X-Gm-Message-State: AMke39mpN6+mUF80BVKomVLGyqU+BlUubzt8qTE/jZx5zLO2o/2T++RVhQ90XTELlqEixnfidr2hPKig4YZNfA==
X-Received: by 10.37.173.82 with SMTP id l18mr14574962ybe.107.1488859339026; Mon, 06 Mar 2017 20:02:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.154.210 with HTTP; Mon, 6 Mar 2017 20:01:38 -0800 (PST)
In-Reply-To: <CAOdDvNrM7=bmgMxB=0NSOmQf_AxcMisUYYTJwW09K+-x4JnA5g@mail.gmail.com>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com> <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com> <B84F48D5CB1E262E120316CA@PSB> <CAOdDvNrM7=bmgMxB=0NSOmQf_AxcMisUYYTJwW09K+-x4JnA5g@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 6 Mar 2017 20:01:38 -0800
Message-ID: <CABcZeBMNDeL=gq2nS2MCNWJtrjBAcgVc+9Yb9GuBZYg=bq=NRQ@mail.gmail.com>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Patrick McManus <pmcmanus@mozilla.com>
Content-Type: multipart/alternative; boundary=f403045eb8ea06098f054a1c149a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8iLc5hgvbhseHodfx3xxMSnmP64>
Cc: John C Klensin <john-ietf@jck.com>, Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 04:02:22 -0000

--f403045eb8ea06098f054a1c149a
Content-Type: text/plain; charset=UTF-8

On Wed, Mar 1, 2017 at 1:41 PM, Patrick McManus <pmcmanus@mozilla.com>
wrote:
>
> (2) Intermittent review of snapshots, ones that are generally
>> believed by their editors to be coherent and self-consistent.
>> Github revision tracking often makes that approach very
>> burdensome; change logs in documents and diffs between versions
>> are often more helpful.
>>
>
> This seems to suggest that github based drafts go from -00 to WGLC with
> interim changes only happening on github. That's not the way it works in my
> experience - to me it feels like the same number of drafts are produced
> (some data here would be interesting.. http/2 had around 19 revisions at
> the end iirc even though we used github extensively.. I believe tls 1.3 is
> on draft 19 or 20 and it is also github centric) and they continue to have
> changelogs.
>

Just to reinforce a couple of points mcmanus is making here:

1. I'm not seeing much evidence that people produce significantly fewer
draft
revisions when Github is in use. As patrick says, TLS is currently on -18
and
I'm about to do -19. To take three comparison points of roughly comparable
size:

- TLS 1.2 (RFC5246) was published after -09
- IKEv2 (RFC4306) was published after -17
- ICE (RFC 5245) was published after -19

My impression is that with Github, much like with non-Github, the draft
issuance
cadence is largely driven by the IETF meeting schedule. Certainly we've
found
that to be true for many of the drafts I am working on (JSEP and TLS in
particular), even though we use Github.

I'd certainly be interested in seeing some evidence that Github drafts come
out less frequently than ones that didn't use Github.


2. Changelog quaity varies, of course, and AFAIK there's no actual
requirement
to do a Changelog, but my experience is that the Github drafts actually do a
somewhat better job of Changelogs, probably because the tooling encourages
you to package things up in a way that makes it easy to do a ChangeLog. This
is especially true if you use PRs because then you can easily go back and
look at every merged PR and that becomes the input to the ChangeLog.
Here, for example, is the TLS ChangeLog.
https://tlswg.github.io/tls13-spec/#rfc.section.1.2


I think what *is* fair to say is that Github enables a far richer
interaction model
(Patrick alluded to this as well) with the result that it highlights the
relative
poverty of the old occasional draft model, but that's not because that model
has suddenly gotten absolutely worse, just that there are now better tools
available and people are taking advantage of them.

-Ekr

--f403045eb8ea06098f054a1c149a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Mar 1, 2017 at 1:41 PM, Patrick McManus <span dir=3D"ltr">&lt;<a href=
=3D"mailto:pmcmanus@mozilla.com" target=3D"_blank">pmcmanus@mozilla.com</a>=
&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><span class=
=3D"gmail-"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
(2) Intermittent review of snapshots, ones that are generally<br>
believed by their editors to be coherent and self-consistent.<br>
Github revision tracking often makes that approach very<br>
burdensome; change logs in documents and diffs between versions<br>
are often more helpful.<br></blockquote><div><br></div></span><div>This see=
ms to suggest that github based drafts go from -00 to WGLC with interim cha=
nges only happening on github. That&#39;s not the way it works in my experi=
ence - to me it feels like the same number of drafts are produced (some dat=
a here would be interesting.. http/2 had around 19 revisions at the end iir=
c even though we used github extensively.. I believe tls 1.3 is on draft 19=
 or 20 and it is also github centric) and they continue to have changelogs.=
</div></div></div></div></blockquote><div><br></div><div>Just to reinforce =
a couple of points mcmanus is making here:</div><div><br></div><div>1. I&#3=
9;m not seeing much evidence that people produce significantly fewer draft<=
/div><div>revisions when Github is in use. As patrick says, TLS is currentl=
y on -18 and</div><div>I&#39;m about to do -19. To take three comparison po=
ints of roughly comparable</div><div>size:</div><div><br></div><div>- TLS 1=
.2 (RFC5246) was published after -09</div><div>- IKEv2 (RFC4306) was publis=
hed after -17</div><div>- ICE (RFC 5245) was published after -19</div><div>=
<br></div><div>My impression is that with Github, much like with non-Github=
, the draft issuance</div><div>cadence is largely driven by the IETF meetin=
g schedule. Certainly we&#39;ve found</div><div>that to be true for many of=
 the drafts I am working on (JSEP and TLS in</div><div>particular), even th=
ough we use Github.</div><div><br></div><div>I&#39;d certainly be intereste=
d in seeing some evidence that Github drafts come</div><div>out less freque=
ntly than ones that didn&#39;t use Github.</div><div><br></div><div><br></d=
iv><div>2. Changelog quaity varies, of course, and AFAIK there&#39;s no act=
ual requirement</div><div>to do a Changelog, but my experience is that the =
Github drafts actually do a</div><div>somewhat better job of Changelogs, pr=
obably because the tooling encourages</div><div>you to package things up in=
 a way that makes it easy to do a ChangeLog. This</div><div>is especially t=
rue if you use PRs because then you can easily go back and</div><div>look a=
t every merged PR and that becomes the input to the ChangeLog.</div><div>He=
re, for example, is the TLS ChangeLog.</div><div><a href=3D"https://tlswg.g=
ithub.io/tls13-spec/#rfc.section.1.2">https://tlswg.github.io/tls13-spec/#r=
fc.section.1.2</a><br></div><div><br></div><div><br></div><div>I think what=
 *is* fair to say is that Github enables a far richer interaction model</di=
v><div>(Patrick alluded to this as well) with the result that it highlights=
 the relative</div><div>poverty of the old occasional draft model, but that=
&#39;s not because that model</div><div>has suddenly gotten absolutely wors=
e, just that there are now better tools</div><div>available and people are =
taking advantage of them.</div><div><br></div><div>-Ekr</div><div><br></div=
><div><br></div><div><br></div><div>=C2=A0</div></div></div></div>

--f403045eb8ea06098f054a1c149a--


From nobody Mon Mar  6 20:07:39 2017
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A8EB129AEC for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 20:07:36 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwsMrIwzSLd9 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 20:07:35 -0800 (PST)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CABB129AE6 for <ietf@ietf.org>; Mon,  6 Mar 2017 20:07:35 -0800 (PST)
Received: by mail-yw0-x229.google.com with SMTP id o4so75044600ywd.3 for <ietf@ietf.org>; Mon, 06 Mar 2017 20:07:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=S4bshWtR3VSD9pqYmPCOW5aXmfs2w1ZKHtOio3OsS/M=; b=helM6LSwOLUVm8yTvGaUS3UQtfSpN4FAuD6NK4LpW3cs5F4xoDdqSVbNjshT7aE0+H dg8rdNkUYEKw+5x+M1s2rqFWnjuS/KqBOVP7qRt0+7PUITWas5/R1Y3VRgCzX330o5fS Qogj/PxW/pcVyPfr5C/3P8O3MB2bHpGwISN5MCPt0vjGY02Bw9mC/9oZGjYd0CObcIiw 8n4rXo14plSG+tDmC6hv585hn56Ld558DuMS8Lty6TZxEqyCjnvMXWDHVArtVK2oh6yZ 3rMqzP1NMYwjVmNZhaLNkgIkjvhXBFCIfgfFJRBzVZa4+dyIpJlc0TVb4ZcDH7qbV5PO ryYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=S4bshWtR3VSD9pqYmPCOW5aXmfs2w1ZKHtOio3OsS/M=; b=IDzgst99XEp0lw27/f2VO0mST5yMa0lAyQ3HX96j7fYAz81p5BjGkjSPP7gm9j5zzO iQXRT1jhXl4dLCR7Mx+PQvt1xD37QcLsTKxf49YFMrqg5mYnxV1FeiUlf2jYzzfxyzUG 7XtScfffttkRq9AzO1ZRaL92KK1VADEYp7vcSVZWFwnOXQtlna25u/9VMzt1dW5ZwC2R Ylryewf/ObCCWkEGOJf5AQQvJcd/LfVfvLTrDI2hUDcKChpvRGqA8pZa9Cg8cOhEvvfL IWF84dqWmUXQggEzITxlEcrwTxP4zyevnsaG+ZvM6IQb2Pdulc0bo+ZY7vEn06Upwk0y 99Zg==
X-Gm-Message-State: AMke39lrgmwpN2eOpKjwWrG01JG49mjQgs2jblFFzzZL/Ogz3lGPuNhpoHzdSUitVxX6PO0ngjCagRLyy5VQ9g==
X-Received: by 10.129.152.22 with SMTP id p22mr15519709ywg.276.1488859654591;  Mon, 06 Mar 2017 20:07:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.154.210 with HTTP; Mon, 6 Mar 2017 20:06:53 -0800 (PST)
In-Reply-To: <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com> <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 6 Mar 2017 20:06:53 -0800
Message-ID: <CABcZeBPH6Y+EdbSfPMH-Rs_k5ZDwKb=13ZOGcWbi_TYJpdpsBQ@mail.gmail.com>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c0b8fb4d52a8c054a1c2660
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N_zTeStR2AdvKJ2uJ0-hIeEUtxA>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 04:07:36 -0000

--94eb2c0b8fb4d52a8c054a1c2660
Content-Type: text/plain; charset=UTF-8

On Wed, Mar 1, 2017 at 11:24 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:
>
> > I'm not arguing against updating data tracker more often - just saying
> this
> > 'editor's draft' convention can work very well between official revisions
> > no matter the cadence a WG chooses.
>
> The details of that discussion probably belong on ietf-and-github@ietf.org
> ,
> but I must point out that this way of working *excludes* from the
> discussion WG participants who don't grok github. Substantial issues
> need to be discussed on the mailing list and substantial (non-typo)
> revisions need to be posted as I-Ds.
>

Well, it's hard to know what to make of this without knowing what you
mean by "substantial" but an active draft takes literally hundreds of PRs
in its lifetime with perhaps half of those being non-typos. We could of
course gateway every PR merge to an IETF draft push. Is that what you're
looking for?

It seems to me that some of the benefit of having discrete draft revisions
is that they represent coherent checkpoints, but you totally lose that if
you treat each commit or merged PR as a co-equal revision.

-Ekr


>     Brian
>
>

--94eb2c0b8fb4d52a8c054a1c2660
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Mar 1, 2017 at 11:24 AM, Brian E Carpenter <span dir=3D"ltr">&l=
t;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.=
carpenter@gmail.com</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v class=3D"HOEnZb"><div class=3D"h5">
&gt; I&#39;m not arguing against updating data tracker more often - just sa=
ying this<br>
&gt; &#39;editor&#39;s draft&#39; convention can work very well between off=
icial revisions<br>
&gt; no matter the cadence a WG chooses.<br>
<br>
</div></div>The details of that discussion probably belong on <a href=3D"ma=
ilto:ietf-and-github@ietf.org">ietf-and-github@ietf.org</a>,<br>
but I must point out that this way of working *excludes* from the<br>
discussion WG participants who don&#39;t grok github. Substantial issues<br=
>
need to be discussed on the mailing list and substantial (non-typo)<br>
revisions need to be posted as I-Ds.<br></blockquote><div><br></div><div>We=
ll, it&#39;s hard to know what to make of this without knowing what you=C2=
=A0</div><div>mean by &quot;substantial&quot; but an active draft takes lit=
erally hundreds of PRs</div><div>in its lifetime with perhaps half of those=
 being non-typos. We could of</div><div>course gateway every PR merge to an=
 IETF draft push. Is that what you&#39;re</div><div>looking for?</div><div>=
<br></div><div>It seems to me that some of the benefit of having discrete d=
raft revisions</div><div>is that they represent coherent checkpoints, but y=
ou totally lose that if</div><div>you treat each commit or merged PR as a c=
o-equal revision.</div><div><br></div><div>-Ekr<br></div><div><br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0 Brian<br>
<br>
</font></span></blockquote></div><br></div></div>

--94eb2c0b8fb4d52a8c054a1c2660--


From nobody Mon Mar  6 20:20:23 2017
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 ED9B9129AF2 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 20:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7rdEHDD4mSkk for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 20:20:18 -0800 (PST)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C340A129AF0 for <ietf@ietf.org>; Mon,  6 Mar 2017 20:20:18 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id o126so22041960pfb.3 for <ietf@ietf.org>; Mon, 06 Mar 2017 20:20:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=vgyCm5KO0iTEanfUzl1cz/2jLZFpJGXkQz5/+XwLxTA=; b=eHdeZHONN3PXtIaCvfCQ9t2PbxiAaHDNU9La8jcdhtcgYfHsbS+m4YL6GjNgw7k1Nz haesFBqPxIDfwbS9oRalMx6jBjBG/LN7/Dow5SwzV854ZFsFsGB1awxS2wXHVEbWR6Cb 3qu9wRyDzuzISiRSlNEOyub1nVIna5PfzmPCI5rLT3cjv2NwQdQVGLQfRrLkIcRlto9S 7ZOyzEIZrx4LDwpYX6wjMs4eXbdWXfDrKnr/K/hrigl0fDrX0ztd6kaM4srJ39jaR1w1 DPQE/iuTnyf6YRRNrNjYAlnzsiS/BDfoBJw8alHDH3qnI9kxjogNxJ2w3Geqr27uf7Ln RThQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=vgyCm5KO0iTEanfUzl1cz/2jLZFpJGXkQz5/+XwLxTA=; b=tG2um1GRZa6RkBXSaq2BjAvLSCSAY3ze0LGR1dpDrtoJRO4Zsb2RlNounFmBMa5sbC jRLNQtrkuTBM2/4bQ6NGoSpPu8NsQqJYlzKkMCMYG6JiyVNdn7KaTl72vLORcZP7DSn+ V3sCJbhQUmGRAOUw9poqwWBDkYZN+8G8Uf4Jl53A+8pRyJpAIF+MZoqknl+hnRub3KM1 sQuvjjhCT6CBJSwzx+MhUTD0+eOguzgjOFCO0UK9xofdzmsWIFUsXjJUDPYGeh12Z3zS B9LnGkuEZ3i9M6ZuMP7RYrjZDS2neoBC0pBD6N+00Ukz09l0kzvE/7x2graEOhVBdpEL 5OoQ==
X-Gm-Message-State: AMke39lhP3aVeVZo8zlqRzlrcfsFLusaZYanhhOpJhpMBB/wwM1eV8JOWbq12ZrFejwm7A==
X-Received: by 10.84.141.129 with SMTP id 1mr31619614plv.166.1488860418380; Mon, 06 Mar 2017 20:20:18 -0800 (PST)
Received: from [192.168.178.23] ([118.148.79.158]) by smtp.gmail.com with ESMTPSA id p4sm42533327pgd.50.2017.03.06.20.20.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Mar 2017 20:20:17 -0800 (PST)
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Eric Rescorla <ekr@rtfm.com>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com> <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com> <CABcZeBPH6Y+EdbSfPMH-Rs_k5ZDwKb=13ZOGcWbi_TYJpdpsBQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <480b22e4-bf25-01fa-87fe-f91bc68940f8@gmail.com>
Date: Tue, 7 Mar 2017 17:20:15 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBPH6Y+EdbSfPMH-Rs_k5ZDwKb=13ZOGcWbi_TYJpdpsBQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EVFn0n-gCwIRySk_KrFK5DYHljM>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 04:20:20 -0000

On 07/03/2017 17:06, Eric Rescorla wrote:
> On Wed, Mar 1, 2017 at 11:24 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>>
>>> I'm not arguing against updating data tracker more often - just saying
>> this
>>> 'editor's draft' convention can work very well between official revisions
>>> no matter the cadence a WG chooses.
>>
>> The details of that discussion probably belong on ietf-and-github@ietf.org
>> ,
>> but I must point out that this way of working *excludes* from the
>> discussion WG participants who don't grok github. Substantial issues
>> need to be discussed on the mailing list and substantial (non-typo)
>> revisions need to be posted as I-Ds.
>>
> 
> Well, it's hard to know what to make of this without knowing what you
> mean by "substantial" but an active draft takes literally hundreds of PRs
> in its lifetime with perhaps half of those being non-typos. We could of
> course gateway every PR merge to an IETF draft push. Is that what you're
> looking for?

No. In fact (countering Michael's point slightly) I get quite annoyed
by draft versions that turn out only to fix few typos or grammatical errors;
those can wait. As for what constitutes "substantial", that's very subjective.
Anything that causes an on-the-wire protocol change would certainly be
substantial. Clarifying ambiguous text might be substantial. But YMMV.

> It seems to me that some of the benefit of having discrete draft revisions
> is that they represent coherent checkpoints, but you totally lose that if
> you treat each commit or merged PR as a co-equal revision.

Yes, I agree.

    Brian


From nobody Mon Mar  6 20:29:04 2017
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C3C41293E9 for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 20:29:03 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1v86rXW4qVRj for <ietf@ietfa.amsl.com>; Mon,  6 Mar 2017 20:29:02 -0800 (PST)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9078126D73 for <ietf@ietf.org>; Mon,  6 Mar 2017 20:29:01 -0800 (PST)
Received: by mail-yw0-x22b.google.com with SMTP id v76so37305084ywg.0 for <ietf@ietf.org>; Mon, 06 Mar 2017 20:29:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Yebf6btEt5lJ1rFcpIUt6G1b+h5Oa4uHKtkKaX+FWMM=; b=1QfpWAw6kyj/6PDu/XZZbvDBAkMpBajdbY9ixq4Id70wQx4OkBwZkIPxfAe/Zpqsj+ V3EzkSf1O9WWuUdI/6c51E8rS28UTL8muUsJObQtfeCyldqBcjy3NG/Y62S2uLw3D4Fy GiFjXysRw5nKkQAS/DpOOUaQ17LWjauujXUH694HeFCRZt86cUFjUa+8BFC9RQgfquGB G1tmOmEk0awarB9ZO2EBF/WifxK+WDJf6POasSjrri/Ef1fwFDOAMBuXhXnoTe1dTm+F DUQ1HoEdyT+ccU26myX3yTk3xGp5tkq93g86I6icQBSSm50/J6q4x8b9Qwc015FWm6J7 xX4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Yebf6btEt5lJ1rFcpIUt6G1b+h5Oa4uHKtkKaX+FWMM=; b=Vo1Uy+JDXecBxrYuqV9Au7TJDJ715YH26ZMYkL1oNHrYhb+1RsrmGAFzulq9H9bVGm mMzc5HzYZSFuG1ThwiosEZ8GxtqJyxQCZJwY6agScFIH/AHEMa5d1dVq08DZFlLItjZV Qi4wlU8NMhPP9TVo2BwnHbpnd8PRND2pRyTOwI9qQ6gbPEinuo8Jw56KCMaQzNX1BXlZ l+q3KYnpEwO053kbK1j/Ye3xTP8/ZYrD6qKhiVc/3T1q9Ofdg+KHgG3SrpyWD/rMRzPF LO/JGKHGBzWFThUZtNSapwTz0Xi6L+xNsPC8a2AntshB2GTGnTc3u9zE3iyjC5V5pr4W gJAQ==
X-Gm-Message-State: AMke39lpn24YHWUfkcHIbyP8xkZzA6gpUxR8py0ocuuxEv2wft/YOMz5tXQKWc1okE+o0+6rc4uj6JH1lsut6A==
X-Received: by 10.13.240.196 with SMTP id z187mr14348642ywe.337.1488860941100;  Mon, 06 Mar 2017 20:29:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.154.210 with HTTP; Mon, 6 Mar 2017 20:28:20 -0800 (PST)
In-Reply-To: <480b22e4-bf25-01fa-87fe-f91bc68940f8@gmail.com>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com> <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com> <CABcZeBPH6Y+EdbSfPMH-Rs_k5ZDwKb=13ZOGcWbi_TYJpdpsBQ@mail.gmail.com> <480b22e4-bf25-01fa-87fe-f91bc68940f8@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 6 Mar 2017 20:28:20 -0800
Message-ID: <CABcZeBNuXUypKkDwY1PXzfpTub+=OhTLBLfdEiwNPaBdKuP12g@mail.gmail.com>
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c034eb083bee3054a1c73e2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1kUEicTDabJiOyQAn-vj4QopX5Y>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 04:29:03 -0000

--94eb2c034eb083bee3054a1c73e2
Content-Type: text/plain; charset=UTF-8

On Mon, Mar 6, 2017 at 8:20 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 07/03/2017 17:06, Eric Rescorla wrote:
> > On Wed, Mar 1, 2017 at 11:24 AM, Brian E Carpenter <
> > brian.e.carpenter@gmail.com> wrote:
> >>
> >>> I'm not arguing against updating data tracker more often - just saying
> >> this
> >>> 'editor's draft' convention can work very well between official
> revisions
> >>> no matter the cadence a WG chooses.
> >>
> >> The details of that discussion probably belong on
> ietf-and-github@ietf.org
> >> ,
> >> but I must point out that this way of working *excludes* from the
> >> discussion WG participants who don't grok github. Substantial issues
> >> need to be discussed on the mailing list and substantial (non-typo)
> >> revisions need to be posted as I-Ds.
> >>
> >
> > Well, it's hard to know what to make of this without knowing what you
> > mean by "substantial" but an active draft takes literally hundreds of PRs
> > in its lifetime with perhaps half of those being non-typos. We could of
> > course gateway every PR merge to an IETF draft push. Is that what you're
> > looking for?
>
> No. In fact (countering Michael's point slightly) I get quite annoyed
> by draft versions that turn out only to fix few typos or grammatical
> errors;
> those can wait. As for what constitutes "substantial", that's very
> subjective.
> Anything that causes an on-the-wire protocol change would certainly be
> substantial. Clarifying ambiguous text might be substantial. But YMMV.
>

But this would still lead to a colossal number of drafts. It's easy to see
this by
looking at recent versions of TLS, where I have handily noted all
on-the-wire
changes in the changelog (or at least tried to). Here are the numbers from
recent drafts:

Draft               Wire changes
-19 (unpublished)   5
-18                 1
-17                 9
-16                 6
-15                 5
-14                 5

As you can see, we have an average of 5 wire-level changes per revision,
so given that we are at draft-19, we would be at around draft-100 by now.
Probably more, because we were more aggressive earlier, and I just
started noting these because people were fielding implementations and
I wanted to make it easier to update. I find it hard to believe that people
would in fact be happier if TLS 1.3 were currently at -100 and to the
best of my knowledge, next to no WG has every produced drafts
at anything like that frequency.

Note that I'm not saying that TLS is especially active (though I suspect
it is more than average). Rather, people (both with and without Github)
tend to batch up a bunch of changes and submit them in a single draft.
It's just that because Github makes the revision history so public and
explicit that people are aware of these as discrete events where you
could publish as individual drafts, rather than as a pile of things that
go into a single draft.

-Ekr

--94eb2c034eb083bee3054a1c73e2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Mar 6, 2017 at 8:20 PM, Brian E Carpenter <span dir=3D"ltr">&lt=
;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.c=
arpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><span class=3D"gmail-">On 07/03/2017 17:06, Eric Rescorl=
a wrote:<br>
&gt; On Wed, Mar 1, 2017 at 11:24 AM, Brian E Carpenter &lt;<br>
&gt; <a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail=
.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; I&#39;m not arguing against updating data tracker more often -=
 just saying<br>
&gt;&gt; this<br>
&gt;&gt;&gt; &#39;editor&#39;s draft&#39; convention can work very well bet=
ween official revisions<br>
&gt;&gt;&gt; no matter the cadence a WG chooses.<br>
&gt;&gt;<br>
&gt;&gt; The details of that discussion probably belong on <a href=3D"mailt=
o:ietf-and-github@ietf.org">ietf-and-github@ietf.org</a><br>
&gt;&gt; ,<br>
&gt;&gt; but I must point out that this way of working *excludes* from the<=
br>
&gt;&gt; discussion WG participants who don&#39;t grok github. Substantial =
issues<br>
&gt;&gt; need to be discussed on the mailing list and substantial (non-typo=
)<br>
&gt;&gt; revisions need to be posted as I-Ds.<br>
&gt;&gt;<br>
&gt;<br>
&gt; Well, it&#39;s hard to know what to make of this without knowing what =
you<br>
&gt; mean by &quot;substantial&quot; but an active draft takes literally hu=
ndreds of PRs<br>
&gt; in its lifetime with perhaps half of those being non-typos. We could o=
f<br>
&gt; course gateway every PR merge to an IETF draft push. Is that what you&=
#39;re<br>
&gt; looking for?<br>
<br>
</span>No. In fact (countering Michael&#39;s point slightly) I get quite an=
noyed<br>
by draft versions that turn out only to fix few typos or grammatical errors=
;<br>
those can wait. As for what constitutes &quot;substantial&quot;, that&#39;s=
 very subjective.<br>
Anything that causes an on-the-wire protocol change would certainly be<br>
substantial. Clarifying ambiguous text might be substantial. But YMMV.<br><=
/blockquote><div><br></div><div>But this would still lead to a colossal num=
ber of drafts. It&#39;s easy to see this by</div><div>looking at recent ver=
sions of TLS, where I have handily noted all on-the-wire</div><div>changes =
in the changelog (or at least tried to). Here are the numbers from</div><di=
v>recent drafts:</div><div><br></div><div><div>Draft =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Wire changes</div><div>-19 (unpublished) =C2=A0=
 5</div><div>-18 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1<=
/div><div>-17 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 9</di=
v><div>-16 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 6</div><=
div>-15 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 5</div><div=
>-14 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 5</div></div><=
div><br></div><div>As you can see, we have an average of 5 wire-level chang=
es per revision,<br></div><div>so given that we are at draft-19, we would b=
e at around draft-100 by now.</div><div>Probably more, because we were more=
 aggressive earlier, and I just</div><div>started noting these because peop=
le were fielding implementations and</div><div>I wanted to make it easier t=
o update. I find it hard to believe that people</div><div>would in fact be =
happier if TLS 1.3 were currently at -100 and to the</div><div>best of my k=
nowledge, next to no WG has every produced drafts</div><div>at anything lik=
e that frequency.</div><div><br></div><div>Note that I&#39;m not saying tha=
t TLS is especially active (though I suspect</div><div>it is more than aver=
age). Rather, people (both with and without Github)</div><div>tend to batch=
 up a bunch of changes and submit them in a single draft.</div><div>It&#39;=
s just that because Github makes the revision history so public and</div><d=
iv>explicit that people are aware of these as discrete events where you</di=
v><div>could publish as individual drafts, rather than as a pile of things =
that</div><div>go into a single draft.</div><div><br></div><div>-Ekr</div><=
div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><=
/div></div></div>

--94eb2c034eb083bee3054a1c73e2--


From nobody Mon Mar  6 23:32:06 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BEA6129416; Mon,  6 Mar 2017 23:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level: 
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e74YwzWNY33J; Mon,  6 Mar 2017 23:32:01 -0800 (PST)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFA30129401; Mon,  6 Mar 2017 23:32:00 -0800 (PST)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 501576026E; Tue,  7 Mar 2017 08:31:59 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.10]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 2650616005E; Tue,  7 Mar 2017 08:31:59 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5C.corporate.adroot.infra.ftgroup ([fe80::4bd:9b2b:3651:6fba%19]) with mapi id 14.03.0319.002; Tue, 7 Mar 2017 08:31:57 +0100
From: <mohamed.boucadair@orange.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: RE: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Topic: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Index: AQHSlp0xr2f4mwtGUUmrdlwH+5hF7qGI6XpA
Date: Tue, 7 Mar 2017 07:31:56 +0000
Message-ID: <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com> <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup> <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com>
In-Reply-To: <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_a9787ef7734b49a48590b793272893d7OPEXCLILM5Ccorporateadr_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NGradLicyWWQxkBUwjN3zWblv34>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 07:32:04 -0000

--_000_a9787ef7734b49a48590b793272893d7OPEXCLILM5Ccorporateadr_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgVGVkLA0KDQpUaGFuayB5b3UgZm9yIHRoZSBhbnN3ZXJzLg0KDQpQbGVhc2Ugc2VlIGlubGlu
ZS4NCg0KQ2hlZXJzLA0KTWVkDQoNCkRlIDogVGVkIEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdt
YWlsLmNvbV0NCkVudm95w6kgOiBsdW5kaSA2IG1hcnMgMjAxNyAxODoxNA0Kw4AgOiBCT1VDQURB
SVIgTW9oYW1lZCBJTVQvT0xODQpDYyA6IGlldGZAaWV0Zi5vcmc7IGRyYWZ0LWhhcmRpZS1wcml2
c2VjLW1ldGFkYXRhLWluc2VydGlvbkBpZXRmLm9yZw0KT2JqZXQgOiBSZTogTGFzdCBDYWxsOiA8
ZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRhdGEtaW5zZXJ0aW9uLTA1LnR4dD4gKERlc2lnbiBj
b25zaWRlcmF0aW9ucyBmb3IgTWV0YWRhdGEgSW5zZXJ0aW9uKSB0byBJbmZvcm1hdGlvbmFsIFJG
Qw0KDQpIaSBNb2hhbWVkLA0KUmVwbGllcyBpbi1saW5lLg0KDQoNCk9uIE1vbiwgTWFyIDYsIDIw
MTcgYXQgMTo0OCBBTSwgPG1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb208bWFpbHRvOm1vaGFt
ZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20+PiB3cm90ZToNCg0KDQrigKIgICAgICAgICBBIEZvcndh
cmQtRm9yIGhlYWRlciBpbnNlcnRlZCBieSBhIHByb3h5IGRvZXMgbm90IHJlc3RvcmUgYW55IGRh
dGE7IGl0IGRvZXMgb25seSByZXZlYWwgZGF0YSB0aGF0IGlzIGFscmVhZHkgcHJlc2VudCBpbiB0
aGUgcGFja2V0IGlzc3VlZCBieSB0aGUgY2xpZW50IGl0c2VsZi4NClRoYXQncyB3aGF0IHJlc3Rv
cmUgbWVhbnMgaGVyZS4NCltNZWRdIFRoZW4sIHRoaXMgbmVlZHMgdG8gYmUgZGVmaW5lZCBpbiB0
aGUgZG9jdW1lbnQuIEkgbmFpdmVseSBhc3N1bWVkIHRoYXQg4oCccmVzdG9yZWTigJ0gaXMgdXNl
ZCB0byBtZWFuIGFueSBwaWVjZSBvZiBpbmZvcm1hdGlvbiB0aGF0IHRoZSBjbGllbnQgZG9lcyBu
b3Qgd2FudCB0byBpbnNlcnQgaW4gYSBwYWNrZXQsIGJ1dCBhbiBvbi1wYXRoIGRldmljZSBkZWNp
ZGVzIHRvIGluamVjdCBpdCBkZXNwaXRlIHRoZXJlIGlzIG5vIGNvbnNlbnQgZnJvbSB0aGUgY2xp
ZW50Lg0KV2hhdCB5b3UgYXJlIGRlc2NyaWJpbmcgaXMgbW9yZSBhYm91dCDigJxtYWludGFpbmlu
Z+KAnSBvciDigJxwcmVzZXJ2aW5n4oCdIGluZm9ybWF0aW9uIG5vdCByZXN0b3JpbmcgaXQuDQoN
ClRoZSBjb21tb24gdXNlcyBvZiByZXN0b3JlIGluIEVuZ2xpc2ggYWxsIGZvY3VzIG9uIHB1dHRp
bmcgc29tZXRoaW5nIGJhY2sgdGhhdCBoYXMgYmVlbiBsb3N0LA0KW01lZF0gQnV0IHRoYXQgaW5m
b3JtYXRpb24gaXMgbm90IGxvc3QgZm9yIGFuIG9uLXBhdGggZGV2aWNlIHRoYXQgZW5jYXBzdWxh
dGVzIGEgcGFja2V0IGluIGFub3RoZXIgb25lIChzbyB0aGUgaW5uZXIgaGVhZGVyIGlzIHN0aWxs
IGNhcnJ5aW5nIHRoZSBzb3VyY2UgSVAgYWRkcmVzcykgb3IgdGhlIG9uZSB0aGF0IHN1cHBsaWVz
IHRoZSBvcmlnaW5hbCBzb3VyY2UgSVAgYWRkcmVzcyBhcyBhIG1ldGFkYXRhIHdoZW4gc291cmNl
IElQIGFkZHJlc3MvcG9ydCByZXdyaXRpbmcgaXMgcmVxdWlyZWQuIFRoZSBub3Rpb24gb2Yg4oCc
cHV0dGluZyBiYWNr4oCdIGRvZXMgbm90IG1ha2Ugc2Vuc2UgdG8gbWUgYmVjYXVzZSB3ZSBhcmUg
bm90IGRlYWxpbmcgd2l0aCB0aGUgaW50ZXJuYWwgcHJvY2Vzc2luZyBvZiBhIHBhY2tldCB3aXRo
aW4gYW4gb24tcGF0aCBkZXZpY2UsIGJ1dCB3ZSBvbmx5IGZvY3VzIG9uIHRoZSBleHRlcm5hbCBi
ZWhhdmlvci4gVGhpcyBpcyBleGFjdGx5IHRoZSByb2xlIG9mIOKAnHZpYeKAnSBoZWFkZXJzIGZv
ciBTSVAgcHJveGllczsgd2hlbiB0aGVyZSBpcyBhIG1pc21hdGNoIHRoZSByZWNlaXZlZCB0YWcg
aXMgY29tcGxldGVkIHdpdGggdGhlIHZpc2libGUgc291cmNlIGFkZHJlc3MuDQoNCnNvIEkgYmVs
aWV2ZSByZXN0b3JlIGlzIGJldHRlciB0aGFuICJtYWludGFpbiIgb3IgInByZXNlcnZlIiwgd2hp
Y2ggaW1wbHkgc29tZXRoaW5nIGlzIGJlaW5nIGNhcnJpZWQgZm9yd2FyZCBhcy1pcywgcmF0aGVy
IHRoYW4gYmVpbmcgcHV0IGJhY2sgYWZ0ZXIgbG9zcy4NCltNZWRdIFBsZWFzZSBzZWUgYWJvdmUu
IEJlY2F1c2Ugd2UgZG9u4oCZdCBoYXZlIGEgc3RhbmRhcmQgYmVoYXZpb3Igb2YgYW4gb24tcGF0
aCBkZXZpY2UgKHByb3h5LCB0dW5uZWwtZW5kcG9pbnQuKSwgSSBzZWVtcyB3ZWlyZCB0byBtZSB0
byBzYXkgdGhhdCBhIHByb3h5IHRoYXQgcHJlc2VydmVzIHRoZSBzb3VyY2UgSVAgYWRkcmVzcyBp
cyDigJxwdXR0aW5nIHBhY2sgYW4gaW5mb3JtYXRpb24gdGhhdCBpcyBsb3N04oCdLg0KDQoNCiAg
SWYgdGhlIGluZm9ybWF0aW9uIGlzIHByZXNlbnQgYXMgbWV0YWRhdGEgaW4gdGhlIHBhY2tldCBz
ZW50IHRvIHRoZSBwcm94eSBidXQgd291bGQgYmUgYWJzZW50IGFzIG1ldGFkYXRhIHVuZGVyIG5v
cm1hbCBvcGVyYXRpb24gb2YgdGhlIHByb3h5LCBhZGRpbmcgaXQgYmFjayBpbiBzb21ld2hlcmUg
ZWxzZSByZXN0b3JlcyB0aGUgbWV0YWRhdGEuDQpbTWVkXSDigJxub3JtYWwgb3BlcmF0aW9uIG9m
IHByb3h54oCdIGlzIG5vdCBhIHN0YW5kYXJkLiBBIOKAnG5vcm1hbCBvcGVyYXRpb24gb2YgcHJv
eHnigJ0gd291bGQgYmUgdG8gbWFpbnRhaW4gdGhlIGluZm9ybWF0aW9uIHNlbnQgYnkgdGhlIGNs
aWVudCB3aGVuIHJlbGF5aW5nIGl0IHRvIHRoZSBzZXJ2ZXIuIEnigJltIHN1cmUgeW91IGtub3cg
Zm9yIGluc3RhbmNlIHRoYXQgU0lQIEIyQlVBcyBjYW4gZG8gd2hhdGV2ZXIgdGhleSB3YW50IQ0K
DQpZb3UncmUgcmlnaHQgdGhhdCB0aGUgbm9ybWFsIG9wZXJhdGlvbiBvZiBhIHByb3h5IGlzIG5v
dCBhIHN0YW5kYXJkLCBhbmQgSSBzaG91bGQgaGF2ZSBzYWlkICJ0aGUgbm9ybWFsIG9wZXJhdGlv
biBvZiB0aGUgcHJvdG9jb2xzIHVzZWQgYnkgYSBwcm94eSIuDQpbTWVkXSBUaGlzIGlzIG11Y2gg
YmV0dGVyLCBidXQgc3RpbGwgbm90IHN1ZmZpY2llbnQuIE9uLXBhdGggZGV2aWNlcyB0aGF0IG1h
bmlwdWxhdGUgcGFja2V0cyBtYXkgbm90IGJlIGEg4oCccHJvdG9jb2wtc3BlY2lmaWMgcHJveHni
gJ06IHR1bm5lbCBlbmRwb2ludCAoZS5nLiwgTElTUCksIENHTiAoTkFUNjQsIE5BVDQ0LCBEUy1M
aXRlKSwgTUFQLUUgQlIsIGV0Yy4NCg0KICBJZiB0aGUgYWN0aW9uIG9mIHRoZSBwcm94eSBpcyB0
byBzdGFydCBhIG5ldyBUQ1AgY29ubmVjdGlvbiB0byBhbiBvcmlnaW4gc2VydmVyLCBmb3IgZXhh
bXBsZSwgdGhlIG5vcm1hbCBvcGVyYXRpb24gb2YgVENQIGlzIHRvIHVzZSB0aGUgaW5pdGlhdG9y
J3MgSVAgYWRkcmVzcy4NCltNZWRdIFRoaXMgaXMgcHJvdG9jb2wtc3BlY2lmaWMuIEkgY2FuIHBy
b3ZpZGUgYW4gZXhhbXBsZSBvZiBhIHByb3h5IGJlaGF2aW9yIHRoYXQgcmVsYXlzIHRoZSBzb3Vy
Y2UgSVAgYWRkcmVzcy9wb3J0IGFzIHBhcnQgb2YgaXRzIG5vcm1hbCBvcGVyYXRpb246IGh0dHA6
Ly93d3cuaGFwcm94eS5vcmcvZG93bmxvYWQvMS44L2RvYy9wcm94eS1wcm90b2NvbC50eHQNCiAg
LSBUQ1AvSVB2NCA6DQogICAgICAiUFJPWFkgVENQNCAyNTUuMjU1LjI1NS4yNTUgMjU1LjI1NS4y
NTUuMjU1IDY1NTM1IDY1NTM1XHJcbiINCiAgICA9PiA1ICsgMSArIDQgKyAxICsgMTUgKyAxICsg
MTUgKyAxICsgNSArIDEgKyA1ICsgMiA9IDU2IGNoYXJzDQoNCiAgLSBUQ1AvSVB2NiA6DQogICAg
ICAiUFJPWFkgVENQNiBmZmZmOmYuLi5mOmZmZmYgZmZmZjpmLi4uZjpmZmZmIDY1NTM1IDY1NTM1
XHJcbiINCiAgICA9PiA1ICsgMSArIDQgKyAxICsgMzkgKyAxICsgMzkgKyAxICsgNSArIDEgKyA1
ICsgMiA9IDEwNCBjaGFycw0KDQoNCiAgVGhlIGxvc2VzIHRoZSBJUCBhZGRyZXNzIG9mIHRoZSBx
dWVyeWluZyBob3N0IGlzIGltcGxpZWQgYnkgdGhhdCBub3JtYWwgb3BlcmF0aW9uKGluIG90aGVy
IHdvcmRzLCBpdCBlbGlkZXMgbWV0YWRhdGEgYWJvdXQgYW55IGNsaWVudCB0aGF0IGNhdXNlZCB0
aGlzIG5ldyBUQ1AgY29ubmVjdGlvbiB0byBiZSBjcmVhdGVEKS4NCltNZWRdIFRoaXMgbWFrZXMg
c2Vuc2UgaWYgbG9zaW5nIHRoZSBvcmlnaW5hbCBJUCBhZGRyZXNzIGlzIGFuIGludGVuZGVkIHBy
b3ByaWV0eSBvZiB0aGUgcHJveHkuIEJ1dCB0aGlzIGNhbm5vdCBiZSBhIGdlbmVyYWxpemVkIHBy
b3h5IGJlaGF2aW9yIChzZWUgdGhlIGV4YW1wbGUgYWJvdmUpLg0KDQpTbyBvcmlnaW4gSVAgYWRk
cmVzcyBzdGFydHMgb3V0IGluIHRoZSBJUCBoZWFkZXIgb2YgdGhlIG9yaWdpbmFsIHBhY2tldCBi
dXQgZ2V0cyBwdXNoZWQgZnJvbSB0aGF0IHNsb3Qgd2hlbiB0aGUgcHJveHkgY29uc3RydWN0cyB0
aGUgb253YXJkIElQIHBhY2tldCB0byB0aGUgc2VydmVyLiAgRm9yIGl0IHRvIHJlYWNoIHRoZSBz
ZXJ2ZXIsIGl0IGhhcyB0byBiZSBwbGFjZWQgc29tZXdoZXJlIGVsc2UgaW4gdGhlIG9ud2FyZCBw
YWNrZXQsIHJlc3RvcmluZyB0aGUgbG9zdCBtZXRhZGF0YS4NCltNZWRdIFRoZSBjbGllbnQgYWdy
ZWVkIHRvIHNlbmQgcGFja2V0cyB3aXRoIGl0cyBzb3VyY2UgSVAgYWRkcmVzcyAod2hpY2ggbWVh
biBjb25zZW50KS4gV2h5IHRoZSBwcm94eSB3b3VsZCBuZWVkIHRvIGFuIGV4dHJhIGNoYW5uZWwg
dG8gZ2V0IGNvbnNlbnQgZm9yIHJlbGF5aW5nIHRoZSBzb3VyY2UgSVAgYWRkcmVzcyB0byBhIHNl
cnZlcj8NCg0KDQpCZWNhdXNlIHRoZSBjbGllbnQgYWdyZWVkIHRvIHNlbmQgcGFja2V0cyB0byB0
aGUgcHJveHkgYnkgcHV0dGluZyBpdCBpbiB0aGUgZGVzdGluYXRpb24NCltNZWRdIFRoZSBjbGll
bnQgaXMgbm90IGV2ZW4gYXdhcmUgdGhhdCBwcm94eSBleGlzdHMgb24gdGhlIHBhdGghIFBhY2tl
dHMgYXJlIHNlbnQgdG8gdGhlIHVsdGltYXRlIHNlcnZlcuKAmXMgYWRkcmVzcywgbm90IHRoZSBv
bmUgb2YgdGhlIHByb3h5LiBFdmVuIGZvciBTT01FIGNhc2VzIHdoZXJlIHBhY2tldHMgYXJlIHNl
bnQgZXhwbGljaXRseSB0byB0aGUgcHJveHkgKGUuZy4sIFNPQ0tTIHByb3h5KSwgYSBzdGF0ZSBp
cyBhbHJlYWR5IGluIHBsYWNlIHRvIGdyYWZ0IHRoZSBvdXRnb2luZyBwYWNrZXRzIHRvIGEgYmlu
ZGluZyBjb250ZXh0IGludm9sdmluZyB0aGUgZGVzdGluYXRpb24gc2VydmVyLg0KDQosIGFuZCBk
aWQgbm90IGFncmVlIHRvIGdlbmVyYWwgZGlzY2xvc3VyZTsgeW91IGNhbid0IGluZmVyIG9ud2Fy
ZCBjb25zZW50Lg0KW01lZF0gSG1t4oCmSeKAmW0gYWZyYWlkIHRoaXMgY29uY2x1c2lvbiBpcyBu
b3QgdGVjaG5pY2FsbHkgYmFja2VkLCBlLmcuLA0KKiBBIGNsaWVudCB0aGF0IHNlbmRzIHBhY2tl
dHMgdG8gYSBzZXJ2ZXIgbG9jYXRlZCBvbiB0aGUgSW50ZXJuZXQgaXMgTk9UIG5lY2Vzc2FyaWx5
IGF3YXJlIHRoYXQgYSBwcm94eSBpcyBzb2xpY2l0ZWQgaW4gZm9yd2FyZGluZyBwYXRoLiBQYWNr
ZXRzIGFyZSBzZW50IHVzaW5nIHRoZSBzZXJ2ZXLigJlzIElQIGFkZHJlc3MuDQoqIFRoZSBjbGll
bnQgYW5kIHByb3h5IG1heSBiZSBvd25lZCBieSB0aGUgc2FtZSBhZG1pbmlzdHJhdGl2ZSBlbnRp
dHkgKGNhc2Ugb2YgZW50ZXJwcmlzZSBuZXR3b3JrcykuIFRoYXQgZW50aXR5IGlzIHJlc3BvbnNp
YmxlIGZvciBlbnN1cmUgd2hpY2ggaW5mb3JtYXRpb24gdGhlIHByb3h5IG5lZWRzIHRvIGxlYWsu
DQoqIFRoZSBwcm94eSBhbmQgdGhlIHNlcnZlciBtYXkgYmUgb3duZWQgYnkgdGhlIHNhbWUgYWRt
aW5pc3RyYXRpdmUgZW50aXR5IChjb250ZW50IHByb3ZpZGVyKS4gU3VwcGx5aW5nIGRhdGEgYnkg
YSBwcm94eSB0byB0aGUgc2VydmVyLCBiYXNlZCBvbiB0aGUgY29udGVudCBvZiBhIHBhY2tldCBy
ZWNlaXZlZCBmcm9tIGEgaG9zdCwgZG9lcyBub3QgaW5kdWNlIGEgcHJpdmFjeSBjb25jZXJuIGhl
cmUgYmVjYXVzZSB0aGUgcHJveHkgYW5kIHRoZSBzZXJ2ZXIgb3duZWQgYnkgdGhlIHNhbWUgZW50
aXR5Lg0KDQpIYWQgaXQgYmVlbiBwcmVzZW50IGluIHRoZSBwYWNrZXQgYXMgaGVhZGVyIHZhbHVl
IGluIHRoZSBIVFRQIGV4Y2hhbmdlLCBpdCB3b3VsZCBub3QgaGF2ZSBiZWVuIHN0cmlwcGVkIGJ5
IG5vcm1hbCBvcGVyYXRpb24uICBUaGVyZSBwcm94eSBvcGVyYXRpb24gZm9yd2FyZGluZyBpdCBv
biB3b3VsZCBiZSBzaW1wbHkgcHJlc2VydmluZyBpdC4NCltNZWRdIFRoaXMgaXMgYW5vdGhlciBx
dWVzdGlvbjogd2hldGhlciB0aGUgc2FtZSBvciBkaXN0aW5jdCBjaGFubmVsIGNhbiBiZSB1c2Vk
IHRvIGNvbW11bmljYXRlIHRoZSBTQU1FIGRhdGEgdGhhdCB3YXMgcHJlc2VudCBpbiB0aGUgaW5p
dGlhbCBwYWNrZXQgaXNzdWVkIGJ5IGEgaG9zdC4NCg0KDQpUaGF0IGRlcGVuZHMgb24gdGhlIG5h
dHVyZSBvZiB0aGUgY2hhbm5lbC4gIE9idmlvdXNseSwgaWYgeW91IHNldCB0aGUgb3JpZ2luIGNs
aWVudHMgSVAgYWRkcmVzcyBhcyB0aGUgc291cmNlIGFkZHJlc3MsIHlvdSdyZSBnb2luZyB0byBn
ZXQgYSBkaWZmZXJlbnQgcmVzdWx0IGZyb20gdGhhdCBzcG9vZmluZyB0aGFuIHB1dHRpbmcgaXQg
aW4gYSBjbGllbnQgc3VibmV0IEVETlMgb3B0aW9uIG9yIGZvcndhcmRlZC1mb3IgaGVhZGVyLg0K
W01lZF0gQWdyZWUuDQoNCg0K4oCiICAgICAgICAgQW4gYWRkcmVzcyBzaGFyaW5nIGRldmljZSwg
dW5kZXIgZm9yIGV4YW1wbGUgRFMtTGl0ZSAoUkZDNjMzMyksIHRoYXQgaW5zZXJ0cyB0aGUgc291
cmNlIElQdjYgcHJlZml4IGluIHRoZSBUQ1AgSE9TVF9JRCBvcHRpb24gKFJGQzc5NzQpIGlzIG5v
dCBSRVNUT1JJTkcgYW55IGRhdGEuIFRoZSBjb250ZW50IG9mIHRoYXQgVENQIG9wdGlvbiBpcyBh
bHJlYWR5IHZpc2libGUgaW4gdGhlIHBhY2tldCBzZW50IGJ5IHRoZSBob3N0Lg0KSSBhZ3JlZSB3
aXRoIHRoZSBJRVNHIGFuYWx5c2lzIG9mIFJGQzc5NzQuICBJdCBkb2VzIHJlc3RvcmUgaW5mb3Jt
YXRpb24gYnkgdGFraW5nIGluZm9ybWF0aW9uIHdoaWNoIG5vcm1hbCBvcGVyYXRpb24gd291bGQg
aGF2ZSBlbGlkZWQgYW5kIHJlc3RvcmVzIGl0Lg0KW01lZF0gVGhlICBpbXBsaWNhdGlvbiBvZiB3
aGF0IHlvdSBhcmUgc2F5aW5nIGhlcmUgaXMgdGhhdCBwcm94aWVzIGFyZSBnb29kIGJlY2F1c2Ug
dGhleSBoaWRlIHRoZSBzb3VyY2UgSVAgYWRkcmVzc2VzIG9mIGhvc3QhDQoNCg0KQWdncmVnYXRp
bmcgcHJveGllcyBjYW4gaGF2ZSBhIHBvc2l0aXZlIHByaXZhY3kgaW1wYWN0LCB5ZXMuICBBbiBv
YnNlcnZlciBzZWVpbmcgdHJhZmZpYyBmcm9tIGFuIGFnZ3JlZ2F0aW5nIHByb3h5IHRvIHNlbnNp
dGl2ZS10b3BpYy5leGFtcGxlLmNvbTxodHRwOi8vc2Vuc2l0aXZlLXRvcGljLmV4YW1wbGUuY29t
PiBrbm93cyBvbmx5IHRoYXQgc29tZSB1c2VyIGJlaGluZCB0aGF0IHByb3h5IGlzIGxvb2tpbmcg
Zm9yIGluZm9ybWF0aW9uIG9uIHNlbnNpdGl2ZS10b3BpYy4gIFRvIGtub3cgd2hpY2ggdXNlciwg
dGhlIG9ic2VydmVyIG11c3QgaGF2ZSBlaXRoZXIgc3Vib3JuZWQgdGhlIHByb3h5IG9yIGhhdmUg
YSB3YXkgb2Ygb2JzZXJ2aW5nIHRyYWZmaWMgYmV0d2VlbiBob3N0cyBhbmQgdGhlIHByb3h5LiAg
Qm90aCBhcmUgbW9yZSBleHBlbnNpdmUgYW5kIGF0IGhpZ2hlciByaXNrIG9mIGRpc2NvdmVyeSB0
aGFuIGEgc2ltcGxlIHRhcCBuZWFyIHNlbnNpdGl2ZS10b3BpYy5leGFtcGxlLmNvbTxodHRwOi8v
c2Vuc2l0aXZlLXRvcGljLmV4YW1wbGUuY29tPi4NCg0KW01lZF0gVGhlIG1haW4gcG9pbnQgaGVy
ZSBpcyB0aGF0LCBldmVuIGluIHRoZSBwcmVzZW5jZSBvZiBhbiBhZ2dyZWdhdGluZyBwcm94eSwg
YSBzZXJ2ZXIgY2FuIGRlbXV4IHVzZXJzIGJ5IGNvcnJlbGF0aW5nIHZhcmlvdXMgaW5mb3JtYXRp
b24gbGVha2VkIGF0IHRoZSBhcHBsaWNhdGlvbiBsYXllciAoZS5nLiwgaHR0cHM6Ly9wYW5vcHRp
Y2xpY2suZWZmLm9yZy8pLiBUcmFja2luZyB0aG9zZSB1c2VycyB3aGVuIHRoZXkgY2hhbmdlIHRo
ZWlyIHNvdXJjZSBJUCBhZGRyZXNzIGlzIHBvc3NpYmxlIGluIHRoaXMgY2FzZSwgdG9vLg0KDQoN
CklmIHRoZSBkYXRhIGlzIHRha2VuIGZyb20gYSBwb3J0aW9uIG9mIHRoZSBwYWNrZXQgdGhhdCB3
b3VsZCBub3Qgbm9ybWFsbHkgYmUgZm9yd2FyZGVkIHRvIGFuIHVwc3RyZWFtIGhvc3QgYW5kIGFk
ZGVkIHRvIGEgcG9ydGlvbiB0aGF0IGlzIGZvcndhcmRlZCB0byBhbiB1cHN0cmVhbSBob3N0LCB0
aGVuIHRoZSBkZXZpY2UgYWRkaW5nIHRoZSBkYXRhIGJhY2sgaW4gc2hvdWxkIGtub3cgaXQgaXMg
YSByZXN0b3JhdGlvbi4NCltNZWRdIFRoYXQgZGVmaW5pdGlvbiBpcyBub3QgdHJpdmlhbCBhcyBt
ZW50aW9uZWQgYWJvdmUuIEkgd291bGQgdXNlIOKAnHByZXNlcnZl4oCdIG9yIOKAnG1haW50YWlu
4oCdIHJhdGhlciB0aGFuIOKAnHJlc3RvcmXigJ0uDQpQbGVhc2Ugc2VlIGFib3ZlLiAgIlJlc3Rv
cmUiIGlzIGNsb3NlciwgaW4gbXkgb3BpbmlvbiwgdGhhbiBlaXRoZXIgcHJlc2VydmUgb3IgbWFp
bnRhaW4uDQoNCg0KDQpJZiB0aGUgZW5kcG9pbnQgc2VuZHMgdGhlIGRhdGEsIGRhdGEgd2lsbCBi
ZSBjb25zaXN0ZW50bHkgYXZhaWxhYmxlIGluIHRoYXQgaGVhZGVyLiAgVGhlIGRhdGEgY2hhbmdl
cywgb2YgY291cnNlLg0KW01lZF0gSeKAmW0gbm90IHN1cmUgdG8gZm9sbG93IHlvdSBoZXJlLiBX
aGF0IGlzIG1lYW50IGJ5IOKAnGNvbnNpc3RlbnQgYXZhaWxhYmlsaXR54oCdIHRoZW4/IERvIHlv
dSBtZWFuIHRoZSBzYW1lIGNoYW5uZWwvcHJvY2VkdXJlIHRvIGNvbW11bmljYXRlIHRoZSBpbmZv
cm1hdGlvbj8gT3Ig4oCcY29uc2lzdGVudCBkYXRh4oCdPw0KDQpJIG1lYW4gdGhhdCBpZiB5b3Ug
ZGVmaW5lIGEgcHJvdG9jb2wgc3VjaCB0aGF0IGEgd2VsbC1mb3JtZWQgbWVzc2FnZSBmcm9tIHRo
ZSBjbGllbnQgaGFzIHRoZSBkYXRhIHRoZSBzZXJ2ZXIgbmVlZHMsIGl0IHdpbGwgYmUgY29uc2lz
dGVudGx5IGF2YWlsYWJsZS4gIElmIHlvdSByZWx5IG9uIGludGVybWVkaWF0ZSBuZXR3b3JrIGRl
dmljZXMgdG8gYWRkIHRoZSBkYXRhLCBpdCBtYXkgbm90IGJlIGF2YWlsYWJsZSBpZiB0aGVyZSBp
cyBub3QgY29vcGVyYXRpbmcgbmV0d29yayBkZXZpY2Ugb24gcGF0aCAoZS5nLiBpZiB0aGUgRE5T
IHJlc29sdmVyIGRvZXMgbm90IHN1cHBvcnQgdGhlIHJlbGV2YW50IEVETlMwIG9wdGlvbikuDQoN
CltNZWRdIFRoYW5rIHlvdS4gUGxlYXNlIGNsYXJpZnkgdGhpcyBpbiB0aGUgZHJhZnQuIEkgaGFk
IHRyb3VibGVzIHRvIHBhcnNlIHdoYXQgeW91IG1lYW50IGJ5IOKAnGNvbnNpc3RlbnQgYXZhaWxh
YmlsaXR54oCdLiBUaGF04oCZcyBzYWlkLCB0aGVyZSBtaWdodCBiZSBhbHNvIOKAnG5vdCBjb29w
ZXJhdGluZyBvbi1wYXRoIGRldmljZXPigJ0gdGhhdCBtYXkgc3RyaXAvYWx0ZXIgdGhlIGNvbnRl
bnQgb2YgY2xpZW50IHN1cHBsaWVkIGRhdGEgKGVhc3kgZm9yIEhUVFAgZm9yIGV4YW1wbGUpLg0K
DQoNCg0KW01lZF0gUmVzb3VyY2VzIG1heSBub3QgYmUgcmVzdHJpY3RlZCB0byBDUFUgb3IgZGlz
ayBidXQgbWF5IGJlIGdyYW50aW5nIGFjY2VzcyB0byB0aGUgc2VydmljZSAoZS5nLiwgZG93bmxv
YWQgYSBmaWxlIHdoZW4gYSBxdW90YSBwZXIgc291cmNlIGFkZHJlc3MgaXMgZW5mb3JjZWQpLiBJ
dCBjYW4gYmUgd2hhdGV2ZXIgdGhlIHNlcnZlcnMgY29uc2lkZXIgdG8gYmUgY3JpdGljYWwgZm9y
IHRoZW07IGl0IGlzIHVwIHRvIHRoZSB0YXN0ZSBvZiB0aGUgc2VydmljZSBkZXNpZ24gdG8gY2hh
cmFjdGVyaXplIGl0LiBUaGUgTkVXIHdvcmRpbmcgcHJvcG9zZWQgYWJvdmUgaXMgdGVjaG5pY2Fs
bHkgY29ycmVjdC4gUGxlYXNlIHJlY29uc2lkZXIgYWRkaW5nIGl0IHRvIHRoZSBkcmFmdC4NCg0K
DQoNCkkgZGlkIGNvbnNpZGVyIGl0LCBidXQgSSBjb250aW51ZSB0byBiZWxpZXZlIHRoYXQgaXQg
bW92ZXMgdGhlIG5lZWRsZSB0b28gZmFyIGludG8gc2ltcGxlIHNlcnZlciBwcmVmZXJlbmNlLiAg
SSByZXRhaW5lZCB0aGUgb3JpZ2luYWwgUFNBUCBsYW5ndWFnZSBpbiAtMDcgYXMgYSByZXN1bHQu
DQpbTWVkXSBlbWVyZ2VuY3kgaXMgb25seSBhbiBleGFtcGxlIDsgb3RoZXIgc2VydmljZXMgbWF5
IGV4aXN0IHRoYXQgaW1wb3NlIHRoZSBzYW1lIHRydXN0IG1vZGVsLg0KDQoNCkkgdGhpbmsgdGhl
cmUgaXMgYSBxdWFsaXRhdGl2ZSBkaWZmZXJlbmNlIGJldHdlZW4gc2l0dWF0aW9ucyBpbiB3aGlj
aCB0aGUgcmVzb3VyY2VzIGF0IHJpc2sgYXJlIGh1bWFuIGxpdmVzIGFuZCB0aG9zZSB3aGVyZSB0
aGV5IGFyZSBob3N0IHJlc291cmNlcy4NCltNZWRdIEkgYWdyZWUgd2l0aCB5b3UgYXMgYW4gaW5k
aXZpZHVhbC4gQnV0LCBpdCBpcyBub3QgdXAgdG8gdXMgdG8gbWFuZGF0ZSB0aGlzIGNvbmRpdGlv
biBmb3IgZXhlY3V0aW5nIHNlcnZpY2VzLiBJdCBpcyB1cCB0byB0aGUgKHByb3RvY29sKSBkZXNp
Z25lcnMvc2VydmljZSBwcm92aWRlcnMgdG8gZGVjaWRlIHdoYXQgaXMgY3JpdGljYWwva2V5IGZv
ciB0aGVpciBzZXJ2aWNlIG9wZXJhdGlvbi4NCiAgVGhhdCdzIHdoeSB0aGUgY2FydmUgb3V0IHdh
cyBsaW1pdGVkIGluIHRoZSBHRU9QUklWIGNhc2UuDQpbTWVkXSBHRU9QUklWIGlzIG5vdCB0aGUg
b25seSBwcm90b2NvbC9zZXJ2aWNlIHRoYXQgaXMgY29uY2VybmVkIHdpdGggaHVtYW4gbGl2ZXMs
IHdlIGNhbiBjb25zaWRlciB2ZWhpY3VsYXIgbmV0d29ya2luZyB0aGF0IHRydXN0IHRoZSBpbmZv
cm1hdGlvbiBzaGFyZWQgYnkgdGhlIGluZnJhc3RydWN0dXJlLiBJIHByZWZlciBuZXV0cmFsIHdv
cmRpbmcgdGhhdCBjaXRlcyBlbWVyZ2VuY3kgYXMgYW4gZXhhbXBsZS4NCg0KDQpJIGFsc28gYWRk
ZWQgYSBub3RlIGFib3V0IHlvdXIgZXh0ZW5zaXZlIHJldmlldy4gIFdoaWxlIHlvdSBhbmQgSSBj
bGVhcmx5IGhhdmUgc29tZSBkaWZmZXJlbmNlcyBvZiB2aWV3LCB0aGUgZG9jdW1lbnQgaGFzIGdv
dHRlbiBiZXR0ZXIgZnJvbSB5b3VyIGVuZ2FnZW1lbnQgd2l0aCBpdCwgYW5kIEkgYXBwcmVjaWF0
ZSB5b3VyIGVmZm9ydHMuDQpbTWVkXSBJIHJldmlld2VkIHRoZSAtMDcuIEFsdGhvdWdoIGl0IGlz
IGJldHRlciBjb21wYXJlZCB0byAtMDUsIEkgc3RpbGwgZG9u4oCZdCB0aGluayBpdCBpcyByZWFk
eSB0byBiZSBwdWJsaXNoZWQgYXMgaXQgaXMuIFRoYW5rIHlvdSBmb3IgeW91ciBlZmZvcnQuDQpB
bmQgdGhhbmsgeW91IGZvciB5b3VycywNCnJlZ2FyZHMsDQpUZWQNCg0KcmVnYXJkcywNClRlZA0K
DQo=

--_000_a9787ef7734b49a48590b793272893d7OPEXCLILM5Ccorporateadr_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgltc28tc3R5bGUtbGluazoiUHLDqWZvcm1hdMOpIEhUTUwgQ2FyIjsNCgltYXJnaW46
MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KcC5tLTYxOTQ2ODUwNTc1MzQzMTkyNjltNzc3MDcyMjI4
ODQyMzE1NzI0OW1zb2xpc3RwYXJhZ3JhcGgsIGxpLm0tNjE5NDY4NTA1NzUzNDMxOTI2OW03Nzcw
NzIyMjg4NDIzMTU3MjQ5bXNvbGlzdHBhcmFncmFwaCwgZGl2Lm0tNjE5NDY4NTA1NzUzNDMxOTI2
OW03NzcwNzIyMjg4NDIzMTU3MjQ5bXNvbGlzdHBhcmFncmFwaA0KCXttc28tc3R5bGUtbmFtZTpt
Xy02MTk0Njg1MDU3NTM0MzE5MjY5bTc3NzA3MjIyODg0MjMxNTcyNDltc29saXN0cGFyYWdyYXBo
Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207DQoJbXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQtc2l6ZToxMi4w
cHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpzcGFuLkVtYWls
U3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToi
Q291cmllciBOZXciOw0KCWNvbG9yOmJsYWNrOw0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250
LXN0eWxlOm5vcm1hbDt9DQpzcGFuLlByZm9ybWF0SFRNTENhcg0KCXttc28tc3R5bGUtbmFtZToi
UHLDqWZvcm1hdMOpIEhUTUwgQ2FyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0
eWxlLWxpbms6IlByw6lmb3JtYXTDqSBIVE1MIjsNCglmb250LWZhbWlseToiQ291cmllciBOZXci
Ow0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkZSO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHls
ZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7
DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3Np
emU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44
NXB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHls
ZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQi
IHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+
PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0
IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFk
Pg0KPGJvZHkgbGFuZz0iRlIiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFz
cz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJs
YWNrIj5IaSBUZWQsDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5UaGFu
ayB5b3UgZm9yIHRoZSBhbnN3ZXJzLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPlBsZWFzZSBzZWUgaW5saW5lLg0KPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJs
YWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkNoZWVycyw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPk1lZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVw
dDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNt
IDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+RGUmbmJzcDs6PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IFRlZCBI
YXJkaWUgW21haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jb21dDQo8YnI+DQo8Yj5FbnZvecOpJm5ic3A7
OjwvYj4gbHVuZGkgNiBtYXJzIDIwMTcgMTg6MTQ8YnI+DQo8Yj7DgCZuYnNwOzo8L2I+IEJPVUNB
REFJUiBNb2hhbWVkIElNVC9PTE48YnI+DQo8Yj5DYyZuYnNwOzo8L2I+IGlldGZAaWV0Zi5vcmc7
IGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbkBpZXRmLm9yZzxicj4NCjxi
Pk9iamV0Jm5ic3A7OjwvYj4gUmU6IExhc3QgQ2FsbDogJmx0O2RyYWZ0LWhhcmRpZS1wcml2c2Vj
LW1ldGFkYXRhLWluc2VydGlvbi0wNS50eHQmZ3Q7IChEZXNpZ24gY29uc2lkZXJhdGlvbnMgZm9y
IE1ldGFkYXRhIEluc2VydGlvbikgdG8gSW5mb3JtYXRpb25hbCBSRkM8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPkhpIE1vaGFtZWQsPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+UmVw
bGllcyBpbi1saW5lLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxicj4NCk9uIE1vbiwgTWFyIDYsIDIwMTcgYXQgMTo0OCBBTSwgJmx0OzxhIGhy
ZWY9Im1haWx0bzptb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tIiB0YXJnZXQ9Il9ibGFuayI+
bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxl
ZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1s
ZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20g
Ni4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGNt
O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4w
cHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJtLTYxOTQ2ODUwNTc1
MzQzMTkyNjltNzc3MDcyMjI4ODQyMzE1NzI0OW1zb2xpc3RwYXJhZ3JhcGgiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpTeW1ib2w7Y29sb3I6
YmxhY2siPsK3PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjcuMHB0
O2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsNCjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkEgRm9yd2Fy
ZC1Gb3IgaGVhZGVyIGluc2VydGVkIGJ5IGEgcHJveHkgZG9lcyBub3QgcmVzdG9yZSBhbnkgZGF0
YTsgaXQgZG9lcyBvbmx5IHJldmVhbCBkYXRhIHRoYXQgaXMgYWxyZWFkeSBwcmVzZW50IGluIHRo
ZSBwYWNrZXQgaXNzdWVkIGJ5IHRoZSBjbGllbnQgaXRzZWxmLjwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+VGhhdCdzIHdo
YXQgcmVzdG9yZSBtZWFucyBoZXJlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIFRoZW4sIHRoaXMg
bmVlZHMgdG8gYmUgZGVmaW5lZCBpbiB0aGUgZG9jdW1lbnQuIEkgbmFpdmVseSBhc3N1bWVkIHRo
YXQg4oCccmVzdG9yZWTigJ0gaXMgdXNlZA0KIHRvIG1lYW4gYW55IHBpZWNlIG9mIGluZm9ybWF0
aW9uIHRoYXQgdGhlIGNsaWVudCBkb2VzIG5vdCB3YW50IHRvIGluc2VydCBpbiBhIHBhY2tldCwg
YnV0IGFuIG9uLXBhdGggZGV2aWNlIGRlY2lkZXMgdG8gaW5qZWN0IGl0IGRlc3BpdGUgdGhlcmUg
aXMgbm8gY29uc2VudCBmcm9tIHRoZSBjbGllbnQuPC9zcGFuPiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGJsb2NrcXVvdGUgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzow
Y20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj5XaGF0IHlvdSBhcmUgZGVzY3JpYmluZyBpcyBtb3JlIGFib3V0
IOKAnG1haW50YWluaW5n4oCdIG9yIOKAnHByZXNlcnZpbmfigJ0gaW5mb3JtYXRpb24gbm90IHJl
c3RvcmluZyBpdC48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBjb21tb24gdXNlcyBvZiByZXN0b3JlIGluIEVuZ2xpc2gg
YWxsIGZvY3VzIG9uIHB1dHRpbmcgc29tZXRoaW5nIGJhY2sgdGhhdCBoYXMgYmVlbiBsb3N0LA0K
PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIEJ1
dCB0aGF0IGluZm9ybWF0aW9uIGlzIG5vdCBsb3N0IGZvciBhbiBvbi1wYXRoIGRldmljZSB0aGF0
IGVuY2Fwc3VsYXRlcyBhIHBhY2tldCBpbiBhbm90aGVyIG9uZSAoc28gdGhlIGlubmVyIGhlYWRl
ciBpcyBzdGlsbCBjYXJyeWluZyB0aGUgc291cmNlIElQDQogYWRkcmVzcykgb3IgdGhlIG9uZSB0
aGF0IHN1cHBsaWVzIHRoZSBvcmlnaW5hbCBzb3VyY2UgSVAgYWRkcmVzcyBhcyBhIG1ldGFkYXRh
IHdoZW4gc291cmNlIElQIGFkZHJlc3MvcG9ydCByZXdyaXRpbmcgaXMgcmVxdWlyZWQuIFRoZSBu
b3Rpb24gb2Yg4oCccHV0dGluZyBiYWNr4oCdIGRvZXMgbm90IG1ha2Ugc2Vuc2UgdG8gbWUgYmVj
YXVzZSB3ZSBhcmUgbm90IGRlYWxpbmcgd2l0aCB0aGUgaW50ZXJuYWwgcHJvY2Vzc2luZyBvZiBh
IHBhY2tldCB3aXRoaW4NCiBhbiBvbi1wYXRoIGRldmljZSwgYnV0IHdlIG9ubHkgZm9jdXMgb24g
dGhlIGV4dGVybmFsIGJlaGF2aW9yLiBUaGlzIGlzIGV4YWN0bHkgdGhlIHJvbGUgb2Yg4oCcdmlh
4oCdIGhlYWRlcnMgZm9yIFNJUCBwcm94aWVzOyB3aGVuIHRoZXJlIGlzIGEgbWlzbWF0Y2ggdGhl
IHJlY2VpdmVkIHRhZyBpcyBjb21wbGV0ZWQgd2l0aCB0aGUgdmlzaWJsZSBzb3VyY2UgYWRkcmVz
cy4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPnNvIEkgYmVsaWV2ZSByZXN0
b3JlIGlzIGJldHRlciB0aGFuICZxdW90O21haW50YWluJnF1b3Q7IG9yICZxdW90O3ByZXNlcnZl
JnF1b3Q7LCB3aGljaCBpbXBseSBzb21ldGhpbmcgaXMgYmVpbmcgY2FycmllZCBmb3J3YXJkIGFz
LWlzLCByYXRoZXIgdGhhbiBiZWluZyBwdXQgYmFjayBhZnRlciBsb3NzLjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+W01lZF0gUGxlYXNlIHNlZSBhYm92ZS4gQmVjYXVzZSB3ZSBkb27igJl0IGhhdmUg
YSBzdGFuZGFyZCBiZWhhdmlvciBvZiBhbiBvbi1wYXRoIGRldmljZSAocHJveHksIHR1bm5lbC1l
bmRwb2ludC4pLCBJIHNlZW1zIHdlaXJkIHRvIG1lIHRvIHNheSB0aGF0IGEgcHJveHkNCiB0aGF0
IHByZXNlcnZlcyB0aGUgc291cmNlIElQIGFkZHJlc3MgaXMg4oCccHV0dGluZyBwYWNrIGFuIGlu
Zm9ybWF0aW9uIHRoYXQgaXMgbG9zdOKAnS4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48YnI+DQom
bmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBj
bSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj4m
bmJzcDsgSWYgdGhlIGluZm9ybWF0aW9uIGlzIHByZXNlbnQgYXMgbWV0YWRhdGEgaW4gdGhlIHBh
Y2tldCBzZW50IHRvIHRoZSBwcm94eSBidXQgd291bGQgYmUgYWJzZW50IGFzIG1ldGFkYXRhIHVu
ZGVyIG5vcm1hbCBvcGVyYXRpb24gb2YgdGhlIHByb3h5LCBhZGRpbmcgaXQgYmFjaw0KIGluIHNv
bWV3aGVyZSBlbHNlIHJlc3RvcmVzIHRoZSBtZXRhZGF0YS4mbmJzcDs8L3NwYW4+PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+W01lZF0g4oCcbm9ybWFsIG9wZXJhdGlvbiBvZiBwcm94eeKAnSBpcyBub3QgYSBz
dGFuZGFyZC4gQSDigJxub3JtYWwgb3BlcmF0aW9uIG9mIHByb3h54oCdIHdvdWxkIGJlIHRvDQog
bWFpbnRhaW4gdGhlIGluZm9ybWF0aW9uIHNlbnQgYnkgdGhlIGNsaWVudCB3aGVuIHJlbGF5aW5n
IGl0IHRvIHRoZSBzZXJ2ZXIuIEnigJltIHN1cmUgeW91IGtub3cgZm9yIGluc3RhbmNlIHRoYXQg
U0lQIEIyQlVBcyBjYW4gZG8gd2hhdGV2ZXIgdGhleSB3YW50ISAmbmJzcDs8L3NwYW4+PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Zb3UncmUgcmlnaHQgdGhhdCB0aGUgbm9ybWFsIG9wZXJh
dGlvbiBvZiBhIHByb3h5IGlzIG5vdCBhIHN0YW5kYXJkLCBhbmQgSSBzaG91bGQgaGF2ZSBzYWlk
ICZxdW90O3RoZSBub3JtYWwgb3BlcmF0aW9uIG9mIHRoZSBwcm90b2NvbHMgdXNlZCBieSBhIHBy
b3h5JnF1b3Q7LjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNr
Ij5bTWVkXSBUaGlzIGlzIG11Y2ggYmV0dGVyLCBidXQgc3RpbGwgbm90IHN1ZmZpY2llbnQuIE9u
LXBhdGggZGV2aWNlcyB0aGF0IG1hbmlwdWxhdGUgcGFja2V0cyBtYXkgbm90IGJlIGEg4oCccHJv
dG9jb2wtc3BlY2lmaWMgcHJveHnigJ06IHR1bm5lbCBlbmRwb2ludCAoZS5nLiwNCiBMSVNQKSwg
Q0dOIChOQVQ2NCwgTkFUNDQsIERTLUxpdGUpLCBNQVAtRSBCUiwgZXRjLiAmbmJzcDs8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDsgSWYgdGhlIGFjdGlvbiBvZiB0aGUg
cHJveHkgaXMgdG8gc3RhcnQgYSBuZXcgVENQIGNvbm5lY3Rpb24gdG8gYW4gb3JpZ2luIHNlcnZl
ciwgZm9yIGV4YW1wbGUsIHRoZSBub3JtYWwgb3BlcmF0aW9uIG9mIFRDUCBpcyB0byB1c2UgdGhl
IGluaXRpYXRvcidzIElQIGFkZHJlc3MuPHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwv
bzpwPjwvc3Bhbj48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBUaGlzIGlzIHByb3RvY29sLXNwZWNpZmljLiBJ
IGNhbiBwcm92aWRlIGFuIGV4YW1wbGUgb2YgYSBwcm94eSBiZWhhdmlvciB0aGF0IHJlbGF5cyB0
aGUgc291cmNlIElQIGFkZHJlc3MvcG9ydCBhcyBwYXJ0IG9mIGl0cyBub3JtYWwgb3BlcmF0aW9u
Og0KPGEgaHJlZj0iaHR0cDovL3d3dy5oYXByb3h5Lm9yZy9kb3dubG9hZC8xLjgvZG9jL3Byb3h5
LXByb3RvY29sLnR4dCI+aHR0cDovL3d3dy5oYXByb3h5Lm9yZy9kb3dubG9hZC8xLjgvZG9jL3By
b3h5LXByb3RvY29sLnR4dDwvYT4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7LSBUQ1AvSVB2NCA6
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJnF1b3Q7UFJPWFkgVENQ
NCAyNTUuMjU1LjI1NS4yNTUgMjU1LjI1NS4yNTUuMjU1IDY1NTM1IDY1NTM1XHJcbiZxdW90Ozxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ID0mZ3Q7IDUgJiM0MzsgMSAmIzQzOyA0ICYjNDM7
IDEgJiM0MzsgMTUgJiM0MzsgMSAmIzQzOyAxNSAmIzQzOyAxICYjNDM7IDUgJiM0MzsgMSAmIzQz
OyA1ICYjNDM7IDIgPSA1NiBjaGFyczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJzcDsg
LSBUQ1AvSVB2NiA6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJnF1
b3Q7UFJPWFkgVENQNiBmZmZmOmYuLi5mOmZmZmYgZmZmZjpmLi4uZjpmZmZmIDY1NTM1IDY1NTM1
XHJcbiZxdW90OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsi
Pj0mZ3Q7IDUgJiM0MzsgMSAmIzQzOyA0ICYjNDM7IDEgJiM0MzsgMzkgJiM0MzsgMSAmIzQzOyAz
OSAmIzQzOyAxICYjNDM7IDUgJiM0MzsgMSAmIzQzOyA1ICYjNDM7IDIgPSAxMDQgY2hhcnM8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiPiZuYnNwOyBUaGUgbG9zZXMgdGhlIElQIGFkZHJlc3Mgb2YgdGhlIHF1ZXJ5aW5nIGhvc3Qg
aXMgaW1wbGllZCBieSB0aGF0IG5vcm1hbCBvcGVyYXRpb24oaW4gb3RoZXIgd29yZHMsIGl0IGVs
aWRlcyBtZXRhZGF0YSBhYm91dCBhbnkgY2xpZW50IHRoYXQgY2F1c2VkIHRoaXMgbmV3IFRDUCBj
b25uZWN0aW9uIHRvIGJlIGNyZWF0ZUQpLjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48
L286cD48L3NwYW4+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gVGhpcyBtYWtlcyBzZW5zZSBpZiBsb3Npbmcg
dGhlIG9yaWdpbmFsIElQIGFkZHJlc3MgaXMgYW4gaW50ZW5kZWQgcHJvcHJpZXR5IG9mIHRoZSBw
cm94eS4gQnV0IHRoaXMgY2Fubm90IGJlIGEgZ2VuZXJhbGl6ZWQgcHJveHkgYmVoYXZpb3IgKHNl
ZSB0aGUgZXhhbXBsZQ0KIGFib3ZlKS4gPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAx
LjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1y
aWdodDowY20iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5n
PSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48
c3BhbiBsYW5nPSJFTi1VUyI+U28gb3JpZ2luIElQIGFkZHJlc3Mgc3RhcnRzIG91dCBpbiB0aGUg
SVAgaGVhZGVyIG9mIHRoZSBvcmlnaW5hbCBwYWNrZXQgYnV0IGdldHMgcHVzaGVkIGZyb20gdGhh
dCBzbG90IHdoZW4gdGhlIHByb3h5IGNvbnN0cnVjdHMgdGhlIG9ud2FyZCBJUCBwYWNrZXQgdG8g
dGhlIHNlcnZlci4mbmJzcDsNCiBGb3IgaXQgdG8gcmVhY2ggdGhlIHNlcnZlciwgaXQgaGFzIHRv
IGJlIHBsYWNlZCBzb21ld2hlcmUgZWxzZSBpbiB0aGUgb253YXJkIHBhY2tldCwgcmVzdG9yaW5n
IHRoZSBsb3N0IG1ldGFkYXRhLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBUaGUgY2xp
ZW50IGFncmVlZCB0byBzZW5kIHBhY2tldHMgd2l0aCBpdHMgc291cmNlIElQIGFkZHJlc3MgKHdo
aWNoIG1lYW4gY29uc2VudCkuIFdoeSB0aGUNCiBwcm94eSB3b3VsZCBuZWVkIHRvIGFuIGV4dHJh
IGNoYW5uZWwgdG8gZ2V0IGNvbnNlbnQgZm9yIHJlbGF5aW5nIHRoZSBzb3VyY2UgSVAgYWRkcmVz
cyB0byBhIHNlcnZlcj8gJm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PC9zcGFu
PjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QmVjYXVzZSB0aGUgY2xpZW50IGFncmVlZCB0
byBzZW5kIHBhY2tldHMgdG8gdGhlIHByb3h5IGJ5IHB1dHRpbmcgaXQgaW4gdGhlIGRlc3RpbmF0
aW9uPHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRd
IFRoZSBjbGllbnQgaXMgbm90IGV2ZW4gYXdhcmUgdGhhdCBwcm94eSBleGlzdHMgb24gdGhlIHBh
dGghIFBhY2tldHMgYXJlIHNlbnQgdG8gdGhlIHVsdGltYXRlIHNlcnZlcuKAmXMgYWRkcmVzcywg
bm90IHRoZSBvbmUgb2YgdGhlIHByb3h5LiBFdmVuIGZvciBTT01FDQogY2FzZXMgd2hlcmUgcGFj
a2V0cyBhcmUgc2VudCBleHBsaWNpdGx5IHRvIHRoZSBwcm94eSAoZS5nLiwgU09DS1MgcHJveHkp
LCBhIHN0YXRlIGlzIGFscmVhZHkgaW4gcGxhY2UgdG8gZ3JhZnQgdGhlIG91dGdvaW5nIHBhY2tl
dHMgdG8gYSBiaW5kaW5nIGNvbnRleHQgaW52b2x2aW5nIHRoZSBkZXN0aW5hdGlvbiBzZXJ2ZXIu
DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmll
ciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4sIGFuZCBkaWQgbm90IGFncmVl
IHRvIGdlbmVyYWwgZGlzY2xvc3VyZTsgeW91IGNhbid0IGluZmVyIG9ud2FyZCBjb25zZW50Ljxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gSG1t4oCmSeKAmW0gYWZyYWlkIHRoaXMgY29uY2x1
c2lvbiBpcyBub3QgdGVjaG5pY2FsbHkgYmFja2VkLCBlLmcuLCAmbmJzcDs8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29s
b3I6YmxhY2siPiogQSBjbGllbnQgdGhhdCBzZW5kcyBwYWNrZXRzIHRvIGEgc2VydmVyIGxvY2F0
ZWQgb24gdGhlIEludGVybmV0IGlzIE5PVCBuZWNlc3NhcmlseSBhd2FyZSB0aGF0IGEgcHJveHkg
aXMgc29saWNpdGVkIGluIGZvcndhcmRpbmcgcGF0aC4gUGFja2V0cyBhcmUgc2VudA0KIHVzaW5n
IHRoZSBzZXJ2ZXLigJlzIElQIGFkZHJlc3MuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4qIFRoZSBj
bGllbnQgYW5kIHByb3h5IG1heSBiZSBvd25lZCBieSB0aGUgc2FtZSBhZG1pbmlzdHJhdGl2ZSBl
bnRpdHkgKGNhc2Ugb2YgZW50ZXJwcmlzZSBuZXR3b3JrcykuIFRoYXQgZW50aXR5IGlzIHJlc3Bv
bnNpYmxlIGZvciBlbnN1cmUgd2hpY2ggaW5mb3JtYXRpb24NCiB0aGUgcHJveHkgbmVlZHMgdG8g
bGVhay4gJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4qIFRoZSBwcm94eSBhbmQgdGhlIHNl
cnZlciBtYXkgYmUgb3duZWQgYnkgdGhlIHNhbWUgYWRtaW5pc3RyYXRpdmUgZW50aXR5IChjb250
ZW50IHByb3ZpZGVyKS4gU3VwcGx5aW5nIGRhdGEgYnkgYSBwcm94eSB0byB0aGUgc2VydmVyLCBi
YXNlZCBvbiB0aGUgY29udGVudA0KIG9mIGEgcGFja2V0IHJlY2VpdmVkIGZyb20gYSBob3N0LCBk
b2VzIG5vdCBpbmR1Y2UgYSBwcml2YWN5IGNvbmNlcm4gaGVyZSBiZWNhdXNlIHRoZSBwcm94eSBh
bmQgdGhlIHNlcnZlciBvd25lZCBieSB0aGUgc2FtZSBlbnRpdHkuDQo8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5n
OjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0K
PGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJF
Ti1VUyI+SGFkIGl0IGJlZW4gcHJlc2VudCBpbiB0aGUgcGFja2V0IGFzIGhlYWRlciB2YWx1ZSBp
biB0aGUgSFRUUCBleGNoYW5nZSwgaXQgd291bGQgbm90IGhhdmUgYmVlbiBzdHJpcHBlZCBieSBu
b3JtYWwgb3BlcmF0aW9uLiZuYnNwOw0KPC9zcGFuPlRoZXJlIHByb3h5IG9wZXJhdGlvbiBmb3J3
YXJkaW5nIGl0IG9uIHdvdWxkIGJlIHNpbXBseSBwcmVzZXJ2aW5nIGl0LjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6Ymxh
Y2siPltNZWRdIFRoaXMgaXMgYW5vdGhlciBxdWVzdGlvbjogd2hldGhlciB0aGUgc2FtZSBvciBk
aXN0aW5jdCBjaGFubmVsIGNhbiBiZSB1c2VkIHRvIGNvbW11bmljYXRlDQogdGhlIFNBTUUgZGF0
YSB0aGF0IHdhcyBwcmVzZW50IGluIHRoZSBpbml0aWFsIHBhY2tldCBpc3N1ZWQgYnkgYSBob3N0
Ljwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PGJyPg0KJm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5n
PSJFTi1VUyI+VGhhdCBkZXBlbmRzIG9uIHRoZSBuYXR1cmUgb2YgdGhlIGNoYW5uZWwuJm5ic3A7
IE9idmlvdXNseSwgaWYgeW91IHNldCB0aGUgb3JpZ2luIGNsaWVudHMgSVAgYWRkcmVzcyBhcyB0
aGUgc291cmNlIGFkZHJlc3MsIHlvdSdyZSBnb2luZyB0byBnZXQgYSBkaWZmZXJlbnQgcmVzdWx0
IGZyb20gdGhhdCBzcG9vZmluZyB0aGFuIHB1dHRpbmcNCiBpdCBpbiBhIGNsaWVudCBzdWJuZXQg
RUROUyBvcHRpb24gb3IgZm9yd2FyZGVkLWZvciBoZWFkZXIuIDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBBZ3JlZS48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4w
cHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdp
bi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90
ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRk
aW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7
bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5n
OjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0ibS02MTk0Njg1MDU3NTM0MzE5MjY5bTc3NzA3MjIyODg0MjMxNTcyNDltc29saXN0cGFyYWdy
YXBoIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6U3ltYm9sO2NvbG9yOmJsYWNrIj7Ctzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZTo3LjBwdDtjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OmJsYWNrIj5BbiBhZGRyZXNzIHNoYXJpbmcgZGV2aWNlLCB1bmRlciBmb3IgZXhhbXBsZSBEUy1M
aXRlIChSRkM2MzMzKSwgdGhhdCBpbnNlcnRzIHRoZSBzb3VyY2UgSVB2NiBwcmVmaXggaW4gdGhl
IFRDUCBIT1NUX0lEIG9wdGlvbiAoUkZDNzk3NCkgaXMgbm90IFJFU1RPUklORyBhbnkgZGF0YS4g
VGhlIGNvbnRlbnQNCiBvZiB0aGF0IFRDUCBvcHRpb24gaXMgYWxyZWFkeSB2aXNpYmxlIGluIHRo
ZSBwYWNrZXQgc2VudCBieSB0aGUgaG9zdC4gPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2Nr
cXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5JIGFncmVlIHdpdGggdGhlIElF
U0cgYW5hbHlzaXMgb2YgUkZDNzk3NC4mbmJzcDsgSXQgZG9lcyByZXN0b3JlIGluZm9ybWF0aW9u
IGJ5IHRha2luZyBpbmZvcm1hdGlvbiB3aGljaCBub3JtYWwgb3BlcmF0aW9uIHdvdWxkIGhhdmUg
ZWxpZGVkIGFuZCByZXN0b3JlcyBpdC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBUaGUmbmJzcDsg
aW1wbGljYXRpb24gb2Ygd2hhdCB5b3UgYXJlIHNheWluZyBoZXJlIGlzIHRoYXQgcHJveGllcyBh
cmUgZ29vZCBiZWNhdXNlIHRoZXkgaGlkZSB0aGUNCiBzb3VyY2UgSVAgYWRkcmVzc2VzIG9mIGhv
c3QhICZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+QWdn
cmVnYXRpbmcgcHJveGllcyBjYW4gaGF2ZSBhIHBvc2l0aXZlIHByaXZhY3kgaW1wYWN0LCB5ZXMu
Jm5ic3A7IEFuIG9ic2VydmVyIHNlZWluZyB0cmFmZmljIGZyb20gYW4gYWdncmVnYXRpbmcgcHJv
eHkgdG8NCjwvc3Bhbj48YSBocmVmPSJodHRwOi8vc2Vuc2l0aXZlLXRvcGljLmV4YW1wbGUuY29t
Ij48c3BhbiBsYW5nPSJFTi1VUyI+c2Vuc2l0aXZlLXRvcGljLmV4YW1wbGUuY29tPC9zcGFuPjwv
YT48c3BhbiBsYW5nPSJFTi1VUyI+IGtub3dzIG9ubHkgdGhhdCBzb21lIHVzZXIgYmVoaW5kIHRo
YXQgcHJveHkgaXMgbG9va2luZyBmb3IgaW5mb3JtYXRpb24gb24gc2Vuc2l0aXZlLXRvcGljLiZu
YnNwOw0KPC9zcGFuPlRvIGtub3cgd2hpY2ggdXNlciwgdGhlIG9ic2VydmVyIG11c3QgaGF2ZSBl
aXRoZXIgc3Vib3JuZWQgdGhlIHByb3h5IG9yIGhhdmUgYSB3YXkgb2Ygb2JzZXJ2aW5nIHRyYWZm
aWMgYmV0d2VlbiBob3N0cyBhbmQgdGhlIHByb3h5LiZuYnNwOyBCb3RoIGFyZSBtb3JlIGV4cGVu
c2l2ZSBhbmQgYXQgaGlnaGVyIHJpc2sgb2YgZGlzY292ZXJ5IHRoYW4gYSBzaW1wbGUgdGFwIG5l
YXINCjxhIGhyZWY9Imh0dHA6Ly9zZW5zaXRpdmUtdG9waWMuZXhhbXBsZS5jb20iPnNlbnNpdGl2
ZS10b3BpYy5leGFtcGxlLmNvbTwvYT4uJm5ic3A7IDxvOnA+DQo8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gVGhlIG1haW4gcG9pbnQg
aGVyZSBpcyB0aGF0LCBldmVuIGluIHRoZSBwcmVzZW5jZSBvZiBhbiBhZ2dyZWdhdGluZyBwcm94
eSwgYSBzZXJ2ZXIgY2FuIGRlbXV4IHVzZXJzIGJ5IGNvcnJlbGF0aW5nIHZhcmlvdXMgaW5mb3Jt
YXRpb24gbGVha2VkIGF0IHRoZQ0KIGFwcGxpY2F0aW9uIGxheWVyIChlLmcuLCA8YSBocmVmPSJo
dHRwczovL3Bhbm9wdGljbGljay5lZmYub3JnLyI+aHR0cHM6Ly9wYW5vcHRpY2xpY2suZWZmLm9y
Zy88L2E+KS4gVHJhY2tpbmcgdGhvc2UgdXNlcnMgd2hlbiB0aGV5IGNoYW5nZSB0aGVpciBzb3Vy
Y2UgSVAgYWRkcmVzcyBpcyBwb3NzaWJsZSBpbiB0aGlzIGNhc2UsIHRvby48L3NwYW4+PHNwYW4g
bGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2Nr
cXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7
cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6
MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJn
aW4tbGVmdDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJv
dHRvbTo1LjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+SWYgdGhlIGRhdGEgaXMgdGFr
ZW4gZnJvbSBhIHBvcnRpb24gb2YgdGhlIHBhY2tldCB0aGF0IHdvdWxkIG5vdCBub3JtYWxseSBi
ZSBmb3J3YXJkZWQgdG8gYW4gdXBzdHJlYW0gaG9zdCBhbmQgYWRkZWQgdG8gYSBwb3J0aW9uIHRo
YXQgaXMgZm9yd2FyZGVkIHRvIGFuIHVwc3RyZWFtIGhvc3QsIHRoZW4gdGhlIGRldmljZQ0KIGFk
ZGluZyB0aGUgZGF0YSBiYWNrIGluIHNob3VsZCBrbm93IGl0IGlzIGEgcmVzdG9yYXRpb24uPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+W01lZF0gVGhhdCBkZWZpbml0aW9uIGlzIG5vdCB0cml2aWFsIGFzIG1lbnRpb25l
ZCBhYm92ZS4gSSB3b3VsZCB1c2Ug4oCccHJlc2VydmXigJ0gb3Ig4oCcbWFpbnRhaW7igJ0gcmF0
aGVyDQogdGhhbiDigJxyZXN0b3Jl4oCdLiA8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+UGxlYXNlIHNlZSBhYm92ZS4mbmJzcDsgJnF1b3Q7UmVzdG9yZSZxdW90OyBpcyBjbG9zZXIs
IGluIG15IG9waW5pb24sIHRoYW4gZWl0aGVyIHByZXNlcnZlIG9yIG1haW50YWluLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KJm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7
bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+SWYgdGhlIGVuZHBvaW50IHNlbmRzIHRoZSBkYXRhLCBkYXRhIHdpbGwgYmUg
Y29uc2lzdGVudGx5IGF2YWlsYWJsZSBpbiB0aGF0IGhlYWRlci4mbmJzcDsgVGhlIGRhdGEgY2hh
bmdlcywgb2YgY291PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5yc2UuPC9zcGFu
PjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIEnigJltIG5vdCBzdXJlIHRvIGZvbGxvdyB5b3UgaGVy
ZS4gV2hhdCBpcyBtZWFudCBieSDigJw8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij5jb25z
aXN0ZW50DQogYXZhaWxhYmlsaXR54oCdIHRoZW48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPj8g
RG8geW91IG1lYW4gdGhlIHNhbWUgY2hhbm5lbC9wcm9jZWR1cmUgdG8gY29tbXVuaWNhdGUgdGhl
IGluZm9ybWF0aW9uPyBPciDigJxjb25zaXN0ZW50IGRhdGHigJ0/PC9zcGFuPjwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPkkgbWVhbiB0aGF0IGlmIHlvdSBkZWZpbmUgYSBwcm90b2NvbCBzdWNo
IHRoYXQgYSB3ZWxsLWZvcm1lZCBtZXNzYWdlIGZyb20gdGhlIGNsaWVudCBoYXMgdGhlIGRhdGEg
dGhlIHNlcnZlciBuZWVkcywgaXQgd2lsbCBiZSBjb25zaXN0ZW50bHkgYXZhaWxhYmxlLiZuYnNw
OyBJZiB5b3UgcmVseSBvbiBpbnRlcm1lZGlhdGUgbmV0d29yayBkZXZpY2VzIHRvIGFkZCB0aGUg
ZGF0YSwgaXQgbWF5DQogbm90IGJlIGF2YWlsYWJsZSBpZiB0aGVyZSBpcyBub3QgY29vcGVyYXRp
bmcgbmV0d29yayBkZXZpY2Ugb24gcGF0aCAoZS5nLiBpZiB0aGUgRE5TIHJlc29sdmVyIGRvZXMg
bm90IHN1cHBvcnQgdGhlIHJlbGV2YW50IEVETlMwIG9wdGlvbikuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJs
YWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIFRoYW5rIHlvdS4gUGxlYXNl
IGNsYXJpZnkgdGhpcyBpbiB0aGUgZHJhZnQuIEkgaGFkIHRyb3VibGVzIHRvIHBhcnNlIHdoYXQg
eW91IG1lYW50IGJ5IOKAnGNvbnNpc3RlbnQNCjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsi
PmF2YWlsYWJpbGl0eTwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPuKA
nS4gVGhhdOKAmXMgc2FpZCwgdGhlcmUgbWlnaHQgYmUgYWxzbyDigJxub3QgY29vcGVyYXRpbmcg
b24tcGF0aCBkZXZpY2Vz4oCdIHRoYXQgbWF5DQogc3RyaXAvYWx0ZXIgdGhlIGNvbnRlbnQgb2Yg
Y2xpZW50IHN1cHBsaWVkIGRhdGEgKGVhc3kgZm9yIEhUVFAgZm9yIGV4YW1wbGUpLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9j
a3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0
O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0
OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9j
a3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0
O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1
LjBwdDttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+
DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3Bh
ZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4m
bmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5b
TWVkXSBSZXNvdXJjZXMgbWF5IG5vdCBiZSByZXN0cmljdGVkIHRvIENQVSBvciBkaXNrIGJ1dCBt
YXkgYmUgZ3JhbnRpbmcgYWNjZXNzIHRvIHRoZSBzZXJ2aWNlDQogKGUuZy4sIGRvd25sb2FkIGEg
ZmlsZSB3aGVuIGEgcXVvdGEgcGVyIHNvdXJjZSBhZGRyZXNzIGlzIGVuZm9yY2VkKS4gSXQgY2Fu
IGJlIHdoYXRldmVyIHRoZSBzZXJ2ZXJzIGNvbnNpZGVyIHRvIGJlIGNyaXRpY2FsIGZvciB0aGVt
OyBpdCBpcyB1cCB0byB0aGUgdGFzdGUgb2YgdGhlIHNlcnZpY2UgZGVzaWduIHRvIGNoYXJhY3Rl
cml6ZSBpdC4gVGhlIE5FVyB3b3JkaW5nIHByb3Bvc2VkIGFib3ZlIGlzIHRlY2huaWNhbGx5IGNv
cnJlY3QuIFBsZWFzZQ0KIHJlY29uc2lkZXIgYWRkaW5nIGl0IHRvIHRoZSBkcmFmdC4gPC9zcGFu
PjxzcGFuIGxhbmc9IkVOLVVTIj48YnI+DQo8YnI+DQombmJzcDsgPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SSBk
aWQgY29uc2lkZXIgaXQsIGJ1dCBJIGNvbnRpbnVlIHRvIGJlbGlldmUgdGhhdCBpdCBtb3ZlcyB0
aGUgbmVlZGxlIHRvbyBmYXIgaW50byBzaW1wbGUgc2VydmVyIHByZWZlcmVuY2UuJm5ic3A7IEkg
cmV0YWluZWQgdGhlIG9yaWdpbmFsIFBTQVAgbGFuZ3VhZ2UgaW4gLTA3IGFzIGEgcmVzdWx0Ljxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPltNZWRdIGVtZXJnZW5jeSBpcyBvbmx5IGFuIGV4YW1wbGUmbmJzcDs7
IG90aGVyIHNlcnZpY2VzIG1heSBleGlzdCB0aGF0IGltcG9zZSB0aGUgc2FtZSB0cnVzdCBtb2Rl
bC4NCjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkkgdGhpbmsgdGhlcmUgaXMgYSBxdWFsaXRhdGl2ZSBkaWZmZXJlbmNlIGJl
dHdlZW4gc2l0dWF0aW9ucyBpbiB3aGljaCB0aGUgcmVzb3VyY2VzIGF0IHJpc2sgYXJlIGh1bWFu
IGxpdmVzIGFuZCB0aG9zZSB3aGVyZSB0aGV5IGFyZSBob3N0IHJlc291cmNlcy48c3BhbiBzdHls
ZT0iY29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gSSBhZ3JlZSB3aXRo
IHlvdSBhcyBhbiBpbmRpdmlkdWFsLiBCdXQsIGl0IGlzIG5vdCB1cCB0byB1cyB0byBtYW5kYXRl
IHRoaXMgY29uZGl0aW9uIGZvciBleGVjdXRpbmcgc2VydmljZXMuIEl0IGlzIHVwIHRvIHRoZSAo
cHJvdG9jb2wpIGRlc2lnbmVycy9zZXJ2aWNlDQogcHJvdmlkZXJzIHRvIGRlY2lkZSB3aGF0IGlz
IGNyaXRpY2FsL2tleSBmb3IgdGhlaXIgc2VydmljZSBvcGVyYXRpb24uPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyI+Jm5ic3A7IFRoYXQncyB3aHkgdGhlIGNhcnZlIG91dCB3YXMgbGltaXRl
ZCBpbiB0aGUgR0VPUFJJViBjYXNlLjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48L286
cD48L3NwYW4+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+W01lZF0gR0VPUFJJViBpcyBub3QgdGhlIG9ubHkgcHJvdG9j
b2wvc2VydmljZSB0aGF0IGlzIGNvbmNlcm5lZCB3aXRoIGh1bWFuIGxpdmVzLCB3ZSBjYW4gY29u
c2lkZXIgdmVoaWN1bGFyIG5ldHdvcmtpbmcgdGhhdCB0cnVzdCB0aGUgaW5mb3JtYXRpb24gc2hh
cmVkDQogYnkgdGhlIGluZnJhc3RydWN0dXJlLiBJIHByZWZlciBuZXV0cmFsIHdvcmRpbmcgdGhh
dCBjaXRlcyBlbWVyZ2VuY3kgYXMgYW4gZXhhbXBsZS48L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMi
Pg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxicj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0
LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEy
LjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPkkgYWxzbyBhZGRlZCBhIG5vdGUgYWJvdXQgeW91ciBl
eHRlbnNpdmUgcmV2aWV3LiZuYnNwOyBXaGlsZSB5b3UgYW5kIEkgY2xlYXJseSBoYXZlIHNvbWUg
ZGlmZmVyZW5jZXMNCjwvc3Bhbj5vZiB2aWV3LCB0aGUgZG9jdW1lbnQgaGFzIGdvdHRlbiBiZXR0
ZXIgZnJvbSB5b3VyIGVuZ2FnZW1lbnQgd2l0aCBpdCwgYW5kIEkgYXBwcmVjaWF0ZSB5b3VyIGVm
Zm9ydHMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZx
dW90Oztjb2xvcjpibGFjayI+W01lZF0gSSByZXZpZXdlZCB0aGUgLTA3LiBBbHRob3VnaCBpdCBp
cyBiZXR0ZXIgY29tcGFyZWQgdG8gLTA1LCBJIHN0aWxsIGRvbuKAmXQgdGhpbmsgaXQgaXMgcmVh
ZHkgdG8gYmUNCiBwdWJsaXNoZWQgYXMgaXQgaXMuIFRoYW5rIHlvdSBmb3IgeW91ciBlZmZvcnQu
PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1
b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEy
LjBwdCI+QW5kIHRoYW5rIHlvdSBmb3IgeW91cnMsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPnJl
Z2FyZHMsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5UZWQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVy
Om5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNt
IDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21hcmdpbi1ib3R0b206MTIuMHB0Ij5yZWdhcmRzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UZWQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_a9787ef7734b49a48590b793272893d7OPEXCLILM5Ccorporateadr_--


From nobody Tue Mar  7 01:08:53 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9E52129461 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 01:08:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3_TahaAu-OP for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 01:08:51 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5D8312945C for <ietf@ietf.org>; Tue,  7 Mar 2017 01:08:50 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 68979280128; Tue,  7 Mar 2017 10:08:49 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id 62C7E280230; Tue,  7 Mar 2017 10:08:49 +0100 (CET)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id 5C2C8280128; Tue,  7 Mar 2017 10:08:49 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 5915E6042903; Tue,  7 Mar 2017 10:08:49 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id 4FAFC4071A; Tue,  7 Mar 2017 10:08:49 +0100 (CET)
Date: Tue, 7 Mar 2017 10:08:49 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Subject: Re: Adding IPv10 to the IETF 98 Agenda.
Message-ID: <20170307090849.jyl7fqqbn3icjw7a@nic.fr>
References: <HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com>
X-Operating-System: Debian GNU/Linux 9.0
X-Kernel: Linux 4.8.0-2-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.3.7.85717
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MHXG9tPc0IcEqHerdrgaOp7k568>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 09:08:51 -0000

On Mon, Mar 06, 2017 at 05:02:38PM +0000,
 Khaled Omar <eng.khaled.omar@hotmail.com> wrote 
 a message of 83 lines which said:

> finally I got a positive response from one of the Internet Area
> Chairs and will be waiting for that discussion during the IETF 98
> meeting.

Good. IETF is too serious. We need a "wild ideas" session, with IPv10,
miraculous DNS alternatives, and everything over the blockchain :-)


From nobody Tue Mar  7 02:18:02 2017
Return-Path: <gunnar.hellstrom@omnitor.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 E93D1129421 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 02:17:53 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1UCEYAfe4Xlg for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 02:17:52 -0800 (PST)
Received: from bin-vsp-out-02.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54C47129434 for <ietf@ietf.org>; Tue,  7 Mar 2017 02:17:49 -0800 (PST)
X-Halon-ID: 4de0d9ec-031f-11e7-af93-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [77.53.231.21]) by bin-vsp-out-02.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Tue,  7 Mar 2017 11:17:43 +0100 (CET)
Subject: Re: [Slim] Review of draft-ietf-slim-negotiating-human-language-08
To: Mahesh Jethanandani <mjethanandani@gmail.com>, ops-dir@ietf.org
References: <148885485450.15073.6095850267163523164.idtracker@ietfa.amsl.com>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <20633096-1dfa-1c01-9591-3c2fb66efa30@omnitor.se>
Date: Tue, 7 Mar 2017 11:17:37 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148885485450.15073.6095850267163523164.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w8bAT-4KgCJrxp0VKaDi-ekQGp0>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 10:17:54 -0000

Mahesh,

Your review brings up interesting aspects.

I can provide some initial responses,


Den 2017-03-07 kl. 03:47, skrev Mahesh Jethanandani:
> Reviewer: Mahesh Jethanandani
> Review result: Has Nits
>
> I have reviewed this document as part of the Operational
> directorate’s ongoing effort to review all IETF documents being
> processed by the IESG.  These comments were written with the intent of
> improving the operational aspects of the IETF drafts. Comments that
> are not addressed in last call may be
> included in AD reviews during the IESG review.  Document editors
> and WG chairs should treat these comments just like any other last
> call comments.
>
> Document reviewed:  draft-ietf-slim-negotiating-human-language-08
>
> Status:
>
> Ready with comments.
>
> Summary:
>
> This document adds new SDP media-level attributes so that when
> establishing interactive communication sessions ("calls"), it is
> possible to negotiate (communicate and match) the caller's language
> and media needs with the capabilities of the called party.
>
> The document is short and easy to read. And it seems to have
> considered many aspects of trying to negotiate a common human language
> or capability. This review looks at the document more from a operator
> or management perspective.
>
> Operational considerations:
>
> >From a operations perspective, there may be a need to troubleshoot the
> interface that sets up the negotiated human language. Identifying
> consistent methods of information that should be counted by both
> parties will go a long way in debugging a problem. For example, in
> this case, it would be helpful to start by collecting how many
> requests were made, how many found a language or medium in common and
> how many were rejected because a common match was not found.
>
> Management considerations:
>
> The old adage says, “Anything that can be configured, can also be
> misconfigured”, unless that is somehow made less possible by providing
> default values, modes or parameters. This can be something that can be
> defined using a data model in YANG.
>
> I assume that the default behavior of receiving a SDP attribute that
> one does not support, results in a throw away of that particular
> attribute, and not the whole message, if combined with other
> attributes. Is this documented somewhere? If not, what does the
> deployment scenario look like, particularly with existing solutions?
In section 5 of RFC 4566 the SDP specification, it is said:
"An SDP parser MUST ignore any attribute it doesn't understand."

In a real world, the deployment will be gradual, so many times, either 
the caller UA or the callee UA will not understand these attributes.

Some possible default actions are mentioned in the draft for cases when 
there are no settings or no support in either end, but the draft is not 
intended to provide exact solutions for the negotiation, but rather only 
provide a protocol for conveying indications sufficient for performing 
the negotiation.
>
> What is the impact on network operations if for example either the
> translator or relay agent fails? How would that impact the
> negotiation?
The draft does not intend to dictate how and by what party a 
language/modality gap is detected, so that a translating agent or 
modality conversion relay service will be desired and invoked in the 
call. The intention is to make such detection and invocation possible, 
at least regarding relay services. The natural way of using the 
mechanism of the draft is that each party involved in the call setup 
will modify the hlang attributes to indicate the joint capabilities and 
preferences of the so far involved parties. If invocation of a party 
fails, its modification of the hlang attributes does not take place and 
the answer will then not likely contain a satisfying set of languages 
for the offering party. This may be a case when the paranthesis in this 
sentence in section 5.2 comes into play: "In an answer, 'hlang-send' is 
the language the answerer will send
    when using the media (which in most cases is one of the languages in
    the offer's 'hlang-recv'), and 'hlang-recv' is the language the
    answerer expects to receive in the media (which in most cases is one
    of the languages in the offer's 'hlang-send')."

If the answering party was the one who intended to invoke the 
translation or relaying if needed, then it can also deny the call if 
that is indicated as a preference in the incoming call.

These details belong to the negotiation mechanism that was not intended 
to be described in detail in the draft.
>
> Also, what is the test, both active and passive for the correct
> operation? Is there a counter being maintained for both correct and
> incorrect negotiation. Goes back to the question of what counters are
> being maintained. Such counters should include values that enable
> isolation of faults. For example, if negotiation fails, what are the
> more specific counters that isolate what within the negotiation
> failed?
>
> Fault Management:
>
> In addition to collection information on how the negotiation is
> working, it is important to be able to propagate both fault and health
> indicators to a management application. Such information needs to be
> documented.
>
> Accounting Management:
>
> Finally, it is always helpful to collect information on utilization
> from capacity, trend analysis, cost allocation, auditing and billing
> perspective.
Interesting aspects. Let us see what others say about what we can 
include at this stage and what should be brougth up in follow-up documents.

/Gunnar
>
> Idnits:
>
> A run of idnits came out clean.
>
>
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Tue Mar  7 03:21:01 2017
Return-Path: <sprevidi@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 9C2EF129625; Tue,  7 Mar 2017 03:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D1EbSm9mGn6D; Tue,  7 Mar 2017 03:20:57 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71FFE129624; Tue,  7 Mar 2017 03:20:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12330; q=dns/txt; s=iport; t=1488885657; x=1490095257; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=5yzUkbzR0I5EamRMiIDOE9sX1xawVk/9L/N/AFxP2RI=; b=TIlvlpSybLeBldsKDgtCKrAKDtagTOxHEO9kh38Q8uwLB8TrAHJlYzro K0HfPjWSwqO37b0YF0vH32iTMLZ1STkB/s+rheNLC1/CvNQzQnFSQUASc BqPgvu4xQO0vC5MjaxuJP3+e0efpzq5Dpd7/OfE8hTTFPM0WWpM5rgV3X s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BtAgDHlr5Y/4oNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1FhgQoHg1iKDJErH5U3gg0fC4UuSgIaggs/GAECAQEBAQEBAWs?= =?us-ascii?q?ohRUBAQEDAQEBIREzBwsFCwIBCA4KAgIRFQICAiULFRACBA4FG4lZCA6vI4Imi?= =?us-ascii?q?n4BAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYELhUOCBQiBWYEJhD5VgkcugjEFnDA?= =?us-ascii?q?Bih2IGIF7hSKDVIR0gTqIQ4p3AR84gQNWFT8RAYRCHYFjdYkGgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.35,258,1484006400"; d="scan'208";a="220713306"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Mar 2017 11:20:55 +0000
Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v27BKtN5009684 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 7 Mar 2017 11:20:55 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 7 Mar 2017 06:20:54 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Tue, 7 Mar 2017 06:20:54 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Susan Hares <shares@ndzh.com>
Subject: Re: [spring] Review of draft-ietf-spring-segment-routing-msdc-03
Thread-Topic: [spring] Review of draft-ietf-spring-segment-routing-msdc-03
Thread-Index: AQHSlpZMkMzvhnBme0W79O2wdqWPfqGJkGaA
Date: Tue, 7 Mar 2017 11:20:54 +0000
Message-ID: <DA020A62-FCD9-4299-AB69-1321FCDB7C26@cisco.com>
References: <148881752958.15101.3565092696759250024.idtracker@ietfa.amsl.com>
In-Reply-To: <148881752958.15101.3565092696759250024.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.216.167]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A23C7CC0D3732F4D97B4C3DA21EF8E8D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eoOx_Svxh6BTGfAQ7zx1Y5OEel8>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-spring-segment-routing-msdc.all@ietf.org" <draft-ietf-spring-segment-routing-msdc.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 11:20:59 -0000

SGkgU3VlLA0KDQp0aGFua3MgZm9yIHRoZSByZXZpZXcuIFNvbWUgY29tbWVudHMgYmVsb3cuDQoN
Cg0KPiBPbiBNYXIgNiwgMjAxNywgYXQgNToyNSBQTSwgU3VzYW4gSGFyZXMgPHNoYXJlc0BuZHpo
LmNvbT4gd3JvdGU6DQo+IA0KPiBSZXZpZXdlcjogU3VzYW4gSGFyZXMNCj4gUmV2aWV3IHJlc3Vs
dDogSGFzIElzc3Vlcw0KPiANCj4gVGhlIFJURy1ESVIgaGFzIHRoZSBjYXRlZ29yaWVzOiAgbWlu
b3IgY29uY2VybnMgb3IgbWFqb3IgY29uY2VybnMNCj4gcmVnYXJkaW5nICJpc3N1ZXMiLCBJIHdp
bCBkaWZmZXJlbnRpYXRlIG15IGlzc3VlcyBieSB0aGlzIHF1YWxpdHkuIA0KPiBJIGFsc28gaGF2
ZSBlZGl0b3JpYWwgbml0cyByZWdhcmRpZ24gdW5kZXIgc3BlY2lmaWVkIHRleHQuIA0KPiANCj4g
TWFqb3IgY29uY2VybnM6IA0KPiAxKSBUaGUgc2VjdXJpdHkgc2VjdGlvbiBpcyBub3Qgc3VmZmlj
aWVudCBmb3IgYW55IHJldmlldyBieSB0aGUNCj4gU2VjdXJpdHkgYXJlYSANCj4gDQo+IFRoaXMg
ZHJhZnQgZGVwZW5kcyBvbiBJRFIgV0cgZHJhZnQgKGlldGYtaWRyLWJncC1wcmVmaXgtc2lkKSB0
aGF0DQo+IGRlZmluZXMgdGhlIEJHUCBTZWdtZW50IGF0dHJpYnV0ZS4gIElmIHRoaXMgYXR0cmli
dXRlIGlzIHVzZWQgd2l0aA0KPiBJUHY2LCB0aGlzIHNpbXBseSBnaXZlcyBtb3JlIGluZnJvbWF0
aW9uIGFib3V0IGEgbGluayB0byBhIG5leHQuIA0KPiBIb3dldmVyLCB0aGUgY29tYmluYXRpb24g
b2YgdGhpcyBpbmZvcm1hdGlvbiB3aXRoIHRoZSBpbmZvcm1hdGlvbg0KPiBwYXNzZWQgdXNpbmcg
ZHJhZnQtaWV0Zi1pZHItYmdwbHMtc2VnbWVudC1yb3V0aW5nLWVwZS0wOSB0aGF0IHV0aWxpemVz
DQo+IEJHUCB0byBwYXNzIEJHUCB0b3BvbG9naWVzIGluIEJHUCAtIHJlcXVpcmVzIGEgYmV0dGVy
IHNlY3VyaXR5DQo+IHNlY3Rpb24uICBCR1AtTFMgd2FzIGRlc2NyaWJlZCB0byBiZSBhbiAiaW5m
b3JtYXRpb24gZ2F0aGVyaW5nIg0KPiBmdW5jdGlvbiBoYW5kbGVkIGJ5IGEgZmV3IHJvdXRlcnMg
b24gdGhlIGVkZ2Ugb2YgdGhlIG5ldHdvcmsgdG8gb2J0YWluDQo+IGxpbmstc3RhdGUgdG9wb2xv
Z3kgaW5mb3JtYXRpb24uICBUaGUgQkdQIHBlZXJzIHdvdWxkIGNhcnJ5IHRoaXMNCj4gaW5mb3Jt
YXRpb24gaW4gYSBzZXBhcmF0ZSBpbmZvcm1hdGlvbmFsIHN0cmVhbS4gIFdpdGggdGhpcyBjb25z
dHJhaW50LA0KPiBpdCB3YXMgYXBwcm92ZWQgYnkgdGhlIElFU0cuICAgDQoNCg0Kd2VsbCwgd2Ug
aGF2ZSBub3cgZGlmZmVyZW50IG1vZGVscyB0aGF0IGhhdmUgYmVlbiBkZXBsb3llZCBhbmQgYXNz
dW1pbmcgdGhhdCBiZ3AtbHMgdXNlcyBhIHNlcGFyYXRlIHN0cmVhbSBpcyBub3QgYWNjdXJhdGUg
aWYgd2UgbG9vayB3aGF04oCZcyBpbiB0aGUgaW5kdXN0cnkuDQoNCkhvd2V2ZXIsIEkgdGFrZSB5
b3VyIHBvaW50IGFuZCBJIGFncmVlIHRoYXQgbW9yZSB0ZXh0IGluIHRoZSBzZWN1cml0eSBzZWN0
aW9uIGlzIHJlcXVpcmVkIGluIG9yZGVyIHRvIGVtcGhhc2l6ZSB0aGF0IHRoZSBtb2RlbCB0aGUg
ZHJhZnQgYWRkcmVzc2VzIGlzIGludGVybmFsIChEQyBhbmQgaW50ZXJjb25uZWN0ZWQgREMgb3Zl
ciBhIHNhbWUtYWRtaW5pc3RyYXRpb24gbmV0d29yaykuDQoNCg0KPiBkcmFmdC1pZXRmLWlkci1i
Z3Bscy1zZWdtZW50LXJvdXRpbmctZXBlICBleHBhbmRzIHRoZSBpbml0aWFsIGNvbmNlcHQNCj4g
b2YgQkdQLUxTIGZyb20gImluZm9ybWF0aW9uIGdhdGhlcmluZyIgdG8gYSBmdWxsLXJvdXRpbmcg
c2NoZW1lIG9mIEJHUA0KPiB3aXRoaW4gQkdQIGZvciBkYXRhIGNlbnRlcnMgYW5kIGZvciBkYXRh
IGNlbnRlciBpbnRlcmNvbm5lY3Rpb24gdG8gdGhlDQo+IG5ldHdvcmsuDQoNCg0KRVBFIGRlZmlu
ZXMgYSBtb2RlbCB3aGVyZSB0aGUgdG9wb2xvZ3kgb2YgdGhlIHBlZXJpbmcgcG9pbnQgKG5vdCB0
aGUgbmV0d29yaywganVzdCB0aGUgcGVlcmluZyBwb2ludCkgaXMgYWR2ZXJ0aXNlZCB0byBhbiBp
bnRlcm5hbCBzZXJ2ZXIuDQoNCg0KPiAgIFRoaXMgZXh0ZW5zaW9uIHRha2VzIGl0IG91dCBvZiB0
aGUgYXBwcm92ZWQgcmFuZ2Ugb2YgdGhlDQo+IEJHUC1MUy4NCg0KDQpJIGRvbuKAmXQga25vdyB3
aGF0IGlzIHRoZSDigJxhcHByb3ZlZCByYW5nZeKAnS4gVG8gbWUsIGJncC1scyBjYXJyaWVzIHRv
cG9sb2d5IGluZm9ybWF0aW9uLiBXZSBzdGFydGVkIHdpdGggbHNkYiwgdGhlbiBleHRlbmRlZCB0
byBtcGxzLWxzcCdzLCBpcCB0dW5uZWxzLCBwZWVyaW5nIHBvaW50cywgYW5kIG1vcmUgd2lsbCBj
b21lLg0KDQpUaGUgc2VjdXJpdHkgb2YgYmdwLWxzIGRvZXNu4oCZdCBjaGFuZ2UuIEl04oCZcyB0
aGUgYm91bmRhcnkgb2YgdGhlIG5ldHdvcmsgd2hlcmUgYmdwLWxzIGlzIGFwcGxpZWQgdGhhdCBt
YXR0ZXJzLg0KDQoNCj4gIFRoZXJlZm9yZSwgdGhlIHNlY3VyaXR5IHNlY3Rpb25zIGluIGJvdGgg
dGhlIElEUiBXRyBkcmFmdHMNCj4gYW5kIHRoaXMgZHJhZnQgbmVlZCB0byBkZXNjcmliZSB0aGUg
bmV3IHRocmVhdCBzY2VuYXJpb3MgYW5kIGRlc2NyaWJlDQo+IHRocmVhdCBtaXRpZ2F0aW9uIHN0
cmF0ZWdpZXMgZm9yIGRlcGxveW1lbnRzLiAgDQoNCg0KSSB3aWxsIGFkZCBtb3JlIHRleHQgYWJv
dXQgdGhlIGluZm9ybWF0aW9uIG9yaWdpbmF0ZWQgYnkgYmdwLWxzIChvciB0aGUgYmdwIHByZWZp
eCBzaWQpIGFuZCBob3cgaXQgaXMgaW50ZW5kZWQgdG8gYmUgY29uc3VtZWQgaW50ZXJuYWxseSB0
byBhIGRvbWFpbi4NCg0KDQo+IEluIGFkZGl0aW9uLCB0aGUgaW5mb3JtYXRpb24gYnkgQkdQLUxT
DQo+IChkcmFmdC1pZXRmLWlkci1iZ3Bscy1zZWdtZW50LXJvdXRpbmctZXBlKSBvciBpbiBkcmFm
dC1pZXRmLWJncC1zaWQNCj4gbWF5IGhhdmUgcHJpdmFjeSBpc3N1ZXMgLSBzbyB0aGVzZSBuZWVk
IHRvIGJlIGRlc2NyaWJlZCB0aGUgc2VjdXJpdHkNCj4gc2VjdGlvbi4gDQoNCg0Kc2FtZSBoZXJl
LiBJIHdpbGwgZW1waGFzaXplIHRoZSBkZXBsb3ltZW50IG1vZGVsIGFuZCB0aGUgc2VjdXJpdHkg
Ym91bmRhcmllcy4NCg0KDQo+IDIpIHRocm91Z2gtb3V0IHRoZSB0ZXh0IHlvdSB1c2Ugd29yZHMg
c3VjaCBhcyAiZWJncDMxMDciIG9yIEJHUCAzMTA3DQo+IHVwZGF0ZXMiDQo+IA0KPiBUaGlzIHBo
cmFzZSBpcyBpbmFjY3VyYXRlLiAgVGhlIGJhc2UgUkZDMzEwNyBzdXBwb3J0IHdpbGwgbm90IHBy
b3ZpZGUNCj4gQkdQLVByZWZpeCBzdXBwb3J0IChhcyBzdXBwb3J0ZWQgaW4gYmdwLWlkci1iZ3At
cHJlZml4LiAgIFNvbWUgdGV4dHMNCj4gZ29lcyBvbiB0byBjbGFyaWZ5IHRoZSBhZGRpdGlvbiBv
ZiB0aGUgQkdQIFNJRCBQcmVmaXggYXR0cmlidXRlLiAgSXQNCj4gd291bGQgYmUgYmV0dGVyIHRv
IGludmVudCBhIG5ldyBwaHJhc2Ugb3IgdGVybS4NCg0KDQpJ4oCZbGwgY2hlY2sgdGhpcyBvdXQu
DQoNCg0KPiBJbiBzZWN0aW9uIDguMSwgdGhlIGF1dGhvcnMgc3RhdGU6DQo+ICJUaGUgUHJlZml4
IFNlZ2VtZW50IGlzIGEgbGlnaHR3ZWlnaHQgZXh0ZW5zaW9uIHRvIHRoZSBCR1AgTGFiZWxsZWQN
Cj4gVW5pY2FzdCIuICBBcyBub3RlZCBpbiBteSAjMSBtYWpvciBjb25jZXJuLCB0aGlzICJoYW5k
LXdhdmluZyINCj4gZGVzY3JpcHRpb24gZWl0aGVyIG5lZWRzIHRvIGJlIHJlZmluZWQgdG8gYmUg
YWNjdXJhdGUuICBJZiB0aGUgTVBMUw0KPiB1c2FnZSBvbmx5IHVzZXMgdGhlIEJHUC1QcmVmaXgg
bGFiZWwgYW5kIGRvZXMgbm90IGV4dGVuZCB0byB0aGUNCj4gRWdyZXNzLCBpdCBpcyBzaW1wbGll
ci4NCg0KDQp0aGUgQkdQIFByZWZpeCBTSUQgQXR0cmlidXRlIGlzIGp1c3QgYW4gZXh0ZW5zaW9u
IHRvIGEgMzEwNyB1cGRhdGUuDQoNCg0KPiAgSG93ZXZlciwgaXQgaXMgbm90IGNsZWFyIHRoYXQg
aXMgd2hhdCBzZWN0aW9uDQo+IDguMSBpcyBhYm91dC4gICBJZiA4LjEgaW5jbHVkZXMgdGhlDQo+
IGRyYWZ0LWlldGYtaWRyLWJncGxzLXNlZ21lbnQtcm91dGluZy1lcGUsIHRoZW4gQkdQLUxTIGFk
ZGl0aW9uIGRvZXMNCj4gaGF2ZSBhIG51bWJlciBvZiBwcmVmaXhlcyBhbmQgcnVsZXMuICAgVGhl
IHRyYWRlLW9mZiBiZXR3ZWVuIEJHUC1MUyArDQo+IEJHUC1MUyBTSUQgKGRyYWZ0LWlldGYtaWRy
LWJncC1zaWQpIGhhbmRsaW5nICsgQkdQIExTIGVncmVzcyBwZWVyDQo+IGVuZ2luZWVyaW5nIGRy
YWZ0IChkcmFmdC1pZXRmLWlkci1iZ3Atc2VnbWVudC1yb3V0aW5nLWVwZSkgYW5kIGENCj4gc2ln
bmFsbGluZyBwcm90b2NvbCBpcyBtb3JlIGNvbXBsZXggdGhhbiB0aGUgaGFuZC13YXZlLg0KDQoN
Ck5vdCBzdXJlIEkgdW5kZXJzdGFuZCB5b3VyIHBvaW50IGJ1dCB0byBtZSB0aGUgc3RhdGVtZW50
OiANCuKAnFRoZSBQcmVmaXggU2VnZW1lbnQgaXMgYSBsaWdodHdlaWdodCBleHRlbnNpb24gdG8g
dGhlIEJHUCBMYWJlbGxlZCBVbmljYXN04oCdDQppcyBjb3JyZWN0IGJlY2F1c2UgdGhlIHByZWZp
eC1zaWQgaXMgcmVhbGx5IGp1c3QgYSBuZXcgYXR0cmlidXRlLiBIZXJlIHdl4oCZcmUganVzdCB0
YWxraW5nIHByb3RvY29sIGV4dGVuc2lvbi4NCg0KVGhlIGludGVyYWN0aW9uIGFuZCBjb21iaW5h
dGlvbiBiZXR3ZWVuIHByZWZpeC1zaWQgYW5kIGVwZSBpcyBhIGRlcGxveW1lbnQgYW5kIG9wZXJh
dGlvbmFsIG1vZGVsIHRoYXQgKHdlIGFncmVlZCBhYm92ZSkgcmVxdWlyZXMgbW9yZSBleHBsYW5h
dGlvbiBpbiB0ZXJtcyBvZiBzZWN1cml0eS4NCg0KDQo+ICBJdCBtYXkgYmUgdGhlDQo+IHJpZ2h0
IGNob2ljZSBiYXNlZCBvbiBjdXJyZW50IGltcGxlbWVudGF0aW9ucyBhbmQgbWFuYWdlbWVudCBp
c3N1ZXMsDQo+IGJ1dCB0aGVzZSBuZWVkIHRvIGJlIGxhaWQgc3BlY2lmaWNhbGx5LiANCj4gDQo+
IDMpIFdoeSBhcmUgeW91IGRlZmluaW5nIDItYnl0ZSBQcml2YXRlIFVzZSBBUyB3aGVuIHRoZXJl
IGFyZSBwbGVudHkgb2YNCj4gNC1CeXRlIFByaXZhdGUgVXNlIEFTIChwLiA1KS4gDQoNCg0Kd2Vs
bCwgd2UganVzdCB3YW50IHRvIGJlIHN1cmUgd2UgYWRkcmVzcyB0aGUgd29yc2UgY2FzZSB3aGVy
ZSB5b3Ugb25seSBoYXZlIDIgb2N0ZXRzLg0KDQoNCj4gDQo+IFRoaXMgdXNhZ2UgaW5jcmVhc2Vz
IHRoZSBjb25mdXNpb24gcmVnYXJkaW5nIDItYnl0ZS80LWJ5dGUgQVNOLiAgSURSDQo+IHNwZWNp
ZmljYWxseSB3b3JrZWQgb24gNCBieXRlIEFTTi4gDQoNCg0KeWVzIGJ1dCBpbiBvcmRlciB0byBi
ZSBhbGlnbmVkIHdpdGggNzkzOCB3ZSBhbHNvIHRha2UgaW50byBhY2NvdW50IDIgb2N0ZXQgQVNO
IGFuZCB0aGUgcmUtdXNhYmlsaXR5IG9mIHRoZXNlIG51bWJlcnMuDQoNCg0KPiBNaW5vciBjb25j
ZXJucyAgDQo+IDEpIEl0IGlzIG5vdCBjbGVhciB3aGF0IGhhcHBlbnMgaW4gc2VjdGlvbiA0LjIu
MiBhbmQgZmlndXJlIDMtNQ0KPiANCj4gV2hhdCBoYXBwZW5zIGlmIHRoZSB0cmFmZmljIGdvZXMg
dG8gbm9kZSAzIGluc3RlYWQgb2Ygbm9kZSA0IG9uIHRoZQ0KPiBFQ01QIHBhdGg/IA0KPiBXaGF0
IGhhcHBlbnMgaWYgdGhlIHRyYWZmaWMgZ29lcyB0byBub2RlIDggaW5zdGVhZCBvZiBub2RlIDcg
b24gdGhlDQo+IEVDTVAgUGF0aD8gDQo+IA0KPiBJcyB0aGVyZSBzb21ldGhpbmcgbWlzc2luZyBp
biB0aGUgc3Ryb3k/IA0KDQoNCm5vcGUuIFRoaXMgaXMgcGxhaW4gc2VnbWVudCByb3V0aW5nLiBB
cyBleHBsYWluZWQgaW4gdGhlIGRyYWZ0LCBhc3N1bWluZyB0aGF0IHlvdSB1c2UgdGhlIHNhbWUg
U1JHQiAoYXMgcmVjb21tZW5kZWQpIGEgbm9kZSBpcyBrbm93biB0aHJvdWdoIHRoZSBzYW1lIHNp
ZCB2YWx1ZSBhbGwgYWxvbmcgdGhlIG5ldHdvcmsgc28gZWNtcCBiZWNvbWVzIHRyaXZpYWwuDQoN
Cg0KPiAyKSBzZWN0aW9uIDQuMyAtIElCR1AgTGFiZWxlZCBVbmljYXN0LiANCj4gDQo+IFRoZSBw
aHJhc2UgImlCR1AzMTA3IHJlZmxlY3Rpb24gd2l0aCBuaG9wLXNlbGYiIG5lZWRzIHRvIGJlIGV4
cGxpY2l0bHkNCj4gc3BlbGxlZCBvdXQgYXMgSUJHUCBSb3V0ZS1SZWZsZWN0aW9uIHdpdGggbmV4
dC1ob3Agc2VsZi4NCg0KDQpvaw0KDQoNCj4gIElmIHRoYXQgaXMNCj4gbm90IHdoYXQgdGhlIGF1
dGhvcnMgbWVhbiwgdGhlbiBpdCBuZWVkcyB0byBiZSBmdXJ0aGVyIHNwZWxsZWQgb3V0LiANCj4g
SXQgaXMgdW5jbGVhciB3aGVyZSB0aGUgY2VudHJhbCBJQkdQIG5vZGVzIGFyZSB0aGF0IHNoYXJl
IGZ1bGx5IHRoZQ0KPiBpbmZvcm1hdGlvbiBsZWFybmVkIGZyb20gdGhlIHRocmVlIGNsdXN0ZXJz
LiAobm9kZXM6NS04IGNsdXN0ZXIgMSwNCj4gbm9kZXMgMy00IGNsdXN0ZXIgMiwgbm9kZXMgOS0x
MCBjbHVzdGVyIDMpLiAgDQo+IA0KPiBUaGlzIHNlY3Rpb24gaGFzIGhpbnRzIG9mIGEgc29sdXRp
b24sIGJ1dCBpdCBpcyBtaXNzIGEgZ3JlYXQgZGVhbC4gDQo+IFBsZWFzZSB1cGdyYWRlIHRvIHNw
ZWNpZmljIHNvbHV0aW9uLiAgQSBkaWFncmFtIG1pZ2h0IGhlbHAuIA0KDQoNCnllcy4gSeKAmWxs
IGNoZWNrIHRoaXMgb3V0LiBJbiBzaG9ydCAoeW91IGNlcnRhaW5seSBmaWd1cmVkIGl0IG91dCkg
aXTigJlzIGFib3V0IHVzaW5nIGlCR1Agc2Vzc2lvbiB3aGVyZSBlYWNoIG5vZGUgYWN0cyBhcyBh
IFJSIHNvIHRvIHByb3BhZ2F0ZSB0byBvdGhlciBpQkdQIHBlZXJzICh0aGlzIGlzIHdoYXQgImlC
R1AgcmVmbGVjdGlvbuKAnSByZWZlcnMgdG8pLiBJIGFncmVlLCBpdOKAmXMgcHJvYmFibHkgYSBi
aXQgdG9vIGNyeXB0aWMuDQoNCg0KPiAzKSBMb2FkIFNoYXJpbmcgaGludHMgKFNlY3Rpb24gNy4x
KSANCj4gDQo+IEVsZXBoYW50IGZsb3cgYW5kIG1pY2UgZmxvd3MgYXJlIGdvb2QgZGVzY3JpcHRp
b25zLiAgRmxvd2xldHMgYW5kIFZMMg0KPiBzaG91bGQgZWl0aGVyIHdhcnJhbnQgYSAxIHNlbnRl
bmNlIGV4cGxhbmF0aW9uIHRoYXQgYWN0dWFsbHkgZGVzY3JpYmVzDQo+IHRoZXNlIGZlYXR1cmVz
IGluIGEgMjIgcGFnZSBkcmFmdCwgb3IgYmUgcmVtb3ZlZC4gIA0KDQoNCldlIGhhdmUgYSByZWZl
cmVuY2UgZm9yIHRoZW0gYnV0IHdpbGwgYWRkIG1vcmUgdGV4dC4NCg0KDQo+IDQpICBUaGUgbGFj
ayBvZiBhIG1hbmFnZWFiaWxpdHkgb3Igb3BlcmF0aW9ucyBzZWN0aW9uIChUQkQgaW4gdmVyc2lv
bg0KPiAtMDIpIC0gY29uY2VybnMgbWUuICBUaGUgb3BlcmF0aW9uYWwgaXNzdWVzIG1heSBiZSB3
ZWxsIGtub3duIHRvIHRoZQ0KPiBkYXRhIGNlbnRlcnMgYW5kIGRldmljZXMgbWFudWZhY3R1cmVy
cyB3aG8gaGF2ZSBpbXBsZW1lbnQgdGhpcw0KPiBzcGVjaWZpY2F0aW9uLCBidXQgdGhpcyBpcyBh
biBpbnRlcm9wZXJhYmlsaXR5IHNwZWNpZmljYXRpb24gZm9yIElFVEYuDQo+IFNvbWUgbWFuYWdl
YWJpbHR5IGNvbW1lbnRzIHNob3VsZCBiZSBpbmNsdWRlZCBvciBhIEJDUCBwb2ludGVkIHRvLiAN
Cg0KDQphY2suDQoNCg0KPiBFZGl0b3JpYWwgaXNzdWVzOiANCg0KDQpJ4oCZbGwgZ28gdGhyb3Vn
aCBhbGwgYmVsb3cgYW5kIHVwZGF0ZSB0aGUgZHJhZnQgYXNhcC4NCg0KVGhhbmtzLg0Kcy4NCg0K
DQo+IA0KPiAjMSAtIFRoZSBmb2xsb3dpbmcgNCBhYmJyZXZpdGlvbnMgbmVlZCB0byBiZSBpbml0
aWFsbHkgZXhwYW5kZWQgd2hlbg0KPiBmaXJzdCB1c2VkOiAgQ0xPcyAocC4zKSwgIFNSR0IocC42
KSwgZmxvd2xldHMgKHAuIDE0KSwgYW5kIFZMMiAocC4NCj4gMTQpLiANCj4gDQo+ICMyIC0gcGFn
ZSA3LCBzZWN0aW9uIDQuMiBsYXN0IHBhcmFncmFwaCANCj4gT2xkLzogYXNzdW1pbmcgdGhlIElQ
IEFkZHJlc3NlcywgQVMgYW5kIGxhYmVsLWluZGV4IGFsbG9jYXRpb24NCj4gcHJldmlvdXNseSBk
ZXNjcmliZWQsIHRoZSINCj4gTmV3LzogYXNzdW1pbmcgdGhlIElQIGFkZHJlc3Mgd2l0aCB0aGUg
QVMgYW5kIGxhYmVsLWluZGV4IGFsbG9jYXRpb24NCj4gcHJldmlvdXNseSBkZXNjcmliZWQsIHRo
ZSIgDQo+IFtDb21tYSBpcyBvcHRpb25hbF0NCj4gDQo+ICMzIC0gcGFnZSAxNCwgc2VjdGlvbiA3
LjEgcGFyYWdyYXBoIDQsICAvKGUuZy4gc3BpbmUgc3dpdGNoIE5vZGUxKS8gIC0NCj4gYnkgdGhl
IGRpYWdyYW0gaXQgc2hvdWxkIGJlIG5vZGUgNS04IG9yIGFuIGVycm9yLiAgUGxlYXNlIGNoZWNr
IHRoZQ0KPiBudW1iZXIgDQo+IA0KPiAjNCAtIHBhZ2UgMTcsIHNlY3Rpb24gOC4yIHBhcmFncmFw
aCAyLiANCj4gDQo+IE9sZC8NCj4gVGhpcyBpcyBlYXNpbHkgYWNjb21wbGlzaGVkIGJ5IGVuY2Fw
c3VsYXRpbmcgdGhlIHRyYWZmZmljIGVpdGhlciANCj4gZGlyZWN0bHkgYXQgdGhlIGhvc3Qgb3Ig
dGhlIHNvdXJjZSBUb1Igbm9kZSBieSBwdXNoaW5nIHRoZSBCR1AtDQo+IFByZWZpeC1TSUQgb2Yg
dGhlIGRlc3RpbmF0aW9uIFRvUiBmb3IgaW50cmEtREMgdHJhZmZpYywgb3IgYm9yZGVyIA0KPiBu
b2RlIGZvciBpbnRlci1EQyBvciBEQy10by1vdXRzaWRlLXdvcmxkIHRyYWZmaWMuLw0KPiANCj4g
TmV3Lw0KPiBUaGlzIGlzIGVhc2lseSBhY2NvbXBsaXNoZWQgYnkgZW5jYXBzdWxhdGluZyB0aGUg
dHJhZmZmaWMgZWl0aGVyIA0KPiBkaXJlY3RseSBhdCB0aGUgaG9zdCBvciB0aGUgc291cmNlIFRv
UiBub2RlICBieSBwdXNoaW5nICB0aGUgQkdQLQ0KPiBQcmVmaXgtU0lEIG9mIHRoZSBkZXN0aW5h
dGlvbiBUb1IgZm9yIGludHJhLURDIHRyYWZmaWMsIG9yDQo+IHRoZSBCR1AtUHJlZml4LVNJRCBm
b3IgdGhlIHRoZSBib3JkZXIgbm9kZSBmb3IgaW50ZXItREMgb3INCj4gREMtdG8tb3V0c2lkZS13
b3JsZCB0cmFmZmljLi8NCj4gDQo+IElmIHRoaXMgaXMgbm90IHRoZSBjb3JyZWN0IGxvZ2ljLCB0
aGVuIHlvdSBjYW4gcmV3b3JkIHRoaXMgZnVydGhlci4gDQo+IEkgcmVhZCBpdCA0IG9yIDUgdGlt
ZXMuIA0KPiANCj4gIzUgLSBBZGRpbmcgYSBkaWFncmFtIHRvIHNlY3Rpb24gNC4zIG1pZ2h0IGhl
bHAgeW91ciBkZXNjcmlwdGlvbi4gDQo+IA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4gc3ByaW5nIG1haWxpbmcgbGlzdA0KPiBzcHJpbmdA
aWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zcHJpbmcN
Cg0K


From nobody Tue Mar  7 04:07:51 2017
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 6FE281295D0; Tue,  7 Mar 2017 04:07:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EUKFvuhKXb_q; Tue,  7 Mar 2017 04:07:46 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF713129484; Tue,  7 Mar 2017 04:07:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 51659BED7; Tue,  7 Mar 2017 12:07:43 +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 RzrP9kKFbg-r; Tue,  7 Mar 2017 12:07:40 +0000 (GMT)
Received: from [172.28.172.2] (unknown [109.125.19.162]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id BC0C0BED6; Tue,  7 Mar 2017 12:07:39 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1488888460; bh=+u2nQsvvauOHw8vUEr9zl0EW1BPBhalvvEfRs95Zw3A=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=BKj9tkKaRC8R5zpmjPGDkDCDRmEOaBs1L+cavcIZ9ljVzFJZA+OZ34MFN6+hKE3q1 wUffTZPubshODNXaair8Q5RxtxosokT/m994IrRVqMsqM06mvmYChG1y4j0GxNIF/L GohWL0LASFf49+S6XOZ8fjjN+YIo0/EdgtdP1Vos=
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
To: mohamed.boucadair@orange.com, Ted Hardie <ted.ietf@gmail.com>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com> <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup> <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com> <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <cebf0487-2d71-ea1e-5dd9-cf1d8c80df3a@cs.tcd.ie>
Date: Tue, 7 Mar 2017 12:07:38 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="s4rBBtEBM47UpdAmu9qPDdcCewgwTCP7d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PmUesGueTyEeTJBi1chH1kwAHA4>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 12:07:49 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--s4rBBtEBM47UpdAmu9qPDdcCewgwTCP7d
Content-Type: multipart/mixed; boundary="xXPbmgmPGO7Nl3eO80n6PvMr2941f0f85";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: mohamed.boucadair@orange.com, Ted Hardie <ted.ietf@gmail.com>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org"
 <draft-hardie-privsec-metadata-insertion@ietf.org>,
 "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <cebf0487-2d71-ea1e-5dd9-cf1d8c80df3a@cs.tcd.ie>
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt>
 (Design considerations for Metadata Insertion) to Informational RFC
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com>
 <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com>
 <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup>
 <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com>
 <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup>
In-Reply-To: <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup>

--xXPbmgmPGO7Nl3eO80n6PvMr2941f0f85
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi Med and Ted,

Thanks for the discussion. My conclusion from that is that
the best next step will be to continue with IESG evaluation.
Progressing this draft had fairly clear support in earlier
discussions on the saag list and in saag meetings, so it
may be Med that you're just in the rough - given the limited
comment during LC, I'd say getting the IESG to evaluate
this will be the easiest way to figure that out. And as an
outgoing AD, I'd much prefer to try get this sorted before
I'm done rather than leaving it to Kathleen or Eric to pick
up later. (Though we can go there if needed.) Anyway, I
think logistically it makes sense to keep this on the March
16th IESG telechat and see where we go from there. I'll
include a pointer to the archive for this mail so other
ADs can easily find this discussion.

As to the content of the discussion, I think Ted has answered
your comments, even though you and he haven't reached full
agreement on all topics. For me it seems like the remaining
areas of discussion were:-

- language around "restore" or not (fwiw I agree with Ted's
  take on that term)

- "consent" - actually it may be best to just remove the two
  uses of that term entirely - the term is fairly legally
  "loaded" and I'm not sure it's needed for this design
  advice anyway - if we can figure a way to rephrase those
  bits that may be an improvement worth making

I'll start the iesg evaluation process for -07 shortly.

Cheers,
S.

PS: Sorry if I've missed anything else that is outstanding.
The form of (not really;-) quoting earlier messages used makes
it very hard to follow the conversation over more than two
emails.

On 07/03/17 07:31, mohamed.boucadair@orange.com wrote:
> Hi Ted,
>=20
> Thank you for the answers.
>=20
> Please see inline.
>=20
> Cheers, Med
>=20
> De : Ted Hardie [mailto:ted.ietf@gmail.com] Envoy=C3=83=C2=A9 : lundi 6=
 mars
> 2017 18:14 =C3=83=E2=82=AC : BOUCADAIR Mohamed IMT/OLN Cc : ietf@ietf.o=
rg;
> draft-hardie-privsec-metadata-insertion@ietf.org Objet : Re: Last
> Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design
> considerations for Metadata Insertion) to Informational RFC
>=20
> Hi Mohamed, Replies in-line.
>=20
>=20
> On Mon, Mar 6, 2017 at 1:48 AM,
> <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
> wrote:
>=20
>=20
> =C3=A2=E2=82=AC=C2=A2         A Forward-For header inserted by a proxy =
does not restore
> any data; it does only reveal data that is already present in the
> packet issued by the client itself. That's what restore means here.=20
> [Med] Then, this needs to be defined in the document. I naively
> assumed that =C3=A2=E2=82=AC=C5=93restored=C3=A2=E2=82=AC=C2=9D is used=
 to mean any piece of information
> that the client does not want to insert in a packet, but an on-path
> device decides to inject it despite there is no consent from the
> client. What you are describing is more about =C3=A2=E2=82=AC=C5=93main=
taining=C3=A2=E2=82=AC=C2=9D or
> =C3=A2=E2=82=AC=C5=93preserving=C3=A2=E2=82=AC=C2=9D information not re=
storing it.
>=20
> The common uses of restore in English all focus on putting something
> back that has been lost, [Med] But that information is not lost for
> an on-path device that encapsulates a packet in another one (so the
> inner header is still carrying the source IP address) or the one that
> supplies the original source IP address as a metadata when source IP
> address/port rewriting is required. The notion of =C3=A2=E2=82=AC=C5=93=
putting back=C3=A2=E2=82=AC=C2=9D
> does not make sense to me because we are not dealing with the
> internal processing of a packet within an on-path device, but we only
> focus on the external behavior. This is exactly the role of =C3=A2=E2=82=
=AC=C5=93via=C3=A2=E2=82=AC=C2=9D
> headers for SIP proxies; when there is a mismatch the received tag is
> completed with the visible source address.
>=20
> so I believe restore is better than "maintain" or "preserve", which
> imply something is being carried forward as-is, rather than being put
> back after loss. [Med] Please see above. Because we don=C3=A2=E2=82=AC=E2=
=84=A2t have a
> standard behavior of an on-path device (proxy, tunnel-endpoint.), I
> seems weird to me to say that a proxy that preserves the source IP
> address is =C3=A2=E2=82=AC=C5=93putting pack an information that is los=
t=C3=A2=E2=82=AC=C2=9D.
>=20
>=20
> If the information is present as metadata in the packet sent to the
> proxy but would be absent as metadata under normal operation of the
> proxy, adding it back in somewhere else restores the metadata. [Med]
> =C3=A2=E2=82=AC=C5=93normal operation of proxy=C3=A2=E2=82=AC=C2=9D is =
not a standard. A =C3=A2=E2=82=AC=C5=93normal
> operation of proxy=C3=A2=E2=82=AC=C2=9D would be to maintain the inform=
ation sent by
> the client when relaying it to the server. I=C3=A2=E2=82=AC=E2=84=A2m s=
ure you know for
> instance that SIP B2BUAs can do whatever they want!
>=20
> You're right that the normal operation of a proxy is not a standard,
> and I should have said "the normal operation of the protocols used by
> a proxy". [Med] This is much better, but still not sufficient.
> On-path devices that manipulate packets may not be a
> =C3=A2=E2=82=AC=C5=93protocol-specific proxy=C3=A2=E2=82=AC=C2=9D: tunn=
el endpoint (e.g., LISP), CGN
> (NAT64, NAT44, DS-Lite), MAP-E BR, etc.
>=20
> If the action of the proxy is to start a new TCP connection to an
> origin server, for example, the normal operation of TCP is to use the
> initiator's IP address. [Med] This is protocol-specific. I can
> provide an example of a proxy behavior that relays the source IP
> address/port as part of its normal operation:
> http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt - TCP/IPv4
> : "PROXY TCP4 255.255.255.255 255.255.255.255 65535 65535\r\n" =3D> 5 +=

> 1 + 4 + 1 + 15 + 1 + 15 + 1 + 5 + 1 + 5 + 2 =3D 56 chars
>=20
> - TCP/IPv6 : "PROXY TCP6 ffff:f...f:ffff ffff:f...f:ffff 65535
> 65535\r\n" =3D> 5 + 1 + 4 + 1 + 39 + 1 + 39 + 1 + 5 + 1 + 5 + 2 =3D 104=

> chars
>=20
>=20
> The loses the IP address of the querying host is implied by that
> normal operation(in other words, it elides metadata about any client
> that caused this new TCP connection to be createD). [Med] This makes
> sense if losing the original IP address is an intended propriety of
> the proxy. But this cannot be a generalized proxy behavior (see the
> example above).
>=20
> So origin IP address starts out in the IP header of the original
> packet but gets pushed from that slot when the proxy constructs the
> onward IP packet to the server.  For it to reach the server, it has
> to be placed somewhere else in the onward packet, restoring the lost
> metadata. [Med] The client agreed to send packets with its source IP
> address (which mean consent). Why the proxy would need to an extra
> channel to get consent for relaying the source IP address to a
> server?
>=20
>=20
> Because the client agreed to send packets to the proxy by putting it
> in the destination [Med] The client is not even aware that proxy
> exists on the path! Packets are sent to the ultimate server=C3=A2=E2=82=
=AC=E2=84=A2s
> address, not the one of the proxy. Even for SOME cases where packets
> are sent explicitly to the proxy (e.g., SOCKS proxy), a state is
> already in place to graft the outgoing packets to a binding context
> involving the destination server.
>=20
> , and did not agree to general disclosure; you can't infer onward
> consent. [Med] Hmm=C3=A2=E2=82=AC=C2=A6I=C3=A2=E2=82=AC=E2=84=A2m afrai=
d this conclusion is not technically
> backed, e.g., * A client that sends packets to a server located on
> the Internet is NOT necessarily aware that a proxy is solicited in
> forwarding path. Packets are sent using the server=C3=A2=E2=82=AC=E2=84=
=A2s IP address. *
> The client and proxy may be owned by the same administrative entity
> (case of enterprise networks). That entity is responsible for ensure
> which information the proxy needs to leak. * The proxy and the server
> may be owned by the same administrative entity (content provider).
> Supplying data by a proxy to the server, based on the content of a
> packet received from a host, does not induce a privacy concern here
> because the proxy and the server owned by the same entity.
>=20
> Had it been present in the packet as header value in the HTTP
> exchange, it would not have been stripped by normal operation.  There
> proxy operation forwarding it on would be simply preserving it. [Med]
> This is another question: whether the same or distinct channel can be
> used to communicate the SAME data that was present in the initial
> packet issued by a host.
>=20
>=20
> That depends on the nature of the channel.  Obviously, if you set the
> origin clients IP address as the source address, you're going to get
> a different result from that spoofing than putting it in a client
> subnet EDNS option or forwarded-for header. [Med] Agree.
>=20
>=20
> =C3=A2=E2=82=AC=C2=A2         An address sharing device, under for exam=
ple DS-Lite
> (RFC6333), that inserts the source IPv6 prefix in the TCP HOST_ID
> option (RFC7974) is not RESTORING any data. The content of that TCP
> option is already visible in the packet sent by the host. I agree
> with the IESG analysis of RFC7974.  It does restore information by
> taking information which normal operation would have elided and
> restores it. [Med] The  implication of what you are saying here is
> that proxies are good because they hide the source IP addresses of
> host!
>=20
>=20
> Aggregating proxies can have a positive privacy impact, yes.  An
> observer seeing traffic from an aggregating proxy to
> sensitive-topic.example.com<http://sensitive-topic.example.com> knows
> only that some user behind that proxy is looking for information on
> sensitive-topic.  To know which user, the observer must have either
> suborned the proxy or have a way of observing traffic between hosts
> and the proxy.  Both are more expensive and at higher risk of
> discovery than a simple tap near
> sensitive-topic.example.com<http://sensitive-topic.example.com>.
>=20
> [Med] The main point here is that, even in the presence of an
> aggregating proxy, a server can demux users by correlating various
> information leaked at the application layer (e.g.,
> https://panopticlick.eff.org/). Tracking those users when they change
> their source IP address is possible in this case, too.
>=20
>=20
> If the data is taken from a portion of the packet that would not
> normally be forwarded to an upstream host and added to a portion that
> is forwarded to an upstream host, then the device adding the data
> back in should know it is a restoration. [Med] That definition is not
> trivial as mentioned above. I would use =C3=A2=E2=82=AC=C5=93preserve=C3=
=A2=E2=82=AC=C2=9D or
> =C3=A2=E2=82=AC=C5=93maintain=C3=A2=E2=82=AC=C2=9D rather than =C3=A2=E2=
=82=AC=C5=93restore=C3=A2=E2=82=AC=C2=9D. Please see above.
> "Restore" is closer, in my opinion, than either preserve or
> maintain.
>=20
>=20
>=20
> If the endpoint sends the data, data will be consistently available
> in that header.  The data changes, of course. [Med] I=C3=A2=E2=82=AC=E2=
=84=A2m not sure to
> follow you here. What is meant by =C3=A2=E2=82=AC=C5=93consistent avail=
ability=C3=A2=E2=82=AC=C2=9D then?
> Do you mean the same channel/procedure to communicate the
> information? Or =C3=A2=E2=82=AC=C5=93consistent data=C3=A2=E2=82=AC=C2=9D=
?
>=20
> I mean that if you define a protocol such that a well-formed message
> from the client has the data the server needs, it will be
> consistently available.  If you rely on intermediate network devices
> to add the data, it may not be available if there is not cooperating
> network device on path (e.g. if the DNS resolver does not support the
> relevant EDNS0 option).
>=20
> [Med] Thank you. Please clarify this in the draft. I had troubles to
> parse what you meant by =C3=A2=E2=82=AC=C5=93consistent availability=C3=
=A2=E2=82=AC=C2=9D. That=C3=A2=E2=82=AC=E2=84=A2s said,
> there might be also =C3=A2=E2=82=AC=C5=93not cooperating on-path device=
s=C3=A2=E2=82=AC=C2=9D that may
> strip/alter the content of client supplied data (easy for HTTP for
> example).
>=20
>=20
>=20
> [Med] Resources may not be restricted to CPU or disk but may be
> granting access to the service (e.g., download a file when a quota
> per source address is enforced). It can be whatever the servers
> consider to be critical for them; it is up to the taste of the
> service design to characterize it. The NEW wording proposed above is
> technically correct. Please reconsider adding it to the draft.
>=20
>=20
>=20
> I did consider it, but I continue to believe that it moves the needle
> too far into simple server preference.  I retained the original PSAP
> language in -07 as a result. [Med] emergency is only an example ;
> other services may exist that impose the same trust model.
>=20
>=20
> I think there is a qualitative difference between situations in which
> the resources at risk are human lives and those where they are host
> resources. [Med] I agree with you as an individual. But, it is not up
> to us to mandate this condition for executing services. It is up to
> the (protocol) designers/service providers to decide what is
> critical/key for their service operation. That's why the carve out
> was limited in the GEOPRIV case. [Med] GEOPRIV is not the only
> protocol/service that is concerned with human lives, we can consider
> vehicular networking that trust the information shared by the
> infrastructure. I prefer neutral wording that cites emergency as an
> example.
>=20
>=20
> I also added a note about your extensive review.  While you and I
> clearly have some differences of view, the document has gotten better
> from your engagement with it, and I appreciate your efforts. [Med] I
> reviewed the -07. Although it is better compared to -05, I still
> don=C3=A2=E2=82=AC=E2=84=A2t think it is ready to be published as it is=
=2E Thank you for
> your effort. And thank you for yours, regards, Ted
>=20
> regards, Ted
>=20


--xXPbmgmPGO7Nl3eO80n6PvMr2941f0f85--

--s4rBBtEBM47UpdAmu9qPDdcCewgwTCP7d
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYvqKKAAoJEC88hzaAX42ilS8H/1yKeGrFHzR+B5AQReGct1R+
Truhn8a/J8ySTxUMw5zVC35xXW6OtvsvkKHjPWauc+cZm6khXOHWP7h/uzvLlPa0
r67nN5oJQ69JIQbl+la4FXghdL8N8Tgl4Srb23pw68J1SO00BPmZEkPWaym3uo2O
fA+H13xTjk/1wu9NlH1+MchNEQKjDGqv2AhUMtGN5LsvuMFUixJ9xlzWLDdw3p2q
inO6yq47YiQ16A2aiRus2IVcfSAuyjYNZ93vLvFUV/oBRBT5cbG9P9nXfvsymZKT
Zl0yGTAH0ixH1SwVM2Medcaj2pUJ8e1HtxZhJLK+HguZn6J2hcxxbtx0EgEGWzs=
=/MQ9
-----END PGP SIGNATURE-----

--s4rBBtEBM47UpdAmu9qPDdcCewgwTCP7d--


From nobody Tue Mar  7 05:03:35 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9342129416; Tue,  7 Mar 2017 05:03:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kXaT-d2Aj8FA; Tue,  7 Mar 2017 05:03:31 -0800 (PST)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B95441293E3; Tue,  7 Mar 2017 05:03:30 -0800 (PST)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 20182C074C; Tue,  7 Mar 2017 14:03:29 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.69]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id D04FF1A0062; Tue,  7 Mar 2017 14:03:28 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA2.corporate.adroot.infra.ftgroup ([fe80::bc1c:ad2f:eda3:8c3d%18]) with mapi id 14.03.0319.002; Tue, 7 Mar 2017 14:03:28 +0100
From: <mohamed.boucadair@orange.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Ted Hardie <ted.ietf@gmail.com>
Subject: RE: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Topic: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Index: AQHSlztu9TXozPQ51U2U3i46uC5cY6GJTDAw
Date: Tue, 7 Mar 2017 13:03:28 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E1D615@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com> <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup> <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com> <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup> <cebf0487-2d71-ea1e-5dd9-cf1d8c80df3a@cs.tcd.ie>
In-Reply-To: <cebf0487-2d71-ea1e-5dd9-cf1d8c80df3a@cs.tcd.ie>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1-zBHqKNlpsJGlpyKgajoZmsU1Q>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 13:03:34 -0000

SGkgU3RlcGhlbiwNCg0KRmlyc3Qgb2YgYWxsLCBJIHJlYWxseSB0aGFuayBUZWQgZm9yIGVuZ2Fn
aW5nIGFuZCBmb3IgbWFraW5nIHNvbWUgY2hhbmdlcyB0byB0aGUgZG9jdW1lbnQuIFRoYXQncyBt
dWNoIGFwcHJlY2lhdGVkLiBOZXZlcnRoZWxlc3MsIEkgc3RpbGwgdGhpbmsgdGhlIGRvY3VtZW50
IGlzbid0IHJlYWR5IHRvIGJlIHB1Ymxpc2hlZCBhcyBpdCBpcyB3aXRoIGFuIElFVEYgY29uc2Vu
c3VzLiAgIA0KDQpUaGUgcG9pbnQgeW91IG1lbnRpb25lZCBhYm91dCAicmVzdG9yZSIgaXMgb25l
IG9mIHRoZSBkaXNhZ3JlZW1lbnRzLCBidXQgbm90IHRoZSBvbmx5IG9uZS4gSSBob3BlIHRoZSBk
aXNjdXNzaW9uIHdpbGwgY29udGludWUgd2l0aCBUZWQgdG8gZml4IHRoaXMgaW4gdGhlIGRvY3Vt
ZW50Lg0KDQpJIGNoZWNrZWQgdGhlIFNBQUcgYXJjaGl2ZXMsIGJ1dCwgdW5sZXNzIEknbSBtaXN0
YWtlbiwgSSBmYWlsZWQgdG8gZmluZCBhIHRlY2huaWNhbCBkaXNjdXNzaW9uIGFib3V0IHRoZSBj
b250ZW50IG9mIHRoZSBkcmFmdCBvciBhIHRocmVhZCBhYm91dCAiZmFpcmx5IGNsZWFyIHN1cHBv
cnQiIHRvICJwcm9ncmVzc2luZyB0aGlzIGRyYWZ0Ii4gDQoNCkkgZG9uJ3QgdGhpbmsgdGhlcmUg
aXMgYSBydXNoIHRvIHB1Ymxpc2ggdGhlIGRvY3VtZW50LiBEbyB3ZT8NCg0KQ2hlZXJzLA0KTWVk
IA0KDQo+IC0tLS0tTWVzc2FnZSBkJ29yaWdpbmUtLS0tLQ0KPiBEZcKgOiBTdGVwaGVuIEZhcnJl
bGwgW21haWx0bzpzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllXQ0KPiBFbnZvecOpwqA6IG1hcmRp
IDcgbWFycyAyMDE3IDEzOjA4DQo+IMOAwqA6IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE47IFRl
ZCBIYXJkaWUNCj4gQ2PCoDogZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRhdGEtaW5zZXJ0aW9u
QGlldGYub3JnOyBpZXRmQGlldGYub3JnDQo+IE9iamV0wqA6IFJlOiBMYXN0IENhbGw6IDxkcmFm
dC1oYXJkaWUtcHJpdnNlYy1tZXRhZGF0YS1pbnNlcnRpb24tMDUudHh0Pg0KPiAoRGVzaWduIGNv
bnNpZGVyYXRpb25zIGZvciBNZXRhZGF0YSBJbnNlcnRpb24pIHRvIEluZm9ybWF0aW9uYWwgUkZD
DQo+IA0KPiANCj4gSGkgTWVkIGFuZCBUZWQsDQo+IA0KPiBUaGFua3MgZm9yIHRoZSBkaXNjdXNz
aW9uLiBNeSBjb25jbHVzaW9uIGZyb20gdGhhdCBpcyB0aGF0DQo+IHRoZSBiZXN0IG5leHQgc3Rl
cCB3aWxsIGJlIHRvIGNvbnRpbnVlIHdpdGggSUVTRyBldmFsdWF0aW9uLg0KPiBQcm9ncmVzc2lu
ZyB0aGlzIGRyYWZ0IGhhZCBmYWlybHkgY2xlYXIgc3VwcG9ydCBpbiBlYXJsaWVyDQo+IGRpc2N1
c3Npb25zIG9uIHRoZSBzYWFnIGxpc3QgYW5kIGluIHNhYWcgbWVldGluZ3MsIHNvIGl0DQo+IG1h
eSBiZSBNZWQgdGhhdCB5b3UncmUganVzdCBpbiB0aGUgcm91Z2ggLSBnaXZlbiB0aGUgbGltaXRl
ZA0KPiBjb21tZW50IGR1cmluZyBMQywgSSdkIHNheSBnZXR0aW5nIHRoZSBJRVNHIHRvIGV2YWx1
YXRlDQo+IHRoaXMgd2lsbCBiZSB0aGUgZWFzaWVzdCB3YXkgdG8gZmlndXJlIHRoYXQgb3V0LiBB
bmQgYXMgYW4NCj4gb3V0Z29pbmcgQUQsIEknZCBtdWNoIHByZWZlciB0byB0cnkgZ2V0IHRoaXMg
c29ydGVkIGJlZm9yZQ0KPiBJJ20gZG9uZSByYXRoZXIgdGhhbiBsZWF2aW5nIGl0IHRvIEthdGhs
ZWVuIG9yIEVyaWMgdG8gcGljaw0KPiB1cCBsYXRlci4gKFRob3VnaCB3ZSBjYW4gZ28gdGhlcmUg
aWYgbmVlZGVkLikgQW55d2F5LCBJDQo+IHRoaW5rIGxvZ2lzdGljYWxseSBpdCBtYWtlcyBzZW5z
ZSB0byBrZWVwIHRoaXMgb24gdGhlIE1hcmNoDQo+IDE2dGggSUVTRyB0ZWxlY2hhdCBhbmQgc2Vl
IHdoZXJlIHdlIGdvIGZyb20gdGhlcmUuIEknbGwNCj4gaW5jbHVkZSBhIHBvaW50ZXIgdG8gdGhl
IGFyY2hpdmUgZm9yIHRoaXMgbWFpbCBzbyBvdGhlcg0KPiBBRHMgY2FuIGVhc2lseSBmaW5kIHRo
aXMgZGlzY3Vzc2lvbi4NCj4gDQo+IEFzIHRvIHRoZSBjb250ZW50IG9mIHRoZSBkaXNjdXNzaW9u
LCBJIHRoaW5rIFRlZCBoYXMgYW5zd2VyZWQNCj4geW91ciBjb21tZW50cywgZXZlbiB0aG91Z2gg
eW91IGFuZCBoZSBoYXZlbid0IHJlYWNoZWQgZnVsbA0KPiBhZ3JlZW1lbnQgb24gYWxsIHRvcGlj
cy4gRm9yIG1lIGl0IHNlZW1zIGxpa2UgdGhlIHJlbWFpbmluZw0KPiBhcmVhcyBvZiBkaXNjdXNz
aW9uIHdlcmU6LQ0KPiANCj4gLSBsYW5ndWFnZSBhcm91bmQgInJlc3RvcmUiIG9yIG5vdCAoZndp
dyBJIGFncmVlIHdpdGggVGVkJ3MNCj4gICB0YWtlIG9uIHRoYXQgdGVybSkNCj4gDQo+IC0gImNv
bnNlbnQiIC0gYWN0dWFsbHkgaXQgbWF5IGJlIGJlc3QgdG8ganVzdCByZW1vdmUgdGhlIHR3bw0K
PiAgIHVzZXMgb2YgdGhhdCB0ZXJtIGVudGlyZWx5IC0gdGhlIHRlcm0gaXMgZmFpcmx5IGxlZ2Fs
bHkNCj4gICAibG9hZGVkIiBhbmQgSSdtIG5vdCBzdXJlIGl0J3MgbmVlZGVkIGZvciB0aGlzIGRl
c2lnbg0KPiAgIGFkdmljZSBhbnl3YXkgLSBpZiB3ZSBjYW4gZmlndXJlIGEgd2F5IHRvIHJlcGhy
YXNlIHRob3NlDQo+ICAgYml0cyB0aGF0IG1heSBiZSBhbiBpbXByb3ZlbWVudCB3b3J0aCBtYWtp
bmcNCj4gDQo+IEknbGwgc3RhcnQgdGhlIGllc2cgZXZhbHVhdGlvbiBwcm9jZXNzIGZvciAtMDcg
c2hvcnRseS4NCj4gDQo+IENoZWVycywNCj4gUy4NCj4gDQo+IFBTOiBTb3JyeSBpZiBJJ3ZlIG1p
c3NlZCBhbnl0aGluZyBlbHNlIHRoYXQgaXMgb3V0c3RhbmRpbmcuDQo+IFRoZSBmb3JtIG9mIChu
b3QgcmVhbGx5Oy0pIHF1b3RpbmcgZWFybGllciBtZXNzYWdlcyB1c2VkIG1ha2VzDQo+IGl0IHZl
cnkgaGFyZCB0byBmb2xsb3cgdGhlIGNvbnZlcnNhdGlvbiBvdmVyIG1vcmUgdGhhbiB0d28NCj4g
ZW1haWxzLg0KPiANCj4gT24gMDcvMDMvMTcgMDc6MzEsIG1vaGFtZWQuYm91Y2FkYWlyQG9yYW5n
ZS5jb20gd3JvdGU6DQo+ID4gSGkgVGVkLA0KPiA+DQo+ID4gVGhhbmsgeW91IGZvciB0aGUgYW5z
d2Vycy4NCj4gPg0KPiA+IFBsZWFzZSBzZWUgaW5saW5lLg0KPiA+DQo+ID4gQ2hlZXJzLCBNZWQN
Cj4gPg0KPiA+IERlIDogVGVkIEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbV0gRW52
b3nDg8KpIDogbHVuZGkgNiBtYXJzDQo+ID4gMjAxNyAxODoxNCDDg+KCrCA6IEJPVUNBREFJUiBN
b2hhbWVkIElNVC9PTE4gQ2MgOiBpZXRmQGlldGYub3JnOw0KPiA+IGRyYWZ0LWhhcmRpZS1wcml2
c2VjLW1ldGFkYXRhLWluc2VydGlvbkBpZXRmLm9yZyBPYmpldCA6IFJlOiBMYXN0DQo+ID4gQ2Fs
bDogPGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbi0wNS50eHQ+IChEZXNp
Z24NCj4gPiBjb25zaWRlcmF0aW9ucyBmb3IgTWV0YWRhdGEgSW5zZXJ0aW9uKSB0byBJbmZvcm1h
dGlvbmFsIFJGQw0KPiA+DQo+ID4gSGkgTW9oYW1lZCwgUmVwbGllcyBpbi1saW5lLg0KPiA+DQo+
ID4NCj4gPiBPbiBNb24sIE1hciA2LCAyMDE3IGF0IDE6NDggQU0sDQo+ID4gPG1vaGFtZWQuYm91
Y2FkYWlyQG9yYW5nZS5jb208bWFpbHRvOm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20+Pg0K
PiA+IHdyb3RlOg0KPiA+DQo+ID4NCj4gPiDDouKCrMKiICAgICAgICAgQSBGb3J3YXJkLUZvciBo
ZWFkZXIgaW5zZXJ0ZWQgYnkgYSBwcm94eSBkb2VzIG5vdCByZXN0b3JlDQo+ID4gYW55IGRhdGE7
IGl0IGRvZXMgb25seSByZXZlYWwgZGF0YSB0aGF0IGlzIGFscmVhZHkgcHJlc2VudCBpbiB0aGUN
Cj4gPiBwYWNrZXQgaXNzdWVkIGJ5IHRoZSBjbGllbnQgaXRzZWxmLiBUaGF0J3Mgd2hhdCByZXN0
b3JlIG1lYW5zIGhlcmUuDQo+ID4gW01lZF0gVGhlbiwgdGhpcyBuZWVkcyB0byBiZSBkZWZpbmVk
IGluIHRoZSBkb2N1bWVudC4gSSBuYWl2ZWx5DQo+ID4gYXNzdW1lZCB0aGF0IMOi4oKsxZNyZXN0
b3JlZMOi4oKswp0gaXMgdXNlZCB0byBtZWFuIGFueSBwaWVjZSBvZiBpbmZvcm1hdGlvbg0KPiA+
IHRoYXQgdGhlIGNsaWVudCBkb2VzIG5vdCB3YW50IHRvIGluc2VydCBpbiBhIHBhY2tldCwgYnV0
IGFuIG9uLXBhdGgNCj4gPiBkZXZpY2UgZGVjaWRlcyB0byBpbmplY3QgaXQgZGVzcGl0ZSB0aGVy
ZSBpcyBubyBjb25zZW50IGZyb20gdGhlDQo+ID4gY2xpZW50LiBXaGF0IHlvdSBhcmUgZGVzY3Jp
YmluZyBpcyBtb3JlIGFib3V0IMOi4oKsxZNtYWludGFpbmluZ8Oi4oKswp0gb3INCj4gPiDDouKC
rMWTcHJlc2VydmluZ8Oi4oKswp0gaW5mb3JtYXRpb24gbm90IHJlc3RvcmluZyBpdC4NCj4gPg0K
PiA+IFRoZSBjb21tb24gdXNlcyBvZiByZXN0b3JlIGluIEVuZ2xpc2ggYWxsIGZvY3VzIG9uIHB1
dHRpbmcgc29tZXRoaW5nDQo+ID4gYmFjayB0aGF0IGhhcyBiZWVuIGxvc3QsIFtNZWRdIEJ1dCB0
aGF0IGluZm9ybWF0aW9uIGlzIG5vdCBsb3N0IGZvcg0KPiA+IGFuIG9uLXBhdGggZGV2aWNlIHRo
YXQgZW5jYXBzdWxhdGVzIGEgcGFja2V0IGluIGFub3RoZXIgb25lIChzbyB0aGUNCj4gPiBpbm5l
ciBoZWFkZXIgaXMgc3RpbGwgY2FycnlpbmcgdGhlIHNvdXJjZSBJUCBhZGRyZXNzKSBvciB0aGUg
b25lIHRoYXQNCj4gPiBzdXBwbGllcyB0aGUgb3JpZ2luYWwgc291cmNlIElQIGFkZHJlc3MgYXMg
YSBtZXRhZGF0YSB3aGVuIHNvdXJjZSBJUA0KPiA+IGFkZHJlc3MvcG9ydCByZXdyaXRpbmcgaXMg
cmVxdWlyZWQuIFRoZSBub3Rpb24gb2Ygw6LigqzFk3B1dHRpbmcgYmFja8Oi4oKswp0NCj4gPiBk
b2VzIG5vdCBtYWtlIHNlbnNlIHRvIG1lIGJlY2F1c2Ugd2UgYXJlIG5vdCBkZWFsaW5nIHdpdGgg
dGhlDQo+ID4gaW50ZXJuYWwgcHJvY2Vzc2luZyBvZiBhIHBhY2tldCB3aXRoaW4gYW4gb24tcGF0
aCBkZXZpY2UsIGJ1dCB3ZSBvbmx5DQo+ID4gZm9jdXMgb24gdGhlIGV4dGVybmFsIGJlaGF2aW9y
LiBUaGlzIGlzIGV4YWN0bHkgdGhlIHJvbGUgb2Ygw6LigqzFk3ZpYcOi4oKswp0NCj4gPiBoZWFk
ZXJzIGZvciBTSVAgcHJveGllczsgd2hlbiB0aGVyZSBpcyBhIG1pc21hdGNoIHRoZSByZWNlaXZl
ZCB0YWcgaXMNCj4gPiBjb21wbGV0ZWQgd2l0aCB0aGUgdmlzaWJsZSBzb3VyY2UgYWRkcmVzcy4N
Cj4gPg0KPiA+IHNvIEkgYmVsaWV2ZSByZXN0b3JlIGlzIGJldHRlciB0aGFuICJtYWludGFpbiIg
b3IgInByZXNlcnZlIiwgd2hpY2gNCj4gPiBpbXBseSBzb21ldGhpbmcgaXMgYmVpbmcgY2Fycmll
ZCBmb3J3YXJkIGFzLWlzLCByYXRoZXIgdGhhbiBiZWluZyBwdXQNCj4gPiBiYWNrIGFmdGVyIGxv
c3MuIFtNZWRdIFBsZWFzZSBzZWUgYWJvdmUuIEJlY2F1c2Ugd2UgZG9uw6LigqzihKJ0IGhhdmUg
YQ0KPiA+IHN0YW5kYXJkIGJlaGF2aW9yIG9mIGFuIG9uLXBhdGggZGV2aWNlIChwcm94eSwgdHVu
bmVsLWVuZHBvaW50LiksIEkNCj4gPiBzZWVtcyB3ZWlyZCB0byBtZSB0byBzYXkgdGhhdCBhIHBy
b3h5IHRoYXQgcHJlc2VydmVzIHRoZSBzb3VyY2UgSVANCj4gPiBhZGRyZXNzIGlzIMOi4oKsxZNw
dXR0aW5nIHBhY2sgYW4gaW5mb3JtYXRpb24gdGhhdCBpcyBsb3N0w6LigqzCnS4NCj4gPg0KPiA+
DQo+ID4gSWYgdGhlIGluZm9ybWF0aW9uIGlzIHByZXNlbnQgYXMgbWV0YWRhdGEgaW4gdGhlIHBh
Y2tldCBzZW50IHRvIHRoZQ0KPiA+IHByb3h5IGJ1dCB3b3VsZCBiZSBhYnNlbnQgYXMgbWV0YWRh
dGEgdW5kZXIgbm9ybWFsIG9wZXJhdGlvbiBvZiB0aGUNCj4gPiBwcm94eSwgYWRkaW5nIGl0IGJh
Y2sgaW4gc29tZXdoZXJlIGVsc2UgcmVzdG9yZXMgdGhlIG1ldGFkYXRhLiBbTWVkXQ0KPiA+IMOi
4oKsxZNub3JtYWwgb3BlcmF0aW9uIG9mIHByb3h5w6LigqzCnSBpcyBub3QgYSBzdGFuZGFyZC4g
QSDDouKCrMWTbm9ybWFsDQo+ID4gb3BlcmF0aW9uIG9mIHByb3h5w6LigqzCnSB3b3VsZCBiZSB0
byBtYWludGFpbiB0aGUgaW5mb3JtYXRpb24gc2VudCBieQ0KPiA+IHRoZSBjbGllbnQgd2hlbiBy
ZWxheWluZyBpdCB0byB0aGUgc2VydmVyLiBJw6LigqzihKJtIHN1cmUgeW91IGtub3cgZm9yDQo+
ID4gaW5zdGFuY2UgdGhhdCBTSVAgQjJCVUFzIGNhbiBkbyB3aGF0ZXZlciB0aGV5IHdhbnQhDQo+
ID4NCj4gPiBZb3UncmUgcmlnaHQgdGhhdCB0aGUgbm9ybWFsIG9wZXJhdGlvbiBvZiBhIHByb3h5
IGlzIG5vdCBhIHN0YW5kYXJkLA0KPiA+IGFuZCBJIHNob3VsZCBoYXZlIHNhaWQgInRoZSBub3Jt
YWwgb3BlcmF0aW9uIG9mIHRoZSBwcm90b2NvbHMgdXNlZCBieQ0KPiA+IGEgcHJveHkiLiBbTWVk
XSBUaGlzIGlzIG11Y2ggYmV0dGVyLCBidXQgc3RpbGwgbm90IHN1ZmZpY2llbnQuDQo+ID4gT24t
cGF0aCBkZXZpY2VzIHRoYXQgbWFuaXB1bGF0ZSBwYWNrZXRzIG1heSBub3QgYmUgYQ0KPiA+IMOi
4oKsxZNwcm90b2NvbC1zcGVjaWZpYyBwcm94ecOi4oKswp06IHR1bm5lbCBlbmRwb2ludCAoZS5n
LiwgTElTUCksIENHTg0KPiA+IChOQVQ2NCwgTkFUNDQsIERTLUxpdGUpLCBNQVAtRSBCUiwgZXRj
Lg0KPiA+DQo+ID4gSWYgdGhlIGFjdGlvbiBvZiB0aGUgcHJveHkgaXMgdG8gc3RhcnQgYSBuZXcg
VENQIGNvbm5lY3Rpb24gdG8gYW4NCj4gPiBvcmlnaW4gc2VydmVyLCBmb3IgZXhhbXBsZSwgdGhl
IG5vcm1hbCBvcGVyYXRpb24gb2YgVENQIGlzIHRvIHVzZSB0aGUNCj4gPiBpbml0aWF0b3IncyBJ
UCBhZGRyZXNzLiBbTWVkXSBUaGlzIGlzIHByb3RvY29sLXNwZWNpZmljLiBJIGNhbg0KPiA+IHBy
b3ZpZGUgYW4gZXhhbXBsZSBvZiBhIHByb3h5IGJlaGF2aW9yIHRoYXQgcmVsYXlzIHRoZSBzb3Vy
Y2UgSVANCj4gPiBhZGRyZXNzL3BvcnQgYXMgcGFydCBvZiBpdHMgbm9ybWFsIG9wZXJhdGlvbjoN
Cj4gPiBodHRwOi8vd3d3LmhhcHJveHkub3JnL2Rvd25sb2FkLzEuOC9kb2MvcHJveHktcHJvdG9j
b2wudHh0IC0gVENQL0lQdjQNCj4gPiA6ICJQUk9YWSBUQ1A0IDI1NS4yNTUuMjU1LjI1NSAyNTUu
MjU1LjI1NS4yNTUgNjU1MzUgNjU1MzVcclxuIiA9PiA1ICsNCj4gPiAxICsgNCArIDEgKyAxNSAr
IDEgKyAxNSArIDEgKyA1ICsgMSArIDUgKyAyID0gNTYgY2hhcnMNCj4gPg0KPiA+IC0gVENQL0lQ
djYgOiAiUFJPWFkgVENQNiBmZmZmOmYuLi5mOmZmZmYgZmZmZjpmLi4uZjpmZmZmIDY1NTM1DQo+
ID4gNjU1MzVcclxuIiA9PiA1ICsgMSArIDQgKyAxICsgMzkgKyAxICsgMzkgKyAxICsgNSArIDEg
KyA1ICsgMiA9IDEwNA0KPiA+IGNoYXJzDQo+ID4NCj4gPg0KPiA+IFRoZSBsb3NlcyB0aGUgSVAg
YWRkcmVzcyBvZiB0aGUgcXVlcnlpbmcgaG9zdCBpcyBpbXBsaWVkIGJ5IHRoYXQNCj4gPiBub3Jt
YWwgb3BlcmF0aW9uKGluIG90aGVyIHdvcmRzLCBpdCBlbGlkZXMgbWV0YWRhdGEgYWJvdXQgYW55
IGNsaWVudA0KPiA+IHRoYXQgY2F1c2VkIHRoaXMgbmV3IFRDUCBjb25uZWN0aW9uIHRvIGJlIGNy
ZWF0ZUQpLiBbTWVkXSBUaGlzIG1ha2VzDQo+ID4gc2Vuc2UgaWYgbG9zaW5nIHRoZSBvcmlnaW5h
bCBJUCBhZGRyZXNzIGlzIGFuIGludGVuZGVkIHByb3ByaWV0eSBvZg0KPiA+IHRoZSBwcm94eS4g
QnV0IHRoaXMgY2Fubm90IGJlIGEgZ2VuZXJhbGl6ZWQgcHJveHkgYmVoYXZpb3IgKHNlZSB0aGUN
Cj4gPiBleGFtcGxlIGFib3ZlKS4NCj4gPg0KPiA+IFNvIG9yaWdpbiBJUCBhZGRyZXNzIHN0YXJ0
cyBvdXQgaW4gdGhlIElQIGhlYWRlciBvZiB0aGUgb3JpZ2luYWwNCj4gPiBwYWNrZXQgYnV0IGdl
dHMgcHVzaGVkIGZyb20gdGhhdCBzbG90IHdoZW4gdGhlIHByb3h5IGNvbnN0cnVjdHMgdGhlDQo+
ID4gb253YXJkIElQIHBhY2tldCB0byB0aGUgc2VydmVyLiAgRm9yIGl0IHRvIHJlYWNoIHRoZSBz
ZXJ2ZXIsIGl0IGhhcw0KPiA+IHRvIGJlIHBsYWNlZCBzb21ld2hlcmUgZWxzZSBpbiB0aGUgb253
YXJkIHBhY2tldCwgcmVzdG9yaW5nIHRoZSBsb3N0DQo+ID4gbWV0YWRhdGEuIFtNZWRdIFRoZSBj
bGllbnQgYWdyZWVkIHRvIHNlbmQgcGFja2V0cyB3aXRoIGl0cyBzb3VyY2UgSVANCj4gPiBhZGRy
ZXNzICh3aGljaCBtZWFuIGNvbnNlbnQpLiBXaHkgdGhlIHByb3h5IHdvdWxkIG5lZWQgdG8gYW4g
ZXh0cmENCj4gPiBjaGFubmVsIHRvIGdldCBjb25zZW50IGZvciByZWxheWluZyB0aGUgc291cmNl
IElQIGFkZHJlc3MgdG8gYQ0KPiA+IHNlcnZlcj8NCj4gPg0KPiA+DQo+ID4gQmVjYXVzZSB0aGUg
Y2xpZW50IGFncmVlZCB0byBzZW5kIHBhY2tldHMgdG8gdGhlIHByb3h5IGJ5IHB1dHRpbmcgaXQN
Cj4gPiBpbiB0aGUgZGVzdGluYXRpb24gW01lZF0gVGhlIGNsaWVudCBpcyBub3QgZXZlbiBhd2Fy
ZSB0aGF0IHByb3h5DQo+ID4gZXhpc3RzIG9uIHRoZSBwYXRoISBQYWNrZXRzIGFyZSBzZW50IHRv
IHRoZSB1bHRpbWF0ZSBzZXJ2ZXLDouKCrOKEonMNCj4gPiBhZGRyZXNzLCBub3QgdGhlIG9uZSBv
ZiB0aGUgcHJveHkuIEV2ZW4gZm9yIFNPTUUgY2FzZXMgd2hlcmUgcGFja2V0cw0KPiA+IGFyZSBz
ZW50IGV4cGxpY2l0bHkgdG8gdGhlIHByb3h5IChlLmcuLCBTT0NLUyBwcm94eSksIGEgc3RhdGUg
aXMNCj4gPiBhbHJlYWR5IGluIHBsYWNlIHRvIGdyYWZ0IHRoZSBvdXRnb2luZyBwYWNrZXRzIHRv
IGEgYmluZGluZyBjb250ZXh0DQo+ID4gaW52b2x2aW5nIHRoZSBkZXN0aW5hdGlvbiBzZXJ2ZXIu
DQo+ID4NCj4gPiAsIGFuZCBkaWQgbm90IGFncmVlIHRvIGdlbmVyYWwgZGlzY2xvc3VyZTsgeW91
IGNhbid0IGluZmVyIG9ud2FyZA0KPiA+IGNvbnNlbnQuIFtNZWRdIEhtbcOi4oKswqZJw6Ligqzi
hKJtIGFmcmFpZCB0aGlzIGNvbmNsdXNpb24gaXMgbm90IHRlY2huaWNhbGx5DQo+ID4gYmFja2Vk
LCBlLmcuLCAqIEEgY2xpZW50IHRoYXQgc2VuZHMgcGFja2V0cyB0byBhIHNlcnZlciBsb2NhdGVk
IG9uDQo+ID4gdGhlIEludGVybmV0IGlzIE5PVCBuZWNlc3NhcmlseSBhd2FyZSB0aGF0IGEgcHJv
eHkgaXMgc29saWNpdGVkIGluDQo+ID4gZm9yd2FyZGluZyBwYXRoLiBQYWNrZXRzIGFyZSBzZW50
IHVzaW5nIHRoZSBzZXJ2ZXLDouKCrOKEonMgSVAgYWRkcmVzcy4gKg0KPiA+IFRoZSBjbGllbnQg
YW5kIHByb3h5IG1heSBiZSBvd25lZCBieSB0aGUgc2FtZSBhZG1pbmlzdHJhdGl2ZSBlbnRpdHkN
Cj4gPiAoY2FzZSBvZiBlbnRlcnByaXNlIG5ldHdvcmtzKS4gVGhhdCBlbnRpdHkgaXMgcmVzcG9u
c2libGUgZm9yIGVuc3VyZQ0KPiA+IHdoaWNoIGluZm9ybWF0aW9uIHRoZSBwcm94eSBuZWVkcyB0
byBsZWFrLiAqIFRoZSBwcm94eSBhbmQgdGhlIHNlcnZlcg0KPiA+IG1heSBiZSBvd25lZCBieSB0
aGUgc2FtZSBhZG1pbmlzdHJhdGl2ZSBlbnRpdHkgKGNvbnRlbnQgcHJvdmlkZXIpLg0KPiA+IFN1
cHBseWluZyBkYXRhIGJ5IGEgcHJveHkgdG8gdGhlIHNlcnZlciwgYmFzZWQgb24gdGhlIGNvbnRl
bnQgb2YgYQ0KPiA+IHBhY2tldCByZWNlaXZlZCBmcm9tIGEgaG9zdCwgZG9lcyBub3QgaW5kdWNl
IGEgcHJpdmFjeSBjb25jZXJuIGhlcmUNCj4gPiBiZWNhdXNlIHRoZSBwcm94eSBhbmQgdGhlIHNl
cnZlciBvd25lZCBieSB0aGUgc2FtZSBlbnRpdHkuDQo+ID4NCj4gPiBIYWQgaXQgYmVlbiBwcmVz
ZW50IGluIHRoZSBwYWNrZXQgYXMgaGVhZGVyIHZhbHVlIGluIHRoZSBIVFRQDQo+ID4gZXhjaGFu
Z2UsIGl0IHdvdWxkIG5vdCBoYXZlIGJlZW4gc3RyaXBwZWQgYnkgbm9ybWFsIG9wZXJhdGlvbi4g
IFRoZXJlDQo+ID4gcHJveHkgb3BlcmF0aW9uIGZvcndhcmRpbmcgaXQgb24gd291bGQgYmUgc2lt
cGx5IHByZXNlcnZpbmcgaXQuIFtNZWRdDQo+ID4gVGhpcyBpcyBhbm90aGVyIHF1ZXN0aW9uOiB3
aGV0aGVyIHRoZSBzYW1lIG9yIGRpc3RpbmN0IGNoYW5uZWwgY2FuIGJlDQo+ID4gdXNlZCB0byBj
b21tdW5pY2F0ZSB0aGUgU0FNRSBkYXRhIHRoYXQgd2FzIHByZXNlbnQgaW4gdGhlIGluaXRpYWwN
Cj4gPiBwYWNrZXQgaXNzdWVkIGJ5IGEgaG9zdC4NCj4gPg0KPiA+DQo+ID4gVGhhdCBkZXBlbmRz
IG9uIHRoZSBuYXR1cmUgb2YgdGhlIGNoYW5uZWwuICBPYnZpb3VzbHksIGlmIHlvdSBzZXQgdGhl
DQo+ID4gb3JpZ2luIGNsaWVudHMgSVAgYWRkcmVzcyBhcyB0aGUgc291cmNlIGFkZHJlc3MsIHlv
dSdyZSBnb2luZyB0byBnZXQNCj4gPiBhIGRpZmZlcmVudCByZXN1bHQgZnJvbSB0aGF0IHNwb29m
aW5nIHRoYW4gcHV0dGluZyBpdCBpbiBhIGNsaWVudA0KPiA+IHN1Ym5ldCBFRE5TIG9wdGlvbiBv
ciBmb3J3YXJkZWQtZm9yIGhlYWRlci4gW01lZF0gQWdyZWUuDQo+ID4NCj4gPg0KPiA+IMOi4oKs
wqIgICAgICAgICBBbiBhZGRyZXNzIHNoYXJpbmcgZGV2aWNlLCB1bmRlciBmb3IgZXhhbXBsZSBE
Uy1MaXRlDQo+ID4gKFJGQzYzMzMpLCB0aGF0IGluc2VydHMgdGhlIHNvdXJjZSBJUHY2IHByZWZp
eCBpbiB0aGUgVENQIEhPU1RfSUQNCj4gPiBvcHRpb24gKFJGQzc5NzQpIGlzIG5vdCBSRVNUT1JJ
TkcgYW55IGRhdGEuIFRoZSBjb250ZW50IG9mIHRoYXQgVENQDQo+ID4gb3B0aW9uIGlzIGFscmVh
ZHkgdmlzaWJsZSBpbiB0aGUgcGFja2V0IHNlbnQgYnkgdGhlIGhvc3QuIEkgYWdyZWUNCj4gPiB3
aXRoIHRoZSBJRVNHIGFuYWx5c2lzIG9mIFJGQzc5NzQuICBJdCBkb2VzIHJlc3RvcmUgaW5mb3Jt
YXRpb24gYnkNCj4gPiB0YWtpbmcgaW5mb3JtYXRpb24gd2hpY2ggbm9ybWFsIG9wZXJhdGlvbiB3
b3VsZCBoYXZlIGVsaWRlZCBhbmQNCj4gPiByZXN0b3JlcyBpdC4gW01lZF0gVGhlICBpbXBsaWNh
dGlvbiBvZiB3aGF0IHlvdSBhcmUgc2F5aW5nIGhlcmUgaXMNCj4gPiB0aGF0IHByb3hpZXMgYXJl
IGdvb2QgYmVjYXVzZSB0aGV5IGhpZGUgdGhlIHNvdXJjZSBJUCBhZGRyZXNzZXMgb2YNCj4gPiBo
b3N0IQ0KPiA+DQo+ID4NCj4gPiBBZ2dyZWdhdGluZyBwcm94aWVzIGNhbiBoYXZlIGEgcG9zaXRp
dmUgcHJpdmFjeSBpbXBhY3QsIHllcy4gIEFuDQo+ID4gb2JzZXJ2ZXIgc2VlaW5nIHRyYWZmaWMg
ZnJvbSBhbiBhZ2dyZWdhdGluZyBwcm94eSB0bw0KPiA+IHNlbnNpdGl2ZS10b3BpYy5leGFtcGxl
LmNvbTxodHRwOi8vc2Vuc2l0aXZlLXRvcGljLmV4YW1wbGUuY29tPiBrbm93cw0KPiA+IG9ubHkg
dGhhdCBzb21lIHVzZXIgYmVoaW5kIHRoYXQgcHJveHkgaXMgbG9va2luZyBmb3IgaW5mb3JtYXRp
b24gb24NCj4gPiBzZW5zaXRpdmUtdG9waWMuICBUbyBrbm93IHdoaWNoIHVzZXIsIHRoZSBvYnNl
cnZlciBtdXN0IGhhdmUgZWl0aGVyDQo+ID4gc3Vib3JuZWQgdGhlIHByb3h5IG9yIGhhdmUgYSB3
YXkgb2Ygb2JzZXJ2aW5nIHRyYWZmaWMgYmV0d2VlbiBob3N0cw0KPiA+IGFuZCB0aGUgcHJveHku
ICBCb3RoIGFyZSBtb3JlIGV4cGVuc2l2ZSBhbmQgYXQgaGlnaGVyIHJpc2sgb2YNCj4gPiBkaXNj
b3ZlcnkgdGhhbiBhIHNpbXBsZSB0YXAgbmVhcg0KPiA+IHNlbnNpdGl2ZS10b3BpYy5leGFtcGxl
LmNvbTxodHRwOi8vc2Vuc2l0aXZlLXRvcGljLmV4YW1wbGUuY29tPi4NCj4gPg0KPiA+IFtNZWRd
IFRoZSBtYWluIHBvaW50IGhlcmUgaXMgdGhhdCwgZXZlbiBpbiB0aGUgcHJlc2VuY2Ugb2YgYW4N
Cj4gPiBhZ2dyZWdhdGluZyBwcm94eSwgYSBzZXJ2ZXIgY2FuIGRlbXV4IHVzZXJzIGJ5IGNvcnJl
bGF0aW5nIHZhcmlvdXMNCj4gPiBpbmZvcm1hdGlvbiBsZWFrZWQgYXQgdGhlIGFwcGxpY2F0aW9u
IGxheWVyIChlLmcuLA0KPiA+IGh0dHBzOi8vcGFub3B0aWNsaWNrLmVmZi5vcmcvKS4gVHJhY2tp
bmcgdGhvc2UgdXNlcnMgd2hlbiB0aGV5IGNoYW5nZQ0KPiA+IHRoZWlyIHNvdXJjZSBJUCBhZGRy
ZXNzIGlzIHBvc3NpYmxlIGluIHRoaXMgY2FzZSwgdG9vLg0KPiA+DQo+ID4NCj4gPiBJZiB0aGUg
ZGF0YSBpcyB0YWtlbiBmcm9tIGEgcG9ydGlvbiBvZiB0aGUgcGFja2V0IHRoYXQgd291bGQgbm90
DQo+ID4gbm9ybWFsbHkgYmUgZm9yd2FyZGVkIHRvIGFuIHVwc3RyZWFtIGhvc3QgYW5kIGFkZGVk
IHRvIGEgcG9ydGlvbiB0aGF0DQo+ID4gaXMgZm9yd2FyZGVkIHRvIGFuIHVwc3RyZWFtIGhvc3Qs
IHRoZW4gdGhlIGRldmljZSBhZGRpbmcgdGhlIGRhdGENCj4gPiBiYWNrIGluIHNob3VsZCBrbm93
IGl0IGlzIGEgcmVzdG9yYXRpb24uIFtNZWRdIFRoYXQgZGVmaW5pdGlvbiBpcyBub3QNCj4gPiB0
cml2aWFsIGFzIG1lbnRpb25lZCBhYm92ZS4gSSB3b3VsZCB1c2Ugw6LigqzFk3ByZXNlcnZlw6Li
gqzCnSBvcg0KPiA+IMOi4oKsxZNtYWludGFpbsOi4oKswp0gcmF0aGVyIHRoYW4gw6LigqzFk3Jl
c3RvcmXDouKCrMKdLiBQbGVhc2Ugc2VlIGFib3ZlLg0KPiA+ICJSZXN0b3JlIiBpcyBjbG9zZXIs
IGluIG15IG9waW5pb24sIHRoYW4gZWl0aGVyIHByZXNlcnZlIG9yDQo+ID4gbWFpbnRhaW4uDQo+
ID4NCj4gPg0KPiA+DQo+ID4gSWYgdGhlIGVuZHBvaW50IHNlbmRzIHRoZSBkYXRhLCBkYXRhIHdp
bGwgYmUgY29uc2lzdGVudGx5IGF2YWlsYWJsZQ0KPiA+IGluIHRoYXQgaGVhZGVyLiAgVGhlIGRh
dGEgY2hhbmdlcywgb2YgY291cnNlLiBbTWVkXSBJw6LigqzihKJtIG5vdCBzdXJlIHRvDQo+ID4g
Zm9sbG93IHlvdSBoZXJlLiBXaGF0IGlzIG1lYW50IGJ5IMOi4oKsxZNjb25zaXN0ZW50IGF2YWls
YWJpbGl0ecOi4oKswp0gdGhlbj8NCj4gPiBEbyB5b3UgbWVhbiB0aGUgc2FtZSBjaGFubmVsL3By
b2NlZHVyZSB0byBjb21tdW5pY2F0ZSB0aGUNCj4gPiBpbmZvcm1hdGlvbj8gT3Igw6LigqzFk2Nv
bnNpc3RlbnQgZGF0YcOi4oKswp0/DQo+ID4NCj4gPiBJIG1lYW4gdGhhdCBpZiB5b3UgZGVmaW5l
IGEgcHJvdG9jb2wgc3VjaCB0aGF0IGEgd2VsbC1mb3JtZWQgbWVzc2FnZQ0KPiA+IGZyb20gdGhl
IGNsaWVudCBoYXMgdGhlIGRhdGEgdGhlIHNlcnZlciBuZWVkcywgaXQgd2lsbCBiZQ0KPiA+IGNv
bnNpc3RlbnRseSBhdmFpbGFibGUuICBJZiB5b3UgcmVseSBvbiBpbnRlcm1lZGlhdGUgbmV0d29y
ayBkZXZpY2VzDQo+ID4gdG8gYWRkIHRoZSBkYXRhLCBpdCBtYXkgbm90IGJlIGF2YWlsYWJsZSBp
ZiB0aGVyZSBpcyBub3QgY29vcGVyYXRpbmcNCj4gPiBuZXR3b3JrIGRldmljZSBvbiBwYXRoIChl
LmcuIGlmIHRoZSBETlMgcmVzb2x2ZXIgZG9lcyBub3Qgc3VwcG9ydCB0aGUNCj4gPiByZWxldmFu
dCBFRE5TMCBvcHRpb24pLg0KPiA+DQo+ID4gW01lZF0gVGhhbmsgeW91LiBQbGVhc2UgY2xhcmlm
eSB0aGlzIGluIHRoZSBkcmFmdC4gSSBoYWQgdHJvdWJsZXMgdG8NCj4gPiBwYXJzZSB3aGF0IHlv
dSBtZWFudCBieSDDouKCrMWTY29uc2lzdGVudCBhdmFpbGFiaWxpdHnDouKCrMKdLiBUaGF0w6Li
gqzihKJzIHNhaWQsDQo+ID4gdGhlcmUgbWlnaHQgYmUgYWxzbyDDouKCrMWTbm90IGNvb3BlcmF0
aW5nIG9uLXBhdGggZGV2aWNlc8Oi4oKswp0gdGhhdCBtYXkNCj4gPiBzdHJpcC9hbHRlciB0aGUg
Y29udGVudCBvZiBjbGllbnQgc3VwcGxpZWQgZGF0YSAoZWFzeSBmb3IgSFRUUCBmb3INCj4gPiBl
eGFtcGxlKS4NCj4gPg0KPiA+DQo+ID4NCj4gPiBbTWVkXSBSZXNvdXJjZXMgbWF5IG5vdCBiZSBy
ZXN0cmljdGVkIHRvIENQVSBvciBkaXNrIGJ1dCBtYXkgYmUNCj4gPiBncmFudGluZyBhY2Nlc3Mg
dG8gdGhlIHNlcnZpY2UgKGUuZy4sIGRvd25sb2FkIGEgZmlsZSB3aGVuIGEgcXVvdGENCj4gPiBw
ZXIgc291cmNlIGFkZHJlc3MgaXMgZW5mb3JjZWQpLiBJdCBjYW4gYmUgd2hhdGV2ZXIgdGhlIHNl
cnZlcnMNCj4gPiBjb25zaWRlciB0byBiZSBjcml0aWNhbCBmb3IgdGhlbTsgaXQgaXMgdXAgdG8g
dGhlIHRhc3RlIG9mIHRoZQ0KPiA+IHNlcnZpY2UgZGVzaWduIHRvIGNoYXJhY3Rlcml6ZSBpdC4g
VGhlIE5FVyB3b3JkaW5nIHByb3Bvc2VkIGFib3ZlIGlzDQo+ID4gdGVjaG5pY2FsbHkgY29ycmVj
dC4gUGxlYXNlIHJlY29uc2lkZXIgYWRkaW5nIGl0IHRvIHRoZSBkcmFmdC4NCj4gPg0KPiA+DQo+
ID4NCj4gPiBJIGRpZCBjb25zaWRlciBpdCwgYnV0IEkgY29udGludWUgdG8gYmVsaWV2ZSB0aGF0
IGl0IG1vdmVzIHRoZSBuZWVkbGUNCj4gPiB0b28gZmFyIGludG8gc2ltcGxlIHNlcnZlciBwcmVm
ZXJlbmNlLiAgSSByZXRhaW5lZCB0aGUgb3JpZ2luYWwgUFNBUA0KPiA+IGxhbmd1YWdlIGluIC0w
NyBhcyBhIHJlc3VsdC4gW01lZF0gZW1lcmdlbmN5IGlzIG9ubHkgYW4gZXhhbXBsZSA7DQo+ID4g
b3RoZXIgc2VydmljZXMgbWF5IGV4aXN0IHRoYXQgaW1wb3NlIHRoZSBzYW1lIHRydXN0IG1vZGVs
Lg0KPiA+DQo+ID4NCj4gPiBJIHRoaW5rIHRoZXJlIGlzIGEgcXVhbGl0YXRpdmUgZGlmZmVyZW5j
ZSBiZXR3ZWVuIHNpdHVhdGlvbnMgaW4gd2hpY2gNCj4gPiB0aGUgcmVzb3VyY2VzIGF0IHJpc2sg
YXJlIGh1bWFuIGxpdmVzIGFuZCB0aG9zZSB3aGVyZSB0aGV5IGFyZSBob3N0DQo+ID4gcmVzb3Vy
Y2VzLiBbTWVkXSBJIGFncmVlIHdpdGggeW91IGFzIGFuIGluZGl2aWR1YWwuIEJ1dCwgaXQgaXMg
bm90IHVwDQo+ID4gdG8gdXMgdG8gbWFuZGF0ZSB0aGlzIGNvbmRpdGlvbiBmb3IgZXhlY3V0aW5n
IHNlcnZpY2VzLiBJdCBpcyB1cCB0bw0KPiA+IHRoZSAocHJvdG9jb2wpIGRlc2lnbmVycy9zZXJ2
aWNlIHByb3ZpZGVycyB0byBkZWNpZGUgd2hhdCBpcw0KPiA+IGNyaXRpY2FsL2tleSBmb3IgdGhl
aXIgc2VydmljZSBvcGVyYXRpb24uIFRoYXQncyB3aHkgdGhlIGNhcnZlIG91dA0KPiA+IHdhcyBs
aW1pdGVkIGluIHRoZSBHRU9QUklWIGNhc2UuIFtNZWRdIEdFT1BSSVYgaXMgbm90IHRoZSBvbmx5
DQo+ID4gcHJvdG9jb2wvc2VydmljZSB0aGF0IGlzIGNvbmNlcm5lZCB3aXRoIGh1bWFuIGxpdmVz
LCB3ZSBjYW4gY29uc2lkZXINCj4gPiB2ZWhpY3VsYXIgbmV0d29ya2luZyB0aGF0IHRydXN0IHRo
ZSBpbmZvcm1hdGlvbiBzaGFyZWQgYnkgdGhlDQo+ID4gaW5mcmFzdHJ1Y3R1cmUuIEkgcHJlZmVy
IG5ldXRyYWwgd29yZGluZyB0aGF0IGNpdGVzIGVtZXJnZW5jeSBhcyBhbg0KPiA+IGV4YW1wbGUu
DQo+ID4NCj4gPg0KPiA+IEkgYWxzbyBhZGRlZCBhIG5vdGUgYWJvdXQgeW91ciBleHRlbnNpdmUg
cmV2aWV3LiAgV2hpbGUgeW91IGFuZCBJDQo+ID4gY2xlYXJseSBoYXZlIHNvbWUgZGlmZmVyZW5j
ZXMgb2YgdmlldywgdGhlIGRvY3VtZW50IGhhcyBnb3R0ZW4gYmV0dGVyDQo+ID4gZnJvbSB5b3Vy
IGVuZ2FnZW1lbnQgd2l0aCBpdCwgYW5kIEkgYXBwcmVjaWF0ZSB5b3VyIGVmZm9ydHMuIFtNZWRd
IEkNCj4gPiByZXZpZXdlZCB0aGUgLTA3LiBBbHRob3VnaCBpdCBpcyBiZXR0ZXIgY29tcGFyZWQg
dG8gLTA1LCBJIHN0aWxsDQo+ID4gZG9uw6LigqzihKJ0IHRoaW5rIGl0IGlzIHJlYWR5IHRvIGJl
IHB1Ymxpc2hlZCBhcyBpdCBpcy4gVGhhbmsgeW91IGZvcg0KPiA+IHlvdXIgZWZmb3J0LiBBbmQg
dGhhbmsgeW91IGZvciB5b3VycywgcmVnYXJkcywgVGVkDQo+ID4NCj4gPiByZWdhcmRzLCBUZWQN
Cj4gPg0KDQo=


From nobody Tue Mar  7 05:08:03 2017
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 AE4C91293E3; Tue,  7 Mar 2017 05:08:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iqa5APlsfe3L; Tue,  7 Mar 2017 05:07:59 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADE3912941E; Tue,  7 Mar 2017 05:07:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7C69FBEF4; Tue,  7 Mar 2017 13:07:56 +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 4NN01h9ZKm92; Tue,  7 Mar 2017 13:07:53 +0000 (GMT)
Received: from [172.28.172.2] (unknown [109.125.19.162]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 95499BEEE; Tue,  7 Mar 2017 13:07:52 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1488892073; bh=4rxYx6+Vyal2zhEjWpQmB2dlfMMryLZQ0rzKqibMNKs=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=GtmP8Xy6cT5dWBZhBjeCe3QQ0bwzcLhXWay1/wryXs3ruyONEJWw2iUzjVItrk377 VY3NFvpLWY1YlJ+1wqGIoOlqQpOBpa3gQ0WBuL1ehcuhNw4vmJQjGpQCLP0WSVcPLb KDJHu4DYSCe7MqxjImqBj1B+Sk13tJCR2I1T2HZQ=
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
To: mohamed.boucadair@orange.com, Ted Hardie <ted.ietf@gmail.com>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com> <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup> <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com> <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup> <cebf0487-2d71-ea1e-5dd9-cf1d8c80df3a@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E1D615@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <d9827c93-9848-6d54-a9e8-c759d2d2a1de@cs.tcd.ie>
Date: Tue, 7 Mar 2017 13:07:50 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E1D615@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ip8pcBLj64CQa79me9xkil3T1Ux0aqsUg"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aiNB245X3Cyf95KvvJSlEBf-t1w>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 13:08:02 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ip8pcBLj64CQa79me9xkil3T1Ux0aqsUg
Content-Type: multipart/mixed; boundary="d8lRhVtic94ior9riDI6NxSeSegXG41dW";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: mohamed.boucadair@orange.com, Ted Hardie <ted.ietf@gmail.com>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org"
 <draft-hardie-privsec-metadata-insertion@ietf.org>,
 "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <d9827c93-9848-6d54-a9e8-c759d2d2a1de@cs.tcd.ie>
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt>
 (Design considerations for Metadata Insertion) to Informational RFC
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com>
 <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com>
 <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup>
 <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com>
 <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup>
 <cebf0487-2d71-ea1e-5dd9-cf1d8c80df3a@cs.tcd.ie>
 <787AE7BB302AE849A7480A190F8B933009E1D615@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E1D615@OPEXCLILMA3.corporate.adroot.infra.ftgroup>

--d8lRhVtic94ior9riDI6NxSeSegXG41dW
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 07/03/17 13:03, mohamed.boucadair@orange.com wrote:
> Hi Stephen,
>=20
> First of all, I really thank Ted for engaging and for making some
> changes to the document. That's much appreciated. Nevertheless, I
> still think the document isn't ready to be published as it is with an
> IETF consensus.

That's clear yes.

>=20
> The point you mentioned about "restore" is one of the disagreements,
> but not the only one. I hope the discussion will continue with Ted to
> fix this in the document.

I mentioned two points of disagreement. I didn't see others
that aren't related to those. (I did see more text, but it
seemed to be the same discussion.)

>=20
> I checked the SAAG archives, but, unless I'm mistaken, I failed to
> find a technical discussion about the content of the draft or a
> thread about "fairly clear support" to "progressing this draft".

It was entwined a bit with the 3552bis discussion. Don't have time
at the 'mo to dig out references but happy to do that later.

>=20
> I don't think there is a rush to publish the document. Do we?

Rush? No. But it is IMO timely and I would like to see it done
before I finish as an AD. Call that a rush if you like but I
think we're our usual sedate selves mostly with this one:-)

Cheers,
S.

>=20
> Cheers, Med
>=20
>> -----Message d'origine----- De=C3=82 : Stephen Farrell
>> [mailto:stephen.farrell@cs.tcd.ie] Envoy=C3=83=C2=A9=C3=82 : mardi 7 m=
ars 2017
>> 13:08 =C3=83=E2=82=AC=C3=82 : BOUCADAIR Mohamed IMT/OLN; Ted Hardie Cc=
=C3=82 :
>> draft-hardie-privsec-metadata-insertion@ietf.org; ietf@ietf.org=20
>> Objet=C3=82 : Re: Last Call:
>> <draft-hardie-privsec-metadata-insertion-05.txt> (Design
>> considerations for Metadata Insertion) to Informational RFC
>>=20
>>=20
>> Hi Med and Ted,
>>=20
>> Thanks for the discussion. My conclusion from that is that the best
>> next step will be to continue with IESG evaluation. Progressing
>> this draft had fairly clear support in earlier discussions on the
>> saag list and in saag meetings, so it may be Med that you're just
>> in the rough - given the limited comment during LC, I'd say getting
>> the IESG to evaluate this will be the easiest way to figure that
>> out. And as an outgoing AD, I'd much prefer to try get this sorted
>> before I'm done rather than leaving it to Kathleen or Eric to pick=20
>> up later. (Though we can go there if needed.) Anyway, I think
>> logistically it makes sense to keep this on the March 16th IESG
>> telechat and see where we go from there. I'll include a pointer to
>> the archive for this mail so other ADs can easily find this
>> discussion.
>>=20
>> As to the content of the discussion, I think Ted has answered your
>> comments, even though you and he haven't reached full agreement on
>> all topics. For me it seems like the remaining areas of discussion
>> were:-
>>=20
>> - language around "restore" or not (fwiw I agree with Ted's take on
>> that term)
>>=20
>> - "consent" - actually it may be best to just remove the two uses
>> of that term entirely - the term is fairly legally "loaded" and I'm
>> not sure it's needed for this design advice anyway - if we can
>> figure a way to rephrase those bits that may be an improvement
>> worth making
>>=20
>> I'll start the iesg evaluation process for -07 shortly.
>>=20
>> Cheers, S.
>>=20
>> PS: Sorry if I've missed anything else that is outstanding. The
>> form of (not really;-) quoting earlier messages used makes it very
>> hard to follow the conversation over more than two emails.
>>=20
>> On 07/03/17 07:31, mohamed.boucadair@orange.com wrote:
>>> Hi Ted,
>>>=20
>>> Thank you for the answers.
>>>=20
>>> Please see inline.
>>>=20
>>> Cheers, Med
>>>=20
>>> De : Ted Hardie [mailto:ted.ietf@gmail.com] Envoy=C3=83=C6=92=C3=82=C2=
=A9 : lundi 6
>>> mars 2017 18:14 =C3=83=C6=92=C3=A2=E2=80=9A=C2=AC : BOUCADAIR Mohamed=
 IMT/OLN Cc :
>>> ietf@ietf.org; draft-hardie-privsec-metadata-insertion@ietf.org
>>> Objet : Re: Last Call:
>>> <draft-hardie-privsec-metadata-insertion-05.txt> (Design=20
>>> considerations for Metadata Insertion) to Informational RFC
>>>=20
>>> Hi Mohamed, Replies in-line.
>>>=20
>>>=20
>>> On Mon, Mar 6, 2017 at 1:48 AM,=20
>>> <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
>>>
>>>=20
wrote:
>>>=20
>>>=20
>>> =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=A2         A Forward-For h=
eader inserted by a proxy does not
>>> restore any data; it does only reveal data that is already
>>> present in the packet issued by the client itself. That's what
>>> restore means here. [Med] Then, this needs to be defined in the
>>> document. I naively assumed that =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=
=85=E2=80=9Crestored=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D is used=

>>> to mean any piece of information that the client does not want to
>>> insert in a packet, but an on-path device decides to inject it
>>> despite there is no consent from the client. What you are
>>> describing is more about =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=
=9Cmaintaining=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D or=20
>>> =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Cpreserving=C3=83=C2=A2=
=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D information not restoring it.
>>>=20
>>> The common uses of restore in English all focus on putting
>>> something back that has been lost, [Med] But that information is
>>> not lost for an on-path device that encapsulates a packet in
>>> another one (so the inner header is still carrying the source IP
>>> address) or the one that supplies the original source IP address
>>> as a metadata when source IP address/port rewriting is required.
>>> The notion of =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Cputting=
 back=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D does not make sense to=

>>> me because we are not dealing with the internal processing of a
>>> packet within an on-path device, but we only focus on the
>>> external behavior. This is exactly the role of =C3=83=C2=A2=C3=A2=E2=80=
=9A=C2=AC=C3=85=E2=80=9Cvia=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D =

>>> headers for SIP proxies; when there is a mismatch the received
>>> tag is completed with the visible source address.
>>>=20
>>> so I believe restore is better than "maintain" or "preserve",
>>> which imply something is being carried forward as-is, rather than
>>> being put back after loss. [Med] Please see above. Because we
>>> don=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=A2=E2=80=9E=C2=A2t have a sta=
ndard behavior of an on-path device
>>> (proxy, tunnel-endpoint.), I seems weird to me to say that a
>>> proxy that preserves the source IP address is =C3=83=C2=A2=C3=A2=E2=80=
=9A=C2=AC=C3=85=E2=80=9Cputting pack
>>> an information that is lost=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=
=9D.
>>>=20
>>>=20
>>> If the information is present as metadata in the packet sent to
>>> the proxy but would be absent as metadata under normal operation
>>> of the proxy, adding it back in somewhere else restores the
>>> metadata. [Med] =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Cnorma=
l operation of proxy=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D is not =
a
>>> standard. A =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Cnormal op=
eration of proxy=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D would be to=

>>> maintain the information sent by the client when relaying it to
>>> the server. I=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=A2=E2=80=9E=C2=A2m =
sure you know for instance that SIP B2BUAs
>>> can do whatever they want!
>>>=20
>>> You're right that the normal operation of a proxy is not a
>>> standard, and I should have said "the normal operation of the
>>> protocols used by a proxy". [Med] This is much better, but still
>>> not sufficient. On-path devices that manipulate packets may not
>>> be a =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Cprotocol-specifi=
c proxy=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D: tunnel endpoint
>>> (e.g., LISP), CGN (NAT64, NAT44, DS-Lite), MAP-E BR, etc.
>>>=20
>>> If the action of the proxy is to start a new TCP connection to
>>> an origin server, for example, the normal operation of TCP is to
>>> use the initiator's IP address. [Med] This is protocol-specific.
>>> I can provide an example of a proxy behavior that relays the
>>> source IP address/port as part of its normal operation:=20
>>> http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt -
>>> TCP/IPv4 : "PROXY TCP4 255.255.255.255 255.255.255.255 65535
>>> 65535\r\n" =3D> 5 + 1 + 4 + 1 + 15 + 1 + 15 + 1 + 5 + 1 + 5 + 2 =3D
>>> 56 chars
>>>=20
>>> - TCP/IPv6 : "PROXY TCP6 ffff:f...f:ffff ffff:f...f:ffff 65535=20
>>> 65535\r\n" =3D> 5 + 1 + 4 + 1 + 39 + 1 + 39 + 1 + 5 + 1 + 5 + 2 =3D
>>> 104 chars
>>>=20
>>>=20
>>> The loses the IP address of the querying host is implied by that=20
>>> normal operation(in other words, it elides metadata about any
>>> client that caused this new TCP connection to be createD). [Med]
>>> This makes sense if losing the original IP address is an intended
>>> propriety of the proxy. But this cannot be a generalized proxy
>>> behavior (see the example above).
>>>=20
>>> So origin IP address starts out in the IP header of the original=20
>>> packet but gets pushed from that slot when the proxy constructs
>>> the onward IP packet to the server.  For it to reach the server,
>>> it has to be placed somewhere else in the onward packet,
>>> restoring the lost metadata. [Med] The client agreed to send
>>> packets with its source IP address (which mean consent). Why the
>>> proxy would need to an extra channel to get consent for relaying
>>> the source IP address to a server?
>>>=20
>>>=20
>>> Because the client agreed to send packets to the proxy by putting
>>> it in the destination [Med] The client is not even aware that
>>> proxy exists on the path! Packets are sent to the ultimate
>>> server=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=A2=E2=80=9E=C2=A2s address=
, not the one of the proxy. Even for SOME
>>> cases where packets are sent explicitly to the proxy (e.g., SOCKS
>>> proxy), a state is already in place to graft the outgoing packets
>>> to a binding context involving the destination server.
>>>=20
>>> , and did not agree to general disclosure; you can't infer
>>> onward consent. [Med] Hmm=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=A6=
I=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=A2=E2=80=9E=C2=A2m afraid this conc=
lusion
>>> is not technically backed, e.g., * A client that sends packets to
>>> a server located on the Internet is NOT necessarily aware that a
>>> proxy is solicited in forwarding path. Packets are sent using the
>>> server=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=A2=E2=80=9E=C2=A2s IP addr=
ess. * The client and proxy may be owned
>>> by the same administrative entity (case of enterprise networks).
>>> That entity is responsible for ensure which information the proxy
>>> needs to leak. * The proxy and the server may be owned by the
>>> same administrative entity (content provider). Supplying data by
>>> a proxy to the server, based on the content of a packet received
>>> from a host, does not induce a privacy concern here because the
>>> proxy and the server owned by the same entity.
>>>=20
>>> Had it been present in the packet as header value in the HTTP=20
>>> exchange, it would not have been stripped by normal operation.
>>> There proxy operation forwarding it on would be simply preserving
>>> it. [Med] This is another question: whether the same or distinct
>>> channel can be used to communicate the SAME data that was present
>>> in the initial packet issued by a host.
>>>=20
>>>=20
>>> That depends on the nature of the channel.  Obviously, if you set
>>> the origin clients IP address as the source address, you're going
>>> to get a different result from that spoofing than putting it in a
>>> client subnet EDNS option or forwarded-for header. [Med] Agree.
>>>=20
>>>=20
>>> =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=A2         An address shar=
ing device, under for example
>>> DS-Lite (RFC6333), that inserts the source IPv6 prefix in the TCP
>>> HOST_ID option (RFC7974) is not RESTORING any data. The content
>>> of that TCP option is already visible in the packet sent by the
>>> host. I agree with the IESG analysis of RFC7974.  It does restore
>>> information by taking information which normal operation would
>>> have elided and restores it. [Med] The  implication of what you
>>> are saying here is that proxies are good because they hide the
>>> source IP addresses of host!
>>>=20
>>>=20
>>> Aggregating proxies can have a positive privacy impact, yes.  An=20
>>> observer seeing traffic from an aggregating proxy to=20
>>> sensitive-topic.example.com<http://sensitive-topic.example.com>
>>> knows only that some user behind that proxy is looking for
>>> information on sensitive-topic.  To know which user, the observer
>>> must have either suborned the proxy or have a way of observing
>>> traffic between hosts and the proxy.  Both are more expensive and
>>> at higher risk of discovery than a simple tap near=20
>>> sensitive-topic.example.com<http://sensitive-topic.example.com>.
>>>=20
>>> [Med] The main point here is that, even in the presence of an=20
>>> aggregating proxy, a server can demux users by correlating
>>> various information leaked at the application layer (e.g.,=20
>>> https://panopticlick.eff.org/). Tracking those users when they
>>> change their source IP address is possible in this case, too.
>>>=20
>>>=20
>>> If the data is taken from a portion of the packet that would not=20
>>> normally be forwarded to an upstream host and added to a portion
>>> that is forwarded to an upstream host, then the device adding the
>>> data back in should know it is a restoration. [Med] That
>>> definition is not trivial as mentioned above. I would use
>>> =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Cpreserve=C3=83=C2=A2=C3=
=A2=E2=80=9A=C2=AC=C3=82=C2=9D or =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=
=E2=80=9Cmaintain=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D rather tha=
n
>>> =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Crestore=C3=83=C2=A2=C3=
=A2=E2=80=9A=C2=AC=C3=82=C2=9D. Please see above. "Restore" is closer, in=

>>> my opinion, than either preserve or maintain.
>>>=20
>>>=20
>>>=20
>>> If the endpoint sends the data, data will be consistently
>>> available in that header.  The data changes, of course. [Med]
>>> I=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=A2=E2=80=9E=C2=A2m not sure to =
follow you here. What is meant by
>>> =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Cconsistent availabili=
ty=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D then? Do you mean the sam=
e
>>> channel/procedure to communicate the information? Or
>>> =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Cconsistent data=C3=83=
=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D?
>>>=20
>>> I mean that if you define a protocol such that a well-formed
>>> message from the client has the data the server needs, it will
>>> be consistently available.  If you rely on intermediate network
>>> devices to add the data, it may not be available if there is not
>>> cooperating network device on path (e.g. if the DNS resolver does
>>> not support the relevant EDNS0 option).
>>>=20
>>> [Med] Thank you. Please clarify this in the draft. I had troubles
>>> to parse what you meant by =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=
=80=9Cconsistent availability=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D=
=2E
>>> That=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=A2=E2=80=9E=C2=A2s said, the=
re might be also =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=E2=80=9Cnot coop=
erating
>>> on-path devices=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=82=C2=9D that may=
 strip/alter the content of client
>>> supplied data (easy for HTTP for example).
>>>=20
>>>=20
>>>=20
>>> [Med] Resources may not be restricted to CPU or disk but may be=20
>>> granting access to the service (e.g., download a file when a
>>> quota per source address is enforced). It can be whatever the
>>> servers consider to be critical for them; it is up to the taste
>>> of the service design to characterize it. The NEW wording
>>> proposed above is technically correct. Please reconsider adding
>>> it to the draft.
>>>=20
>>>=20
>>>=20
>>> I did consider it, but I continue to believe that it moves the
>>> needle too far into simple server preference.  I retained the
>>> original PSAP language in -07 as a result. [Med] emergency is
>>> only an example ; other services may exist that impose the same
>>> trust model.
>>>=20
>>>=20
>>> I think there is a qualitative difference between situations in
>>> which the resources at risk are human lives and those where they
>>> are host resources. [Med] I agree with you as an individual. But,
>>> it is not up to us to mandate this condition for executing
>>> services. It is up to the (protocol) designers/service providers
>>> to decide what is critical/key for their service operation.
>>> That's why the carve out was limited in the GEOPRIV case. [Med]
>>> GEOPRIV is not the only protocol/service that is concerned with
>>> human lives, we can consider vehicular networking that trust the
>>> information shared by the infrastructure. I prefer neutral
>>> wording that cites emergency as an example.
>>>=20
>>>=20
>>> I also added a note about your extensive review.  While you and
>>> I clearly have some differences of view, the document has gotten
>>> better from your engagement with it, and I appreciate your
>>> efforts. [Med] I reviewed the -07. Although it is better compared
>>> to -05, I still don=C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=A2=E2=80=9E=C2=
=A2t think it is ready to be published as
>>> it is. Thank you for your effort. And thank you for yours,
>>> regards, Ted
>>>=20
>>> regards, Ted
>>>=20
>=20


--d8lRhVtic94ior9riDI6NxSeSegXG41dW--

--ip8pcBLj64CQa79me9xkil3T1Ux0aqsUg
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYvrCnAAoJEC88hzaAX42iGZkIAJRNg0sk9QUw9ZwpwxcjnZFD
5nWqi4DcZcWK5SJbXiQY5jRILPF7fXeH7E4PoKS7LBO/6d1LeMS7KiihTEcDmuaR
/RR4UgcO8jBAGjft1mgygl289IsBitCrqnwh8/iSQzyDKEeBlAPfvvseBdEQzzAl
QiQ3XlaIq5uK9JBNQ0Ax3v4GWXHm59GNM3FtK5djRcHDbM/oNAT5y+FZJGrz79Ar
ebyjgbuirjUO2VnM0iIAztLuNrmtvpfMLDQTFT8CUZfTdXcIjQ9jZQpMOfcM/XRN
YOsk4bhb3wJu+4rRT5qFNcQ3xTiz6IIcydW61/WVpcuIDpDvraMX69v8T8bwCkk=
=SZXQ
-----END PGP SIGNATURE-----

--ip8pcBLj64CQa79me9xkil3T1Ux0aqsUg--


From nobody Tue Mar  7 07:42:52 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 518EF12964B; Tue,  7 Mar 2017 06:39:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uk0-L_tt6day; Tue,  7 Mar 2017 06:39:40 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F61F1295D7; Tue,  7 Mar 2017 06:35:04 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.90.29; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Stefano Previdi \(sprevidi\)'" <sprevidi@cisco.com>
References: <148881752958.15101.3565092696759250024.idtracker@ietfa.amsl.com> <DA020A62-FCD9-4299-AB69-1321FCDB7C26@cisco.com>
In-Reply-To: <DA020A62-FCD9-4299-AB69-1321FCDB7C26@cisco.com>
Subject: RE: [RTG-DIR] [spring] Review of	draft-ietf-spring-segment-routing-msdc-03
Date: Tue, 7 Mar 2017 09:30:04 -0500
Message-ID: <011d01d2974f$501e0180$f05a0480$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIZjZbZx8c0DAtGCq00IBCvUzcJmALEl04aoOVVLnA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PaITntlHOMtPkA6x4VsPwPK-zzk>
Cc: rtg-dir@ietf.org, spring@ietf.org, ietf@ietf.org, draft-ietf-spring-segment-routing-msdc.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 14:39:58 -0000

Stefano:=20

Summary:  As I have often said, I believe in helping BGP meet the needs =
of operators (DC or BGP), and this includes BGP-LS.  If your transition =
from OSPF/IS-IS LSPs to BGP in BGP to MPLS is to meet operator needs - =
great.   Just document the security concern issues (new types of =
information, privacy issues on sending link info).=20

My "concern" comments on BGP-LS only focus on 3 things:=20
1) Upgrade your security section to deal with issues regarding new types =
of information and privacy issues on sending link-information (inside DC =
or DCI)=20
 1 to 3 paragraphs should be sufficient.  I will suggest text.=20
2) Be precise in your RFC3107 terminology -=20
3)  Encourage the use of 4-byte Private AS, and treat 2-byte Private =
ASes as a legacy issues.   =20

All response below boil down to this summary.   Editorial Nits are your =
choice to adopt/not-adopt.  IETF LC and IESG review will provide you =
lots of feedback on editorial nits. =20

Sue=20

-----Original Message-----
From: rtg-dir [mailto:rtg-dir-bounces@ietf.org] On Behalf Of Stefano =
Previdi (sprevidi)
Sent: Tuesday, March 7, 2017 6:21 AM
To: Susan Hares
Cc: rtg-dir@ietf.org; spring@ietf.org; ietf@ietf.org; =
draft-ietf-spring-segment-routing-msdc.all@ietf.org
Subject: Re: [RTG-DIR] [spring] Review of =
draft-ietf-spring-segment-routing-msdc-03

Hi Sue,

thanks for the review. Some comments below.


> On Mar 6, 2017, at 5:25 PM, Susan Hares <shares@ndzh.com> wrote:
>=20
> Reviewer: Susan Hares
> Review result: Has Issues
>=20
> The RTG-DIR has the categories:  minor concerns or major concerns=20
> regarding "issues", I wil differentiate my issues by this quality.
> I also have editorial nits regardign under specified text.=20
>=20
> Major concerns:=20
> 1) The security section is not sufficient for any review by the=20
> Security area
>=20
> This draft depends on IDR WG draft (ietf-idr-bgp-prefix-sid) that=20
> defines the BGP Segment attribute.  If this attribute is used with=20
> IPv6, this simply gives more infromation about a link to a next.
> However, the combination of this information with the information=20
> passed using draft-ietf-idr-bgpls-segment-routing-epe-09 that utilizes =

> BGP to pass BGP topologies in BGP - requires a better security=20
> section.  BGP-LS was described to be an "information gathering"
> function handled by a few routers on the edge of the network to obtain =

> link-state topology information.  The BGP peers would carry this=20
> information in a separate informational stream.  With this constraint,
> it was approved by the IESG.  =20

Stefano: well, we have now different models that have been deployed and =
assuming that bgp-ls uses a separate stream is not accurate if we look =
what=E2=80=99s in the industry.  However, I take your point and I agree =
that more text in the security section is required in order to emphasize =
that the model the draft addresses is internal (DC and interconnected DC =
over a same-administration network).

Sue:  Good.  I look forward to your security section.  Please note to =
clearly state (or reference) whether the interconnected DC is over =
physically isolated or logically isolated on shared infrastructure.   =
Please indicated any privacy issues.=20

> draft-ietf-idr-bgpls-segment-routing-epe  expands the initial concept=20
> of BGP-LS from "information gathering" to a full-routing scheme of BGP =

> within BGP for data centers and for data center interconnection to the =

> network.

Stefano: EPE defines a model where the topology of the peering point =
(not the network, just the peering point) is advertised to an internal =
server.
Yes, but the topology of peering point may be considered information =
that falls under the "privacy" issues in security.   The security =
considerations should indicate whether you assume the peering point is =
physically isolated or shared infrastructure.  If shared infrastructure, =
are you requiring TCP-AO to e securie.=20

>   This extension takes it out of the approved range of the BGP-LS.
Stefano:  I don=E2=80=99t know what is the =E2=80=9Capproved =
range=E2=80=9D. To me, bgp-ls carries topology information. We started =
with lsdb, then extended to mpls-lsp's, ip tunnels, peering points, and =
more will come. The security of bgp-ls doesn=E2=80=99t change. =
It=E2=80=99s the boundary of the network where bgp-ls is applied that =
matters.

Sue: The focus is the security in this sentence.  The security case in =
the original BGP-LS was the transportation of the BGP-LS information =
(OSPF/ISIS topologies) on a separate network.  If you have changed due =
to customer needs/wants, fine.  Just provide the security case in the 3 =
paragraphs. =20

>  Therefore, the security sections in both the IDR WG drafts and this=20
> draft need to describe the new threat scenarios and describe threat=20
> mitigation strategies for deployments.

Stefano: I will add more text about the information originated by bgp-ls =
(or the bgp prefix sid) and how it is intended to be consumed internally =
to a domain.
Sue: Great!=20

> In addition, the information by BGP-LS =
(draft-ietf-idr-bgpls-segment-routing-epe) or in draft-ietf-bgp-sid=20
> may have privacy issues - so these need to be described the security  =
section.

Stefano: same here. I will emphasize the deployment model and the =
security boundaries.
Sue: Wonderful!=20

> 2) through-out the text you use words such as "ebgp3107" or BGP 3107=20
> updates"
>=20
> This phrase is inaccurate.  The base RFC3107 support will not provide
> BGP-Prefix support (as supported in bgp-idr-bgp-prefix.   Some texts
> goes on to clarify the addition of the BGP SID Prefix attribute.  It=20
> would be better to invent a new phrase or term.

Stefano: I=E2=80=99ll check this out.
Sue: Great, just be a bit more precise in the test to aid future =
implementations.=20

> In section 8.1, the authors state:
> "The Prefix Segement is a lightweight extension to the BGP Labelled=20
> Unicast".  As noted in my #1 major concern, this "hand-waving"
> description either needs to be refined to be accurate.  If the MPLS=20
> usage only uses the BGP-Prefix label and does not extend to the=20
> Egress, it is simplier.

Stefano: the BGP Prefix SID Attribute is just an extension to a 3107 =
update.
Sue: BGP Prefix is an BGP attribute that goes along with BGP-lS BGP =
topology information in the whole solution. =20
The easiest thing is to just leave out the "evaluation".
 Alternatively, make the evaluation more precise by including more =
description.  =20

>  However, it is not clear that is what section
> 8.1 is about.   If 8.1 includes the
> draft-ietf-idr-bgpls-segment-routing-epe, then BGP-LS addition does
> have a number of prefixes and rules.   The trade-off between BGP-LS +
> BGP-LS SID (draft-ietf-idr-bgp-sid) handling + BGP LS egress peer=20
> engineering draft (draft-ietf-idr-bgp-segment-routing-epe) and a=20
> signalling protocol is more complex than the hand-wave.

Stefano: Not sure I understand your point but to me the statement:  =
=E2=80=9CThe Prefix Segment is a lightweight extension to the BGP =
Labelled Unicast=E2=80=9D is correct because the prefix-sid is really =
just a new attribute. Here we=E2=80=99re just talking protocol =
extension. The interaction and combination between prefix-sid and epe is =
a deployment and operational model that (we agreed above) requires more =
explanation in terms of security.

Sue: My purpose here is to simply point out where your RFC3107 and new =
BGP Prefix SID Text too loose. =20
If you want to say that "BGP Prefix SID is a new BGP attribute and it =
along with RFC3107 NLRI provides the internal-DC without the =
DCI-interconnection" - just state that.  =20
This is the purpose of the sentence below:=20
> It may be the  right choice based on current implementations and =
management issues,  but these need to be laid specifically.


> 3) Why are you defining 2-byte Private Use AS when there are plenty of =

> 4-Byte Private Use AS (p. 5).
Stefano: well, we just want to be sure we address the worse case where =
you only have 2 octets.
Sue:  It would be better to encourage the general use of 4-Byte ASes =
which have enough space to give most data center's one AS per box, and =
then deal with the worst case issues.=20

>=20
> This usage increases the confusion regarding 2-byte/4-byte ASN.  IDR  =
specifically worked on 4 byte ASN.

Stefano: yes but in order to be aligned with 7938 we also take into =
account 2 octet ASN and the re-usability of these numbers.
Sue: Wonderful, just add the 4 byte AS. =20

> Minor concerns
> 1) It is not clear what happens in section 4.2.2 and figure 3-5
>=20
> What happens if the traffic goes to node 3 instead of node 4 on the=20
> ECMP path?
> What happens if the traffic goes to node 8 instead of node 7 on the=20
> ECMP Path?
>=20
> Is there something missing in the stroy?=20


nope. This is plain segment routing. As explained in the draft, assuming =
that you use the same SRGB (as recommended) a node is known through the =
same sid value all along the network so ecmp becomes trivial.


> 2) section 4.3 - IBGP Labeled Unicast.=20
>=20
> The phrase "iBGP3107 reflection with nhop-self" needs to be explicitly =

> spelled out as IBGP Route-Reflection with next-hop self.

ok

>  If that is
> not what the authors mean, then it needs to be further spelled out.=20
> It is unclear where the central IBGP nodes are that share fully the=20
> information learned from the three clusters. (nodes:5-8 cluster 1,=20
> nodes 3-4 cluster 2, nodes 9-10 cluster 3).
>=20
> This section has hints of a solution, but it is miss a great deal.=20
> Please upgrade to specific solution.  A diagram might help.=20


yes. I=E2=80=99ll check this out. In short (you certainly figured it =
out) it=E2=80=99s about using iBGP session where each node acts as a RR =
so to propagate to other iBGP peers (this is what "iBGP =
reflection=E2=80=9D refers to). I agree, it=E2=80=99s probably a bit too =
cryptic.


> 3) Load Sharing hints (Section 7.1)
>=20
> Elephant flow and mice flows are good descriptions.  Flowlets and VL2=20
> should either warrant a 1 sentence explanation that actually describes =

> these features in a 22 page draft, or be removed.


We have a reference for them but will add more text.


> 4)  The lack of a manageability or operations section (TBD in version
> -02) - concerns me.  The operational issues may be well known to the=20
> data centers and devices manufacturers who have implement this=20
> specification, but this is an interoperability specification for IETF.
> Some manageabilty comments should be included or a BCP pointed to.=20


ack.


> Editorial issues:=20


I=E2=80=99ll go through all below and update the draft asap.

Thanks.
s.


>=20
> #1 - The following 4 abbrevitions need to be initially expanded when=20
> first used:  CLOs (p.3),  SRGB(p.6), flowlets (p. 14), and VL2 (p.
> 14).=20
>=20
> #2 - page 7, section 4.2 last paragraph
> Old/: assuming the IP Addresses, AS and label-index allocation=20
> previously described, the"
> New/: assuming the IP address with the AS and label-index allocation=20
> previously described, the"
> [Comma is optional]
>=20
> #3 - page 14, section 7.1 paragraph 4,  /(e.g. spine switch Node1)/  - =

> by the diagram it should be node 5-8 or an error.  Please check the=20
> number
>=20
> #4 - page 17, section 8.2 paragraph 2.=20
>=20
> Old/
> This is easily accomplished by encapsulating the trafffic either=20
> directly at the host or the source ToR node by pushing the BGP-=20
> Prefix-SID of the destination ToR for intra-DC traffic, or border node =

> for inter-DC or DC-to-outside-world traffic./
>=20
> New/
> This is easily accomplished by encapsulating the trafffic either=20
> directly at the host or the source ToR node  by pushing  the BGP-=20
> Prefix-SID of the destination ToR for intra-DC traffic, or the=20
> BGP-Prefix-SID for the the border node for inter-DC or=20
> DC-to-outside-world traffic./
>=20
> If this is not the correct logic, then you can reword this further.=20
> I read it 4 or 5 times.=20
>=20
> #5 - Adding a diagram to section 4.3 might help your description.=20
>=20
>=20
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring



From nobody Tue Mar  7 07:44:01 2017
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 70D461294DD for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 06:43:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RmHzSjTrtGHD for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 06:43:06 -0800 (PST)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3B3D129499 for <ietf@ietf.org>; Tue,  7 Mar 2017 06:38:54 -0800 (PST)
Received: by mail-oi0-x233.google.com with SMTP id 62so2719204oih.2 for <ietf@ietf.org>; Tue, 07 Mar 2017 06:38:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=bygm1ecp4D4r14MYTII+9UoobMfNhJjIdCbmmVoZV2s=; b=gSplRpRct2qQaKTtZKZw1Lzuq02qlg7wZ+aefpgK0VyTlkX+jIc6+mx/SxpI8DtbDr 10n+UtN0yvysR2L/3LEfD9RAdDnQFgP5M4sZwcEG4MqB7wRaw0GOZA0KqBgzyZMtcYES CsNlrOmI845PCU4K9z4eyKUSUeOqsstL7KI/qc8ljqUHktrRqFXZ6g9U+m6AKRmrPoMw XaIrHsNBeAjOBuTtaMOq5nDg7KJZO2pc0jC+I5tbOCkl10EqVRtjJEV0dFNAM/v8tV6q wTgbK4GHiuOSgUjgaVth7PVbrgI06Qzf3VrcYFb/dnjQ9pm8HkJkYN98VZfDSZI2pZ8t g9RA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=bygm1ecp4D4r14MYTII+9UoobMfNhJjIdCbmmVoZV2s=; b=p2go5sD8iPh103z1xfNJvtizKOmSKfVU53jCa1smYUNFGovbDoNa4kUIZ98FZttwrg MK8zq+2YwSVmyLLQOfo1ghY3xTeoXPpVsAAKQUaEKqKACK5ZxxYq2507DYEGCPDEd8iM ELwIxVGA7iXWIT8VWRFUoExlGMJmubv7wPuqsWCkgP4MEXDQ7mmOeNXYY6Drb8QOl/6U Z5PGpfWigAHGfG6nVoaUuv3ud6cMaeKvu5S/yzjQnmX9db6DATl6xzWtoTy5yOK006Rz t/8YsOElG4mwjUDO8wHiq/5yImQeEbtbCJeZhCmMUonAmKGr8Ktylui368E4DZO7UZHo I5Pg==
X-Gm-Message-State: AMke39kaMR4nAmg8tojrACWgSp0vOVWrSXAmCAJcU9qgdrDRXmZfydVvS/QQEuH7cAEBSgDxg5DM3zMwvNeUhA==
X-Received: by 10.129.115.84 with SMTP id o81mr263260ywc.186.1488897534222; Tue, 07 Mar 2017 06:38:54 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Tue, 7 Mar 2017 06:38:53 -0800 (PST)
In-Reply-To: <20170307090849.jyl7fqqbn3icjw7a@nic.fr>
References: <HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com> <20170307090849.jyl7fqqbn3icjw7a@nic.fr>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 7 Mar 2017 09:38:53 -0500
X-Google-Sender-Auth: C58bIrXSLlsr8oL7dEopFqYAkz8
Message-ID: <CAMm+LwgJg39CFKvxNNPkwC4XUCWPtrSAxTtce34p11UC8E+NyQ@mail.gmail.com>
Subject: Re: Adding IPv10 to the IETF 98 Agenda.
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: multipart/alternative; boundary=001a1147e302a2685c054a24f8ed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zzaPI36DdD9qC_YqQ4sBnZlMmBM>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 14:43:21 -0000

--001a1147e302a2685c054a24f8ed
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 7, 2017 at 4:08 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
wrote:

> On Mon, Mar 06, 2017 at 05:02:38PM +0000,
>  Khaled Omar <eng.khaled.omar@hotmail.com> wrote
>  a message of 83 lines which said:
>
> > finally I got a positive response from one of the Internet Area
> > Chairs and will be waiting for that discussion during the IETF 98
> > meeting.
>
> Good. IETF is too serious. We need a "wild ideas" session, with IPv10,
> miraculous DNS alternatives, and everything over the blockchain :-)
>
>
=E2=80=8BWe do. You get 20 slides and 6 minutes 40 seconds.=E2=80=8B

--001a1147e302a2685c054a24f8ed
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Ma=
r 7, 2017 at 4:08 AM, Stephane Bortzmeyer <span dir=3D"ltr">&lt;<a href=3D"=
mailto:bortzmeyer@nic.fr" target=3D"_blank">bortzmeyer@nic.fr</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">On Mon, Mar 06, 2017 at 05:02:38=
PM +0000,<br>
=C2=A0Khaled Omar &lt;<a href=3D"mailto:eng.khaled.omar@hotmail.com">eng.kh=
aled.omar@hotmail.com</a>&gt; wrote<br>
<span class=3D"">=C2=A0a message of 83 lines which said:<br>
<br>
&gt; finally I got a positive response from one of the Internet Area<br>
&gt; Chairs and will be waiting for that discussion during the IETF 98<br>
&gt; meeting.<br>
<br>
</span>Good. IETF is too serious. We need a &quot;wild ideas&quot; session,=
 with IPv10,<br>
miraculous DNS alternatives, and everything over the blockchain :-)<br>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra"><div class=3D"gmail=
_default" style=3D"font-size:small">=E2=80=8BWe do. You get 20 slides and 6=
 minutes 40 seconds.=E2=80=8B</div><br></div></div>

--001a1147e302a2685c054a24f8ed--


From nobody Tue Mar  7 08:18:46 2017
Return-Path: <sprevidi@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 75522129524; Tue,  7 Mar 2017 07:31:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VG4OFNT6Xu1N; Tue,  7 Mar 2017 07:31:01 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D0F8129454; Tue,  7 Mar 2017 07:30:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17580; q=dns/txt; s=iport; t=1488900638; x=1490110238; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=S1AVl0XkYCNxhxusGvbXp8LriEEU+GWJ5RS53dKz18M=; b=a/NWJwvTY57ygc5A2m8KeooKEVUAOHLlJQCJAeRppipvSdKhyuxNV/mx s0sS9Ccod/cbuJ3e4uM2H26Ni7i/YFnDn9/pngP/Z8sUrjscYRt6r0Ypb pShx45qQrK6I1qA5J9109SU45MaDtfmA+9UwRjFfFqPdXqNz6J0mAmRR1 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CkAQAu0b5Y/5NdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1FhgQoHg1iKDJEsH5U3gg0fC4UuSgIaggo/GAECAQEBAQEBAWs?= =?us-ascii?q?ohRUBAQEDAQEBIREzBwsFBwQCAQgOAwQBAQECAhESAwICAiULFAEICAIEDgUbi?= =?us-ascii?q?VwIDq9rgiaKfwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQuFQ4IFCIFZgQmEPhY?= =?us-ascii?q?/gkcugjEFnDABih2IGYF7hSKDVIR0gTqIQ4p3AR84gQNWFT8RAYRCHYFjdYkGg?= =?us-ascii?q?Q0BAQE?=
X-IronPort-AV: E=Sophos;i="5.35,258,1484006400"; d="scan'208";a="393734302"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2017 15:30:36 +0000
Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v27FUaae005750 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 7 Mar 2017 15:30:36 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 7 Mar 2017 10:30:35 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Tue, 7 Mar 2017 10:30:35 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Susan Hares <shares@ndzh.com>
Subject: Re: [RTG-DIR] [spring] Review of draft-ietf-spring-segment-routing-msdc-03
Thread-Topic: [RTG-DIR] [spring] Review of draft-ietf-spring-segment-routing-msdc-03
Thread-Index: AQHSl1C1j/llEigTj0eG9gQNVVJNQ6GJ1LOA
Date: Tue, 7 Mar 2017 15:30:35 +0000
Message-ID: <53E0AE02-089D-46DE-9812-E3BC5FDF2C98@cisco.com>
References: <148881752958.15101.3565092696759250024.idtracker@ietfa.amsl.com> <DA020A62-FCD9-4299-AB69-1321FCDB7C26@cisco.com> <011d01d2974f$501e0180$f05a0480$@ndzh.com>
In-Reply-To: <011d01d2974f$501e0180$f05a0480$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.216.167]
Content-Type: text/plain; charset="utf-8"
Content-ID: <44778CAA118FEE4A949AB4D9ED882F86@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Fx62r7J0zqw_5nLmKZgwRg4703Q>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-spring-segment-routing-msdc.all@ietf.org" <draft-ietf-spring-segment-routing-msdc.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 15:31:05 -0000

DQo+IE9uIE1hciA3LCAyMDE3LCBhdCAzOjMwIFBNLCBTdXNhbiBIYXJlcyA8c2hhcmVzQG5kemgu
Y29tPiB3cm90ZToNCj4gDQo+IFN0ZWZhbm86IA0KPiANCj4gU3VtbWFyeTogIEFzIEkgaGF2ZSBv
ZnRlbiBzYWlkLCBJIGJlbGlldmUgaW4gaGVscGluZyBCR1AgbWVldCB0aGUgbmVlZHMgb2Ygb3Bl
cmF0b3JzIChEQyBvciBCR1ApLCBhbmQgdGhpcyBpbmNsdWRlcyBCR1AtTFMuICBJZiB5b3VyIHRy
YW5zaXRpb24gZnJvbSBPU1BGL0lTLUlTIExTUHMgdG8gQkdQIGluIEJHUCB0byBNUExTIGlzIHRv
IG1lZXQgb3BlcmF0b3IgbmVlZHMgLSBncmVhdC4gICBKdXN0IGRvY3VtZW50IHRoZSBzZWN1cml0
eSBjb25jZXJuIGlzc3VlcyAobmV3IHR5cGVzIG9mIGluZm9ybWF0aW9uLCBwcml2YWN5IGlzc3Vl
cyBvbiBzZW5kaW5nIGxpbmsgaW5mbykuIA0KPiANCj4gTXkgImNvbmNlcm4iIGNvbW1lbnRzIG9u
IEJHUC1MUyBvbmx5IGZvY3VzIG9uIDMgdGhpbmdzOiANCj4gMSkgVXBncmFkZSB5b3VyIHNlY3Vy
aXR5IHNlY3Rpb24gdG8gZGVhbCB3aXRoIGlzc3VlcyByZWdhcmRpbmcgbmV3IHR5cGVzIG9mIGlu
Zm9ybWF0aW9uIGFuZCBwcml2YWN5IGlzc3VlcyBvbiBzZW5kaW5nIGxpbmstaW5mb3JtYXRpb24g
KGluc2lkZSBEQyBvciBEQ0kpIA0KDQoNCmFncmVlZCBhbmQgd2lsbCBkbyBzby4gTm90ZSBhbHNv
IHRoYXQgRVBFIGlzIGp1c3Qgb25lIHBpZWNlIG9mIHRoZSBwaWN0dXJlIGRlc2NyaWJlZCBpbiB0
aGUgZHJhZnQuDQoNCg0KPiAxIHRvIDMgcGFyYWdyYXBocyBzaG91bGQgYmUgc3VmZmljaWVudC4g
IEkgd2lsbCBzdWdnZXN0IHRleHQuIA0KPiAyKSBCZSBwcmVjaXNlIGluIHlvdXIgUkZDMzEwNyB0
ZXJtaW5vbG9neSAtIA0KDQoNCmFncmVlZC4gSSBhZGRlZCBzb21lIHRleHQgZXhwbGFpbmluZyB3
aGF0IHdlIGludGVuZCBieSAzMTA3IGViZ3AgYW5kIGliZ3AuDQoNCg0KPiAzKSAgRW5jb3VyYWdl
IHRoZSB1c2Ugb2YgNC1ieXRlIFByaXZhdGUgQVMsIGFuZCB0cmVhdCAyLWJ5dGUgUHJpdmF0ZSBB
U2VzIGFzIGEgbGVnYWN5IGlzc3Vlcy4gDQoNCg0Kb2ssIHdpbGwgZG8gc28uDQoNCg0KPiBBbGwg
cmVzcG9uc2UgYmVsb3cgYm9pbCBkb3duIHRvIHRoaXMgc3VtbWFyeS4gICBFZGl0b3JpYWwgTml0
cyBhcmUgeW91ciBjaG9pY2UgdG8gYWRvcHQvbm90LWFkb3B0LiAgSUVURiBMQyBhbmQgSUVTRyBy
ZXZpZXcgd2lsbCBwcm92aWRlIHlvdSBsb3RzIG9mIGZlZWRiYWNrIG9uIGVkaXRvcmlhbCBuaXRz
Lg0KDQoNCnl1cCwgSSBhcHBsaWVkIGFsbCBvZiB0aGVtLg0KDQpUaGFua3MuDQpzLg0KDQoNCj4g
IA0KPiANCj4gU3VlIA0KPiANCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTog
cnRnLWRpciBbbWFpbHRvOnJ0Zy1kaXItYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFN0
ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpDQo+IFNlbnQ6IFR1ZXNkYXksIE1hcmNoIDcsIDIwMTcg
NjoyMSBBTQ0KPiBUbzogU3VzYW4gSGFyZXMNCj4gQ2M6IHJ0Zy1kaXJAaWV0Zi5vcmc7IHNwcmlu
Z0BpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1zcHJpbmctc2VnbWVudC1yb3V0
aW5nLW1zZGMuYWxsQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbUlRHLURJUl0gW3NwcmluZ10g
UmV2aWV3IG9mIGRyYWZ0LWlldGYtc3ByaW5nLXNlZ21lbnQtcm91dGluZy1tc2RjLTAzDQo+IA0K
PiBIaSBTdWUsDQo+IA0KPiB0aGFua3MgZm9yIHRoZSByZXZpZXcuIFNvbWUgY29tbWVudHMgYmVs
b3cuDQo+IA0KPiANCj4+IE9uIE1hciA2LCAyMDE3LCBhdCA1OjI1IFBNLCBTdXNhbiBIYXJlcyA8
c2hhcmVzQG5kemguY29tPiB3cm90ZToNCj4+IA0KPj4gUmV2aWV3ZXI6IFN1c2FuIEhhcmVzDQo+
PiBSZXZpZXcgcmVzdWx0OiBIYXMgSXNzdWVzDQo+PiANCj4+IFRoZSBSVEctRElSIGhhcyB0aGUg
Y2F0ZWdvcmllczogIG1pbm9yIGNvbmNlcm5zIG9yIG1ham9yIGNvbmNlcm5zIA0KPj4gcmVnYXJk
aW5nICJpc3N1ZXMiLCBJIHdpbCBkaWZmZXJlbnRpYXRlIG15IGlzc3VlcyBieSB0aGlzIHF1YWxp
dHkuDQo+PiBJIGFsc28gaGF2ZSBlZGl0b3JpYWwgbml0cyByZWdhcmRpZ24gdW5kZXIgc3BlY2lm
aWVkIHRleHQuIA0KPj4gDQo+PiBNYWpvciBjb25jZXJuczogDQo+PiAxKSBUaGUgc2VjdXJpdHkg
c2VjdGlvbiBpcyBub3Qgc3VmZmljaWVudCBmb3IgYW55IHJldmlldyBieSB0aGUgDQo+PiBTZWN1
cml0eSBhcmVhDQo+PiANCj4+IFRoaXMgZHJhZnQgZGVwZW5kcyBvbiBJRFIgV0cgZHJhZnQgKGll
dGYtaWRyLWJncC1wcmVmaXgtc2lkKSB0aGF0IA0KPj4gZGVmaW5lcyB0aGUgQkdQIFNlZ21lbnQg
YXR0cmlidXRlLiAgSWYgdGhpcyBhdHRyaWJ1dGUgaXMgdXNlZCB3aXRoIA0KPj4gSVB2NiwgdGhp
cyBzaW1wbHkgZ2l2ZXMgbW9yZSBpbmZyb21hdGlvbiBhYm91dCBhIGxpbmsgdG8gYSBuZXh0Lg0K
Pj4gSG93ZXZlciwgdGhlIGNvbWJpbmF0aW9uIG9mIHRoaXMgaW5mb3JtYXRpb24gd2l0aCB0aGUg
aW5mb3JtYXRpb24gDQo+PiBwYXNzZWQgdXNpbmcgZHJhZnQtaWV0Zi1pZHItYmdwbHMtc2VnbWVu
dC1yb3V0aW5nLWVwZS0wOSB0aGF0IHV0aWxpemVzIA0KPj4gQkdQIHRvIHBhc3MgQkdQIHRvcG9s
b2dpZXMgaW4gQkdQIC0gcmVxdWlyZXMgYSBiZXR0ZXIgc2VjdXJpdHkgDQo+PiBzZWN0aW9uLiAg
QkdQLUxTIHdhcyBkZXNjcmliZWQgdG8gYmUgYW4gImluZm9ybWF0aW9uIGdhdGhlcmluZyINCj4+
IGZ1bmN0aW9uIGhhbmRsZWQgYnkgYSBmZXcgcm91dGVycyBvbiB0aGUgZWRnZSBvZiB0aGUgbmV0
d29yayB0byBvYnRhaW4gDQo+PiBsaW5rLXN0YXRlIHRvcG9sb2d5IGluZm9ybWF0aW9uLiAgVGhl
IEJHUCBwZWVycyB3b3VsZCBjYXJyeSB0aGlzIA0KPj4gaW5mb3JtYXRpb24gaW4gYSBzZXBhcmF0
ZSBpbmZvcm1hdGlvbmFsIHN0cmVhbS4gIFdpdGggdGhpcyBjb25zdHJhaW50LA0KPj4gaXQgd2Fz
IGFwcHJvdmVkIGJ5IHRoZSBJRVNHLiAgIA0KPiANCj4gU3RlZmFubzogd2VsbCwgd2UgaGF2ZSBu
b3cgZGlmZmVyZW50IG1vZGVscyB0aGF0IGhhdmUgYmVlbiBkZXBsb3llZCBhbmQgYXNzdW1pbmcg
dGhhdCBiZ3AtbHMgdXNlcyBhIHNlcGFyYXRlIHN0cmVhbSBpcyBub3QgYWNjdXJhdGUgaWYgd2Ug
bG9vayB3aGF04oCZcyBpbiB0aGUgaW5kdXN0cnkuICBIb3dldmVyLCBJIHRha2UgeW91ciBwb2lu
dCBhbmQgSSBhZ3JlZSB0aGF0IG1vcmUgdGV4dCBpbiB0aGUgc2VjdXJpdHkgc2VjdGlvbiBpcyBy
ZXF1aXJlZCBpbiBvcmRlciB0byBlbXBoYXNpemUgdGhhdCB0aGUgbW9kZWwgdGhlIGRyYWZ0IGFk
ZHJlc3NlcyBpcyBpbnRlcm5hbCAoREMgYW5kIGludGVyY29ubmVjdGVkIERDIG92ZXIgYSBzYW1l
LWFkbWluaXN0cmF0aW9uIG5ldHdvcmspLg0KPiANCj4gU3VlOiAgR29vZC4gIEkgbG9vayBmb3J3
YXJkIHRvIHlvdXIgc2VjdXJpdHkgc2VjdGlvbi4gIFBsZWFzZSBub3RlIHRvIGNsZWFybHkgc3Rh
dGUgKG9yIHJlZmVyZW5jZSkgd2hldGhlciB0aGUgaW50ZXJjb25uZWN0ZWQgREMgaXMgb3ZlciBw
aHlzaWNhbGx5IGlzb2xhdGVkIG9yIGxvZ2ljYWxseSBpc29sYXRlZCBvbiBzaGFyZWQgaW5mcmFz
dHJ1Y3R1cmUuICAgUGxlYXNlIGluZGljYXRlZCBhbnkgcHJpdmFjeSBpc3N1ZXMuIA0KPiANCj4+
IGRyYWZ0LWlldGYtaWRyLWJncGxzLXNlZ21lbnQtcm91dGluZy1lcGUgIGV4cGFuZHMgdGhlIGlu
aXRpYWwgY29uY2VwdCANCj4+IG9mIEJHUC1MUyBmcm9tICJpbmZvcm1hdGlvbiBnYXRoZXJpbmci
IHRvIGEgZnVsbC1yb3V0aW5nIHNjaGVtZSBvZiBCR1AgDQo+PiB3aXRoaW4gQkdQIGZvciBkYXRh
IGNlbnRlcnMgYW5kIGZvciBkYXRhIGNlbnRlciBpbnRlcmNvbm5lY3Rpb24gdG8gdGhlIA0KPj4g
bmV0d29yay4NCj4gDQo+IFN0ZWZhbm86IEVQRSBkZWZpbmVzIGEgbW9kZWwgd2hlcmUgdGhlIHRv
cG9sb2d5IG9mIHRoZSBwZWVyaW5nIHBvaW50IChub3QgdGhlIG5ldHdvcmssIGp1c3QgdGhlIHBl
ZXJpbmcgcG9pbnQpIGlzIGFkdmVydGlzZWQgdG8gYW4gaW50ZXJuYWwgc2VydmVyLg0KPiBZZXMs
IGJ1dCB0aGUgdG9wb2xvZ3kgb2YgcGVlcmluZyBwb2ludCBtYXkgYmUgY29uc2lkZXJlZCBpbmZv
cm1hdGlvbiB0aGF0IGZhbGxzIHVuZGVyIHRoZSAicHJpdmFjeSIgaXNzdWVzIGluIHNlY3VyaXR5
LiAgIFRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyBzaG91bGQgaW5kaWNhdGUgd2hldGhlciB5
b3UgYXNzdW1lIHRoZSBwZWVyaW5nIHBvaW50IGlzIHBoeXNpY2FsbHkgaXNvbGF0ZWQgb3Igc2hh
cmVkIGluZnJhc3RydWN0dXJlLiAgSWYgc2hhcmVkIGluZnJhc3RydWN0dXJlLCBhcmUgeW91IHJl
cXVpcmluZyBUQ1AtQU8gdG8gZSBzZWN1cmllLiANCj4gDQo+PiAgVGhpcyBleHRlbnNpb24gdGFr
ZXMgaXQgb3V0IG9mIHRoZSBhcHByb3ZlZCByYW5nZSBvZiB0aGUgQkdQLUxTLg0KPiBTdGVmYW5v
OiAgSSBkb27igJl0IGtub3cgd2hhdCBpcyB0aGUg4oCcYXBwcm92ZWQgcmFuZ2XigJ0uIFRvIG1l
LCBiZ3AtbHMgY2FycmllcyB0b3BvbG9neSBpbmZvcm1hdGlvbi4gV2Ugc3RhcnRlZCB3aXRoIGxz
ZGIsIHRoZW4gZXh0ZW5kZWQgdG8gbXBscy1sc3AncywgaXAgdHVubmVscywgcGVlcmluZyBwb2lu
dHMsIGFuZCBtb3JlIHdpbGwgY29tZS4gVGhlIHNlY3VyaXR5IG9mIGJncC1scyBkb2VzbuKAmXQg
Y2hhbmdlLiBJdOKAmXMgdGhlIGJvdW5kYXJ5IG9mIHRoZSBuZXR3b3JrIHdoZXJlIGJncC1scyBp
cyBhcHBsaWVkIHRoYXQgbWF0dGVycy4NCj4gDQo+IFN1ZTogVGhlIGZvY3VzIGlzIHRoZSBzZWN1
cml0eSBpbiB0aGlzIHNlbnRlbmNlLiAgVGhlIHNlY3VyaXR5IGNhc2UgaW4gdGhlIG9yaWdpbmFs
IEJHUC1MUyB3YXMgdGhlIHRyYW5zcG9ydGF0aW9uIG9mIHRoZSBCR1AtTFMgaW5mb3JtYXRpb24g
KE9TUEYvSVNJUyB0b3BvbG9naWVzKSBvbiBhIHNlcGFyYXRlIG5ldHdvcmsuICBJZiB5b3UgaGF2
ZSBjaGFuZ2VkIGR1ZSB0byBjdXN0b21lciBuZWVkcy93YW50cywgZmluZS4gIEp1c3QgcHJvdmlk
ZSB0aGUgc2VjdXJpdHkgY2FzZSBpbiB0aGUgMyBwYXJhZ3JhcGhzLiAgDQo+IA0KPj4gVGhlcmVm
b3JlLCB0aGUgc2VjdXJpdHkgc2VjdGlvbnMgaW4gYm90aCB0aGUgSURSIFdHIGRyYWZ0cyBhbmQg
dGhpcyANCj4+IGRyYWZ0IG5lZWQgdG8gZGVzY3JpYmUgdGhlIG5ldyB0aHJlYXQgc2NlbmFyaW9z
IGFuZCBkZXNjcmliZSB0aHJlYXQgDQo+PiBtaXRpZ2F0aW9uIHN0cmF0ZWdpZXMgZm9yIGRlcGxv
eW1lbnRzLg0KPiANCj4gU3RlZmFubzogSSB3aWxsIGFkZCBtb3JlIHRleHQgYWJvdXQgdGhlIGlu
Zm9ybWF0aW9uIG9yaWdpbmF0ZWQgYnkgYmdwLWxzIChvciB0aGUgYmdwIHByZWZpeCBzaWQpIGFu
ZCBob3cgaXQgaXMgaW50ZW5kZWQgdG8gYmUgY29uc3VtZWQgaW50ZXJuYWxseSB0byBhIGRvbWFp
bi4NCj4gU3VlOiBHcmVhdCEgDQo+IA0KPj4gSW4gYWRkaXRpb24sIHRoZSBpbmZvcm1hdGlvbiBi
eSBCR1AtTFMgKGRyYWZ0LWlldGYtaWRyLWJncGxzLXNlZ21lbnQtcm91dGluZy1lcGUpIG9yIGlu
IGRyYWZ0LWlldGYtYmdwLXNpZCANCj4+IG1heSBoYXZlIHByaXZhY3kgaXNzdWVzIC0gc28gdGhl
c2UgbmVlZCB0byBiZSBkZXNjcmliZWQgdGhlIHNlY3VyaXR5ICBzZWN0aW9uLg0KPiANCj4gU3Rl
ZmFubzogc2FtZSBoZXJlLiBJIHdpbGwgZW1waGFzaXplIHRoZSBkZXBsb3ltZW50IG1vZGVsIGFu
ZCB0aGUgc2VjdXJpdHkgYm91bmRhcmllcy4NCj4gU3VlOiBXb25kZXJmdWwhIA0KPiANCj4+IDIp
IHRocm91Z2gtb3V0IHRoZSB0ZXh0IHlvdSB1c2Ugd29yZHMgc3VjaCBhcyAiZWJncDMxMDciIG9y
IEJHUCAzMTA3IA0KPj4gdXBkYXRlcyINCj4+IA0KPj4gVGhpcyBwaHJhc2UgaXMgaW5hY2N1cmF0
ZS4gIFRoZSBiYXNlIFJGQzMxMDcgc3VwcG9ydCB3aWxsIG5vdCBwcm92aWRlDQo+PiBCR1AtUHJl
Zml4IHN1cHBvcnQgKGFzIHN1cHBvcnRlZCBpbiBiZ3AtaWRyLWJncC1wcmVmaXguICAgU29tZSB0
ZXh0cw0KPj4gZ29lcyBvbiB0byBjbGFyaWZ5IHRoZSBhZGRpdGlvbiBvZiB0aGUgQkdQIFNJRCBQ
cmVmaXggYXR0cmlidXRlLiAgSXQgDQo+PiB3b3VsZCBiZSBiZXR0ZXIgdG8gaW52ZW50IGEgbmV3
IHBocmFzZSBvciB0ZXJtLg0KPiANCj4gU3RlZmFubzogSeKAmWxsIGNoZWNrIHRoaXMgb3V0Lg0K
PiBTdWU6IEdyZWF0LCBqdXN0IGJlIGEgYml0IG1vcmUgcHJlY2lzZSBpbiB0aGUgdGVzdCB0byBh
aWQgZnV0dXJlIGltcGxlbWVudGF0aW9ucy4gDQo+IA0KPj4gSW4gc2VjdGlvbiA4LjEsIHRoZSBh
dXRob3JzIHN0YXRlOg0KPj4gIlRoZSBQcmVmaXggU2VnZW1lbnQgaXMgYSBsaWdodHdlaWdodCBl
eHRlbnNpb24gdG8gdGhlIEJHUCBMYWJlbGxlZCANCj4+IFVuaWNhc3QiLiAgQXMgbm90ZWQgaW4g
bXkgIzEgbWFqb3IgY29uY2VybiwgdGhpcyAiaGFuZC13YXZpbmciDQo+PiBkZXNjcmlwdGlvbiBl
aXRoZXIgbmVlZHMgdG8gYmUgcmVmaW5lZCB0byBiZSBhY2N1cmF0ZS4gIElmIHRoZSBNUExTIA0K
Pj4gdXNhZ2Ugb25seSB1c2VzIHRoZSBCR1AtUHJlZml4IGxhYmVsIGFuZCBkb2VzIG5vdCBleHRl
bmQgdG8gdGhlIA0KPj4gRWdyZXNzLCBpdCBpcyBzaW1wbGllci4NCj4gDQo+IFN0ZWZhbm86IHRo
ZSBCR1AgUHJlZml4IFNJRCBBdHRyaWJ1dGUgaXMganVzdCBhbiBleHRlbnNpb24gdG8gYSAzMTA3
IHVwZGF0ZS4NCj4gU3VlOiBCR1AgUHJlZml4IGlzIGFuIEJHUCBhdHRyaWJ1dGUgdGhhdCBnb2Vz
IGFsb25nIHdpdGggQkdQLWxTIEJHUCB0b3BvbG9neSBpbmZvcm1hdGlvbiBpbiB0aGUgd2hvbGUg
c29sdXRpb24uICANCj4gVGhlIGVhc2llc3QgdGhpbmcgaXMgdG8ganVzdCBsZWF2ZSBvdXQgdGhl
ICJldmFsdWF0aW9uIi4NCj4gQWx0ZXJuYXRpdmVseSwgbWFrZSB0aGUgZXZhbHVhdGlvbiBtb3Jl
IHByZWNpc2UgYnkgaW5jbHVkaW5nIG1vcmUgZGVzY3JpcHRpb24uICAgDQo+IA0KPj4gSG93ZXZl
ciwgaXQgaXMgbm90IGNsZWFyIHRoYXQgaXMgd2hhdCBzZWN0aW9uDQo+PiA4LjEgaXMgYWJvdXQu
ICAgSWYgOC4xIGluY2x1ZGVzIHRoZQ0KPj4gZHJhZnQtaWV0Zi1pZHItYmdwbHMtc2VnbWVudC1y
b3V0aW5nLWVwZSwgdGhlbiBCR1AtTFMgYWRkaXRpb24gZG9lcw0KPj4gaGF2ZSBhIG51bWJlciBv
ZiBwcmVmaXhlcyBhbmQgcnVsZXMuICAgVGhlIHRyYWRlLW9mZiBiZXR3ZWVuIEJHUC1MUyArDQo+
PiBCR1AtTFMgU0lEIChkcmFmdC1pZXRmLWlkci1iZ3Atc2lkKSBoYW5kbGluZyArIEJHUCBMUyBl
Z3Jlc3MgcGVlciANCj4+IGVuZ2luZWVyaW5nIGRyYWZ0IChkcmFmdC1pZXRmLWlkci1iZ3Atc2Vn
bWVudC1yb3V0aW5nLWVwZSkgYW5kIGEgDQo+PiBzaWduYWxsaW5nIHByb3RvY29sIGlzIG1vcmUg
Y29tcGxleCB0aGFuIHRoZSBoYW5kLXdhdmUuDQo+IA0KPiBTdGVmYW5vOiBOb3Qgc3VyZSBJIHVu
ZGVyc3RhbmQgeW91ciBwb2ludCBidXQgdG8gbWUgdGhlIHN0YXRlbWVudDogIOKAnFRoZSBQcmVm
aXggU2VnbWVudCBpcyBhIGxpZ2h0d2VpZ2h0IGV4dGVuc2lvbiB0byB0aGUgQkdQIExhYmVsbGVk
IFVuaWNhc3TigJ0gaXMgY29ycmVjdCBiZWNhdXNlIHRoZSBwcmVmaXgtc2lkIGlzIHJlYWxseSBq
dXN0IGEgbmV3IGF0dHJpYnV0ZS4gSGVyZSB3ZeKAmXJlIGp1c3QgdGFsa2luZyBwcm90b2NvbCBl
eHRlbnNpb24uIFRoZSBpbnRlcmFjdGlvbiBhbmQgY29tYmluYXRpb24gYmV0d2VlbiBwcmVmaXgt
c2lkIGFuZCBlcGUgaXMgYSBkZXBsb3ltZW50IGFuZCBvcGVyYXRpb25hbCBtb2RlbCB0aGF0ICh3
ZSBhZ3JlZWQgYWJvdmUpIHJlcXVpcmVzIG1vcmUgZXhwbGFuYXRpb24gaW4gdGVybXMgb2Ygc2Vj
dXJpdHkuDQo+IA0KPiBTdWU6IE15IHB1cnBvc2UgaGVyZSBpcyB0byBzaW1wbHkgcG9pbnQgb3V0
IHdoZXJlIHlvdXIgUkZDMzEwNyBhbmQgbmV3IEJHUCBQcmVmaXggU0lEIFRleHQgdG9vIGxvb3Nl
LiAgDQo+IElmIHlvdSB3YW50IHRvIHNheSB0aGF0ICJCR1AgUHJlZml4IFNJRCBpcyBhIG5ldyBC
R1AgYXR0cmlidXRlIGFuZCBpdCBhbG9uZyB3aXRoIFJGQzMxMDcgTkxSSSBwcm92aWRlcyB0aGUg
aW50ZXJuYWwtREMgd2l0aG91dCB0aGUgRENJLWludGVyY29ubmVjdGlvbiIgLSBqdXN0IHN0YXRl
IHRoYXQuICAgDQo+IFRoaXMgaXMgdGhlIHB1cnBvc2Ugb2YgdGhlIHNlbnRlbmNlIGJlbG93OiAN
Cj4+IEl0IG1heSBiZSB0aGUgIHJpZ2h0IGNob2ljZSBiYXNlZCBvbiBjdXJyZW50IGltcGxlbWVu
dGF0aW9ucyBhbmQgbWFuYWdlbWVudCBpc3N1ZXMsICBidXQgdGhlc2UgbmVlZCB0byBiZSBsYWlk
IHNwZWNpZmljYWxseS4NCj4gDQo+IA0KPj4gMykgV2h5IGFyZSB5b3UgZGVmaW5pbmcgMi1ieXRl
IFByaXZhdGUgVXNlIEFTIHdoZW4gdGhlcmUgYXJlIHBsZW50eSBvZiANCj4+IDQtQnl0ZSBQcml2
YXRlIFVzZSBBUyAocC4gNSkuDQo+IFN0ZWZhbm86IHdlbGwsIHdlIGp1c3Qgd2FudCB0byBiZSBz
dXJlIHdlIGFkZHJlc3MgdGhlIHdvcnNlIGNhc2Ugd2hlcmUgeW91IG9ubHkgaGF2ZSAyIG9jdGV0
cy4NCj4gU3VlOiAgSXQgd291bGQgYmUgYmV0dGVyIHRvIGVuY291cmFnZSB0aGUgZ2VuZXJhbCB1
c2Ugb2YgNC1CeXRlIEFTZXMgd2hpY2ggaGF2ZSBlbm91Z2ggc3BhY2UgdG8gZ2l2ZSBtb3N0IGRh
dGEgY2VudGVyJ3Mgb25lIEFTIHBlciBib3gsIGFuZCB0aGVuIGRlYWwgd2l0aCB0aGUgd29yc3Qg
Y2FzZSBpc3N1ZXMuIA0KPiANCj4+IA0KPj4gVGhpcyB1c2FnZSBpbmNyZWFzZXMgdGhlIGNvbmZ1
c2lvbiByZWdhcmRpbmcgMi1ieXRlLzQtYnl0ZSBBU04uICBJRFIgIHNwZWNpZmljYWxseSB3b3Jr
ZWQgb24gNCBieXRlIEFTTi4NCj4gDQo+IFN0ZWZhbm86IHllcyBidXQgaW4gb3JkZXIgdG8gYmUg
YWxpZ25lZCB3aXRoIDc5Mzggd2UgYWxzbyB0YWtlIGludG8gYWNjb3VudCAyIG9jdGV0IEFTTiBh
bmQgdGhlIHJlLXVzYWJpbGl0eSBvZiB0aGVzZSBudW1iZXJzLg0KPiBTdWU6IFdvbmRlcmZ1bCwg
anVzdCBhZGQgdGhlIDQgYnl0ZSBBUy4gIA0KPiANCj4+IE1pbm9yIGNvbmNlcm5zDQo+PiAxKSBJ
dCBpcyBub3QgY2xlYXIgd2hhdCBoYXBwZW5zIGluIHNlY3Rpb24gNC4yLjIgYW5kIGZpZ3VyZSAz
LTUNCj4+IA0KPj4gV2hhdCBoYXBwZW5zIGlmIHRoZSB0cmFmZmljIGdvZXMgdG8gbm9kZSAzIGlu
c3RlYWQgb2Ygbm9kZSA0IG9uIHRoZSANCj4+IEVDTVAgcGF0aD8NCj4+IFdoYXQgaGFwcGVucyBp
ZiB0aGUgdHJhZmZpYyBnb2VzIHRvIG5vZGUgOCBpbnN0ZWFkIG9mIG5vZGUgNyBvbiB0aGUgDQo+
PiBFQ01QIFBhdGg/DQo+PiANCj4+IElzIHRoZXJlIHNvbWV0aGluZyBtaXNzaW5nIGluIHRoZSBz
dHJveT8gDQo+IA0KPiANCj4gbm9wZS4gVGhpcyBpcyBwbGFpbiBzZWdtZW50IHJvdXRpbmcuIEFz
IGV4cGxhaW5lZCBpbiB0aGUgZHJhZnQsIGFzc3VtaW5nIHRoYXQgeW91IHVzZSB0aGUgc2FtZSBT
UkdCIChhcyByZWNvbW1lbmRlZCkgYSBub2RlIGlzIGtub3duIHRocm91Z2ggdGhlIHNhbWUgc2lk
IHZhbHVlIGFsbCBhbG9uZyB0aGUgbmV0d29yayBzbyBlY21wIGJlY29tZXMgdHJpdmlhbC4NCj4g
DQo+IA0KPj4gMikgc2VjdGlvbiA0LjMgLSBJQkdQIExhYmVsZWQgVW5pY2FzdC4gDQo+PiANCj4+
IFRoZSBwaHJhc2UgImlCR1AzMTA3IHJlZmxlY3Rpb24gd2l0aCBuaG9wLXNlbGYiIG5lZWRzIHRv
IGJlIGV4cGxpY2l0bHkgDQo+PiBzcGVsbGVkIG91dCBhcyBJQkdQIFJvdXRlLVJlZmxlY3Rpb24g
d2l0aCBuZXh0LWhvcCBzZWxmLg0KPiANCj4gb2sNCj4gDQo+PiBJZiB0aGF0IGlzDQo+PiBub3Qg
d2hhdCB0aGUgYXV0aG9ycyBtZWFuLCB0aGVuIGl0IG5lZWRzIHRvIGJlIGZ1cnRoZXIgc3BlbGxl
ZCBvdXQuIA0KPj4gSXQgaXMgdW5jbGVhciB3aGVyZSB0aGUgY2VudHJhbCBJQkdQIG5vZGVzIGFy
ZSB0aGF0IHNoYXJlIGZ1bGx5IHRoZSANCj4+IGluZm9ybWF0aW9uIGxlYXJuZWQgZnJvbSB0aGUg
dGhyZWUgY2x1c3RlcnMuIChub2Rlczo1LTggY2x1c3RlciAxLCANCj4+IG5vZGVzIDMtNCBjbHVz
dGVyIDIsIG5vZGVzIDktMTAgY2x1c3RlciAzKS4NCj4+IA0KPj4gVGhpcyBzZWN0aW9uIGhhcyBo
aW50cyBvZiBhIHNvbHV0aW9uLCBidXQgaXQgaXMgbWlzcyBhIGdyZWF0IGRlYWwuIA0KPj4gUGxl
YXNlIHVwZ3JhZGUgdG8gc3BlY2lmaWMgc29sdXRpb24uICBBIGRpYWdyYW0gbWlnaHQgaGVscC4g
DQo+IA0KPiANCj4geWVzLiBJ4oCZbGwgY2hlY2sgdGhpcyBvdXQuIEluIHNob3J0ICh5b3UgY2Vy
dGFpbmx5IGZpZ3VyZWQgaXQgb3V0KSBpdOKAmXMgYWJvdXQgdXNpbmcgaUJHUCBzZXNzaW9uIHdo
ZXJlIGVhY2ggbm9kZSBhY3RzIGFzIGEgUlIgc28gdG8gcHJvcGFnYXRlIHRvIG90aGVyIGlCR1Ag
cGVlcnMgKHRoaXMgaXMgd2hhdCAiaUJHUCByZWZsZWN0aW9u4oCdIHJlZmVycyB0bykuIEkgYWdy
ZWUsIGl04oCZcyBwcm9iYWJseSBhIGJpdCB0b28gY3J5cHRpYy4NCj4gDQo+IA0KPj4gMykgTG9h
ZCBTaGFyaW5nIGhpbnRzIChTZWN0aW9uIDcuMSkNCj4+IA0KPj4gRWxlcGhhbnQgZmxvdyBhbmQg
bWljZSBmbG93cyBhcmUgZ29vZCBkZXNjcmlwdGlvbnMuICBGbG93bGV0cyBhbmQgVkwyIA0KPj4g
c2hvdWxkIGVpdGhlciB3YXJyYW50IGEgMSBzZW50ZW5jZSBleHBsYW5hdGlvbiB0aGF0IGFjdHVh
bGx5IGRlc2NyaWJlcyANCj4+IHRoZXNlIGZlYXR1cmVzIGluIGEgMjIgcGFnZSBkcmFmdCwgb3Ig
YmUgcmVtb3ZlZC4NCj4gDQo+IA0KPiBXZSBoYXZlIGEgcmVmZXJlbmNlIGZvciB0aGVtIGJ1dCB3
aWxsIGFkZCBtb3JlIHRleHQuDQo+IA0KPiANCj4+IDQpICBUaGUgbGFjayBvZiBhIG1hbmFnZWFi
aWxpdHkgb3Igb3BlcmF0aW9ucyBzZWN0aW9uIChUQkQgaW4gdmVyc2lvbg0KPj4gLTAyKSAtIGNv
bmNlcm5zIG1lLiAgVGhlIG9wZXJhdGlvbmFsIGlzc3VlcyBtYXkgYmUgd2VsbCBrbm93biB0byB0
aGUgDQo+PiBkYXRhIGNlbnRlcnMgYW5kIGRldmljZXMgbWFudWZhY3R1cmVycyB3aG8gaGF2ZSBp
bXBsZW1lbnQgdGhpcyANCj4+IHNwZWNpZmljYXRpb24sIGJ1dCB0aGlzIGlzIGFuIGludGVyb3Bl
cmFiaWxpdHkgc3BlY2lmaWNhdGlvbiBmb3IgSUVURi4NCj4+IFNvbWUgbWFuYWdlYWJpbHR5IGNv
bW1lbnRzIHNob3VsZCBiZSBpbmNsdWRlZCBvciBhIEJDUCBwb2ludGVkIHRvLiANCj4gDQo+IA0K
PiBhY2suDQo+IA0KPiANCj4+IEVkaXRvcmlhbCBpc3N1ZXM6IA0KPiANCj4gDQo+IEnigJlsbCBn
byB0aHJvdWdoIGFsbCBiZWxvdyBhbmQgdXBkYXRlIHRoZSBkcmFmdCBhc2FwLg0KPiANCj4gVGhh
bmtzLg0KPiBzLg0KPiANCj4gDQo+PiANCj4+ICMxIC0gVGhlIGZvbGxvd2luZyA0IGFiYnJldml0
aW9ucyBuZWVkIHRvIGJlIGluaXRpYWxseSBleHBhbmRlZCB3aGVuIA0KPj4gZmlyc3QgdXNlZDog
IENMT3MgKHAuMyksICBTUkdCKHAuNiksIGZsb3dsZXRzIChwLiAxNCksIGFuZCBWTDIgKHAuDQo+
PiAxNCkuIA0KPj4gDQo+PiAjMiAtIHBhZ2UgNywgc2VjdGlvbiA0LjIgbGFzdCBwYXJhZ3JhcGgN
Cj4+IE9sZC86IGFzc3VtaW5nIHRoZSBJUCBBZGRyZXNzZXMsIEFTIGFuZCBsYWJlbC1pbmRleCBh
bGxvY2F0aW9uIA0KPj4gcHJldmlvdXNseSBkZXNjcmliZWQsIHRoZSINCj4+IE5ldy86IGFzc3Vt
aW5nIHRoZSBJUCBhZGRyZXNzIHdpdGggdGhlIEFTIGFuZCBsYWJlbC1pbmRleCBhbGxvY2F0aW9u
IA0KPj4gcHJldmlvdXNseSBkZXNjcmliZWQsIHRoZSINCj4+IFtDb21tYSBpcyBvcHRpb25hbF0N
Cj4+IA0KPj4gIzMgLSBwYWdlIDE0LCBzZWN0aW9uIDcuMSBwYXJhZ3JhcGggNCwgIC8oZS5nLiBz
cGluZSBzd2l0Y2ggTm9kZTEpLyAgLSANCj4+IGJ5IHRoZSBkaWFncmFtIGl0IHNob3VsZCBiZSBu
b2RlIDUtOCBvciBhbiBlcnJvci4gIFBsZWFzZSBjaGVjayB0aGUgDQo+PiBudW1iZXINCj4+IA0K
Pj4gIzQgLSBwYWdlIDE3LCBzZWN0aW9uIDguMiBwYXJhZ3JhcGggMi4gDQo+PiANCj4+IE9sZC8N
Cj4+IFRoaXMgaXMgZWFzaWx5IGFjY29tcGxpc2hlZCBieSBlbmNhcHN1bGF0aW5nIHRoZSB0cmFm
ZmZpYyBlaXRoZXIgDQo+PiBkaXJlY3RseSBhdCB0aGUgaG9zdCBvciB0aGUgc291cmNlIFRvUiBu
b2RlIGJ5IHB1c2hpbmcgdGhlIEJHUC0gDQo+PiBQcmVmaXgtU0lEIG9mIHRoZSBkZXN0aW5hdGlv
biBUb1IgZm9yIGludHJhLURDIHRyYWZmaWMsIG9yIGJvcmRlciBub2RlIA0KPj4gZm9yIGludGVy
LURDIG9yIERDLXRvLW91dHNpZGUtd29ybGQgdHJhZmZpYy4vDQo+PiANCj4+IE5ldy8NCj4+IFRo
aXMgaXMgZWFzaWx5IGFjY29tcGxpc2hlZCBieSBlbmNhcHN1bGF0aW5nIHRoZSB0cmFmZmZpYyBl
aXRoZXIgDQo+PiBkaXJlY3RseSBhdCB0aGUgaG9zdCBvciB0aGUgc291cmNlIFRvUiBub2RlICBi
eSBwdXNoaW5nICB0aGUgQkdQLSANCj4+IFByZWZpeC1TSUQgb2YgdGhlIGRlc3RpbmF0aW9uIFRv
UiBmb3IgaW50cmEtREMgdHJhZmZpYywgb3IgdGhlIA0KPj4gQkdQLVByZWZpeC1TSUQgZm9yIHRo
ZSB0aGUgYm9yZGVyIG5vZGUgZm9yIGludGVyLURDIG9yIA0KPj4gREMtdG8tb3V0c2lkZS13b3Js
ZCB0cmFmZmljLi8NCj4+IA0KPj4gSWYgdGhpcyBpcyBub3QgdGhlIGNvcnJlY3QgbG9naWMsIHRo
ZW4geW91IGNhbiByZXdvcmQgdGhpcyBmdXJ0aGVyLiANCj4+IEkgcmVhZCBpdCA0IG9yIDUgdGlt
ZXMuIA0KPj4gDQo+PiAjNSAtIEFkZGluZyBhIGRpYWdyYW0gdG8gc2VjdGlvbiA0LjMgbWlnaHQg
aGVscCB5b3VyIGRlc2NyaXB0aW9uLiANCj4+IA0KPj4gDQo+PiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gc3ByaW5nIG1haWxpbmcgbGlzdA0KPj4g
c3ByaW5nQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L3NwcmluZw0KPiANCj4gDQoNCg==


From nobody Tue Mar  7 08:19:29 2017
Return-Path: <stewart.bryant@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 7FB7A12958A for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 07:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7OqvVe__uJp for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 07:43:34 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11E89129630 for <ietf@ietf.org>; Tue,  7 Mar 2017 07:43:02 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id t189so8297826wmt.1 for <ietf@ietf.org>; Tue, 07 Mar 2017 07:43:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to; bh=t1liks9zUfObfXFwT32s/7Oj51euQCqcTPcAW6cm4vI=; b=dqo9JYQaSlAHQVBGsfcIF+Kek+0z2H0sx04Dt64VT3ejdLUt+lE6XfVSW8WN1TkTxt AsW+w3RjHb9SJPg0xPxos8PgBWWx/HV2qUUow3IHMqn0PZ7ynFoPM4XLVoW7fWRuo5Wp cZWkXX7kiApYIUko5b0jyMj24xLOIyS9aT412PQWSXjHQ4owGdCIJQnOxgHJsQLeH3kq 5m5Z0hb9afMHPd/c0aOymypZnlPrvGTdKHBRMZEfUQSswiwTqKyOBNDDAHJRD3sWFK20 NBMTX/NVReQWbKDKgFZ8g+eJ67hg04sEujUFuDSOztVrNUHQgwZJ3yxB6JHGiXoQugj6 SX1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to; bh=t1liks9zUfObfXFwT32s/7Oj51euQCqcTPcAW6cm4vI=; b=bGQ5x98ygaPt+2g6okPBEcQ+a8foA4qdT0tVgNfXJ7bQMO0SY7YN9FfUyQwEarNlkT UqeRKcF0xLWNUZpEq95Z41RFGC80m/MA5ET7On90N5KPK3Fo6iJRfkvNymebm0F4CSL4 8ixKlwgY/8lVcT0uC/ggpKlFokfxihPyWSpmFNpe0tsRNxIkVWybDfLS5lxd0fnxaV5Y vJ7Uqlf2mByAqtMvJVU2wS4mZ0ehFdyq5+DR3z1pkYQvHRaZHzVuYCsFLp4cdxFbDBYn Ygdl7ZliTpUOuVeaPs/OPS/Nf+qcIxw5w8ARDr1J54G4nbK08/zJO0d14jEfcZyyrDXn S+1A==
X-Gm-Message-State: AMke39no58r2YoEqi/O5F3+O0XMQ/rwFeMpg4T4k8o4BcTeBmyeBklYO6Cvx9FlxfMM+yw==
X-Received: by 10.28.15.142 with SMTP id 136mr19993776wmp.66.1488901380329; Tue, 07 Mar 2017 07:43:00 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id w17sm463362wra.28.2017.03.07.07.42.59 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Mar 2017 07:42:59 -0800 (PST)
Subject: Re: Adding IPv10 to the IETF 98 Agenda.
References: <HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com> <20170307090849.jyl7fqqbn3icjw7a@nic.fr> <CAMm+LwgJg39CFKvxNNPkwC4XUCWPtrSAxTtce34p11UC8E+NyQ@mail.gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <18ee4435-726b-f054-e90b-419409197c11@gmail.com>
Date: Tue, 7 Mar 2017 15:42:57 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAMm+LwgJg39CFKvxNNPkwC4XUCWPtrSAxTtce34p11UC8E+NyQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------2614FC4754C1EA91ADE259F9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eO9saimMAnjuRSJhvWXvNoMIXtc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 15:43:36 -0000

This is a multi-part message in MIME format.
--------------2614FC4754C1EA91ADE259F9
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


>     Good. IETF is too serious. We need a "wild ideas" session, with IPv10,
>     miraculous DNS alternatives, and everything over the blockchain :-)
>
>
It might be interesting to have a wild ideas slot in the form of a 
series of 10 mins
talks. Some of the  ideas might sink, others might trigger better ideas, 
some might
fly, others will be before their time and fly a few years later.

Stewart

--------------2614FC4754C1EA91ADE259F9
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">
    <span class=""></span><br>
    <span class=""></span>
    <blockquote
cite="mid:CAMm+LwgJg39CFKvxNNPkwC4XUCWPtrSAxTtce34p11UC8E+NyQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"><span
                class="">
              </span>Good. IETF is too serious. We need a "wild ideas"
              session, with IPv10,<br>
              miraculous DNS alternatives, and everything over the
              blockchain :-)<br>
              <br>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    It might be interesting to have a wild ideas slot in the form of a
    series of 10 mins<br>
    talks. Some of the  ideas might sink, others might trigger better
    ideas, some might<br>
    fly, others will be before their time and fly a few years later.<br>
    <br>
    Stewart<br>
  </body>
</html>

--------------2614FC4754C1EA91ADE259F9--


From nobody Tue Mar  7 08:19:48 2017
Return-Path: <srdonovan@usdonovans.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B4A012959D for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 07:45:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level: 
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDP_CyhFfx4A for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 07:45:24 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [173.247.247.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77C041295B9 for <ietf@ietf.org>; Tue,  7 Mar 2017 07:45:04 -0800 (PST)
Received: from cpe-97-99-50-102.tx.res.rr.com ([97.99.50.102]:49238 helo=Steves-MacBook-Air.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <srdonovan@usdonovans.com>) id 1clHII-000EXm-77 for ietf@ietf.org; Tue, 07 Mar 2017 07:45:04 -0800
Subject: Re: Review of draft-ietf-dime-load-07
To: ietf@ietf.org
References: <148784049413.20240.15876379956092850264.idtracker@ietfa.amsl.com>
From: Steve Donovan <srdonovan@usdonovans.com>
Message-ID: <0390f072-bf67-d77b-a47f-b76140be81ae@usdonovans.com>
Date: Tue, 7 Mar 2017 09:44:57 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148784049413.20240.15876379956092850264.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srdonovan@usdonovans.com
X-Authenticated-Sender: biz131.inmotionhosting.com: srdonovan@usdonovans.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rcnb9dXn319XEOJuC6X6weutiqo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 15:45:25 -0000

Roni,

Thank you for your review.  Please see my comments inline.

Steve

On 2/23/17 3:01 AM, Roni Even wrote:
> Reviewer: Roni Even
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-dime-load-07
> Reviewer: Roni Even
> Review Date: 2017-02-23
> IETF LC End Date: 2017-02-27
> IESG Telechat date: 2017-03-16
>
> Summary: This draft is almost ready for publication as a standard
> track RFC
>
> Major issues:
>
> Minor issues:
>
> I understand that each node can calculate the load differently , the
> example in figure 8 demonstrate that the agent selection may be
> different if the agent aggregates load from the servers to calculate
> its load or just conveys his load, possibly even that each one of the
> agents will use different method. Why not mandate load calculation
> using aggregated weighted loads?
SRD> The working group thought it was best to leave this as an 
implementation decision.
>
> Nits/editorial comments:
> 1. In section 5 paragraph 9 "The load report includes a value
> indicating the load of the sending
>     node relative load of the sending node, " should be just "The load
> report includes a value indicating the relative load of the sending
> node,"
SRD> Yes, change made.
> 2. In section 6.2 "weigth "
SRD> Change made.
> 3. in the security consideration what about an endpoint in the middle
> changing the host load value causing a change in the routing
> decisions.
SRD> I'm assuming that you mean an agent in the middle changing the host 
value.  I've added the following to the security considerations section 
-- "Given that routing decisions are impacted by load information, there 
is potential for negative impacts on a Diameter network caused by 
erroneous or malicious load reports. This includes the malicious 
changing of load values by Diameter Agents."
>
>
>
>


From nobody Tue Mar  7 08:20:49 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45ECF1295CC for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 07:54:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ElNKzwUWsfZ for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 07:54:14 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BDEF12949B for <ietf@ietf.org>; Tue,  7 Mar 2017 07:53:49 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 14D24280128 for <ietf@ietf.org>; Tue,  7 Mar 2017 16:53:47 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id 0FC152801D8; Tue,  7 Mar 2017 16:53:47 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 09230280128 for <ietf@ietf.org>; Tue,  7 Mar 2017 16:53:47 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 006CE6103EFE for <ietf@ietf.org>; Tue,  7 Mar 2017 16:53:47 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id EDAF641016; Tue,  7 Mar 2017 16:53:46 +0100 (CET)
Date: Tue, 7 Mar 2017 16:53:46 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: The CIA mentions us
Message-ID: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 9.0
X-Kernel: Linux 4.8.0-2-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000520, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.3.7.153916
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QyPVFC3g5yhG7R87OFd47kLgPEM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 15:54:31 -0000

In the Vault7 leak (malware library of the CIA
<https://wikileaks.org/ciav7p1/>), there is a page giving advices to
malware authors: how to avoid leaving traces
<https://wikileaks.org/ciav7p1/cms/page_14587109.html>. Among very
good advices, it talks of the IETF:

DO use ITEF [sic] RFC compliant network protocols as a blending
layer. The actual data, which must be encrypted in transit across the
network, should be tunneled through a well known and standardized
protocol (e.g. HTTPS)

Custom protocols can stand-out to network analysts and IDS filters.


From nobody Tue Mar  7 08:20:54 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE46B1295F0 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:00:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=Ok7UKcNq; dkim=pass (1024-bit key) header.d=yitter.info header.b=WGgrDK7L
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id reCaApTeoKA6 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 07:59:47 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49AD61295D2 for <ietf@ietf.org>; Tue,  7 Mar 2017 07:59:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id AA993BE4B8 for <ietf@ietf.org>; Tue,  7 Mar 2017 15:58:45 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1488902325; bh=HMrUZkiYTRO2iiUyU/xmwjDMCqG95VnKd8i3QQfQ8a0=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Ok7UKcNqdl0VlpbK2okqQi+zfiR1LxjEASZfi36swL/KXzHKdSTVNGMJfkhu9I2qy KezF1nXH4//WbOkkmaRlnFf9cyRnieLjguJ49eDkg5Ubc/aASpJrynU4h2AV5klGfv kStATpyPTBLLYJfrwROPICsridoVtUwtWRStRTtM=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DkGl8r3LHPaD for <ietf@ietf.org>; Tue,  7 Mar 2017 15:58:44 +0000 (UTC)
Date: Tue, 7 Mar 2017 10:58:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1488902324; bh=HMrUZkiYTRO2iiUyU/xmwjDMCqG95VnKd8i3QQfQ8a0=; h=Date:From:To:Subject:References:In-Reply-To:From; b=WGgrDK7LCQSCbS47HiHUxMxQyt8g9j6HIh7vd9ri8z3LL4trknnREN88ohYfw9LlK wMNTCI/OhMqu2rttQcJ26Ia5swGLVeo15fYbdfLoEwNBqBWlkDjZLOIbGnmYDmOn1O /oFcoZrpSPssYF/iNS9LqkVw/ey/6G7rc9RrXssE=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Adding IPv10 to the IETF 98 Agenda.
Message-ID: <20170307155842.GG13753@mx4.yitter.info>
References: <HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com> <20170307090849.jyl7fqqbn3icjw7a@nic.fr> <CAMm+LwgJg39CFKvxNNPkwC4XUCWPtrSAxTtce34p11UC8E+NyQ@mail.gmail.com> <18ee4435-726b-f054-e90b-419409197c11@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <18ee4435-726b-f054-e90b-419409197c11@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Lm8NE5oGai7d7AgFIgRPF6Xt0UM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 16:00:02 -0000

On Tue, Mar 07, 2017 at 03:42:57PM +0000, Stewart Bryant wrote:
> It might be interesting to have a wild ideas slot in the form of a series of
> 10 mins
> talks.

That sounds like a lightning-talks session.  I wonder whether the
plenary would be a good venue for that, or whether that would be too
large an audience?  We might not have to do it every time, but perhaps
this is a suggestion for the IAB technical plenary program to
consider.  What do people think?

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Tue Mar  7 08:21:02 2017
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 6C938129583 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:04:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.668
X-Spam-Level: 
X-Spam-Status: No, score=-1.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybvMNJ53rtBg for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:04:01 -0800 (PST)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F2DD1295C1 for <ietf@ietf.org>; Tue,  7 Mar 2017 08:02:55 -0800 (PST)
Received: by mail-pg0-x236.google.com with SMTP id 25so1991400pgy.0 for <ietf@ietf.org>; Tue, 07 Mar 2017 08:02:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=yzLBXvRAZYnDp6PByuK3Rzec3YocYMXErwrdSe8bvbk=; b=MmT45XF7i3iTTeJ1sBQ4Ixt32P+IDBMfKS20tDzuOoyMbaUZ4EAdVeApqDaLjk5DvN 4yEPMOcGBC2ZJJ3ZIEk9UpfNSP9sgfU08q4kPmTIhJSUesyqNz+rXD8JA1qLg/EhveQG 9ZOn0tQ72ZU8vgMeHbtUwcbIFvBr6KqokLdjrgl1MRJZ8toXrBUOn7XUVJ+eOJqHlkjM DhbbVc/rgTwBbmMli73np7YoLS9E95ipHpUBFHvib+AfCM7qX4GMBeixxWXb/zJFCtAY DADbgGVKINg7LHBuCSBMmJKMi7Ocr4uyKyLvz14fZPEyCediNys1zWDXOuvV6lN94sI3 vbWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=yzLBXvRAZYnDp6PByuK3Rzec3YocYMXErwrdSe8bvbk=; b=fKic8LlSpYZ5Aui+BsKpQ2134OOmKeIOroV3fvJQl5BaR/okdW7zgd5VIuE3o77aTP yAc9X/EzCX/1lBuDSPoSKLutvHA+VJfGzgmshBEMUEYun9V6YRkYyqRa4SgfoHnPW5NF rNY6HzUdaCeGTK0tqoerqJzb/tOwIzQLQgtBrIOP5SONHV0NbJfYdstNiQnLqgsVIuhV Y0En16t5T2tkxn81GQbe7Zvav1592pCQK+Ra0Lk9BABJ6TRRIR1X6mw8wSFQATU8Yg54 7YbO/9PEq1TtDkNN6659EA6oeJznZeVuggRaYm2GUviOw9nKJTh4qAcg1c+668RCL8DL 7iTg==
X-Gm-Message-State: AMke39l8nVwwVYwDjv86nnRGq24JYkibuPDSE11dSsH0E1HVFif6Xtmzcf64/8LPD3HyDnzxWM4tk2fxLjwmnA==
X-Received: by 10.37.45.17 with SMTP id t17mr349139ybt.177.1488902574978; Tue, 07 Mar 2017 08:02:54 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Tue, 7 Mar 2017 08:02:54 -0800 (PST)
In-Reply-To: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 7 Mar 2017 11:02:54 -0500
X-Google-Sender-Auth: PISPCG12nB3aofuRm9CtUy0_0-0
Message-ID: <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com>
Subject: Re: The CIA mentions us
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: multipart/alternative; boundary=94eb2c1b10c8163ba8054a262558
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0NCzJNhfYe2rt_1m7e9wYOWvCdc>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 16:04:03 -0000

--94eb2c1b10c8163ba8054a262558
Content-Type: text/plain; charset=UTF-8

This is all really good advice. I think it should be published as an RFC.

On Tue, Mar 7, 2017 at 10:53 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
wrote:

> In the Vault7 leak (malware library of the CIA
> <https://wikileaks.org/ciav7p1/>), there is a page giving advices to
> malware authors: how to avoid leaving traces
> <https://wikileaks.org/ciav7p1/cms/page_14587109.html>. Among very
> good advices, it talks of the IETF:
>
> DO use ITEF [sic] RFC compliant network protocols as a blending
> layer. The actual data, which must be encrypted in transit across the
> network, should be tunneled through a well known and standardized
> protocol (e.g. HTTPS)
>
> Custom protocols can stand-out to network analysts and IDS filters.
>
>

--94eb2c1b10c8163ba8054a262558
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Thi=
s is all really good advice. I think it should be published as an RFC.</div=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Ma=
r 7, 2017 at 10:53 AM, Stephane Bortzmeyer <span dir=3D"ltr">&lt;<a href=3D=
"mailto:bortzmeyer@nic.fr" target=3D"_blank">bortzmeyer@nic.fr</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">In the Vault7 leak (malware lib=
rary of the CIA<br>
&lt;<a href=3D"https://wikileaks.org/ciav7p1/" rel=3D"noreferrer" target=3D=
"_blank">https://wikileaks.org/<wbr>ciav7p1/</a>&gt;), there is a page givi=
ng advices to<br>
malware authors: how to avoid leaving traces<br>
&lt;<a href=3D"https://wikileaks.org/ciav7p1/cms/page_14587109.html" rel=3D=
"noreferrer" target=3D"_blank">https://wikileaks.org/<wbr>ciav7p1/cms/page_=
14587109.html</a><wbr>&gt;. Among very<br>
good advices, it talks of the IETF:<br>
<br>
DO use ITEF [sic] RFC compliant network protocols as a blending<br>
layer. The actual data, which must be encrypted in transit across the<br>
network, should be tunneled through a well known and standardized<br>
protocol (e.g. HTTPS)<br>
<br>
Custom protocols can stand-out to network analysts and IDS filters.<br>
<br>
</blockquote></div><br></div>

--94eb2c1b10c8163ba8054a262558--


From nobody Tue Mar  7 08:21:20 2017
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 3218C1294C8 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:10:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jYvjiBkFbefC for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:09:49 -0800 (PST)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D81A2129460 for <ietf@ietf.org>; Tue,  7 Mar 2017 08:09:13 -0800 (PST)
Received: by mail-it0-x233.google.com with SMTP id m27so11779079iti.1 for <ietf@ietf.org>; Tue, 07 Mar 2017 08:09:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=JfKdg9CgvOoAGzYr+KCTRJ59aTLCAPtn+OBfKy5kTyc=; b=uLuzx62mhz+KDyvqTPDrAfMISmTCIQtkRqIW2k6P4ENb3dkdkJMIU9Slnt4Nbzfi4+ +LYoj8FtbSvE1cN3HJw3Q2DJCc2VX8CNyUK0EavfEx5LsvobVPbmi+U2i/twcE8qdOVb rfic9J5mhXXJlfRJ5lGYpxfbgHFl1GRqZfmV1Cf4HxKchyN8y/xnnc1ChmFGp9+4Tv3C sb1sRK24QZdRy7SFhZNBR7G31ryCD2OZKR9kSCD2v6KFgF2GsGlN1FPCxiiclHYI7hV5 NxOJIt2AnENINVgRw8MrMDls2lMtg/ZIGhZMnRdKyfmXVNQG2X0L3yxD/l6LsM1pb3T2 /phw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=JfKdg9CgvOoAGzYr+KCTRJ59aTLCAPtn+OBfKy5kTyc=; b=YJ9kp0SueWPNreUPQW4dDpiAWd61E9N9/x6Lzvo0PWR0Sk/kusxc063IuFY3t7D3Ko NRLMV7CMKAbAk00tII+s757FIyGvle/1DY6s9YIUrVwJb1wI5ZqYeILCOvAtIdW2zGd1 FGBxu85/MM50Rc2VNvDqft5d89GjXIDwS03FuoONLNrShrcozSOzrtVf25EG0erwSKfV UCApcWXGyxO8/i6zC/yvQxOr44nma4BeMfDlMMymgtwrVXqDgZFNe+d60yTLWBkjG7M8 yZQqjvXfTFClZ4EpT/0S+qt+a1mEDiCwnPD7xABmfOpe2vUfVM+HmSQiGX2gBMIz39mq KpUQ==
X-Gm-Message-State: AMke39l9Nm/Rh3fnVWXqgj0+BjZLgSlNdI+4umWWcjtYhPD1X+z96gPBhTQdvTAS/ORVf+zjJcikrShfzbbreA==
X-Received: by 10.129.119.130 with SMTP id s124mr384123ywc.202.1488902953075;  Tue, 07 Mar 2017 08:09:13 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Tue, 7 Mar 2017 08:09:12 -0800 (PST)
In-Reply-To: <20170307155842.GG13753@mx4.yitter.info>
References: <HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com> <20170307090849.jyl7fqqbn3icjw7a@nic.fr> <CAMm+LwgJg39CFKvxNNPkwC4XUCWPtrSAxTtce34p11UC8E+NyQ@mail.gmail.com> <18ee4435-726b-f054-e90b-419409197c11@gmail.com> <20170307155842.GG13753@mx4.yitter.info>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 7 Mar 2017 11:09:12 -0500
X-Google-Sender-Auth: 5JvIJ5GelKDummMKuufOjU8MMp4
Message-ID: <CAMm+LwjS5u3XybH3Ps-n4r5rgJr+pT-afqvgkaRDh+tjwQb+Tg@mail.gmail.com>
Subject: Re: Adding IPv10 to the IETF 98 Agenda.
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=001a114903829f9781054a263be6
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ussZOW5R9zU9HamN57ppN2P-oIY>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 16:10:04 -0000

--001a114903829f9781054a263be6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=E2=80=8BI have given lightning talks in several W3C plenaries. They are a =
very
good format for getting many ideas across.

It would be a much better use of plenary time than a lot of things we do.

The ideas do not need to be as wild as 'lets re-engineer protocols in the
narrow waist'. Or they could be the opposite. We might have someone suggest
IPv6 should go on a diet as its waist is not thin enough.




On Tue, Mar 7, 2017 at 10:58 AM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> On Tue, Mar 07, 2017 at 03:42:57PM +0000, Stewart Bryant wrote:
> > It might be interesting to have a wild ideas slot in the form of a
> series of
> > 10 mins
> > talks.
>
> That sounds like a lightning-talks session.  I wonder whether the
> plenary would be a good venue for that, or whether that would be too
> large an audience?  We might not have to do it every time, but perhaps
> this is a suggestion for the IAB technical plenary program to
> consider.  What do people think?
>
> A
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
>

--001a114903829f9781054a263be6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">=E2=
=80=8BI have given lightning talks in several W3C plenaries. They are a ver=
y good format for getting many ideas across.</div><div class=3D"gmail_defau=
lt" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">It would be a much better use of plenary time than a l=
ot of things we do.</div><div class=3D"gmail_default" style=3D"font-size:sm=
all"><br></div><div class=3D"gmail_default" style=3D"font-size:small">The i=
deas do not need to be as wild as &#39;lets re-engineer protocols in the na=
rrow waist&#39;. Or they could be the opposite. We might have someone sugge=
st IPv6 should go on a diet as its waist is not thin enough.</div><div clas=
s=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small"><br></div></div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Tue, Mar 7, 2017 at 10:58 AM, Andrew Sullivan <=
span dir=3D"ltr">&lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_b=
lank">ajs@anvilwalrusden.com</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"><span class=3D"">On Tue, Mar 07, 2017 at 03:42:57PM +0000, Stewar=
t Bryant wrote:<br>
&gt; It might be interesting to have a wild ideas slot in the form of a ser=
ies of<br>
&gt; 10 mins<br>
&gt; talks.<br>
<br>
</span>That sounds like a lightning-talks session.=C2=A0 I wonder whether t=
he<br>
plenary would be a good venue for that, or whether that would be too<br>
large an audience?=C2=A0 We might not have to do it every time, but perhaps=
<br>
this is a suggestion for the IAB technical plenary program to<br>
consider.=C2=A0 What do people think?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
A<br>
<br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
<br>
</font></span></blockquote></div><br></div>

--001a114903829f9781054a263be6--


From nobody Tue Mar  7 08:21:33 2017
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 DBC83129513 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:11:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K9unOy-p6C7l for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:11:16 -0800 (PST)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2809C12952E for <ietf@ietf.org>; Tue,  7 Mar 2017 08:10:37 -0800 (PST)
Received: by mail-io0-x22f.google.com with SMTP id f84so7183489ioj.0 for <ietf@ietf.org>; Tue, 07 Mar 2017 08:10:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=qFLlYfUCBTr1Yqr4LFrdZIzAph7L6/YHBA2RwgAgpEQ=; b=SIXIjNsdbN9qRpp9ZDRPL6nWodw2qfn6OARnCt2U0ZgBRaj2INsS/hi3CmhzbMDtoW CyEPMk6IoNouSCJgc1mZzE3Eqm5mRMm0Uy3mpAFjT7XuQwtYdM69tQlOaHvdOyUnr2rq B5QgzLJhskoXku/nDbtxKzP5bFOw+tJdF4vrhygDUfXlZwvCHk/WgGW8r6WV3XYgRLKJ 1F5YH1EmTVRjjwrPSXpkMfv8+chtr206+X42GOo2Ru6fXmzeIQJH64r10UEE6EmGFeGj x/A6ElGexmeMOCoZ0s9XShC4PFs7LZmIWFIQgVJFNZE7XiKBvn5Dyz61e6fjwZxf5BX8 kSrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=qFLlYfUCBTr1Yqr4LFrdZIzAph7L6/YHBA2RwgAgpEQ=; b=A4iaPfCvNNgIiZzBZDMRD2MVCbSpPCg08chr7G/oPTVRKq+6s6c4Rz7/Id6v9JVZkh gMtgrthaAJz/p3F2SBJlrUnX6Q3oJHeOzK+dBcdlc8suMd3zLTVAXY0rVFXy75AuIYDW ywdxEDXniVI/isqlUC3FXbYqBKWmPq/SOobwdHcGax6g8sIyCeKvvxQBlF1f125ZZuKj waZT2pO7xRiNo3NeEhI6C3TtnKboNSaTRpNYJk9HuSqlMIke4eicPVLkXTSg87WDu2As bCfJkLheK62FEoLQ2bYzemLA25JPQ/YyReZVHPxPwWvEuDJwHU43dod6hwyFyDvjdLYj 8VkA==
X-Gm-Message-State: AMke39mt3yPJeopkAPCXMzRHQubnPyWM8cnOajkj8hoKVK0GA0Yz76HIYUZruvXFpy/CIm/qxFMLGYu6hMBDbQ==
X-Received: by 10.129.163.214 with SMTP id a205mr360687ywh.285.1488903033377;  Tue, 07 Mar 2017 08:10:33 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Tue, 7 Mar 2017 08:10:32 -0800 (PST)
In-Reply-To: <20170307160840.duv7wwg5sm23nrek@nic.fr>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 7 Mar 2017 11:10:32 -0500
X-Google-Sender-Auth: fquULK16BM6EO_k1ztN57E8eyc8
Message-ID: <CAMm+LwibXemfar++GBvaxn5wvMFdnT34OiGp=QykNdEM6wyfXw@mail.gmail.com>
Subject: Re: The CIA mentions us
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: multipart/alternative; boundary=94eb2c12849068dacc054a264040
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NvJJBpvGRR5Ovw9ewOkgvQCGMWc>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 16:11:40 -0000

--94eb2c12849068dacc054a264040
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 7, 2017 at 11:08 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
wrote:

> On Tue, Mar 07, 2017 at 11:02:54AM -0500,
>  Phillip Hallam-Baker <phill@hallambaker.com> wrote
>  a message of 54 lines which said:
>
> > This is all really good advice. I think it should be published as an
> > RFC.
>
> I suspect we may run into IPR problems. The CIA author did not read
> the Note Well.
>

=E2=80=8BIf it was an NSA author they certainly would have=E2=80=8B

--94eb2c12849068dacc054a264040
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">On =
Tue, Mar 7, 2017 at 11:08 AM, Stephane Bortzmeyer <span dir=3D"ltr">&lt;<a =
href=3D"mailto:bortzmeyer@nic.fr" target=3D"_blank">bortzmeyer@nic.fr</a>&g=
t;</span> wrote:<br></div><div class=3D"gmail_extra"><div class=3D"gmail_qu=
ote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">On Tue, Mar 07, 2017 at 11:02:54AM -050=
0,<br>
=C2=A0Phillip Hallam-Baker &lt;<a href=3D"mailto:phill@hallambaker.com">phi=
ll@hallambaker.com</a>&gt; wrote<br>
<span class=3D"">=C2=A0a message of 54 lines which said:<br>
<br>
&gt; This is all really good advice. I think it should be published as an<b=
r>
&gt; RFC.<br>
<br>
</span>I suspect we may run into IPR problems. The CIA author did not read<=
br>
the Note Well.<br>
</blockquote></div><br></div><div class=3D"gmail_extra"><div class=3D"gmail=
_default" style=3D"font-size:small">=E2=80=8BIf it was an NSA author they c=
ertainly would have=E2=80=8B</div><br></div><div class=3D"gmail_extra"><br>=
</div></div>

--94eb2c12849068dacc054a264040--


From nobody Tue Mar  7 08:21:59 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CED6129413 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BdIDQJbZRfr1 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:16:14 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97F9E129503 for <ietf@ietf.org>; Tue,  7 Mar 2017 08:08:41 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 2CEAD280128; Tue,  7 Mar 2017 17:08:40 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id 2733A2801D8; Tue,  7 Mar 2017 17:08:40 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 2077E280128; Tue,  7 Mar 2017 17:08:40 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 1D8FD6042914; Tue,  7 Mar 2017 17:08:40 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id 1AA3041016; Tue,  7 Mar 2017 17:08:40 +0100 (CET)
Date: Tue, 7 Mar 2017 17:08:40 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: The CIA mentions us
Message-ID: <20170307160840.duv7wwg5sm23nrek@nic.fr>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com>
X-Operating-System: Debian GNU/Linux 9.0
X-Kernel: Linux 4.8.0-2-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.3.7.155715
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5d9__oxqnMWT0qKu8MX4JRZL5vM>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 16:16:14 -0000

On Tue, Mar 07, 2017 at 11:02:54AM -0500,
 Phillip Hallam-Baker <phill@hallambaker.com> wrote 
 a message of 54 lines which said:

> This is all really good advice. I think it should be published as an
> RFC.

I suspect we may run into IPR problems. The CIA author did not read
the Note Well.


From nobody Tue Mar  7 08:23:42 2017
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 D471B129503 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0WTpE4E0t56B for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 08:23:37 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08BBB1294B8 for <ietf@ietf.org>; Tue,  7 Mar 2017 08:23:37 -0800 (PST)
Received: from mbp-4.local ([8.18.217.206]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v27GNXFV098353 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 7 Mar 2017 16:23:34 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [8.18.217.206] claimed to be mbp-4.local
Subject: Re: The CIA mentions us
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Phillip Hallam-Baker <phill@hallambaker.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com>
Date: Tue, 7 Mar 2017 08:23:35 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170307160840.duv7wwg5sm23nrek@nic.fr>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EkU6bxRnp9iHM5V7PvW3bGPNPWDMLeRKG"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PeA1HKStCzq0aGsuV4z6dRv4ekY>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 16:23:41 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--EkU6bxRnp9iHM5V7PvW3bGPNPWDMLeRKG
Content-Type: multipart/mixed; boundary="lpvbD79fflvAqMEhHCRiic02CtjRTLlWS";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>,
 Phillip Hallam-Baker <phill@hallambaker.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com>
Subject: Re: The CIA mentions us
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr>
 <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com>
 <20170307160840.duv7wwg5sm23nrek@nic.fr>
In-Reply-To: <20170307160840.duv7wwg5sm23nrek@nic.fr>

--lpvbD79fflvAqMEhHCRiic02CtjRTLlWS
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 3/7/17 8:08 AM, Stephane Bortzmeyer wrote:
> On Tue, Mar 07, 2017 at 11:02:54AM -0500,
>  Phillip Hallam-Baker <phill@hallambaker.com> wrote=20
>  a message of 54 lines which said:
>
>> This is all really good advice. I think it should be published as an
>> RFC.
> I suspect we may run into IPR problems. The CIA author did not read
> the Note Well.
>
https://en.wikipedia.org/wiki/Copyright_status_of_work_by_the_U.S._govern=
ment



--lpvbD79fflvAqMEhHCRiic02CtjRTLlWS--

--EkU6bxRnp9iHM5V7PvW3bGPNPWDMLeRKG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAli+3ogACgkQ8AA1q7Z/VrL18wCbBDy/IKOxo/giBGGn8LdggcL0
NwwAn3BBW9JWXBAsW3+Cvxa40hsSXFK4
=i08q
-----END PGP SIGNATURE-----

--EkU6bxRnp9iHM5V7PvW3bGPNPWDMLeRKG--


From nobody Tue Mar  7 09:54:51 2017
Return-Path: <rg+ietf@randy.pensive.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 824EC129474; Tue,  7 Mar 2017 09:54:46 -0800 (PST)
X-Quarantine-ID: <7YkpsM9pDH0X>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7YkpsM9pDH0X; Tue,  7 Mar 2017 09:54:45 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAA512945A; Tue,  7 Mar 2017 09:54:45 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 7 Mar 2017 09:43:06 -0800
Mime-Version: 1.0
Message-Id: <p06240600d4e4a43fb6cd@[99.111.97.136]>
In-Reply-To: <20633096-1dfa-1c01-9591-3c2fb66efa30@omnitor.se>
References: <148885485450.15073.6095850267163523164.idtracker@ietfa.amsl.com> <20633096-1dfa-1c01-9591-3c2fb66efa30@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Tue, 7 Mar 2017 09:54:42 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, Mahesh Jethanandani <mjethanandani@gmail.com>, ops-dir@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] Review of draft-ietf-slim-negotiating-human-language-08
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zrhUW9qwdIGY7_h-VDHz-flb_lQ>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 17:54:46 -0000

At 11:17 AM +0100 3/7/17, Gunnar Hellstr=F6m wrote:

>>  Finally, it is always helpful to collect information on utilization
>>  from capacity, trend analysis, cost allocation, auditing and billing
>>  perspective.
>  Interesting aspects. Let us see what others say=20
> about what we can include at this stage and=20
> what should be brougth up in follow-up=20
> documents.

This is an operational and implementation issue=20
which is out of scope of the draft.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Isn't it strange that the same people that laugh at gypsy fortune
tellers take economists seriously?


From nobody Tue Mar  7 10:29:31 2017
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 14C6D1294C1 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 10:29:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DEVVSB4m_z-4 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 10:29:29 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 597CB129467 for <ietf@ietf.org>; Tue,  7 Mar 2017 10:29:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D448EBEBB; Tue,  7 Mar 2017 18:29: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 2sDdc0W1QG7Z; Tue,  7 Mar 2017 18:29:26 +0000 (GMT)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 4DDF4BE80; Tue,  7 Mar 2017 18:29:26 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1488911366; bh=i/Pyx2Qjpr41mQXG+qoQNsvJBGLzMVldcsfwkF7FrrU=; h=Subject:To:References:From:Date:In-Reply-To:From; b=v9vc4r4ZQT5F5SXTzlyhn9NfOW5YsnIC0MIBE0di98dc3puvXhgDptDO0yaL2tkj8 QoiR8pxvNhxZmenqMpMZyvrBxEm2KYPs6XjZpRXw1OO8bKPR1iAOV5k9e50ELA5saX PFoJAKkAMLNTz+sSuDEuBQNvCPCZ4k1Q87ysy/hE=
Subject: Re: Adding IPv10 to the IETF 98 Agenda.
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com> <20170307090849.jyl7fqqbn3icjw7a@nic.fr> <CAMm+LwgJg39CFKvxNNPkwC4XUCWPtrSAxTtce34p11UC8E+NyQ@mail.gmail.com> <18ee4435-726b-f054-e90b-419409197c11@gmail.com> <20170307155842.GG13753@mx4.yitter.info>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <0936b875-1c21-1a25-bec9-ef5a3c1d485e@cs.tcd.ie>
Date: Tue, 7 Mar 2017 18:29:25 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <20170307155842.GG13753@mx4.yitter.info>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7SRu560UlqX4gFsOKhLDV1KlAF7953mOm"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oocB_c9LLdw80VWMxp9RtJQ6auA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 18:29:31 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7SRu560UlqX4gFsOKhLDV1KlAF7953mOm
Content-Type: multipart/mixed; boundary="bjBoiaF7kr0bPCHiWVtQVtBnXDhH4vEhh";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Message-ID: <0936b875-1c21-1a25-bec9-ef5a3c1d485e@cs.tcd.ie>
Subject: Re: Adding IPv10 to the IETF 98 Agenda.
References: <HE1PR04MB1449B0672C109C5C2A6AC52CBD2C0@HE1PR04MB1449.eurprd04.prod.outlook.com>
 <20170307090849.jyl7fqqbn3icjw7a@nic.fr>
 <CAMm+LwgJg39CFKvxNNPkwC4XUCWPtrSAxTtce34p11UC8E+NyQ@mail.gmail.com>
 <18ee4435-726b-f054-e90b-419409197c11@gmail.com>
 <20170307155842.GG13753@mx4.yitter.info>
In-Reply-To: <20170307155842.GG13753@mx4.yitter.info>

--bjBoiaF7kr0bPCHiWVtQVtBnXDhH4vEhh
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 07/03/17 15:58, Andrew Sullivan wrote:
> On Tue, Mar 07, 2017 at 03:42:57PM +0000, Stewart Bryant wrote:
>> It might be interesting to have a wild ideas slot in the form of a ser=
ies of
>> 10 mins
>> talks.
>=20
> That sounds like a lightning-talks session.  I wonder whether the
> plenary would be a good venue for that, or whether that would be too
> large an audience?  We might not have to do it every time, but perhaps
> this is a suggestion for the IAB technical plenary program to
> consider.  What do people think?

Not the plenary. Too big an audience for less well developed
ideas, and too scary for many presenters. (And, at a plenary,
there would always be someone excited by any random talk, so
a smaller set of listeners may actually be beneficial for QA
reasons.)

Yes to the idea that the IAB (or IESG) could try a session like
this a couple of times and see how it goes. Put it in a small
room during the normal daytime in parallel with other stuff
and see what happens.

There would need to be a programme ctte or some rules as to
how one gets a slot. If the latter, then I don't like FCFS
as we'd end up with the same presenters too many times if I
know us:-)

S.


>=20
> A
>=20


--bjBoiaF7kr0bPCHiWVtQVtBnXDhH4vEhh--

--7SRu560UlqX4gFsOKhLDV1KlAF7953mOm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYvvwFAAoJEC88hzaAX42iN5MH+wQgnKXb56Hoq14JdG+I+V62
X/fGewfbk7e1KQ1CHbS35AT7XoPYfpEhZWYKpkgoIFs2HznIy8m2WAThNrYLY9wG
0SafjeNLRCOyVOYDnIE6+LuAemCuWh86mlQxZezs6Fvkpndue/71ITWp0BH3USbO
iITc0CUYDxiQNinQ+tpAxge7ls9ebT70IyPH5OQ2vXFeSTxMXNj8GCivYXedKNWU
Po9HTU19ritzERKeSPrXFkC4bSaExyWD6IuuHTdx6jCOGhci28rKMrL7RfkCJcHU
PJoVjk5LEOM4GXC/jTFL6oOoqNuaqf1GNh4UCuN1DdEjiOwmJ3Yooyg9+oX706A=
=7ItH
-----END PGP SIGNATURE-----

--7SRu560UlqX4gFsOKhLDV1KlAF7953mOm--


From nobody Tue Mar  7 10:32:14 2017
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 8624E1294C1 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 10:32:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSloprSLdPCz for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 10:32:11 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 446DA1294AA for <ietf@ietf.org>; Tue,  7 Mar 2017 10:32:11 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id BFB6E80A38; Tue,  7 Mar 2017 19:32:07 +0100 (CET)
Subject: Re: The CIA mentions us
To: joel jaeggli <joelja@bogus.com>, Stephane Bortzmeyer <bortzmeyer@nic.fr>,  Phillip Hallam-Baker <phill@hallambaker.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com>
Date: Tue, 7 Mar 2017 14:40:11 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U22AhWmQippLcdpgeMugw3nI0V4>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 18:32:13 -0000

On 03/07/2017 01:23 PM, joel jaeggli wrote:
> On 3/7/17 8:08 AM, Stephane Bortzmeyer wrote:
>> On Tue, Mar 07, 2017 at 11:02:54AM -0500,
>>  Phillip Hallam-Baker <phill@hallambaker.com> wrote 
>>  a message of 54 lines which said:
>>
>>> This is all really good advice. I think it should be published as an
>>> RFC.
>> I suspect we may run into IPR problems. The CIA author did not read
>> the Note Well.
>>
> https://en.wikipedia.org/wiki/Copyright_status_of_work_by_the_U.S._government

Well... one would still need to assess whether such work is official or
not. :-)  At times, intelligence agency's work is not official --
actually, officially, such work didn't happen. :-)

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Mar  7 10:35:35 2017
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 85BFE1294A8 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 10:35:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ClNQPY_uxTv for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 10:35:32 -0800 (PST)
Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BEED12948C for <ietf@ietf.org>; Tue,  7 Mar 2017 10:35:32 -0800 (PST)
Received: from pure.maildistiller.com (unknown [10.110.50.25]) by dispatch1-us1.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTP id C877B800D9; Tue,  7 Mar 2017 18:35:26 +0000 (UTC)
X-Virus-Scanned: Proofpoint Essentials engine
Received: from mx4-us4.ppe-hosted.com (unknown [10.110.49.250]) by pure.maildistiller.com (Proofpoint Essentials ESMTP Server) with ESMTPS id 923F560055; Tue,  7 Mar 2017 18:35:26 +0000 (UTC)
Received: from xpasc.com (96-82-113-225-static.hfc.comcastbusiness.net [96.82.113.225]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx4-us4.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id B6DF26006D; Tue,  7 Mar 2017 18:35:16 +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 v27IZFYx022913; Tue, 7 Mar 2017 10:35:15 -0800
Date: Tue, 7 Mar 2017 10:35:15 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: The CIA mentions us
In-Reply-To: <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com>
Message-ID: <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-MDID: 1488911726-6sulRLd19bMw
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C9IEIzyeHEg1ptd8DJ0zGo6rJM8>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 18:35:34 -0000

On Tue, 7 Mar 2017, Fernando Gont wrote:

> On 03/07/2017 01:23 PM, joel jaeggli wrote:
> > On 3/7/17 8:08 AM, Stephane Bortzmeyer wrote:
> >> On Tue, Mar 07, 2017 at 11:02:54AM -0500,
> >>  Phillip Hallam-Baker <phill@hallambaker.com> wrote
> >>  a message of 54 lines which said:
> >>
> >>> This is all really good advice. I think it should be published as an
> >>> RFC.
> >> I suspect we may run into IPR problems. The CIA author did not read
> >> the Note Well.
> >>
> > https://en.wikipedia.org/wiki/Copyright_status_of_work_by_the_U.S._government
>
> Well... one would still need to assess whether such work is official or
> not. :-)  At times, intelligence agency's work is not official --
> actually, officially, such work didn't happen. :-)

Yeah, leaked classified materials don't need a copyright for protection.
One can go to jail with out ever getting a chance to discuss copyright
status.


From nobody Tue Mar  7 10:47:28 2017
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 340691294A8 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 10:47:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ycb_pLUUwUsu for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 10:47:26 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0EB0129467 for <ietf@ietf.org>; Tue,  7 Mar 2017 10:47:25 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 2497F8074B; Tue,  7 Mar 2017 19:47:20 +0100 (CET)
From: Fernando Gont <fgont@si6networks.com>
Subject: Re: The CIA mentions us
To: David Morris <dwm@xpasc.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com>
Message-ID: <f9546015-ea7d-b23e-f68c-cb6243c6d181@si6networks.com>
Date: Tue, 7 Mar 2017 15:41:39 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZEokHYqNJ8nbd39YRSssL7u_tKI>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 18:47:27 -0000

On 03/07/2017 03:35 PM, David Morris wrote:
>>>>
>>> https://en.wikipedia.org/wiki/Copyright_status_of_work_by_the_U.S._government
>>
>> Well... one would still need to assess whether such work is official or
>> not. :-)  At times, intelligence agency's work is not official --
>> actually, officially, such work didn't happen. :-)
> 
> Yeah, leaked classified materials don't need a copyright for protection.
> One can go to jail with out ever getting a chance to discuss copyright
> status.

One should consider oneself lucky in that case ;-)

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Mar  7 11:10:58 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8571B12949F for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 11:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.505
X-Spam-Level: *
X-Spam-Status: No, score=1.505 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_96_XX=3.405] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KuT5QSsDQqGS for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 11:10:47 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 396CF129420 for <ietf@ietf.org>; Tue,  7 Mar 2017 11:10:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 8739C300448 for <ietf@ietf.org>; Tue,  7 Mar 2017 14:10:46 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id nGiPxF2X-dlF for <ietf@ietf.org>; Tue,  7 Mar 2017 14:10:45 -0500 (EST)
Received: from russellsleysmbp.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 7F4123002C1 for <ietf@ietf.org>; Tue,  7 Mar 2017 14:10:45 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20170209223951.GW28349@mournblade.imrryr.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <25454827-48CD-4268-A44E-35ECB67C0BCE@vigilsec.com>
References: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org> <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com> <20170209223951.GW28349@mournblade.imrryr.org>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5hO8laaZFxln5tTNoGGzbU64jjQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Date: Tue, 07 Mar 2017 19:10:50 -0000
X-Original-Date: Thu, 9 Feb 2017 19:06:18 -0500
X-List-Received-Date: Tue, 07 Mar 2017 19:10:50 -0000

Viktor:

[bottom posting]

>=20
>> RFC 5280 says:
>>=20
>> A name constraint for Internet mail addresses MAY specify a
>> particular mailbox, all addresses at a particular host, or all
>> mailboxes in a domain.  To indicate a particular mailbox, the
>> constraint is the complete mail address.  For example,
>> "root@example.com" indicates the root mailbox on the host
>> "example.com".  To indicate all Internet mail addresses on a
>> particular host, the constraint is specified as the host name.  For
>> example, the constraint "example.com" is satisfied by any mail
>> address at the host "example.com".  To specify any address within a
>> domain, the constraint is specified with a leading period (as with
>> URIs).  For example, ".example.com" indicates all the Internet mail
>> addresses in the domain "example.com", but not Internet mail
>> addresses on the host "example.com=E2=80=9D.
>>=20
>> I think you are talking about constraints on addresses at a =
particular
>> host and constraints on mailboxes in a domain, but not constraints on =
a
>> particular mailbox.  Please correct me is I got that wrong.
>=20
> Primarily, but not exclusively.  In the case that an issuer CA is
> constrainted to a specific rfc822Name, it should not be possible
> to evade that constraint by using the same (all-ASCII) address as
> an SmtpUtf8Name.
>=20
>> I think you are suggesting that any A-label in the rfc822Name be =
converted
>> to a U-label, and the result is used to constrain the SmtpUtf8Name.
>=20
> No.  I am *not* suggesting *any* conversions.  If a CA has rfc822Name
> constraints and no SmptUtf8Name constraints, and the rfc822Name
> constraints limit the CA to "example.com", ".example.com", or as
> you suggest above, a particular set of explicit rfc822Name addresses,
> my suggestion is that it MUST NOT be able to issue SmtpUtf8Name =
altnames
> that violate those constraints.  For example:
>=20
> * CA is constrained to permitted subtree rfc822Name: example.com
> 	- can issue SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@exam=
ple.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, the second
> is a clear violation of the principle of least surprise (and the
> policy of the parent CA that created the name constraint).
>=20
>> If people like your suggestion, then a constraint for a particular =
mailbox
>> will still require a SmtpUtf8Name, so I think the mechanism described =
in
>> the draft is needed.  It would just be used in combination with the =
above.
>=20
> As to particular addresses, again:
>=20
>=20
> * CA is constrained to permitted subtree rfc822Name: =
viktor@example.com
> 	- cannot SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@example=
.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, in clear
> violation of the name constraint on the permitted email addresses.


Wei is arguing that the two (ffc822Name and SmtpMUtf8Name) should be =
completely separate.

You are arguing for some crossover, but I do not understand how A-labels =
in the rfc822Name are handled in your proposal.

If rfc822Name permits 'xn--fa-hia.de=E2=80=99 then it would need to be =
translated to 'fa=C3=9F.de=E2=80=99 for comparison in SmtpUtf8Name.

Russ


From nobody Tue Mar  7 11:26:30 2017
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 C483A12940F for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 11:26:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JGkyEh1-iXI7 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 11:26:27 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE764129426 for <ietf@ietf.org>; Tue,  7 Mar 2017 11:26:27 -0800 (PST)
Received: from [128.9.184.171] ([128.9.184.171]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v27JQ7N6001978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Mar 2017 11:26:07 -0800 (PST)
Subject: Re: More haste, less speed.
To: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
References: <CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <709c9dc3-82a7-55f8-8357-e0626b4dab32@isi.edu>
Date: Tue, 7 Mar 2017 11:26:06 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------62A8F08CFCB555D3A59AB560"
X-MailScanner-ID: v27JQ7N6001978
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4VCPYgEQjdVuvBNSA95wpC76jhI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 19:26:29 -0000

This is a multi-part message in MIME format.
--------------62A8F08CFCB555D3A59AB560
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit



On 3/6/2017 8:27 AM, Phillip Hallam-Baker wrote:
> Specifications are moving through IETF faster than ever. Rarely is the
> question asked, is this actually a good thing.

FWIW, I have been a proponent of "less is more". The forest of RFCs we
publish don't help implementers find what's important, and many often
conflict with each other (even within the BCP and standards-track).

Documents in last call should, IMO, need sufficient positive support to
move forward. Even after a WG has adopted a doc, we should still be able
to say "no" to a doc, not just "no objection".

Joe

--------------62A8F08CFCB555D3A59AB560
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 3/6/2017 8:27 AM, Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote
cite="mid:CAMm+Lwg1dvzMSKbWwoF0V6ZM5Q5_WVYxvpV=4_u=T0OTjCPxPQ@mail.gmail.com"
      type="cite">
      <div class="gmail_default" style="font-size:small">Specifications
        are moving through IETF faster than ever. Rarely is the question
        asked, is this actually a good thing.</div>
    </blockquote>
    <br>
    FWIW, I have been a proponent of "less is more". The forest of RFCs
    we publish don't help implementers find what's important, and many
    often conflict with each other (even within the BCP and
    standards-track).<br>
    <br>
    Documents in last call should, IMO, need sufficient positive support
    to move forward. Even after a WG has adopted a doc, we should still
    be able to say "no" to a doc, not just "no objection".<br>
    <br>
    Joe<br>
  </body>
</html>

--------------62A8F08CFCB555D3A59AB560--


From nobody Tue Mar  7 11:33:18 2017
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 170EA1294B4 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 11:33:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vOD_BcEb9OP for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 11:33:15 -0800 (PST)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBA9A1294AC for <ietf@ietf.org>; Tue,  7 Mar 2017 11:33:15 -0800 (PST)
Received: by mail-pf0-x241.google.com with SMTP id o126so1070505pfb.1 for <ietf@ietf.org>; Tue, 07 Mar 2017 11:33:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=uAUyyo8/xql4NJWV2Krp2zL5YivzrCRTVkyBx/K61ws=; b=B1xGdIblbS2UwDnld7hyMynDnT/Pen9t10O02zdvTeoqkbj36qt3AmwjqiqjxWqQdW VszaP2Q3rLk66eQjPXuK6hW9yBcMY+6hLKBkx3jcnRSw4BzK3flt2PvFkbCWJBX8EVuo lL6RPk5t+pDGR5BsA79SsVvGF7M6zVKRGd1ExXYAdR2Lno8VRRcw+guXLE/48+dplJnP bFwOnTvb9wghLoI23GTt7brAtz3cdhOPHylGbCkyP9zQxJHRb5Bg8UaYbZIRa84bVipW KKgdhsYUVRoa2yGM863F7R4msMwflwPkrESBO8aj24d2umA0pCdF4gmL6QQFfhHmKBJJ ZFMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=uAUyyo8/xql4NJWV2Krp2zL5YivzrCRTVkyBx/K61ws=; b=ixoeaIpWkiQJGlghIKpTrw+T6tTMnkVWBeX/eNdS30EOoz+wI+GMV5AMb552//Q4aL uIiCRyEtC4lCbxyDurZpy7SCLmkk1ZwdK1E7O2vbUESKZJu2HN+RCT16UTVHZfmEdJyo FS951/24tUZJvdAymSoO8RbkeVYc9LqtO3LtKEyOU6QnCQ08zahgSjwgm7PTe/DhtTHt NJY0wk3B14fHqOo+pLAUWJVQmOnc9rqzu/U6cdKWCK+T6ViN1yaVRO5KFG9IdDJ3bPIs ZnObw4YleB/LQP7vC4Z1PAm8NauEMU1AL6nKjmWUk++h8Qge1QBF0X7HdyjtCtdnyI78 P+cw==
X-Gm-Message-State: AMke39kISmGPC1aCefxUxn5SsDbFPVJQUCQzmplL14wx03QhM0S1i1Vxwrnw/DNEshI2FQ==
X-Received: by 10.84.241.201 with SMTP id t9mr2851578plm.18.1488915195221; Tue, 07 Mar 2017 11:33:15 -0800 (PST)
Received: from ?IPv6:2406:e007:77b4:1:28cc:dc4c:9703:6781? ([2406:e007:77b4:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id s13sm1366680pfd.46.2017.03.07.11.33.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Mar 2017 11:33:14 -0800 (PST)
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Eric Rescorla <ekr@rtfm.com>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com> <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com> <CABcZeBPH6Y+EdbSfPMH-Rs_k5ZDwKb=13ZOGcWbi_TYJpdpsBQ@mail.gmail.com> <480b22e4-bf25-01fa-87fe-f91bc68940f8@gmail.com> <CABcZeBNuXUypKkDwY1PXzfpTub+=OhTLBLfdEiwNPaBdKuP12g@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <2e88da54-18ad-e96c-f76c-29a0470404c9@gmail.com>
Date: Wed, 8 Mar 2017 08:33:14 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBNuXUypKkDwY1PXzfpTub+=OhTLBLfdEiwNPaBdKuP12g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wXM-LPPSHI7aKChf1npWf0g7utU>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 19:33:17 -0000

On 07/03/2017 17:28, Eric Rescorla wrote:
> On Mon, Mar 6, 2017 at 8:20 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> On 07/03/2017 17:06, Eric Rescorla wrote:
>>> On Wed, Mar 1, 2017 at 11:24 AM, Brian E Carpenter <
>>> brian.e.carpenter@gmail.com> wrote:
>>>>
>>>>> I'm not arguing against updating data tracker more often - just saying
>>>> this
>>>>> 'editor's draft' convention can work very well between official
>> revisions
>>>>> no matter the cadence a WG chooses.
>>>>
>>>> The details of that discussion probably belong on
>> ietf-and-github@ietf.org
>>>> ,
>>>> but I must point out that this way of working *excludes* from the
>>>> discussion WG participants who don't grok github. Substantial issues
>>>> need to be discussed on the mailing list and substantial (non-typo)
>>>> revisions need to be posted as I-Ds.
>>>>
>>>
>>> Well, it's hard to know what to make of this without knowing what you
>>> mean by "substantial" but an active draft takes literally hundreds of PRs
>>> in its lifetime with perhaps half of those being non-typos. We could of
>>> course gateway every PR merge to an IETF draft push. Is that what you're
>>> looking for?
>>
>> No. In fact (countering Michael's point slightly) I get quite annoyed
>> by draft versions that turn out only to fix few typos or grammatical
>> errors;
>> those can wait. As for what constitutes "substantial", that's very
>> subjective.
>> Anything that causes an on-the-wire protocol change would certainly be
>> substantial. Clarifying ambiguous text might be substantial. But YMMV.
>>
> 
> But this would still lead to a colossal number of drafts. 

I realised when reading your reply that it depends a lot
on what stage the draft has reached. In the early phases,
you're right of course. There could be many protocol changes
in quick succession, and they should be bundled up. My comment
was over-influenced by a draft I'm currently editing, where
IETF Last Call has led to a couple of minor on-the-wire changes.
At this stage, they are definitely significant and require a
new version (but even so, they will be bundled with numerous
editorial updates).

<snip>

> As you can see, we have an average of 5 wire-level changes per revision,

I have data for draft-ietf-anima-grasp, since I started logging
protocol changes at version 02. The average is about 3 per revision.
So maybe we are in fact agreeing violently.

    Brian


From nobody Tue Mar  7 12:37:28 2017
Return-Path: <alex@strugee.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 84AB5129577 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 12:37:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CPo5P_44nryc for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 12:37:25 -0800 (PST)
Received: from steevie.strugee.net (strugee.net [216.160.72.225]) by ietfa.amsl.com (Postfix) with ESMTP id 7493A129540 for <ietf@ietf.org>; Tue,  7 Mar 2017 12:37:25 -0800 (PST)
Received: from localhost (unknown [207.251.103.46]) by steevie.strugee.net (Postfix) with ESMTPSA id A42E276E369; Tue,  7 Mar 2017 12:37:23 -0800 (PST)
Date: Tue, 7 Mar 2017 15:37:19 -0500
From: Alex Jordan <alex@strugee.net>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Interest in a push-based two-factor auth standard?
Message-ID: <20170307203719.GB6276@Alexs-MacBook-Pro>
References: <20170302055128.GJ12470@Alexs-MacBook-Pro> <CAMm+Lwg_kAtYUGivYSF5ZzF5nfywS4rzYG88UEzxgjRL2_=83Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="FkmkrVfFsRoUs1wW"
Content-Disposition: inline
In-Reply-To: <CAMm+Lwg_kAtYUGivYSF5ZzF5nfywS4rzYG88UEzxgjRL2_=83Q@mail.gmail.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QojLXlqlhIaXu5TlSoXyPiUpTUc>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 20:37:26 -0000

--FkmkrVfFsRoUs1wW
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 06, 2017 at 08:05:11AM -0500, Phillip Hallam-Baker wrote:

> What we are discussing goes beyond two factor auth. If you have a cell
> phone with a device specific signature key, it can sign the response which
> means that you automatically collect up a non repudiable audit log of the
> user's actions. This is beyond anything possible with OTP number sequences
> or USB dongles.

Indeed. I suspect there are a lot of unexplored uses for such a
standard, but haven't explored it fully yet. (Note also that the lack
of deniability could be seen as a positive thing _or_ a negative
thing, depending.)

> =E2=80=8Bi am interested and have developed several protocols of this typ=
e using
> JSON. My work provides prior art back to 2010 at the very least.

Are there any public references for this work?

I think what makes most sense at this point is for me to draw up a
rough Internet draft and then send it to the Security area and see
what they think the best way forward is. Looking at prior work will
probably aid in the design of such a draft.

Does that seem okay to those who have expressed interest in this?

Cheers!

AJ

--FkmkrVfFsRoUs1wW
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJ8BAEBCgBmBQJYvxn/XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRERDMyMDZGODZEQ0VFMjMzQ0MwOUQ3NDgy
Njc5NDAzNDYzM0RCQkMwAAoJECZ5QDRjPbvAaNQQAOCGKuxmINRMuszKPZ55nAIe
JJ4I9K6twpkFT0sQ0DurGcGXdKfmZhGr1K3vGrtTG6YdEDfKoRXBCCO2XM5I/r0w
G37Sxm6Kui0XrxgPKXLlv+DJOZ0xvN3L3ueOxiJy9ytWPinDwgqbhs4D9+PnEEEJ
iIiVidO0SL/TxoydS/kieGTzcYJNuo0WaA3daVZfXZvGMyarykrdbEVZ4QMC+Dn7
zN9aOijrToA4JSeQKItpJ6fNtGgTvahd39GNrJhzh+VMvNU/bIkJCR2bAD+H51y1
dlh35UI5YA9pNZnNXEUVOUrFXDRdDjF2outJ8y6je0ToJKhIeeqafGxodIkaMirc
Jz1jhiKZ5Itte1kohDYbsagTKRLTTXH0R9aolOLtfLbDSGm0kpgLTyHRB1xe5SOk
6RSOoXgWmLnsbpiU73ESuAqfs+sz820hOX+bQhdgB0ByX1U0tHevTlzlUYxBMGF4
jBeX7Np+Nd8aVPx9YpThKYHhLTudUaD1+uWWuf7z9DQE1x2vuDKE4pDB8SeDrSNr
S81AmIrwXRrXpT2Of1OyVF9CKNyT04d42ECmGR4dEYHglTfTOB9ePFPAfuC8xwng
vAS+FIG+gnlYiEdSgMyUuYALk80ylRCzka8JG6HzZ5X54XjngajC3rYJ7Xw+K6il
LTABaIybF6QgDOwFVYLI
=GtK5
-----END PGP SIGNATURE-----

--FkmkrVfFsRoUs1wW--


From nobody Tue Mar  7 13:16:22 2017
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 722F212946F; Tue,  7 Mar 2017 13:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1RwweeXfmCo0; Tue,  7 Mar 2017 13:16:19 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E59C1293F5; Tue,  7 Mar 2017 13:16:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id CA3A8BEFA; Tue,  7 Mar 2017 21:16: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 fXMsBbfmUTrl; Tue,  7 Mar 2017 21:16:15 +0000 (GMT)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1DE39BF02; Tue,  7 Mar 2017 21:16:11 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1488921371; bh=FCvE+9rhp8dJcrXTpKf2x7YtOA9hpZCbx5zZUQr8LxQ=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=QbAY+GuIuVmqPO/jPGn8kJozS4kzkdh+dDoPIAnWz+aq7zVFTRlJ04W1QNMQbBuMT ke9tCryNoJ6Jp1bw4ezYn79tSZ7SAT7UAEy0Q07jxY5Rjtzxc5gnwb+4OzE1fNr8lh BES91swYr3HTPTSxwVXch9z4Jpm76jtyoJimDBDc=
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
To: mohamed.boucadair@orange.com, Ted Hardie <ted.ietf@gmail.com>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com> <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup> <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com> <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup> <cebf0487-2d71-ea1e-5dd9-cf1d8c80df3a@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E1D615@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <d9827c93-9848-6d54-a9e8-c759d2d2a1de@cs.tcd.ie>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <b730e510-a960-73d0-881a-315813a7c14a@cs.tcd.ie>
Date: Tue, 7 Mar 2017 21:16:10 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <d9827c93-9848-6d54-a9e8-c759d2d2a1de@cs.tcd.ie>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pmbHBpDOBw3NAWC6Ah9IRW3aeTEF3WmmN"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CObu8qwAHkLNzR-YN71DTI68S7E>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 21:16:21 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--pmbHBpDOBw3NAWC6Ah9IRW3aeTEF3WmmN
Content-Type: multipart/mixed; boundary="TlKJtQbeDCRFjhHhC1dFe9e7jv21XaVkx";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: mohamed.boucadair@orange.com, Ted Hardie <ted.ietf@gmail.com>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org"
 <draft-hardie-privsec-metadata-insertion@ietf.org>,
 "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <b730e510-a960-73d0-881a-315813a7c14a@cs.tcd.ie>
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt>
 (Design considerations for Metadata Insertion) to Informational RFC
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com>
 <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E1B2E6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMBATNM9VAAoRVzAPrvshqeAkNjL_VA_Bwz_JhU75DTRiA@mail.gmail.com>
 <787AE7BB302AE849A7480A190F8B933009E1BDA0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <CA+9kkMAMBaq7p4t88T=Rvkg3Qr+wRaGxfPHnKAj7eReWq2Unkw@mail.gmail.com>
 <68cef6ce-f517-4b36-ae91-cc82c6fa4465@OPEXCLILM42.corporate.adroot.infra.ftgroup>
 <CA+9kkMD7p70mPp1ta1L1Zy7sDN9_=3zrFr=3nfbK8Wyb0C-fOg@mail.gmail.com>
 <a9787ef7-734b-49a4-8590-b793272893d7@OPEXCLILM5C.corporate.adroot.infra.ftgroup>
 <cebf0487-2d71-ea1e-5dd9-cf1d8c80df3a@cs.tcd.ie>
 <787AE7BB302AE849A7480A190F8B933009E1D615@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <d9827c93-9848-6d54-a9e8-c759d2d2a1de@cs.tcd.ie>
In-Reply-To: <d9827c93-9848-6d54-a9e8-c759d2d2a1de@cs.tcd.ie>

--TlKJtQbeDCRFjhHhC1dFe9e7jv21XaVkx
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 07/03/17 13:07, Stephen Farrell wrote:
>> I checked the SAAG archives, but, unless I'm mistaken, I failed to
>> find a technical discussion about the content of the draft or a
>> thread about "fairly clear support" to "progressing this draft".
> It was entwined a bit with the 3552bis discussion. Don't have time
> at the 'mo to dig out references but happy to do that later.
>=20

Sorry to not have had time earlier, but the saag threads for
this are at [1,2] and a bit of [3]. As I said the meat of this
draft was envisaged to be included in a 3552bis, but the latter
has so far not progressed. (IOW, one needs to hunt down the
discussion a bit, sorry;-)

Cheers,
S.

[1] https://www.ietf.org/mail-archive/web/saag/current/msg07452.html
[2] https://www.ietf.org/mail-archive/web/saag/current/msg07096.html
[3] https://www.ietf.org/mail-archive/web/saag/current/msg07117.html


--TlKJtQbeDCRFjhHhC1dFe9e7jv21XaVkx--

--pmbHBpDOBw3NAWC6Ah9IRW3aeTEF3WmmN
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYvyMaAAoJEC88hzaAX42iIboH/2+eGNV8zzA44doJ1HTHMnua
bq27zGTa66uSn1ty0R8DwxdUHPYskuHsK0TZBlZlDAya0bYYsmj5g3bTmIEFTipQ
R3XVqve/M83uW6F7y0YBBEgjQ8xnPQLwPqgkwH0g0rXllvQUqIYyZEbs/U5hNOAG
2KRONlZPqkVAjO82Zj6x5lnad2FPyDpxChlOOuXBvN0+o5WgbI6rJStzZfNLdTAu
MfSRd8/rk775imDaV0o6vXPr+1+RPClhll/hySF+J7S8oRh5pkwu3+XveM2DOBmg
hhcOFbnzQLbV7BpWVqCAcMY+FmufwJGe8ZUqbzl2ODOwiofwiLQNlU/6AycSAI4=
=G/zi
-----END PGP SIGNATURE-----

--pmbHBpDOBw3NAWC6Ah9IRW3aeTEF3WmmN--


From nobody Tue Mar  7 14:18:14 2017
Return-Path: <ietf-dane@dukhovni.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 B896C12960D for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 14:18:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vosJHt3I-8i for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 14:18:11 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B746129630 for <ietf@ietf.org>; Tue,  7 Mar 2017 14:18:01 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 93D577A32D8 for <ietf@ietf.org>; Tue,  7 Mar 2017 22:18:00 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <25454827-48CD-4268-A44E-35ECB67C0BCE@vigilsec.com>
Date: Tue, 7 Mar 2017 17:17:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A84C7A12-2B68-4A2E-AB3B-85811023AF90@dukhovni.org>
References: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org> <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com> <20170209223951.GW28349@mournblade.imrryr.org> <25454827-48CD-4268-A44E-35ECB67C0BCE@vigilsec.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UI80qs6HFDDCeNbJgZm1oyD6gvE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Mar 2017 22:18:13 -0000

> On Feb 9, 2017, at 7:06 PM, Russ Housley <housley@vigilsec.com> wrote:
>=20
>=20
> Wei is arguing that the two (ffc822Name and SmtpMUtf8Name) should be =
completely separate.
>=20
> You are arguing for some crossover,

I am not arguing for "some crossover", I am arguing to stop bypass =
attacks
when rfc822Name constraints are specified by a (legacy) CA, and =
SmtpUtf8Name
constraints are not.

Anything that prevents the creation of SmtpUt8Name entries that violate =
the
intent of the rfc822Name constraints is sufficient.  In particular, it =
is
not absolutely necessary to allow "fa=C3=9F.de" to be used via a =
name-constained
legacy certificate.  The most recently proposed compromise was to just =
ban
all SmtpUtf8Name altnames when rfc822Name constraints are set, with no
corresponding SmtpUtf8Name constraints.

> but I do not understand how A-labels in the rfc822Name are handled in =
your proposal.

No special treatment, just disallow bypass via use of unconstrained =
SmtpUtf8Name.

> If rfc822Name permits 'xn--fa-hia.de=E2=80=99 then it would need to be =
translated to 'fa=C3=9F.de=E2=80=99 for comparison in SmtpUtf8Name.

Simplest to avoid translation, and just deny.

--=20
	Viktor.


From nobody Tue Mar  7 16:02:41 2017
Return-Path: <suresh.krishnan@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 4E90F129516; Tue,  7 Mar 2017 16:02:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MA-vKLPOZ6e2; Tue,  7 Mar 2017 16:02:34 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E7E0129489; Tue,  7 Mar 2017 16:02:34 -0800 (PST)
X-AuditID: c6180641-c3fff70000000a06-d5-58bf03c15d30
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id 79.ED.02566.1C30FB85; Tue,  7 Mar 2017 20:02:28 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0319.002; Tue, 7 Mar 2017 19:02:30 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Susan Hares <shares@ndzh.com>
Subject: Re: Review of draft-ietf-6man-rfc1981bis-04
Thread-Topic: Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSlQrd5BFYuQiyL06FWZtjocLrOqGI8MuAgAAj+oCAAVN9gA==
Date: Wed, 8 Mar 2017 00:02:30 +0000
Message-ID: <31B447FF-6D4D-4D2A-BD25-FB93D58B08E6@ericsson.com>
References: <148864769030.23464.9110014115039938058.idtracker@ietfa.amsl.com> <FD5C174D-080B-4D59-88EB-ADE08AAA2D73@gmail.com> <00fb01d296f5$85c57570$91506050$@ndzh.com>
In-Reply-To: <00fb01d296f5$85c57570$91506050$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_A7DE507A-13D0-4DF8-9820-AA1A7A2ED685"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDIsWRmVeSWpSXmKPExsUyuXRPgu4R5v0RBjcXCFlsfb+PzeLY2tcs Fs82zmexeHn2PZNFb9MSZos/b16xOLB57Jx1l91jyZKfTB6zX19nDWCO4rJJSc3JLEst0rdL 4MrYeeM+S8Fl64pV0w6xNDDOMu9i5OSQEDCReHPpK1sXIxeHkMB6RonZr/ezQjjLGCXmXZjC AlLFBlS1YednJhBbREBR4sjVdewgRcwCNxklOi4tYQVJCAMVTZsziRmiyFTi5Pqr7BC2k8Tj o5fYQGwWARWJfxePgQ3iFbCXODr9GjvEtrWMEst/32YESXAKmEuc3HwRrIFRQEzi+6k1YA3M AuISt57MZ4K4W0Ti4cXTbBC2qMTLx/9YIWwliTmvrzFDXDeFUWLR5qXMENsEJU7OfMIygVFk FpJZs5DVzUJSB1GkLbFs4WugOAeQrSMxeSEjRNhU4vXRj1C2tcSMXwfZIGxFiSndD9kXMHKs YuQoLS7IyU03MtzECIzHYxJsjjsY9/Z6HmIU4GBU4uHdMGlfhBBrYllxZe4hRhWg1kcbVl9g lGLJy89LVRLhbbfcHyHEm5JYWZValB9fVJqTWnyIUZqDRUmc93rI/XAhgfTEktTs1NSC1CKY LBMHp1QDo8Pm3Ya63+5wTNWKrFkqzHih6VFN26H8JYtFw31Ftp24KXXtWcZnm5YN28yOu2jc u91u8O3tXo6VJ1++3cfxXz/mVgyvXKTEhRf8RnblNX+/l7gIV8UdXRSfJnNjr5XHpSR5PoEt C8ymXHAKdn523oEpJeufuJTuxKtM+455hZ05X2j6U6tMVomlOCPRUIu5qDgRAChfW6HPAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EF2gRwgAyPqQz6M9YK1kZb26nZU>
Cc: 6man WG <ipv6@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, Robert Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 00:02:36 -0000

--Apple-Mail=_A7DE507A-13D0-4DF8-9820-AA1A7A2ED685
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Sue,
  Thanks for your review.=20

> On Mar 6, 2017, at 10:47 PM, Susan Hares <shares@ndzh.com> wrote:
>=20
> Bob:=20
>=20
> Thank you for your response.    I'm pulling up the remaining questions =
to the top here.  All my questions were about corner cases and "what =
ifs" - which is just the result of being a reviewer of a =
long-implemented specification.=20
>=20
> 1) I thought the IPv6 LAN was targeted for new mobile networks or =
sensor networks.   If so, it may be in the future that the wireless =
connections would want to change the MTU on a network to increase the =
ability to change the MTU.   If you're answer is, we'll make the timer =
adjustment when these technology use it in this way, this is a fine =
answer.=20

The mobile and sensor networks you talk about can independently increase =
the MTU on the access link to which the host initiating PMTUD connects =
to. While this will affect the assumed initial value of the PMTU, it may =
or may not affect the final PMTU. If the first hop link was the link =
with the smallest MTU on the path, increasing it would have an effect on =
the PMTU. Else, it will not.=20

>=20
> 3) The question #4 - I was trying to determine what the interaction =
between the SEND with an MTU size option, and this update to RFC1918.   =
It appears in the specification these two functions are interacting.   =
Is this my imagination?  If not, just for my own information - where do =
I find this in the specification.  =20

The SEND MTU option (which is the same as the ND MTU option - type 5) is =
used just to communicate the MTU of the local link. There is no real =
interaction between this and PMTUD except for the fact that the Path MTU =
cannot exceed this number.

Thanks
Suresh


--Apple-Mail=_A7DE507A-13D0-4DF8-9820-AA1A7A2ED685
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzA4MDAwMjI0WjAjBgkqhkiG9w0B
CQQxFgQUZDqtU2YDu+51htj/Hp0X6OFLVWYwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQBdUJvLN2k0SO77M6cEn3F8KcbkVGav5o58lJ4qyej0jXS1hVGl1p7ARJKzbxdQ
4MKjPA2vXWflqucD+ndzOrpF0c29wdofYM4CKKxmjgQOCpJwz88mGfK4yKQ3i4QQ/YTZiKlR9zsM
cEJkB9XwY2CrnTjLYkUDW2L0lEHWNc0opFAbbHuESrAyh2JbReFqMLJsaqvCRhslwFWpGVYDkwzk
7BztiALV+0JQHaCjw50L7wMzBmQDWzCi+/EwlAzjwY+vABHOdfOf2WEgg2rc7abx3lVck/lvnZQY
A0oNGrO7Av1+rfPeXwYZLQlvV9BJ4wVuOwu/Nx14DMekwc1MRC3WAAAAAAAA

--Apple-Mail=_A7DE507A-13D0-4DF8-9820-AA1A7A2ED685--


From nobody Tue Mar  7 17:48:42 2017
Return-Path: <kaduk@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 907DA129482; Tue,  7 Mar 2017 17:48:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6s9YZnzysVYy; Tue,  7 Mar 2017 17:48:34 -0800 (PST)
Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C240B129447; Tue,  7 Mar 2017 17:48:30 -0800 (PST)
X-AuditID: 1209190d-af7ff70000003148-0c-58bf62ece4dc
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by  (Symantec Messaging Gateway) with SMTP id 45.44.12616.CE26FB85; Tue,  7 Mar 2017 20:48:28 -0500 (EST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id v281mRZg014404; Tue, 7 Mar 2017 20:48:28 -0500
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v281mOPt003933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Mar 2017 20:48:26 -0500
Date: Tue, 7 Mar 2017 19:48:24 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: secdir@ietf.org, ietf@ietf.org, draft-ietf-jsonbis-rfc7159bis.all@ietf.org
Subject: secdir review of draft-ietf-jsonbis-rfc7159bis-03
Message-ID: <20170308014823.GF30306@kduck.kaduk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.6.1 (2016-04-27)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOIsWRmVeSWpSXmKPExsUixCmqrPsmaX+EwbRDGhaznv1gtHi2cT6L xYeFD1kcmD2WLPnJFMAYxWWTkpqTWZZapG+XwJXR2ziTvaDHqmLHr37GBsZd+l2MnBwSAiYS s1+cYeti5OIQEmhjkrh36i8rhLOBUeL/hdXsEM4VJokHe0+wgrSwCKhIfJ83iw3EZgOyG7ov M4PYIgJ+Em+W7GcHsYUFrCTWHpjKCGLzAq1o+7mDDcIWlDg58wkLiM0soCVx499Lpi5GDiBb WmL5Pw6QsKiAskTDjAfMExh5ZyHpmIWkYxZCxwJG5lWMsim5Vbq5iZk5xanJusXJiXl5qUW6 Rnq5mSV6qSmlmxjB4SXJu4Px312vQ4wCHIxKPLweZ/dFCLEmlhVX5h5ilORgUhLlXRy9P0KI Lyk/pTIjsTgjvqg0J7X4EKMEB7OSCG+7JVCONyWxsiq1KB8mJc3BoiTOK67RGCEkkJ5Ykpqd mlqQWgSTleHgUJLgNQbGkZBgUWp6akVaZk4JQpqJgxNkOA/Q8J+JIMOLCxJzizPTIfKnGBWl xHk/JQAlBEASGaV5cL2g+JfI3l/zilEc6BVhXj6QFTzA1AHX/QpoMBPQYG3XvSCDSxIRUlIN jNYOxRkNvSuZFD49ufBlx2Gvvq9NVmbxstYXNn/16I4Rz9/bG7+js+CevfeP60n6mvemM8YL 73udac0gfOnplCnnu3JdhYttd/zxX73bNmbbXMkdH7fcqBTdGXXjuNGBb2YibI0bLQ4uYjqx baq5xY5t6W95hT3nNf6NX7dJcuLFzwwmDN+ONCqxFGckGmoxFxUnAgB18B3W2gIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jvZ1PbWO8exO_Gkg1vCN2LgS5LI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 01:48:35 -0000

Hi all,

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should
treat these comments just like any other last call comments.

It is rather surprising to find notable omissions with what is
effectively rfc4627ter, though that seems to be my conclusion after
performing this review.  Luckily, they should be easy to resolve
with just a touch more text in the security considerations, for the
most part.

As an overall summary, this document is a simple, clean, crisp
writeup of the JSON interchange format, which is expected to match
that of the ECMAscript standard.

Since this is a data format and not a protocol, any security issues
with this document are expected to be second-order effects, relating
to how the format is used or could be (mis)used by consuming
protocols.  It is useful to give guidance on issues that may occur
due to known-bad implementations, edge cases that can cause trouble,
etc., and this document does so, noting that the fields in an object
are unordered (but some implementations respect the order in their
APIs), when comparing field names the potential for escaped
characters must be taken into account, many implementations have
limited precision/bounds for numbers, non-number mathematical values
cannot be expressed in JSON, etc.

However, I think that the security considerations section would
benefit from some discussion of potential/example consequences of
failing to heed those issues:

Doing name comparison without respect for excaping could let an
attacker inject unsanitized data into what is supposed to be a
trusted structure, potentially giving privilege escalation,
compromising authentication and authorization, etc.

Considering only the first (or last) of duplicated name/value pairs
can lead to vulnerabilities by bypassing security checks, in mixed
environments.  Similarly, a reliance on fields being returned in
order could cause issues (certainly denial of service, potentially
worse) if an attacker uses a different order than expected.  Perhaps
the start of section 4 could refer forward to discussion in the
security considerations, which give some exposition on the
consequences of breaking the "names within an object SHOULD be
unique" guidance.

Implementations should probably check that their numerical routines
do not attempt to emit "NaN" or "Inf" or simlar, though I do not
have a good picture of how that would affect real systems
(hopefully, just a parse error on the receiver, as those are not
permitted by the grammar).  Similarly, the use of extremely large or
precise numbers in mixed environments can lead to unexpected
results.  I expect that there could be vulnerabilities here, such as
if code can be induced into a loop with incearingly large values,
where a sender ends up producing numbers larger than can be
represented on the receiver, which then saturates its
strtonum-equivalent and hits an unexpected codepath.


I'm also concerned about the freewheeling use of Unicode.  While
this document does discuss the potential encodings and lists UTF-8
as the default (and most interoperable), I think it would benefit
from a stricter warning that parties using JSON for communication
must have some out-of-band way to agree on what encoding is to be
used.  I would expect that this is usually going to be done by the
protocol using JSON, but could see a place for the actual
communicating peers to have out-of-band knowledge.  (An application
having to guess what encoding is being used based on heuristics is a
recipe for disaster.)

Additionally, the document makes no mention of Unicode
normalization, which can be a minefield.  The precis working group
has a lot of work in this area, from which the executive summary is:
it's a lot of work to do things correctly, and being sloppy usually
leads to vulnerabilities.  The most obvious issue would be in (the
comparison of) field names using strings that can be represented
differently in different normalization forms (for example, e with
acute accent), which can be either U+00e9 or U+0064 and the
combining character U+0301.  Simply converting to Unicode code
points is insufficient for an implementation to cause those strings
to compare as equivalent.  I think this document should at least
mention that Unicode normalization forms exist and should be
considered by protocol designers when using JSON with characters
outside of US-ASCII.


Section 9 (parsers) mentions that an implementation "may set limits"
on various parameters.  That seems like a good place to give some
guidance on what limits are in common use and how protocols or
protocol peers might discover and/or negotiate each others'
implementation limits.


With the proposed additions to the security considerations out of
the say, on to some other minutiae.

Section 3 describes that "[a] JSON value MUST be an object, array,
number, or string, or one of the following three literal names:
false null true"; in the introduction, this (equivalent) list is
given as "object, array, number, string, boolean, or null", in the
guise of "four primitive types (strings, numbers, booleans, and
null) and two structured types (objects and arrays)".  There may be
some value in using consistent terminology between the two
locations, but it would be pretty minor value and might not be worth
the effort.

The format for numbers (Section 6) permits an explicit (redundant)
plus sign in the exponent part, but not in front of the overall
number.  This feels slightly strange to me, but I don't know if
there are any implementations that get this wrong.  (I also don't
really see security consequences of getting it wrong.)  Similarly,
the fractional part must contain a digit (that is, a number ending
in a decimal point is forbidden), which is probably harmless.  I'll also
note that the number 3.141592653589793238462643383279 is used as an
example of a precision unrepresentable in 64-bit IEEE 754
floating-point, but the next digit in the expansion of pi is a '5',
which would round up to ...80.  Maybe another digit should be added
to keep overly pedantic readers from worrying about rounding modes :)

Should section 8.3 (string comparison) use any RFC 2119 language
with respect to treating strings as equal that use escapes (or even
normalization forms, as covered above)?

The IANA considerations (section 11) might be a little more explicit
that the IANA "Media Types" registry is what is being modified.
I'm also rather curious about the claim that no "charset" parameter
is needed as it "really has no effect on compliant recipients".  Why
is this not a good way to communicate whether UTF-8, UTF-16, or
UTF-32 is in use for a given text?

It might also be useful to have an example of an array object that
contains elements of different type, to reinforce that this is
permitted.

With respect to section 1.3, I personally am more used to seeing a
"changes since <previous document>" section that lays out what
changed inline, as opposed to with (opaque) references to specific
errata.  But that is rather an editorial issue so my personal
preference should not bind you.

-Ben


From nobody Tue Mar  7 18:02:54 2017
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 DFE95129400 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 18:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NGXXsnGBXyqU for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 18:02:51 -0800 (PST)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB9B6120724 for <ietf@ietf.org>; Tue,  7 Mar 2017 18:02:50 -0800 (PST)
Received: by mail-qk0-x22c.google.com with SMTP id y76so38986372qkb.0 for <ietf@ietf.org>; Tue, 07 Mar 2017 18:02:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=zkHMoVIgm3eYahKLRQiExv4R3LjAyTh7yORCJCmfB2A=; b=Qu1VAG6QbOclvvC3u/4q1jazFzAyrX7HFuYvxOhE1j/t2C8eL4GlyRXhkGSo28LQQJ kSHXPl/h8rMoHOO2lXgC5oCwSH25uA1DcEjv8Q2YdZc/dQuyQ8onIy0kRp0zMTrlW52N AxLOxa7qklC3833rCPwJcZhUw82uowRIP/7Lkzw/nMDPhg04ByQTBrIu/ri3BrJOJ6Jk l2me22akXURqRGTOo5REG3B2UHhPHKzIzxAV9/YSgrFf8hMJwV3zcVzIMouSTofVdupL HiwuiizKQ0k2e0uV6yjvP7DySzqRsZn0nS4gZRihEEQlaOEVTLxX3Xb63f1u3qpeoDBS hk+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=zkHMoVIgm3eYahKLRQiExv4R3LjAyTh7yORCJCmfB2A=; b=KEQluMdHPf1E5vVhiQe0rEv+do59NUfcP/M/jeLmOM+R6zVOufl4QEOUV9HGySQ/NC tWJh8Lhl3Wg15il6B51U5YVUtRdzlverpeB/XtWedR8Uk1CB7Qdyc906AeUBXVa1T+q+ vmrptzohPvvvdnj7VCh5PxBkyJCXyRxbn3PpWuLmg8eHCvdU5DfINBIVlNH7H/sx+DzE v4gfuP17s7S52lwok9wgL24lQDK9mhVjERxIP2DBa2rt/RekWvtAgNNuYnVjWZnjiPbL u+0k8PIhgHq7miV8yiB9o6iaOC/nKmD5mIjHEQsiH7lpIVseRvdPoGZihNjeW2LVGWzM WzVg==
X-Gm-Message-State: AMke39k37qy/KTkL6xtPLVifEY4xRqCuU9PhhdZkDt0NQ4Nj3fvKwfdWJCBWTUlpywqDimV5U5d2EZyfXTBUKQ==
X-Received: by 10.129.172.25 with SMTP id k25mr778699ywh.165.1488938570011; Tue, 07 Mar 2017 18:02:50 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Tue, 7 Mar 2017 18:02:49 -0800 (PST)
In-Reply-To: <20170307203719.GB6276@Alexs-MacBook-Pro>
References: <20170302055128.GJ12470@Alexs-MacBook-Pro> <CAMm+Lwg_kAtYUGivYSF5ZzF5nfywS4rzYG88UEzxgjRL2_=83Q@mail.gmail.com> <20170307203719.GB6276@Alexs-MacBook-Pro>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 7 Mar 2017 21:02:49 -0500
X-Google-Sender-Auth: KPYmqouI3porXark02WyLWXJEHc
Message-ID: <CAMm+LwjxRiUofiDo3UoPYfJPy=QSCze99bq+6xcUj6HfV7yheg@mail.gmail.com>
Subject: Re: Interest in a push-based two-factor auth standard?
To: Alex Jordan <alex@strugee.net>
Content-Type: multipart/alternative; boundary=94eb2c1badfc8edf05054a2e86f9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9c2HPkchGbScuNb7zP94J-ficQA>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 02:02:53 -0000

--94eb2c1badfc8edf05054a2e86f9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 7, 2017 at 3:37 PM, Alex Jordan <alex@strugee.net> wrote:

> On Mon, Mar 06, 2017 at 08:05:11AM -0500, Phillip Hallam-Baker wrote:
>
> > What we are discussing goes beyond two factor auth. If you have a cell
> > phone with a device specific signature key, it can sign the response
> which
> > means that you automatically collect up a non repudiable audit log of t=
he
> > user's actions. This is beyond anything possible with OTP number
> sequences
> > or USB dongles.
>
> Indeed. I suspect there are a lot of unexplored uses for such a
> standard, but haven't explored it fully yet. (Note also that the lack
> of deniability could be seen as a positive thing _or_ a negative
> thing, depending.)
>
> > =E2=80=8Bi am interested and have developed several protocols of this t=
ype using
> > JSON. My work provides prior art back to 2010 at the very least.
>
> Are there any public references for this work?
>

https://tools.ietf.org/id/draft-hallambaker-owcp-00.txt
https://tools.ietf.org/html/draft-hallambaker-sxs-confirm-02

=E2=80=8BThat is not the latest version.=E2=80=8B There might even be a lat=
er published
version.

I have code. The reason I have not updated the drafts is that right now I
am working on the problem of binding all the user's devices together so
that they can respond to a confirmation request from their phone or their
watch or any other device(s) they pick. Each device always signs with a
unique device key however so the signatures can be tracked back to the
device used.





> I think what makes most sense at this point is for me to draw up a
> rough Internet draft and then send it to the Security area and see
> what they think the best way forward is. Looking at prior work will
> probably aid in the design of such a draft.
>
> Does that seem okay to those who have expressed interest in this?
>
> Cheers!
>
> AJ
>

--94eb2c1badfc8edf05054a2e86f9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Ma=
r 7, 2017 at 3:37 PM, Alex Jordan <span dir=3D"ltr">&lt;<a href=3D"mailto:a=
lex@strugee.net" target=3D"_blank">alex@strugee.net</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">=
On Mon, Mar 06, 2017 at 08:05:11AM -0500, Phillip Hallam-Baker wrote:<br>
<br>
&gt; What we are discussing goes beyond two factor auth. If you have a cell=
<br>
&gt; phone with a device specific signature key, it can sign the response w=
hich<br>
&gt; means that you automatically collect up a non repudiable audit log of =
the<br>
&gt; user&#39;s actions. This is beyond anything possible with OTP number s=
equences<br>
&gt; or USB dongles.<br>
<br>
</span>Indeed. I suspect there are a lot of unexplored uses for such a<br>
standard, but haven&#39;t explored it fully yet. (Note also that the lack<b=
r>
of deniability could be seen as a positive thing _or_ a negative<br>
thing, depending.)<br>
<span class=3D"gmail-"><br>
&gt; =E2=80=8Bi am interested and have developed several protocols of this =
type using<br>
&gt; JSON. My work provides prior art back to 2010 at the very least.<br>
<br>
</span>Are there any public references for this work?<br></blockquote><div>=
<br></div><div><a href=3D"https://tools.ietf.org/id/draft-hallambaker-owcp-=
00.txt">https://tools.ietf.org/id/draft-hallambaker-owcp-00.txt</a><br></di=
v><div><a href=3D"https://tools.ietf.org/html/draft-hallambaker-sxs-confirm=
-02">https://tools.ietf.org/html/draft-hallambaker-sxs-confirm-02</a><br></=
div><div><br></div><div><div class=3D"gmail_default" style=3D"font-size:sma=
ll">=E2=80=8BThat is not the latest version.=E2=80=8B There might even be a=
 later published version.</div><div class=3D"gmail_default" style=3D"font-s=
ize:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small"=
>I have code. The reason I have not updated the drafts is that right now I =
am working on the problem of binding all the user&#39;s devices together so=
 that they can respond to a confirmation request from their phone or their =
watch or any other device(s) they pick. Each device always signs with a uni=
que device key however so the signatures can be tracked back to the device =
used.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div=
></div><div><br></div><div><br></div><div>=C2=A0</div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">
I think what makes most sense at this point is for me to draw up a<br>
rough Internet draft and then send it to the Security area and see<br>
what they think the best way forward is. Looking at prior work will<br>
probably aid in the design of such a draft.<br>
<br>
Does that seem okay to those who have expressed interest in this?<br>
<br>
Cheers!<br>
<span class=3D"gmail-HOEnZb"><font color=3D"#888888"><br>
AJ<br>
</font></span></blockquote></div><br></div></div>

--94eb2c1badfc8edf05054a2e86f9--


From nobody Tue Mar  7 18:52:46 2017
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 66C97128B37; Tue,  7 Mar 2017 18:52:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.37
X-Spam-Level: 
X-Spam-Status: No, score=-2.37 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J198sQIeTZK1; Tue,  7 Mar 2017 18:52:39 -0800 (PST)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D434120724; Tue,  7 Mar 2017 18:52:39 -0800 (PST)
Received: by mail-it0-x231.google.com with SMTP id h10so83890375ith.1; Tue, 07 Mar 2017 18:52:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=wJOp1LVW4UtJRSWiIUfPM+7tXGn2Q6qPgP1YEk6n1uk=; b=JhV8puMkw8F3nSDNDOo3jmz24ZhUgYiTkbqHsQ4ZF6KOoteqo7HmFLsc6xInxy4CdK Brp/v1MyjHtf+0zvJHG1h+Zc/goqH54EJULM/ajFll6MvsbNONT7xikQv9QQBTR06G+5 wRzLIqqxa4sW5jQt36NuVGdrHtdI9n+ZeAokLLji2Y+yFIAzBomAoN23Er1yL4wi7UcB qxZsIo6Kh6lv9+pQ5naoK1Qm75RC+jsLfIJKViHLIC7V17mGys+5nUWCKPBjDeK3lJXq pGg7Huj9Ct25grbKpv5BOWAJtUPApabHfnPiObqkjs1rdY0K9yxrnzOxk2tRLdFdGJ+A aolA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=wJOp1LVW4UtJRSWiIUfPM+7tXGn2Q6qPgP1YEk6n1uk=; b=Iu0jDuvn+IlaKrBbSU3+D3NxF0iArUIKqGmRYWer/dJFN9zODfoZbCsK8ckKnYUmyy HPBTKixBdE80zcPMya+TGeuMJ3gggV127vLxevqATevC64CiwGD1SyMDAHk/dBaRrC4I KyjNPyrsEbVT935tpJiLbgjtJSonKMTnnPccmx+ZV6KTvMOZaV9w4VED99fwIH2WHAr2 DjAq6Dzct4N+foQCZRl5j1Bzc9jXiSC9FB7Ep7TIpH6yf2QB6u4uTK8JQ1YW0lU+4N8z 8Vnaed/qRto7u6MnM/mWeNkvhDbkXvUtibEhilz2NWHB014+WKXcJrFhic77czkPoNkW /hCg==
X-Gm-Message-State: AMke39nwtKApka7s1sqn7iHM4WC7bF2y+QXSpPay+gHNLUEcUG2ytcMjcDKHGfNXGbn8nzwN5kbRsLTYN27P3A==
X-Received: by 10.36.184.129 with SMTP id m123mr4321768ite.120.1488941558346;  Tue, 07 Mar 2017 18:52:38 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.35.200 with HTTP; Tue, 7 Mar 2017 18:52:37 -0800 (PST)
In-Reply-To: <20170308014823.GF30306@kduck.kaduk.org>
References: <20170308014823.GF30306@kduck.kaduk.org>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 7 Mar 2017 21:52:37 -0500
X-Google-Sender-Auth: OY5Elvczs5e1sNmTDoLMMtjd1is
Message-ID: <CAC4RtVBJU80fKw+eqBXbvCmXy=k8fyu5d_x_KqoHZYp6Mp62FQ@mail.gmail.com>
Subject: Re: [secdir] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Benjamin Kaduk <kaduk@mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/R97GQiq7RoY4z0TqfYJ8mFuz43c>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, IETF discussion list <ietf@ietf.org>, secdir <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 02:52:40 -0000

Hi, Ben.
A note on the Internationalization points:

> I'm also concerned about the freewheeling use of Unicode.  While
> this document does discuss the potential encodings and lists UTF-8
> as the default (and most interoperable), I think it would benefit
> from a stricter warning that parties using JSON for communication
> must have some out-of-band way to agree on what encoding is to be
> used.  I would expect that this is usually going to be done by the
> protocol using JSON, but could see a place for the actual
> communicating peers to have out-of-band knowledge.  (An application
> having to guess what encoding is being used based on heuristics is a
> recipe for disaster.)
>
> Additionally, the document makes no mention of Unicode
> normalization, which can be a minefield.  The precis working group
> has a lot of work in this area, from which the executive summary is:
> it's a lot of work to do things correctly, and being sloppy usually
> leads to vulnerabilities.  The most obvious issue would be in (the
> comparison of) field names using strings that can be represented
> differently in different normalization forms (for example, e with
> acute accent), which can be either U+00e9 or U+0064 and the
> combining character U+0301.  Simply converting to Unicode code
> points is insufficient for an implementation to cause those strings
> to compare as equivalent.  I think this document should at least
> mention that Unicode normalization forms exist and should be
> considered by protocol designers when using JSON with characters
> outside of US-ASCII.

I believe that all of this is the realm of the protocol *using* JSON,
and doesn't belong in the JSON spec itself.  The JSON spec makes it
clear what the encoding options are, and leaves things such as the set
of allowed characters (and any restrictions on them), the
normalization and canonicalization, and the comparison rules to the
next level... and I believe that's how it should be.  Different uses
of JSON will have different needs in these regards, and *those*
specifications are the right places to say that.

Barry


From nobody Tue Mar  7 19:30:48 2017
Return-Path: <kaduk@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 A1B90129480; Tue,  7 Mar 2017 19:30:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUhQ77D-etSr; Tue,  7 Mar 2017 19:30:40 -0800 (PST)
Received: from dmz-mailsec-scanner-1.mit.edu (dmz-mailsec-scanner-1.mit.edu [18.9.25.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D91F129469; Tue,  7 Mar 2017 19:30:40 -0800 (PST)
X-AuditID: 1209190c-6c7ff70000005cc1-9f-58bf7add58da
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by  (Symantec Messaging Gateway) with SMTP id 72.52.23745.DDA7FB85; Tue,  7 Mar 2017 22:30:38 -0500 (EST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id v283UbdT026028; Tue, 7 Mar 2017 22:30:37 -0500
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v283UXJs001011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Mar 2017 22:30:36 -0500
Date: Tue, 7 Mar 2017 21:30:33 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [secdir] secdir review of draft-ietf-jsonbis-rfc7159bis-03
Message-ID: <20170308033033.GI30306@kduck.kaduk.org>
References: <20170308014823.GF30306@kduck.kaduk.org> <CAC4RtVBJU80fKw+eqBXbvCmXy=k8fyu5d_x_KqoHZYp6Mp62FQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAC4RtVBJU80fKw+eqBXbvCmXy=k8fyu5d_x_KqoHZYp6Mp62FQ@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMIsWRmVeSWpSXmKPExsUixCmqrHuvan+EwbZVQhaHFl9itZj17Aej xbON81ksPix8yOLA4tGyqpfZY8mSn0wBTFFcNimpOZllqUX6dglcGZtWtjEV/Beu+H33LXsD 4x/+LkZODgkBE4m/t54xdTFycQgJtDFJHNzZxgaSEBLYwCix6wEvROIKk8TZ6c3sIAkWARWJ 0zP+sYLYbEB2Q/dlZhBbREBT4vnnKUwgNrNAucSRU9vB6oUF3CV2nf8EFOfg4AXa9mazBsT8 aokra6aBtfIKCEqcnPmEBaJVS+LGv5dg5cwC0hLL/3GAhDkFAiU27loPViIqoCzRMOMB8wRG gVlIumch6Z6F0L2AkXkVo2xKbpVubmJmTnFqsm5xcmJeXmqRrqFebmaJXmpK6SZGcNhK8uxg PPPG6xCjAAejEg+vx9l9EUKsiWXFlbmHGCU5mJREeQ9m7o8Q4kvKT6nMSCzOiC8qzUktPsQo wcGsJMLbbgmU401JrKxKLcqHSUlzsCiJ80poNEYICaQnlqRmp6YWpBbBZGU4OJQkeBsrgRoF i1LTUyvSMnNKENJMHJwgw3mAhreB1PAWFyTmFmemQ+RPMSpKifNeqgBKCIAkMkrz4HpBaUUi e3/NK0ZxoFeEeQ+AtPMAUxJc9yugwUxAg7Vd94IMLklESEk1MMZtUV8ZXJXCphC01XTy4ldn pwXI37knsOVamFZQ307tAwfuMH4PTFrPGLbUhEvf6LnK098+P2Y/05zLsT3wtLrS1OLEtd8e iWxt37s4w3Hjo8zHl0VVb1RYKGknL/jlu8ZPaael5px7b7hu25iKWDwRz5l24QzTwpyHiVVf UgN/CB6Q698pOVeJpTgj0VCLuag4EQDC+67mBgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vLKKdPcuYcg-VnB4SjGV10OvFFo>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, IETF discussion list <ietf@ietf.org>, secdir <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 03:30:42 -0000

Hi Barry,

On Tue, Mar 07, 2017 at 09:52:37PM -0500, Barry Leiba wrote:
> Hi, Ben.
> A note on the Internationalization points:
> 
> > I'm also concerned about the freewheeling use of Unicode.  While
> > this document does discuss the potential encodings and lists UTF-8
> > as the default (and most interoperable), I think it would benefit
> > from a stricter warning that parties using JSON for communication
> > must have some out-of-band way to agree on what encoding is to be
> > used.  I would expect that this is usually going to be done by the
> > protocol using JSON, but could see a place for the actual
> > communicating peers to have out-of-band knowledge.  (An application
> > having to guess what encoding is being used based on heuristics is a
> > recipe for disaster.)
> >
> > Additionally, the document makes no mention of Unicode
> > normalization, which can be a minefield.  The precis working group
> > has a lot of work in this area, from which the executive summary is:
> > it's a lot of work to do things correctly, and being sloppy usually
> > leads to vulnerabilities.  The most obvious issue would be in (the
> > comparison of) field names using strings that can be represented
> > differently in different normalization forms (for example, e with
> > acute accent), which can be either U+00e9 or U+0064 and the
> > combining character U+0301.  Simply converting to Unicode code
> > points is insufficient for an implementation to cause those strings
> > to compare as equivalent.  I think this document should at least
> > mention that Unicode normalization forms exist and should be
> > considered by protocol designers when using JSON with characters
> > outside of US-ASCII.
> 
> I believe that all of this is the realm of the protocol *using* JSON,
> and doesn't belong in the JSON spec itself.  The JSON spec makes it
> clear what the encoding options are, and leaves things such as the set
> of allowed characters (and any restrictions on them), the
> normalization and canonicalization, and the comparison rules to the
> next level... and I believe that's how it should be.  Different uses
> of JSON will have different needs in these regards, and *those*
> specifications are the right places to say that.

I agree that it is appopriate for the JSON spec to merely list out the
options and leave decisions to the consuming applications/protocols.
However, it seems irresponsible to not mention that those designing
such protocols should be aware of the potential issues.

-Ben


From nobody Tue Mar  7 21:51:08 2017
Return-Path: <jrmitche@puck.nether.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 26B291293FD; Tue,  7 Mar 2017 21:51:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jon Mitchell <jrmitche@puck.nether.net>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-mpls-tp-temporal-hitless-psm-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148895226612.17662.7706011588102984090@ietfa.amsl.com>
Date: Tue, 07 Mar 2017 21:51:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Vu0cuPNykym1XDZgzYVqq_9dNKs>
Cc: mpls@ietf.org, draft-ietf-mpls-tp-temporal-hitless-psm.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 05:51:06 -0000

Reviewer: Jon Mitchell
Review result: Has Nits

I have reviewed this document as part of the Operational directorate's

ongoing effort to review all IETF documents being processed by the
IESG.  These 
comments were written with the intent of improving the operational
aspects of the 
IETF drafts. Comments that are not addressed in last call may be
included in AD reviews 
during the IESG review.  Document editors and WG chairs should treat
these comments 
just like any other last call comments. 

Document is Ready with Nits.  I share the concern that it's not
totally clear upfront this is
a requirements versus solution document.  There is also not much in
the way of requirements
of notification or how to signal back to the operator that a fault has
occurred, but this
may be OK if whatever solution would meet the requirements of this
draft will include
such text or rely on existing mechanisms discussed in RFC6371.



From nobody Tue Mar  7 22:39:59 2017
Return-Path: <roni.even@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED3EA129480 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 22:39:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CAF0vjeSf1n5 for <ietf@ietfa.amsl.com>; Tue,  7 Mar 2017 22:39:56 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3318712941D for <ietf@ietf.org>; Tue,  7 Mar 2017 22:39:56 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DCJ65574; Wed, 08 Mar 2017 06:39:54 +0000 (GMT)
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 8 Mar 2017 06:39:53 +0000
Received: from DGGEMM506-MBS.china.huawei.com ([169.254.4.77]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0301.000; Wed, 8 Mar 2017 14:39:45 +0800
From: Roni Even <roni.even@huawei.com>
To: Steve Donovan <srdonovan@usdonovans.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Review of draft-ietf-dime-load-07
Thread-Topic: Review of draft-ietf-dime-load-07
Thread-Index: AQHSl1pAwVKbCs8uhUmqxDAuAs02/6GKfpuA
Date: Wed, 8 Mar 2017 06:39:46 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD78E455@DGGEMM506-MBS.china.huawei.com>
References: <148784049413.20240.15876379956092850264.idtracker@ietfa.amsl.com> <0390f072-bf67-d77b-a47f-b76140be81ae@usdonovans.com>
In-Reply-To: <0390f072-bf67-d77b-a47f-b76140be81ae@usdonovans.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.201.224]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.58BFA73A.0067, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.77, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: f18fa6d5fdf9278fa46629f36c32d4a9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NcqrrqtXnE8vkQTTw0NMbygmFw8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 06:39:58 -0000

SGkgU3RldmUsDQpUaGFua3MsIEkgaGF2ZSBubyBtb3JlIGNvbW1lbnRzDQpSb25pDQoNCj4gLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0ZiBbbWFpbHRvOmlldGYtYm91bmNl
c0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFN0ZXZlIERvbm92YW4NCj4gU2VudDog15nXldedwqDX
kiAwNyDXnteo16UgMjAxNyAxNzo0NQ0KPiBUbzogaWV0ZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBS
ZTogUmV2aWV3IG9mIGRyYWZ0LWlldGYtZGltZS1sb2FkLTA3DQo+IA0KPiBSb25pLA0KPiANCj4g
VGhhbmsgeW91IGZvciB5b3VyIHJldmlldy4gIFBsZWFzZSBzZWUgbXkgY29tbWVudHMgaW5saW5l
Lg0KPiANCj4gU3RldmUNCj4gDQo+IE9uIDIvMjMvMTcgMzowMSBBTSwgUm9uaSBFdmVuIHdyb3Rl
Og0KPiA+IFJldmlld2VyOiBSb25pIEV2ZW4NCj4gPiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRo
IE5pdHMNCj4gPg0KPiA+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRo
aXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4gPiBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2
aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5DQo+ID4gdGhlIElFU0cg
Zm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlr
ZQ0KPiA+IGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+ID4NCj4gPiBGb3IgbW9yZSBp
bmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+ID4NCj4gPiA8aHR0cHM6Ly90cmFj
LmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCj4gPg0KPiA+IERvY3VtZW50OiBk
cmFmdC1pZXRmLWRpbWUtbG9hZC0wNw0KPiA+IFJldmlld2VyOiBSb25pIEV2ZW4NCj4gPiBSZXZp
ZXcgRGF0ZTogMjAxNy0wMi0yMw0KPiA+IElFVEYgTEMgRW5kIERhdGU6IDIwMTctMDItMjcNCj4g
PiBJRVNHIFRlbGVjaGF0IGRhdGU6IDIwMTctMDMtMTYNCj4gPg0KPiA+IFN1bW1hcnk6IFRoaXMg
ZHJhZnQgaXMgYWxtb3N0IHJlYWR5IGZvciBwdWJsaWNhdGlvbiBhcyBhIHN0YW5kYXJkDQo+ID4g
dHJhY2sgUkZDDQo+ID4NCj4gPiBNYWpvciBpc3N1ZXM6DQo+ID4NCj4gPiBNaW5vciBpc3N1ZXM6
DQo+ID4NCj4gPiBJIHVuZGVyc3RhbmQgdGhhdCBlYWNoIG5vZGUgY2FuIGNhbGN1bGF0ZSB0aGUg
bG9hZCBkaWZmZXJlbnRseSAsIHRoZQ0KPiA+IGV4YW1wbGUgaW4gZmlndXJlIDggZGVtb25zdHJh
dGUgdGhhdCB0aGUgYWdlbnQgc2VsZWN0aW9uIG1heSBiZQ0KPiA+IGRpZmZlcmVudCBpZiB0aGUg
YWdlbnQgYWdncmVnYXRlcyBsb2FkIGZyb20gdGhlIHNlcnZlcnMgdG8gY2FsY3VsYXRlDQo+ID4g
aXRzIGxvYWQgb3IganVzdCBjb252ZXlzIGhpcyBsb2FkLCBwb3NzaWJseSBldmVuIHRoYXQgZWFj
aCBvbmUgb2YgdGhlDQo+ID4gYWdlbnRzIHdpbGwgdXNlIGRpZmZlcmVudCBtZXRob2QuIFdoeSBu
b3QgbWFuZGF0ZSBsb2FkIGNhbGN1bGF0aW9uDQo+ID4gdXNpbmcgYWdncmVnYXRlZCB3ZWlnaHRl
ZCBsb2Fkcz8NCj4gU1JEPiBUaGUgd29ya2luZyBncm91cCB0aG91Z2h0IGl0IHdhcyBiZXN0IHRv
IGxlYXZlIHRoaXMgYXMgYW4NCj4gaW1wbGVtZW50YXRpb24gZGVjaXNpb24uDQo+ID4NCj4gPiBO
aXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4gPiAxLiBJbiBzZWN0aW9uIDUgcGFyYWdyYXBoIDkg
IlRoZSBsb2FkIHJlcG9ydCBpbmNsdWRlcyBhIHZhbHVlDQo+ID4gaW5kaWNhdGluZyB0aGUgbG9h
ZCBvZiB0aGUgc2VuZGluZw0KPiA+ICAgICBub2RlIHJlbGF0aXZlIGxvYWQgb2YgdGhlIHNlbmRp
bmcgbm9kZSwgIiBzaG91bGQgYmUganVzdCAiVGhlIGxvYWQNCj4gPiByZXBvcnQgaW5jbHVkZXMg
YSB2YWx1ZSBpbmRpY2F0aW5nIHRoZSByZWxhdGl2ZSBsb2FkIG9mIHRoZSBzZW5kaW5nDQo+ID4g
bm9kZSwiDQo+IFNSRD4gWWVzLCBjaGFuZ2UgbWFkZS4NCj4gPiAyLiBJbiBzZWN0aW9uIDYuMiAi
d2VpZ3RoICINCj4gU1JEPiBDaGFuZ2UgbWFkZS4NCj4gPiAzLiBpbiB0aGUgc2VjdXJpdHkgY29u
c2lkZXJhdGlvbiB3aGF0IGFib3V0IGFuIGVuZHBvaW50IGluIHRoZSBtaWRkbGUNCj4gPiBjaGFu
Z2luZyB0aGUgaG9zdCBsb2FkIHZhbHVlIGNhdXNpbmcgYSBjaGFuZ2UgaW4gdGhlIHJvdXRpbmcN
Cj4gPiBkZWNpc2lvbnMuDQo+IFNSRD4gSSdtIGFzc3VtaW5nIHRoYXQgeW91IG1lYW4gYW4gYWdl
bnQgaW4gdGhlIG1pZGRsZSBjaGFuZ2luZyB0aGUgaG9zdA0KPiB2YWx1ZS4gIEkndmUgYWRkZWQg
dGhlIGZvbGxvd2luZyB0byB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgc2VjdGlvbg0KPiAt
LSAiR2l2ZW4gdGhhdCByb3V0aW5nIGRlY2lzaW9ucyBhcmUgaW1wYWN0ZWQgYnkgbG9hZCBpbmZv
cm1hdGlvbiwgdGhlcmUgaXMNCj4gcG90ZW50aWFsIGZvciBuZWdhdGl2ZSBpbXBhY3RzIG9uIGEg
RGlhbWV0ZXIgbmV0d29yayBjYXVzZWQgYnkgZXJyb25lb3VzDQo+IG9yIG1hbGljaW91cyBsb2Fk
IHJlcG9ydHMuIFRoaXMgaW5jbHVkZXMgdGhlIG1hbGljaW91cyBjaGFuZ2luZyBvZiBsb2FkIHZh
bHVlcw0KPiBieSBEaWFtZXRlciBBZ2VudHMuIg0KPiA+DQo+ID4NCj4gPg0KPiA+DQoNCg==


From nobody Tue Mar  7 23:40:02 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 794D1129638; Tue,  7 Mar 2017 23:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzJ8W64Eygl1; Tue,  7 Mar 2017 23:39:58 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66A4D129613; Tue,  7 Mar 2017 23:39:58 -0800 (PST)
Received: from [192.168.178.20] ([93.217.100.107]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LdKs1-1c34dz37uD-00iXAJ; Wed, 08 Mar 2017 08:39:50 +0100
Subject: Re: secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Benjamin Kaduk <kaduk@mit.edu>, secdir@ietf.org, ietf@ietf.org, draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>
References: <20170308014823.GF30306@kduck.kaduk.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de>
Date: Wed, 8 Mar 2017 08:39:50 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170308014823.GF30306@kduck.kaduk.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:EYTmLyyauoZDVxPqbNB2Y4XlnUQetAOq4i6nJRmPvAmRmgckyl/ rrbKcjiAhgBVcTX4R1MVAGl/U+fgjAEOtLdTMYuH1hBXwQVSexVgZphDBxJB8xRWTTM0kqr mEU1XhEPYbjibmKD1MlFnkHDudg6Rc/rGrZk5JKbUnj/n+Loc6xWgBfiPBCg/JBIRHY+Hcb D126Hj/HE1Gw5zpVeV3Xg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:perBMTujxkg=:r5rO1SlULzgIB8MUe1Ulb+ DVIjAQa52p1q/gvO9wIegLcEcGSwXrDsbgxkF+LHagkaqCK+vtEyDyE+JdL6REDC4bFIGhrnx xsxm4QShfHf5hDZcR5zAHJ9bVYMoRFMkQnkaAWM8/kJS1eax9PTOwQu7bo7hmYKzHvkhYeFIH YV5YFqBcX6udcN4qb8Fg1MKxnEML0KZj+2UI4z/GGUaqWHChdlUHHH+Lcu/DYQhtXWWeu03Xh YybWCFeUYBWOwF4Z5b/YYKwje0CazsoJN+eE9z3uO6BGBcljI21ezN/Y7khgfv4QvvPoypCLp Nx57ObEhrrlMG++qMPLfZnYLWqJ3A/Tb09PBPV4r6k6cxhjdkvW9mBpq5F8zVll5VSP+wuQED f/Z7tNyLk0QT7g3Jo3i3yStgdGOlKf87k71vHo1LN/G9Eyqp46qgSMHlNvgspfjvSoVMlUnQb wzVCKPQnoEbKBp9xvrPxs9UJ0Ozf+L9D3C2Ekw0+hF+ETYeSUBm0bbuPEAtpreIift4pd+Grj ruLsiJTW3G6ZO+mTNZYoPgW7RN+6vTnjXG1LaaQrneZ9Uv9kQkKJCnoS9eutTqxjOY3/7VWD1 E31NQNjBWsA0bBPcwrCwMCAO32LXJhSUz+UlGWEhVABcjZxaJldlZYQ7FmVItzOAC9K+HiSd1 wq1IEcH2M3tD16GybBDcRstMbHg2pDcE9YxQ7zyIOVdNdCudsN/25fLcmViQPQ4jFyHBImUFJ 9jMGmXHnUfDT4f4H2x41UilmSLgNWmBBa6cBFkmlLBFhSfehwNg2c371MDUxheUVhoYINYs2A r5rLBCZs26VrU9VdJWf8qb0oPDqNUZRi6nDC15KPMOjHRcEm0jL1Z1nC12tru1xSvkTSeiE07 c1svbH6/bQHlyIEKwR43rgM6dkjIiT4qFnFXw92SSMneOE0yOHBS/9/guKv/gk9fQSzD4PFf9 0KU0+cp2Pj/knCM2w4govzRbZ1LRKPwpaebtIozOnugnqIoaxeVvxZLvJlRSN3Oua3aD0dfqZ 1BE1S1CmeVoLYSR9BJJZxuo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4KIT9T4Gc50r4SL_PFNdBVR4bwo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 07:40:00 -0000

On 2017-03-08 02:48, Benjamin Kaduk wrote:
> I'm also concerned about the freewheeling use of Unicode.  While
> this document does discuss the potential encodings and lists UTF-8
> as the default (and most interoperable), I think it would benefit
> from a stricter warning that parties using JSON for communication
> must have some out-of-band way to agree on what encoding is to be
> used.  I would expect that this is usually going to be done by the
> protocol using JSON, but could see a place for the actual
> communicating peers to have out-of-band knowledge.  (An application
> having to guess what encoding is being used based on heuristics is a
> recipe for disaster.)
> ...

AFAIU, there is no need for out-of-band knowledge (which would be very 
bad). Recipients are supposed to inspect the payload and detect which of 
the three encoding was used.

That said, we probably should make that clearer.

 > ...
> I'm also rather curious about the claim that no "charset" parameter
> is needed as it "really has no effect on compliant recipients".  Why
> is this not a good way to communicate whether UTF-8, UTF-16, or
> UTF-32 is in use for a given text?
> ...

It might have been, but that's now how it is implemented.

Best regards, Julian


From nobody Tue Mar  7 23:47:30 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5EBB129613; Tue,  7 Mar 2017 23:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D2W-Ixh5_Csb; Tue,  7 Mar 2017 23:47:28 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C0C412896F; Tue,  7 Mar 2017 23:47:28 -0800 (PST)
Received: from [192.168.178.20] ([93.217.100.107]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ls7MZ-1cGtcJ1JNP-013vHb; Wed, 08 Mar 2017 08:47:24 +0100
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Benjamin Kaduk <kaduk@mit.edu>, secdir@ietf.org, ietf@ietf.org, draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <456b4234-0d94-1033-507c-710878bb5159@gmx.de>
Date: Wed, 8 Mar 2017 08:47:24 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:8Oqw7wVY0/DD8a7XvzdcgSqIJ8e45LLLt/e4P6dikmvYOmslNGc 3c7YrlpPUwJgB2IdgdzoE0B8Jd6dITvwdbhueX/s/XsJoGSmoUMsb2jFWeW4wGNprm1Wy87 zzUKKIpDEbiPh18UHa+wZeyPZdyORwATSgjjs8UBVRW9DfFcppERh8WaiIweQVXTrn9uwd3 D/lKmFd4VF/WKXG2KS8lg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:l7kQeR809eg=:qNzJhp1XQQ8LmH98LXoIs+ znoQXUT7x2LkuuTduHNxzaWVLkpnp+msMWNtxIp3cJkw2UYTXn7z2P+rLD3zb4XhRGrWFw0YQ IdvEYIa6U7lHcvtvLi/BBeZQdje2CT/UXy1qWGrYa3zDzX+03904UNYjI5ls0c6Y7L7a/k10m BH32EFjtJbgEzQ1iv9Hg7lJOXhQvWhJ7qWgGK8ORl9i0hSCGoz1vqhjyqbcDUpxBTfziQn2Ro 5gGfhrqNNgDKBMUJcdQYDk4oIA2CSsODvhjg/JMa6/MM4Tkqjyf2P7qG66rf9VmrBUssVH9vT 5uESjzMgPiagzbi0z6yEA6rMj+fWmzE7///BpAHFvZVgATbMbJC2BQUTW42nIMpfLGhSgpYyO rrS7LeM3/G/0LvugipxEGqN2NtYN47Rt3oDg2O1n/9BKdkEZTuyOWY8x/jsWDtoN1qCA7Azbp jta20R7UVDUCuke9LQY1aLQtmuKjxgBD+4z72wJdSxTFcvKnp6BmYUYisfuHx2qoDpuXcylUc GqLUzh15GuV1/W5i808Wk2ukNo2mxjDaXfMjXp5n3XtXSH0s0Hk9dSyY0Pk4KJ6Ae6PdFflAj QxEq4tXzu3sOhdkMgzN7PUe850lzx2S3duzDBRIKL3rzcFELPFjoCdKsoYyRdipAjqEGqOoGz Uk8WKQfYpuX9APj45TJ6kQKmPVyXEiBGpvkTHw2djW4DRZ3tgGlKk0d+7ax/C77CfISu/PTAd fMvUn2oNaMtjs6ViAw8HivT370GLkIEttX3XA2WOcvGC8jt48quAZ8rVKCfaTmEY/5KwQMkn5 YJMSaBX
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oTXuRIHwhjvwtd4tsLfnCYvhacc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 07:47:29 -0000

On 2017-03-08 08:39, Julian Reschke wrote:
> On 2017-03-08 02:48, Benjamin Kaduk wrote:
>> I'm also concerned about the freewheeling use of Unicode.  While
>> this document does discuss the potential encodings and lists UTF-8
>> as the default (and most interoperable), I think it would benefit
>> from a stricter warning that parties using JSON for communication
>> must have some out-of-band way to agree on what encoding is to be
>> used.  I would expect that this is usually going to be done by the
>> protocol using JSON, but could see a place for the actual
>> communicating peers to have out-of-band knowledge.  (An application
>> having to guess what encoding is being used based on heuristics is a
>> recipe for disaster.)
>> ...
>
> AFAIU, there is no need for out-of-band knowledge (which would be very
> bad). Recipients are supposed to inspect the payload and detect which of
> the three encoding was used.
>
> That said, we probably should make that clearer.
>
>> ...
>> I'm also rather curious about the claim that no "charset" parameter
>> is needed as it "really has no effect on compliant recipients".  Why
>> is this not a good way to communicate whether UTF-8, UTF-16, or
>> UTF-32 is in use for a given text?
>> ...
>
> It might have been, but that's now how it is implemented.

s/now/not/



From nobody Wed Mar  8 00:49:54 2017
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 370EF129570; Wed,  8 Mar 2017 00:49:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b710WRAu6p_3; Wed,  8 Mar 2017 00:49:50 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07726129468; Wed,  8 Mar 2017 00:49:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v288nkNt029277; Wed, 8 Mar 2017 09:49:46 +0100 (CET)
Received: from eduroam-cart-clients-173.wlan.uni-bremen.de (eduroam-cart-clients-173.wlan.uni-bremen.de [134.102.145.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vdRzZ4WlPzDJ02; Wed,  8 Mar 2017 09:49:46 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de>
Date: Wed, 8 Mar 2017 09:49:46 +0100
X-Mao-Original-Outgoing-Id: 510655785.753134-e042b3f3f8d107f7b5e7cdf9db835f90
Content-Transfer-Encoding: quoted-printable
Message-Id: <6FEE55BE-10A8-4198-A4F0-4203BE0866F4@tzi.org>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ghfZ4XRDYnwj_0rHk9Wrkl9wt_o>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>, IETF <ietf@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 08:49:53 -0000

On 8 Mar 2017, at 08:39, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> > ...
>> I'm also rather curious about the claim that no "charset" parameter
>> is needed as it "really has no effect on compliant recipients".  Why
>> is this not a good way to communicate whether UTF-8, UTF-16, or
>> UTF-32 is in use for a given text?
>> ...
>=20
> It might have been, but that's now how it is implemented.

Indeed, and the reality is that JSON over UTF-16 or UTF-32 simply does =
not exist as an interchange format, so the algorithm is to always just =
assume UTF-8.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  8 01:35:59 2017
Return-Path: <lavanyahm@ece.iisc.ernet.in>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60984129452 for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 01:35:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cu1Sghlk2DaV for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 01:35:55 -0800 (PST)
Received: from relay.iisc.ernet.in (relay.iisc.ernet.in [14.139.128.66]) by ietfa.amsl.com (Postfix) with ESMTP id EF35A129446 for <ietf@ietf.org>; Wed,  8 Mar 2017 01:35:54 -0800 (PST)
Received: from ece.iisc.ernet.in (ece.iisc.ernet.in [10.32.1.10]) by relay.iisc.ernet.in (Postfix) with ESMTP id EAC13AE9D5F; Wed,  8 Mar 2017 15:05:45 +0530 (IST)
Received: from www.ece.iisc.ernet.in (ece.iisc.ernet.in [10.32.1.10]) by ece.iisc.ernet.in (8.14.7/8.14.7) with ESMTP id v289caIf019895; Wed, 8 Mar 2017 15:08:36 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 08 Mar 2017 15:08:36 +0530
From: lavanyahm <lavanyahm@ece.iisc.ernet.in>
To: ietf@ietf.org
Subject: IETF Hackathon98 - remote presentation
Message-ID: <026ee8a65aad5df788fb3af89780fdcc@ece.iisc.ernet.in>
X-Sender: lavanyahm@ece.iisc.ernet.in
User-Agent: Roundcube Webmail/1.2.1
X-IISc-MailScanner-Information: Please contact nethelp@serc.iisc.in for more information
X-IISc-MailScanner-ID: EAC13AE9D5F.A9393
X-IISc-MailScanner: Found to be clean
X-IISc-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-2.901, required 6.5, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, RP_MATCHES_RCVD -0.00)
X-IISc-MailScanner-From: lavanyahm@ece.iisc.ernet.in
MailScanner-NULL-Check: 1489570549.41924@X/wTJ8vfBT6iEqtPSydXzA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nQmh7PpFWfyOkjIyU5gh2VoSJJY>
Cc: ietf-secretariat@ietf.org, hackathon <hackathon-bounces@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 09:35:58 -0000

Hello All,

I have registered for the IETF Hackathon98 and I reside in Bangalore, 
India.
In this regard I would like to know if I can present my project 
remotely. If so, kindly let me know the venue and other information.

Regards,
Lavanya HM

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


From nobody Wed Mar  8 06:36:06 2017
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 5CA5F1296B5; Wed,  8 Mar 2017 06:36:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSmzqFUjnP5d; Wed,  8 Mar 2017 06:36:02 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A34041296A9; Wed,  8 Mar 2017 06:36:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id F4042BE77; Wed,  8 Mar 2017 14:35:59 +0000 (GMT)
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 NYmjPq8GKI5s; Wed,  8 Mar 2017 14:35:59 +0000 (GMT)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 51081BE3E; Wed,  8 Mar 2017 14:35:59 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1488983759; bh=Uu8z7VxxIRcfL9EVoVYxtCnl0fO1Gh1e0wZUphA06Zo=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=OE09aiWQM7Wgw8kAQ2bIDFp5uX039Ko7Z56ruk+vtz5g0p2CwoxECivkbnwy3N310 I/kUtvVqIexNcmyaRNEw+Jn8q4igifk8LorJUD2Dr6QWTTfaIc4ZrzWYa4lmfQkFE1 VICn5ujR1DWROjw2N0/6B/7cSgWbS2vuMvOV5A4I=
Subject: Re: Review of draft-ietf-dane-smime-15
To: Dale Worley <worley@ariadne.com>, gen-art@ietf.org
References: <148811824790.2888.13003369227902377285.idtracker@ietfa.amsl.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <8a3922c2-b8e4-e51b-77bc-b4db501ecaff@cs.tcd.ie>
Date: Wed, 8 Mar 2017 14:35:58 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148811824790.2888.13003369227902377285.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pBm3GRLI28rEaQhJdL4gUVR9eMplpVQgl"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k5IN0OLnTLkcBV20NTKzuP4Ii98>
Cc: draft-ietf-dane-smime.all@ietf.org, ietf@ietf.org, dane@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 14:36:05 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--pBm3GRLI28rEaQhJdL4gUVR9eMplpVQgl
Content-Type: multipart/mixed; boundary="fmsXoULrpvAf0LwULFfE3QvUPXuSuUNks";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Dale Worley <worley@ariadne.com>, gen-art@ietf.org
Cc: draft-ietf-dane-smime.all@ietf.org, ietf@ietf.org, dane@ietf.org
Message-ID: <8a3922c2-b8e4-e51b-77bc-b4db501ecaff@cs.tcd.ie>
Subject: Re: Review of draft-ietf-dane-smime-15
References: <148811824790.2888.13003369227902377285.idtracker@ietfa.amsl.com>
In-Reply-To: <148811824790.2888.13003369227902377285.idtracker@ietfa.amsl.com>

--fmsXoULrpvAf0LwULFfE3QvUPXuSuUNks
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi,

Thanks Dale for the detailed review and the discussion.

I've had a read through the resulting thread and don't
see anything that wasn't discussed in the WG that needs
a major change (please do yell if I've missed something),
so I'll leave this on the March 16th IESG telechat for
IESG evaluation. (In part to try get this document done
before I'm finished as an AD so we can cleanly close the
dane WG:-)

That said, I've not seen a response from the authors to
the details below, and it'd be good to see that, so
authors, please do reply to this and make any editorial
changes needed. If you can do have those changes done
by the end of Friday (or close-to) that'd be great so
it's not changing while the IESG are reading it.

Thanks,
S.


On 26/02/17 14:10, Dale Worley wrote:
> Reviewer: Dale Worley
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft.  The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document:  draft-ietf-dane-smime-15
> Reviewer:  Dale R. Worley
> Review Date:  2017-02-26
> IETF LC End Date:  2017-03-03
> IESG Telechat date: 2017-03-16
>=20
> Summary:  This draft is basically ready for publication, but has nits
> that should be fixed before publication.
>=20
> * Technical points
>=20
> 1. I assume that in parallel with RFC 6698, DNAME records must be
> followed during SMIMEA resolution.  It's not clear to me whether
> CNAME
> records must also be followed or how, given that SNAMEA records are
> not for host names, but their grandparent node is a host name.
>=20
> 2. Presumably it was deliberate not to have the first label for an
> SNAMEA record be the canonical UTF-8 string for the local-part, even
> though the DNS architecture (RFC 1035) seems to admit binary labels.
>=20
> 3. Presumably it was deliberate to hash using SHA2-256 truncated to
> 224
> bits rather than use SHA-224.
>=20
> 4. Is it worth suggesting that some mechanism might be devised for
> annotating an e-mail message with the canonical form of the sender's
> local-part that is intended to be used to authenticate the message?
> The last sentence of the 1st paragraph of section 1 suggests that
> this
> is deliberately out of scope for this document, but it might be worth
> suggesting experimentation regarding this in section 4, which seems
> to
> be entirely about further experimentation.
>=20
> * Editorial/Nits
>=20
> Should there be an explicit statement that the resolver must follow
> CNAME and DNAME records?  That seems to be required by RFC 6698
> section A.2.1, but that requirement is buried rather deeply.  Also,
> is
> CNAME following required?  My vague understanding is that CNAME can
> only be used to alias host names, and SMIMEA records are not for host
> names (contrasting with the DANE records for TLS) -- though the
> grandparent node of any SNAMEA is a host name.
>=20
> Also, some adjustments of the resolution process of RFC 6698 re CNAME
> records were made in RFC 7671, but this draft only mentions 7671 in
> passing, in the introduction.  It seems that it should be noted that
> 7671 contains a lot of operational information about DANE.
>=20
> 1.  Introduction
>=20
>    There are other requirements on the MUA, such as
>    associating the identity in the certificate with that of the
> message,
>    that are out of scope for this document.
>=20
> "that of the message" isn't quite right, as "that" is parallel to
> "the
> identity", and the message doesn't itself have an identity.  More
> accurate would be "the purported sender of the message", as was used
> in 3rd sentence of the paragraph.
>=20
> 2.  The SMIMEA Resource Record
>=20
>    ... the semantics are also the same except
>    where RFC 6698 talks about TLS at the target protocol for the
>    certificate information.
>=20
> s/TLS at/TLS as/
>=20
> 3.  Location of the SMIMEA Record
>=20
>    The DNS does not allow the use of all characters that are
> supported
>    in the "local-part" of email addresses as defined in [RFC5322] and
>    [RFC6530].
>=20
> I don't have the full background on this.  My memory ends at RFC
> 1035:
>=20
>     Although labels can contain any 8 bit values in octets that make
> up a
>     label, it is strongly recommended that labels follow the
> preferred
>     syntax described elsewhere in this memo, which is compatible with
>     existing host naming conventions.
>=20
> I suspect there is by now a defined way to have "UTF-8 labels".=20
> Given
> that this draft doesn't use such a mechanism, there's probably a
> discussion out there why just using a UTF-8 string as a label doesn't
> work.  It would be helpful to put a reference to that discussion
> here,
> because the mechanism in the draft is doing a lot of work to avoid
> the
> seemingly obvious mechanism.
>=20
>    2.  The local-part is first canonicalized using the following
> rules.
>        If the local-part is unquoted, any whitespace (CFWS) around
> dots
>        (".") is removed.  Any enclosing double quotes are removed.=20
> Any
>        literal quoting is removed.
>=20
> I think this could be more exactly expressed along the following
> lines.  Given the costs of not having this implemented exactly the
> same way in all implementations, it's probably worth the extra words.
>=20
>    2.  The local-part is first canonicalized using the following
>        rules.  If the local-part is unquoted, any whitespace (CFWS)
>        around dots (".") is removed.  If the local-part is quoted,
> the
>        enclosing double quotes, contained FWS, and the initial
>        backslashes of quoted-pairs are removed.  (The obsolete
>        local-part format obs-local-part is canonicalized similarly:
>        CFWS around dots is removed and any word component that is a
>        quoted-string is canonicalized as if it was a separate
>        local-part.)
>=20
> --
>=20
>    4.  The local-part is hashed using the SHA2-256 [RFC5754]
> algorithm,
>        with the hash truncated to 28 octets and represented in its
>        hexadecimal representation, to become the left-most label in
> the
>        prepared domain name.
>=20
> Why use "SHA2-256 [RFC5754] algorithm, with the hash truncated to 28
> octets" rather than "SHA2-224 [RFC5754]"?  (The two aren't the same,
> because SHA-224 has a different IV than SHA2-256, but they seem to
> have the same security properties.)  Is this because implementations
> will already implement SHA2-256 (for matching type 1)?
>=20
> You probably want to specify hexadecimal case here.  DNS is
> considered
> to be case-insensitive, but it's probably unwise to depend on that
> fact.  (Or is this known not to be a problem in DNS?)
>=20
> 7.  Certificate Size and DNS
>=20
>    The algorithm type and key
>    size of certificates should not be modified to accommodate this
>    section.
>=20
> The term "algorithm type" is not defined; what is meant here?  Also,
> "of certificates" seems awkward; the encryption/signing algorithms
> and
> keys exist prior to the certificate which vouches for them.  Perhaps:
>=20
>    A user's S/MIME encryption/signing algorithms and keys should not
>    be changed solely to reduce DNS RR sizes.
>=20
> 9.  Security Considerations
>=20
>    If an obtained S/MIME certificate is revoked or expired, that
>    certificate MUST NOT be used, even if that would result in sending
> a
>    message in plaintext.
>=20
> Shouldn't this be moved to section 6?  This seems to be a
> specification, but it is not contained in the definition of the
> semantics.  The "security considerations" section is where you would
> see the explanation of the reason for this specification.
>=20
> [END]
>=20
>=20
>=20


--fmsXoULrpvAf0LwULFfE3QvUPXuSuUNks--

--pBm3GRLI28rEaQhJdL4gUVR9eMplpVQgl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYwBbOAAoJEC88hzaAX42irwYIAKsaW04XF3Z4n8qima2JZDCH
XauRswKlVaGg+kwYXD60KDFI6bHP+iWSyXiHgvVltHMAvjGzIB1gljHLTsJkFL/D
QNW2CKe+VubCx/i8SRdis0jDnopJ052AqDyCw/r/F2QwRxgtRoTehBdtOTqErEBa
cRfrP/OjLfSc+G5ATfvkuitMaxHnMMZOZJBF9Za2GPCWxyt3KrRJazpMjVmUja4m
iWF499N7EV53ZKPu6Pps4zyPNoJnPSUkmkfLYTEFhLPgbXRdLwJtesu/oBTGZvhl
4Mi/U4JDWIJpX/d2o2PNtM+Phhsdl4SUOARsOZ0eX3S89B9tUb1ExTbK1fBAL+M=
=goyg
-----END PGP SIGNATURE-----

--pBm3GRLI28rEaQhJdL4gUVR9eMplpVQgl--


From nobody Wed Mar  8 08:22:32 2017
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 91D21126DFB; Wed,  8 Mar 2017 08:22:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7K7OAnCzeD2o; Wed,  8 Mar 2017 08:22:29 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A59911293FB; Wed,  8 Mar 2017 08:22:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 359FEBE74; Wed,  8 Mar 2017 16:22:27 +0000 (GMT)
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 g7VJ91IF2gm0; Wed,  8 Mar 2017 16:22:26 +0000 (GMT)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 80A11BE5C; Wed,  8 Mar 2017 16:22:26 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1488990146; bh=lY6U4W5VBenuNRZ4o8uth1UN4sqP7TcC5DK94bv2Vbo=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=Jhx9pK7lqgDgPkkiVbIStuwtRRFnndGn8Xjui467XoiO48ItlD7LZOFPfXg4vMgJ3 wQVixcWIc5qY3pHTXfFIwePDzwCZSq33B35YgtKVisXLQEE8gusnvIJ0YAxNgPXIaP zUY7V1PkJ7WWRNdTcEIEAy1T4oQyngNinxsbvE88=
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: IETF general list <ietf@ietf.org>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org> <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie>
Date: Wed, 8 Mar 2017 16:22:25 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="quAp4X6UJvPOAv7q2DWUgEAos2xxHDs4F"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G-UGc8g7U__5sYvLxHVWlz9n5z8>
Cc: "spasm@ietf.org" <spasm@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 16:22:31 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--quAp4X6UJvPOAv7q2DWUgEAos2xxHDs4F
Content-Type: multipart/mixed; boundary="v4rPmfsUwDLw1amHFe2u3QOqS6PrrkQbG";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: IETF general list <ietf@ietf.org>
Cc: "spasm@ietf.org" <spasm@ietf.org>
Message-ID: <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt>
 (Internationalized Email Addresses in X.509 certificates) to Proposed
 Standard
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy>
 <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com>
 <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org>
 <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie>
In-Reply-To: <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie>

--v4rPmfsUwDLw1amHFe2u3QOqS6PrrkQbG
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

So I don't think we've yet resolved the issues raised
with this. And since the March 16th telechat will be my
last one I figure that the best thing to do is to ask
that this go back to the working group for resolution.

Once that's sorted out, then the WG can kick it over
to their new AD. Note that this need not add any major
delay - it'd be entirely possible to have it back on a
telechat agenda shortly after IETF98, all going well.

If nobody yells, I'll do that tomorrow.

If someone does yell, please do that now and accompany
your yell with the OLD/NEW changes that you claim resolve
the issues raised. (To be honest though, I think this
would benefit from more WG discussion so I'll not be so
easy to convince if someone does yell thusly;-)

Cheers,
S.

On 23/02/17 20:16, Stephen Farrell wrote:
>=20
> Folks,
>=20
> I've just reviewed the IETF LC for this draft. Thanks all for
> the comments and discussion which I think have thrown up some
> real issues.
>=20
> As of now, it is not clear to me that we have finished the
> work with this one, at least the issues to do with name
> constraints seem to me to call for some more WG consideration.
>=20
> I think Russ (as lamps WG chair) has a similar opinion
> that we're not done yet.
>=20
> That said, I had put this on the March 16th IESG telechat
> for consideration. If we do manage to reach a clear enough
> consensus on a published revision to the draft in say the
> next week then that schedule should still be fine. So I'd
> encourage the authors and others who've commented to try
> again and see if, in that timeframe, we can get to where
> we're happy that the issues raised have been handled well
> enough.
>=20
> But, if it looks (as it does to me today) as if this'll take
> a bit longer to figure out, then I figure the right thing to
> do will be to let the lamps WG figure out how to proceed.
> (And that'll mean that my successor as the responsible AD
> for the lamps WG will handle further actions with the doc.)
>=20
> Bottom line: if this isn't settled in the next week or so,
> I'll take it off the March 16th IESG telechat and let the WG
> continue the discussion.
>=20
> Cheers,
> S.
>=20
> PS: To add to the name constraints discussion, I did wonder
> if anyone really wants to use those. So for example, if we
> defined the new name form so that certificate chains with
> any name constraints at all and one of those names anywhere
> are always treated as invalid, then would that cause any
> real breakage? (It certainly would cause theoretical breakage,
> but if that's all then I'd be ok with that:-)
>=20
>=20
>=20


--v4rPmfsUwDLw1amHFe2u3QOqS6PrrkQbG--

--quAp4X6UJvPOAv7q2DWUgEAos2xxHDs4F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYwC/BAAoJEC88hzaAX42iocYIALp9f0AnHtixvM+KOZO8nn8d
0cwBZZzvEtSfWNzvWyMOk5rzTjAAdfLwSegfc90n563fosY5LXhhgbfuzURpztOs
EHNj7myTkUhI08LuwPGqs/FIS4p79JH5h1R3bW7im+KstENOV8aB3XlrZkBCMHyj
YP4XvC62TVFxO60QF0LZaokjStiMJbEv603eK0aH0US0sHLdJnyBswKhcJYbzB6J
pV8jp3OR9TH0O2lbUmHo3I1W2zGjgAKfgbT/B9bSt0PsuvidZfkNIgiR9giLCKAI
ZtFMxPbAnQ8kijKaGPwLWsYDeT15/oS/e+8pI/tWo9dj+ss1ehMftTqDWMDN7b4=
=TY2X
-----END PGP SIGNATURE-----

--quAp4X6UJvPOAv7q2DWUgEAos2xxHDs4F--


From nobody Wed Mar  8 08:54:22 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 830CD1295CA; Wed,  8 Mar 2017 08:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3htr6rfER5Gi; Wed,  8 Mar 2017 08:54:19 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94A761295F2; Wed,  8 Mar 2017 08:54:18 -0800 (PST)
Received: from [192.168.1.34] ([5.10.171.186]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MNqcR-1ct4R72TFL-007S6X; Wed, 08 Mar 2017 17:54:10 +0100
Subject: Re: Last Call: <draft-ietf-jsonbis-rfc7159bis-03.txt> (The JavaScript Object Notation (JSON) Data Interchange Format) to Internet Standard
To: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com> <CAC4RtVDuoKFoCckrDYLPKxC2Oj_Ctr9vZSAALBMBk=foW2MdzA@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <f0453539-bc8f-f5cd-d50b-0d5592355924@gmx.de>
Date: Wed, 8 Mar 2017 17:54:09 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAC4RtVDuoKFoCckrDYLPKxC2Oj_Ctr9vZSAALBMBk=foW2MdzA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:0EBULuRrIaEOP9mq3WYOHIk/iGpQmn5GhqA8UBSiukl91r7fasZ OmDoOdm0v7iL5V0bqkFPacymmpV9vZnbEOvv2kohz5BejF75nrWBKIN8IPy4h4CWtcT/aBZ HI2VHlLUvUvlBp7A7eBVG2IhqrbxitwxEFYR2qTupbdiV0M+iIMR1zlAgRrXIH+azMxdU26 3xdJltXDJ8AuqGxmITwKQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:v0cfFMDJEqo=:5b6eUxVlXy77OTvdbR7UDi auXXJSGXZqkMqGpKvkDjgs1ycTdCGEPUe93EW0ohQVjMOYsAnCLUQRf8gXctTM+K4yOZ7XNUR THPQ+W9KLtYGwyrwQkxh4YFGskZebsUrIXHCSstqKCjT2et0sHCPpZ2rLkc8P4yKwH3t9/u4O w/Het1teWetwBXTv0IUlyPR9Hh3RU3LcXWekF98UXj4rlFtvnWi7OiWp3WSNfRjqP37opqXYx stItlLQ8qt55JcZqNPSuL3Vek+DnFMLD+6Mc3/fKP81nkYr5MspZKe2QMyHDMRHp88EKeMM6U Xxr6sROM9MT8D0f/mBJjP6ttCu2wx8yg9gQ4k48LUKvtyUggKjWTWdX/AOFRxzw1/A//hGqYm pY0qIToAxIm3FKLzKYA9EenD8cZEXtU5VXfPA1Je5ifP0FmRSsuwPhk9LxOAEkXQgKZNHA4DR oo2N1zca1PIzGPEJ2Z1zMA2AKRBhF6tsS/9XX72Dd4ZSY3qCRmSfEVwQPnFnEiJ0RIUZqHSBz ITzW0+6D2mwBi6GnMxCZ5uVoXPi4GQpXffJyc8E36ECDB4r0sDdiVX7T1SlA3D1s6hHdeY/5s Dx55M+hcE9+ODNdGt26ljm7YSW/ZpwGB/qNjZ8UgYa2/w7IHPenRkjlFzuGKg7pWLdR0rH0JH LCRYWALcf8R7zN1mzyE3fbRq3fcnd6O63VSvpSGt1YOW4jsMCkpmg4NJQlB7FvvpHesgWrXc+ PjV6R8mxjapKxXfeRgK061u2hQiAnRHH1Kss/9RyHiKYJz4mOEya0lE2JAKQGEtrbQwhspyMS jQ6USJQ
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AFLjk-qIzRGj_tQs2v2U-OEaIFM>
Cc: Matt Miller <mamille2@cisco.com>, Alexey Melnikov <alexey.melnikov@isode.com>, draft-ietf-jsonbis-rfc7159bis@ietf.org, jsonbis-chairs@ietf.org, "json@ietf.org" <json@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 16:54:20 -0000

On 2017-02-21 23:01, Barry Leiba wrote:
> ...

Looking at 
<https://tools.ietf.org/rfcdiff?url2=draft-ietf-jsonbis-rfc7159bis-03.txt&url1=rfc7159>, 
I see:

"Section 15.2 has been updated to remove ECMA 404, update the version of 
ECMA-262, and refresh the errata list."

However, the ECMA-262 reference changes from

>    [ECMA-262] Ecma International, "ECMAScript Language Specification
>               Edition 5.1", Standard ECMA-262, June 2011,
>               <http://www.ecma-international.org/publications/standards/
>               Ecma-262.htm>.

to

>    [ECMA-262]
>               Ecma International, "ECMAScript Language Specification,
>               Third Edition", Standard ECMA-262, December 1999,
>               <http://www.ecma-international.org/publications/files/
>               ECMA-ST-ARCH/
>               ECMA-262,%203rd%20edition,%20December%201999.pdf>.


...which looks like a downgrade to me.

I believe this should be:

>    [ECMA-262]  Ecma International, "ECMAScript(R) 2016 Language
>                Specification, 7th Edition", ECMA 262, June 2016,
>                <https://www.ecma-international.org/ecma-262/7.0/>.

Best regards, Julian


From nobody Wed Mar  8 09:02:10 2017
Return-Path: <linuxwolf+ietf@outer-planes.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 C3021129621 for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 09:02:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mg6L5bajuKSF for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 09:02:07 -0800 (PST)
Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB811129554 for <ietf@ietf.org>; Wed,  8 Mar 2017 09:02:07 -0800 (PST)
Received: by mail-it0-x244.google.com with SMTP id f203so6404631itf.2 for <ietf@ietf.org>; Wed, 08 Mar 2017 09:02:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=V7770Qlw3vBIwJcROjdvN9VO5CwoEY/jF9eEq2rbaWk=; b=NFJAadvZ4X+AAYhrtN5M4GWUfTGr32DmZf0Pg4KrfGBkhaqq334co2UtmdNo21Xbey QuEhKihY8MQ6qRh3XCHCoZzlU1Sil021gt42xBrHWG/buHFyIQ3i9xBF64RMUMUmvto7 7W5COOmggMgygso7fqe+Q7vgO5QpGNp+lzrjPnOzVFsUWu03rVrvjzRX1nB3X1i9NRyc HS4pIXH32SzyAXbbhDG04+/Iz1Ic5/aS7Dm6BM1Sy/9L/B2RYRn3UiMkW76awIrkR0RI otRzP2V24IvKaMJL2HNbSqOe0D+smuuxaHd7BHmJLgyVaFhU011IFGE3LpEQ8INchjE3 legQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to; bh=V7770Qlw3vBIwJcROjdvN9VO5CwoEY/jF9eEq2rbaWk=; b=cqwg/2JV5/wAL2c1Q8yrlDMruARmOHVd/4Bw6GbWinNaBHWorbDp7Z19LvKjMfg4sh SJ0au+mAsM/1e0jsswkOYFOgySCe45CTpFQyZPcGapaF1X/f2WPYo+oHDDcZW/myzJFi VjwIU7AQzQ2+vEQJnriw8JofvsJll2jKOA3tG/W4EejlWFXP/l3m1WnciOXYiGWn80jP y5GcITKFw7/jIhCItKMkuKRXyjam/ANcW7rEReAtpztmxHz+3+B01+ZXMPUyuYwhMwqt ZTFdzp0saSEXAWQVByIRJEDEgoTTCuPgh9Lz88Dp1cOpwJd3Y3PSHCKHTByYbw+lHnSj VYgA==
X-Gm-Message-State: AMke39l9otUACSNVxSx0SITGnKhekDwSK+Y1HjIBUaBNsVZ5RrObALD4aoT+xcflBBdbAg==
X-Received: by 10.36.44.12 with SMTP id i12mr7149576iti.92.1488992526939; Wed, 08 Mar 2017 09:02:06 -0800 (PST)
Received: from [192.168.29.239] (c-73-217-32-196.hsd1.co.comcast.net. [73.217.32.196]) by smtp.gmail.com with ESMTPSA id b88sm7896813itd.21.2017.03.08.09.02.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Mar 2017 09:02:06 -0800 (PST)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
Subject: Re: Last Call: <draft-ietf-jsonbis-rfc7159bis-03.txt> (The JavaScript Object Notation (JSON) Data Interchange Format) to Internet Standard
To: Julian Reschke <julian.reschke@gmx.de>, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com> <CAC4RtVDuoKFoCckrDYLPKxC2Oj_Ctr9vZSAALBMBk=foW2MdzA@mail.gmail.com> <f0453539-bc8f-f5cd-d50b-0d5592355924@gmx.de>
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
Message-ID: <25d4b0e3-d59f-ca30-0a8c-dae40569b5c0@outer-planes.net>
Date: Wed, 8 Mar 2017 10:02:04 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <f0453539-bc8f-f5cd-d50b-0d5592355924@gmx.de>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tD6osuXSiSV4Ca1t86IgmFavwpMAWa6Ts"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rsCOGULBeMNErLgG5ctsT5L1--Q>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, draft-ietf-jsonbis-rfc7159bis@ietf.org, jsonbis-chairs@ietf.org, "json@ietf.org" <json@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 17:02:10 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--tD6osuXSiSV4Ca1t86IgmFavwpMAWa6Ts
Content-Type: multipart/mixed; boundary="WiCShMOauoKiajBVU14KKvEQNM7kQkjaf";
 protected-headers="v1"
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: Julian Reschke <julian.reschke@gmx.de>,
 Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
Cc: "json@ietf.org" <json@ietf.org>,
 Alexey Melnikov <alexey.melnikov@isode.com>,
 draft-ietf-jsonbis-rfc7159bis@ietf.org, jsonbis-chairs@ietf.org
Message-ID: <25d4b0e3-d59f-ca30-0a8c-dae40569b5c0@outer-planes.net>
Subject: Re: Last Call: <draft-ietf-jsonbis-rfc7159bis-03.txt> (The JavaScript
 Object Notation (JSON) Data Interchange Format) to Internet Standard
References: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com>
 <CAC4RtVDuoKFoCckrDYLPKxC2Oj_Ctr9vZSAALBMBk=foW2MdzA@mail.gmail.com>
 <f0453539-bc8f-f5cd-d50b-0d5592355924@gmx.de>
In-Reply-To: <f0453539-bc8f-f5cd-d50b-0d5592355924@gmx.de>

--WiCShMOauoKiajBVU14KKvEQNM7kQkjaf
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 17/03/08 09:54, Julian Reschke wrote:
> On 2017-02-21 23:01, Barry Leiba wrote:
>> ...
>=20
> Looking at
> <https://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-jsonbis-rfc7159bis-03=
=2Etxt&url1=3Drfc7159>,
> I see:
>=20
> "Section 15.2 has been updated to remove ECMA 404, update the version o=
f
> ECMA-262, and refresh the errata list."
>=20
> However, the ECMA-262 reference changes from
>=20
>>    [ECMA-262] Ecma International, "ECMAScript Language Specification
>>               Edition 5.1", Standard ECMA-262, June 2011,
>>               <http://www.ecma-international.org/publications/standard=
s/
>>               Ecma-262.htm>.
>=20
> to
>=20
>>    [ECMA-262]
>>               Ecma International, "ECMAScript Language Specification,
>>               Third Edition", Standard ECMA-262, December 1999,
>>               <http://www.ecma-international.org/publications/files/
>>               ECMA-ST-ARCH/
>>               ECMA-262,%203rd%20edition,%20December%201999.pdf>.
>=20
>=20
> ...which looks like a downgrade to me.
>=20
> I believe this should be:
>=20
>>    [ECMA-262]  Ecma International, "ECMAScript(R) 2016 Language
>>                Specification, 7th Edition", ECMA 262, June 2016,
>>                <https://www.ecma-international.org/ecma-262/7.0/>.
>=20
> Best regards, Julian

Hello Julian,

the rationale for referencing third edition specifically is to give
evidence of the JSON's specification history.  Maybe the word "update"
is debatable here, but I think the reference itself is valid.


- m&m

Matthew A. Miller


--WiCShMOauoKiajBVU14KKvEQNM7kQkjaf--

--tD6osuXSiSV4Ca1t86IgmFavwpMAWa6Ts
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYwDkNAAoJEOz0ck4QngW76vwH/AlmDy/qPE7RPpod2SmUHHz0
+zrtZo0Zy/WduZxvmgBXs2JD0Ce+FqjTmpTYUVSK/mTf7vPpK4WWxdAjn+Q7vOlr
Mu3b6RPRKGVbphOvZVIQbVZKnz5kI1T4IsOCquY93KDlOB2RdMs1vqBxpkJ0Plas
IQoN0pnVGtcdWweO6sloy+8VN6lIpDRcN7YaETnTvNPikv87z1iWViKtZ9yZwufo
auRvpsXwk32bT0jHnjQBwQKNtMkcdY9R33h/+vNnYCBf3PaIkvri6h9Nc2ZFFzGI
CZAi0uzmXknFFMgXGgwY95eoLAZQJ/m2PuPDpd7U/MNL02gcZo72RcR6m5WO6Rg=
=CWCJ
-----END PGP SIGNATURE-----

--tD6osuXSiSV4Ca1t86IgmFavwpMAWa6Ts--


From nobody Wed Mar  8 09:08:19 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C582A12952C; Wed,  8 Mar 2017 09:08:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P5FyIO9gKEP0; Wed,  8 Mar 2017 09:08:12 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A972129524; Wed,  8 Mar 2017 09:08:12 -0800 (PST)
Received: from [192.168.1.34] ([5.10.171.186]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MZxch-1cYFaJ08g3-00LnUM; Wed, 08 Mar 2017 18:08:08 +0100
Subject: Re: Last Call: <draft-ietf-jsonbis-rfc7159bis-03.txt> (The JavaScript Object Notation (JSON) Data Interchange Format) to Internet Standard
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com> <CAC4RtVDuoKFoCckrDYLPKxC2Oj_Ctr9vZSAALBMBk=foW2MdzA@mail.gmail.com> <f0453539-bc8f-f5cd-d50b-0d5592355924@gmx.de> <25d4b0e3-d59f-ca30-0a8c-dae40569b5c0@outer-planes.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <1d5419fc-875f-394b-5371-4d53c9064aae@gmx.de>
Date: Wed, 8 Mar 2017 18:08:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <25d4b0e3-d59f-ca30-0a8c-dae40569b5c0@outer-planes.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:3VjjbSBz2DADqPxSCkyLCYnSZiW6HVZJtpctZIXMqqafUOOJs/k Kv1eRaYvDHd2dE5QWLbs3F2xNhwEpGslvMetX3ON1eAkfCcuytQllQuwTeZJjRPXtx8/jmH PIR7+XHUhGl7++DNImar8Hwbo2rU8pUR+Z/XXr+4NsOMPnAESZleuo7vxE7VhTpq3GF3XFi rUBalg6pJl7jo4X/aIu3w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:xWTHgRELCEA=:WcGsv3xs3qd+YMt5IrbXrg wTfl7vVek5ItyHUGoBbeeDUEcOLtcfDIOILdt/4sKzRwinTPvJwyAY3ghBwN4MjgXVJfCF2ce lbx6n3wXVyEaLOpVuPD79z4NQWPQ/SFzrTdd5QjKseYTpHnldNJqK5mHvw3M3EsvXmG5tT+jF Wy/xQGOqb9nUu4lEgG2PP7FNzfDR19PDta3Gjoye44xGJuwDg2gPNfuwsbtLfAiqQ4rBp438w OXeOlVGz8UNJTaRwSFAdYfxvHe/E0yljgawaQp+K0bgUT+Cz8XEKmFiUwGplH+3UJktBN6I8b 4M3QMiBaimKoj24w4iTxxYJg6f3FThzoa3OtI8W6lvI6Fxms8H59NGlWx2PhaNmctP3E07St9 4jJZ0y5y1Wsx7ydxHRCqIeUo2HirZTP1Ym9YLdgejNYcdIeYzw5zwcpvOZQ7bzDGa+u0OVzig 0fP4z0FJJGHSglC0Pu4+KnsSdVRv8xl3eWBXc0OATGQ9Fj5wpm4nHvzC45XTMlKGFB5XiTrxn C8wWplhZScXARdV/zE65ekUSSNfS0aNEyI8Jubw/qcmgorgMRAqu+P4S5T3ty0CWdVRhtG4OA uRl6QckUNjK8H6orkOLgMNx7E066y5xEWBA4JCu+E10cgUuFp0qUTx8p42Y0fr4ukwWICaZ94 sTc0RHljuMePKzSYFnRfZq9+7soohqJfX+e0FcRI7KvKkA30sn6Csk9Shog4jfA48sYPCKImO 5qdEBnunez9E1S5XIykKLV11ZgAJOT1pgwN4oJYhRWbbT9yDTABTudm7iNfY8tKrYrYECsgq7 qBQH0+p
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YwqxCz7Kb3Q-YeMQ0IVTPcE4QbE>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, draft-ietf-jsonbis-rfc7159bis@ietf.org, jsonbis-chairs@ietf.org, "json@ietf.org" <json@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 17:08:14 -0000

On 2017-03-08 18:02, Matthew Miller wrote:
> ...
> the rationale for referencing third edition specifically is to give
> evidence of the JSON's specification history.  Maybe the word "update"
> is debatable here, but I think the reference itself is valid.
> ...

Well. In that case, why is the 3rd edition a specifically good one to cite?

Best regards, Julian


From nobody Wed Mar  8 09:14:04 2017
Return-Path: <linuxwolf+ietf@outer-planes.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 147671297BD for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 09:14:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XhN88xfEJPpL for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 09:14:02 -0800 (PST)
Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705941297B8 for <ietf@ietf.org>; Wed,  8 Mar 2017 09:14:01 -0800 (PST)
Received: by mail-it0-x241.google.com with SMTP id f203so6486756itf.2 for <ietf@ietf.org>; Wed, 08 Mar 2017 09:14:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=HnmsjfEd7NZT+EO6ECYRJbsWfymUQe8KPGyLEYbGrlU=; b=ajlbCgs6j3RPqQiFZ/I2Xx3PoqoSt53KeGkPwf+DC1bor6KR9i3MFZGtqdwwPssxtp ek9VgZeIYM8+pQZgPkKV4p05cYkG5a8VWXZAma9M+z2DpmiGoHzcl1Yr++7+ZEiOcqEh sICcjX2fZelC1s3rFq7xq6EaNvB/5psAYxPqBIt8oZnEW8NdwGNYQLOpg8CjWXOqbxnP IiqhOTfyGnGt8+yOWiFdJu/fIt/i7PuSHwaWSBWUT6Q6IC1tmf4xJxTp0VeiySWVHjEP 5W/o1m6hf2/4Fi23jvDtooouF+XRTjhwV4l+LTkIqqk0ABUKI4zuYrfTK+FW1dcSZpgY B5mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to; bh=HnmsjfEd7NZT+EO6ECYRJbsWfymUQe8KPGyLEYbGrlU=; b=dLWzi+lxVH3JLlNGoLEn62yHek2ZM2O17CpdnMu2st5dCmv+Fa9QkMM8nAh0kOBQjz ry6bQBcp+sBSDdrxizZTfJQuupVOk92s7+yTR9kqDvyf2r5Y3io/Nq/wqzzfRMJexe/N 5Vg81MYkkQPKCSWBMGDHb97Nspe++3vsmxzzVhfJRk3ijAc9tOmt5EzpVhp6RrRArg8O S/xKMI80A6n6BlmQcSwfKFkpZHGkxdgnsdpEwbPf+nujIFEN5O9QFZlNK41XqKbt5pil CJT9+UUnTSoQ1fKZSGjlCfYk5lAvrn32ZnEKXB3aB6rmg8RYVjsUsuyKY2oPqajn/9vf fi3A==
X-Gm-Message-State: AMke39nB+V+8ZZtD7iTKaJF0ZEd97CVqaVqEeMkBVryeTZdkR7dcbtyphbn4Wxmw+7nzbA==
X-Received: by 10.107.19.97 with SMTP id b94mr7017931ioj.93.1488993240704; Wed, 08 Mar 2017 09:14:00 -0800 (PST)
Received: from [192.168.29.239] (c-73-217-32-196.hsd1.co.comcast.net. [73.217.32.196]) by smtp.gmail.com with ESMTPSA id g200sm1760651ioe.28.2017.03.08.09.13.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Mar 2017 09:14:00 -0800 (PST)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
Subject: Re: Last Call: <draft-ietf-jsonbis-rfc7159bis-03.txt> (The JavaScript Object Notation (JSON) Data Interchange Format) to Internet Standard
To: Julian Reschke <julian.reschke@gmx.de>, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com> <CAC4RtVDuoKFoCckrDYLPKxC2Oj_Ctr9vZSAALBMBk=foW2MdzA@mail.gmail.com> <f0453539-bc8f-f5cd-d50b-0d5592355924@gmx.de> <25d4b0e3-d59f-ca30-0a8c-dae40569b5c0@outer-planes.net> <1d5419fc-875f-394b-5371-4d53c9064aae@gmx.de>
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
Message-ID: <6726c1a4-1856-f53e-4caa-e72a25f51511@outer-planes.net>
Date: Wed, 8 Mar 2017 10:13:58 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <1d5419fc-875f-394b-5371-4d53c9064aae@gmx.de>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="nvrIllvQKCAPHD4bq0Q8B7sMnJiAUXIfV"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xbvIrjFNdv2ErAQ8_hszSaUkESs>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, draft-ietf-jsonbis-rfc7159bis@ietf.org, jsonbis-chairs@ietf.org, "json@ietf.org" <json@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 17:14:03 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--nvrIllvQKCAPHD4bq0Q8B7sMnJiAUXIfV
Content-Type: multipart/mixed; boundary="m86GTmpe80lFfNrmK5xNpTORs86Oe6xwm";
 protected-headers="v1"
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: Julian Reschke <julian.reschke@gmx.de>,
 Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
Cc: "json@ietf.org" <json@ietf.org>,
 Alexey Melnikov <alexey.melnikov@isode.com>,
 draft-ietf-jsonbis-rfc7159bis@ietf.org, jsonbis-chairs@ietf.org
Message-ID: <6726c1a4-1856-f53e-4caa-e72a25f51511@outer-planes.net>
Subject: Re: Last Call: <draft-ietf-jsonbis-rfc7159bis-03.txt> (The JavaScript
 Object Notation (JSON) Data Interchange Format) to Internet Standard
References: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com>
 <CAC4RtVDuoKFoCckrDYLPKxC2Oj_Ctr9vZSAALBMBk=foW2MdzA@mail.gmail.com>
 <f0453539-bc8f-f5cd-d50b-0d5592355924@gmx.de>
 <25d4b0e3-d59f-ca30-0a8c-dae40569b5c0@outer-planes.net>
 <1d5419fc-875f-394b-5371-4d53c9064aae@gmx.de>
In-Reply-To: <1d5419fc-875f-394b-5371-4d53c9064aae@gmx.de>

--m86GTmpe80lFfNrmK5xNpTORs86Oe6xwm
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 17/03/08 10:08, Julian Reschke wrote:
> On 2017-03-08 18:02, Matthew Miller wrote:
>> ...
>> the rationale for referencing third edition specifically is to give
>> evidence of the JSON's specification history.  Maybe the word "update"=

>> is debatable here, but I think the reference itself is valid.
>> ...
>=20
> Well. In that case, why is the 3rd edition a specifically good one to c=
ite?
>=20
> Best regards, Julian

Third Edition is where the object literal syntax (from whence JSON was
begotten) made its appearance.  Also, the latest editions of ECMA-262
doesn't discuss JSON the data format; that is what (for them) ECMA-404
is for.


- m&m

Matthew Miller


--m86GTmpe80lFfNrmK5xNpTORs86Oe6xwm--

--nvrIllvQKCAPHD4bq0Q8B7sMnJiAUXIfV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYwDvXAAoJEOz0ck4QngW7PhwIAL8gYbUArmQjygv4oYXpSIU3
AmFueCo1VucqSXMKImSN2olWkwrPqnBPppd8YIStjNzX72WFjOrN76mdfY6mbt7q
9dt9ZQ/GrBs8FcbVpHRpL1P2p+9SdXqi69B97b3haUK2vEZ2cXwbw7xGcpSZLHK6
/cTRkpTFBXKrzu14semSVPAM5TX8ns6HGDp3MkYRc4ZAoAkODfIemFODy11/RQt/
VoXXIw4vBfeeWfrHdYZEIkSO56QezH0XFbdJaag/9HSBYnyzaAhGHZwy7h7FkTkB
CtK1esemipSc5wuK1WHb0luUUVma/wI5FRmGEkFfZIIH+SOL/C5zVgZV6Quu7oc=
=a0An
-----END PGP SIGNATURE-----

--nvrIllvQKCAPHD4bq0Q8B7sMnJiAUXIfV--


From nobody Wed Mar  8 09:38:50 2017
Return-Path: <eckelcu@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 16543128824; Wed,  8 Mar 2017 09:38:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mniAMeMeQcmm; Wed,  8 Mar 2017 09:38:47 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1488E1270B4; Wed,  8 Mar 2017 09:38:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1930; q=dns/txt; s=iport; t=1488994727; x=1490204327; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yat4McQ8gbMWSoDmXOO7erflgTW2JuWxcaZvPZlaCf0=; b=jz6tSiu3nOrF298+WSh09oSvYJYUUx2f2HVUjuCAbDiQFiUqt+FFkq0k kY9jmr7ro4lE/FmsGPpQJMHgL+q4fWCoJJXLLTuNZePjd5fq342PukQ76 KYdDOt27W3BvMQTeFL2I5s4VPzTk9DN5GjRJ++u3eVuLUl2wM2y7tzuqf Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DuAQDXQMBY/4QNJK1eGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1GBaweDWYoMkUyTKYIPgg2GIgIagiY/GAECAQEBAQEBAWsohRUBAQE?= =?us-ascii?q?BAyMRRQwEAgEIEQMBAgMCJgICAjAVCAgCBA4FiX+wVIImin0BAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEdgQuHSIFhO06EVIMGLoIxAQScNgGSN5Egkz0BHziBA1YVUAG?= =?us-ascii?q?GQnUBiQWBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.36,265,1486425600"; d="scan'208";a="395086626"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Mar 2017 17:38:46 +0000
Received: from XCH-RCD-016.cisco.com (xch-rcd-016.cisco.com [173.37.102.26]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v28Hckds023477 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 Mar 2017 17:38:46 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-016.cisco.com (173.37.102.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 8 Mar 2017 11:38:45 -0600
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Wed, 8 Mar 2017 11:38:45 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: lavanyahm <lavanyahm@ece.iisc.ernet.in>
Subject: Re: IETF Hackathon98 - remote presentation
Thread-Topic: IETF Hackathon98 - remote presentation
Thread-Index: AQHSl+97ldZM/etn6EOgT0WFj0NBnKGLFDYA
Date: Wed, 8 Mar 2017 17:38:45 +0000
Message-ID: <94F5D1A8-F225-4F4A-84B9-A2373353D31A@cisco.com>
References: <026ee8a65aad5df788fb3af89780fdcc@ece.iisc.ernet.in>
In-Reply-To: <026ee8a65aad5df788fb3af89780fdcc@ece.iisc.ernet.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.156.131.1]
Content-Type: text/plain; charset="utf-8"
Content-ID: <79A72A6D69D6A544BCDE72E55411C4F9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v2NEAvsRZ0ULDwpg-YpF8TVNrzM>
Cc: hackathon <hackathon-bounces@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 17:38:49 -0000

SGkgTGF2YW55YSwNCg0KV2hpbGUgaXQgaXMgb2YgY291cnNlIGJlc3QgdG8gYmUgb25zaXRlIGZv
ciB0aGUgaGFja2F0aG9uLCByZW1vdGUgcGFydGljaXBhdGlvbiBpcyBwb3NzaWJsZSBhbmQgZW5j
b3VyYWdlZCBpbiBjYXNlcyBpbiB3aGljaCB0cmF2ZWwgaXMgbm90IHBvc3NpYmxlLiBUaGUga2lj
a29mZiBhdCB0aGUgc3RhcnQgb2YgdGhlIGhhY2thdGhvbiBhbmQgdGhlIHByb2plY3QgcHJlc2Vu
dGF0aW9ucyBhdCB0aGUgZW5kIHdpbGwgYmUgYXZhaWxhYmxlIHJlbW90ZWx5IHZpYSBNZWV0ZWNo
by4gUmVtb3ZlIHByZXNlbnRhdGlvbnMgY2FuIGJlIGFjY29tbW9kYXRlZCBhcyB3ZWxsLiBXZSBh
bHNvIGhhdmUgYSBqYWJiZXIgcm9vbSwgaGFja2F0aG9uQGphYmJlci5pZXRmLm9yZw0KDQpJbiB0
aGUgcGFzdCwgcmVtb3RlIHBhcnRpY2lwYXRpb24gaGFzIHdvcmtlZCBiZXN0IHdoZW4gcmVtb3Rl
IHBhcnRpY2lwYW50cyB3b3JrIGNsb3NlbHkgd2l0aCBhIHRlYW0gdGhhdCBoYXMgbG9jYWwgcGFy
dGljaXBhbnRzIGFzIHdlbGwuIEluIHRoaXMgY2FzZSwgeW91IHNob3VsZCBjb250YWN0IHRoZSBj
aGFtcGlvbihzKSBmb3IgdGhhdCBwcm9qZWN0IHRvIGRldGVybWluZSBob3cgYmVzdCB0byBjb29y
ZGluYXRlLg0KDQpDaGVlcnMsDQpDaGFybGVzDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQpGcm9tOiBsYXZhbnlhaG0gPGxhdmFueWFobUBlY2UuaWlzYy5lcm5ldC5pbj4NCkRhdGU6IFdl
ZG5lc2RheSwgTWFyY2ggOCwgMjAxNyBhdCAxOjM4IEFNDQpUbzogImlldGZAaWV0Zi5vcmciIDxp
ZXRmQGlldGYub3JnPg0KQ2M6IGhhY2thdGhvbiA8aGFja2F0aG9uLWJvdW5jZXNAaWV0Zi5vcmc+
LCAiaWV0Zi1zZWNyZXRhcmlhdEBpZXRmLm9yZyIgPGlldGYtc2VjcmV0YXJpYXRAaWV0Zi5vcmc+
DQpTdWJqZWN0OiBJRVRGIEhhY2thdGhvbjk4IC0gcmVtb3RlIHByZXNlbnRhdGlvbg0KDQogICAg
SGVsbG8gQWxsLA0KICAgIA0KICAgIEkgaGF2ZSByZWdpc3RlcmVkIGZvciB0aGUgSUVURiBIYWNr
YXRob245OCBhbmQgSSByZXNpZGUgaW4gQmFuZ2Fsb3JlLCANCiAgICBJbmRpYS4NCiAgICBJbiB0
aGlzIHJlZ2FyZCBJIHdvdWxkIGxpa2UgdG8ga25vdyBpZiBJIGNhbiBwcmVzZW50IG15IHByb2pl
Y3QgDQogICAgcmVtb3RlbHkuIElmIHNvLCBraW5kbHkgbGV0IG1lIGtub3cgdGhlIHZlbnVlIGFu
ZCBvdGhlciBpbmZvcm1hdGlvbi4NCiAgICANCiAgICBSZWdhcmRzLA0KICAgIExhdmFueWEgSE0N
CiAgICANCiAgICAtLSANCiAgICBUaGlzIG1lc3NhZ2UgaGFzIGJlZW4gc2Nhbm5lZCBmb3Igdmly
dXNlcyBhbmQNCiAgICBkYW5nZXJvdXMgY29udGVudCBieSBNYWlsU2Nhbm5lciwgYW5kIGlzDQog
ICAgYmVsaWV2ZWQgdG8gYmUgY2xlYW4uDQogICAgDQogICAgDQoNCg==


From nobody Wed Mar  8 09:52:52 2017
Return-Path: <eckelcu@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 010081294D0; Wed,  8 Mar 2017 09:52:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id USXVuvNo3EZi; Wed,  8 Mar 2017 09:52:44 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 420401294B2; Wed,  8 Mar 2017 09:52:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1946; q=dns/txt; s=iport; t=1488995564; x=1490205164; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=lAg4QByoe85hG0IVLnPRlT5jcN+u+4WJqbrCbVYvG3s=; b=UCv8DkOWoAlAemw9QsfI9gV11847l3IQ4y+lvrVEik9XbyDQ3KR8jPxT DtyXHATEhjwSLOoMxhcRDpr6i0nG2tGV8vyp0s6+hR7DlIQeFIJyJ/3kD kT1DTlWM7j5n+YKBr5UzXJbd0u4QPtNTFhEHwN3OVCPpccEKELknxMqlw g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B2AQBiRMBY/4gNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1GBaweDWYoMkUyTKYIPgg2GIgIagiY/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAyMRRQwEAgEIEQMBAgMCJgICAjAVCAgCBAENBYl/sFSCJop+AQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBHYELh0iBYTtOhFSDBi6CMQEEnDYBkjeRIJM9AR84gQN?= =?us-ascii?q?WFVABhkJ1AYkFgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.36,265,1486425600"; d="scan'208";a="217829135"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Mar 2017 17:52:43 +0000
Received: from XCH-RCD-019.cisco.com (xch-rcd-019.cisco.com [173.37.102.29]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v28Hm3jk003558 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 Mar 2017 17:48:03 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-019.cisco.com (173.37.102.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 8 Mar 2017 11:48:02 -0600
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Wed, 8 Mar 2017 11:48:02 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: lavanyahm <lavanyahm@ece.iisc.ernet.in>, "hackathon@ietf.org" <hackathon@ietf.org>
Subject: Re: IETF Hackathon98 - remote presentation
Thread-Topic: IETF Hackathon98 - remote presentation
Thread-Index: AQHSl+97ldZM/etn6EOgT0WFj0NBnKGLFt0A
Date: Wed, 8 Mar 2017 17:48:02 +0000
Message-ID: <8CBFBCE5-23F2-4FCF-8D97-D30560506D0C@cisco.com>
References: <026ee8a65aad5df788fb3af89780fdcc@ece.iisc.ernet.in>
In-Reply-To: <026ee8a65aad5df788fb3af89780fdcc@ece.iisc.ernet.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.156.131.1]
Content-Type: text/plain; charset="utf-8"
Content-ID: <86E7D54B104E5544A56CAA407E8B1508@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gqblIieGqHywIw4HWFsUnNzbagI>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 17:52:46 -0000

SGkgTGF2YW55YSwNCiAgICANCldoaWxlIGl0IGlzIG9mIGNvdXJzZSBiZXN0IHRvIGJlIG9uc2l0
ZSBmb3IgdGhlIGhhY2thdGhvbiwgcmVtb3RlIHBhcnRpY2lwYXRpb24gaXMgcG9zc2libGUgYW5k
IGVuY291cmFnZWQgaW4gY2FzZXMgaW4gd2hpY2ggdHJhdmVsIGlzIG5vdCBwb3NzaWJsZS4gVGhl
IGtpY2tvZmYgYXQgdGhlIHN0YXJ0IG9mIHRoZSBoYWNrYXRob24gYW5kIHRoZSBwcm9qZWN0IHBy
ZXNlbnRhdGlvbnMgYXQgdGhlIGVuZCB3aWxsIGJlIGF2YWlsYWJsZSByZW1vdGVseSB2aWEgTWVl
dGVjaG8uIFJlbW92ZSBwcmVzZW50YXRpb25zIGNhbiBiZSBhY2NvbW1vZGF0ZWQgYXMgd2VsbC4g
V2UgYWxzbyBoYXZlIGEgamFiYmVyIHJvb20sIGhhY2thdGhvbkBqYWJiZXIuaWV0Zi5vcmcNCiAg
ICANCkluIHRoZSBwYXN0LCByZW1vdGUgcGFydGljaXBhdGlvbiBoYXMgd29ya2VkIGJlc3Qgd2hl
biByZW1vdGUgcGFydGljaXBhbnRzIHdvcmsgY2xvc2VseSB3aXRoIGEgdGVhbSB0aGF0IGhhcyBs
b2NhbCBwYXJ0aWNpcGFudHMgYXMgd2VsbC4gSW4gdGhpcyBjYXNlLCB5b3Ugc2hvdWxkIGNvbnRh
Y3QgdGhlIGNoYW1waW9uKHMpIGZvciB0aGF0IHByb2plY3QgdG8gZGV0ZXJtaW5lIGhvdyBiZXN0
IHRvIGNvb3JkaW5hdGUuDQogICAgDQpDaGVlcnMsDQpDaGFybGVzDQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiBsYXZhbnlhaG0gPGxhdmFueWFobUBlY2UuaWlzYy5lcm5ldC5p
bj4NCkRhdGU6IFdlZG5lc2RheSwgTWFyY2ggOCwgMjAxNyBhdCAxOjM4IEFNDQpUbzogImlldGZA
aWV0Zi5vcmciIDxpZXRmQGlldGYub3JnPg0KQ2M6IGhhY2thdGhvbiA8aGFja2F0aG9uLWJvdW5j
ZXNAaWV0Zi5vcmc+LCAiaWV0Zi1zZWNyZXRhcmlhdEBpZXRmLm9yZyIgPGlldGYtc2VjcmV0YXJp
YXRAaWV0Zi5vcmc+DQpTdWJqZWN0OiBJRVRGIEhhY2thdGhvbjk4IC0gcmVtb3RlIHByZXNlbnRh
dGlvbg0KDQogICAgSGVsbG8gQWxsLA0KICAgIA0KICAgIEkgaGF2ZSByZWdpc3RlcmVkIGZvciB0
aGUgSUVURiBIYWNrYXRob245OCBhbmQgSSByZXNpZGUgaW4gQmFuZ2Fsb3JlLCANCiAgICBJbmRp
YS4NCiAgICBJbiB0aGlzIHJlZ2FyZCBJIHdvdWxkIGxpa2UgdG8ga25vdyBpZiBJIGNhbiBwcmVz
ZW50IG15IHByb2plY3QgDQogICAgcmVtb3RlbHkuIElmIHNvLCBraW5kbHkgbGV0IG1lIGtub3cg
dGhlIHZlbnVlIGFuZCBvdGhlciBpbmZvcm1hdGlvbi4NCiAgICANCiAgICBSZWdhcmRzLA0KICAg
IExhdmFueWEgSE0NCiAgICANCiAgICAtLSANCiAgICBUaGlzIG1lc3NhZ2UgaGFzIGJlZW4gc2Nh
bm5lZCBmb3IgdmlydXNlcyBhbmQNCiAgICBkYW5nZXJvdXMgY29udGVudCBieSBNYWlsU2Nhbm5l
ciwgYW5kIGlzDQogICAgYmVsaWV2ZWQgdG8gYmUgY2xlYW4uDQogICAgDQogICAgDQoNCg==


From nobody Wed Mar  8 10:11:43 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D79F7129440; Wed,  8 Mar 2017 10:11:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZUBsvXbJk3n; Wed,  8 Mar 2017 10:11:36 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F491128AB0; Wed,  8 Mar 2017 10:11:36 -0800 (PST)
Received: from [192.168.178.20] ([93.217.100.107]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MbJTE-1cV76y3pdU-00Iitb; Wed, 08 Mar 2017 19:11:29 +0100
Subject: Re: [Json] Last Call: <draft-ietf-jsonbis-rfc7159bis-03.txt> (The JavaScript Object Notation (JSON) Data Interchange Format) to Internet Standard
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com> <CAC4RtVDuoKFoCckrDYLPKxC2Oj_Ctr9vZSAALBMBk=foW2MdzA@mail.gmail.com> <f0453539-bc8f-f5cd-d50b-0d5592355924@gmx.de> <25d4b0e3-d59f-ca30-0a8c-dae40569b5c0@outer-planes.net> <1d5419fc-875f-394b-5371-4d53c9064aae@gmx.de> <6726c1a4-1856-f53e-4caa-e72a25f51511@outer-planes.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <80790084-3dc9-225f-33f5-a95be290cb91@gmx.de>
Date: Wed, 8 Mar 2017 19:11:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <6726c1a4-1856-f53e-4caa-e72a25f51511@outer-planes.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:4Ian1WYI4EOlLCtAro64luWklgFLC6/LEiQByn1Rqvdf/cu1NFP 6Ybn39gvprE7zJJn2j9NOJRmQ37eH/1ZhVHPvM0EZKBxJC0hu0EaKBPp9kSIQIjESeUxZZo GEKu5TsXAtBSiY5I+r0ANsAjG3CbH7cdQJ5PV4OuJCAwQTkhVK3OE6dztr4vQDah6SwxObb hjbvik9q0PxnVYMihLyjg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:tQ5LEZuLGms=:LGqwUAI4+h3ctsrViXT+VF bzVkOO4mM9GXxurI+V9TsShkLw0ZLnOoua4kmfEo4wGvEExqdvZrYh05h/oqAoAtHXq7aggsl BQ58aZspT9ojtXK4/hfH8CYNXIQ/pyjiGeXvLreTmzy3vhR5rm88P9BNqNXoXI6Lpx2TRkm7U Sieq7lrzpwSCDbcRE4P/vtJiwVVJ732FolNDvtl2J3btW8cuFHvB/xA9msoI0i+P9nqhy6lYi DfLgS3iXte7LnBpON/DPL/VcVpfUZkqUXb0SMVPxjeSXT7jp+7uxk5EaGYbh7b3eik7eOdWth hlRBRzAN9HnqjoRKLrXOHWE/bAKM9hZ753P1DeL3ckTEvOR5ZnchEnK5OlrgDo1Se15NhJP2S orDW67G2+sCW/HNX1sw9J5LanzUohfEngvXibTooxLaz0p8KjWExrtRFbGuRXqFQAWUipU2UG 5RL0hids8JhND+ct1pzM8ekHWKl80pFtmyrYGwObct/awp3tCxzHBf4eSgRHDCmvLex8cAjrM SslWkH5/k6RL4xvQastmHWzMrQqPR7MeHqG0itbUAtzl57Em+VBS86KQ1Snr4Xf3/ZYcP5Vhk t/xM1LAY47tShPsH4Nf1miFmT6q8ycO1/2xCbnTHcnvCQo/H+qOQMF1KJK+4S/HbvAOPxL3eK mPp4Cz7mZGrEWZDY8xAusn9H/n7jhcsCPxjON3FVrQJOj7SixPKDe84Jpu/LuIYvLepvbs8LN i1GOWMdX6IWl2WSozUeABJOt/ubzPITCD8ft2E3RdwFTtlxT4sESXYfFLgzyWcpDD5Ns3tWyr 9CD+PY0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wmluwI4Nz3knKpTQ38lSZ7ax8RQ>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, "json@ietf.org" <json@ietf.org>, jsonbis-chairs@ietf.org, draft-ietf-jsonbis-rfc7159bis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 18:11:38 -0000

On 2017-03-08 18:13, Matthew Miller wrote:
>
> On 17/03/08 10:08, Julian Reschke wrote:
>> On 2017-03-08 18:02, Matthew Miller wrote:
>>> ...
>>> the rationale for referencing third edition specifically is to give
>>> evidence of the JSON's specification history.  Maybe the word "update"
>>> is debatable here, but I think the reference itself is valid.
>>> ...
>>
>> Well. In that case, why is the 3rd edition a specifically good one to cite?
>>
>> Best regards, Julian
>
> Third Edition is where the object literal syntax (from whence JSON was
> begotten) made its appearance.  Also, the latest editions of ECMA-262
> doesn't discuss JSON the data format; that is what (for them) ECMA-404
> is for.

OK. A few words about this, either in the place where it's referenced, 
or as annotation of the reference, would be helpful.

Best regards, Julian


From nobody Wed Mar  8 10:22:20 2017
Return-Path: <eckelcu@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 3A8741293DC; Wed,  8 Mar 2017 10:22:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eJlhRZ_P6aSE; Wed,  8 Mar 2017 10:22:13 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2E1B128AB0; Wed,  8 Mar 2017 10:22:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1356; q=dns/txt; s=iport; t=1488997332; x=1490206932; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=LND+UQ/694ve0WTWsPa4WNM7YWLsW1vew9PtMQdnV4U=; b=W3MNDksAwbyT1cUIyd/sB/q+ePD9jycWhv3ImKOnBzj5zLQHq92j/5Ia hwH9jE9MZCsbtahpAoJza4DIRtoSsoTNXpUdFCMe9/GdG//2l7WyBUMj2 sgrw+kX2oGdxcROcafWJGooySKZispjIz8dT3JHYcfVJLsH/pcrWL8JcW k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CHAgDtSsBY/5xdJa1eGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1FhgQoHg1mKDJEuk0iCD4INKoV4HIImPxgBAgEBAQEBAQFrHQuFPxF?= =?us-ascii?q?FEgEiAggeAgQwFRIEDgWJfw6wL4IminwBAQEBAQEBAQEBAQEBAQEBAQEBAQEYB?= =?us-ascii?q?YELh0gIijyCXwWcNgGSN4F7hSOKApM9AR84gQNWFT8RAYZCdQGJBYENAQEB?=
X-IronPort-AV: E=Sophos;i="5.36,265,1486425600"; d="scan'208";a="394538531"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2017 18:22:12 +0000
Received: from XCH-RCD-016.cisco.com (xch-rcd-016.cisco.com [173.37.102.26]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v28IMBIO030470 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 Mar 2017 18:22:11 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-016.cisco.com (173.37.102.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 8 Mar 2017 12:22:11 -0600
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Wed, 8 Mar 2017 12:22:11 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "hackathon@ietf.org" <hackathon@ietf.org>
Subject: IETF hackathon - Register and Add your Projects NOW!
Thread-Topic: IETF hackathon - Register and Add your Projects NOW!
Thread-Index: AQHSmDjnS1lE1orADkGnalS00Bn9JQ==
Date: Wed, 8 Mar 2017 18:22:11 +0000
Message-ID: <2A0A7272-B5D0-4289-A5BE-817162982534@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.156.131.1]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7B59EDBA9792C44C8D88DA197E082121@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZAoA_ts2PVKjF3ZJ41lxpLl8IoU>
Cc: IETF chairs <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 18:22:14 -0000

SGV5IEZvbGtzLA0KDQpPbmx5IGEgbGl0dGxlIG92ZXIgdHdvIHdlZWtzIHVudGlsIElFVEYgOTgg
YW5kIHRoZSBoYWNrYXRob24uIElmIHlvdSBwbGFuIHRvIHBhcnRpY2lwYXRlIGFuZCBoYXZlIG5v
dCB5ZXQgcmVnaXN0ZXJlZCwgcGxlYXNlIGRvIHNvIE5PVyENClQtc2hpcnQsIGZvb2QsIGFuZCBi
ZWVyIG9yZGVycyBhcmUgYWxsIGJlaW5nIHBsYWNlZCB0aGlzIHdlZWssIHNvIGl0IGlzIHZlcnkg
aW1wb3J0YW50IHRoYXQgeW91IHJlZ2lzdGVyIG5vdyBpZiB5b3UgcGxhbiB0byBqb2luIHVzLiDi
mLoNCg0KUmVnaXN0cmF0aW9uIGZvciB0aGUgaGFja2F0aG9uIGlzIEZSRUUgYW5kIFJFUVVJUkVE
LiBJdCBpcyBpbmRlcGVuZGVudCBvZiByZWdpc3RyYXRpb24gZm9yIHRoZSBJRVRGIG1lZXRpbmcg
aXRzZWxmLiANCllvdSBjYW4gZmluZCBtb3JlIGluZm8gb24gdGhlIGhhY2thdGhvbiwgaW5jbHVk
aW5nIHRoZSBhZ2VuZGEgYW5kIGEgZGV0YWlsZWQgbGlzdCBvZiBwcm9qZWN0cyBoZXJlOg0KaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvaGFja2F0aG9uLzk4LWhhY2thdGhvbi5odG1sDQpodHRwczovL3d3
dy5pZXRmLm9yZy9yZWdpc3RyYXRpb24vTWVldGluZ1dpa2kvd2lraS85OGhhY2thdGhvbg0KDQpX
aGVuIHlvdSByZWdpc3RlciwgcGxlYXNlIGluZGljYXRlIHRoZSBwcm9qZWN0cyBhbmQvb3IgdGVj
aG5vbG9naWVzIHdpdGggd2hpY2ggeW91IHBsYW4gdG8gd29yay4gSWYgeW91IHdhbnQgdG8gc3Vn
Z2VzdCBvciBjaGFtcGlvbiBhIG5ldyBwcm9qZWN0LCBwbGVhc2Ugc2hhcmUgd2l0aCB0aGUgaGFj
a2F0aG9uQGlldGYub3JnIGxpc3QgYW5kIGFkZCB5b3VyIHByb2plY3QgdG8gdGhlIHdpa2kuDQoN
ClF1ZXN0aW9ucz8gRmVlbCBmcmVlIHRvIHNlbmQgdG8gdGhlIGxpc3QgKGJlIHN1cmUgeW91IHN1
YnNjcmliZSB0byB0aGUgbGlzdCBmaXJzdCkgb3IgY29udGFjdCBtZSBkaXJlY3RseS4NCg0KVGhh
bmtzLA0KQ2hhcmxlcw0KDQoNCg0K


From nobody Wed Mar  8 15:07:21 2017
Return-Path: <weihaw@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 65DA912961A for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 15:07:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbHKS6UwDiBw for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 15:07:17 -0800 (PST)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91E021294E1 for <ietf@ietf.org>; Wed,  8 Mar 2017 15:07:17 -0800 (PST)
Received: by mail-oi0-x232.google.com with SMTP id 62so28260084oih.2 for <ietf@ietf.org>; Wed, 08 Mar 2017 15:07:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KLuKM/q7nKMMf9OE6AXWW2WdOCB3SyvmSlI0N89wHyw=; b=oQj3HKDOJoxI55mHqxySDimnUs3SQyMe62AozhMHn3xvKsQ8JdOdoFXUetBJ8pdcg/ vEZdlo/JkEnYblSMqWJXYWcdJi4JhlQ90AJ+uEsEoTmpn0Fu3sKjRx3mx0iJe/8XkVlE KWgJUi+nNsEI71kWf1Dn97SW6fNEWsTGh4cksTZFnwA15imAvp3bg8xQedLFMq5ILsP6 CTMe3363njUOHCDh7mzCk1zpPd12XsQ8eHIKg95rgcewuLGiYqm7FLFKIh60dC3Ha/Ey 0dOEvZG+LXOsPUP9L6FtZXLY1tDu7WoQl13/HxOw91Ffq5osd6zxtq19M6eFHn1lQSTi BUpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KLuKM/q7nKMMf9OE6AXWW2WdOCB3SyvmSlI0N89wHyw=; b=OrnCB6JhtmoLE94eRMUwPaMOT5tGGTfocFhgMuL3oOeibCTbDi4RL3GTCRG6ATs0za AjE/+ip76Om9211b5Zfe38lnMHHXAVqIfUZXvC/YjNs9jkLf2ilBszDB41Skzmd42XP/ Gy8Lp6uhy54tG75dqoiZTlO/eFK4dX/r00A5Q4BY/EjOfQslKr9cR7y/3DSylu9eakSS oeoA5mkozTzwlL9Gx7LekIpCWP7F4Jm+BoYeCofRXDqS8MzCPK73n+7uDRncSgjbKINF 0tWuxJv26xBmEz0PsUk8+OszVBu6Oh5rChV7/fNQZ9FLb7X4mOH28NdtNvrgOuQuhIYd paQw==
X-Gm-Message-State: AMke39mqgi0xnjMl5j7zuk1rE1d34teufnoSNgU2DR2zPGfu6zV7R3Us0QCP5XQoNgbPKLIqhcQN1hz17BGIYSOP
X-Received: by 10.202.79.18 with SMTP id d18mr5439041oib.9.1489014436781; Wed, 08 Mar 2017 15:07:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.41.226 with HTTP; Wed, 8 Mar 2017 15:07:15 -0800 (PST)
In-Reply-To: <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org> <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie> <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie>
From: Wei Chuang <weihaw@google.com>
Date: Wed, 8 Mar 2017 15:07:15 -0800
Message-ID: <CAAFsWK2RMGp0jqesx3cTbN=S7p0WuhH+0AbeJuuiZPF6WCbQOQ@mail.gmail.com>
Subject: Re: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a113d85c49687df054a40301b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Uak2BCcrKIDvKtrGtfKIMgCsBYA>
Cc: "spasm@ietf.org" <spasm@ietf.org>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 23:07:19 -0000

--001a113d85c49687df054a40301b
Content-Type: multipart/alternative; boundary=001a113d85c492465c054a40302a

--001a113d85c492465c054a40302a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi Stephen,

Let me provide that yell to see if this draft resolves the last set of
concerns.
https://tools.ietf.org/html/draft-ietf-lamps-eai-addresses-07

The diff is here:
https://tools.ietf.org/rfcdiff?url2=draft-ietf-lamps-eai-addresses-07.txt

-Wei


On Wed, Mar 8, 2017 at 8:22 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> Hiya,
>
> So I don't think we've yet resolved the issues raised
> with this. And since the March 16th telechat will be my
> last one I figure that the best thing to do is to ask
> that this go back to the working group for resolution.
>
> Once that's sorted out, then the WG can kick it over
> to their new AD. Note that this need not add any major
> delay - it'd be entirely possible to have it back on a
> telechat agenda shortly after IETF98, all going well.
>
> If nobody yells, I'll do that tomorrow.
>
> If someone does yell, please do that now and accompany
> your yell with the OLD/NEW changes that you claim resolve
> the issues raised. (To be honest though, I think this
> would benefit from more WG discussion so I'll not be so
> easy to convince if someone does yell thusly;-)
>
> Cheers,
> S.
>
> On 23/02/17 20:16, Stephen Farrell wrote:
> >
> > Folks,
> >
> > I've just reviewed the IETF LC for this draft. Thanks all for
> > the comments and discussion which I think have thrown up some
> > real issues.
> >
> > As of now, it is not clear to me that we have finished the
> > work with this one, at least the issues to do with name
> > constraints seem to me to call for some more WG consideration.
> >
> > I think Russ (as lamps WG chair) has a similar opinion
> > that we're not done yet.
> >
> > That said, I had put this on the March 16th IESG telechat
> > for consideration. If we do manage to reach a clear enough
> > consensus on a published revision to the draft in say the
> > next week then that schedule should still be fine. So I'd
> > encourage the authors and others who've commented to try
> > again and see if, in that timeframe, we can get to where
> > we're happy that the issues raised have been handled well
> > enough.
> >
> > But, if it looks (as it does to me today) as if this'll take
> > a bit longer to figure out, then I figure the right thing to
> > do will be to let the lamps WG figure out how to proceed.
> > (And that'll mean that my successor as the responsible AD
> > for the lamps WG will handle further actions with the doc.)
> >
> > Bottom line: if this isn't settled in the next week or so,
> > I'll take it off the March 16th IESG telechat and let the WG
> > continue the discussion.
> >
> > Cheers,
> > S.
> >
> > PS: To add to the name constraints discussion, I did wonder
> > if anyone really wants to use those. So for example, if we
> > defined the new name form so that certificate chains with
> > any name constraints at all and one of those names anywhere
> > are always treated as invalid, then would that cause any
> > real breakage? (It certainly would cause theoretical breakage,
> > but if that's all then I'd be ok with that:-)
> >
> >
> >
>
>
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>
>

--001a113d85c492465c054a40302a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr">Hi Stephen,<div><br></div><div>Let me provide that yell to see if this draft resolves the last set of concerns.</div><div><a href="https://tools.ietf.org/html/draft-ietf-lamps-eai-addresses-07">https://tools.ietf.org/html/draft-ietf-lamps-eai-addresses-07</a><br><br>The diff is here:</div><div><a href="https://tools.ietf.org/rfcdiff?url2=draft-ietf-lamps-eai-addresses-07.txt">https://tools.ietf.org/rfcdiff?url2=draft-ietf-lamps-eai-addresses-07.txt</a><br></div><div><br></div><div>-Wei</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 8, 2017 at 8:22 AM, Stephen Farrell <span dir="ltr">&lt;<a href="mailto:stephen.farrell@cs.tcd.ie" target="_blank">stephen.farrell@cs.tcd.ie</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hiya,<br>
<br>
So I don&#39;t think we&#39;ve yet resolved the issues raised<br>
with this. And since the March 16th telechat will be my<br>
last one I figure that the best thing to do is to ask<br>
that this go back to the working group for resolution.<br>
<br>
Once that&#39;s sorted out, then the WG can kick it over<br>
to their new AD. Note that this need not add any major<br>
delay - it&#39;d be entirely possible to have it back on a<br>
telechat agenda shortly after IETF98, all going well.<br>
<br>
If nobody yells, I&#39;ll do that tomorrow.<br>
<br>
If someone does yell, please do that now and accompany<br>
your yell with the OLD/NEW changes that you claim resolve<br>
the issues raised. (To be honest though, I think this<br>
would benefit from more WG discussion so I&#39;ll not be so<br>
easy to convince if someone does yell thusly;-)<br>
<br>
Cheers,<br>
S.<br>
<div class="HOEnZb"><div class="h5"><br>
On 23/02/17 20:16, Stephen Farrell wrote:<br>
&gt;<br>
&gt; Folks,<br>
&gt;<br>
&gt; I&#39;ve just reviewed the IETF LC for this draft. Thanks all for<br>
&gt; the comments and discussion which I think have thrown up some<br>
&gt; real issues.<br>
&gt;<br>
&gt; As of now, it is not clear to me that we have finished the<br>
&gt; work with this one, at least the issues to do with name<br>
&gt; constraints seem to me to call for some more WG consideration.<br>
&gt;<br>
&gt; I think Russ (as lamps WG chair) has a similar opinion<br>
&gt; that we&#39;re not done yet.<br>
&gt;<br>
&gt; That said, I had put this on the March 16th IESG telechat<br>
&gt; for consideration. If we do manage to reach a clear enough<br>
&gt; consensus on a published revision to the draft in say the<br>
&gt; next week then that schedule should still be fine. So I&#39;d<br>
&gt; encourage the authors and others who&#39;ve commented to try<br>
&gt; again and see if, in that timeframe, we can get to where<br>
&gt; we&#39;re happy that the issues raised have been handled well<br>
&gt; enough.<br>
&gt;<br>
&gt; But, if it looks (as it does to me today) as if this&#39;ll take<br>
&gt; a bit longer to figure out, then I figure the right thing to<br>
&gt; do will be to let the lamps WG figure out how to proceed.<br>
&gt; (And that&#39;ll mean that my successor as the responsible AD<br>
&gt; for the lamps WG will handle further actions with the doc.)<br>
&gt;<br>
&gt; Bottom line: if this isn&#39;t settled in the next week or so,<br>
&gt; I&#39;ll take it off the March 16th IESG telechat and let the WG<br>
&gt; continue the discussion.<br>
&gt;<br>
&gt; Cheers,<br>
&gt; S.<br>
&gt;<br>
&gt; PS: To add to the name constraints discussion, I did wonder<br>
&gt; if anyone really wants to use those. So for example, if we<br>
&gt; defined the new name form so that certificate chains with<br>
&gt; any name constraints at all and one of those names anywhere<br>
&gt; are always treated as invalid, then would that cause any<br>
&gt; real breakage? (It certainly would cause theoretical breakage,<br>
&gt; but if that&#39;s all then I&#39;d be ok with that:-)<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
</div></div><br>______________________________<wbr>_________________<br>
Spasm mailing list<br>
<a href="mailto:Spasm@ietf.org">Spasm@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/spasm" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/spasm</a><br>
<br></blockquote></div><br></div>

--001a113d85c492465c054a40302a--

--001a113d85c49687df054a40301b
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCBJveztXIFL4CUkp5/jo67V
gUpg5M2E4+zZke5gIiTJxDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAzMDgyMzA3MTdaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEApvT3IGe2usxRXKhvM2pjVsDbzaHxzbzErs+JZrvF
b2vTIuXUKd2NsdnN4ohOZKp12vPY2eakNZExPODBy3SVTTxDH/p3PWs1gjps99ys+L3UpTvZiAEw
so4t9wciTWU0tQhpBIVNeKccnx2ZAzsT9czshItoSIcsLu8PrXXDwXT/P5SIrV0d4jdPdFovLGSN
gs5IFZaD8K+oXQA8Fenlv0wy0wqRMA2E8HRXFm8etzlaHGrm3/iZmpLop1n8iHebdGsBivlUqNLg
DHMdvLVXg/l+NVDF01J5zN0gpjeSd5ACwPOpWShMmWACY8fnryPvfxLZWV9JlbnhweB+u8dXCA==
--001a113d85c49687df054a40301b--


From nobody Wed Mar  8 15:28:04 2017
Return-Path: <ietf-dane@dukhovni.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 2D779127058; Wed,  8 Mar 2017 15:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5kzJ1vIatIp; Wed,  8 Mar 2017 15:27:57 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63D56120726; Wed,  8 Mar 2017 15:27:57 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 6D1A37A32D8; Wed,  8 Mar 2017 23:27:56 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Date: Wed, 8 Mar 2017 18:27:55 -0500
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org> <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie> <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie> <CAAFsWK2RMGp0jqesx3cTbN=S7p0WuhH+0AbeJuuiZPF6WCbQOQ@mail.gmail.com>
To: "spasm@ietf.org" <spasm@ietf.org>, IETF general list <ietf@ietf.org>
In-Reply-To: <CAAFsWK2RMGp0jqesx3cTbN=S7p0WuhH+0AbeJuuiZPF6WCbQOQ@mail.gmail.com>
Message-Id: <BCEFAA3C-B711-4269-81C8-4DA0E1AA7AD0@dukhovni.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ouNEFR9Gnf81WS1xz4vHt2xxyRU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Mar 2017 23:27:59 -0000

> On Mar 8, 2017, at 6:07 PM, Wei Chuang <weihaw@google.com> wrote:
> 
> https://tools.ietf.org/rfcdiff?url2=draft-ietf-lamps-eai-addresses-07.txt

This diff covers a lot more than just name constraints.  One oddity that
stands out is in section 5:

	3.  Ensure local-part is UTF-8.

I don't see how one would "ensure" such a thing, since no encoding
information is available for the localpart, is I would expect that
is always presumptively UTF-8 (if not us-ascii).

More importantly I don't believe that the name constraint issues are
adequately or correctly addressed in this revision.

Instead of prohibiting issuance of EE certs that HAVE SmtpUTF8Name SAN
elements via a cert chain that has a certificate with *just* rfc822Name
constraints, it attempts to require an unnecessary (and I think not
entirely robust) correspondence between the two types constraint, and
needlessly bans EE certs whose chains include just rfc822Name constraints
even in the absence of SmtpUTF8Name SAN elements.

The changes in this revision seem to me to be too extensive, and not
yet finished. :-(

-- 
	Viktor.


From nobody Wed Mar  8 17:17:20 2017
Return-Path: <weihaw@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 55CE71295D3 for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 17:17:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d5lUeqVpGEzY for <ietf@ietfa.amsl.com>; Wed,  8 Mar 2017 17:17:17 -0800 (PST)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 496CE12953D for <ietf@ietf.org>; Wed,  8 Mar 2017 17:17:17 -0800 (PST)
Received: by mail-oi0-x235.google.com with SMTP id 2so29234349oif.0 for <ietf@ietf.org>; Wed, 08 Mar 2017 17:17:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JpFsSAbT5LMiZndgBX3WbEy1Mcyb6ianjp1yjDRnm1o=; b=c5nhLUN7y5iWXefxIVx9mVct/+7mAIjsGP0ta61BMEux6cKovYk6sqOXSLVjKEAB0T Zeoi5lpsg9ESpx2sQqG0jb3QNIhf9g7eXUu5Ma+rnVijxIlI8np3MvqVIKGd3k/glRxi ZMDuAxol40rdn9FG0ZdgCynWVqJmJgTUWFz4OnymnifvViD60wfQa5v1PX3nxO8PWYqw xrtT8t9rMfOuVUouDEqZqRmpaWEfIak6DmkTHmrfxFTAvl/0dC/ET1YlvWe6/8353GE0 tYoFr0Yiptbrnrb+GwsF4RVqXDtf91p1WbzYyHYjGlYNVmkvUGMd/HYGROVwtxy6/0pn sfsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JpFsSAbT5LMiZndgBX3WbEy1Mcyb6ianjp1yjDRnm1o=; b=ZcbiGiYJgRXaFQCcznrRQ6cfwetbt6MErV1G6J4invBhE+fn3y6Z7VOfU6f9p+FpXB fUftNtLqLpKAXhRUy7YhcAucTW8hg7OX+UWySDE3LvanGYIEDMc2JomuyZ4Sz+w0TX/V uefwvTpbt9HKlzf9ezgNsrQTbEmM9XMDosbTWpVmX94LCV+8ZKnTnrYu1EzbmazO0g2r hHN9N9f6zCmz78kjsKUFt0B3yjkQ8s8uAPQG6TKg6+if6tyr2/lZpQyYtnPOXnOaOBJL SaCXu30uZ76zj7SMUVWwbzHlM6UGk/atQ/7BHtnJV11nOA1qmZ7ir6SW1EAJdRWFJ2p1 efCw==
X-Gm-Message-State: AMke39kOSgk/PVQjCvv/LD8tH6opjtbf5Nn/vY+BZ47QtRgPWizod4ObuCPGD/caCQf7F24xLZNRgGKf81cBTPws
X-Received: by 10.202.90.84 with SMTP id o81mr5034972oib.106.1489022236419; Wed, 08 Mar 2017 17:17:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.41.226 with HTTP; Wed, 8 Mar 2017 17:17:15 -0800 (PST)
In-Reply-To: <BCEFAA3C-B711-4269-81C8-4DA0E1AA7AD0@dukhovni.org>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org> <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie> <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie> <CAAFsWK2RMGp0jqesx3cTbN=S7p0WuhH+0AbeJuuiZPF6WCbQOQ@mail.gmail.com> <BCEFAA3C-B711-4269-81C8-4DA0E1AA7AD0@dukhovni.org>
From: Wei Chuang <weihaw@google.com>
Date: Wed, 8 Mar 2017 17:17:15 -0800
Message-ID: <CAAFsWK3yJ9r+6abTXZQsNsey+VcRpdtVv=Hku_54_LZ9y1T2xQ@mail.gmail.com>
Subject: Re: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: Viktor Dukhovni <ietf-dane@dukhovni.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a113d52727bee0f054a4201cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vI4lqkViTrCA-6rEJfjiE8AMqqs>
Cc: "spasm@ietf.org" <spasm@ietf.org>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 01:17:19 -0000

--001a113d52727bee0f054a4201cf
Content-Type: multipart/alternative; boundary=001a113d5272774752054a420152

--001a113d5272774752054a420152
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Okay.  I think the direction then is to have SmtpUTF8Name respect
rfc822Name name constraints and vice versa.

-Wei

On Wed, Mar 8, 2017 at 3:27 PM, Viktor Dukhovni <ietf-dane@dukhovni.org>
wrote:

>
> > On Mar 8, 2017, at 6:07 PM, Wei Chuang <weihaw@google.com> wrote:
> >
> > https://tools.ietf.org/rfcdiff?url2=draft-ietf-lamps-
> eai-addresses-07.txt
>
> This diff covers a lot more than just name constraints.  One oddity that
> stands out is in section 5:
>
>         3.  Ensure local-part is UTF-8.
>
> I don't see how one would "ensure" such a thing, since no encoding
> information is available for the localpart, is I would expect that
> is always presumptively UTF-8 (if not us-ascii).
>
> More importantly I don't believe that the name constraint issues are
> adequately or correctly addressed in this revision.
>
> Instead of prohibiting issuance of EE certs that HAVE SmtpUTF8Name SAN
> elements via a cert chain that has a certificate with *just* rfc822Name
> constraints, it attempts to require an unnecessary (and I think not
> entirely robust) correspondence between the two types constraint, and
> needlessly bans EE certs whose chains include just rfc822Name constraints
> even in the absence of SmtpUTF8Name SAN elements.
>
> The changes in this revision seem to me to be too extensive, and not
> yet finished. :-(
>
> --
>         Viktor.
>
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>

--001a113d5272774752054a420152
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr">Okay.  I think the direction then is to have SmtpUTF8Name respect rfc822Name name constraints and vice versa.<div><br></div><div>-Wei</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 8, 2017 at 3:27 PM, Viktor Dukhovni <span dir="ltr">&lt;<a href="mailto:ietf-dane@dukhovni.org" target="_blank">ietf-dane@dukhovni.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
&gt; On Mar 8, 2017, at 6:07 PM, Wei Chuang &lt;<a href="mailto:weihaw@google.com">weihaw@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; <a href="https://tools.ietf.org/rfcdiff?url2=draft-ietf-lamps-eai-addresses-07.txt" rel="noreferrer" target="_blank">https://tools.ietf.org/<wbr>rfcdiff?url2=draft-ietf-lamps-<wbr>eai-addresses-07.txt</a><br>
<br>
This diff covers a lot more than just name constraints.  One oddity that<br>
stands out is in section 5:<br>
<br>
        3.  Ensure local-part is UTF-8.<br>
<br>
I don&#39;t see how one would &quot;ensure&quot; such a thing, since no encoding<br>
information is available for the localpart, is I would expect that<br>
is always presumptively UTF-8 (if not us-ascii).<br>
<br>
More importantly I don&#39;t believe that the name constraint issues are<br>
adequately or correctly addressed in this revision.<br>
<br>
Instead of prohibiting issuance of EE certs that HAVE SmtpUTF8Name SAN<br>
elements via a cert chain that has a certificate with *just* rfc822Name<br>
constraints, it attempts to require an unnecessary (and I think not<br>
entirely robust) correspondence between the two types constraint, and<br>
needlessly bans EE certs whose chains include just rfc822Name constraints<br>
even in the absence of SmtpUTF8Name SAN elements.<br>
<br>
The changes in this revision seem to me to be too extensive, and not<br>
yet finished. :-(<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
        Viktor.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<wbr>_________________<br>
Spasm mailing list<br>
<a href="mailto:Spasm@ietf.org">Spasm@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/spasm" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/spasm</a><br>
</div></div></blockquote></div><br></div>

--001a113d5272774752054a420152--

--001a113d52727bee0f054a4201cf
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCAVVK0iDJzPLi0Oh+gTgxSx
lbTPkzbQyljj7lj7GOqNXzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAzMDkwMTE3MTZaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAvX6oSkBn06Ui+5iSamyIeXQ1n9h3nTb+rT3F3C4C
0U9nhz8dXwmMmf59mFTU7zZsF8vKSn6Od0biSEANvUYL4qy2BPv6WYpROp1pY05epRugSFShOXNL
6GE2OSMfucPuKhRaoRnbnqRwg+FH2BX3u3/7cj84A8JRLcNZ+Ilxv1AjGwQEd1O+LDPWM5DZAVYY
pJucNGl3F8iywHRZ4oT4VBsTYih02xWJv1GcBVtbxD59nOmGcwN0i9skJdHI7ocDvY8jerRot7au
kgBm+zXFx+yUyI93mWiAlipEy2D5meqrWqCvsrIPisMmsFoJXs0hZOZK62AbTZMJ9KT/1xXiuw==
--001a113d52727bee0f054a4201cf--


From nobody Wed Mar  8 17:36:42 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 955171295FD; Wed,  8 Mar 2017 17:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level: 
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GJwyhYV_xVKw; Wed,  8 Mar 2017 17:36:39 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4BFA1295FB; Wed,  8 Mar 2017 17:36:38 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.24.193; 
From: "Susan Hares" <shares@ndzh.com>
To: "'NetNull'" <netnull@hushmail.com>, <ietf@ietf.org>
References: <148899842565.20196.8824136696352094471.idtracker@ietfa.amsl.com> <6c93044b224adcc771c1980f4a227098@smtp.hushmail.com>
In-Reply-To: <6c93044b224adcc771c1980f4a227098@smtp.hushmail.com>
Subject: RE: [I2nsf] Last Call: <draft-ietf-i2nsf-problem-and-use-cases-11.txt> (I2NSF Problem Statement and Use cases) to Proposed Standard
Date: Wed, 8 Mar 2017 20:32:01 -0500
Message-ID: <004201d29874$f50835f0$df18a1d0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0043_01D2984B.0C3477E0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHo7MDlR8nuQ0NakF7bxj0qbciG5qFfEC4Q
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UsvPywdwwNCwAPEHVpe_Lk5x0p4>
Cc: i2nsf@ietf.org, i2nsf-chairs@ietf.org, draft-ietf-i2nsf-problem-and-use-cases@ietf.org, 'IETF-Announce' <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 01:36:41 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0043_01D2984B.0C3477E0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Ed:=20

=20

Thank you for this comment.  I will make this change in version-12.   =
I=E2=80=99ll wait a few days to see if additional comments are provided =
during IETF LC.=20

=20

Sue=20

=20

From: NetNull [mailto:netnull@hushmail.com]=20
Sent: Wednesday, March 8, 2017 2:23 PM
To: ietf@ietf.org
Cc: IETF-Announce; i2nsf@ietf.org; adrian@olddog.co.uk; =
kathleen.moriarty.ietf@gmail.com; =
draft-ietf-i2nsf-problem-and-use-cases@ietf.org; i2nsf-chairs@ietf.org
Subject: Re: [I2nsf] Last Call: =
<draft-ietf-i2nsf-problem-and-use-cases-11.txt> (I2NSF Problem Statement =
and Use cases) to Proposed Standard

=20

I endorse this draft, and appreciate citation from the original use-case =
draft.  However, note that my organization has changed from Fortinet to =
Curveball Networks

=20

Ed Lopez - Curveball Networks

On March 8, 2017 at 1:40 PM, The IESG <iesg-secretary@ietf.org> wrote:


The IESG has received a request from the Interface to Network Security=20
Functions WG (i2nsf) to consider the following document:=20
- 'I2NSF Problem Statement and Use cases'=20
<draft-ietf-i2nsf-problem-and-use-cases-11.txt> as Proposed Standard=20

The IESG plans to make a decision in the next few weeks, and solicits=20
final comments on this action. Please send substantive comments to the=20
ietf@ietf.org mailing lists by 2017-03-22. Exceptionally, comments may =
be=20
sent to iesg@ietf.org instead. In either case, please retain the=20
beginning of the Subject line to allow automated sorting.=20

Abstract=20


This document describes the problem statement for Interface to=20
Network Security Functions (I2NSF) as well as some companion use=20
cases.=20




The file can be obtained via=20
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-problem-and-use-cases/ =


IESG discussion can be tracked via=20
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-problem-and-use-cases/b=
allot/=20


No IPR declarations have been submitted directly on this I-D.=20




_______________________________________________=20
I2nsf mailing list=20
I2nsf@ietf.org=20
https://www.ietf.org/mailman/listinfo/i2nsf=20


------=_NextPart_000_0043_01D2984B.0C3477E0
Content-Type: text/html;
	charset="utf-8"
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=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Ed: <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thank you for this comment.=C2=A0 I will make this change in =
version-12.=C2=A0=C2=A0 I=E2=80=99ll wait a few days to see if =
additional comments are provided during IETF LC. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Sue <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
NetNull [mailto:netnull@hushmail.com] <br><b>Sent:</b> Wednesday, March =
8, 2017 2:23 PM<br><b>To:</b> ietf@ietf.org<br><b>Cc:</b> IETF-Announce; =
i2nsf@ietf.org; adrian@olddog.co.uk; kathleen.moriarty.ietf@gmail.com; =
draft-ietf-i2nsf-problem-and-use-cases@ietf.org; =
i2nsf-chairs@ietf.org<br><b>Subject:</b> Re: [I2nsf] Last Call: =
&lt;draft-ietf-i2nsf-problem-and-use-cases-11.txt&gt; (I2NSF Problem =
Statement and Use cases) to Proposed Standard<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I endorse =
this draft, and appreciate citation from the original use-case draft. =
&nbsp;However, note that my organization has changed from Fortinet to =
Curveball Networks<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Ed Lopez - Curveball Networks<br><br>On March 8, 2017 =
at 1:40 PM, The IESG &lt;<a =
href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt; =
wrote:<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>The IESG has received a request from =
the Interface to Network Security <br>Functions WG (i2nsf) to consider =
the following document: <br>- 'I2NSF Problem Statement and Use cases' =
<br>&lt;draft-ietf-i2nsf-problem-and-use-cases-11.txt&gt; as Proposed =
Standard <br><br>The IESG plans to make a decision in the next few =
weeks, and solicits <br>final comments on this action. Please send =
substantive comments to the <br><a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by =
2017-03-22. Exceptionally, comments may be <br>sent to <a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, =
please retain the <br>beginning of the Subject line to allow automated =
sorting. <br><br>Abstract <br><br><br>This document describes the =
problem statement for Interface to <br>Network Security Functions =
(I2NSF) as well as some companion use <br>cases. <br><br><br><br><br>The =
file can be obtained via <br><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-i2nsf-problem-and-use=
-cases/">https://datatracker.ietf.org/doc/draft-ietf-i2nsf-problem-and-us=
e-cases/</a> <br><br>IESG discussion can be tracked via <br><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-i2nsf-problem-and-use=
-cases/ballot/">https://datatracker.ietf.org/doc/draft-ietf-i2nsf-problem=
-and-use-cases/ballot/</a> <br><br><br>No IPR declarations have been =
submitted directly on this I-D. =
<br><br><br><br><br>_______________________________________________ =
<br>I2nsf mailing list <br><a =
href=3D"mailto:I2nsf@ietf.org">I2nsf@ietf.org</a> <br><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf">https://www.ietf.org=
/mailman/listinfo/i2nsf</a> =
<o:p></o:p></p></div></div></div></body></html>
------=_NextPart_000_0043_01D2984B.0C3477E0--


From nobody Wed Mar  8 19:19:25 2017
Return-Path: <ietf-dane@dukhovni.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 A7E77129717; Wed,  8 Mar 2017 19:19:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HbCfQ_P6vvTc; Wed,  8 Mar 2017 19:19:23 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC96F1296FD; Wed,  8 Mar 2017 19:19:22 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 8C5F97A32D8; Thu,  9 Mar 2017 03:19:21 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CAAFsWK3yJ9r+6abTXZQsNsey+VcRpdtVv=Hku_54_LZ9y1T2xQ@mail.gmail.com>
Date: Wed, 8 Mar 2017 22:19:20 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8A5967B-9C19-4167-8A20-B82DFD46A924@dukhovni.org>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org> <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie> <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie> <CAAFsWK2RMGp0jqesx3cTbN=S7p0WuhH+0AbeJuuiZPF6WCbQOQ@mail.gmail.com> <BCEFAA3C-B711-4269-81C8-4DA0E1AA7AD0@dukhovni.org> <CAAFsWK3yJ9r+6abTXZQsNsey+VcRpdtVv=Hku_54_LZ9y1T2xQ@mail.gmail.com>
To: "spasm@ietf.org" <spasm@ietf.org>, IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gAop0pv8_CZRLO8Dkd8VBNUthak>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: "spasm@ietf.org" <spasm@ietf.org>, IETF general list <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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 03:19:25 -0000

> On Mar 8, 2017, at 8:17 PM, Wei Chuang <weihaw@google.com> wrote:
>=20
> Okay.  I think the direction then is to have SmtpUTF8Name respect =
rfc822Name name constraints and vice versa.

Well, no, the simplest proposal on the table is for SmtpUTF8Name to
be *prohibited* when rfc822Name constraints are present and SmtpUTF8Name
constraints are not.  When both present, they can operate independently.

The verifier logic is then:

	1. If neither rfc822Name constraints nor SmtpUTF8Name =
constraints
           are present in any CA certificate in the chain, any mixture =
of
           rfc822Name and SmtpUTF8Name SAN elements is valid.

	2. If some certificate in the chain contains *only* rfc822Name
	   constraints, then these apply to rfc822Name SAN elements, but
	   all SmtpUTF8Names are prohibited.

	3. When both types of constraints are present in all CA =
certificates
           that have either type, then constraints for each SAN type are
	   exclusively based on just the corresponding constraint type.

	4. If some certificate in the chain contains only SmtpUTF8Name
 	   constraints then those are unavoidably at risk of bypass via
           rfc822Name SAN elements when processed by legacy verifiers.
	   Therefore, this should be avoided, and the CA needs to
 	   publish rfc822Name constraints that prevent bypass.  Such
	   constraints *need not* be equivalent (not always possible)
	   to the desired SmtpUTF8Name constraints.  Rather, it suffices
	   to not permit rfc822Name elements that would be prohibited
	   if they were simply cut/pasted (with no A-label to U-label
           conversions) as SmtpUTF8Name elements.  It is not necessary
	   for these to permit everything that SmtpUTF8Name permits.

Thus for example, if SmtpUtf8Name only permits addresses in the non =
NR-LDH
domain "=D0=B4=D1=83=D1=85=D0=BE=D0=B2=D0=BD=D1=8B=D0=B9.org" (or a =
specific set of addresses in such a domain),
then the corresponding rfc822Name constraint could just permit "." (or =
the
reserved "invalid" TLD if that's preferable) which is not a usable email
domain.  This ensures that only the permitted SmtpUTF8Name SANs are used
and no rfc822Name SANs are used.

If, instead the Smtp8Name constraints are excluded non-ASCII address =
forms,
then since these have no literal rfc822Name equivalents, the rfc822Name
constraints can be omitted with the same effect.

Only when the intention is to permit NR-LDH domains with either ASCII or
UTF-8 localparts (or an all-ASCII full address) do the rfc822Name and
SmtpUTF8Name constraints need to be fully equivalent.  This is of course
trivial to do.  Just cut/paste the same string into both types of
constraint.

--=20
	Viktor.


From nobody Wed Mar  8 21:54:15 2017
Return-Path: <kaduk@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 BBDF2127ABE; Wed,  8 Mar 2017 21:54:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I3jHOIdMARNR; Wed,  8 Mar 2017 21:54:09 -0800 (PST)
Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1FBA1297CB; Wed,  8 Mar 2017 21:53:54 -0800 (PST)
X-AuditID: 12074422-1a7ff70000001f4d-f9-58c0edf1de49
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by  (Symantec Messaging Gateway) with SMTP id 4C.84.08013.1FDE0C85; Thu,  9 Mar 2017 00:53:53 -0500 (EST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id v295rqUr019091; Thu, 9 Mar 2017 00:53:53 -0500
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v295rmPK016024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Mar 2017 00:53:51 -0500
Date: Wed, 8 Mar 2017 23:53:48 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
Message-ID: <20170309055348.GL30306@kduck.kaduk.org>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <456b4234-0d94-1033-507c-710878bb5159@gmx.de>
User-Agent: Mutt/1.6.1 (2016-04-27)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJIsWRmVeSWpSXmKPExsUixG6nrvvx7YEIg593rS1mPfvBaPFs43wW i3tzii02P3zDavFh4UMWB1aPDx/jPJYs+ckUwBTFZZOSmpNZllqkb5fAldH0r4W5oJ234uDV /UwNjPO5uhg5OSQETCR+z77D2sXIxSEk0MYk8e/Cb0YIZwOjxNo1M5ggnCtMErP/bmICaWER UJH49WgyK4jNBmQ3dF9mBrFFBLQkbt/bywhiMwtUSEw+sB3MFhZwleiYexusnhdo3Y7uDVAb pjBKfJ+4ngUiIShxcuYTFohmLYkb/14CLeMAsqUllv/jAAlzClhJTHr9B2yOqICyRMOMB8wT GAVmIemehaR7FkL3AkbmVYyyKblVurmJmTnFqcm6xcmJeXmpRbqmermZJXqpKaWbGMEh7KK0 g3HiP69DjAIcjEo8vALCByKEWBPLiitzDzFKcjApifIaBACF+JLyUyozEosz4otKc1KLDzFK cDArifDuugSU401JrKxKLcqHSUlzsCiJ84prNEYICaQnlqRmp6YWpBbBZGU4OJQkeJe9AWoU LEpNT61Iy8wpQUgzcXCCDOcBGh4DUsNbXJCYW5yZDpE/xagoJc67DiQhAJLIKM2D6wWlGIns /TWvGMWBXhHm/QpSxQNMT3Ddr4AGMwEN1nbdCzK4JBEhJdXA6CK2ffoffsUt9/cHnjPwT2Ox +7s+QjDNt//idxGJz8+FvEV+SzlrMyUp8oUdP/hT2+ays3F754ObKkvvMOd4KSr9NH23/Eax Y552Bf/La/bbfpvd/8Uc9Vevm3tewNcFFvN+/Jghwd3GK1geuyx/qbDBTL2Vi25IaLjfCpgd LDxfWMhVu3SvEktxRqKhFnNRcSIAVklLhwwDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/acTZt7JT2gB16BjtYbvtpTFUEPc>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 05:54:10 -0000

On Wed, Mar 08, 2017 at 08:47:24AM +0100, Julian Reschke wrote:
> On 2017-03-08 08:39, Julian Reschke wrote:
> > On 2017-03-08 02:48, Benjamin Kaduk wrote:
> >> I'm also concerned about the freewheeling use of Unicode.  While
> >> this document does discuss the potential encodings and lists UTF-8
> >> as the default (and most interoperable), I think it would benefit
> >> from a stricter warning that parties using JSON for communication
> >> must have some out-of-band way to agree on what encoding is to be
> >> used.  I would expect that this is usually going to be done by the
> >> protocol using JSON, but could see a place for the actual
> >> communicating peers to have out-of-band knowledge.  (An application
> >> having to guess what encoding is being used based on heuristics is a
> >> recipe for disaster.)
> >> ...
> >
> > AFAIU, there is no need for out-of-band knowledge (which would be very
> > bad). Recipients are supposed to inspect the payload and detect which of
> > the three encoding was used.
> >
> > That said, we probably should make that clearer.

If that's what's supposed to happen, it should probably be more
clear, yes.  (But aren't there texts that have valid interpretations
in multiple encodings?)


> >> ...
> >> I'm also rather curious about the claim that no "charset" parameter
> >> is needed as it "really has no effect on compliant recipients".  Why
> >> is this not a good way to communicate whether UTF-8, UTF-16, or
> >> UTF-32 is in use for a given text?
> >> ...
> >
> > It might have been, but that's now how it is implemented.
> 
> s/now/not/

Alas.

Thanks for the insight.

-Ben


From nobody Thu Mar  9 01:10:29 2017
Return-Path: <jari.arkko@piuha.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 6EB0B1294DA for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 01:10:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y1ZtvU2XnSHH for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 01:10:23 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id F01671294BE for <ietf@ietf.org>; Thu,  9 Mar 2017 01:10:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 81B552CFD8 for <ietf@ietf.org>; Thu,  9 Mar 2017 11:10:14 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wPXnSWrpYcxl for <ietf@ietf.org>; Thu,  9 Mar 2017 11:10:13 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id C3EDF2CC5E for <ietf@ietf.org>; Thu,  9 Mar 2017 11:10:13 +0200 (EET) (envelope-from jari.arkko@piuha.net)
From: Jari Arkko <jari.arkko@piuha.net>
X-Pgp-Agent: GPGMail
Content-Type: multipart/signed; boundary="Apple-Mail=_890ECBE3-7F80-458E-97AD-9763E2A14A56"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: Final version of draft-bradner-rfc3979bis
Date: Thu, 9 Mar 2017 11:10:12 +0200
References: <1AC9187F-A147-40E6-B356-DFF4E8356F13@sobco.com>
To: IETF <ietf@ietf.org>
Message-Id: <D2B41D67-4E2C-4B65-83F1-C36497ACA19F@piuha.net>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U3YzaMNAxhR1Ea1b_NN3YN8Hihc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 09:10:27 -0000

--Apple-Mail=_890ECBE3-7F80-458E-97AD-9763E2A14A56
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_FA29203E-523D-450C-8854-109E5EDBAC3B"


--Apple-Mail=_FA29203E-523D-450C-8854-109E5EDBAC3B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

For your information, based on IESG discussions we=92ve made
a few small, final edits to the most recent draft version. I plan to
approve the document tomorrow Friday.

The link to changes in -13 is below, but the main changes
are all clarifications or improved wording. They relate to
which counsel was referred to (IETF=92s), rules regarding
general technology background presentations in plenary,
role of the three principles wrt RFC 2026, removal of the
=93some evidence" text from 4.D that got there by accident,
suggestions around standards with multiple distinct parts,
recognition of defensive licenses, and uploading general
disclosures to the IETF web site.

I want to thank everyone who has contributed to this
effort.

(And I know 1.f has a typo that reveals what tools are
being used to format this draft :-) )

Jari

> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-bradner-rfc3979bis-13.txt
> Date: March 8, 2017 at 7:10:09 PM EST
> To: "Jorge Contreras" <cntreras@gmail.com>, "Scott Bradner" =
<sob@sobco.com>
>=20
>=20
> A new version of I-D, draft-bradner-rfc3979bis-13.txt
> has been successfully submitted by Scott Bradner and posted to the
> IETF repository.
>=20
> Name:		draft-bradner-rfc3979bis
> Revision:	13
> Title:		Intellectual Property Rights in IETF Technology
> Document date:	2017-03-08
> Group:		Individual Submission
> Pages:		25
> URL:            =
https://www.ietf.org/internet-drafts/draft-bradner-rfc3979bis-13.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/
> Htmlized:       =
https://tools.ietf.org/html/draft-bradner-rfc3979bis-13
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-bradner-rfc3979bis-13
>=20
> Abstract:
>   The IETF policies about Intellectual Property Rights (IPR), such as
>   patent rights, relative to technologies developed in the IETF are
>   designed to ensure that IETF working groups and participants have as
>   much information as possible about any IPR constraints on a =
technical
>   proposal as early as possible in the development process. The
>   policies are intended to benefit the Internet community and the
>   public at large, while respecting the legitimate rights of IPR
>   holders.  This document sets out the IETF policies concerning IPR
>   related to technology worked on within the IETF.  It also describes
>   the objectives that the policies are designed to meet.  This =
document
>   updates RFC 2026 and, with RFC 5378, replaces Section 10 of RFC =
2026.
>   This document also obsoletes RFC 3979 and RFC 4879.


--Apple-Mail=_FA29203E-523D-450C-8854-109E5EDBAC3B
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;"><div>For your information, based on IESG discussions =
we=92ve made</div><div>a few small, final edits to the most recent draft =
version. I plan to</div><div>approve the document tomorrow =
Friday.</div><div><br></div><div>The link to changes in -13 is below, =
but the main changes</div><div>are all clarifications or improved =
wording. They relate to</div><div>which counsel was referred to =
(IETF=92s), rules regarding</div><div>general technology background =
presentations in plenary,</div><div>role of the three principles wrt RFC =
2026, removal of the</div><div>=93some evidence" text from 4.D that got =
there by accident,</div><div>suggestions around standards with multiple =
distinct parts,</div><div>recognition of defensive licenses, and =
uploading general</div><div>disclosures to the IETF web =
site.</div><div><br></div><div>I want to thank everyone who has =
contributed to this</div><div>effort.</div><div><br></div><div>(And I =
know 1.f has a typo that reveals what tools are</div><div>being used to =
format this draft :-) =
)</div><div><br></div><div>Jari</div><div><br></div><div><div><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div><blockquote =
type=3D"cite" class=3D""><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetica, =
sans-serif;" class=3D""><b class=3D"">From: </b></span><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif;" class=3D""><a href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, 'Helvetica Neue', Helvetica, sans-serif;" =
class=3D""><b class=3D"">Subject: </b></span><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=3D""><b=
 class=3D"">New Version Notification for =
draft-bradner-rfc3979bis-13.txt</b><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, 'Helvetica Neue', Helvetica, sans-serif;" =
class=3D""><b class=3D"">Date: </b></span><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" =
class=3D"">March 8, 2017 at 7:10:09 PM EST<br class=3D""></span></div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, 'Helvetica Neue', Helvetica, sans-serif;" =
class=3D""><b class=3D"">To: </b></span><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" =
class=3D"">"Jorge Contreras" &lt;<a href=3D"mailto:cntreras@gmail.com" =
class=3D"">cntreras@gmail.com</a>&gt;, "Scott Bradner" &lt;<a =
href=3D"mailto:sob@sobco.com" class=3D"">sob@sobco.com</a>&gt;<br =
class=3D""></span></div><br class=3D""><div class=3D""><div class=3D""><br=
 class=3D"">A new version of I-D, draft-bradner-rfc3979bis-13.txt<br =
class=3D"">has been successfully submitted by Scott Bradner and posted =
to the<br class=3D"">IETF repository.<br class=3D""><br =
class=3D"">Name:<span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-bradner-rfc3979bis<br class=3D"">Revision:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>13<br =
class=3D"">Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Intellectual Property Rights in IETF Technology<br =
class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2017-03-08<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Individual Submission<br class=3D"">Pages:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>25<br =
class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/internet-drafts/draft-bradner-rfc3979bis-13.t=
xt" =
class=3D"">https://www.ietf.org/internet-drafts/draft-bradner-rfc3979bis-1=
3.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/" =
class=3D"">https://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/</a><=
br class=3D"">Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-bradner-rfc3979bis-13" =
class=3D"">https://tools.ietf.org/html/draft-bradner-rfc3979bis-13</a><br =
class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-bradner-rfc3979bis-13" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-bradner-rfc3979bis-13=
</a><br class=3D""><br class=3D"">Abstract:<br class=3D""> =
&nbsp;&nbsp;The IETF policies about Intellectual Property Rights (IPR), =
such as<br class=3D""> &nbsp;&nbsp;patent rights, relative to =
technologies developed in the IETF are<br class=3D""> =
&nbsp;&nbsp;designed to ensure that IETF working groups and participants =
have as<br class=3D""> &nbsp;&nbsp;much information as possible about =
any IPR constraints on a technical<br class=3D""> &nbsp;&nbsp;proposal =
as early as possible in the development process. The<br class=3D""> =
&nbsp;&nbsp;policies are intended to benefit the Internet community and =
the<br class=3D""> &nbsp;&nbsp;public at large, while respecting the =
legitimate rights of IPR<br class=3D""> &nbsp;&nbsp;holders. &nbsp;This =
document sets out the IETF policies concerning IPR<br class=3D""> =
&nbsp;&nbsp;related to technology worked on within the IETF. &nbsp;It =
also describes<br class=3D""> &nbsp;&nbsp;the objectives that the =
policies are designed to meet. &nbsp;This document<br class=3D""> =
&nbsp;&nbsp;updates RFC 2026 and, with RFC 5378, replaces Section 10 of =
RFC 2026.<br class=3D""> &nbsp;&nbsp;This document also obsoletes RFC =
3979 and RFC 4879.<br =
class=3D""></div></div></blockquote></div></div></div></div><br></body></h=
tml>=

--Apple-Mail=_FA29203E-523D-450C-8854-109E5EDBAC3B--

--Apple-Mail=_890ECBE3-7F80-458E-97AD-9763E2A14A56
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYwRv1AAoJEM80gCTQU46qivQP/1PkBQuFUXDqpVpO8Eh70QVf
YHV+BsPLSOo/W2XfSnhursHfNTsGRW68Y67EqZ22tlSQ+ggSQ2cnnNVhnnz4ud3y
dXTuUhVU2rw9n0IkwKhE2E1FyOQ4OXeDsDiDJNT2AG29DbEt9nCAtGAohsVssNbE
oBfBeaOjZrUqjatQmVqeauTBpnGZ8Z6lRrNtyOSxNGK05+9oN22xaspHy1Hg+eKx
wRqqxT5d60eIf1w+rnf/7rBdH1ISNdQpFPkSLb2jrCoVXiSRlqmohMxV3CIqRybF
f3CnF9xbtrr9SZV5Ap8DKFmDSXeGfZg8V+C+eL2LDKw644VYomauak1jfZ5docRg
+1ma77DPK0gcGQ8Tbsypt3qtXSvRhNgzjkWfqAdJ26ODceVvuubtdwtXufooKe7V
EZnfiootfPPw/MX4iy3AVKJXFVCTbXcF76oXD2c6K/ltf/7dbgQVO0sC29HX2M9m
7aTF2mMTTpUDSMikZ1mxcd/5jXytWZ3lzsZ6TIiKDaOLJSYcukBf0eOm9H7U+a+L
OdnJABM4uVOGSjRTxhAVWgM0AEpddFyqMXuU7Zw1Q+u+Xt4IQivkxK5k2nsgbN8w
6oUSmlftm8BDLHDx9FH1MsxYTz7d2CjC+3dEo7p1jIoClvC8hyew/x+iI2Ain4L1
i3Zd1qwo7Ay1GsnO1dl/
=Ar4p
-----END PGP SIGNATURE-----

--Apple-Mail=_890ECBE3-7F80-458E-97AD-9763E2A14A56--


From nobody Thu Mar  9 01:36:06 2017
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 D6772129438 for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 01:36:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id msiSOrqTRejJ for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 01:36:02 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0094.outbound.protection.outlook.com [104.47.2.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1A111293EE for <ietf@ietf.org>; Thu,  9 Mar 2017 01:36:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=RiRjRhhMnFASaxv3nk3jK+8zL9vQCgo3A6L67bUcUnY=; b=Uf5rzA56/ZFnU+UJ5XEnjVyPJZop1YqsgXiPoDNVi7KTeqXrr//dEtpMNIk8k/H4pTrjF7OyORsot34xBBTUIHoho29Rz40dxZCvV3L9UbOj0Pq4Cjk7tPykTBsLbdfGUVcdojOp3SJp5lUjQiJ9zlPpuXJ9ukTiZlSQLx3dhqU=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.185.203.75) by DB5PR07MB1558.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::8) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.961.8; Thu, 9 Mar 2017 09:35:58 +0000
Message-ID: <00c401d298b8$616fffa0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: IETF general list <ietf@ietf.org>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org> <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie> <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie> <CAAFsWK2RMGp0jqesx3cTbN=S7p0WuhH+0AbeJuuiZPF6WCbQOQ@mail.gmail.com> <BCEFAA3C-B711-4269-81C8-4DA0E1AA7AD0@dukhovni.org> <CAAFsWK3yJ9r+6abTXZQsNsey+VcRpdtVv=Hku_54_LZ9y1T2xQ@mail.gmail.com> <B8A5967B-9C19-4167-8A20-B82DFD46A924@dukhovni.org>
Subject: Re: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Date: Thu, 9 Mar 2017 09:34:35 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
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.185.203.75]
X-ClientProxiedBy: DB6PR0202CA0039.eurprd02.prod.outlook.com (2603:10a6:4:a5::25) To DB5PR07MB1558.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::8)
X-MS-Office365-Filtering-Correlation-Id: 117042ff-b545-4820-0a31-08d466cfb1a1
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DB5PR07MB1558;
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1558; 3:/9ImxB9mmd52uHPWrrPdUERm3VEEVUdhKlYEcLMJeVUjqzcCwzkjH+lkx9sYmM6BeHOPnV/RLY6Ph8REcpXSTAh1VRc5s0lKx9tvlTcYTkbXyLDxn0+Qeoh5mvusMgpCoCQMEbbItkYfpgwew2ZyiSOY0c+cFmO9u9FCboefgtrAuVY630YcOYnHoO6dE37UNvXotNkI5d2ivZzuQ93ju4LVMgi05RiZNaLxkMYx01EyZkEKhDiEyNmfVLav/gVbK+ZXi9aP/ff1dtY+zYtgpw==; 25:3H7pvwGdRUzZrCyZeWcTe1NfY7tSDkL1vQP7zhIB7lZIdtBUPkF7AnJOsBGXhoqrue09oMGpAWFiCVuNPJdz2L5ySQFkxRi7ETN5/sYozMtVtQI3qE8fh42D5Bjxd6Bu5KhMZQy6/xpM8A626Plp/N9e3Rr3vrkpMTtHuWjrDINTbw/yRILR5mcmcuXyLqBqJCGtV6dkSNYOT3NpF/6zxe3aP0wdAUHmwMm3fvw7xY4e0Yv17N132DZkoHBbsCi6BBMzUcMkmhNFtKV8Fl6sMkWNzQdwNoDwq1jiKwMmmCP5IFl+Ip/qzwmXOEHzIvnK/+ZpNzeq8FPZrAt2/NzKh4VqJAgk0DNW5ZT+wCWZNdCbsl0AIFpdYZD/EvIbVWc2wdgEFXdnYZ9PQ9K0ZTIsG7A4x2JqibvTSJK7gbBsVvlB3swpG2J0yL/PM86IQN0gSDiiZfL692vpdaJ3nWZQDA==
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1558; 31:sOngp8N3PH+QY6fbD4UpfLGRu+xnDYFx313B06QWUjAQ2YwoNH7g3JLWBQjzFZsm6ID6RN4ye/wdsuKJHgr2/I2Jp9WantCMak0aPMZLNnzgbzS9hruUNa8zmT6pl+iUEoyyH6QR/aZEeaEUM882z+kxHTy2gIsNZlYyOe8jKj/yszSPEsLwsU0Q0vgSNmiYbJL9+HcjcjwXHZPw06b1FJkIxXMxybKuKRZW2qWncpTM4DFNNOPShoj7oMJYl+c+aY89S0FDJPynnVw6/iVOXQ==
X-Microsoft-Antispam-PRVS: <DB5PR07MB155865CD7380FFC1B07258BAC6210@DB5PR07MB1558.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(192374486261705)(131327999870524)(211936372134217); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123558025)(20161123555025)(20161123560025)(20161123562025)(20161123564025)(6072148); SRVR:DB5PR07MB1558; BCL:0; PCL:0; RULEID:; SRVR:DB5PR07MB1558; 
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1558; 4:1VXRuvhzbehdmcKMVkfMkjcbbu65yIEeHVaMg0Mv2ZT8zoWukJ0XlgbJ++esR9IeDe+RR7bvH1msC+H0inSMEjRdILusqOdjNY6XjHz2PjfBc0PE+exCSZqWbWbM415x0A5kPpQl1+xo/ysnGNsO4Qa6Hzw0zj+JyeClhp3PWAqp6zGJGx3/Bh5E2TlWi9xQ3oRpKv4yRluJYlM0tFbaSXv9GsbSynTNVm7T+r7W4v3heMFh+d5yb7kyYYxNJ9CkZ1rGz9kjRrJVJELmJmuzZXQwzCa+f0HiziGni2NTnO4Y26BllScf8ZqnbfY+KuV886DhsIe0gdZocA1snUHfqjUMyGFUVLLcbHxcQ29bpaEqYDUcS8m12UGSECZg6KXLRJikWC93Fgf+cR6yDIAotnrl/ZVSWln8llh4B92EZtyvpDWU1kp4FGOJzTiIdyqDCjeFjW1X6OtezlLFlsrH3XgUNkBiotI1Ezbb4cGx8R0jHby/POZ6Lwjt8reAMvvhDE5FV14qYBdtlFv8we/T0GJErND7JFXTA3rKCbLW3alU34ZFNj0YpN+xRntuuIbQuKkPSWTfwnc6Y3yrFIyMxocY5pizfJDBwMDnqZG7XAibwbTkrSM6Z4h0NjWOLayDMorNioltDck30pfQzlx5GJa+YosfCvnRO3v/Hn+b+SyGOF1o059fXeEGfAnD5uUGWI1/G5w+zKF4uvtujIgqqsAtbW0dUCATpFnSkLXhAmU=
X-Forefront-PRVS: 0241D5F98C
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39450400003)(13464003)(24454002)(377454003)(305945005)(86362001)(7736002)(62236002)(44716002)(81166006)(44736005)(561944003)(2906002)(66066001)(5820100001)(84392002)(9686003)(189998001)(1556002)(47776003)(8676002)(33646002)(93886004)(4720700003)(6916009)(2870700001)(6246003)(81686999)(76176999)(38730400002)(110136004)(116806002)(3846002)(6666003)(50986999)(6496005)(81816999)(5660300001)(53936002)(6116002)(230783001)(61296003)(42186005)(23676002)(6486002)(1456003)(50226002)(50466002)(229853002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR07MB1558; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjVQUjA3TUIxNTU4OzIzOmNPSTJqb09zWmt5emw2UXV2bDE1YmI1bzRv?= =?utf-8?B?M3puYnNmRkV2bGdDV1hGT2twYnA3czBxMVZEeHFkMnR1NDNLN2NvM3d5OUt4?= =?utf-8?B?bmZnUVJVYlN5Lzljc1EyRU9mbnlNOFpnSUdrVFg2ZjFDNkNTREZ1elhiaWRJ?= =?utf-8?B?UTJEU2dPK21jdDNSU0tQKzF3RkJZb2Y5dEpjSEk1emFEdWhRbmRGQkJxU3dP?= =?utf-8?B?WnRidkVCaVJiS0Z2cFk5RDQ2K0tKTVhIbTRTdTNKeHR0TEZ1YmxEQlB3RUNl?= =?utf-8?B?Z3E2eXJxWGk4eHNBVUhLanpGeEdsMWpGWmZ0eko3WVVhRi9EMmY4NStKbWxt?= =?utf-8?B?VlIzcFNPNE5XSUZyQm90YU01R3RYbGtVUzdKRGMwNS9oZjQ3WmJoaHNCczdV?= =?utf-8?B?dEFETEcwY1dRZmh1cTFNTU1VblhGUTJQVmt6NW1RTU9zNTdTUCtPWGVBaFpJ?= =?utf-8?B?ZkpaZGNhRmJMeGhZRmRMc1Rvd0Q2K2Z2UjcyRjlPd01TWEEvSVVBM3NUUWc3?= =?utf-8?B?azBKQy9QZDk2WmVuVHBSbGNnbEpDYWlKTHBDVlc3aEl0TVZlS09iaXZPdDdm?= =?utf-8?B?QU1ENU1HVDBaMlptbDFQckJzb1piRVArRkN3Y2lJd1ZQWEllblg2RWVVam5w?= =?utf-8?B?RDUrYmRmZXphM1NVVzNDTkNyS0diUUREWmRHK1J2NUZwRkk3bllPa2Q4aE04?= =?utf-8?B?SmNRdHhkYnpHeWxLZFdTSEFSV0hPbmd6dkxrUXJqcUF0Uk83amF5SHJTcE8r?= =?utf-8?B?L1Zxb2lRM3Z4T0tDcmxDNDdJTlBGY0lUUWwwODg5ZVNLa3l6aFl5OUpMeW5X?= =?utf-8?B?TVRnYjBoMnhnMjlUajZOOHVuVEdUWDlXYmlxa2hYMTJVN1liQThiSE9xdmo1?= =?utf-8?B?NjRLbTdFajViem0xOWxNOUpZaEFGQnMyeUVremNCdk1WeGNyNGhraXBKR2l3?= =?utf-8?B?N1BOcU9RQUFXSkMvSlhKbkpyR3U0Z3Z6QnlZQ3haRUYybVM4OUtjR0hYUTJT?= =?utf-8?B?Q1ZyTndSOG5UeHB6U3BHeUErelltYXY3NVhOVW9aU0tUSVI0SFZ4TWpqN0to?= =?utf-8?B?L3Zpb3VwOUNiYWJYMjJuQnc2VUU5bUxkb2FTL2VuVjBtaDFiNWlub015UEkx?= =?utf-8?B?d0l4U3pHVkZJU3FqcmJXQ0NqZVdIT3dwd210UTBoMUFMNHYxOHFSYmZiNlhQ?= =?utf-8?B?c3dQOE55UzhSRXVtQU14c1pDQlJNdnpaSVdpZkhVZnRRaUV1Y0xZL1RiVHUr?= =?utf-8?B?UU13VzUrT3hiajk2NXA5RWNuMWUxL1RZeXpGODhaRFdRNWxFU0FBR1grWEZU?= =?utf-8?B?TWVrblc4a2JXZzltR1FUSzlnQzZVUStDUmRoaWlWMzBhQm9PeS8zVWxmTlpt?= =?utf-8?B?dU9XSE5vckNjcDNpc3BmWlZoa0EzZGhiZ3lsMVNQK2pIREZkZDlLbFZ5WjZq?= =?utf-8?B?Z0RoZlVqSlVYUlhaQ0FwcmFrd2RsTWtqQWRVRXk0d1ppRGlXajhQdDZtSkN1?= =?utf-8?B?NmZOMWh3bVU0b0htK21GQUN5MUJEVFlLcjZnTzdrNVlySm1LRXBYM0xFQVM2?= =?utf-8?B?RzU1ZG1YelAxZStGN0w4QTlCa1o4RUdXSk9CK3ZiMXZMRndYRWRJY2RUUVJF?= =?utf-8?B?RGUzcVpJR1dPVDFLcGRYSWNsaE9TWU5BSHZCbXBXd2huWVJMNzZzc2xRPT0=?=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1558; 6:7uY/VjcBLTCRZ7w/4194OywCx9xxmLmSBKIgDX2uZZHXDjSJdA7YXgkl8ipeK8AAFiO7Jh8ENtemkRnEEE/6nK19nHKz2RD1cBId9KADYwb9I/KK9fEuyX28Ig32Po9rIgargtsHjrRelPJQBXJgvGeKdvn5MbPoqKd0fIgfCcsWEf+WQJDc7mQ+IYmfA2mR4JGu4KBC/tHSpaqSoCuDtO/lSJkesIxz0h7rm8hdj7O0iqf+SnpeEo6eWtFmSmIoHWor6WFRvKdIAnxb8+65m/mRivpx45U4AkBlmPA/KZzwbX2VfG64KzYMEsfQdCyIJ4NoOgsK9gtCc8gDjBEJ64AME4vbFEDWcZK0uh1YEY/4T8C2U/mCXyPX6rOk0V6jYSL1v5r934/GqUQPmHpbyQ==; 5:P2+0KKiMbx3auA9Vk6vZflkQAcPkQXDT5lZDokDbqf56oO7WkRVw1HaaflHhQAyq0xxJk0dFFEPlVAhdKrIaR+dzVVvGhjygeG7DonvhNAWhgMSgxgS3MNpaq8ngd0f1/0Yds9Xc07bbg90mZtDRwJqK6j9eIpFZiu/B4TXdQG0=; 24:fgbdk6mCYqWiXPJGnHdVfxs1WZCsmX4w2QzY8hVsixS+9El96J15HPCrwmQlCUxhH288ND+s0U8gmoj6GPfSztw/KstmjU1vYlVdJEBy6zk=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1558; 7:/cu/s5eEhSDjZ5ELOMpSo4eBJCovKZitwiFsuf91q1nqfvBrtbMGSnP41pdPo34LgXFcaV7qW6FqXIxuJDWiRo3l4mc9XuAMuO6YNgMgj2BTaDF9lw0KoQPqPlr/cpic4rwXkN2tXzOd3zUwl7ZW65ZQZazLa3pkEiXR6QqLaHnpAm+E1YwM5ecra2NgIf5RJF4SwJINWch8IuuFLBsHbBF/Smt7sPX92IE4RGV+FIwbbUTVOguvHSxAtXd8z5ygTW1M/wIu320szyU3eO3tn177kIU8dZ+WwlHnoH1jo1YQdxuCNiB4lFUOAJxZi74obIVgrqHQVtb+1PwZE45fcA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Mar 2017 09:35:58.8279 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1558
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5oqJJY1leIZvHoUTGwttaWIZ-NE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 09:36:05 -0000

----- Original Message -----
From: "Viktor Dukhovni" <ietf-dane@dukhovni.org>
To: <spasm@ietf.org>; "IETF general list" <ietf@ietf.org>
Sent: Thursday, March 09, 2017 3:19 AM
> On Mar 8, 2017, at 8:17 PM, Wei Chuang <weihaw@google.com> wrote:
>
> Okay.  I think the direction then is to have SmtpUTF8Name respect
rfc822Name name constraints and vice versa.

Well, no, the simplest proposal on the table is for SmtpUTF8Name to
be *prohibited* when rfc822Name constraints are present and SmtpUTF8Name
constraints are not.  When both present, they can operate independently.

<tp>

Getting security right can be tricky as the legion of failed attempts
that make it to RFC testify but what you are proposing here seems so
simple, so obviously the right thing to do that I am puzzled, bewildered
even, that anyone can disagree with you.

Tom Petch

The verifier logic is then:

1. If neither rfc822Name constraints nor SmtpUTF8Name constraints
           are present in any CA certificate in the chain, any mixture
of
           rfc822Name and SmtpUTF8Name SAN elements is valid.

2. If some certificate in the chain contains *only* rfc822Name
   constraints, then these apply to rfc822Name SAN elements, but
   all SmtpUTF8Names are prohibited.

3. When both types of constraints are present in all CA certificates
           that have either type, then constraints for each SAN type are
   exclusively based on just the corresponding constraint type.

4. If some certificate in the chain contains only SmtpUTF8Name
     constraints then those are unavoidably at risk of bypass via
           rfc822Name SAN elements when processed by legacy verifiers.
   Therefore, this should be avoided, and the CA needs to
     publish rfc822Name constraints that prevent bypass.  Such
   constraints *need not* be equivalent (not always possible)
   to the desired SmtpUTF8Name constraints.  Rather, it suffices
   to not permit rfc822Name elements that would be prohibited
   if they were simply cut/pasted (with no A-label to U-label
           conversions) as SmtpUTF8Name elements.  It is not necessary
   for these to permit everything that SmtpUTF8Name permits.

Thus for example, if SmtpUtf8Name only permits addresses in the non
NR-LDH
domain "духовный.org" (or a specific set of addresses in such a domain),
then the corresponding rfc822Name constraint could just permit "." (or
the
reserved "invalid" TLD if that's preferable) which is not a usable email
domain.  This ensures that only the permitted SmtpUTF8Name SANs are used
and no rfc822Name SANs are used.

If, instead the Smtp8Name constraints are excluded non-ASCII address
forms,
then since these have no literal rfc822Name equivalents, the rfc822Name
constraints can be omitted with the same effect.

Only when the intention is to permit NR-LDH domains with either ASCII or
UTF-8 localparts (or an all-ASCII full address) do the rfc822Name and
SmtpUTF8Name constraints need to be fully equivalent.  This is of course
trivial to do.  Just cut/paste the same string into both types of
constraint.

--
Viktor.


From nobody Thu Mar  9 06:19:38 2017
Return-Path: <prvs=234c810c4=Badri.Subramanyan@ril.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ACA8129658; Thu,  9 Mar 2017 06:19:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dcGHxnTIWoTF; Thu,  9 Mar 2017 06:19:33 -0800 (PST)
Received: from gwsmtp011.ril.com (gwsmtp011.ril.com [116.50.78.50]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18358129649; Thu,  9 Mar 2017 06:19:28 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.36,268,1486405800"; d="scan'208";a="363759333"
From: <Badri.Subramanyan@ril.com>
To: <kathleen.moriarty.ietf@gmail.com>, <saag@ietf.org>, <ietf@ietf.org>
Subject: RE: Last call feedback: draft-mm-wg-effect-encrypt
Thread-Topic: Last call feedback: draft-mm-wg-effect-encrypt
Thread-Index: AQHSmEkdymufh+be8EG0ggEJbV3WwqGMUL1A
Date: Thu, 9 Mar 2017 14:19:19 +0000
Message-ID: <de0f76fc31094afc8f5951c3654fb07e@SIDC1EXMBX24.in.ril.com>
References: <CAHbuEH4+bd=0PJa1rWDQN6tbeRK5vXKdbcUwsj2=zf9V8ejeDg@mail.gmail.com>
In-Reply-To: <CAHbuEH4+bd=0PJa1rWDQN6tbeRK5vXKdbcUwsj2=zf9V8ejeDg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2ewhfgIptwICK35jw1Dl27O7sJ8>
Cc: acmorton@att.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 14:19:36 -0000

S2F0aGxlZW4vQWwsDQoNCglUaGFua3MgZm9yIHRoZSBjbGFyaWZpY2F0aW9uLiBJIGhhdmUgaW5j
bHVkZWQgbXkgY29tbWVudHMgaW5saW5lLiANCglJIGFtIHN0aWxsIGxvb2tpbmcgZm9yIHJlZmVy
ZW5jZXMgYW5kIHdpbGwgc2VuZCBpdCBvdXQgYXMgSSBmaW5kIHRoZW0uDQoNClRoYW5rcywNCkJh
ZHJpDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBLYXRobGVlbiBNb3JpYXJ0
eSBbbWFpbHRvOmthdGhsZWVuLm1vcmlhcnR5LmlldGZAZ21haWwuY29tXSANClNlbnQ6IFdlZG5l
c2RheSwgTWFyY2ggMDgsIDIwMTcgMjoxOCBQTQ0KVG86IHNhYWdAaWV0Zi5vcmcNCkNjOiBCYWRy
aSBTdWJyYW1hbnlhbiA8QmFkcmkuU3VicmFtYW55YW5AcmlsLmNvbT47IEFMRlJFRCBDIE1PUlRP
TiAoQUwpIDxhY21vcnRvbkBhdHQuY29tPjsgc3RlcGhlbi4gZmFycmVsbCA8c3RlcGhlbi5mYXJy
ZWxsQGNzLnRjZC5pZT4NClN1YmplY3Q6IExhc3QgY2FsbCBmZWVkYmFjazogZHJhZnQtbW0td2ct
ZWZmZWN0LWVuY3J5cHQNCg0KSGVsbG8gQmFkcmksDQoNClRoYW5rIHlvdSB2ZXJ5IG11Y2ggZm9y
IHlvdXIgcmV2aWV3IGFuZCBmZWVkYmFjayBvbiB0aGUgZHJhZnQuICBUaGlzIGlzIHZlcnkgaGVs
cGZ1bCB0byBhZGQgaW4geW91ciBwZXJzcGVjdGl2ZS4gIEkgZG8gaGF2ZSBhIGZldyBxdWVzdGlv
bnMgaW4gbGluZSBhbmQgYW0gaG9waW5nIHlvdSBoYXZlIHNvbWUgZ29vZCByZWZlcmVuY2VzIGZv
ciB1cyB0byBjaXRlIGFzIHdlbGwuICBXZSBuZWVkIHRvIGdldCBhIGRyYWZ0IHJldmlzaW9uIG91
dCBieSBGcmlkYXksIHNvIGhvcGVmdWxseSB3ZSBjYW4gaXRlcmF0ZSBxdWlja2x5Lg0KDQoNCj4N
Cj4gT24gRmViIDIzLCAyMDE3LCBhdCA5OjU0IEFNLCAiQmFkcmkuU3VicmFtYW55YW5AcmlsLmNv
bSINCj4gPEJhZHJpLlN1YnJhbWFueWFuQHJpbC5jb20+IHdyb3RlOg0KPg0KPiBIZWxsbywNCj4N
Cj4NCj4NCj4gICAgICAgICAgICAgICAgIEkgd29yayBmb3IgYSBNb2JpbGUgU2VydmljZSBQcm92
aWRlciBhbmQgd2FudGVkIHRvIA0KPiBzdGFydCBieSB0aGFua2luZyB5b3UgZm9yIHB1dHRpbmcg
dGhpcyBkb2N1bWVudCB0b2dldGhlciAoRWZmZWN0cyBvZiANCj4gUGVydmFzaXZlIEVuY3J5cHRp
b24pLiBFbmNyeXB0aW9uIG9mIGNvbnRlbnQgaGFzIGJlZW4gaW1wYWN0aW5nIHRoZSANCj4gc2Vy
dmljZSBwcm92aWRlcnMgZm9yIHNvbWV0aW1lLCBhbmQgdGhpcyBkb2N1bWVudCBvdXRsaW5lcyBp
dCB2ZXJ5IA0KPiB3ZWxsLiBJIGhhZCBhIGZldyBjb21tZW50cy9zdWdnZXN0aW9ucyBvbiB0aGUg
ZG9jdW1lbnQuIFRoaXMgZG9jdW1lbnRzIA0KPiBpcyBjb21wcmVoZW5zaXZlLCBidXQgdGhlcmUg
YXJlIGEgZmV3IGltcGFjdHMgbW9yZSBzcGVjaWZpYyB0byBNb2JpbGUgDQo+IENhcnJpZXJzIHdo
aWNoIEkgdGhvdWdodCB3ZXJlIG5vdCBpbmNsdWRlZC4gSSB3b3VsZCBncmVhdGx5IGFwcHJlY2lh
dGUgDQo+IGl0LCBpZiB5b3UgY291bGQgbG9vayBpbnRvIHRoZXNlIGFuZCBtb2RpZnkgdGhlIGRv
Y3VtZW50IGFzIHN1aXRlZC4NCj4NCj4NCj4NCj4gMS4gICAgICAgQUxHIOKAkyBBcHBsaWNhdGlv
biBMYXllciBHYXRld2F5LCBpcyBhIGZlYXR1cmUgdXNlZCBieSBGaXJld2FsbHMsDQo+IE5BVCBi
b3hlcyBhbmQgTG9hZCBCYWxhbmNlcnMgdG8gaWRlbnRpZnkgc3RyZWFtcyB3aGljaCBhcmUgcmVs
YXRlZCBhbmQgDQo+IHRyZWF0IHRoZW0gYWxpa2UuIE1hbnkgb2YgdGhlIHByb3RvY29scyB3b3Jr
IGluIGNvbmp1bmN0aW9uIHRvIGRlbGl2ZXIgYSBzZXJ2aWNlLg0KPiBFZy4gUlRTUC9SVENQL1JU
UCBwcm90b2NvbHMgYXJlIHVzZWQgdG8gcHJvdmlkZSB2aWRlbyBzZXJ2aWNlLiBSVFNQIA0KPiB1
c2VzIFRDUCBhbmQgbmVnb3RpYXRlcyB0aGUgVURQIHBvcnRzIHVzZWQgZm9yIFJUUCBhbmQgUlRD
UCANCj4gY29tbXVuaWNhdGlvbi4gUlRTUCBhbmQgUlRDUCBmb3JtIHRoZSBjb250cm9sIHBsYW5l
LCB3aGVuIFJUUCBmb3JtcyB0aGUgZGF0YSBwbGFuZS4NCj4NCj4gYS4gICAgICAgVGhlIEFMRyBm
ZWF0dXJlIG1ha2VzIHRoZSBGaXJld2FsbCBhcHBsaWNhdGlvbi1hd2FyZSBhbmQgYWxsb3cgb3IN
Cj4gYmxvY2sgYSB2aWRlbyBjb250ZW50IGFzIGRlc2lyZWQuDQo+DQo+IGIuICAgICAgVGhpcyBm
ZWF0dXJlIGlzIGFsc28gdXNlZCBhcyBvZiB0b2RheSBvbiB0aGUgRmlyZXdhbGwgb3IgTkFUIGJv
eC4NCj4gVGhlIHNjZW5hcmlvIGhlcmUgaXMsIHRoZSBGVy9OQVQgYm94IGFjdHMgYXMgYSBkZW1h
cmNhdGlvbiBwb2ludCANCj4gYmV0d2VlbiB0aGUgRE1aIGFuZCB1bnRydXN0ZWQgbmV0d29yaywg
d2hpY2ggYWxsb3dzIG91dCBib3VuZCB0cmFmZmljIA0KPiBhbmQgYW55IGZsb3cgaW5pdGlhdGVk
IGZyb20gd2l0aGluIHRoZSBETVouIFdoZW4gd2UgaGF2ZSBzZXJ2aWNlIHdpdGggDQo+IG11bHRp
cGxlIGZsb3dzLCBzb21lIG9mIHRoZXNlIGNvdWxkIGJlIGluaXRpYXRlZCBmcm9tIHdpdGhpbiB0
aGUgRE1aLCANCj4gd2hpY2ggc2hvdWxkIGVuYWJsZSBvdGhlciBmbG93cyBpbiBib3RoIGRpcmVj
dGlvbnMuIEVnLiBSVFNQIFJlcXVlc3QgDQo+IGZyb20gd2l0aGluIHRoZSBETVogd291bGQgbmVl
ZCB0byBhbGxvdyBSVFAgcGFja2V0cyBmcm9tIHRoZSB1bnRydXN0ZWQgDQo+IHpvbmUgaW50byB0
aGUgRE1aLiBUaGUgRlcvTkFUIGJveCBjYW4gb25seSBhbGxvdyB0aGlzIGlmIHRoZXkgYXJlIA0K
PiBhd2FyZSBvZiB0aGUgY28tcmVsYXRpb24gYmV0d2VlbiB0aGUgZGlmZmVyZW50IGZsb3dzIHVz
aW5nIGZlYXR1cmUgbGlrZSBBTEcuDQo+DQo+IGMuICAgICAgIFRoZSBBTEcgZmVhdHVyZSBvbiBh
IExCIHNpbWlsYXJseSB3b3VsZCBhbGxvdyB0aGUgaWRlbnRpZmljYXRpb24gb2YNCj4gdGhlIGRp
ZmZlcmVudCBjby1yZWxhdGVkIGZsb3dzIGFuZCB0cmVhdCB0aGVtIGFsaWtlIOKAkyBhbGxvdywg
YmxvY2ssIExCIA0KPiB0aGVtIHRvIHRoZSBzYW1lIHNlcnZlciBvciByZS1yb3V0ZSB0byBhbm90
aGVyIHNldCBvZiBzZXJ2ZXJzLg0KPg0KPiBJZiB0aGUgc3RyZWFtcyBhcmUgZW5jcnlwdGVkLCB0
aGVuIHRoZSBBTEcgZmVhdHVyZSB3b3VsZCBiZSByZW5kZXJlZCANCj4gdXNlbGVzcy4gVGhpcyB3
b3VsZCBsaW1pdCB0aGUgY2FwYWJpbGl0eSBvZiBhbnkgbmV0d29yayBlbGVtZW50IHRvIA0KPiBt
YWtlIHNtYXJ0IHBvbGljaW5nIGFuZCByb3V0aW5nIGRlY2lzaW9ucyBiYXNlZCBvbiBhcHBsaWNh
dGlvbiBsYXllciBhdHRyaWJ1dGVzLg0KDQpEbyB5b3Uga25vdyBpZiB0aGVzZSBjYW4gd29yayB3
aXRoIGEgMi10dXBsZSBvciA1LXR1cGxlPyAgSXMgdGhlcmUgYW4gaW1wYWN0IGZyb20gZW5jcnlw
dGlvbiB2aWEgVExTIGZvciBpbnN0YW5jZT8gIElmIHNvLCB3aGF0IGlzIHRoYXQgaW1wYWN0Pw0K
W0JhZHJpXSBUaGUgcnVsZXMgaW4gbW9zdCBvZiB0aGUgY2FzZXMgaXMgNS10dXBsZSB0byBhY2N1
cmF0ZWx5IGRlcGljdCBhIGZsb3cuIFllcywgdGhlcmUgaXMgYW4gaW1wYWN0IGZyb20gZW5jcnlw
dGlvbiB2aWEgVExTIGFzIG1vc3Qgb2YgdGhlIGltcGxlbWVudGF0aW9ucyBvZiBBTEcgZ2V0IGlu
Zm9ybWF0aW9uIHJlZ2FyZGluZyBzdXBwb3J0aW5nIHByb3RvY29scyBieSBwYXJzaW5nIGRhdGEu
IFdpdGggVExTIGVuY3J5cHRpb24sIHRoZSBBTEcgbG9zZXMgdGhlIGFiaWxpdHkgdG8gcGFyc2Us
IGhlbmNlIGdldCBpbmZvcm1hdGlvbiBvbiB0aGUgc3VwcG9ydGluZyBwcm90b2NvbHMuDQoNCldo
YXQgaXMgdXNlZCBieSBBTEcgdG8gY29ycmVsYXRlIHN0cmVhbXM/ICBUaGlzIHdvdWxkIGJlIGhl
bHBmdWwgdG8gdW5kZXJzdGFuZCBpZiB0aGlzIHBhcnRpY3VsYXIgbWV0aG9kIGZvciBBTEdzIGRv
ZXMgYmVjb21lICd1c2VsZXNzJw0KYW5kIGFsc28gdG8gZmlndXJlIG91dCBpZiBvdGhlciBvcHRp
b25zIG1heSBleGlzdCB0byBwZXJmb3JtIHRoZSBmdW5jdGlvbnMgbmVlZGVkLg0KW0JhZHJpXSBS
RkMgMjY2MywgU2VjdGlvbiAyLjkgZ2l2ZXMgaW5mb3JtYXRpb24gYWJvdXQgQUxHLiBUaGVyZSBp
c27igJl0IG9uZSBkZWZpbmVkIG1ldGhvZCB0byBpbXBsZW1lbnQgaXQgYW5kIHNvbWUgb2YgdGhl
IG1ldGhvZHMgdXNlZCBieSB2ZW5kb3JzIGFyZSBpbmNsdWRlZCBiZWxvdy4NCjEuICBQYXJzZSB0
aGUgY29udGVudCBvZiB0aGUgcHJpbWFyeSBzdHJlYW0gYW5kIGlkZW50aWZ5IHRoZSA1LXR1cGxl
IG9mIHRoZSBzdXBwb3J0aW5nIHN0cmVhbXMgYXMgaXQgaXMgYmVpbmcgbmVnb3RpYXRlZC4NCjIu
IEludGVyY2VwdCBhbmQgbW9kaWZ5IHRoZSA1LXR1cGxlIGluZm9ybWF0aW9uIG9mIHRoZSBzdXBw
b3J0aW5nIHN0cmVhbSBhcyB0aGUgaXQgaXMgYmVpbmcgbmVnb3RpYXRlZCBvbiB0aGUgcHJpbWFy
eSBzdHJlYW0uIFRoaXMgaXMgYSBsaXR0bGUgbW9yZSBpbnRydXNpdmUgaW4gbmF0dXJlLg0KDQpE
byB5b3UgaGF2ZSByZWZlcmVuY2VzIG9uIHRoaXMgdGhhdCBhcmUgc3RhYmxlIChvbmVzIHdlIGNh
biBjaXRlIGluIGFuIFJGQyk/DQpSRkMgMjY2MywgU2VjdGlvbiAyLjkNCg0KSSBoYXZlIGFsc28g
c3BlbGxlZCBvdXQgc29tZSBvZiB0aGUgYWNyb255bXMgYmVsb3cNClJUU1AgLSBSZWFsIFRpbWUg
U3RyZWFtaW5nIFByb3RvY29sDQpSVENQIC0gUmVhbCBUaW1lIENvbnRyb2wgUHJvdG9jb2wNClJU
UCAtIFJlYWwgVGltZSBQcm90b2NvbA0KQUxHIC0gQXBwbGljYXRpb24gTGV2ZWwgR2F0ZXdheS9B
cHBsaWNhdGlvbiBMYXllciBHYXRld2F5DQpMQiAtIExvYWQgQmFsYW5jZXJzDQpETVogLSBEZW1p
bGl0YXJpemVkIFpvbmUNCkZXIC0gRmlyZXdhbGwNCg0KPg0KPiAyLiAgICAgICBPdmVyLVRoZS1U
b3AgQ2FjaGluZyB3ZWIgY29udGVudCDigJMgWW91IGRpZCB0b3VjaCB1cG9uIHRoaXMgdG9waWMg
aW4NCj4gc2VjdGlvbiAyLjEuNCwgYnV0IEkgdGhpbmsgdGhpcyBpcyBhIGJpZyBlbm91Z2ggdG9w
aWMgdGhhdCBpdCB3YXJyYW50cyANCj4gaXRzIG93biBzdWJzZWN0aW9uLiBBcyB0aGUgSW50ZXJu
ZXQgdHJhZmZpYyBpbmNyZWFzZXMgYWNyb3NzIHRoZSANCj4gd29ybGQsIE1vYmlsZSBDYXJyaWVy
cyBhbmQgb3RoZXIgU2VydmljZSBQcm92aWRlcnMgYXJlIHVzaW5nIGNhY2hpbmcgDQo+IHNvbHV0
aW9uIHRvIGtlZXAgdXAgd2l0aCB0aGUgYmFuZHdpZHRoIG5lZWRzLiBDYWNoaW5nIGF0IGEgaGln
aCBsZXZlbCANCj4gd291bGQgYWxsb3cgZm9yIHdlYi92aWRlbyBhbmQgb3RoZXIgY2FjaGVzIHRv
IGJlIGxvY2F0ZWQgY2xvc2VyIHRvIHRoZSANCj4gY3VzdG9tZXJzLiBUaGUgZmlyc3QgdGltZSBh
IGNvbnRlbnQgaXMgcmVxdWVzdGVkLCBpdCBpcyBzdG9yZWQgaW4gdGhlIA0KPiBjYWNoZSBhbmQg
ZXZlcnkgcmVxdWVzdCBnb2luZyBmb3J3YXJkIHdvdWxkIGJlIHNlcnZlZCBmcm9tIHRoZSBjYWNo
ZSANCj4gdGh1cyBjdXR0aW5nIGRvd24gb24gdGhlIGJhY2toYXVsIHRvbm5hZ2UgYmV0d2VlbiB0
aGUgc291cmNlIG9mIHRoZSANCj4gY29udGVudCBhbmQgdGhlIGNhY2hlLiBUaGlzIG5vdCBvbmx5
IGhlbHBzIGluIGN1dHRpbmcgZG93biBvbiB0aGUgDQo+IGJhbmR3aWR0aCByZXF1aXJlbWVudHMs
IGJ1dCBhbHNvIGN1dHMgZG93biBvbiB0aGUgbGF0ZW5jeSB3aXRoIHF1aWNrZXIgdGltZSB0byBm
aXJzdCBieXRlIGFuZCBpbXByb3ZlcyBjdXN0b21lciBleHBlcmllbmNlLg0KPiBNb2JpbGUgQ2Fy
cmllcnMgYXJlIGRlcGxveWluZyBjYWNoZXMgY2xvc2VyIHRvIHRoZSBjdXN0b21lcnMsIHRodXMg
DQo+IGN1dHRpbmcgZG93biBsYXRlbmN5IGRyYXN0aWNhbGx5LiBUaGVzZSBjYWNoZXMgcGxheSBh
biBldmVuIG1vcmUgDQo+IHNpZ25pZmljYW50IHJvbGUgd2hlbiB0aGUgbGF0ZW5jeSB0byB0aGUg
ZGVzdGluYXRpb24gaXMgdmVyeSBoaWdoLCBlZzogDQo+IE1vYmlsZSBjYXJyaWVyIGlzIGxvY2F0
ZWQgaW4gdGhlIEFzaWEsIGJ1dCB0aGUgc291cmNlIGNvbnRlbnQgaXMgbG9jYXRlZCBpbiBVUyBv
ciB2aWNlIHZlcnNhLg0KPiBUaGlzIGFsc28gaGVscHMgbW9iaWxlIGNhcnJpZXJzIGxvY2F0ZWQg
b3V0c2lkZSBvZiBVUywgdG8gY3V0IGRvd24gb24gDQo+IHRoZWlyIEludGVybmV0IHRyYWZmaWMg
dG8gdGhlIFVTLCB3aGljaCBkaXJlY3RseSB0cmFuc2xhdGVzIHRvIA0KPiBzYXZpbmdzLiBUaGUg
Y2FjaGUgc2VydmVyIHVzZXMgaW5mb3JtYXRpb24gaW4gdGhlIEhUVFAgaGVhZGVycywgDQo+IHBh
eWxvYWQgYW5kIG90aGVyIGF0dHJpYnV0ZSB0byBtYWtlIHRoZSBlZmZlY3RpdmUgY2FjaGluZyBk
ZWNpc2lvbnMuIA0KPiBBcyB3ZSBtb3ZlIHRvIGVuY3J5cHRpb24gdGhlIGNhY2hlIHNlcnZlciBk
b2VzIG5vdCBoYXZlIHRoaXMgaW5mb3JtYXRpb24sIHJlbmRlcmluZyB0aGVtIHVzZWxlc3MuDQoN
CkRvIHlvdSBoYXZlIHJlZmVyZW5jZXMgb24gdGhpcyB0cmVuZD8gIEl0IHdvdWxkIGJlIGdvb2Qg
aWYgd2UgY2FuIGNpdGUgYSByZXNvdXJjZSBhcyB3ZSBhbHNvIGhlYXJkIGF0IHRoZSBNQVJORVcg
d29ya3Nob3AgdGhhdCBzb21lIGNvbnRlbnQgY2FycmllcnMgcHJlZmVyIGVuZC10by1lbmQgc29s
dXRpb25zLiAgSW4gdGhhdCBjYXNlLCBjYWNoaW5nIHdvdWxkbid0IHdvcmsgYW55d2F5LiAgSWYg
dGhlcmUgYXJlIHRyZW5kcyBpbiBib3RoIGRpcmVjdGlvbnMsIGl0IHdvdWxkIGJlIGdvb2QgdG8g
Y2l0ZSByZXNvdXJjZXMuDQpDYWNoaW5nIGhlbHBzIGluIHJlZHVjaW5nIExhdGVuY3kgYW5kIElu
dGVybmV0IGJhbmR3aWR0aCBmb3IgdGhlIGEgTW9iaWxlIENhcnJpZXIsIHdoaWNoIGlzIHRoZSBi
YXNpcyBvZiBIVFRQIENhY2hpbmcgYXMgZGVzY3JpYmVkIGluIFJGQyA3MjM0LiBMZXQgbWUgY2hl
Y2sgdG8gc2VlIGlmIHRoZXJlIGFyZSBhbnkgd2hpdGUgcGFwZXJzIHdoaWNoIHRhbGsgYWJvdXQg
dGhpcyB0cmVuZCBvZiB1c2luZyBPVFQgQ2FjaGVzLi4uDQpSRkMgNzIzNCBnaXZlcyBpbmZvcm1h
dGlvbiBvbiBIVFRQIENhY2hpbmcgYW5kIHRoZSBleHBlY3RlZCBiZW5lZml0cy4gDQo+DQo+IDMu
ICAgICAgIEhUVFAgaGVhZGVyIGVucmljaG1lbnQg4oCTIEhUVFAgaGVhZGVyIGVucmljaG1lbnQg
aGFzIGJlZW4gYQ0KPiBtZWNoYW5pc20gZm9yIHRoZSBtb2JpbGUgY2FycmllciB0byBwcm92aWRl
IOKAnGFsbG93ZWTigJ0gKE5vbi1DUE5JKSANCj4gc3Vic2NyaWJlciBpbmZvcm1hdGlvbiB0byB0
aGlyZCBwYXJ0aWVzIG9yIG90aGVyIGludGVybmFsIHN5c3RlbXMuIFRoZSANCj4gdGhpcmQgcGFy
dGllcyBjYW4gaW4gdHVybiBwcm92aWRlIGN1c3RvbWl6ZWQgc2VydmljZSwgb3IgdXNlIGl0IHRv
IA0KPiBiaWxsIHRoZSBjdXN0b21lciBvciBhbGxvdy9ibG9jayBzZWxlY3RpdmUgY29udGVudOKA
pi4gVGhpcyANCj4gaGVhZGVyLWVucmljaG1lbnQgbWV0aG9kIGlzIGFsc28gdXNlZCB3aXRoaW4g
dGhlIE1vYmlsZSBDYXJyaWVyIHRvIA0KPiBwYXNzIGluZm9ybWF0aW9uIGludGVybmFsbHkgYmV0
d2VlbiBzdWItc3lzdGVtcywgdGh1cyBrZWVwaW5nIHRoZSANCj4gaW50ZXJuYWwgc3lzdGVtcyBs
b29zZWx5LWNvdXBsZWQuIFdpdGggZW5jcnlwdGlvbiwgdGhlIG1vYmlsZSBjYXJyaWVyIA0KPiBs
b3NlcyB0aGUgY2FwYWJpbGl0eSB0byBpbmNsdWRlIGFueSBpbmZvcm1hdGlvbiBpbiB0aGUgY29u
dGVudCBpdHNlbGYgDQo+IGFzIGl0IGlzIGVuY3J5cHRlZCwgbWFraW5nIGl0IGltcG9zc2libGUg
Zm9yIHRoZSBtb2JpbGUgY2FycmllciB0byBwYXNzIG9uIHRoZSBpbmZvcm1hdGlvbiBpbiBhbnkg
SFRUUCBoZWFkZXJzLg0KDQpBIHJlZmVyZW5jZSB3b3VsZCBiZSBoZWxwZnVsLCB0aGFua3MhDQoN
Cj4NCj4gNC4gICAgICAgSFRUUCBSZWRpcmVjdGlvbiDigJMgQXMgb2YgdG9kYXkgdGhlIE1vYmls
ZSBDYXJyaWVyIHdvdWxkIG5lZWQgdG8NCj4gYmxvY2sgb3IgcmVkaXJlY3QgYSBjdXN0b21lciBm
b3IgbXVsdGlwbGUgcmVhc29ucw0KDQo+DQo+IGEuICAgICAgIFRoZSBjdXN0b21lciBtYXkgbm90
IGJlIGFsbG93ZWQgdG8gdmlldyB0aGUgY29udGVudCBkdWUgdG8gcGFyZW50YWwNCj4gY29udHJv
bHMuDQoNCk9LLCBzbyB5b3UgaGF2ZSB0aGUgaW5mb3JtYXRpb24gdG8gYmxvY2ssIGJ1dCBubyBh
YmlsaXR5IHRvIHJlZGlyZWN0IGluIHRoaXMgY2FzZS4NCg0KW0JhZHJpXSBZZXMsIHRoYXQgdGhl
IGV4YWN0bHkgdGhlIHNjZW5hcmlvLiBUaGUgbW9iaWxlIHByb3ZpZGVyIGhhcyB0aGUgZGVzdGlu
YXRpb24gZG9tYWluL0lQIEFkZHJlc3MgZnJvbSB0aGUgQ3VzdG9tZXIgcmVxdWVzdCBhbmQgaWRl
bnRpZmllcyB0aGlzIGRvbWFpbiBhcyBhIGJsb2NrZWQgZG9tYWluIHVuZGVyIFBhcmVudGFsIGNv
bnRyb2wuDQoNCj4NCj4gYi4gICAgICBUaGUgY3VzdG9tZXIgIG1heSBub3QgYmUgYWxsb3dlZCB0
byB2aWV3IHRoZSBjb250ZW50IGFzIHRoZXkgaGF2ZQ0KPiBub3QgcHVyY2hhc2VkIHRoZSBjb250
ZW50Lg0KDQpXb3VsZG4ndCB0aGlzIGJlIGEgc2VydmVyLXNpZGUgZGVjaXNpb24gYW55d2F5PyAg
SW4gdGhhdCBjYXNlLCBUTFMgbWFrZXMgbm8gZGlmZmVyZW5jZS4NCg0KPg0KPiBjLiAgICAgICBU
aGUgY3VzdG9tZXIgbWF5IG5vdCBiZSBhbGxvd2VkIGFzIHRoZXkgaGF2ZSByZWFjaGVkIHRoZWly
IHVzYWdlDQo+IGxpbWl0IGFuZCBuZWVkIHRvIGJ1eSBhZGRpdGlvbmFsIGRhdGEuDQo+DQo+IEN1
cnJlbnRseSwgdGhlIE1vYmlsZSBjYXJyaWVyIHJlZGlyZWN0cyB0aGUgY3VzdG9tZXIgdXNpbmcg
SFRUUCANCj4gcmVkaXJlY3QgdG8gYSBwYWdlIHdoaWNoIGVkdWNhdGVzIHRoZSBjdXN0b21lciBv
biB0aGUgcmVhc29uIGZvciB0aGUgDQo+IGJsb2NrYWdlIGFuZCBwcm92aWRlIHN0ZXBzIHRvIHBy
b2NlZWQuIE9uY2UgdGhlIGNvbnRlbnQgaXMgZW5jcnlwdGVkLCANCj4gdGhlIE1vYmlsZSBjYXJy
aWVyIGxvc2VzIHRoZSBvcHRpb24gdG8gcmVkaXJlY3QgdGhlIHRyYWZmaWMgYW5kIHRoZSANCj4g
b25seSBvcHRpb24gYmVpbmcgdG8gYmxvY2sgdGhlIGN1c3RvbWVyLCBmb3IgYWxsIHNjZW5hcmlv
cy4gVGhpcyB3b3VsZCANCj4gbm90IG9ubHkgY2F1c2UgYmFkIGN1c3RvbWVyIGV4cGVyaWVuY2Us
IGJ1dCB3b3VsZCBhbHNvIG5lZWQgYW5vdGhlciANCj4gd2F5IHRvIHBhc3Mgb24gdGhlIGFkZGl0
aW9uYWwgaW5mb3JtYXRpb24gdG8gdGhlIGN1c3RvbWVyIOKAkyB0ZXh0IA0KPiBtZXNzYWdlLiBJ
ZiBmb3IgYW55IHJlYXNvbiwgdGhlIGN1c3RvbWVyIGlzIG5vdCBhYmxlIHRvIGZpbmQgdGhlIA0K
PiBpbmZvcm1hdGlvbiwgaGUvc2hlIHdvdWxkIGhhdmUgdG8gY2FsbCBjdXN0b21lciBjYXJlIHRv
IGZpbmQgb3V0IHRoZSANCj4gcmVhc29uLiBUaGlzIGlzIG5vdCBvbmx5IGFuIGluY29udmVuaWVu
Y2UgdG8gdGhlIGN1c3RvbWVyLCBidXQgYWxzbyBhbiBvdmVyaGVhZCB0byB0aGUgc2VydmljZSBw
cm92aWRlci4NCj4NCj4NCg0KVGhpcyBpcyByZWFzb25hYmxlIHRvIGFkZC4gIERvIHlvdSBoYXZl
IGEgcmVmZXJlbmNlIHdlIGNhbiBjaXRlIG9uIHRoZSBwcmFjdGljZXM/DQpbQmFkcmldIFRoZXNl
IGFyZSBwcmFjdGljZXMgdGhhdCBoYXZlIGJlZW4gZm9sbG93ZWQgaW4gdGhlIGluZHVzdHJ5LCBi
dXQgZG9u4oCZdCBrbm93IGlmIHRoZXkgaGF2ZSBiZWVuIHB1Ymxpc2hlZCBhbnl3aGVyZS4gSSB3
aWxsIGNoZWNrIGFuZCBnZXQgYmFjayB0byB5b3UuDQoNClRoYW5rIHlvdSENCkthdGhsZWVuDQo+
DQo+ICAgICAgICAgICAgICAgICBQbGVhc2UgZmVlbCBmcmVlIHRvIGdldCBiYWNrIHRvIG1lIGlm
IHlvdSBoYXZlIGFueSANCj4gcXVlc3Rpb25zLg0KPg0KPg0KPg0KPiBUaGFua3MsDQo+DQo+IEJh
ZHJpDQo+DQo+IFJlbGlhbmNlIEppbw0KPg0KPg0KPiAiQ29uZmlkZW50aWFsaXR5IFdhcm5pbmc6
IFRoaXMgbWVzc2FnZSBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSANCj4gaW50ZW5kZWQgb25seSBm
b3IgdGhlIHVzZSBvZiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50KHMpLCBhcmUgDQo+IGNvbmZpZGVu
dGlhbCBhbmQgbWF5IGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCAN
Cj4gcmVjaXBpZW50LCB5b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSByZXZpZXcsIHJl
LXRyYW5zbWlzc2lvbiwgDQo+IGNvbnZlcnNpb24gdG8gaGFyZCBjb3B5LCBjb3B5aW5nLCBjaXJj
dWxhdGlvbiBvciBvdGhlciB1c2Ugb2YgdGhpcyANCj4gbWVzc2FnZSBhbmQgYW55IGF0dGFjaG1l
bnRzIGlzIHN0cmljdGx5IHByb2hpYml0ZWQuIElmIHlvdSBhcmUgbm90IHRoZSANCj4gaW50ZW5k
ZWQgcmVjaXBpZW50LCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkgYnkgcmV0
dXJuIA0KPiBlbWFpbCBhbmQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgYW55IGF0dGFjaG1lbnRz
IGZyb20geW91ciBzeXN0ZW0uDQo+DQo+IFZpcnVzIFdhcm5pbmc6IEFsdGhvdWdoIHRoZSBjb21w
YW55IGhhcyB0YWtlbiByZWFzb25hYmxlIHByZWNhdXRpb25zIA0KPiB0byBlbnN1cmUgbm8gdmly
dXNlcyBhcmUgcHJlc2VudCBpbiB0aGlzIGVtYWlsLiBUaGUgY29tcGFueSBjYW5ub3QgDQo+IGFj
Y2VwdCByZXNwb25zaWJpbGl0eSBmb3IgYW55IGxvc3Mgb3IgZGFtYWdlIGFyaXNpbmcgZnJvbSB0
aGUgdXNlIG9mIA0KPiB0aGlzIGVtYWlsIG9yIGF0dGFjaG1lbnQuIg0KDQoNCg0KLS0gDQoNCkJl
c3QgcmVnYXJkcywNCkthdGhsZWVuDQoNCiJDb25maWRlbnRpYWxpdHkgV2FybmluZzogVGhpcyBt
ZXNzYWdlIGFuZCBhbnkgYXR0YWNobWVudHMgYXJlIGludGVuZGVkIG9ubHkgZm9yIHRoZSB1c2Ug
b2YgdGhlIGludGVuZGVkIHJlY2lwaWVudChzKS4gDQphcmUgY29uZmlkZW50aWFsIGFuZCBtYXkg
YmUgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudC4geW91
IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCBhbnkgDQpyZXZpZXcuIHJlLXRyYW5zbWlzc2lvbi4g
Y29udmVyc2lvbiB0byBoYXJkIGNvcHkuIGNvcHlpbmcuIGNpcmN1bGF0aW9uIG9yIG90aGVyIHVz
ZSBvZiB0aGlzIG1lc3NhZ2UgYW5kIGFueSBhdHRhY2htZW50cyBpcyANCnN0cmljdGx5IHByb2hp
Yml0ZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQuIHBsZWFzZSBub3Rp
ZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBieSByZXR1cm4gZW1haWwuIA0KYW5kIGRlbGV0ZSB0
aGlzIG1lc3NhZ2UgYW5kIGFueSBhdHRhY2htZW50cyBmcm9tIHlvdXIgc3lzdGVtLg0KDQpWaXJ1
cyBXYXJuaW5nOiBBbHRob3VnaCB0aGUgY29tcGFueSBoYXMgdGFrZW4gcmVhc29uYWJsZSBwcmVj
YXV0aW9ucyB0byBlbnN1cmUgbm8gdmlydXNlcyBhcmUgcHJlc2VudCBpbiB0aGlzIGVtYWlsLiAN
ClRoZSBjb21wYW55IGNhbm5vdCBhY2NlcHQgcmVzcG9uc2liaWxpdHkgZm9yIGFueSBsb3NzIG9y
IGRhbWFnZSBhcmlzaW5nIGZyb20gdGhlIHVzZSBvZiB0aGlzIGVtYWlsIG9yIGF0dGFjaG1lbnQu
Igo=


From nobody Thu Mar  9 08:19:56 2017
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 1CD5812959C for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 08:19:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.668
X-Spam-Level: 
X-Spam-Status: No, score=-1.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 70QDcPYhUdQo for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 08:19:53 -0800 (PST)
Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72D1A1293D6 for <ietf@ietf.org>; Thu,  9 Mar 2017 08:19:53 -0800 (PST)
Received: by mail-yb0-x22d.google.com with SMTP id g132so3773247ybg.3 for <ietf@ietf.org>; Thu, 09 Mar 2017 08:19:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=5J4H+PAoVvmrAXgTUYPXDyw2fDACJw3EnFefjuJYWw0=; b=AmFymR2njA5fmyXqUsrBAKPS4vzaVzZVKPnZnjKRnX36yJAPQ/Dk2Vc1NXnnqgYXUD SA3DHJq0QStyHIvDBUusyO5YLQ00fSxDLSoYN3faO4YP2aam0RZ8SFQsWY9JsJ7HCiw4 1vsc/A42AbneUNdFlAQePQ4lDV+o/uNvrLYjLcJouUGd6LOkTCnQH4NdXE/Ijn8xyCsG sXAyxK3ewHTrRnWoUb/n8koiR+Rh4oflKIq4KrIUkwg2dqWIOBb6X7TgrfbGF73I3ypw wxNl1CSp2qkMbJDuBCQ5rH6FMcCswVhk4ApFQoI2+q4WVIj2KhJbXRiHadGpK2ghSJeQ bFkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=5J4H+PAoVvmrAXgTUYPXDyw2fDACJw3EnFefjuJYWw0=; b=g7OGnbmPJjkSgSe9/g9NBy2EgSM8J3ZqmrpJ6LQ6PTKuKDtLpoE3ekZCfgUT18QqqQ YuXYQDxmOdCjYA3FCBVSaDI+FzGwp9c05j/K6eLhGQLdfRIB0wr9n45AQAPhhkyBTw19 Zzjy6H3tMuv1C1BOMYeghiQOqyUXrN1W1VpunBxos09u5JeR/E1p+psOtUIsmfGT+c89 DuWqJE4sKqZUUXG3y8OAcg3bity75WjIlkSkakN4HCKCvKGY7UT3K2h6Gydt4lJlTAeR fXlTfmxDaAJ0l1OXfGhgpwhggnF8v307jGM4Sfdq+2Mo2KAjpRG/uzrisYHJGBWS64il Y1hg==
X-Gm-Message-State: AMke39lCGbdsqDtwfvlxgYcIU2iBibdQZfHHHTTcWP29n1jBaWvTfXWlE1Ng3ohbT/iCiSCQHzL9lT33MMi3Hw==
X-Received: by 10.37.36.86 with SMTP id k83mr4649938ybk.130.1489076392556; Thu, 09 Mar 2017 08:19:52 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Thu, 9 Mar 2017 08:19:51 -0800 (PST)
In-Reply-To: <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 9 Mar 2017 11:19:51 -0500
X-Google-Sender-Auth: 0Z8LO9G77YSw_4WsZ5QZtVIq46g
Message-ID: <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com>
Subject: Re: The CIA mentions us
To: David Morris <dwm@xpasc.com>
Content-Type: multipart/alternative; boundary=001a113d46ec6bffff054a4e9d9d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XxEA-07koos27qB8nHUfnbwkvqU>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 16:19:55 -0000

--001a113d46ec6bffff054a4e9d9d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=E2=80=8BOK just so people know. I am working on this with a well known co-=
author
and we have a totally serious purpose behind the humorous aspects.

One point is that this is material people developing apps should be reading
so as to develop counter-counter measures.

The bigger point is that these documents and the weaponized attacks should
have been protected by end-to-end encryption throughout their lifecycle,
including on the Web server. We are currently at a conference on building
international norms for cyber and would like to establish 'lock up your
weapons' as a norm.

Besides being a norm that benefits the community, it is a norm that would
benefit every one of the 117 national cyber commands that currently exist.






=E2=80=8B

On Tue, Mar 7, 2017 at 1:35 PM, David Morris <dwm@xpasc.com> wrote:

>
>
> On Tue, 7 Mar 2017, Fernando Gont wrote:
>
> > On 03/07/2017 01:23 PM, joel jaeggli wrote:
> > > On 3/7/17 8:08 AM, Stephane Bortzmeyer wrote:
> > >> On Tue, Mar 07, 2017 at 11:02:54AM -0500,
> > >>  Phillip Hallam-Baker <phill@hallambaker.com> wrote
> > >>  a message of 54 lines which said:
> > >>
> > >>> This is all really good advice. I think it should be published as a=
n
> > >>> RFC.
> > >> I suspect we may run into IPR problems. The CIA author did not read
> > >> the Note Well.
> > >>
> > > https://en.wikipedia.org/wiki/Copyright_status_of_work_by_
> the_U.S._government
> >
> > Well... one would still need to assess whether such work is official or
> > not. :-)  At times, intelligence agency's work is not official --
> > actually, officially, such work didn't happen. :-)
>
> Yeah, leaked classified materials don't need a copyright for protection.
> One can go to jail with out ever getting a chance to discuss copyright
> status.
>

--001a113d46ec6bffff054a4e9d9d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">=E2=
=80=8BOK just so people know. I am working on this with a well known co-aut=
hor and we have a totally serious purpose behind the humorous aspects.</div=
><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div clas=
s=3D"gmail_default" style=3D"font-size:small">One point is that this is mat=
erial people developing apps should be reading so as to develop counter-cou=
nter measures.</div><div class=3D"gmail_default" style=3D"font-size:small">=
<br></div><div class=3D"gmail_default" style=3D"font-size:small">The bigger=
 point is that these documents and the weaponized attacks should have been =
protected by end-to-end encryption throughout their lifecycle, including on=
 the Web server. We are currently at a conference on building international=
 norms for cyber and would like to establish &#39;lock up your weapons&#39;=
 as a norm.</div><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_default" style=3D"font-size:small">Besides being=
 a norm that benefits the community, it is a norm that would benefit every =
one of the 117 national cyber commands that currently exist.</div><div clas=
s=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"f=
ont-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:s=
mall"><br></div><div class=3D"gmail_default" style=3D"font-size:small"><br>=
</div><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8B</div=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Ma=
r 7, 2017 at 1:35 PM, David Morris <span dir=3D"ltr">&lt;<a href=3D"mailto:=
dwm@xpasc.com" target=3D"_blank">dwm@xpasc.com</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><span class=3D""><br>
<br>
On Tue, 7 Mar 2017, Fernando Gont wrote:<br>
<br>
&gt; On 03/07/2017 01:23 PM, joel jaeggli wrote:<br>
&gt; &gt; On 3/7/17 8:08 AM, Stephane Bortzmeyer wrote:<br>
&gt; &gt;&gt; On Tue, Mar 07, 2017 at 11:02:54AM -0500,<br>
&gt; &gt;&gt;=C2=A0 Phillip Hallam-Baker &lt;<a href=3D"mailto:phill@hallam=
baker.com">phill@hallambaker.com</a>&gt; wrote<br>
&gt; &gt;&gt;=C2=A0 a message of 54 lines which said:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; This is all really good advice. I think it should be publ=
ished as an<br>
&gt; &gt;&gt;&gt; RFC.<br>
&gt; &gt;&gt; I suspect we may run into IPR problems. The CIA author did no=
t read<br>
&gt; &gt;&gt; the Note Well.<br>
&gt; &gt;&gt;<br>
&gt; &gt; <a href=3D"https://en.wikipedia.org/wiki/Copyright_status_of_work=
_by_the_U.S._government" rel=3D"noreferrer" target=3D"_blank">https://en.wi=
kipedia.org/wiki/<wbr>Copyright_status_of_work_by_<wbr>the_U.S._government<=
/a><br>
&gt;<br>
&gt; Well... one would still need to assess whether such work is official o=
r<br>
&gt; not. :-)=C2=A0 At times, intelligence agency&#39;s work is not officia=
l --<br>
&gt; actually, officially, such work didn&#39;t happen. :-)<br>
<br>
</span>Yeah, leaked classified materials don&#39;t need a copyright for pro=
tection.<br>
One can go to jail with out ever getting a chance to discuss copyright<br>
status.<br>
</blockquote></div><br></div>

--001a113d46ec6bffff054a4e9d9d--


From nobody Thu Mar  9 08:28:52 2017
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 4E4821296AC for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 08:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.668
X-Spam-Level: 
X-Spam-Status: No, score=-1.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zLsav-LVCCeP for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 08:28:50 -0800 (PST)
Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F2891296A8 for <ietf@ietf.org>; Thu,  9 Mar 2017 08:28:50 -0800 (PST)
Received: by mail-yb0-x231.google.com with SMTP id m133so3831538ybb.1 for <ietf@ietf.org>; Thu, 09 Mar 2017 08:28:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AFGUQ6/IUhiQF+71ZGyzyGt0Gli6nrsrs7q23ceGrIU=; b=PIoMiA7BcOxz/sqAAv1S7PGKbJNYZnVWl5/MrkYQN90TNjGQfNhEMf6SUd7OazTJzz Q5PWWuXNB46z+veD4//w7p4mspDY0UU2Y8a6P2CXmjATjNZ/utuReTd13rM796J2rZ89 azm9OoCRTuN3Q7LhdTxkK436fsl69SVH6cw6TjRhGUNT82n7rdIXCRyRdAFJYwOT/4eE 8boZc/nq6bDxW58s3lN+mPEIkXiT35UZpa788qBq4IGR65qz6lsfkVyJ6DwQ5B7jpukD aYSg+30EGtNix995ujOk8gknzPl3XnFjRWJIkorUVp76gMqQxUYo/lTmlcRFCiifdObq DV2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=AFGUQ6/IUhiQF+71ZGyzyGt0Gli6nrsrs7q23ceGrIU=; b=eNoPxrRa9G9wg4m52J7G7WaC6Hs3Du7MJSDHFtAOYoyN7yyFzPk7cy0b/0Oc9vVq1M 1s6bOLvbCRnBjG+bakQ5DM5kUQnMhzZIls5DLZR8TxCSN3SIihX7Gq16HoYYYmEhiUYS dZXA6SR0dEmXDv0t1eoP64R/JGIfTeQTx9BADKPwDMLiupF2x0XJ1O21xxN8W8EBH+9Y n68DuL/7U/2zBzE8bkG+vZvEEqeyCwqPl5nYWnfpaf9NwMTmt6mD0y8RyU8hVX+zRfoF s8r38j3TKKzoj9xbbIm1vci5OOFdmE7V5aht9i3bbbEa8qzDIWO/cpMLgDa9BCW+D3uu eKFw==
X-Gm-Message-State: AMke39mI+mExSkz0YDL/2yiOzKmmZIKszTW39uzvfo8V/3XpBU5FJq6BypIWeQAjyDls1OeygSWLheohT8iwmQ==
X-Received: by 10.37.96.137 with SMTP id u131mr4328295ybb.1.1489076929210; Thu, 09 Mar 2017 08:28:49 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Thu, 9 Mar 2017 08:28:48 -0800 (PST)
In-Reply-To: <f9546015-ea7d-b23e-f68c-cb6243c6d181@si6networks.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <f9546015-ea7d-b23e-f68c-cb6243c6d181@si6networks.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 9 Mar 2017 11:28:48 -0500
X-Google-Sender-Auth: MJXXivwy0zzVH3RJ_kVyvKPQQ-g
Message-ID: <CAMm+LwgHa64a6brkXadA2Okty7=394ZbMyQgKy32=mjXvgA4zQ@mail.gmail.com>
Subject: Re: The CIA mentions us
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a1143cd7468b156054a4ebd33
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_vdV7T5vEiJ_otiJB8yKAD92pys>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 16:28:51 -0000

--001a1143cd7468b156054a4ebd33
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 7, 2017 at 1:41 PM, Fernando Gont <fgont@si6networks.com> wrote=
:

> On 03/07/2017 03:35 PM, David Morris wrote:
> >>>>
> >>> https://en.wikipedia.org/wiki/Copyright_status_of_work_by_
> the_U.S._government
> >>
> >> Well... one would still need to assess whether such work is official o=
r
> >> not. :-)  At times, intelligence agency's work is not official --
> >> actually, officially, such work didn't happen. :-)
> >
> > Yeah, leaked classified materials don't need a copyright for protection=
.
> > One can go to jail with out ever getting a chance to discuss copyright
> > status.
>
> One should consider oneself lucky in that case ;-)
>
> Cheers,


=E2=80=8BUS law is rather interesting. Unlike UK law where it is not necess=
ary to
'sign the official secrets act' to be covered by it, US civil law is rather
less severe.=E2=80=8B Military law is a different matter, active duty milit=
ary can
be ordered to be careful with classified materials. Civil law requires
intention to transmit to an unauthorized party or carelessness amounting to
constructive intent.

The documents do include material that purports to be classified as secret.
As a result many people are unable to read it because they have security
clearances and can't comment.

There certainly isn't a need to be concerned about copyright status as the
documents purport to be government property which would put them in the
public domain if true.

--001a1143cd7468b156054a4ebd33
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Ma=
r 7, 2017 at 1:41 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D"mailto=
:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On 03/07/2017=
 03:35 PM, David Morris wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; <a href=3D"https://en.wikipedia.org/wiki/Copyright_status_of_w=
ork_by_the_U.S._government" rel=3D"noreferrer" target=3D"_blank">https://en=
.wikipedia.org/wiki/<wbr>Copyright_status_of_work_by_<wbr>the_U.S._governme=
nt</a><br>
&gt;&gt;<br>
&gt;&gt; Well... one would still need to assess whether such work is offici=
al or<br>
&gt;&gt; not. :-)=C2=A0 At times, intelligence agency&#39;s work is not off=
icial --<br>
&gt;&gt; actually, officially, such work didn&#39;t happen. :-)<br>
&gt;<br>
&gt; Yeah, leaked classified materials don&#39;t need a copyright for prote=
ction.<br>
&gt; One can go to jail with out ever getting a chance to discuss copyright=
<br>
&gt; status.<br>
<br>
</span>One should consider oneself lucky in that case ;-)<br>
<br>
Cheers,</blockquote><div><br></div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">=E2=80=8BUS law is rather interesting. Unlike UK law where i=
t is not necessary to &#39;sign the official secrets act&#39; to be covered=
 by it, US civil law is rather less severe.=E2=80=8B Military law is a diff=
erent matter, active duty military can be ordered to be careful with classi=
fied materials. Civil law requires intention to transmit to an unauthorized=
 party or carelessness amounting to constructive intent.</div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">The documents do include material that purp=
orts to be classified as secret. As a result many people are unable to read=
 it because they have security clearances and can&#39;t comment.</div><div =
class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"g=
mail_default" style=3D"font-size:small">There certainly isn&#39;t a need to=
 be concerned about copyright status as the documents purport to be governm=
ent property which would put them in the public domain if true.</div></div>=
</div></div>

--001a1143cd7468b156054a4ebd33--


From nobody Thu Mar  9 10:22:58 2017
Return-Path: <weihaw@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 DD94D1296E1 for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 10:22:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thM5bWRsR7Rl for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 10:22:55 -0800 (PST)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E8431296EC for <ietf@ietf.org>; Thu,  9 Mar 2017 10:22:55 -0800 (PST)
Received: by mail-oi0-x230.google.com with SMTP id m124so40492923oig.1 for <ietf@ietf.org>; Thu, 09 Mar 2017 10:22:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Rv0NKGsjrZt+Lp7X5SLRTAfi3qGr70uY3U1CkKSOZPM=; b=Aek5cQRdkge1xGQqizREk/WUcvIwYJ/fxCs616X2xSogZ8TJc/jf/YR2QC9nRKbX/+ RWErXYS9h0mZN2S/Bm6C6oGKsn6rW/QFY5yTa0EQy1LcEuLbG9GO+NwNZMHSFDbpPwCK GcHHMYDJjeAKCZmQiJkpyW3fiptoguiLEkxFyXXuq1l4BN6FgTiVNfJ1tkVKhoTRRZ21 1+vdHNRT6z0IBI8OvNFKwi98bcw8QesobE7f1sEgyYtixYutEAfiMKlroigGjtUZTg8g v6CQJ7L9Hgikw2NSTHc0dcqcGQJmvSk8i6T3SVc6falS1+clU/9PxsfaTujwyl6TdU6G EBOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Rv0NKGsjrZt+Lp7X5SLRTAfi3qGr70uY3U1CkKSOZPM=; b=tGxT3ZvrPLxRjAFfX+dyvAroCiK+pXism/iIJWdrLNt9mrcKIrvPUIEdNWNyXHqb9u sz0teSi80q8Kt6hifSRldspU01WG7Z5dD/NCuKxpf07jJh8dhDpCkQSF0nZModzfjPyy Ymy6eYnv+UbSlb7ltqMXhvm5FVAf25SAK7uH730GwKJfSmwrrg1Frce3WZEFZlHSGZJB 4YuFPMAK6Z+huig6C+XsIm9AJiQDgWzIHX4nqU1uTyxo2bN8lAqAAc7BtU76r5M2oriL HiVv/sJwLW3lgom5WjU7eYYB5/QF8fEQvqhlCuNIuC9GuFS0dQtV/XW1j2CjSVGawlup io9w==
X-Gm-Message-State: AMke39ks+hz5FdNmziGOsV84xL+XU37zzg4H1O+nvUt1N0TKS5qJ6l7PS1NeUTPDpjlBRo3S8swy17stTESecVKW
X-Received: by 10.202.90.84 with SMTP id o81mr7074567oib.106.1489083773985; Thu, 09 Mar 2017 10:22:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.41.226 with HTTP; Thu, 9 Mar 2017 10:22:26 -0800 (PST)
In-Reply-To: <00c401d298b8$616fffa0$4001a8c0@gateway.2wire.net>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org> <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie> <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie> <CAAFsWK2RMGp0jqesx3cTbN=S7p0WuhH+0AbeJuuiZPF6WCbQOQ@mail.gmail.com> <BCEFAA3C-B711-4269-81C8-4DA0E1AA7AD0@dukhovni.org> <CAAFsWK3yJ9r+6abTXZQsNsey+VcRpdtVv=Hku_54_LZ9y1T2xQ@mail.gmail.com> <B8A5967B-9C19-4167-8A20-B82DFD46A924@dukhovni.org> <00c401d298b8$616fffa0$4001a8c0@gateway.2wire.net>
From: Wei Chuang <weihaw@google.com>
Date: Thu, 9 Mar 2017 10:22:26 -0800
Message-ID: <CAAFsWK1Q=d-9E++J0Z7UyEn3mshKkbYZ9yuGX974XvU8rO0VQw@mail.gmail.com>
Subject: Re: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: IETF general list <ietf@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a113d52726e708f054a5055ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Cor3cMSxOIHfcyVU_zTtyiBPiPE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 18:22:57 -0000

--001a113d52726e708f054a5055ca
Content-Type: multipart/alternative; boundary=001a113d5272641498054a50554e

--001a113d5272641498054a50554e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

There seems to be a consensus here and internally to the changes that
Viktor proposes.  We can put that in the next draft update.

-Wei

On Thu, Mar 9, 2017 at 1:34 AM, tom p. <daedulus@btconnect.com> wrote:

> ----- Original Message -----
> From: "Viktor Dukhovni" <ietf-dane@dukhovni.org>
> To: <spasm@ietf.org>; "IETF general list" <ietf@ietf.org>
> Sent: Thursday, March 09, 2017 3:19 AM
> > On Mar 8, 2017, at 8:17 PM, Wei Chuang <weihaw@google.com> wrote:
> >
> > Okay.  I think the direction then is to have SmtpUTF8Name respect
> rfc822Name name constraints and vice versa.
>
> Well, no, the simplest proposal on the table is for SmtpUTF8Name to
> be *prohibited* when rfc822Name constraints are present and SmtpUTF8Name
> constraints are not.  When both present, they can operate independently.
>
> <tp>
>
> Getting security right can be tricky as the legion of failed attempts
> that make it to RFC testify but what you are proposing here seems so
> simple, so obviously the right thing to do that I am puzzled, bewildered
> even, that anyone can disagree with you.
>
> Tom Petch
>
> The verifier logic is then:
>
> 1. If neither rfc822Name constraints nor SmtpUTF8Name constraints
>            are present in any CA certificate in the chain, any mixture
> of
>            rfc822Name and SmtpUTF8Name SAN elements is valid.
>
> 2. If some certificate in the chain contains *only* rfc822Name
>    constraints, then these apply to rfc822Name SAN elements, but
>    all SmtpUTF8Names are prohibited.
>
> 3. When both types of constraints are present in all CA certificates
>            that have either type, then constraints for each SAN type are
>    exclusively based on just the corresponding constraint type.
>
> 4. If some certificate in the chain contains only SmtpUTF8Name
>      constraints then those are unavoidably at risk of bypass via
>            rfc822Name SAN elements when processed by legacy verifiers.
>    Therefore, this should be avoided, and the CA needs to
>      publish rfc822Name constraints that prevent bypass.  Such
>    constraints *need not* be equivalent (not always possible)
>    to the desired SmtpUTF8Name constraints.  Rather, it suffices
>    to not permit rfc822Name elements that would be prohibited
>    if they were simply cut/pasted (with no A-label to U-label
>            conversions) as SmtpUTF8Name elements.  It is not necessary
>    for these to permit everything that SmtpUTF8Name permits.
>
> Thus for example, if SmtpUtf8Name only permits addresses in the non
> NR-LDH
> domain "духовный.org <http://xn--b1adqpd3ao5c.org>" (or a specific set of
> addresses in such a domain),
> then the corresponding rfc822Name constraint could just permit "." (or
> the
> reserved "invalid" TLD if that's preferable) which is not a usable email
> domain.  This ensures that only the permitted SmtpUTF8Name SANs are used
> and no rfc822Name SANs are used.
>
> If, instead the Smtp8Name constraints are excluded non-ASCII address
> forms,
> then since these have no literal rfc822Name equivalents, the rfc822Name
> constraints can be omitted with the same effect.
>
> Only when the intention is to permit NR-LDH domains with either ASCII or
> UTF-8 localparts (or an all-ASCII full address) do the rfc822Name and
> SmtpUTF8Name constraints need to be fully equivalent.  This is of course
> trivial to do.  Just cut/paste the same string into both types of
> constraint.
>
> --
> Viktor.
>
>

--001a113d5272641498054a50554e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr">There seems to be a consensus here and internally to the changes that Viktor proposes.  We can put that in the next draft update.<div><br></div><div>-Wei</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 9, 2017 at 1:34 AM, tom p. <span dir="ltr">&lt;<a href="mailto:daedulus@btconnect.com" target="_blank">daedulus@btconnect.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">----- Original Message -----<br>
From: &quot;Viktor Dukhovni&quot; &lt;<a href="mailto:ietf-dane@dukhovni.org">ietf-dane@dukhovni.org</a>&gt;<br>
To: &lt;<a href="mailto:spasm@ietf.org">spasm@ietf.org</a>&gt;; &quot;IETF general list&quot; &lt;<a href="mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br>
Sent: Thursday, March 09, 2017 3:19 AM<br>
&gt; On Mar 8, 2017, at 8:17 PM, Wei Chuang &lt;<a href="mailto:weihaw@google.com">weihaw@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Okay.  I think the direction then is to have SmtpUTF8Name respect<br>
rfc822Name name constraints and vice versa.<br>
<br>
Well, no, the simplest proposal on the table is for SmtpUTF8Name to<br>
be *prohibited* when rfc822Name constraints are present and SmtpUTF8Name<br>
constraints are not.  When both present, they can operate independently.<br>
<br>
</span>&lt;tp&gt;<br>
<br>
Getting security right can be tricky as the legion of failed attempts<br>
that make it to RFC testify but what you are proposing here seems so<br>
simple, so obviously the right thing to do that I am puzzled, bewildered<br>
even, that anyone can disagree with you.<br>
<br>
Tom Petch<br>
<div class="CSS_CV_TRIMMABLE_"><div class="CSS_CV_ELIDED_TEXT_"><br>
The verifier logic is then:<br>
<br>
1. If neither rfc822Name constraints nor SmtpUTF8Name constraints<br>
           are present in any CA certificate in the chain, any mixture<br>
of<br>
           rfc822Name and SmtpUTF8Name SAN elements is valid.<br>
<br>
2. If some certificate in the chain contains *only* rfc822Name<br>
   constraints, then these apply to rfc822Name SAN elements, but<br>
   all SmtpUTF8Names are prohibited.<br>
<br>
3. When both types of constraints are present in all CA certificates<br>
           that have either type, then constraints for each SAN type are<br>
   exclusively based on just the corresponding constraint type.<br>
<br>
4. If some certificate in the chain contains only SmtpUTF8Name<br>
     constraints then those are unavoidably at risk of bypass via<br>
           rfc822Name SAN elements when processed by legacy verifiers.<br>
   Therefore, this should be avoided, and the CA needs to<br>
     publish rfc822Name constraints that prevent bypass.  Such<br>
   constraints *need not* be equivalent (not always possible)<br>
   to the desired SmtpUTF8Name constraints.  Rather, it suffices<br>
   to not permit rfc822Name elements that would be prohibited<br>
   if they were simply cut/pasted (with no A-label to U-label<br>
           conversions) as SmtpUTF8Name elements.  It is not necessary<br>
   for these to permit everything that SmtpUTF8Name permits.<br>
<br>
Thus for example, if SmtpUtf8Name only permits addresses in the non<br>
NR-LDH<br>
domain &quot;<a href="http://xn--b1adqpd3ao5c.org" rel="noreferrer" target="_blank">духовный.org</a>&quot; (or a specific set of addresses in such a domain),<br>
then the corresponding rfc822Name constraint could just permit &quot;.&quot; (or<br>
the<br>
reserved &quot;invalid&quot; TLD if that&#39;s preferable) which is not a usable email<br>
domain.  This ensures that only the permitted SmtpUTF8Name SANs are used<br>
and no rfc822Name SANs are used.<br>
<br>
If, instead the Smtp8Name constraints are excluded non-ASCII address<br>
forms,<br>
then since these have no literal rfc822Name equivalents, the rfc822Name<br>
constraints can be omitted with the same effect.<br>
<br>
Only when the intention is to permit NR-LDH domains with either ASCII or<br>
UTF-8 localparts (or an all-ASCII full address) do the rfc822Name and<br>
SmtpUTF8Name constraints need to be fully equivalent.  This is of course<br>
trivial to do.  Just cut/paste the same string into both types of<br>
constraint.<br>
<br>
--<br>
Viktor.<br>
<br>
</div></div></blockquote></div><br></div>

--001a113d5272641498054a50554e--

--001a113d52726e708f054a5055ca
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCDgCahJdiBBpla8Cq8q6/xM
QG6o48//7C49OQyg1dtPUDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAzMDkxODIyNTRaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAykEF/IDjBwIR1zQQOGVv/Oj3XaI0qQTc7MwesLV9
3i1icWwBCCu5gKoxFNUgsKz1Vq+bhDF4qAjTUv28COqmLw5/1IRd3DYmd9RMrQPD2yMq4CjG32IE
CgklOoEcrI+/8hbdPVXIrT2ZH059cxA7uXa/zuyj7/oUOCU7JC/6ixTqjL8n5hZjc/lzCtZf3bTX
u2qCZ8TFPa/zUvgihaBHvRWeOeAshk8Cff3LU0qUQKiL0j92M04mzT+ecWxsOcfXFeOunNLJQkfr
PLvGl2MnRA7SdT3WmeNks3HEKSoMPg7Xj9FKE9ZCVTB6LdoXcTEisfXlN9MDQoAjw8uluFTRlA==
--001a113d52726e708f054a5055ca--


From nobody Thu Mar  9 12:36:17 2017
Return-Path: <jari.arkko@piuha.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 9C9E21293EE for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 12:36:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iQhX6gkGt8ab for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 12:36:13 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 52DA7120725 for <ietf@ietf.org>; Thu,  9 Mar 2017 12:36:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5CDE52CFD8; Thu,  9 Mar 2017 22:36:11 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n0X8y41ldLUP; Thu,  9 Mar 2017 22:36:10 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 954232CC5E; Thu,  9 Mar 2017 22:36:10 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: The CIA mentions us
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_FBCC34E0-7192-4B40-8D7A-206573E9F758"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com>
Date: Thu, 9 Mar 2017 22:36:07 +0200
Message-Id: <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6EZmyCMXpR-K1ZwsmcvawKEfU8U>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 20:36:15 -0000

--Apple-Mail=_FBCC34E0-7192-4B40-8D7A-206573E9F758
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Up-leveling a bit from the discussion of best practices for surveillance
organisations and virus builders (who apparently are partly the same
crowd). We can make some more general observations, I think,
maybe a bit more relevant for the rest of us.

I don=92t think the reported findings are particularly surprising. But
they seem to support what I think we knew already:

1. Security isn=92t a single feature, but needs to be thought in terms
of the whole. Comms security and devices and ...

2. There is no such thing as privileged access to the good guys. It
will leak / break / be shared.

3. Secretly held vulnerabilities make us all less safe.

4. The security of our communications and applications matters a
lot. Lives are at stake, not just your browsing history.

Jari


--Apple-Mail=_FBCC34E0-7192-4B40-8D7A-206573E9F758
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYwby4AAoJEM80gCTQU46qi2MQAMUQxu9z5UrQhyt7oJkuwuDI
GMQMwYhsrL69s0Zi92IqctN7/UL81CULnP/8KJiRVk+xPDzWuDtjycLPXQl+M01I
U/JGASaTnTq3SnTIZOt/c8jRIl9vrtvycc/Esk8zDGla+Th2r0ZbpTbZ6pqwkCVm
KK2IvQQk8EtaHyBqJIAMZ1tbQsQl7NLZMuKqUDvJtD+AKwDPif0e4kJONjM0bYIu
F58ehZdEoSFo4jSvoa27jwMzgCD7kPUbgeKv/wO2hEuQndhQrTOeYkedojso4ltj
yEi+OqudaH6ucSoC8Zb+ts+lE1ViiOCbq+veRxqr0SHEZaLU0oMmn3+T9IWkeQsx
SBkz/f31KrDWoV/7JexkltWS4mDC77i6DyaEuchZURYeTYdMN0vTGOVrFFoJf4ZG
DtDLixhOnPZP9/uskJMV/Sl8SeeJP66W7R0yLJtBZ5s1VQlu/QyTMicZlgWFeEbO
F/h2Xn3WXO5ZvAAlsifk797Ddz0lzjYFPfGIC+uiNqf4mHuhWuWoDpA2LG0C2dUy
Qj8tUrVyM2kihyyeVTZeSovVmuXt4cOjC+iDcbQ+BaAYr/sJ2w/yaZ6i3OYfvMRn
b9SO3tcKi1q1lBwTJs3fs5fDPrutlRWr/b9oVlX0aAHbvaipmIzqifga+tz1OMjT
oMw8HDPRJf7/56N+124C
=KagG
-----END PGP SIGNATURE-----

--Apple-Mail=_FBCC34E0-7192-4B40-8D7A-206573E9F758--


From nobody Thu Mar  9 13:02:48 2017
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 CAE20129534 for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 13:02:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0auhaazBzBn8 for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 13:02:45 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89E6012940C for <ietf@ietf.org>; Thu,  9 Mar 2017 13:02:45 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cm5Cq-000FCO-Fy; Thu, 09 Mar 2017 16:02:40 -0500
Date: Thu, 09 Mar 2017 16:02:34 -0500
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>, Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: The CIA mentions us
Message-ID: <00A55B3A256BD71DFB1866B4@PSB>
In-Reply-To: <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.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
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9aWUUgeA-2Mp4yprYE9kxLC2Zxg>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 21:02:47 -0000

Jari,

Let me suggest one addition to your list (with which I otherwise
agree):

5. No matter how strong the in-transit encryption or other
measures, they doesn't mean much if the relevant endpoint hosts,
or intermediate hosts that have the traffic in the clear, can be
compromised.  We all know that, but we seem to sometimes need
reminding.   In particular, while it is definitely not an
argument against link encryption, we need to be cautious that we
are not protecting things in a way that inadvertently shifts the
points of vunerability from one place to another (especially
another that is either more easily compromised or that
constitutes larger and more concentrated single point of
failure) and then assume that it makes things more secure
overall.

best,
    john


--On Thursday, March 9, 2017 22:36 +0200 Jari Arkko
<jari.arkko@piuha.net> wrote:

> Up-leveling a bit from the discussion of best practices for
> surveillance organisations and virus builders (who apparently
> are partly the same crowd). We can make some more general
> observations, I think, maybe a bit more relevant for the rest
> of us.
> 
> I don't think the reported findings are particularly
> surprising. But they seem to support what I think we knew
> already:
> 
> 1. Security isn't a single feature, but needs to be thought
> in terms of the whole. Comms security and devices and ...
> 
> 2. There is no such thing as privileged access to the good
> guys. It will leak / break / be shared.
> 
> 3. Secretly held vulnerabilities make us all less safe.
> 
> 4. The security of our communications and applications matters
> a lot. Lives are at stake, not just your browsing history.
> 
> Jari
> 





From nobody Thu Mar  9 13:11:37 2017
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 AB67C1294A3 for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 13:11:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXwDLjR-QCkv for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 13:11:34 -0800 (PST)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E679B12943D for <ietf@ietf.org>; Thu,  9 Mar 2017 13:11:33 -0800 (PST)
Received: by mail-yw0-x22c.google.com with SMTP id v198so13571432ywc.2 for <ietf@ietf.org>; Thu, 09 Mar 2017 13:11:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=NneRMIpGvPLvdWvQU5cSonVdmYINWzsF5BoJ2UHxQOM=; b=D0HJYuZgBgkHfP/yy4tmDa44aveWLtmZ3MOG75Tbe8lOIB7Ht3hbnRh0yyAIpmPg/r VvsMSWsobNFd2FrgmZgvfRlNjWqp/ivOxdOEaJKERmrjKsGYTtSy4Jg+Uv+FiwLq4pgy DLEovyIJtH302nhyPx+G2g1mr5Radbpf6v+oR5t4NUSxglkmRqv9hW+eZhIMmAJNwrq5 5BfdimR61IOGVxuFl5Sv169UPziyvLgVi5TTIdpi/CqJL3A2nCFuFsUlIAcCCjY14u40 CKSKiObUw5IuFHzlTq/Yh5DPhGCJ/6r9jbVERh3kewXZKa3bmtvK4uiKOgarBLj5KFVL uVTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=NneRMIpGvPLvdWvQU5cSonVdmYINWzsF5BoJ2UHxQOM=; b=l9XmcoZHECzKzRQKCtP2xIrjL3oFr8opliT1776Mf51TBXlVgwJhmVvGmtC7EUzCrW v0p1rh73akl8f4NqnuaX66ZwZc9NflNL8iB0P7bRJVgfjewY2IRZlwTZRT1LEEG4+H6O ZY0MBymznFIl17M8XPxdZ5q1lOC3vMGA97VdRYL5O1N9EGzQDpOxc74cfe0qahnMq1fd WmcIb17x81Ets3vs0dxWV5DlEmURGDEpFwiGCkflQEVJ0XfN6oH/oWVlsp9nD2zCrHlD ISX0R66mgrDTkNDXIAOiYoz8wFReC53QIdqBpB76BB0KpNrYA6W5HxOKeWv2gjx1My4k cu1w==
X-Gm-Message-State: AMke39mk8M5mAVxCnAb6nrwxQw1rH0BwRqRQxAmV3Hy/MGpTZjeAQFjsBFFRph7n+K5mJrGQT1yZEIXQBup65Q==
X-Received: by 10.129.172.25 with SMTP id k25mr5303311ywh.165.1489093892999; Thu, 09 Mar 2017 13:11:32 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Thu, 9 Mar 2017 13:11:32 -0800 (PST)
In-Reply-To: <00A55B3A256BD71DFB1866B4@PSB>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <00A55B3A256BD71DFB1866B4@PSB>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 9 Mar 2017 16:11:32 -0500
X-Google-Sender-Auth: ApLtdDjJaJpMP-JjpouLGaOQT7s
Message-ID: <CAMm+Lwg1MzDOn9xQ_-3oKcZ1odFF552sPGJhu17KRTP0SNR2vw@mail.gmail.com>
Subject: Re: The CIA mentions us
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=94eb2c1badfc8791ee054a52b043
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QjCExhwWqaE-e9VNfl6RrAGOswo>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 21:11:35 -0000

--94eb2c1badfc8791ee054a52b043
Content-Type: text/plain; charset=UTF-8

There are two issues

1) Requirements, how should this data be secured?
2) Technology, how can the requirements be met?

I totally agree that transport layer encryption is not enough here. The
security requirement is end to end.

Proprietary products that meet that requirement do exist and the US
agencies that do this work have the financial and technical means to deploy
and use them and I have no problem with the idea of imposing a requirement
on that group that requires them to pay for the tools.

However, it is not just the US agencies doing this work. There are now 117
cyber commands and there is a real problem of 'loose cyber-weapons'. It is
to the interest of the US and to all the other cyber-commands that a norm
is established that cyber weapons are secured end to end throughout their
lifecyle and tools produced to enable that to be achieved.


Such tools do not currently exist. However some key patent expiries that
have occurred and will be complete in November this year make true end to
end data level encryption practical. I have proof of concept but short of
infringing code running in the lab which I will push out as soon as I can
together with the supporting specifications.






On Thu, Mar 9, 2017 at 4:02 PM, John C Klensin <john-ietf@jck.com> wrote:

> Jari,
>
> Let me suggest one addition to your list (with which I otherwise
> agree):
>
> 5. No matter how strong the in-transit encryption or other
> measures, they doesn't mean much if the relevant endpoint hosts,
> or intermediate hosts that have the traffic in the clear, can be
> compromised.  We all know that, but we seem to sometimes need
> reminding.   In particular, while it is definitely not an
> argument against link encryption, we need to be cautious that we
> are not protecting things in a way that inadvertently shifts the
> points of vunerability from one place to another (especially
> another that is either more easily compromised or that
> constitutes larger and more concentrated single point of
> failure) and then assume that it makes things more secure
> overall.
>
> best,
>     john
>
>
> --On Thursday, March 9, 2017 22:36 +0200 Jari Arkko
> <jari.arkko@piuha.net> wrote:
>
> > Up-leveling a bit from the discussion of best practices for
> > surveillance organisations and virus builders (who apparently
> > are partly the same crowd). We can make some more general
> > observations, I think, maybe a bit more relevant for the rest
> > of us.
> >
> > I don't think the reported findings are particularly
> > surprising. But they seem to support what I think we knew
> > already:
> >
> > 1. Security isn't a single feature, but needs to be thought
> > in terms of the whole. Comms security and devices and ...
> >
> > 2. There is no such thing as privileged access to the good
> > guys. It will leak / break / be shared.
> >
> > 3. Secretly held vulnerabilities make us all less safe.
> >
> > 4. The security of our communications and applications matters
> > a lot. Lives are at stake, not just your browsing history.
> >
> > Jari
> >
>
>
>
>
>

--94eb2c1badfc8791ee054a52b043
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">The=
re are two issues</div><div class=3D"gmail_default" style=3D"font-size:smal=
l"><br></div><div class=3D"gmail_default" style=3D"font-size:small">1) Requ=
irements, how should this data be secured?</div><div class=3D"gmail_default=
" style=3D"font-size:small">2) Technology, how can the requirements be met?=
</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div=
 class=3D"gmail_default" style=3D"font-size:small">I totally agree that tra=
nsport layer encryption is not enough here. The security requirement is end=
 to end.=C2=A0</div><div class=3D"gmail_default" style=3D"font-size:small">=
<br></div><div class=3D"gmail_default" style=3D"font-size:small">Proprietar=
y products that meet that requirement do exist and the US agencies that do =
this work have the financial and technical means to deploy and use them and=
 I have no problem with the idea of imposing a requirement on that group th=
at requires them to pay for the tools.</div><div class=3D"gmail_default" st=
yle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fon=
t-size:small">However, it is not just the US agencies doing this work. Ther=
e are now 117 cyber commands and there is a real problem of &#39;loose cybe=
r-weapons&#39;. It is to the interest of the US and to all the other cyber-=
commands that a norm is established that cyber weapons are secured end to e=
nd throughout their lifecyle and tools produced to enable that to be achiev=
ed.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><=
div class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">Such tools do not currently ex=
ist. However some key patent expiries that have occurred and will be comple=
te in November this year make true end to end data level encryption practic=
al. I have proof of concept but short of infringing code running in the lab=
 which I will push out as soon as I can together with the supporting specif=
ications.</div><div class=3D"gmail_default" style=3D"font-size:small"><br><=
/div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div =
class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"g=
mail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-size:small"><br></div></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Thu, Mar 9, 2017 at 4:02 PM, John C Klensin=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blan=
k">john-ietf@jck.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">Jari,<br>
<br>
Let me suggest one addition to your list (with which I otherwise<br>
agree):<br>
<br>
5. No matter how strong the in-transit encryption or other<br>
measures, they doesn&#39;t mean much if the relevant endpoint hosts,<br>
or intermediate hosts that have the traffic in the clear, can be<br>
compromised.=C2=A0 We all know that, but we seem to sometimes need<br>
reminding.=C2=A0 =C2=A0In particular, while it is definitely not an<br>
argument against link encryption, we need to be cautious that we<br>
are not protecting things in a way that inadvertently shifts the<br>
points of vunerability from one place to another (especially<br>
another that is either more easily compromised or that<br>
constitutes larger and more concentrated single point of<br>
failure) and then assume that it makes things more secure<br>
overall.<br>
<br>
best,<br>
=C2=A0 =C2=A0 john<br>
<br>
<br>
--On Thursday, March 9, 2017 22:36 +0200 Jari Arkko<br>
<div class=3D"HOEnZb"><div class=3D"h5">&lt;<a href=3D"mailto:jari.arkko@pi=
uha.net">jari.arkko@piuha.net</a>&gt; wrote:<br>
<br>
&gt; Up-leveling a bit from the discussion of best practices for<br>
&gt; surveillance organisations and virus builders (who apparently<br>
&gt; are partly the same crowd). We can make some more general<br>
&gt; observations, I think, maybe a bit more relevant for the rest<br>
&gt; of us.<br>
&gt;<br>
&gt; I don&#39;t think the reported findings are particularly<br>
&gt; surprising. But they seem to support what I think we knew<br>
&gt; already:<br>
&gt;<br>
&gt; 1. Security isn&#39;t a single feature, but needs to be thought<br>
&gt; in terms of the whole. Comms security and devices and ...<br>
&gt;<br>
&gt; 2. There is no such thing as privileged access to the good<br>
&gt; guys. It will leak / break / be shared.<br>
&gt;<br>
&gt; 3. Secretly held vulnerabilities make us all less safe.<br>
&gt;<br>
&gt; 4. The security of our communications and applications matters<br>
&gt; a lot. Lives are at stake, not just your browsing history.<br>
&gt;<br>
&gt; Jari<br>
&gt;<br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div>

--94eb2c1badfc8791ee054a52b043--


From nobody Thu Mar  9 13:18:46 2017
Return-Path: <vinayakh@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 A1F4912954D for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 13:18:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ILfXJQeRUVkR for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 13:18:43 -0800 (PST)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14E57129546 for <ietf@ietf.org>; Thu,  9 Mar 2017 13:18:43 -0800 (PST)
Received: by mail-qk0-x22f.google.com with SMTP id v125so137561255qkh.2 for <ietf@ietf.org>; Thu, 09 Mar 2017 13:18:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eqfSdKZqu2dmYagECFRwAwDCbP3CHHN9HD5m/yyg13g=; b=VGNzEKVeHf6gyeJEgfU4iesccQGqn5nUhYWNTw9cfCciJprZ+gr/bn/J3+BbmaaVrf xyBC77ONnbCLCK698q9wLb8IUzrTzTOUJ0pnXvy085BFJS8mCeLLoRi23bY8P5nMOTUX IYF6npQ9wIfh+tJv0+FhmU4sv0h+yWL7FD23akE1Ow3bbUsYILtaJ0/47GwobKzu0Kz3 pGJI8LFDl0ODzTNGxJpOScKyLBaONB/xKz6wVM7qwYE2nLSsaqzQb9Qq1cNkDuQpGsr0 v3mPpTZUE/iVem7jc2b3JgqLwj44kf9Bv45yJ5hoz90U6NshmsOlcZpzZHuJOaNTOmc/ GIHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eqfSdKZqu2dmYagECFRwAwDCbP3CHHN9HD5m/yyg13g=; b=l+YxnlCRyFwNrve54HiUkN0OzMEOpUvMnIntKGMHUg+0DKix0i4BRiC/CEtQrjaFG5 D95A4pSvIQiXu/tW+uQOnTQiIIFb16qfVU42VYh/NSAc/JiDYCV6WCIlHwWLTniVKH0a Ln93cHeT/OVLj0i4siXFs5IvExLMTVjHY1AwhKQ4qw3WQ/JEfhLt/c0Bmpw42eehmQIp xm3IPZks4IXi8hMlT3qMSlf2pk4PqnXrAHYvOnRUyv7TC9XdlPl2UdQQoVNsjN57Mfct YYvcoCXMQqv27IHmgI9+RKNTYoLfwOxBBZMT5oCKcDkdWYwBwTH4dSiyurCYCZrC6tIq 73Og==
X-Gm-Message-State: AMke39kyFswnvp8TnVIhqzntjavXqbRlmR5HGw31+9UQhenQzEraHbyFtMpjhuDu3VC7ICoY5taLvep7eYSBMw==
X-Received: by 10.200.33.141 with SMTP id 13mr17490712qty.83.1489094322096; Thu, 09 Mar 2017 13:18:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.237.50.228 with HTTP; Thu, 9 Mar 2017 13:18:41 -0800 (PST)
In-Reply-To: <CAMm+Lwg1MzDOn9xQ_-3oKcZ1odFF552sPGJhu17KRTP0SNR2vw@mail.gmail.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <00A55B3A256BD71DFB1866B4@PSB> <CAMm+Lwg1MzDOn9xQ_-3oKcZ1odFF552sPGJhu17KRTP0SNR2vw@mail.gmail.com>
From: Vinayak Hegde <vinayakh@gmail.com>
Date: Fri, 10 Mar 2017 02:48:41 +0530
Message-ID: <CAKe6YvOaOZd4WAea6BgcuzpfHL2GhCfVYLnVHU_fFHtVrj9p+w@mail.gmail.com>
Subject: Re: The CIA mentions us
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WwhFmPhBOmPipXt5Cdxteb_9sZE>
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 21:18:44 -0000

On Fri, Mar 10, 2017 at 2:41 AM, Phillip Hallam-Baker
<phill@hallambaker.com> wrote:
> There are two issues
>
> 1) Requirements, how should this data be secured?
> 2) Technology, how can the requirements be met?
>
> I totally agree that transport layer encryption is not enough here. The
> security requirement is end to end.

Agreed. IETF typically looks mostly at data-in-transit[1]. However
taking a systems perspective we need to look at data-in-use[2] and
data-at-rest[3] as well. Other important aspects such as key-mgmt also
matter here but I am not sure how much of this falls under the purview
of the IETF.

-- Vinayak
1. https://en.wikipedia.org/wiki/Data_in_transit
2. https://en.wikipedia.org/wiki/Data_in_use
3. https://en.wikipedia.org/wiki/Data_at_rest


From nobody Thu Mar  9 14:03:29 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C358012956B; Thu,  9 Mar 2017 14:03:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Subject: Review of draft-leiba-rfc2119-update-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148909700476.5826.6498223456244647305@ietfa.amsl.com>
Date: Thu, 09 Mar 2017 14:03:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n1qcZtGVYR3WOj5LpjLmdV2pcBo>
Cc: draft-leiba-rfc2119-update.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 22:03:25 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-leiba-rfc2119-update-02
Reviewer: Robert Sparks
Review Date: 2017-03-09
IETF LC End Date: 2017-03-09
IESG Telechat date: 2017-03-16

Summary: Ready for publication as part of BCP 14




From nobody Thu Mar  9 14:07:51 2017
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 CB25D129420; Thu,  9 Mar 2017 14:07:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level: 
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRadHL6Z25nY; Thu,  9 Mar 2017 14:07:48 -0800 (PST)
Received: from [192.168.8.102] (37-219-125-199.nat.bb.dnainternet.fi [37.219.125.199]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id BCB80129588; Thu,  9 Mar 2017 14:07:45 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Conclusion of the facilitators experiment
Date: Fri, 10 Mar 2017 00:07:38 +0200
Message-Id: <99E8AECE-B27E-404E-8C23-69F0DA1FC8C3@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PmBUHr0ctJ0gmVcTke4jS4oDY4o>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 22:07:49 -0000

The ietf@ietf.org list is a high-volume discussion list with diverse =
topics ranging from document last calls to new proposals and to =
operational or process issues. Occasionally, discussions get a bit too =
heated or repetitive.

In March 2016, I asked S. Moonesamy, Christian Huitema, and Carlos =
Pignataro to act as facilitators, as an experiment. After IETF 97 we had =
a discussion of the results on the list. Based on feedback from the =
participants and the facilitators themselves, the general conclusion =
seemed to be that while the facilitation can have helped in some cases, =
the results are not sufficient to justify the fairly significant effort =
required to do this. In addition, the facilitators found the scope of =
their task difficult, squeezed between the ADs focused on directing the =
substantive discussions and the sergeant-at-arms focusing on ensuring =
appropriateness of the posts.

The experiment is concluded. The experiment is a success because we =
learned from it, even if facilitation itself is not worth the effort.

I want to thank SM, Christian, and Carlos for your willingness to try =
this and for the effort. Thank you!

Going forward, we continue to think about what to do here, and =
suggestions are always welcome. I won=92t be making any further changes, =
but I know Alissa has this as one of the many things on her mind as =
well.

Jari Arkko, IETF Chair


From nobody Thu Mar  9 14:08:21 2017
Return-Path: <barryleiba@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 C45351295B5; Thu,  9 Mar 2017 14:08:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QcnJPRMUmyZb; Thu,  9 Mar 2017 14:08:12 -0800 (PST)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62A171295BC; Thu,  9 Mar 2017 14:08:09 -0800 (PST)
Received: by mail-io0-x233.google.com with SMTP id g6so37685179ioj.1; Thu, 09 Mar 2017 14:08:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=nmRcyg2zFYWEiRilAMyMJXDqtCGym/+q3TemhZ81/hA=; b=Se27XXN6J5eaGOKgAtb801WHGwneYMIUGWrv6sc3D96EKU/OWSQ25jGWD12nX4dlJu bM63XN87aRI7q3pEm6wLc6oX8dKR485Gk2/aSKlZAxfy+22px5KQ7nR/25HTlT649Ng4 Vf0YiQzN1DUXkFZueMJJWrJku2JFzSqDf0999gP3rSNH3m63gmEp2NhUFrre9l6iXPHw WoG3IsRGjjL7yWm7UA3n0QL2345q6CW0WPJEyGvSKxHwx+gYl/bSh/cyUxIsfP184tyB nrXLuRtZ57HPkQ4v3rSeRFm9JlbXAUaNADDSzP8wjthFBVD0j/WGwfoZyM12ryHRvXvk 6V0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=nmRcyg2zFYWEiRilAMyMJXDqtCGym/+q3TemhZ81/hA=; b=hvjqy8QMyUdbXjAKBC5mGMYLtptpqoTsXB/RRLvA90mlAMGTngl1XbYweUAm/kI7hp VDt6TFgCDeBRapYoyCdluRE60HjggpWTM5gcWhDDmvojIEGBhkfSwua4sWTS/Z0XR1th +EFxjOconzpWklm/Ya8RDdHcA4zH4X0roVnSC2Ykpqdyn749+pvnRcoQvjubzNkErZtm 2M6efe1h5RAsfYqPs8ktKMuS53mYI6zyWrsBaGSjhuegvvGvlxdGFhMsW9rvvI1ZDi08 bPQyn0r9mDiuhlvRVYUFvgJdkGykaJs+3cGkEL+cv8TR0E+D2LzMNgn6Xw+C/1NUBgJY F/oQ==
X-Gm-Message-State: AMke39myA+OK96+02Fb5bOm9raeA9Ta3jDLktEXnqnhZ2jcY1q6A4S3IutbhvL7TisDm7oTl7jv+frJpsm7mFQ==
X-Received: by 10.107.182.9 with SMTP id g9mr12263330iof.233.1489097288662; Thu, 09 Mar 2017 14:08:08 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.107.187.7 with HTTP; Thu, 9 Mar 2017 14:08:07 -0800 (PST)
In-Reply-To: <148909700476.5826.6498223456244647305@ietfa.amsl.com>
References: <148909700476.5826.6498223456244647305@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 9 Mar 2017 17:08:07 -0500
X-Google-Sender-Auth: FyZhB6uP2vI130wfda0VyRVhCz8
Message-ID: <CALaySJ+Q05Ni02L9BKL9RjwgmvB3FwcUyGAe33qZaRQVtxvcfA@mail.gmail.com>
Subject: Re: Review of draft-leiba-rfc2119-update-02
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3eqTC6YIalJ9x9oYvfkMuFhYMT8>
Cc: General Area Review Team <gen-art@ietf.org>, draft-leiba-rfc2119-update.all@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Mar 2017 22:08:15 -0000

Thanks, Robert!

Barry

On Thu, Mar 9, 2017 at 5:03 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> Reviewer: Robert Sparks
> Review result: Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-leiba-rfc2119-update-02
> Reviewer: Robert Sparks
> Review Date: 2017-03-09
> IETF LC End Date: 2017-03-09
> IESG Telechat date: 2017-03-16
>
> Summary: Ready for publication as part of BCP 14
>
>
>



-- 
Barry
--
Barry Leiba  (barryleiba@computer.org)
http://internetmessagingtechnology.org/


From nobody Thu Mar  9 18:49:18 2017
Return-Path: <willi.uebelherr@riseup.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 D572812947E for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 18:49:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2B178-ZyGMRX for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 18:49:16 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 661731294DF for <ietf@ietf.org>; Thu,  9 Mar 2017 18:49:16 -0800 (PST)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 10F771A2101 for <ietf@ietf.org>; Fri, 10 Mar 2017 00:29:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1489105767; bh=NpzJTi87zB9CX2ir6scoFuXB8v4OOxczaGesVEwpdgc=; h=Subject:References:From:To:Date:In-Reply-To:From; b=Uz512KEQqamQ8HwhNGfn57Tm0y2BSrSid4G1gLrnu0ZHICq061v54dfC6XIaarLUg dEHSH++N5TN+RMj4kfWu84UVRn7R8ykopagbliL7qu8z0gmhu3Jr5ch78M/6UvUbxI vQZLvene9xrvApTJumxjg0jJWXYKupEXZRMoqk4Q=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id E56C01C25B1
Subject: Re: The CIA mentions us
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <00A55B3A256BD71DFB1866B4@PSB> <CAMm+Lwg1MzDOn9xQ_-3oKcZ1odFF552sPGJhu17KRTP0SNR2vw@mail.gmail.com>
From: willi uebelherr <willi.uebelherr@riseup.net>
To: IETF discussion <ietf@ietf.org>
Message-ID: <46f2b74c-a3cc-b0b5-f547-c3a423f82e22@riseup.net>
Date: Thu, 9 Mar 2017 21:28:53 -0300
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwg1MzDOn9xQ_-3oKcZ1odFF552sPGJhu17KRTP0SNR2vw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O65PFCJWAR6SEP2nZrQzrgdxiBE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 02:49:18 -0000

Dear Phillip,

i follow your highly interesting discussion. Many thanks.

We can say, not always we need the encryption of our data. But if we 
need it, we have to do it.

End to end encryption means person to person. In this example of IETF 
discussion list, this means, that i need the encryption key with you, 
Phillip. Independent of mailbox or maillist servers. The data in the 
mailbox and in the maillist and maillist archive are encrypted. And if 
we use a strong algorithm base, nobody others can read the data in the 
email. Only Phillip and Willi.

The encryption from you to the receiver list makes no sense. And if we 
published any text for many people, encryption makes no sense too.

Patent law. You speak about. For me, every patent right is a criminal 
task. Therefore, it don't exist for me. The knowledge is always world 
heritage. Therefore, we can use every algorithm, what we want.

many greetings, willi


On 09/03/2017 18:11, Phillip Hallam-Baker wrote:
> There are two issues
>
> 1) Requirements, how should this data be secured?
> 2) Technology, how can the requirements be met?
>
> I totally agree that transport layer encryption is not enough here. The
> security requirement is end to end.
>
> Proprietary products that meet that requirement do exist and the US
> agencies that do this work have the financial and technical means to deploy
> and use them and I have no problem with the idea of imposing a requirement
> on that group that requires them to pay for the tools.
>
> However, it is not just the US agencies doing this work. There are now 117
> cyber commands and there is a real problem of 'loose cyber-weapons'. It is
> to the interest of the US and to all the other cyber-commands that a norm
> is established that cyber weapons are secured end to end throughout their
> lifecyle and tools produced to enable that to be achieved.
>
>
> Such tools do not currently exist. However some key patent expiries that
> have occurred and will be complete in November this year make true end to
> end data level encryption practical. I have proof of concept but short of
> infringing code running in the lab which I will push out as soon as I can
> together with the supporting specifications.
>
>
>
>
>
>
> On Thu, Mar 9, 2017 at 4:02 PM, John C Klensin <john-ietf@jck.com> wrote:
>
>> Jari,
>>
>> Let me suggest one addition to your list (with which I otherwise
>> agree):
>>
>> 5. No matter how strong the in-transit encryption or other
>> measures, they doesn't mean much if the relevant endpoint hosts,
>> or intermediate hosts that have the traffic in the clear, can be
>> compromised.  We all know that, but we seem to sometimes need
>> reminding.   In particular, while it is definitely not an
>> argument against link encryption, we need to be cautious that we
>> are not protecting things in a way that inadvertently shifts the
>> points of vunerability from one place to another (especially
>> another that is either more easily compromised or that
>> constitutes larger and more concentrated single point of
>> failure) and then assume that it makes things more secure
>> overall.
>>
>> best,
>>     john
>>
>>
>> --On Thursday, March 9, 2017 22:36 +0200 Jari Arkko
>> <jari.arkko@piuha.net> wrote:
>>
>>> Up-leveling a bit from the discussion of best practices for
>>> surveillance organisations and virus builders (who apparently
>>> are partly the same crowd). We can make some more general
>>> observations, I think, maybe a bit more relevant for the rest
>>> of us.
>>>
>>> I don't think the reported findings are particularly
>>> surprising. But they seem to support what I think we knew
>>> already:
>>>
>>> 1. Security isn't a single feature, but needs to be thought
>>> in terms of the whole. Comms security and devices and ...
>>>
>>> 2. There is no such thing as privileged access to the good
>>> guys. It will leak / break / be shared.
>>>
>>> 3. Secretly held vulnerabilities make us all less safe.
>>>
>>> 4. The security of our communications and applications matters
>>> a lot. Lives are at stake, not just your browsing history.
>>>
>>> Jari
>>>
>>
>>
>>
>>
>>
>


From nobody Thu Mar  9 21:53:26 2017
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 0BD3A128BA2 for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 21:53:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.522
X-Spam-Level: 
X-Spam-Status: No, score=-1.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.08, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g3xvLGMYBacx for <ietf@ietfa.amsl.com>; Thu,  9 Mar 2017 21:53:22 -0800 (PST)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EEC6124281 for <ietf@ietf.org>; Thu,  9 Mar 2017 21:53:22 -0800 (PST)
Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2A5mewV092371 for <ietf@ietf.org>; Fri, 10 Mar 2017 00:53:19 -0500
Received: from e16.ny.us.ibm.com (e16.ny.us.ibm.com [129.33.205.206]) by mx0a-001b2d01.pphosted.com with ESMTP id 2937t4nt9p-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 10 Mar 2017 00:53:19 -0500
Received: from localhost by e16.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, 10 Mar 2017 00:53:17 -0500
Received: from b03cxnp08026.gho.boulder.ibm.com (9.17.130.18) by e16.ny.us.ibm.com (146.89.104.203) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 10 Mar 2017 00:53:15 -0500
Received: from b03ledav001.gho.boulder.ibm.com (b03ledav001.gho.boulder.ibm.com [9.17.130.232]) by b03cxnp08026.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v2A5rE4N5898508 for <ietf@ietf.org>; Thu, 9 Mar 2017 22:53:14 -0700
Received: from b03ledav001.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C0EE96E044 for <ietf@ietf.org>; Thu,  9 Mar 2017 22:53:14 -0700 (MST)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav001.gho.boulder.ibm.com (Postfix) with ESMTPS id A7AC06E035 for <ietf@ietf.org>; Thu,  9 Mar 2017 22:53:14 -0700 (MST)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v2A5rCYC027340 for <ietf@ietf.org>; Fri, 10 Mar 2017 00:53:12 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v2A5rCpM027323 for ietf@ietf.org; Fri, 10 Mar 2017 00:53:12 -0500
From: narten@us.ibm.com
Date: Fri, 10 Mar 2017 00:53:12 -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-TM-AS-GCONF: 00
x-cbid: 17031005-0024-0000-0000-000002054BE7
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006755; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000206; SDB=6.00832511; UDB=6.00408567; IPR=6.00610099;  BA=6.00005202; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014585; XFM=3.00000013; UTC=2017-03-10 05:53:16
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17031005-0025-0000-0000-000042688BC3
Message-Id: <201703100553.v2A5rCpM027323@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-10_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=75 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703100049
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QZEAwVwx0XkmF_vuovPbdYJ_8Cg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 05:53:24 -0000

Total of 117 messages in the last 7 days.
 
script run at: Fri Mar 10 00:53:07 EST 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  3.42% |    4 | 14.71% |   241526 | mohamed.boucadair@orange.com
  9.40% |   11 |  8.29% |   136162 | phill@hallambaker.com
  5.13% |    6 |  6.20% |   101838 | stephen.farrell@cs.tcd.ie
  0.85% |    1 |  7.62% |   125022 | david.black@dell.com
  4.27% |    5 |  3.88% |    63712 | shares@ndzh.com
  5.13% |    6 |  3.01% |    49407 | julian.reschke@gmx.de
  5.13% |    6 |  2.84% |    46585 | linuxwolf+ietf@outer-planes.net
  5.13% |    6 |  2.82% |    46321 | ietf-dane@dukhovni.org
  2.56% |    3 |  3.91% |    64249 | weihaw@google.com
  1.71% |    2 |  3.73% |    61246 | ted.ietf@gmail.com
  2.56% |    3 |  2.47% |    40592 | ekr@rtfm.com
  2.56% |    3 |  2.05% |    33688 | kaduk@mit.edu
  2.56% |    3 |  1.67% |    27346 | eckelcu@cisco.com
  1.71% |    2 |  2.31% |    37887 | sprevidi@cisco.com
  1.71% |    2 |  2.18% |    35800 | daedulus@btconnect.com
  2.56% |    3 |  1.27% |    20770 | stewart.bryant@gmail.com
  1.71% |    2 |  1.82% |    29929 | nalini.elkins@insidethestack.com
  1.71% |    2 |  1.72% |    28221 | suresh.krishnan@ericsson.com
  1.71% |    2 |  1.63% |    26819 | gregimirsky@gmail.com
  1.71% |    2 |  1.57% |    25734 | jari.arkko@piuha.net
  1.71% |    2 |  1.52% |    24940 | eng.khaled.omar@hotmail.com
  1.71% |    2 |  1.23% |    20154 | brian.e.carpenter@gmail.com
  1.71% |    2 |  1.08% |    17804 | barryleiba@computer.org
  1.71% |    2 |  0.97% |    15949 | john-ietf@jck.com
  1.71% |    2 |  0.96% |    15777 | alex@strugee.net
  1.71% |    2 |  0.86% |    14087 | bortzmeyer@nic.fr
  1.71% |    2 |  0.84% |    13858 | fgont@si6networks.com
  0.85% |    1 |  1.53% |    25151 | robert@raszuk.net
  0.85% |    1 |  1.05% |    17258 | badri.subramanyan@ril.com
  0.85% |    1 |  1.05% |    17248 | sankalp@cdac.in
  0.85% |    1 |  0.85% |    13984 | bob.hinden@gmail.com
  0.85% |    1 |  0.79% |    12965 | narten@us.ibm.com
  0.85% |    1 |  0.74% |    12071 | gunnar.hellstrom@omnitor.se
  0.85% |    1 |  0.68% |    11177 | willi.uebelherr@riseup.net
  0.85% |    1 |  0.63% |    10348 | jmh@joelhalpern.com
  0.85% |    1 |  0.62% |    10116 | housley@vigilsec.com
  0.85% |    1 |  0.57% |     9411 | roni.even@huawei.com
  0.85% |    1 |  0.53% |     8694 | srdonovan@usdonovans.com
  0.85% |    1 |  0.53% |     8639 | vinayakh@gmail.com
  0.85% |    1 |  0.51% |     8341 | gem@rellim.com
  0.85% |    1 |  0.49% |     8046 | touch@isi.edu
  0.85% |    1 |  0.49% |     8013 | mjethanandani@gmail.com
  0.85% |    1 |  0.49% |     7973 | joelja@bogus.com
  0.85% |    1 |  0.47% |     7758 | dwm@xpasc.com
  0.85% |    1 |  0.47% |     7699 | mellon@fugue.com
  0.85% |    1 |  0.47% |     7660 | mcr+ietf@sandelman.ca
  0.85% |    1 |  0.46% |     7491 | ajs@anvilwalrusden.com
  0.85% |    1 |  0.43% |     7129 | cabo@tzi.org
  0.85% |    1 |  0.42% |     6845 | chair@ietf.org
  0.85% |    1 |  0.41% |     6800 | rg+ietf@randy.pensive.org
  0.85% |    1 |  0.41% |     6707 | csp@csperkins.org
  0.85% |    1 |  0.40% |     6588 | lavanyahm@ece.iisc.ernet.in
  0.85% |    1 |  0.35% |     5698 | jrmitche@puck.nether.net
  0.85% |    1 |  0.34% |     5605 | ron.even.tlv@gmail.com
  0.85% |    1 |  0.33% |     5379 | elwynd@dial.pipex.com
  0.85% |    1 |  0.32% |     5331 | rjsparks@nostrum.com
--------+------+--------+----------+------------------------
100.00% |  117 |100.00% |  1641548 | Total


From nobody Thu Mar  9 23:36:00 2017
Return-Path: <prvs=2358de106=Badri.Subramanyan@ril.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF2CD12945D; Thu,  9 Mar 2017 23:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OrQulRtdyeVl; Thu,  9 Mar 2017 23:35:54 -0800 (PST)
Received: from gwsmtp010.ril.com (unknown [203.199.41.20]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F43D129456; Thu,  9 Mar 2017 23:35:49 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.36,139,1486405800"; d="scan'208";a="377191291"
From: <Badri.Subramanyan@ril.com>
To: <kathleen.moriarty.ietf@gmail.com>, <saag@ietf.org>, <ietf@ietf.org>
Subject: RE: Last call feedback: draft-mm-wg-effect-encrypt
Thread-Topic: Last call feedback: draft-mm-wg-effect-encrypt
Thread-Index: AQHSmEkdymufh+be8EG0ggEJbV3WwqGMUL1AgAD0g4A=
Date: Fri, 10 Mar 2017 07:35:18 +0000
Message-ID: <c056c07568974f37aa0366bbe8a93422@SIDC1EXMBX24.in.ril.com>
References: <CAHbuEH4+bd=0PJa1rWDQN6tbeRK5vXKdbcUwsj2=zf9V8ejeDg@mail.gmail.com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uTqGEWJLsNd9fs-tZEc9O9Zb69M>
Cc: acmorton@att.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 07:35:58 -0000

S2F0aGxlZW4vQWwsDQoNCglJIGhhdmUgaW5jbHVkZWQgYWRkaXRpb25hbCBpbmZvcm1hdGlvbiBp
bmxpbmUuIFBsZWFzZSBsZXQgbWUga25vdyBpZiB5b3UgbmVlZCBhZGRpdGlvbmFsIGluZm9ybWF0
aW9uLg0KDQpUaGFua3MsDQpCYWRyaQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv
bTogQmFkcmkgU3VicmFtYW55YW4gDQpTZW50OiBUaHVyc2RheSwgTWFyY2ggMDksIDIwMTcgODox
OSBBTQ0KVG86ICdLYXRobGVlbiBNb3JpYXJ0eScgPGthdGhsZWVuLm1vcmlhcnR5LmlldGZAZ21h
aWwuY29tPjsgJ3NhYWdAaWV0Zi5vcmcnIDxzYWFnQGlldGYub3JnPjsgJ2lldGZAaWV0Zi5vcmcn
IDxpZXRmQGlldGYub3JnPg0KQ2M6ICdBTEZSRUQgQyBNT1JUT04gKEFMKScgPGFjbW9ydG9uQGF0
dC5jb20+OyAnc3RlcGhlbi4gZmFycmVsbCcgPHN0ZXBoZW4uZmFycmVsbEBjcy50Y2QuaWU+DQpT
dWJqZWN0OiBSRTogTGFzdCBjYWxsIGZlZWRiYWNrOiBkcmFmdC1tbS13Zy1lZmZlY3QtZW5jcnlw
dA0KDQpLYXRobGVlbi9BbCwNCg0KCVRoYW5rcyBmb3IgdGhlIGNsYXJpZmljYXRpb24uIEkgaGF2
ZSBpbmNsdWRlZCBteSBjb21tZW50cyBpbmxpbmUuIA0KCUkgYW0gc3RpbGwgbG9va2luZyBmb3Ig
cmVmZXJlbmNlcyBhbmQgd2lsbCBzZW5kIGl0IG91dCBhcyBJIGZpbmQgdGhlbS4NCg0KVGhhbmtz
LA0KQmFkcmkNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEthdGhsZWVuIE1v
cmlhcnR5IFttYWlsdG86a2F0aGxlZW4ubW9yaWFydHkuaWV0ZkBnbWFpbC5jb21dDQpTZW50OiBX
ZWRuZXNkYXksIE1hcmNoIDA4LCAyMDE3IDI6MTggUE0NClRvOiBzYWFnQGlldGYub3JnDQpDYzog
QmFkcmkgU3VicmFtYW55YW4gPEJhZHJpLlN1YnJhbWFueWFuQHJpbC5jb20+OyBBTEZSRUQgQyBN
T1JUT04gKEFMKSA8YWNtb3J0b25AYXR0LmNvbT47IHN0ZXBoZW4uIGZhcnJlbGwgPHN0ZXBoZW4u
ZmFycmVsbEBjcy50Y2QuaWU+DQpTdWJqZWN0OiBMYXN0IGNhbGwgZmVlZGJhY2s6IGRyYWZ0LW1t
LXdnLWVmZmVjdC1lbmNyeXB0DQoNCkhlbGxvIEJhZHJpLA0KDQpUaGFuayB5b3UgdmVyeSBtdWNo
IGZvciB5b3VyIHJldmlldyBhbmQgZmVlZGJhY2sgb24gdGhlIGRyYWZ0LiAgVGhpcyBpcyB2ZXJ5
IGhlbHBmdWwgdG8gYWRkIGluIHlvdXIgcGVyc3BlY3RpdmUuICBJIGRvIGhhdmUgYSBmZXcgcXVl
c3Rpb25zIGluIGxpbmUgYW5kIGFtIGhvcGluZyB5b3UgaGF2ZSBzb21lIGdvb2QgcmVmZXJlbmNl
cyBmb3IgdXMgdG8gY2l0ZSBhcyB3ZWxsLiAgV2UgbmVlZCB0byBnZXQgYSBkcmFmdCByZXZpc2lv
biBvdXQgYnkgRnJpZGF5LCBzbyBob3BlZnVsbHkgd2UgY2FuIGl0ZXJhdGUgcXVpY2tseS4NCg0K
DQo+DQo+IE9uIEZlYiAyMywgMjAxNywgYXQgOTo1NCBBTSwgIkJhZHJpLlN1YnJhbWFueWFuQHJp
bC5jb20iDQo+IDxCYWRyaS5TdWJyYW1hbnlhbkByaWwuY29tPiB3cm90ZToNCj4NCj4gSGVsbG8s
DQo+DQo+DQo+DQo+ICAgICAgICAgICAgICAgICBJIHdvcmsgZm9yIGEgTW9iaWxlIFNlcnZpY2Ug
UHJvdmlkZXIgYW5kIHdhbnRlZCB0byANCj4gc3RhcnQgYnkgdGhhbmtpbmcgeW91IGZvciBwdXR0
aW5nIHRoaXMgZG9jdW1lbnQgdG9nZXRoZXIgKEVmZmVjdHMgb2YgDQo+IFBlcnZhc2l2ZSBFbmNy
eXB0aW9uKS4gRW5jcnlwdGlvbiBvZiBjb250ZW50IGhhcyBiZWVuIGltcGFjdGluZyB0aGUgDQo+
IHNlcnZpY2UgcHJvdmlkZXJzIGZvciBzb21ldGltZSwgYW5kIHRoaXMgZG9jdW1lbnQgb3V0bGlu
ZXMgaXQgdmVyeSANCj4gd2VsbC4gSSBoYWQgYSBmZXcgY29tbWVudHMvc3VnZ2VzdGlvbnMgb24g
dGhlIGRvY3VtZW50LiBUaGlzIGRvY3VtZW50cyANCj4gaXMgY29tcHJlaGVuc2l2ZSwgYnV0IHRo
ZXJlIGFyZSBhIGZldyBpbXBhY3RzIG1vcmUgc3BlY2lmaWMgdG8gTW9iaWxlIA0KPiBDYXJyaWVy
cyB3aGljaCBJIHRob3VnaHQgd2VyZSBub3QgaW5jbHVkZWQuIEkgd291bGQgZ3JlYXRseSBhcHBy
ZWNpYXRlIA0KPiBpdCwgaWYgeW91IGNvdWxkIGxvb2sgaW50byB0aGVzZSBhbmQgbW9kaWZ5IHRo
ZSBkb2N1bWVudCBhcyBzdWl0ZWQuDQo+DQo+DQo+DQo+IDEuICAgICAgIEFMRyDigJMgQXBwbGlj
YXRpb24gTGF5ZXIgR2F0ZXdheSwgaXMgYSBmZWF0dXJlIHVzZWQgYnkgRmlyZXdhbGxzLA0KPiBO
QVQgYm94ZXMgYW5kIExvYWQgQmFsYW5jZXJzIHRvIGlkZW50aWZ5IHN0cmVhbXMgd2hpY2ggYXJl
IHJlbGF0ZWQgYW5kIA0KPiB0cmVhdCB0aGVtIGFsaWtlLiBNYW55IG9mIHRoZSBwcm90b2NvbHMg
d29yayBpbiBjb25qdW5jdGlvbiB0byBkZWxpdmVyIGEgc2VydmljZS4NCj4gRWcuIFJUU1AvUlRD
UC9SVFAgcHJvdG9jb2xzIGFyZSB1c2VkIHRvIHByb3ZpZGUgdmlkZW8gc2VydmljZS4gUlRTUCAN
Cj4gdXNlcyBUQ1AgYW5kIG5lZ290aWF0ZXMgdGhlIFVEUCBwb3J0cyB1c2VkIGZvciBSVFAgYW5k
IFJUQ1AgDQo+IGNvbW11bmljYXRpb24uIFJUU1AgYW5kIFJUQ1AgZm9ybSB0aGUgY29udHJvbCBw
bGFuZSwgd2hlbiBSVFAgZm9ybXMgdGhlIGRhdGEgcGxhbmUuDQo+DQo+IGEuICAgICAgIFRoZSBB
TEcgZmVhdHVyZSBtYWtlcyB0aGUgRmlyZXdhbGwgYXBwbGljYXRpb24tYXdhcmUgYW5kIGFsbG93
IG9yDQo+IGJsb2NrIGEgdmlkZW8gY29udGVudCBhcyBkZXNpcmVkLg0KPg0KPiBiLiAgICAgIFRo
aXMgZmVhdHVyZSBpcyBhbHNvIHVzZWQgYXMgb2YgdG9kYXkgb24gdGhlIEZpcmV3YWxsIG9yIE5B
VCBib3guDQo+IFRoZSBzY2VuYXJpbyBoZXJlIGlzLCB0aGUgRlcvTkFUIGJveCBhY3RzIGFzIGEg
ZGVtYXJjYXRpb24gcG9pbnQgDQo+IGJldHdlZW4gdGhlIERNWiBhbmQgdW50cnVzdGVkIG5ldHdv
cmssIHdoaWNoIGFsbG93cyBvdXQgYm91bmQgdHJhZmZpYyANCj4gYW5kIGFueSBmbG93IGluaXRp
YXRlZCBmcm9tIHdpdGhpbiB0aGUgRE1aLiBXaGVuIHdlIGhhdmUgc2VydmljZSB3aXRoIA0KPiBt
dWx0aXBsZSBmbG93cywgc29tZSBvZiB0aGVzZSBjb3VsZCBiZSBpbml0aWF0ZWQgZnJvbSB3aXRo
aW4gdGhlIERNWiwgDQo+IHdoaWNoIHNob3VsZCBlbmFibGUgb3RoZXIgZmxvd3MgaW4gYm90aCBk
aXJlY3Rpb25zLiBFZy4gUlRTUCBSZXF1ZXN0IA0KPiBmcm9tIHdpdGhpbiB0aGUgRE1aIHdvdWxk
IG5lZWQgdG8gYWxsb3cgUlRQIHBhY2tldHMgZnJvbSB0aGUgdW50cnVzdGVkIA0KPiB6b25lIGlu
dG8gdGhlIERNWi4gVGhlIEZXL05BVCBib3ggY2FuIG9ubHkgYWxsb3cgdGhpcyBpZiB0aGV5IGFy
ZSANCj4gYXdhcmUgb2YgdGhlIGNvLXJlbGF0aW9uIGJldHdlZW4gdGhlIGRpZmZlcmVudCBmbG93
cyB1c2luZyBmZWF0dXJlIGxpa2UgQUxHLg0KPg0KPiBjLiAgICAgICBUaGUgQUxHIGZlYXR1cmUg
b24gYSBMQiBzaW1pbGFybHkgd291bGQgYWxsb3cgdGhlIGlkZW50aWZpY2F0aW9uIG9mDQo+IHRo
ZSBkaWZmZXJlbnQgY28tcmVsYXRlZCBmbG93cyBhbmQgdHJlYXQgdGhlbSBhbGlrZSDigJMgYWxs
b3csIGJsb2NrLCBMQiANCj4gdGhlbSB0byB0aGUgc2FtZSBzZXJ2ZXIgb3IgcmUtcm91dGUgdG8g
YW5vdGhlciBzZXQgb2Ygc2VydmVycy4NCj4NCj4gSWYgdGhlIHN0cmVhbXMgYXJlIGVuY3J5cHRl
ZCwgdGhlbiB0aGUgQUxHIGZlYXR1cmUgd291bGQgYmUgcmVuZGVyZWQgDQo+IHVzZWxlc3MuIFRo
aXMgd291bGQgbGltaXQgdGhlIGNhcGFiaWxpdHkgb2YgYW55IG5ldHdvcmsgZWxlbWVudCB0byAN
Cj4gbWFrZSBzbWFydCBwb2xpY2luZyBhbmQgcm91dGluZyBkZWNpc2lvbnMgYmFzZWQgb24gYXBw
bGljYXRpb24gbGF5ZXIgYXR0cmlidXRlcy4NCg0KRG8geW91IGtub3cgaWYgdGhlc2UgY2FuIHdv
cmsgd2l0aCBhIDItdHVwbGUgb3IgNS10dXBsZT8gIElzIHRoZXJlIGFuIGltcGFjdCBmcm9tIGVu
Y3J5cHRpb24gdmlhIFRMUyBmb3IgaW5zdGFuY2U/ICBJZiBzbywgd2hhdCBpcyB0aGF0IGltcGFj
dD8NCltCYWRyaV0gVGhlIHJ1bGVzIGluIG1vc3Qgb2YgdGhlIGNhc2VzIGlzIDUtdHVwbGUgdG8g
YWNjdXJhdGVseSBkZXBpY3QgYSBmbG93LiBZZXMsIHRoZXJlIGlzIGFuIGltcGFjdCBmcm9tIGVu
Y3J5cHRpb24gdmlhIFRMUyBhcyBtb3N0IG9mIHRoZSBpbXBsZW1lbnRhdGlvbnMgb2YgQUxHIGdl
dCBpbmZvcm1hdGlvbiByZWdhcmRpbmcgc3VwcG9ydGluZyBwcm90b2NvbHMgYnkgcGFyc2luZyBk
YXRhLiBXaXRoIFRMUyBlbmNyeXB0aW9uLCB0aGUgQUxHIGxvc2VzIHRoZSBhYmlsaXR5IHRvIHBh
cnNlLCBoZW5jZSBnZXQgaW5mb3JtYXRpb24gb24gdGhlIHN1cHBvcnRpbmcgcHJvdG9jb2xzLg0K
DQpXaGF0IGlzIHVzZWQgYnkgQUxHIHRvIGNvcnJlbGF0ZSBzdHJlYW1zPyAgVGhpcyB3b3VsZCBi
ZSBoZWxwZnVsIHRvIHVuZGVyc3RhbmQgaWYgdGhpcyBwYXJ0aWN1bGFyIG1ldGhvZCBmb3IgQUxH
cyBkb2VzIGJlY29tZSAndXNlbGVzcycNCmFuZCBhbHNvIHRvIGZpZ3VyZSBvdXQgaWYgb3RoZXIg
b3B0aW9ucyBtYXkgZXhpc3QgdG8gcGVyZm9ybSB0aGUgZnVuY3Rpb25zIG5lZWRlZC4NCltCYWRy
aV0gUkZDIDI2NjMsIFNlY3Rpb24gMi45IGdpdmVzIGluZm9ybWF0aW9uIGFib3V0IEFMRy4gVGhl
cmUgaXNu4oCZdCBvbmUgZGVmaW5lZCBtZXRob2QgdG8gaW1wbGVtZW50IGl0IGFuZCBzb21lIG9m
IHRoZSBtZXRob2RzIHVzZWQgYnkgdmVuZG9ycyBhcmUgaW5jbHVkZWQgYmVsb3cuDQoxLiAgUGFy
c2UgdGhlIGNvbnRlbnQgb2YgdGhlIHByaW1hcnkgc3RyZWFtIGFuZCBpZGVudGlmeSB0aGUgNS10
dXBsZSBvZiB0aGUgc3VwcG9ydGluZyBzdHJlYW1zIGFzIGl0IGlzIGJlaW5nIG5lZ290aWF0ZWQu
DQoyLiBJbnRlcmNlcHQgYW5kIG1vZGlmeSB0aGUgNS10dXBsZSBpbmZvcm1hdGlvbiBvZiB0aGUg
c3VwcG9ydGluZyBzdHJlYW0gYXMgdGhlIGl0IGlzIGJlaW5nIG5lZ290aWF0ZWQgb24gdGhlIHBy
aW1hcnkgc3RyZWFtLiBUaGlzIGlzIGEgbGl0dGxlIG1vcmUgaW50cnVzaXZlIGluIG5hdHVyZS4N
Cg0KRG8geW91IGhhdmUgcmVmZXJlbmNlcyBvbiB0aGlzIHRoYXQgYXJlIHN0YWJsZSAob25lcyB3
ZSBjYW4gY2l0ZSBpbiBhbiBSRkMpPw0KUkZDIDI2NjMsIFNlY3Rpb24gMi45DQoNCkkgaGF2ZSBh
bHNvIHNwZWxsZWQgb3V0IHNvbWUgb2YgdGhlIGFjcm9ueW1zIGJlbG93IFJUU1AgLSBSZWFsIFRp
bWUgU3RyZWFtaW5nIFByb3RvY29sIFJUQ1AgLSBSZWFsIFRpbWUgQ29udHJvbCBQcm90b2NvbCBS
VFAgLSBSZWFsIFRpbWUgUHJvdG9jb2wgQUxHIC0gQXBwbGljYXRpb24gTGV2ZWwgR2F0ZXdheS9B
cHBsaWNhdGlvbiBMYXllciBHYXRld2F5IExCIC0gTG9hZCBCYWxhbmNlcnMgRE1aIC0gRGVtaWxp
dGFyaXplZCBab25lIEZXIC0gRmlyZXdhbGwNCg0KPg0KPiAyLiAgICAgICBPdmVyLVRoZS1Ub3Ag
Q2FjaGluZyB3ZWIgY29udGVudCDigJMgWW91IGRpZCB0b3VjaCB1cG9uIHRoaXMgdG9waWMgaW4N
Cj4gc2VjdGlvbiAyLjEuNCwgYnV0IEkgdGhpbmsgdGhpcyBpcyBhIGJpZyBlbm91Z2ggdG9waWMg
dGhhdCBpdCB3YXJyYW50cyANCj4gaXRzIG93biBzdWJzZWN0aW9uLiBBcyB0aGUgSW50ZXJuZXQg
dHJhZmZpYyBpbmNyZWFzZXMgYWNyb3NzIHRoZSANCj4gd29ybGQsIE1vYmlsZSBDYXJyaWVycyBh
bmQgb3RoZXIgU2VydmljZSBQcm92aWRlcnMgYXJlIHVzaW5nIGNhY2hpbmcgDQo+IHNvbHV0aW9u
IHRvIGtlZXAgdXAgd2l0aCB0aGUgYmFuZHdpZHRoIG5lZWRzLiBDYWNoaW5nIGF0IGEgaGlnaCBs
ZXZlbCANCj4gd291bGQgYWxsb3cgZm9yIHdlYi92aWRlbyBhbmQgb3RoZXIgY2FjaGVzIHRvIGJl
IGxvY2F0ZWQgY2xvc2VyIHRvIHRoZSANCj4gY3VzdG9tZXJzLiBUaGUgZmlyc3QgdGltZSBhIGNv
bnRlbnQgaXMgcmVxdWVzdGVkLCBpdCBpcyBzdG9yZWQgaW4gdGhlIA0KPiBjYWNoZSBhbmQgZXZl
cnkgcmVxdWVzdCBnb2luZyBmb3J3YXJkIHdvdWxkIGJlIHNlcnZlZCBmcm9tIHRoZSBjYWNoZSAN
Cj4gdGh1cyBjdXR0aW5nIGRvd24gb24gdGhlIGJhY2toYXVsIHRvbm5hZ2UgYmV0d2VlbiB0aGUg
c291cmNlIG9mIHRoZSANCj4gY29udGVudCBhbmQgdGhlIGNhY2hlLiBUaGlzIG5vdCBvbmx5IGhl
bHBzIGluIGN1dHRpbmcgZG93biBvbiB0aGUgDQo+IGJhbmR3aWR0aCByZXF1aXJlbWVudHMsIGJ1
dCBhbHNvIGN1dHMgZG93biBvbiB0aGUgbGF0ZW5jeSB3aXRoIHF1aWNrZXIgdGltZSB0byBmaXJz
dCBieXRlIGFuZCBpbXByb3ZlcyBjdXN0b21lciBleHBlcmllbmNlLg0KPiBNb2JpbGUgQ2Fycmll
cnMgYXJlIGRlcGxveWluZyBjYWNoZXMgY2xvc2VyIHRvIHRoZSBjdXN0b21lcnMsIHRodXMgDQo+
IGN1dHRpbmcgZG93biBsYXRlbmN5IGRyYXN0aWNhbGx5LiBUaGVzZSBjYWNoZXMgcGxheSBhbiBl
dmVuIG1vcmUgDQo+IHNpZ25pZmljYW50IHJvbGUgd2hlbiB0aGUgbGF0ZW5jeSB0byB0aGUgZGVz
dGluYXRpb24gaXMgdmVyeSBoaWdoLCBlZzoNCj4gTW9iaWxlIGNhcnJpZXIgaXMgbG9jYXRlZCBp
biB0aGUgQXNpYSwgYnV0IHRoZSBzb3VyY2UgY29udGVudCBpcyBsb2NhdGVkIGluIFVTIG9yIHZp
Y2UgdmVyc2EuDQo+IFRoaXMgYWxzbyBoZWxwcyBtb2JpbGUgY2FycmllcnMgbG9jYXRlZCBvdXRz
aWRlIG9mIFVTLCB0byBjdXQgZG93biBvbiANCj4gdGhlaXIgSW50ZXJuZXQgdHJhZmZpYyB0byB0
aGUgVVMsIHdoaWNoIGRpcmVjdGx5IHRyYW5zbGF0ZXMgdG8gDQo+IHNhdmluZ3MuIFRoZSBjYWNo
ZSBzZXJ2ZXIgdXNlcyBpbmZvcm1hdGlvbiBpbiB0aGUgSFRUUCBoZWFkZXJzLCANCj4gcGF5bG9h
ZCBhbmQgb3RoZXIgYXR0cmlidXRlIHRvIG1ha2UgdGhlIGVmZmVjdGl2ZSBjYWNoaW5nIGRlY2lz
aW9ucy4NCj4gQXMgd2UgbW92ZSB0byBlbmNyeXB0aW9uIHRoZSBjYWNoZSBzZXJ2ZXIgZG9lcyBu
b3QgaGF2ZSB0aGlzIGluZm9ybWF0aW9uLCByZW5kZXJpbmcgdGhlbSB1c2VsZXNzLg0KDQpEbyB5
b3UgaGF2ZSByZWZlcmVuY2VzIG9uIHRoaXMgdHJlbmQ/ICBJdCB3b3VsZCBiZSBnb29kIGlmIHdl
IGNhbiBjaXRlIGEgcmVzb3VyY2UgYXMgd2UgYWxzbyBoZWFyZCBhdCB0aGUgTUFSTkVXIHdvcmtz
aG9wIHRoYXQgc29tZSBjb250ZW50IGNhcnJpZXJzIHByZWZlciBlbmQtdG8tZW5kIHNvbHV0aW9u
cy4gIEluIHRoYXQgY2FzZSwgY2FjaGluZyB3b3VsZG4ndCB3b3JrIGFueXdheS4gIElmIHRoZXJl
IGFyZSB0cmVuZHMgaW4gYm90aCBkaXJlY3Rpb25zLCBpdCB3b3VsZCBiZSBnb29kIHRvIGNpdGUg
cmVzb3VyY2VzLg0KQ2FjaGluZyBoZWxwcyBpbiByZWR1Y2luZyBMYXRlbmN5IGFuZCBJbnRlcm5l
dCBiYW5kd2lkdGggZm9yIHRoZSBhIE1vYmlsZSBDYXJyaWVyLCB3aGljaCBpcyB0aGUgYmFzaXMg
b2YgSFRUUCBDYWNoaW5nIGFzIGRlc2NyaWJlZCBpbiBSRkMgNzIzNC4gTGV0IG1lIGNoZWNrIHRv
IHNlZSBpZiB0aGVyZSBhcmUgYW55IHdoaXRlIHBhcGVycyB3aGljaCB0YWxrIGFib3V0IHRoaXMg
dHJlbmQgb2YgdXNpbmcgT1RUIENhY2hlcy4uLg0KUkZDIDcyMzQgZ2l2ZXMgaW5mb3JtYXRpb24g
b24gSFRUUCBDYWNoaW5nIGFuZCB0aGUgZXhwZWN0ZWQgYmVuZWZpdHMuIFRoZSBJbnRlcm5ldCBQ
cm90b2NvbCBKb3VybmFsIHB1Ymxpc2hlZCBieSBDaXNjbyBhbHNvIGNvbnRhaW5zIGluZm9ybWF0
aW9uIG9uIHdlYiBjYWNoaW5nIGFuZCBpdHMgYmVuZWZpdCAoaHR0cDovL3d3dy5jaXNjby5jb20v
Yy9kYW0vZW5fdXMvYWJvdXQvYWMxMjMvYWMxNDcvYXJjaGl2ZWRfaXNzdWVzL2lwal8yLTMvaXBq
XzItMy5wZGYpIC4gVGhlIGZvbGxvd2luZyBhcnRpY2xlIGFsc28gdGFsa3MgYWJvdXQgcHJveHkg
YW5kIGNhY2hpbmcgb24gdGhlIG1vYmlsZSBjYXJyaWVyIG5ldHdvcmtzIC0gaHR0cHM6Ly9uc2wu
Y3MudXNjLmVkdS9+anlyL3BhcGVycy85MDgxOC5wZGYNCj4NCj4gMy4gICAgICAgSFRUUCBoZWFk
ZXIgZW5yaWNobWVudCDigJMgSFRUUCBoZWFkZXIgZW5yaWNobWVudCBoYXMgYmVlbiBhDQo+IG1l
Y2hhbmlzbSBmb3IgdGhlIG1vYmlsZSBjYXJyaWVyIHRvIHByb3ZpZGUg4oCcYWxsb3dlZOKAnSAo
Tm9uLUNQTkkpIA0KPiBzdWJzY3JpYmVyIGluZm9ybWF0aW9uIHRvIHRoaXJkIHBhcnRpZXMgb3Ig
b3RoZXIgaW50ZXJuYWwgc3lzdGVtcy4gVGhlIA0KPiB0aGlyZCBwYXJ0aWVzIGNhbiBpbiB0dXJu
IHByb3ZpZGUgY3VzdG9taXplZCBzZXJ2aWNlLCBvciB1c2UgaXQgdG8gDQo+IGJpbGwgdGhlIGN1
c3RvbWVyIG9yIGFsbG93L2Jsb2NrIHNlbGVjdGl2ZSBjb250ZW504oCmLiBUaGlzIA0KPiBoZWFk
ZXItZW5yaWNobWVudCBtZXRob2QgaXMgYWxzbyB1c2VkIHdpdGhpbiB0aGUgTW9iaWxlIENhcnJp
ZXIgdG8gDQo+IHBhc3MgaW5mb3JtYXRpb24gaW50ZXJuYWxseSBiZXR3ZWVuIHN1Yi1zeXN0ZW1z
LCB0aHVzIGtlZXBpbmcgdGhlIA0KPiBpbnRlcm5hbCBzeXN0ZW1zIGxvb3NlbHktY291cGxlZC4g
V2l0aCBlbmNyeXB0aW9uLCB0aGUgbW9iaWxlIGNhcnJpZXIgDQo+IGxvc2VzIHRoZSBjYXBhYmls
aXR5IHRvIGluY2x1ZGUgYW55IGluZm9ybWF0aW9uIGluIHRoZSBjb250ZW50IGl0c2VsZiANCj4g
YXMgaXQgaXMgZW5jcnlwdGVkLCBtYWtpbmcgaXQgaW1wb3NzaWJsZSBmb3IgdGhlIG1vYmlsZSBj
YXJyaWVyIHRvIHBhc3Mgb24gdGhlIGluZm9ybWF0aW9uIGluIGFueSBIVFRQIGhlYWRlcnMuDQoN
CkEgcmVmZXJlbmNlIHdvdWxkIGJlIGhlbHBmdWwsIHRoYW5rcyENCltCYWRyaV0gUkZDIDcyMzAg
YWxsb3dzIG9mIGFkZGl0aW9uIGFuZCB1c2Ugb2YgbmV3IGhlYWRlcnMgaW4gc2VjdGlvbiAzLjIg
KDMuMi4xIHNwZWNpZmljYWxseSkuIEluaXRpYWxseSBjdXN0b20gaGVhZGVycyBwcmVwZW5kZWQg
dGhlIHZhbHVlICJ4LSIgdG8gdGhlIGhlYWRlciBuYW1lLiBFdmVuIHRob3VnaCB0aGlzIHByYWN0
aWNlIHdhcyBkZXByZWNhdGVkIGluIFJGQyA2NjQ4LCB0aGVzZSBoZWFkZXIgYXJlIHN0aWxsIHdp
ZGVseSB1c2VkIHRvIG1haW50YWluIHN1cHBvcnQgZm9yIGxlZ2FjeSBzeXN0ZW1zLiBUaGUgcGFw
ZXIgIkhlYWRlciBFbnJpY2htZW50IG9yIElTUCBFbnJpY2htZW50PyIgKGh0dHBzOi8vd3d3Lmlj
aXIub3JnL3Zlcm4vcGFwZXJzL2hlYWRlci1lbnJpY2htZW50LWhvdG1pZGRsZTE1LnBkZikgdGFs
a3MgYWJvdXQgdGhlIHVzZSBvZiB0aGlzIGZlYXR1cmUgYWNyb3NzIGRpZmZlcmVudCBNb2JpbGUg
Q2FycmllcnMuIFRoaXMgcGFwZXIgYWxzbyBnZXRzIGludG8gdGhlIHZ1bG5lcmFiaWxpdHkgb2Yg
dXNpbmcgdGhpcyBtZWNoYW5pc20sIGlmIGN1c3RvbWVyIHByaXZhY3kgaW5mb3JtYXRpb24gaXMg
c2VudCBvdmVyIHRoZSBpbnRlcm5ldC4gDQoNCj4NCj4gNC4gICAgICAgSFRUUCBSZWRpcmVjdGlv
biDigJMgQXMgb2YgdG9kYXkgdGhlIE1vYmlsZSBDYXJyaWVyIHdvdWxkIG5lZWQgdG8NCj4gYmxv
Y2sgb3IgcmVkaXJlY3QgYSBjdXN0b21lciBmb3IgbXVsdGlwbGUgcmVhc29ucw0KDQo+DQo+IGEu
ICAgICAgIFRoZSBjdXN0b21lciBtYXkgbm90IGJlIGFsbG93ZWQgdG8gdmlldyB0aGUgY29udGVu
dCBkdWUgdG8gcGFyZW50YWwNCj4gY29udHJvbHMuDQoNCk9LLCBzbyB5b3UgaGF2ZSB0aGUgaW5m
b3JtYXRpb24gdG8gYmxvY2ssIGJ1dCBubyBhYmlsaXR5IHRvIHJlZGlyZWN0IGluIHRoaXMgY2Fz
ZS4NCg0KW0JhZHJpXSBZZXMsIHRoYXQgdGhlIGV4YWN0bHkgdGhlIHNjZW5hcmlvLiBUaGUgbW9i
aWxlIHByb3ZpZGVyIGhhcyB0aGUgZGVzdGluYXRpb24gZG9tYWluL0lQIEFkZHJlc3MgZnJvbSB0
aGUgQ3VzdG9tZXIgcmVxdWVzdCBhbmQgaWRlbnRpZmllcyB0aGlzIGRvbWFpbiBhcyBhIGJsb2Nr
ZWQgZG9tYWluIHVuZGVyIFBhcmVudGFsIGNvbnRyb2wuDQoNCj4NCj4gYi4gICAgICBUaGUgY3Vz
dG9tZXIgIG1heSBub3QgYmUgYWxsb3dlZCB0byB2aWV3IHRoZSBjb250ZW50IGFzIHRoZXkgaGF2
ZQ0KPiBub3QgcHVyY2hhc2VkIHRoZSBjb250ZW50Lg0KDQpXb3VsZG4ndCB0aGlzIGJlIGEgc2Vy
dmVyLXNpZGUgZGVjaXNpb24gYW55d2F5PyAgSW4gdGhhdCBjYXNlLCBUTFMgbWFrZXMgbm8gZGlm
ZmVyZW5jZS4NCltCYWRyaV0gVGhlIHBhcnRpY3VsYXIgc2NlbmFyaW8gSSB3YXMgcmVmZXJyaW5n
IHRvIGlzIHdoZXJlIHRoZSBjdXN0b21lciBpcyBjaGFyZ2VkIGJ5IHRoZSBNb2JpbGUgQ2Fycmll
ciBvbiBiZWhhbGYgb2YgdGhlIGNvbnRlbnQgcHJvdmlkZXIuIEFzIGFuIGV4YW1wbGUgYSBjdXN0
b21lciBidXlzIGEgc3RyZWFtaW5nIHNlcnZpY2UgZnJvbSB0aGUgbW9iaWxlIHByb3ZpZGVyLCB3
aGljaCBhbGxvd3MgdGhlIGN1c3RvbWVyIHRvIHN0cmVhbSB2aWRlbyBjb250ZW50IGZyb20gdGhl
IHZpZGVvIHByb3ZpZGVyLiBUaGUgY3VzdG9tZXIgZ2V0cyBhIHNpbmdsZSBiaWxsIGZyb20gdGhl
IE1vYmlsZSBwcm92aWRlciwgYW5kIHRoZSBNb2JpbGUgcHJvdmlkZXIgaGFzIGEgcmV2LXNoYXJl
IG1vZGVsIHdpdGggdGhlIHZpZGVvIHByb3ZpZGVyLiBUaGlzIGlzIG1ldGhvZCBpcyB1c2VkIGJ5
IE1vYmlsZSBwcm92aWRlcnMgYW5kIGNvbnRlbnQgcGFydG5lcnMgdG8gcHJvbW90ZSBlYWNoIG90
aGVyIGFuZCBpbiByZXR1cm4gdGhlIGN1c3RvbWVyIGdldCB0aGUgY29udmVuaWVuY2Ugb2Ygb25l
IGJpbGwgYXMgY29tcGFyZWQgdG8gZGlmZmVyZW50IGJpbGwgZnJvbSBlYWNoIGNvbnRlbnQgcGFy
dG5lci4NCj4NCj4gYy4gICAgICAgVGhlIGN1c3RvbWVyIG1heSBub3QgYmUgYWxsb3dlZCBhcyB0
aGV5IGhhdmUgcmVhY2hlZCB0aGVpciB1c2FnZQ0KPiBsaW1pdCBhbmQgbmVlZCB0byBidXkgYWRk
aXRpb25hbCBkYXRhLg0KPg0KPiBDdXJyZW50bHksIHRoZSBNb2JpbGUgY2FycmllciByZWRpcmVj
dHMgdGhlIGN1c3RvbWVyIHVzaW5nIEhUVFAgDQo+IHJlZGlyZWN0IHRvIGEgcGFnZSB3aGljaCBl
ZHVjYXRlcyB0aGUgY3VzdG9tZXIgb24gdGhlIHJlYXNvbiBmb3IgdGhlIA0KPiBibG9ja2FnZSBh
bmQgcHJvdmlkZSBzdGVwcyB0byBwcm9jZWVkLiBPbmNlIHRoZSBjb250ZW50IGlzIGVuY3J5cHRl
ZCwgDQo+IHRoZSBNb2JpbGUgY2FycmllciBsb3NlcyB0aGUgb3B0aW9uIHRvIHJlZGlyZWN0IHRo
ZSB0cmFmZmljIGFuZCB0aGUgDQo+IG9ubHkgb3B0aW9uIGJlaW5nIHRvIGJsb2NrIHRoZSBjdXN0
b21lciwgZm9yIGFsbCBzY2VuYXJpb3MuIFRoaXMgd291bGQgDQo+IG5vdCBvbmx5IGNhdXNlIGJh
ZCBjdXN0b21lciBleHBlcmllbmNlLCBidXQgd291bGQgYWxzbyBuZWVkIGFub3RoZXIgDQo+IHdh
eSB0byBwYXNzIG9uIHRoZSBhZGRpdGlvbmFsIGluZm9ybWF0aW9uIHRvIHRoZSBjdXN0b21lciDi
gJMgdGV4dCANCj4gbWVzc2FnZS4gSWYgZm9yIGFueSByZWFzb24sIHRoZSBjdXN0b21lciBpcyBu
b3QgYWJsZSB0byBmaW5kIHRoZSANCj4gaW5mb3JtYXRpb24sIGhlL3NoZSB3b3VsZCBoYXZlIHRv
IGNhbGwgY3VzdG9tZXIgY2FyZSB0byBmaW5kIG91dCB0aGUgDQo+IHJlYXNvbi4gVGhpcyBpcyBu
b3Qgb25seSBhbiBpbmNvbnZlbmllbmNlIHRvIHRoZSBjdXN0b21lciwgYnV0IGFsc28gYW4gb3Zl
cmhlYWQgdG8gdGhlIHNlcnZpY2UgcHJvdmlkZXIuDQo+DQo+DQoNClRoaXMgaXMgcmVhc29uYWJs
ZSB0byBhZGQuICBEbyB5b3UgaGF2ZSBhIHJlZmVyZW5jZSB3ZSBjYW4gY2l0ZSBvbiB0aGUgcHJh
Y3RpY2VzPw0KW0JhZHJpXSBUaGVzZSBhcmUgcHJhY3RpY2VzIHRoYXQgaGF2ZSBiZWVuIGZvbGxv
d2VkIGluIHRoZSBpbmR1c3RyeSwgYnV0IGRvbuKAmXQga25vdyBpZiB0aGV5IGhhdmUgYmVlbiBw
dWJsaXNoZWQgYW55d2hlcmUuIEkgd2lsbCBjaGVjayBhbmQgZ2V0IGJhY2sgdG8geW91Lg0KDQpU
aGFuayB5b3UhDQpLYXRobGVlbg0KPg0KPiAgICAgICAgICAgICAgICAgUGxlYXNlIGZlZWwgZnJl
ZSB0byBnZXQgYmFjayB0byBtZSBpZiB5b3UgaGF2ZSBhbnkgDQo+IHF1ZXN0aW9ucy4NCj4NCj4N
Cj4NCg0KPiBUaGFua3MsDQo+DQo+IEJhZHJpDQo+DQo+IFJlbGlhbmNlIEppbw0KPg0KPg0KPiAi
Q29uZmlkZW50aWFsaXR5IFdhcm5pbmc6IFRoaXMgbWVzc2FnZSBhbmQgYW55IGF0dGFjaG1lbnRz
IGFyZSANCj4gaW50ZW5kZWQgb25seSBmb3IgdGhlIHVzZSBvZiB0aGUgaW50ZW5kZWQgcmVjaXBp
ZW50KHMpLCBhcmUgDQo+IGNvbmZpZGVudGlhbCBhbmQgbWF5IGJlIHByaXZpbGVnZWQuIElmIHlv
dSBhcmUgbm90IHRoZSBpbnRlbmRlZCANCj4gcmVjaXBpZW50LCB5b3UgYXJlIGhlcmVieSBub3Rp
ZmllZCB0aGF0IGFueSByZXZpZXcsIHJlLXRyYW5zbWlzc2lvbiwgDQo+IGNvbnZlcnNpb24gdG8g
aGFyZCBjb3B5LCBjb3B5aW5nLCBjaXJjdWxhdGlvbiBvciBvdGhlciB1c2Ugb2YgdGhpcyANCj4g
bWVzc2FnZSBhbmQgYW55IGF0dGFjaG1lbnRzIGlzIHN0cmljdGx5IHByb2hpYml0ZWQuIElmIHlv
dSBhcmUgbm90IHRoZSANCj4gaW50ZW5kZWQgcmVjaXBpZW50LCBwbGVhc2Ugbm90aWZ5IHRoZSBz
ZW5kZXIgaW1tZWRpYXRlbHkgYnkgcmV0dXJuIA0KPiBlbWFpbCBhbmQgZGVsZXRlIHRoaXMgbWVz
c2FnZSBhbmQgYW55IGF0dGFjaG1lbnRzIGZyb20geW91ciBzeXN0ZW0uDQo+DQo+IFZpcnVzIFdh
cm5pbmc6IEFsdGhvdWdoIHRoZSBjb21wYW55IGhhcyB0YWtlbiByZWFzb25hYmxlIHByZWNhdXRp
b25zIA0KPiB0byBlbnN1cmUgbm8gdmlydXNlcyBhcmUgcHJlc2VudCBpbiB0aGlzIGVtYWlsLiBU
aGUgY29tcGFueSBjYW5ub3QgDQo+IGFjY2VwdCByZXNwb25zaWJpbGl0eSBmb3IgYW55IGxvc3Mg
b3IgZGFtYWdlIGFyaXNpbmcgZnJvbSB0aGUgdXNlIG9mIA0KPiB0aGlzIGVtYWlsIG9yIGF0dGFj
aG1lbnQuIg0KDQoNCg0KLS0gDQoNCkJlc3QgcmVnYXJkcywNCkthdGhsZWVuDQoNCiJDb25maWRl
bnRpYWxpdHkgV2FybmluZzogVGhpcyBtZXNzYWdlIGFuZCBhbnkgYXR0YWNobWVudHMgYXJlIGlu
dGVuZGVkIG9ubHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGludGVuZGVkIHJlY2lwaWVudChzKS4gDQph
cmUgY29uZmlkZW50aWFsIGFuZCBtYXkgYmUgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3QgdGhl
IGludGVuZGVkIHJlY2lwaWVudC4geW91IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCBhbnkgDQpy
ZXZpZXcuIHJlLXRyYW5zbWlzc2lvbi4gY29udmVyc2lvbiB0byBoYXJkIGNvcHkuIGNvcHlpbmcu
IGNpcmN1bGF0aW9uIG9yIG90aGVyIHVzZSBvZiB0aGlzIG1lc3NhZ2UgYW5kIGFueSBhdHRhY2ht
ZW50cyBpcyANCnN0cmljdGx5IHByb2hpYml0ZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRl
ZCByZWNpcGllbnQuIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBieSByZXR1
cm4gZW1haWwuIA0KYW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGFueSBhdHRhY2htZW50cyBm
cm9tIHlvdXIgc3lzdGVtLg0KDQpWaXJ1cyBXYXJuaW5nOiBBbHRob3VnaCB0aGUgY29tcGFueSBo
YXMgdGFrZW4gcmVhc29uYWJsZSBwcmVjYXV0aW9ucyB0byBlbnN1cmUgbm8gdmlydXNlcyBhcmUg
cHJlc2VudCBpbiB0aGlzIGVtYWlsLiANClRoZSBjb21wYW55IGNhbm5vdCBhY2NlcHQgcmVzcG9u
c2liaWxpdHkgZm9yIGFueSBsb3NzIG9yIGRhbWFnZSBhcmlzaW5nIGZyb20gdGhlIHVzZSBvZiB0
aGlzIGVtYWlsIG9yIGF0dGFjaG1lbnQuIgo=


From nobody Fri Mar 10 06:27:12 2017
Return-Path: <mcr+ietf@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 8D9E112958E for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 06:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D7NZ0a7Wcg3X for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 06:27:09 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14DC7129579 for <ietf@ietf.org>; Fri, 10 Mar 2017 06:27:09 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 06718E206; Fri, 10 Mar 2017 09:49:57 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 043466381A; Fri, 10 Mar 2017 09:27:08 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: The CIA mentions us
In-Reply-To: <CAMm+Lwg1MzDOn9xQ_-3oKcZ1odFF552sPGJhu17KRTP0SNR2vw@mail.gmail.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <00A55B3A256BD71DFB1866B4@PSB> <CAMm+Lwg1MzDOn9xQ_-3oKcZ1odFF552sPGJhu17KRTP0SNR2vw@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Fri, 10 Mar 2017 09:27:07 -0500
Message-ID: <405.1489156027@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PUI58mbF_rSF5TYHM2mdjv7V5GI>
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 14:27:10 -0000

--=-=-=
Content-Type: text/plain


Phillip Hallam-Baker <phill@hallambaker.com> wrote:
    > However, it is not just the US agencies doing this work. There are now
    > 117 cyber commands and there is a real problem of 'loose
    > cyber-weapons'. It is to the interest of the US and to all the other
    > cyber-commands that a norm is established that cyber weapons are
    > secured end to end throughout their lifecyle and tools produced to
    > enable that to be achieved.

I'm not really sure I understand what it means to secure a cyber weapon.

You could be talking about keeping the source code in locked briefcases,
or you could be talking about some kind of snake-oil DRM on the binaries,
like the movie and game industries thinks they have "invented".  Or something
else completely.

    > Such tools do not currently exist. However some key patent expiries
    > that have occurred and will be complete in November this year make true
    > end to end data level encryption practical. I have proof of concept but
    > short of infringing code running in the lab which I will push out as
    > soon as I can together with the supporting specifications.

Now here you seem to be talking about securing things in transit.

if I may air some of my griping: tcpdump has recently dealt with some hundred
potential vulnerabilities found by futzing.  I was interested to find a file
called "PCAP" in the Vault 7 archives, but it's not really released yet.

What's annoying is that there is money for attack tools, and there are
rewards for finding exploits, but not much for fixing bugs, and many serious
disincentives to good design in the first place.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljCt7kACgkQgItw+93Q
3WWygAf+Kxzh7tl1zjKH0rVtJorR9tU0C/iJzGKoVj0d0C3b3LJ5J627TzO68tdb
q84XKMkDJkWugMSmBMvbFsICSGXNmMSx6yuEWlwxhZDrd8NPtFJssFxFRhO8HKgH
SUToZEUA1iOVLmLyq65s/bTTqOpb8uS6g+CZoqY4ayr5AHAi0pGCXDPI10YazdM1
Oq/2mJcZsdFOkSMM3Egy/gQhFzTBWiKkB4Q+bwv07e4+2qDO2RlyeG8hbuoQtjYs
1HbSkSV0rcDStt71PhkjEBQOgoOFYEiYeUHV9yRiJ6c4qQS4BnpUrttaVBQnLLcT
BDdo/aXoesBFHQLwOeDc/429VUODCw==
=sQzU
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Mar 10 09:14:28 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA9481295FD; Fri, 10 Mar 2017 09:14:15 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-ippm-twamp-time-format-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148916605590.6778.14181761811890656682@ietfa.amsl.com>
Date: Fri, 10 Mar 2017 09:14:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g3Wl5B-6OcVPjM0FKZc003re0Sc>
Cc: draft-ietf-ippm-twamp-time-format.all@ietf.org, ietf@ietf.org, ippm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 17:14:16 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ippm-twamp-time-format-??
Reviewer: Joel Halpern
Review Date: 2017-03-10
IETF LC End Date: 2017-03-15
IESG Telechat date: Not scheduled for a telechat

Summary: This revision fully resolves my concerns from -03

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A



From nobody Fri Mar 10 09:14:41 2017
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 B45B91295FD for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 09:14:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hEo6nce4c3LU for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 09:14:33 -0800 (PST)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E76D7129982 for <ietf@ietf.org>; Fri, 10 Mar 2017 09:14:31 -0800 (PST)
Received: by mail-wr0-x22d.google.com with SMTP id g10so68987450wrg.2 for <ietf@ietf.org>; Fri, 10 Mar 2017 09:14:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Xb5BVnpooBhRMrZdPA1fv/thSrU/GwK5dO0vh+ASrQY=; b=f6S4aX1RrsWkNLnABHEifNvZsVTecJ7B1DOYtkEGVI4XMeqZyO/jrMCACOb54LHas3 mHpnhwXLXe+gVRhNYp2dQR8DEsaKaQshDIyDixYowRqs7T3YbjLPEAZ8YXYXKL95kpU2 v8eoNfEQFOTGN8fot32ZJnirZKFAVN2VSMbCY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Xb5BVnpooBhRMrZdPA1fv/thSrU/GwK5dO0vh+ASrQY=; b=RunPtUjkPd7Q2m+WFQNAI7biR1Uck8S8UVUYOpjfOTtgEh/dFMFopbQURShZ0pz06q vloEwcuJOvpkHpbij2AHIcsGsbZTNtwhQrb2FaiRoPzlEkq2CX9S4Wc5Jj2jyR/Usp+Z RvdXCkQiFmGmr7I8V4Z3ufCvXYq1S3SHfLRV6L4ulOVinWosegUgl5T/cmlw1g00aXYp pbN/rMJi3F4fQZiaHdeDjFy/kA3iF6vJ3qna9DR+Z28shdwC2eyBMb9RdqRfHi+PrZBP 2H9Gw3JeVZUqWHOn9zI2qDMafM4oIfOpa6jc2IxCX080NOeWnXoLm3vqKXnhJ1jIs9hg 6eRw==
X-Gm-Message-State: AMke39lWHLcMr+tlUoNaA+OEn/OGKLQo5mvxsEU07sWoP5jADe806o25ZFj1xB8HnOelOP5HInJnqUZ2kkyHUxvI
X-Received: by 10.223.152.83 with SMTP id v77mr16831342wrb.109.1489166070458;  Fri, 10 Mar 2017 09:14:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.151.17 with HTTP; Fri, 10 Mar 2017 09:14:29 -0800 (PST)
In-Reply-To: <CAMm+LwgHa64a6brkXadA2Okty7=394ZbMyQgKy32=mjXvgA4zQ@mail.gmail.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <f9546015-ea7d-b23e-f68c-cb6243c6d181@si6networks.com> <CAMm+LwgHa64a6brkXadA2Okty7=394ZbMyQgKy32=mjXvgA4zQ@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Fri, 10 Mar 2017 17:14:29 +0000
Message-ID: <CAKHUCzwVf_nCwYMjj5Bk_uh-c+WLCEoje33RcBsObX+H55JX7A@mail.gmail.com>
Subject: Re: The CIA mentions us
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PzqkFANHkF83Z2Ci58JkagDi7Xw>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 17:14:38 -0000

On 9 March 2017 at 16:28, Phillip Hallam-Baker <phill@hallambaker.com> wrote:
> US law is rather interesting. Unlike UK law where it is not necessary to
> 'sign the official secrets act' to be covered by it, US civil law is rather
> less severe. Military law is a different matter, active duty military can be
> ordered to be careful with classified materials. Civil law requires
> intention to transmit to an unauthorized party or carelessness amounting to
> constructive intent.

In the UK, you don't have to have "signed the Act" to be covered by it
since the 1989 Act, no.

You do, however, sign even now, but it's there to remove a particular
defence of "I didn't know this was classified [any more]", since one
signs to acknowledge that information seen might be classified and
that one understands that one shouldn't disclose them.

Of course this is delightfully off topic at this point.

Dave.


From nobody Fri Mar 10 10:50:03 2017
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 68A611295A9 for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 10:50:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q8hpz6TX_gL1 for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 10:49:59 -0800 (PST)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70077129583 for <ietf@ietf.org>; Fri, 10 Mar 2017 10:49:59 -0800 (PST)
Received: by mail-yw0-x231.google.com with SMTP id p77so29304317ywg.1 for <ietf@ietf.org>; Fri, 10 Mar 2017 10:49:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=zr891jBl6ldF3KTTMhqbUnqJqHPNJr9z0F8AKNAK3QU=; b=qjdFFb4RMKlMQvAe7FtU/OD6ANiuSkvJKVRga1VoAwOVIOwBUgkJPDzCk11ZB6iNrm KhxfGw/wbzEY3pUdTmWJGpKkK4Dr76SpfAdDQrtcm2jp2B8YuOwy6EEyRgCw1v+zXMsI RP119t9/0Y8bmxCyfSktg1wLF02JZi5MlS8Mf3QWrFnFCYkoO8RnqpVswZw6fiiOey0t hjt8dAW6Tzj+ATe0Xm7Tz0tmEPP4x+zQLDnZlVYkURhiEYph+BF5hI1V3dnX2xQm/+Yo kWSOvPSGfG5l4CATzCX+hQuRasvMbnWFKLY0gHndLR6yQM9Hu/n0X1sw3nKYQBFtSQhp 69yg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=zr891jBl6ldF3KTTMhqbUnqJqHPNJr9z0F8AKNAK3QU=; b=f9yJJcT8CzueP64WlHE2mLHiMBJct2uNHzkUvaW48gvkF62o+3G5HeHH139rjoE7ZX h27IRnikFRtHDBn8VoD+xnJP57vwli70HmTAH0IdANNtj8JDAIsgPDz4EdESZbQaiSvc 86jtZD316muI1ESN41uRFc4hNTRBdP64GVkNaqjtaKze2jODBEhy3bvcH2m+TbVPrzie kdIAXd8bUQL3mBWdm0tYahtAcyB4AjN7rxo4nPBHk6pwxdVepqS05FfIgkR+FHvJMABF lvADqdI6lmU3QdehmyB6o3EuzeRiZVVYS7KNt6FFI8IapSYDev6uWNcMTwXp8vCgBD9G QAvw==
X-Gm-Message-State: AMke39kE5xi1bzWl6wR8hROVgmi0/c/Symk7cMrYhHH5+rfFEplHU0ImGg70h1ayvsK7FDIQbJA8wGvR2vZutQ==
X-Received: by 10.129.109.75 with SMTP id i72mr8785721ywc.340.1489171798599; Fri, 10 Mar 2017 10:49:58 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Fri, 10 Mar 2017 10:49:57 -0800 (PST)
In-Reply-To: <405.1489156027@obiwan.sandelman.ca>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <00A55B3A256BD71DFB1866B4@PSB> <CAMm+Lwg1MzDOn9xQ_-3oKcZ1odFF552sPGJhu17KRTP0SNR2vw@mail.gmail.com> <405.1489156027@obiwan.sandelman.ca>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 10 Mar 2017 13:49:57 -0500
X-Google-Sender-Auth: iF4xGrgB3Z6ALYxJOuj4Bmxo6CA
Message-ID: <CAMm+Lwj9=t6UtQJ8880QR1zycJfpcuCZX1MgQtko1wef_1PwDQ@mail.gmail.com>
Subject: Re: The CIA mentions us
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a114db4ac10b0fe054a64d4b5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DxM8v2RZHhIsMQGfq0Mx0YACWNs>
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 18:50:01 -0000

--001a114db4ac10b0fe054a64d4b5
Content-Type: text/plain; charset=UTF-8

I do not mean either transport or snake oil.

DRM has been a bust because two problems were conflated

1) Limiting access to confidential documents to those with a need to know

2) Preventing disclosure but those granted access.

The first is a completely tractable problem of cryptographic engineering
that I have a working, almost open (November) solution for with MIT License
reference code.

The second is never going to have an absolute solution. Even with
trustworthy hardware, there are techniques that can break a device if you
are prepared to pay a lot of money to do so. Techniques that involve
electron microscopes and sanding down the back of devices. Even FIPS-140
level 3 are not absolutely immune.

But this disclosure would probably have been prevented with (1) alone and
almost certainly with (1) plus pervasive accountability controls. Which
incidentally, Mesh/Recrypt does support.


I want to establish an international norm that cyber commands secure their
attack code end to end and I am proposing an infrastructure that does
exactly that.

Now the utility of such a scheme embedded into Office, OfficeLibre and the
like would be vastly wider than just cyber commands. But one of the
pathologies of the US government research funding programs is that the only
work that can be funded is work that has a military application. So I am
framing the problem in this form for the benefit of DARPA program managers
looking to give me money to work on this.


I call my subset of the DRM problem Confidential Data Control. The
introduction of 'rights' into the problem statement is entirely spurious.

Right now, the crypto code works in Ed25519 and will probably work for
Ed448 by this evening. Getting it to work on Montgomery curves is a little
more complicated as I have to figure out how to do point addition as a
primitive separate from multiplication. If someone could shoot me some code
to copy, it would help me save a few hours and spend some quality time with
my daleks this evening.


On Fri, Mar 10, 2017 at 9:27 AM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Phillip Hallam-Baker <phill@hallambaker.com> wrote:
>     > However, it is not just the US agencies doing this work. There are
> now
>     > 117 cyber commands and there is a real problem of 'loose
>     > cyber-weapons'. It is to the interest of the US and to all the other
>     > cyber-commands that a norm is established that cyber weapons are
>     > secured end to end throughout their lifecyle and tools produced to
>     > enable that to be achieved.
>
> I'm not really sure I understand what it means to secure a cyber weapon.
>
> You could be talking about keeping the source code in locked briefcases,
> or you could be talking about some kind of snake-oil DRM on the binaries,
> like the movie and game industries thinks they have "invented".  Or
> something
> else completely.
>
>     > Such tools do not currently exist. However some key patent expiries
>     > that have occurred and will be complete in November this year make
> true
>     > end to end data level encryption practical. I have proof of concept
> but
>     > short of infringing code running in the lab which I will push out as
>     > soon as I can together with the supporting specifications.
>
> Now here you seem to be talking about securing things in transit.
>
> if I may air some of my griping: tcpdump has recently dealt with some
> hundred
> potential vulnerabilities found by futzing.  I was interested to find a
> file
> called "PCAP" in the Vault 7 archives, but it's not really released yet.
>
> What's annoying is that there is money for attack tools, and there are
> rewards for finding exploits, but not much for fixing bugs, and many
> serious
> disincentives to good design in the first place.
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>

--001a114db4ac10b0fe054a64d4b5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">I d=
o not mean either transport or snake oil.</div><div class=3D"gmail_default"=
 style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"=
font-size:small">DRM has been a bust because two problems were conflated</d=
iv><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div cl=
ass=3D"gmail_default" style=3D"font-size:small">1) Limiting access to confi=
dential documents to those with a need to know</div><div class=3D"gmail_def=
ault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" styl=
e=3D"font-size:small">2) Preventing disclosure but those granted access.</d=
iv><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div cl=
ass=3D"gmail_default" style=3D"font-size:small">The first is a completely t=
ractable problem of cryptographic engineering that I have a working, almost=
 open (November) solution for with MIT License reference code.</div><div cl=
ass=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gma=
il_default" style=3D"font-size:small">The second is never going to have an =
absolute solution. Even with trustworthy hardware, there are techniques tha=
t can break a device if you are prepared to pay a lot of money to do so. Te=
chniques that involve electron microscopes and sanding down the back of dev=
ices. Even FIPS-140 level 3 are not absolutely immune.</div><div class=3D"g=
mail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-size:small">But this disclosure would probably have been =
prevented with (1) alone and almost certainly with (1) plus pervasive accou=
ntability controls. Which incidentally, Mesh/Recrypt does support.</div><di=
v class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">I want to establish an international norm t=
hat cyber commands secure their attack code end to end and I am proposing a=
n infrastructure that does exactly that.</div><div class=3D"gmail_default" =
style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"f=
ont-size:small">Now the utility of such a scheme embedded into Office, Offi=
ceLibre and the like would be vastly wider than just cyber commands. But on=
e of the pathologies of the US government research funding programs is that=
 the only work that can be funded is work that has a military application. =
So I am framing the problem in this form for the benefit of DARPA program m=
anagers looking to give me money to work on this.</div><div class=3D"gmail_=
default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">I call my subset of the DRM problem Confidential Data Contro=
l. The introduction of &#39;rights&#39; into the problem statement is entir=
ely spurious.<br></div><div class=3D"gmail_default" style=3D"font-size:smal=
l"><br></div><div class=3D"gmail_default" style=3D"font-size:small">Right n=
ow, the crypto code works in Ed25519 and will probably work for Ed448 by th=
is evening. Getting it to work on Montgomery curves is a little more compli=
cated as I have to figure out how to do point addition as a primitive separ=
ate from multiplication. If someone could shoot me some code to copy, it wo=
uld help me save a few hours and spend some quality time with my daleks thi=
s evening.</div><div class=3D"gmail_default" style=3D"font-size:small"><br>=
</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fr=
i, Mar 10, 2017 at 9:27 AM, Michael Richardson <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr+ietf@sandelman.ca<=
/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"><span class=3D""><b=
r>
Phillip Hallam-Baker &lt;<a href=3D"mailto:phill@hallambaker.com">phill@hal=
lambaker.com</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; However, it is not just the US agencies doing this work.=
 There are now<br>
=C2=A0 =C2=A0 &gt; 117 cyber commands and there is a real problem of &#39;l=
oose<br>
=C2=A0 =C2=A0 &gt; cyber-weapons&#39;. It is to the interest of the US and =
to all the other<br>
=C2=A0 =C2=A0 &gt; cyber-commands that a norm is established that cyber wea=
pons are<br>
=C2=A0 =C2=A0 &gt; secured end to end throughout their lifecyle and tools p=
roduced to<br>
=C2=A0 =C2=A0 &gt; enable that to be achieved.<br>
<br>
</span>I&#39;m not really sure I understand what it means to secure a cyber=
 weapon.<br>
<br>
You could be talking about keeping the source code in locked briefcases,<br=
>
or you could be talking about some kind of snake-oil DRM on the binaries,<b=
r>
like the movie and game industries thinks they have &quot;invented&quot;.=
=C2=A0 Or something<br>
else completely.<br>
<span class=3D""><br>
=C2=A0 =C2=A0 &gt; Such tools do not currently exist. However some key pate=
nt expiries<br>
=C2=A0 =C2=A0 &gt; that have occurred and will be complete in November this=
 year make true<br>
=C2=A0 =C2=A0 &gt; end to end data level encryption practical. I have proof=
 of concept but<br>
=C2=A0 =C2=A0 &gt; short of infringing code running in the lab which I will=
 push out as<br>
=C2=A0 =C2=A0 &gt; soon as I can together with the supporting specification=
s.<br>
<br>
</span>Now here you seem to be talking about securing things in transit.<br=
>
<br>
if I may air some of my griping: tcpdump has recently dealt with some hundr=
ed<br>
potential vulnerabilities found by futzing.=C2=A0 I was interested to find =
a file<br>
called &quot;PCAP&quot; in the Vault 7 archives, but it&#39;s not really re=
leased yet.<br>
<br>
What&#39;s annoying is that there is money for attack tools, and there are<=
br>
rewards for finding exploits, but not much for fixing bugs, and many seriou=
s<br>
disincentives to good design in the first place.<br>
<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
=C2=A0-=3D IPv6 IoT consulting =3D-<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--001a114db4ac10b0fe054a64d4b5--


From nobody Fri Mar 10 12:13:37 2017
Return-Path: <jari.arkko@piuha.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 1035C129440 for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 12:13:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LPfGsrLCOvhB for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 12:13:34 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id AB2E2129424 for <ietf@ietf.org>; Fri, 10 Mar 2017 12:13:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 098432CFD8 for <ietf@ietf.org>; Fri, 10 Mar 2017 22:13:32 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10txQR2O6MUH for <ietf@ietf.org>; Fri, 10 Mar 2017 22:13:31 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 566B02CC5E for <ietf@ietf.org>; Fri, 10 Mar 2017 22:13:31 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_B10D7AC6-ACAE-441D-8DB0-2F7FC7992BB3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: The CIA mentions us
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net>
Date: Fri, 10 Mar 2017 22:13:28 +0200
Message-Id: <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net>
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vrPUOJ7JAibs8shZ2sFoJbn_puA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 20:13:36 -0000

--Apple-Mail=_B10D7AC6-ACAE-441D-8DB0-2F7FC7992BB3
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=windows-1252

FWIW, Stephen and I wrote a blog article around the
more high-level conclusions on this topic.

https://www.ietf.org/blog/2017/03/observations-on-the-cia-revelations/

Comments appreciated.

Jari


--Apple-Mail=_B10D7AC6-ACAE-441D-8DB0-2F7FC7992BB3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYwwjpAAoJEM80gCTQU46qLL4QAJfSqFreR2P5JbCsBtp7vlr+
vHhhbgDv6LY+AKbA1QsS0fxk6TrMoH4AhVK09TgG1gcOKhBXNvrwpR65/AlmRkod
gfBPRu3GIT8l8zNf3+oqhxKvcUds+gSt1WMjdbAy2gf/FFAO/XCECNKUo4IhYUdL
iN65JrhlrfkbW6OF0WM6cOAce68dUEYmABUv/jmzNlJU4RqMVNKPJvzjTDy3/UOb
jMycjivwF9UfPJrMse7srPDXGpxWAw6xYuVKtgecXL43ozrGLvmeBEjW2r4D/MFu
KhNzsPpXbfR7jZHVFV+D/FxLY+5LLm2sgmBGXL/vClfiwbZbrqVYA4VFK/9VOB7y
JvPVgGubKFtRTzhAeQBLcanB97aDtyapb+Ydig/M4hHdbHbCQzFdQvrU7XLIFyAn
AsjMtJdjQISYAg3Dl0/87HRjWn7dunt+FXtVTAL7mFMQcw3WeV0wQlfDgydxaizw
b0791XA8l4FCTHjSA0YiZ0XVWlwoyh6RnJNuwu68Fjpebawtq4miIgWHJAV4hUvn
HB2U6X7/lYlJmrTJAGs0+9whtwJB4Dtv1t0AMkKyAnc8qm7OmenxU8wDuh+3R8A2
q00zum2I09Zbfo24nlJk1MY+OnahvLiyCzUX58P61PJJE5D35jffKYUKbRi1NbgO
apVMmJtYKGh11dB9zojG
=vtZ8
-----END PGP SIGNATURE-----

--Apple-Mail=_B10D7AC6-ACAE-441D-8DB0-2F7FC7992BB3--


From nobody Fri Mar 10 13:46:57 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9CE1294AA for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 13:46:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 687_H9R7nooy for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 13:46:53 -0800 (PST)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A70B71294F4 for <ietf@ietf.org>; Fri, 10 Mar 2017 13:46:49 -0800 (PST)
Received: by mail-qk0-x231.google.com with SMTP id p64so188463437qke.1 for <ietf@ietf.org>; Fri, 10 Mar 2017 13:46:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fz+5vT9jD09MRHOGYb+ll9AHFTBrtUIhcBYVoY6QjdU=; b=o9tKLmm7gVlw6jTBwpHluYcqV3l0zOB7YP1mr+RsfbWdS1CvUsJmkBk2uipAe2x6Z6 fOyrlbbSEs211IkGwA2Ye6SgjubpQrz1CD2Uh9uQF5hXM0iw9N3ih9/fRNz/b6vLIBl1 QCUrwjX6zayASR4aBv82S2EdfLmpNvuLSYOB6304oc2oVS7w62o/Bh2X+ALjC71ExkZZ bu7BUc5HLAvoarRDx98vdiMSqFljfwfYpAACPRoAW3CluxbmCL55Ap28yC0CR28orcpt MaWzIMqkGM7vQ9StJ7FzLUCW9Un0tCV9Ye4Vw+h0uf6lqnM06ifamzwP2eSVWCkyeIao YWgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fz+5vT9jD09MRHOGYb+ll9AHFTBrtUIhcBYVoY6QjdU=; b=GzuHCHX+NPyQxL87lmdPx907sksYlhMB3Mj7rykkBiWs/WeMRvro7gxM6hscXBIHe2 Dz3xJL0uXzifWyw9+HKAHeqGZ98nbn0x3NJIpK0hsfjelXUO9B6pZfMAIh0Iudkba1kO 16ioMyyZeBefHQtAhZAteUgmiN051EEJOR4rCkaojLjfpVsHKWLK6XatRUwYixpCO+e0 1ENZtRiscVUjhrkRutY6fcBAJ9d11mirxvnIqjEpFXA+tPaX0/xUOiFPnfnJm2wZEGwg o5pQ9SwYNYeP8nn7YZxMiaD3ANfmSFrX3gyZvUVGhy6j4gfD5HNIAv5Ifo+OPh21YRpo cUBA==
X-Gm-Message-State: AMke39l6I/gLoBe/is2226OnXt7pwW5pGSVJG0wFLEWAAVPv318zv5LF6pON8rYKg2rO4g==
X-Received: by 10.237.41.229 with SMTP id o92mr21305637qtd.223.1489182408895;  Fri, 10 Mar 2017 13:46:48 -0800 (PST)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id d26sm7167016qtg.26.2017.03.10.13.46.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Mar 2017 13:46:48 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: The CIA mentions us
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net>
Date: Fri, 10 Mar 2017 16:46:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/28xRpsIpkePOGNm2JCYzuKCw7Hc>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 21:46:56 -0000

The one thing I wish you'd mentioned in this blog, but did not, is a =
point someone made earlier on this thread: that the fact that the CIA =
needs to hack individual devices to bypass end-to-end encryption means =
that what we are doing in promoting encryption is effective and worth =
doing: rather than everybody's communications being vulnerable, =
individuals must now be targeted.=


From nobody Fri Mar 10 14:53:13 2017
Return-Path: <bob.hinden@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 7FBA5129410 for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 14:53:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9dEzTjY3podV for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 14:53:10 -0800 (PST)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFC161293E8 for <ietf@ietf.org>; Fri, 10 Mar 2017 14:53:09 -0800 (PST)
Received: by mail-io0-x22e.google.com with SMTP id l7so57369836ioe.3 for <ietf@ietf.org>; Fri, 10 Mar 2017 14:53:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=p4oXde7TeO8ygRX8Jjle/+KfT0Ed8w+MBd9PtXbosOU=; b=PfI+vwB8DgQr7J7BB7kt9hsSExvUQZ8Wkf39/M41EF+ufSnquhjEE/FuEwQXfzP5Yx rjLnPVSC1gX9Gheah+JxDkB6hfI9R0N+1ZgmLNOztKuy/6dqXQqONal0hd6kPnLT8gBG smfUiLSwiFjEbg16RiwZzNd5TEvhDODmqKMyAYbMmesNIxSsYCnYkpMU5FLX3Gnk4+0R z+BPa+qWPQpexpVKtwHh41e3BCt7p/X3e0VwfZpkvQuNXGI0loL8lV/kxNtx5Qk9BTt3 u94gAH38bVdSUSXhF9RC0/lB1uzjy9XFAB/bhfjzY1zsrvlv89n8U7JAgoYsPjvMgdR9 eO5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=p4oXde7TeO8ygRX8Jjle/+KfT0Ed8w+MBd9PtXbosOU=; b=DsHu07y1vFvckd9tlFOXQeh0AgH3uZNxohCtEhp/CFnkBUVo2di7c37FS0Bhr0FVxV Jn20a5LJX3hxO25+G75CKbiwfDQ8A11XcAwNeYHXMI1SFLq2xE0g+LTzPTPH/lHgkP7z fxjC/VBjLpDhU2HGV1CE0FsIlkYips98n/hPP054kMuYePwpWDld4dIFep96aM1RlCVA 1VeiU0K8Uojh0FfhbY+uqvVKN5jzTICWMtazazQYlJjO1UKjlwVjvkH5IrNnWv335TYv G6gFUu5Cj4WRySrY9/0E8+JysngRbG5hKRgh+bOYLzZ2a3mKXVtDnrHa551/3lodTm5g uyUQ==
X-Gm-Message-State: AMke39mwEANpfuAH4z4cRKStmZlJ2DtK9IPQBFPjLqXDDAfoigDtx/354Yq1UdoHvQ/0Sw==
X-Received: by 10.107.19.38 with SMTP id b38mr11183906ioj.67.1489186389349; Fri, 10 Mar 2017 14:53:09 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id 12sm366779itl.31.2017.03.10.14.53.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Mar 2017 14:53:08 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7799C0F0-69E5-4072-A0CD-FAF73ABFBCF1"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: The CIA mentions us
Date: Fri, 10 Mar 2017 14:53:06 -0800
In-Reply-To: <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com>
To: Ted Lemon <mellon@fugue.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TkBDBZ2-dp2iTzqcPFJDP5rxUhI>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 22:53:11 -0000

--Apple-Mail=_7799C0F0-69E5-4072-A0CD-FAF73ABFBCF1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Ted,

> On Mar 10, 2017, at 1:46 PM, Ted Lemon <mellon@fugue.com> wrote:
>=20
> The one thing I wish you'd mentioned in this blog, but did not, is a =
point someone made earlier on this thread: that the fact that the CIA =
needs to hack individual devices to bypass end-to-end encryption means =
that what we are doing in promoting encryption is effective and worth =
doing: rather than everybody's communications being vulnerable, =
individuals must now be targeted.

I think that=E2=80=99s a good point.

To expand what you said, these tools are for targeted attacks, not mass =
surveillance.  Encryption continues to be a strong protection against =
mass surveillance.

Bob



--Apple-Mail=_7799C0F0-69E5-4072-A0CD-FAF73ABFBCF1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYwy5SAAoJEK7rdBF357uo774H+wT9OKTITyOacOGtuqulo9qF
/sVuoXVdWnzOKTo76tHJ+pXydtdEWO4PAOZ879dCsio0dG8aujeCbmkl750l98bK
LE+cFF8iSItl8VCi7Kg4TVQ6ce24jwP16RKiP271VNzkLUHXb2HQ7R8TJtxJh3r3
+AJACMHONIDlcbfzRZ8bMRT2wphiY70WspZT9UrLsVC1NtT5KaUB4d4Ffr7q9Mpa
cUgl6wGXNHgs/pmemr1zbQ8bNQazdqdU1lDxvY+efbSPIQyaT7jnJXjJb7TuFZZS
3byd342WvdHvPfHAt//q1+UzlIdnItP+M2jcUiMHgYDdlmy1gtpIqzcc02lRBrE=
=vXRS
-----END PGP SIGNATURE-----

--Apple-Mail=_7799C0F0-69E5-4072-A0CD-FAF73ABFBCF1--


From nobody Fri Mar 10 15:48:17 2017
Return-Path: <jari.arkko@piuha.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 0F0921294CC for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 15:48:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKyZomc-hsQL for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 15:48:14 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C1E841289C4 for <ietf@ietf.org>; Fri, 10 Mar 2017 15:48:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0FD0C2CFD8; Sat, 11 Mar 2017 01:48:12 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G2D3z5impnBG; Sat, 11 Mar 2017 01:48:11 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 90C182CC5E; Sat, 11 Mar 2017 01:48:11 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: The CIA mentions us
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_69DAAA1A-6350-4ED1-ACD2-6B226FD153CD"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com>
Date: Sat, 11 Mar 2017 01:48:08 +0200
Message-Id: <BD825880-A4EC-4786-B4D8-9085EFE073C7@piuha.net>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>, Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KQso1eAcqa84Z-EzAGvkzx6unY8>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Mar 2017 23:48:16 -0000

--Apple-Mail=_69DAAA1A-6350-4ED1-ACD2-6B226FD153CD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

It is a good point. Thanks. I=92ll consider making a revision. Tomorrow.

Jari


--Apple-Mail=_69DAAA1A-6350-4ED1-ACD2-6B226FD153CD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYwzs5AAoJEM80gCTQU46qiRMP/1DlEDSm2QAvC3MxRIC0793U
iV/qC6XraqZEltyJwOQflgcDwzmmmF8LGGUyvvOiwSbF68p6CI4Zu2yh/aWW5FAl
pUEUW0FJU9QxZHpbUH1bv6MDLht2Zf2/NF5HzDJX7XrC/odunATuOLeqBs8WbzYD
zN0xlvWQVmgmwqQu70GfOw3G5BjpM/5Xf7LmFEmJpOBcuVpJdxrBO9kM2KHLTej0
/ja0oI3AXog9EEN3BxeYCcwU5nRnaLyEQC4crITLfyvKXJ/G5NsHzRb3I0EoTM4I
q15ceRxwj5T4AGsBn5qlGvrguVEMRiSLb7dW7HJNS+6tLeMR38z5yNkDlnu1BXww
KN7brkOCDEsDXYWdiGP8cLvBy5EVUaQzLKTSmWTCCe7lJil9oDaHBu2DiZULhpRz
35T/3McszfwSaBBtAZ70VIR3bvOPC4yLLpBx6zmga9o7OrW3PHSvtnrw8eaEmHOs
TZD6ej+G0YArfdU984lWtw/C/V2OosAEbXqn48P3cXjr8LHY0YMGzNiL0c0vy14F
SZiKukfp41VysHd3PWLyO0k+OY72uNi0zyt16sBjiaR87+ImyQyVsztfmzHmZI2v
QUjuofAjQf3ToNZdltqX2iQ7YCYGpQbdxZRiT5My5Fcj9hicjkoA4J/jFqenkQ7W
cAtnOLe4exo9P9v60art
=wbX+
-----END PGP SIGNATURE-----

--Apple-Mail=_69DAAA1A-6350-4ED1-ACD2-6B226FD153CD--


From nobody Fri Mar 10 18:02:21 2017
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 59BDD129518 for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 18:02:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XJSUuNdvjGFt for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 18:02:14 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B4E71294CC for <ietf@ietf.org>; Fri, 10 Mar 2017 18:02:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 8D03FBE83; Sat, 11 Mar 2017 02:02: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 XQ_AiOspXNeo; Sat, 11 Mar 2017 02:02:08 +0000 (GMT)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 16176BDCC; Sat, 11 Mar 2017 02:02:08 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1489197728; bh=ti5Z79OzQfE+BQG27YoPaASR51ZkADvZGEFZiwdx/oQ=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=zo2u1bFtpKEotvYTH6enxd9iHikvJdDgHH3o3aFAMVVXnormICMVgB8UBuP/k7Q7L cT2ifJGSt2sQHpM/NiLlHT+ajzk6wbJRf1flhl6F9Cgu2RJ+tbQIKu06dGsFG9XU4Z SF/lsp0em1cvnbRT4jsvLmnGFcFNKq1o9oRTjRI8=
Subject: Re: The CIA mentions us
To: Bob Hinden <bob.hinden@gmail.com>, Ted Lemon <mellon@fugue.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie>
Date: Sat, 11 Mar 2017 02:02:07 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PqpT54mP6kWdQN2Q2LJUpcxuGO2kkuo93"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WfbAh53oaQ1qNao2pH_hpvCODwY>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Mar 2017 02:02:20 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PqpT54mP6kWdQN2Q2LJUpcxuGO2kkuo93
Content-Type: multipart/mixed; boundary="jBPviSa0jdrI2lwaCA4QUEIimiRGUvpJV";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Bob Hinden <bob.hinden@gmail.com>, Ted Lemon <mellon@fugue.com>
Cc: IETF <ietf@ietf.org>
Message-ID: <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie>
Subject: Re: The CIA mentions us
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr>
 <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com>
 <20170307160840.duv7wwg5sm23nrek@nic.fr>
 <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com>
 <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com>
 <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com>
 <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com>
 <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net>
 <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net>
 <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com>
 <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com>
In-Reply-To: <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com>

--jBPviSa0jdrI2lwaCA4QUEIimiRGUvpJV
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi Ted, Bob,

On 10/03/17 22:53, Bob Hinden wrote:
> Ted,
>=20
>> On Mar 10, 2017, at 1:46 PM, Ted Lemon <mellon@fugue.com> wrote:
>>=20
>> The one thing I wish you'd mentioned in this blog, but did not, is
>> a point someone made earlier on this thread: that the fact that the
>> CIA needs to hack individual devices to bypass end-to-end
>> encryption means that what we are doing in promoting encryption is
>> effective and worth doing: rather than everybody's communications
>> being vulnerable, individuals must now be targeted.
>=20
> I think that=C3=A2=E2=82=AC=E2=84=A2s a good point.
>=20
> To expand what you said, these tools are for targeted attacks, not
> mass surveillance.=20

I don't think your optimistic conclusion here follows, for two
reasons. Firstly, we've seen that the adversary here is not
driven by economic concerns and will attack not just a weakest
link, but all possible targets they can afford given their very
very large budgets. That I think means that these kinds of attacker
will attempt both pervasive and targeted attacks, and the fact
that they attempt the latter does not mean that the don't try
both. Secondly, it may be that different kinds of attacker have
different kinds of targets/goals and that some attackers here
(such as the claimed source of these materials) are generally
more interested in individuals and not in populations. So again,
without further information, the interest in targeted attacks
does not imply a technical or practical inability to mount
pervasive monitoring attacks.

And while I do think that the actions that many people in the
Internet community and in the IETF have taken have probably
made pervasive monitoring harder and/or more costly, I do not
think that's really that relevant to this particular leak. In
this case, I think the much more interesting thing is that
this is yet another demonstration that attack code that is
intended to be used for attacks (as opposed to demonstration)
is in the end hugely counter-productive. (And immoral too IMO,
but I'd not claim that we all need to agree with that last;-)

> Encryption continues to be a strong protection
> against mass surveillance.

I totally agree encryption is a major tool in our armoury.
But that's kind of orthogonal to issues arising from this
incident I think.

Cheers,
S.

>=20
> Bob
>=20
>=20


--jBPviSa0jdrI2lwaCA4QUEIimiRGUvpJV--

--PqpT54mP6kWdQN2Q2LJUpcxuGO2kkuo93
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYw1qfAAoJEC88hzaAX42i948H/RbynLUSvitWQ1ag9RBbLwn4
ZbkbeqSa4H/HMrNqF7vq8TRWxMzbseC/0AZT7thFoLtWm4kh8wssMgrNn9uMu9mg
kbpp4XYZIl4GNv5tuwJq4zjwq0LlpaozkA4nGXyDl4M0xXdqN60kRIQG04YK089+
CLwxwLkmhnglG6e6ebdqDfmdBnbKXOL1Tu57Qr6aRo25hdgg+fZKLgcXYmYiUEg6
tJ8P9P8JL53nq7++cHlJgb1yHMyfKIgr/8KFNgZSh5FZQ7tYQXsF+v1CVuIryPDU
A+cJDqYPr0fxq0ndVTz/ySPlC1J9TFWglcsAlfRhsLFuBhVoX4LM/GwquZmyGdo=
=LASB
-----END PGP SIGNATURE-----

--PqpT54mP6kWdQN2Q2LJUpcxuGO2kkuo93--


From nobody Fri Mar 10 18:09:06 2017
Return-Path: <cowan@ccil.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 4590F129544 for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 18:09:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ccil-org.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exZz8nT9BHrM for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 18:09:03 -0800 (PST)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C60C4129531 for <ietf@ietf.org>; Fri, 10 Mar 2017 18:08:57 -0800 (PST)
Received: by mail-wr0-x232.google.com with SMTP id g10so74736853wrg.2 for <ietf@ietf.org>; Fri, 10 Mar 2017 18:08:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=09DcN8lr70VIKGmVSwBDfg4zFIJpN6+l9pPEM7I/2II=; b=AaNY1fO0w02ZlBqNKKJXurf6/N9ERh4CY8zf52eHGWar/akzNoxnYnPA7EIQDAXKLg IY7xNJyuUiXbRWmg6ZyTI5Z3WBiCP73RP0UvVHZmTDHpZV5S8sN2XiAvZv+cy0CR8m8V 7ZVozdONfvTr4Pr+TPx61LWk3/LkImM4DsPNsm1luehm2yfJAKh7ANBN58oqfSEVSYgA e5gbkL7tGLN3sm5LCGcsBhb94P5xewC8dwm9ktsioxADkFdBzG7rCpY5ZGlSBY0f9y+j alMowvOhGnLFoP9v5v5GQP25GSF1YyyGJ/oHqjVl7dt6WGRxIYRJZkUB28917imtsaNb hVbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=09DcN8lr70VIKGmVSwBDfg4zFIJpN6+l9pPEM7I/2II=; b=uL+DvrGyqkouXyjNpNqf2p84HhZW0sTfJgXGom3yuHrHfqAJyukna5Nmu6LmrqVyjG /Srh3NhYamy3n2+0dZ12JE8OEC0n0aWzZsOnMkPrXe7TI1E0r32qZCzOjdPNJgm9fBQk mgPxfTqTyIfl3pN8tou+DGkwK2CVyIsKnY47fbJBWDcJMKI30mK7uC5t0WAYgGk+8S0m bCBINHZRYLkMohrjsrUkyMduZ/ijoE01mnPa8Nt1acWsMG3JNdL9te2+XO5A3FWp3sku ozu+R/m9NlURlMUMyambwgVOZ+B1UpyX86hqtVTtjFaB8z3H/YCfjjcN+x0vjr9f5SXQ S++A==
X-Gm-Message-State: AMke39lBZdqsPlAmwr7gXq9v2ygbOX9lopJKNBibxdUWNRwQO/iUqyu5pV3OtsvEY/F3EkIlT9epR75cxwYoWtZs
X-Received: by 10.223.152.215 with SMTP id w81mr20250782wrb.151.1489198136300;  Fri, 10 Mar 2017 18:08:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.181.14 with HTTP; Fri, 10 Mar 2017 18:08:35 -0800 (PST)
In-Reply-To: <20170309055348.GL30306@kduck.kaduk.org>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org>
From: John Cowan <cowan@ccil.org>
Date: Fri, 10 Mar 2017 21:08:35 -0500
Message-ID: <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com>
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Benjamin Kaduk <kaduk@mit.edu>
Content-Type: multipart/alternative; boundary=001a113c36a6ea2d48054a6af5a1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z0NZEaUsNrYosZkdTEcSPnmub4M>
Cc: Julian Reschke <julian.reschke@gmx.de>, draft-ietf-jsonbis-rfc7159bis.all@ietf.org, secdir@ietf.org, ietf@ietf.org, "json@ietf.org" <json@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Mar 2017 02:09:04 -0000

--001a113c36a6ea2d48054a6af5a1
Content-Type: text/plain; charset=UTF-8

On Thu, Mar 9, 2017 at 12:53 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:

If that's what's supposed to happen, it should probably be more
> clear, yes.  (But aren't there texts that have valid interpretations
> in multiple encodings?)
>

Not if the content is well-formed JSON and the only possible encodings are
UTF-8, UTF-16, and UTF-32.  It suffices to examine the first four bytes of
the input.  If there are no NUL bytes in the first four bytes, it is UTF-8;
if there are two NUL bytes, it is UTF-16; if there are three NUL bytes, it
is UTF-32.  This works because the grammar requires the first character to
be in the ASCII repertoire, and the NUL *character* (U+0000) is not allowed
at all.

-- 
John Cowan          http://vrici.lojban.org/~cowan        cowan@ccil.org
I don't know half of you half as well as I should like, and I like less
than half of you half as well as you deserve.  --Bilbo

--001a113c36a6ea2d48054a6af5a1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Thu, Mar 9, 2017 at 12:53 AM, Benjamin Kaduk <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:kaduk@mit.edu" target=3D"_blank">kaduk@mit.edu</a>&gt;</span> =
wrote:</div><div class=3D"gmail_quote"><br><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex"><div id=3D"gmail-m_5855668069085138240:gk" class=3D"gmail=
-m_5855668069085138240a3s gmail-m_5855668069085138240aXjCH gmail-m_58556680=
69085138240m15ab1a1cc9d8b0d8">If that&#39;s what&#39;s supposed to happen, =
it should probably be more<br>
clear, yes.=C2=A0 (But aren&#39;t there texts that have valid interpretatio=
ns<br>
in multiple encodings?)<br></div></blockquote></div><br>Not if the content =
is well-formed JSON and the only possible encodings are UTF-8, UTF-16, and =
UTF-32.=C2=A0 It suffices to examine the first four bytes of the input.=C2=
=A0 If there are no NUL bytes=C2=A0in the first four bytes, it is UTF-8; if=
 there are two NUL bytes, it is UTF-16; if there are three NUL bytes, it is=
 UTF-32.=C2=A0 This works because the grammar requires the first character =
to be in the ASCII repertoire, and the NUL *character* (U+0000) is not allo=
wed at all.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_e=
xtra">--=C2=A0</div><div class=3D"gmail_extra"><div class=3D"gmail_extra">J=
ohn Cowan =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://vrici.lojban.=
org/~cowan">http://vrici.lojban.org/~cowan</a> =C2=A0 =C2=A0 =C2=A0 =C2=A0<=
a href=3D"mailto:cowan@ccil.org">cowan@ccil.org</a></div><div class=3D"gmai=
l_extra">I don&#39;t know half of you half as well as I should like, and I =
like less</div><div class=3D"gmail_extra">than half of you half as well as =
you deserve. =C2=A0--Bilbo</div><div class=3D"gmail_extra"><br></div></div>=
</div>

--001a113c36a6ea2d48054a6af5a1--


From nobody Fri Mar 10 18:11:24 2017
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 811C0129514 for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 18:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVxf4S6_9JeX for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 18:11:22 -0800 (PST)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82EA01294EE for <ietf@ietf.org>; Fri, 10 Mar 2017 18:11:22 -0800 (PST)
Received: by mail-yw0-x22b.google.com with SMTP id o4so34366948ywd.3 for <ietf@ietf.org>; Fri, 10 Mar 2017 18:11:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=wwt0k217s8RV/E6A9FqXo8SMrX+jxSzzczyUUbqj1NQ=; b=m5FiFCKYHuHwpImEGTN5F6dD49UZ5Q2XYLmq5LnYjOIAMo1ld5EE4ZGXF4jnChqLw7 UTJ2qQKXAwXAC5lTsyZiTVfYYdUDZQvZYEjB5Sr5YGqFzR2yg0IJpZOGEdEiF+XDo25A oD8S3RjKakQ0LYmW0EOO7XKVefwkFaPRTYNeu1qvVisceK0/EOvR9bxnYiKQRqdlYJiL iMGuFcOZ5WqYFWyPhpdul2BctY4FLJCdIcGLx5zGu0WFxQuscHFCG7lDvIeBsGIYBa9K XVXjnKCNWwXNMNm2IQiMt7ho1Z4VoAWkoDOjezk4Tl2x0eKvPU1TRYXQ3TArlCaDBPRQ 3aHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=wwt0k217s8RV/E6A9FqXo8SMrX+jxSzzczyUUbqj1NQ=; b=q8i4hPxpoNiDmeRjoDrz3W2vVyxdUhDyU+wFfpaju4dvvRDVHkoqGc/d8rXg2kyDcj eGwSuie+yeuo5iigFnLZbonEsouRWXiHtglje8tHrpSTPUs6sw1+BcALwgoF8SEC15ps xwtuWeh3Z1d/J18bvi4S2KYsR5XQxhEDg9996XIw477Ya83Kl52KoY6kLhD8ruj0fsPk 3Fde4GMsq74bmeOM+gNHebh/uJ90E0hIMI3rEegsGmoGPlR1/old34yUU8keW0v8+ZBG ESa2geiV3zTuhckIf6dEi06MMV7eEPgDsNS/9FQImWHR2wST/ukNmEnQHhdGSPSipop1 pv8g==
X-Gm-Message-State: AMke39kJifcH5mMg79zr/RPCnjh+HkH0jb7+s3Ym0yKEAB+TZvnYnf8OlCgm9m8k8yUnVxShy2v3f60WDWxUUA==
X-Received: by 10.129.97.214 with SMTP id v205mr9617591ywb.237.1489198281731;  Fri, 10 Mar 2017 18:11:21 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.19.20 with HTTP; Fri, 10 Mar 2017 18:11:21 -0800 (PST)
In-Reply-To: <BD825880-A4EC-4786-B4D8-9085EFE073C7@piuha.net>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com> <BD825880-A4EC-4786-B4D8-9085EFE073C7@piuha.net>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 10 Mar 2017 21:11:21 -0500
X-Google-Sender-Auth: OQQhBnMm0FWB6VaY58Zpq6Z5WcQ
Message-ID: <CAMm+LwioyDe9UVBLF-WxgCfFktx+nx0y=YQ_nKCqzDUrACTcZg@mail.gmail.com>
Subject: Re: The CIA mentions us
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a11490cd89536a4054a6afeb6
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pa1Y60Wi1SJed_U9sa7SgR3GwSQ>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Mar 2017 02:11:23 -0000

--001a11490cd89536a4054a6afeb6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

You also need to start off with

But Hilary's Emails!

On Fri, Mar 10, 2017 at 6:48 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> It is a good point. Thanks. I=E2=80=99ll consider making a revision. Tomo=
rrow.
>
> Jari
>
>

--001a11490cd89536a4054a6afeb6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">You=
 also need to start off with=C2=A0</div><div class=3D"gmail_default" style=
=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-s=
ize:small">But Hilary&#39;s Emails!</div></div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On Fri, Mar 10, 2017 at 6:48 PM, Jari Arkko <=
span dir=3D"ltr">&lt;<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_bla=
nk">jari.arkko@piuha.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">It is a good point. Thanks. I=E2=80=99ll consider making a revision. =
Tomorrow.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br></div>

--001a11490cd89536a4054a6afeb6--


From nobody Fri Mar 10 19:02:11 2017
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 D8455126BF7 for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 19:02:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECSWKWxZ3tfe for <ietf@ietfa.amsl.com>; Fri, 10 Mar 2017 19:02:08 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85519120726 for <ietf@ietf.org>; Fri, 10 Mar 2017 19:02:08 -0800 (PST)
Received: from mb.local (c-174-62-74-200.hsd1.ca.comcast.net [174.62.74.200]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v2B31x36039784 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Sat, 11 Mar 2017 03:02:00 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host c-174-62-74-200.hsd1.ca.comcast.net [174.62.74.200] claimed to be mb.local
Subject: Re: The CIA mentions us
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Bob Hinden <bob.hinden@gmail.com>, Ted Lemon <mellon@fugue.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com> <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <6baeee0f-4c2a-c02d-8fc4-f8c8b426aadd@bogus.com>
Date: Fri, 10 Mar 2017 19:01:53 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uDwiv2mWxaBNrOEN9DaH5s0oVwKQsgJ3f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FDANd29zhshfEWo9dl7JED5LVqk>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Mar 2017 03:02:10 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--uDwiv2mWxaBNrOEN9DaH5s0oVwKQsgJ3f
Content-Type: multipart/mixed; boundary="L7pcnJJV9KunSKPFEGMPsOJWQI5OBnS8R";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>,
 Bob Hinden <bob.hinden@gmail.com>, Ted Lemon <mellon@fugue.com>
Cc: IETF <ietf@ietf.org>
Message-ID: <6baeee0f-4c2a-c02d-8fc4-f8c8b426aadd@bogus.com>
Subject: Re: The CIA mentions us
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr>
 <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com>
 <20170307160840.duv7wwg5sm23nrek@nic.fr>
 <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com>
 <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com>
 <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com>
 <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com>
 <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net>
 <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net>
 <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com>
 <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com>
 <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie>
In-Reply-To: <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie>

--L7pcnJJV9KunSKPFEGMPsOJWQI5OBnS8R
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 3/10/17 6:02 PM, Stephen Farrell wrote:
>=20
> Hi Ted, Bob,
>=20
> On 10/03/17 22:53, Bob Hinden wrote:
>> Ted,
>>
>>> On Mar 10, 2017, at 1:46 PM, Ted Lemon <mellon@fugue.com> wrote:
>>>
>>> The one thing I wish you'd mentioned in this blog, but did not, is
>>> a point someone made earlier on this thread: that the fact that the
>>> CIA needs to hack individual devices to bypass end-to-end
>>> encryption means that what we are doing in promoting encryption is
>>> effective and worth doing: rather than everybody's communications
>>> being vulnerable, individuals must now be targeted.
>>
>> I think that=C3=A2=E2=82=AC=E2=84=A2s a good point.
>>
>> To expand what you said, these tools are for targeted attacks, not
>> mass surveillance.=20
>=20
> I don't think your optimistic conclusion here follows, for two
> reasons. Firstly, we've seen that the adversary here is not
> driven by economic concerns and will attack not just a weakest
> link, but all possible targets they can afford given their very
> very large budgets. That I think means that these kinds of attacker
> will attempt both pervasive and targeted attacks, and the fact
> that they attempt the latter does not mean that the don't try
> both.=20

Indiscriminately targeted attacks are clearly a persistent threat.
Attack tools that can leverage automation and large economies of scale
are part of the the basic oeuvre.  If your organization is large and
diffuse, the difference between indiscriminate attacks and targeted ones
may have no practical distinction .

> Secondly, it may be that different kinds of attacker have
> different kinds of targets/goals and that some attackers here
> (such as the claimed source of these materials) are generally
> more interested in individuals and not in populations. So again,
> without further information, the interest in targeted attacks
> does not imply a technical or practical inability to mount
> pervasive monitoring attacks.

low hanging fruit being what they are, if your goal is actually to
undermine the faith that efforts security focused tooling is actually
serving a useful purpose; then you seed leaks of your attack tooling or
someone else's because they're already  and sit back while your
adversaries have to ratchet up their own efforts.

> And while I do think that the actions that many people in the
> Internet community and in the IETF have taken have probably
> made pervasive monitoring harder and/or more costly, I do not
> think that's really that relevant to this particular leak. In
> this case, I think the much more interesting thing is that
> this is yet another demonstration that attack code that is
> intended to be used for attacks (as opposed to demonstration)
> is in the end hugely counter-productive. (And immoral too IMO,
> but I'd not claim that we all need to agree with that last;-)
>=20
>> Encryption continues to be a strong protection
>> against mass surveillance.
>=20
> I totally agree encryption is a major tool in our armoury.
> But that's kind of orthogonal to issues arising from this
> incident I think.
>=20
> Cheers,
> S.
>=20
>>
>> Bob
>>
>>
>=20



--L7pcnJJV9KunSKPFEGMPsOJWQI5OBnS8R--

--uDwiv2mWxaBNrOEN9DaH5s0oVwKQsgJ3f
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAljDaKIACgkQ8AA1q7Z/VrIbSwCdHxeoItTG15RyJOd9i6xBwMid
YzAAn210EIJWjmGRcYUAEuFV46p3JOke
=6Zvj
-----END PGP SIGNATURE-----

--uDwiv2mWxaBNrOEN9DaH5s0oVwKQsgJ3f--


From nobody Fri Mar 10 20:40:37 2017
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 A1C11129470; Fri, 10 Mar 2017 20:40:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mYneXSRGMVeP; Fri, 10 Mar 2017 20:40:34 -0800 (PST)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87FDC120727; Fri, 10 Mar 2017 20:40:31 -0800 (PST)
Received: by mail-it0-x22b.google.com with SMTP id w124so1863290itb.0; Fri, 10 Mar 2017 20:40:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=p0njDvUvVrGTvukYkjW8m8V1DR+dRJHFTaYneXpDl3Y=; b=VZ9Q7MJ+9geo5v1mnglIvAX+75Q1TVwbk8QXdNPfxGAVeBKxeXgXfl5TgH2PsFGYJ3 HWLJaA5o8Hv2hmL60tYaRYUXcwl5ZRuw1J7iwt2xzwoj9MsR6TTVKJYC1PG99dwDPG1R uZWcfo68A4PmA7dQfsXh+rh7aGF3itmDnT8U5YIuVtC1ERgX+OBtOjfMB5Iw/t41CeMI u0gQZttTLr+3/2V9JMq/mv+F0CDJbQ73tw77fZroQQazBKh3n8JoFor/DBOLR7DgIUfK wGfOSDqBtB8zs87P75zD6NpbTn/bd1mUPydxfUvC+WkPScSbQaJFfv549t1SWqKPQ9gg 4cwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=p0njDvUvVrGTvukYkjW8m8V1DR+dRJHFTaYneXpDl3Y=; b=X3dolf4GSkabCcjgAV6w1iDCRHJsfUWEEVdxiLqg3t38I51GroxpH50ceN6tEiJBVF dkK7+vWGOE7UVd7o68juLqqJGhwDdkxytXqR6cbKZ0T4+hu9slalpS7QpMyzizFurgiE OSYxK0xyR+8Mitkw6eKGErYLgMk8i4dyH08FQiZtKXxBCK7tnoywl1MfTQYg8VT2Jljk XhLTtorrh2uH+ufg4Sxbl8SSZ1IU5UxlfFR3uRif/gPDIvDjcsDFDg+QFuMTw11Sm12v eC2PBUpyW19Kgh1jIk5q5GkFk4510FPEy92qPT7I9Y3RjoAyZGTv0hJKW1tkW5aCtAZ8 6z3g==
X-Gm-Message-State: AFeK/H1qkWFWbi8gfJyRylAOwU0zHy3cr7v/VRs8u5qX8esHIwga8FgIGbP6LRYUvYI+V9DlLbGDZod+52GNbg==
X-Received: by 10.36.88.202 with SMTP id f193mr2082495itb.14.1489207230669; Fri, 10 Mar 2017 20:40:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.135.215 with HTTP; Fri, 10 Mar 2017 20:40:15 -0800 (PST)
In-Reply-To: <CAF4+nEGGnJkHC93UokZDEDO2St5SNE0mLvi6-oF3SYj2Lei_BA@mail.gmail.com>
References: <148423706509.29345.14522113109638417885.idtracker@ietfa.amsl.com> <CAF4+nEEVpXbWiToCq8oK1QFnpL+m8Q7=yuKdOHv4Og98NB6jhg@mail.gmail.com> <CAFgnS4V+yHnpHo0-5tKLo8yDTc7_hgDa5-DFdHwLe4mPtHzDWw@mail.gmail.com> <CAF4+nEGGnJkHC93UokZDEDO2St5SNE0mLvi6-oF3SYj2Lei_BA@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 10 Mar 2017 23:40:15 -0500
Message-ID: <CAF4+nEExM7ob+n+6OZsUEW8azwbFK7U6RF5NW68NHCi6rAhdNA@mail.gmail.com>
Subject: Re: Review of draft-ietf-trill-rfc6439bis-04
To: Dan Romascanu <dromasca@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U9WtjGTybpTvsFSNysqs19zA3ic>
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-trill-rfc6439bis.all@ietf.org, IETF Discussion <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Mar 2017 04:40:35 -0000

Hi Dan,

Could you look at the recently posted version -05 to see if this
resolves your comments?

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


On Wed, Jan 18, 2017 at 2:16 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> Hi Dan,
>
> On Tue, Jan 17, 2017 at 3:45 AM, Dan Romascanu <dromasca@gmail.com> wrote:
>> Hi Donald,
>>
>> Thank you for your answer and explanations. They make sense to me, but I
>> still beleive that the document may benefit if some edits are being done to
>> clarify what may be the obvious for the people who know all details and
>> history, but not for the other users of the document in the future -
>> implementers and operators.
>
> Sure, I agree that it would benefit for the addition of some text here
> and there./
>
>> Specifically:
>>
>>> I am not aware of any case where this draft replaces a TLV in the
>> sense of requiring use of a new TLV.  It does provide some new TLVs
>> and procedures that are believed to be superior to or useful additions
>> to previous ones. But I am not aware of any case where it "obsoletes"
>> previous provisions in the sense of prohibiting their use.
>>
>> The header of the document includes Obsoletes 6439. If part of the content
>> of 6439 remains valid this needs to be clarified, If some superior TLVs and
>> procedures are introduced there is a need to explain what will happen with
>> the previous ones. Should they be implemented? deployed? activated?
>
> OK. Stating that essentially all of RFC 6439 is incorporated and
> outlining what parts of the new draft are optional improvements over
> which part of RFC 6439, etc. would probably be a good addition.
>
>>> I don't know that much is really required to be said about
>> "transition" when you specify an optional optimization. Since it is
>> optional, by implication the implementer is free to use it or not and
>> things will work either way. This could be stated explicitly in those
>> cases.
>>
>> If I understand what you say, the new features are optional (although the
>> status of the document is Proposed Standard), they can or cannot be
>> implemented (one, the other, both?) and the network will  still work. Yes, I
>> suggest to explicitly state this).
>
> OK.
>
>>> RFC 6325, the base TRILL protocol RFC, says TRILL switches (RBridges)
>> SHOULD support SNMPv3 and there are TRILL MIB specifications in RFCs
>> 6850 and 7784. However, there are also YANG modules underway in
>> draft-ietf-trill-yang, draft-ietf-trill-yang-oam, and
>> draft-ietf-trill-yang-pm.
>>
>>> It does not seem best for this rfc6439bis draft to change the
>> implementation requirement level for SNMP or NETCONF for TRILL. If that
>> were to be done, it seems like something more appropriate for the base
>> TRILL YANG draft (draft-ietf-trill-yang-*) to do.
>>
>> If I was an implementer of TRILL, or an operator considering to deploy
>> TRILL, I would have a hard time trying to understand what to implement and
>> what to deploy as management interfaces. Maybe this is not the place but I
>> believe that there need to be some documentation on this respect.
>
> OK. I think it would be reasonable to say something about the current
> implementation requirement level of SNMPv3 and to say that YANG
> modules are under development, so implementers will know more about
> what is going on.
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
>> Thanks and Regards,
>> Dan
>>
>>
>> On Tue, Jan 17, 2017 at 3:48 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:
>>>
>>> Hi Dan,
>>>
>>> Thanks for your review. As per my further response below, while the
>>> draft could perhaps use some clarifying additions related to
>>> operations, I do not believe it is as bad as you say.
>>>
>>> On Thu, Jan 12, 2017 at 11:04 AM, Dan Romascanu <dromasca@gmail.com>
>>> wrote:
>>> >
>>> > Reviewer: Dan Romascanu
>>> > Review result: Has Issues
>>> >
>>> > I have reviewed this document as part of the Operational
>>> > directorate's ongoing effort to review all IETF documents being
>>> > processed by the IESG.  These comments were written with the intent
>>> > of improving the operational aspects of the IETF drafts. Comments
>>> > that are not addressed in last call may be included in AD reviews
>>> > during the IESG review.  Document editors and WG chairs should treat
>>> > these comments just like any other last call comments.
>>> >
>>> > This document clarifies and updates the TRILL Appointed
>>> >  Forwarder mechanism. It updates RFC 6325, updates RFC 7177, and
>>> >  obsoletes RFC 6439.
>>> >
>>> > It's a complex document which requires extra reading to understand
>>> > the context and the interraction with other RFCs. I believe that
>>> > from an OPS-DIR perspective there are issues that need to be
>>> > discussed before the document can be approved.
>>> >
>>> > The main issues with the document in its current form are:
>>> >
>>> > 1. The document makes consistent changes in the way TRILL
>>> > operates. It replaces TLVs and procedures, define new ones,
>>> > obsoletes previous mechanisms that define VLAN mapping, and
>>>
>>> I am not aware of any case where this draft replaces a TLV in the
>>> sense of requiring use of a new TLV.  It does provide some new TLVs
>>> and procedures that are believed to be superior to or useful additions
>>> to previous ones. But I am not aware of any case where it "obsoletes"
>>> previous provisions in the sense of prohibiting their use.
>>>
>>> > incorporates updated material from other RFCs. There is however no
>>> > indication in the text about the transition between existing
>>> > deployed versions of TRILL based on RFC 6439 and related protocols
>>> > with the current updated mechanisms. Are these backward compatible?
>>>
>>> I don't know that much is really required to be said about
>>> "transition" when you specify an optional optimization. Since it is
>>> optional, by implication the implementer is free to use it or not and
>>> things will work either way. This could be stated explicitly in those
>>> cases.
>>>
>>> Much of the material in this draft comes from RFC 6439 or the parts of
>>> RFC 7177 that updated RFC 6439. Most of the new material is optional
>>> improved behaviors.
>>>
>>> The only mandatory new behavior is the mandatory support of the link
>>> local E-L1CS flooding scope [RFC7357] specified in Section 8. There is
>>> material in this draft covering backwards compatibility for this new
>>> mandatory behavior.  Section 8 already explains how to determine
>>> whether or not all TRILL switches on a link support E-L1CS flooding
>>> scope. The only use of E-L1CS flooding scope in this draft is as part
>>> of a mechanism for the DRB (Designated RBridge (TRILL switch)) to
>>> advertise Forwarder Appointments and, as stated in Section 2.1 (see
>>> paragraph at the bottom of page 8 in draft -04), if any RBridge on the
>>> link does not support E-L1CS, then the DRB MUST fall back to
>>> advertising those appointments in Hellos. Section 8, which mandates
>>> support of E-L1CS, also requires that any use of E-L1CS specified in
>>> the future must provide for backward compatibility.
>>>
>>> > Do they need a simultaneous upgrade of the whole network?
>>>
>>> No.
>>>
>>> > 2. The document lacks a section or even minimal text concerning
>>> > operational and manageability considerations.  There are several
>>>
>>> Such a section can be added but there is not much to say. For example,
>>> as explained below, there is very little specified in this document to
>>> configure.
>>>
>>> > mentions in the text concerning network managers or operator
>>> > actions, but there is no indication or reference to what management
>>> > protocols and data models are to be used for configuration,
>>>
>>> RFC 6325, the base TRILL protocol RFC, says TRILL switches (RBridges)
>>> SHOULD support SNMPv3 and there are TRILL MIB specifications in RFCs
>>> 6850 and 7784. However, there are also YANG modules underway in
>>> draft-ietf-trill-yang, draft-ietf-trill-yang-oam, and
>>> draft-ietf-trill-yang-pm.
>>>
>>> It does not seem best for this rfc6439bis draft to change the
>>> implementation requirement level for SNMP or NETCONF for TRILL. If that
>>> were to be done, it seems like something more appropriate for the base
>>> TRILL YANG draft (draft-ietf-trill-yang-*) to do.
>>>
>>> > retrieval of operational status information, or alerts. I believe
>>> > that these need to be added explicitly or by reference.
>>>
>>> Reviewing the significant protocol additions in this draft at a high
>>> level:
>>>
>>> - There is significant material about the various ways the Designated
>>>   RBridge on a link can announce who it is selecting as the Appointed
>>>   Forwarder on the link for various VLANs. The election of the
>>>   Designated RBridge depends on a configurable priority but that
>>>   election is unchanged from RFC 7177 and in fact is identical to the
>>>   election of the designated router on any IS-IS link. The decision on
>>>   which RBridges to appointer as forwarder for which VLAN is out of
>>>   scope. I don't see that there is anything to configure here, other
>>>   than RBridge priority to be DRB, which is already specified in other
>>>   RFCs.
>>>
>>> - There are some optional optimizations to the inhibition mechanism.
>>>   The inhibition mechanism is necessary for loop safety but any
>>>   RBridge can use or not use any of these optimizations, as they
>>>   choose, and things will work fine.
>>>
>>> - Port Shutdown message: There are two new configuration parameters
>>>   here, namely how many copies of the Port Shutdown message to send
>>>   and at what interval. These are listed, along with units and default
>>>   value in Section 6.6.
>>>
>>> - FGL-VLAN mapping consistency check: As specified in RFC 7172, in a
>>>   TRILL campus supporting Fine Grained Labels (FGL), the VLAN of a
>>>   native frame can be mapped to an FGL on ingress and an FGL is mapped
>>>   to a VLAN on egress. This draft makes no changes to that mechanism.
>>>   It merely provides that an RBridge performing such mapping can
>>>   optionally advertise the mapping it is performing at a port to other
>>>   RBridges with ports on the same link which can then check it for
>>>   consistency with any mapping they are performing. It is recommended
>>>   that the network operator be alerted to such inconsistency and there
>>>   is a configurable parameter for how long the inconsistency needs to
>>>   exist before such alert. Is it your position that some specific
>>>   protocol mechanism must be specified by which the network operator
>>>   is alerted?
>>>
>>> Thanks,
>>> Donald
>>> ===============================
>>>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>>  155 Beaver Street, Milford, MA 01757 USA
>>>  d3e3e3@gmail.com
>>
>>


From nobody Fri Mar 10 22:12:55 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60964129469; Fri, 10 Mar 2017 22:12:53 -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=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rnqyjii5-GiD; Fri, 10 Mar 2017 22:12:52 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 065CD128BA2; Fri, 10 Mar 2017 22:12:51 -0800 (PST)
Received: from [192.168.178.20] ([93.217.121.40]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LhNwC-1cQSw22LQW-00maWB; Sat, 11 Mar 2017 07:12:46 +0100
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: John Cowan <cowan@ccil.org>, Benjamin Kaduk <kaduk@mit.edu>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de>
Date: Sat, 11 Mar 2017 07:12:45 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:LCf1AaG3eRDHEgm3RLe10joYTBzTE+NJvIdrjH8yV4V+orhcr+k BhzWYehxmeNAzrC4qfYOiu1WDRVldvGFCKvMf2NuUZMz28aYJ1E/4W1SFUOEdLQsgW4qIkF tzCy6LzoWLe9wXy4TEQOjHTKu1MqS1U6etzGLjI25S8lAVPOCMHgCWUMUnQgIeA+F9exGIW UEvzgwtXFWTfeWd24so0Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:japFPxPXC5Q=:N+IIWiOcKYz/pHLBgRumPI 6qVqJqSP5KVQIw7VeyNZIn+ZE1QXz4GDRT86zqMl9dsv/WBoYlFfvhUiOEMTGzIj4ST31HEFB LYrSlt4x939UQuKFHlGbdmmYzgUMQQRvmeqh966bEX0Pooq7bXB2rzzmTd6x/KmMro07V6NQJ xNAkaGbMQWOVuqLpEFHJIPj8VDezsryKVQ2Yf7+bARo/l1ehz7G5lbZBjo/LKdY3CCB9GDKt3 wFanGcqyvLUYpcc0Whqc73t058dvQMcq8OnM/tbxrL0LzOeQyJG2j2Zgt/HykkT5kTxFku0Sf vPDM6vcoGvskLn2IxNQoscQJ5IkdXccq2SUkUzn9DZUGRu88lwuui45j7dnKVfrbDgHU47hoq WEB6qE0AeDFr7+nMI7q3csnEcZVeyl7Iq+dKLeOzyO7W25C7HAWAJFaIMsHT23w6DuaneBzDa OyYrTwcgNqV354e1W0g1sv652QoJ2cqJgKRu+3UrbEKaUvL6ue3uHpntbPRuPyIgmNXF6ZJCD Qk0gMqHoVcoC8mv/tpp59a8wSn9gx2UcDKFDWJEkVKAMMjgolIUS6SSX+OT6JJOTt865mpIDU gcGTtnHDRq17MFVHDFxb/uqgz0sdTNYonmzRC0PjEy455eBmWVJDqPbZTMX5aG63AOt/sBC/t 1ED23UfR9XkEOmMlY4GXqCd/uENPk3EuhBWoX83Q7tM6xZCBuxJiTqCIsEzx1B1gjS9WWWX8a ZQyWNbTrQ35BGmsCP6zsH+gQ0rQszCTH3B8GYlwEdQQwmSYb+/0QqMgROXYJuK7PZYVBfMxDb vbPWOPq
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fDUoBtgDUXYprxWC3x7mfGtfu-w>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, secdir@ietf.org, ietf@ietf.org, "json@ietf.org" <json@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Mar 2017 06:12:53 -0000

On 2017-03-11 03:08, John Cowan wrote:
>
> On Thu, Mar 9, 2017 at 12:53 AM, Benjamin Kaduk <kaduk@mit.edu
> <mailto:kaduk@mit.edu>> wrote:
>
>     If that's what's supposed to happen, it should probably be more
>     clear, yes.  (But aren't there texts that have valid interpretations
>     in multiple encodings?)
>
>
> Not if the content is well-formed JSON and the only possible encodings
> are UTF-8, UTF-16, and UTF-32.  It suffices to examine the first four
> bytes of the input.  If there are no NUL bytes in the first four bytes,
> it is UTF-8; if there are two NUL bytes, it is UTF-16; if there are
> three NUL bytes, it is UTF-32.  This works because the grammar requires
> the first character to be in the ASCII repertoire, and the NUL
> *character* (U+0000) is not allowed at all.

Good explanation. Maybe the spec should include it.

Best regards, Julian


From nobody Fri Mar 10 23:46:26 2017
Return-Path: <dromasca@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 22FE91293FD; Fri, 10 Mar 2017 23:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5b_1SChq73Cn; Fri, 10 Mar 2017 23:46:15 -0800 (PST)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D9751279EB; Fri, 10 Mar 2017 23:46:15 -0800 (PST)
Received: by mail-qt0-x236.google.com with SMTP id i34so4514097qtc.0; Fri, 10 Mar 2017 23:46:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ICJ+EcScPd72SuZ8IkMuzT22IW52Gv3IHbqRl7Xr6Rs=; b=Tqs8qUKigkeQkmJuFGvNX1kcsbh2cQKmEzOQcspuqGrlaDAN9LMUY94vygdUJ2j5Is /fRpd6tzOEXeL29ZI1xEQ/mU0+D7VIJS8KRzPDdud8pMouAIkoEAgvvjQ6l6zpU6VoMP d++ILsuvPy0p3JDWdbaSsjtalmufKtyPrpDaXeG4f6guQNjdQ1zB53wM6kS1B8q64G0P CTpVlsSCpkE0EIqiRE7RDlRc+8Owrd8Wr9FCWuSiqOAuag3vFdhvYnMI4VQ7TT7aAY3+ DURZj+jiPNoxIerILsR8Lo/rCZArxPqYTo4b0nM6hfeQySkB+of6LDukuOSZBV3Rm7aU XFwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ICJ+EcScPd72SuZ8IkMuzT22IW52Gv3IHbqRl7Xr6Rs=; b=hmSVo5sJfPS6oQjv0wUX+I46MFj3X1Lk1Uvxv3hoDLOtgT8OykygZpsezW5rIXPxPF nr611gPscPJh6djEF0qnh4Jo2Jzw52lTDKKke93f+Q12OoyRnJzVI3CROJf69XBIhbOx gP5lZIzNWbnvaz31XnbsZlYMagYRdkzDCn4dT8KQVnGfBPeLAiqdbIVueu+AaWE8nJkP WKr4oBgRWC5yXwS1Nv6VRgTNqZKKjuhQqbzuUs+yKh2heqgX0WIt8HYN63xRLUKn5aH1 MrprhUQUXJd3M/dLlzI/DliFTgFjdDCepV68uH93doMUlMSkj4tIKJB3dBA5UGlC/WA+ 4fng==
X-Gm-Message-State: AMke39n70ra3dQJ0ajVgQirsMgtVODdVammrnWyv9NnO7K5GsuZCRtlVNqu59xnGLoCnddKXdkWYeIZfcOveHQ==
X-Received: by 10.200.40.210 with SMTP id j18mr25282067qtj.272.1489218374429;  Fri, 10 Mar 2017 23:46:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.41.170 with HTTP; Fri, 10 Mar 2017 23:46:13 -0800 (PST)
In-Reply-To: <CAF4+nEExM7ob+n+6OZsUEW8azwbFK7U6RF5NW68NHCi6rAhdNA@mail.gmail.com>
References: <148423706509.29345.14522113109638417885.idtracker@ietfa.amsl.com> <CAF4+nEEVpXbWiToCq8oK1QFnpL+m8Q7=yuKdOHv4Og98NB6jhg@mail.gmail.com> <CAFgnS4V+yHnpHo0-5tKLo8yDTc7_hgDa5-DFdHwLe4mPtHzDWw@mail.gmail.com> <CAF4+nEGGnJkHC93UokZDEDO2St5SNE0mLvi6-oF3SYj2Lei_BA@mail.gmail.com> <CAF4+nEExM7ob+n+6OZsUEW8azwbFK7U6RF5NW68NHCi6rAhdNA@mail.gmail.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Sat, 11 Mar 2017 18:16:13 +1030
Message-ID: <CAFgnS4UHAwp+SF4Sn0CAzmifSpToV7oXHcjTiz0BJVK2xfEq_w@mail.gmail.com>
Subject: Re: Review of draft-ietf-trill-rfc6439bis-04
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary=001a11405b4e337449054a6fac2d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uECBWYSX-0FgF-vAgMeMArEu4eQ>
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-trill-rfc6439bis.all@ietf.org, IETF Discussion <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Mar 2017 07:46:18 -0000

--001a11405b4e337449054a6fac2d
Content-Type: text/plain; charset=UTF-8

Looks good now. Thanks for addressing my concerns.

Dan



On Sat, Mar 11, 2017 at 3:10 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi Dan,
>
> Could you look at the recently posted version -05 to see if this
> resolves your comments?
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
>
> On Wed, Jan 18, 2017 at 2:16 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> > Hi Dan,
> >
> > On Tue, Jan 17, 2017 at 3:45 AM, Dan Romascanu <dromasca@gmail.com>
> wrote:
> >> Hi Donald,
> >>
> >> Thank you for your answer and explanations. They make sense to me, but I
> >> still beleive that the document may benefit if some edits are being
> done to
> >> clarify what may be the obvious for the people who know all details and
> >> history, but not for the other users of the document in the future -
> >> implementers and operators.
> >
> > Sure, I agree that it would benefit for the addition of some text here
> > and there./
> >
> >> Specifically:
> >>
> >>> I am not aware of any case where this draft replaces a TLV in the
> >> sense of requiring use of a new TLV.  It does provide some new TLVs
> >> and procedures that are believed to be superior to or useful additions
> >> to previous ones. But I am not aware of any case where it "obsoletes"
> >> previous provisions in the sense of prohibiting their use.
> >>
> >> The header of the document includes Obsoletes 6439. If part of the
> content
> >> of 6439 remains valid this needs to be clarified, If some superior TLVs
> and
> >> procedures are introduced there is a need to explain what will happen
> with
> >> the previous ones. Should they be implemented? deployed? activated?
> >
> > OK. Stating that essentially all of RFC 6439 is incorporated and
> > outlining what parts of the new draft are optional improvements over
> > which part of RFC 6439, etc. would probably be a good addition.
> >
> >>> I don't know that much is really required to be said about
> >> "transition" when you specify an optional optimization. Since it is
> >> optional, by implication the implementer is free to use it or not and
> >> things will work either way. This could be stated explicitly in those
> >> cases.
> >>
> >> If I understand what you say, the new features are optional (although
> the
> >> status of the document is Proposed Standard), they can or cannot be
> >> implemented (one, the other, both?) and the network will  still work.
> Yes, I
> >> suggest to explicitly state this).
> >
> > OK.
> >
> >>> RFC 6325, the base TRILL protocol RFC, says TRILL switches (RBridges)
> >> SHOULD support SNMPv3 and there are TRILL MIB specifications in RFCs
> >> 6850 and 7784. However, there are also YANG modules underway in
> >> draft-ietf-trill-yang, draft-ietf-trill-yang-oam, and
> >> draft-ietf-trill-yang-pm.
> >>
> >>> It does not seem best for this rfc6439bis draft to change the
> >> implementation requirement level for SNMP or NETCONF for TRILL. If that
> >> were to be done, it seems like something more appropriate for the base
> >> TRILL YANG draft (draft-ietf-trill-yang-*) to do.
> >>
> >> If I was an implementer of TRILL, or an operator considering to deploy
> >> TRILL, I would have a hard time trying to understand what to implement
> and
> >> what to deploy as management interfaces. Maybe this is not the place
> but I
> >> believe that there need to be some documentation on this respect.
> >
> > OK. I think it would be reasonable to say something about the current
> > implementation requirement level of SNMPv3 and to say that YANG
> > modules are under development, so implementers will know more about
> > what is going on.
> >
> > Thanks,
> > Donald
> > ===============================
> >  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> >  155 Beaver Street, Milford, MA 01757 USA
> >  d3e3e3@gmail.com
> >
> >> Thanks and Regards,
> >> Dan
> >>
> >>
> >> On Tue, Jan 17, 2017 at 3:48 AM, Donald Eastlake <d3e3e3@gmail.com>
> wrote:
> >>>
> >>> Hi Dan,
> >>>
> >>> Thanks for your review. As per my further response below, while the
> >>> draft could perhaps use some clarifying additions related to
> >>> operations, I do not believe it is as bad as you say.
> >>>
> >>> On Thu, Jan 12, 2017 at 11:04 AM, Dan Romascanu <dromasca@gmail.com>
> >>> wrote:
> >>> >
> >>> > Reviewer: Dan Romascanu
> >>> > Review result: Has Issues
> >>> >
> >>> > I have reviewed this document as part of the Operational
> >>> > directorate's ongoing effort to review all IETF documents being
> >>> > processed by the IESG.  These comments were written with the intent
> >>> > of improving the operational aspects of the IETF drafts. Comments
> >>> > that are not addressed in last call may be included in AD reviews
> >>> > during the IESG review.  Document editors and WG chairs should treat
> >>> > these comments just like any other last call comments.
> >>> >
> >>> > This document clarifies and updates the TRILL Appointed
> >>> >  Forwarder mechanism. It updates RFC 6325, updates RFC 7177, and
> >>> >  obsoletes RFC 6439.
> >>> >
> >>> > It's a complex document which requires extra reading to understand
> >>> > the context and the interraction with other RFCs. I believe that
> >>> > from an OPS-DIR perspective there are issues that need to be
> >>> > discussed before the document can be approved.
> >>> >
> >>> > The main issues with the document in its current form are:
> >>> >
> >>> > 1. The document makes consistent changes in the way TRILL
> >>> > operates. It replaces TLVs and procedures, define new ones,
> >>> > obsoletes previous mechanisms that define VLAN mapping, and
> >>>
> >>> I am not aware of any case where this draft replaces a TLV in the
> >>> sense of requiring use of a new TLV.  It does provide some new TLVs
> >>> and procedures that are believed to be superior to or useful additions
> >>> to previous ones. But I am not aware of any case where it "obsoletes"
> >>> previous provisions in the sense of prohibiting their use.
> >>>
> >>> > incorporates updated material from other RFCs. There is however no
> >>> > indication in the text about the transition between existing
> >>> > deployed versions of TRILL based on RFC 6439 and related protocols
> >>> > with the current updated mechanisms. Are these backward compatible?
> >>>
> >>> I don't know that much is really required to be said about
> >>> "transition" when you specify an optional optimization. Since it is
> >>> optional, by implication the implementer is free to use it or not and
> >>> things will work either way. This could be stated explicitly in those
> >>> cases.
> >>>
> >>> Much of the material in this draft comes from RFC 6439 or the parts of
> >>> RFC 7177 that updated RFC 6439. Most of the new material is optional
> >>> improved behaviors.
> >>>
> >>> The only mandatory new behavior is the mandatory support of the link
> >>> local E-L1CS flooding scope [RFC7357] specified in Section 8. There is
> >>> material in this draft covering backwards compatibility for this new
> >>> mandatory behavior.  Section 8 already explains how to determine
> >>> whether or not all TRILL switches on a link support E-L1CS flooding
> >>> scope. The only use of E-L1CS flooding scope in this draft is as part
> >>> of a mechanism for the DRB (Designated RBridge (TRILL switch)) to
> >>> advertise Forwarder Appointments and, as stated in Section 2.1 (see
> >>> paragraph at the bottom of page 8 in draft -04), if any RBridge on the
> >>> link does not support E-L1CS, then the DRB MUST fall back to
> >>> advertising those appointments in Hellos. Section 8, which mandates
> >>> support of E-L1CS, also requires that any use of E-L1CS specified in
> >>> the future must provide for backward compatibility.
> >>>
> >>> > Do they need a simultaneous upgrade of the whole network?
> >>>
> >>> No.
> >>>
> >>> > 2. The document lacks a section or even minimal text concerning
> >>> > operational and manageability considerations.  There are several
> >>>
> >>> Such a section can be added but there is not much to say. For example,
> >>> as explained below, there is very little specified in this document to
> >>> configure.
> >>>
> >>> > mentions in the text concerning network managers or operator
> >>> > actions, but there is no indication or reference to what management
> >>> > protocols and data models are to be used for configuration,
> >>>
> >>> RFC 6325, the base TRILL protocol RFC, says TRILL switches (RBridges)
> >>> SHOULD support SNMPv3 and there are TRILL MIB specifications in RFCs
> >>> 6850 and 7784. However, there are also YANG modules underway in
> >>> draft-ietf-trill-yang, draft-ietf-trill-yang-oam, and
> >>> draft-ietf-trill-yang-pm.
> >>>
> >>> It does not seem best for this rfc6439bis draft to change the
> >>> implementation requirement level for SNMP or NETCONF for TRILL. If that
> >>> were to be done, it seems like something more appropriate for the base
> >>> TRILL YANG draft (draft-ietf-trill-yang-*) to do.
> >>>
> >>> > retrieval of operational status information, or alerts. I believe
> >>> > that these need to be added explicitly or by reference.
> >>>
> >>> Reviewing the significant protocol additions in this draft at a high
> >>> level:
> >>>
> >>> - There is significant material about the various ways the Designated
> >>>   RBridge on a link can announce who it is selecting as the Appointed
> >>>   Forwarder on the link for various VLANs. The election of the
> >>>   Designated RBridge depends on a configurable priority but that
> >>>   election is unchanged from RFC 7177 and in fact is identical to the
> >>>   election of the designated router on any IS-IS link. The decision on
> >>>   which RBridges to appointer as forwarder for which VLAN is out of
> >>>   scope. I don't see that there is anything to configure here, other
> >>>   than RBridge priority to be DRB, which is already specified in other
> >>>   RFCs.
> >>>
> >>> - There are some optional optimizations to the inhibition mechanism.
> >>>   The inhibition mechanism is necessary for loop safety but any
> >>>   RBridge can use or not use any of these optimizations, as they
> >>>   choose, and things will work fine.
> >>>
> >>> - Port Shutdown message: There are two new configuration parameters
> >>>   here, namely how many copies of the Port Shutdown message to send
> >>>   and at what interval. These are listed, along with units and default
> >>>   value in Section 6.6.
> >>>
> >>> - FGL-VLAN mapping consistency check: As specified in RFC 7172, in a
> >>>   TRILL campus supporting Fine Grained Labels (FGL), the VLAN of a
> >>>   native frame can be mapped to an FGL on ingress and an FGL is mapped
> >>>   to a VLAN on egress. This draft makes no changes to that mechanism.
> >>>   It merely provides that an RBridge performing such mapping can
> >>>   optionally advertise the mapping it is performing at a port to other
> >>>   RBridges with ports on the same link which can then check it for
> >>>   consistency with any mapping they are performing. It is recommended
> >>>   that the network operator be alerted to such inconsistency and there
> >>>   is a configurable parameter for how long the inconsistency needs to
> >>>   exist before such alert. Is it your position that some specific
> >>>   protocol mechanism must be specified by which the network operator
> >>>   is alerted?
> >>>
> >>> Thanks,
> >>> Donald
> >>> ===============================
> >>>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> >>>  155 Beaver Street, Milford, MA 01757 USA
> >>>  d3e3e3@gmail.com
> >>
> >>
>

--001a11405b4e337449054a6fac2d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Looks good now. Thanks for addressing my concern=
s.<br><br></div>Dan<br><br></div>=C2=A0<br></div><div class=3D"gmail_extra"=
><br><div class=3D"gmail_quote">On Sat, Mar 11, 2017 at 3:10 PM, Donald Eas=
tlake <span dir=3D"ltr">&lt;<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_=
blank">d3e3e3@gmail.com</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">Hi Dan,<br>
<br>
Could you look at the recently posted version -05 to see if this<br>
resolves your comments?<br>
<span class=3D"im HOEnZb"><br>
Thanks,<br>
Donald<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<wbr>=3D<br>
=C2=A0Donald E. Eastlake 3rd=C2=A0 =C2=A0<a href=3D"tel:%2B1-508-333-2270" =
value=3D"+15083332270">+1-508-333-2270</a> (cell)<br>
=C2=A0155 Beaver Street, Milford, MA 01757 USA<br>
=C2=A0<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a><br>
<br>
<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">On Wed, Jan 18, 2017 at 2:16=
 PM, Donald Eastlake &lt;<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.c=
om</a>&gt; wrote:<br>
&gt; Hi Dan,<br>
&gt;<br>
&gt; On Tue, Jan 17, 2017 at 3:45 AM, Dan Romascanu &lt;<a href=3D"mailto:d=
romasca@gmail.com">dromasca@gmail.com</a>&gt; wrote:<br>
&gt;&gt; Hi Donald,<br>
&gt;&gt;<br>
&gt;&gt; Thank you for your answer and explanations. They make sense to me,=
 but I<br>
&gt;&gt; still beleive that the document may benefit if some edits are bein=
g done to<br>
&gt;&gt; clarify what may be the obvious for the people who know all detail=
s and<br>
&gt;&gt; history, but not for the other users of the document in the future=
 -<br>
&gt;&gt; implementers and operators.<br>
&gt;<br>
&gt; Sure, I agree that it would benefit for the addition of some text here=
<br>
&gt; and there./<br>
&gt;<br>
&gt;&gt; Specifically:<br>
&gt;&gt;<br>
&gt;&gt;&gt; I am not aware of any case where this draft replaces a TLV in =
the<br>
&gt;&gt; sense of requiring use of a new TLV.=C2=A0 It does provide some ne=
w TLVs<br>
&gt;&gt; and procedures that are believed to be superior to or useful addit=
ions<br>
&gt;&gt; to previous ones. But I am not aware of any case where it &quot;ob=
soletes&quot;<br>
&gt;&gt; previous provisions in the sense of prohibiting their use.<br>
&gt;&gt;<br>
&gt;&gt; The header of the document includes Obsoletes 6439. If part of the=
 content<br>
&gt;&gt; of 6439 remains valid this needs to be clarified, If some superior=
 TLVs and<br>
&gt;&gt; procedures are introduced there is a need to explain what will hap=
pen with<br>
&gt;&gt; the previous ones. Should they be implemented? deployed? activated=
?<br>
&gt;<br>
&gt; OK. Stating that essentially all of RFC 6439 is incorporated and<br>
&gt; outlining what parts of the new draft are optional improvements over<b=
r>
&gt; which part of RFC 6439, etc. would probably be a good addition.<br>
&gt;<br>
&gt;&gt;&gt; I don&#39;t know that much is really required to be said about=
<br>
&gt;&gt; &quot;transition&quot; when you specify an optional optimization. =
Since it is<br>
&gt;&gt; optional, by implication the implementer is free to use it or not =
and<br>
&gt;&gt; things will work either way. This could be stated explicitly in th=
ose<br>
&gt;&gt; cases.<br>
&gt;&gt;<br>
&gt;&gt; If I understand what you say, the new features are optional (altho=
ugh the<br>
&gt;&gt; status of the document is Proposed Standard), they can or cannot b=
e<br>
&gt;&gt; implemented (one, the other, both?) and the network will=C2=A0 sti=
ll work. Yes, I<br>
&gt;&gt; suggest to explicitly state this).<br>
&gt;<br>
&gt; OK.<br>
&gt;<br>
&gt;&gt;&gt; RFC 6325, the base TRILL protocol RFC, says TRILL switches (RB=
ridges)<br>
&gt;&gt; SHOULD support SNMPv3 and there are TRILL MIB specifications in RF=
Cs<br>
&gt;&gt; 6850 and 7784. However, there are also YANG modules underway in<br=
>
&gt;&gt; draft-ietf-trill-yang, draft-ietf-trill-yang-oam, and<br>
&gt;&gt; draft-ietf-trill-yang-pm.<br>
&gt;&gt;<br>
&gt;&gt;&gt; It does not seem best for this rfc6439bis draft to change the<=
br>
&gt;&gt; implementation requirement level for SNMP or NETCONF for TRILL. If=
 that<br>
&gt;&gt; were to be done, it seems like something more appropriate for the =
base<br>
&gt;&gt; TRILL YANG draft (draft-ietf-trill-yang-*) to do.<br>
&gt;&gt;<br>
&gt;&gt; If I was an implementer of TRILL, or an operator considering to de=
ploy<br>
&gt;&gt; TRILL, I would have a hard time trying to understand what to imple=
ment and<br>
&gt;&gt; what to deploy as management interfaces. Maybe this is not the pla=
ce but I<br>
&gt;&gt; believe that there need to be some documentation on this respect.<=
br>
&gt;<br>
&gt; OK. I think it would be reasonable to say something about the current<=
br>
&gt; implementation requirement level of SNMPv3 and to say that YANG<br>
&gt; modules are under development, so implementers will know more about<br=
>
&gt; what is going on.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Donald<br>
&gt; =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<wbr>=3D<br>
&gt;=C2=A0 Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 (cell)<br>
&gt;=C2=A0 155 Beaver Street, Milford, MA 01757 USA<br>
&gt;=C2=A0 <a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a><br>
&gt;<br>
&gt;&gt; Thanks and Regards,<br>
&gt;&gt; Dan<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Tue, Jan 17, 2017 at 3:48 AM, Donald Eastlake &lt;<a href=3D"ma=
ilto:d3e3e3@gmail.com">d3e3e3@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Hi Dan,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thanks for your review. As per my further response below, whil=
e the<br>
&gt;&gt;&gt; draft could perhaps use some clarifying additions related to<b=
r>
&gt;&gt;&gt; operations, I do not believe it is as bad as you say.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Thu, Jan 12, 2017 at 11:04 AM, Dan Romascanu &lt;<a href=3D=
"mailto:dromasca@gmail.com">dromasca@gmail.com</a>&gt;<br>
&gt;&gt;&gt; wrote:<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; Reviewer: Dan Romascanu<br>
&gt;&gt;&gt; &gt; Review result: Has Issues<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; I have reviewed this document as part of the Operational<=
br>
&gt;&gt;&gt; &gt; directorate&#39;s ongoing effort to review all IETF docum=
ents being<br>
&gt;&gt;&gt; &gt; processed by the IESG.=C2=A0 These comments were written =
with the intent<br>
&gt;&gt;&gt; &gt; of improving the operational aspects of the IETF drafts. =
Comments<br>
&gt;&gt;&gt; &gt; that are not addressed in last call may be included in AD=
 reviews<br>
&gt;&gt;&gt; &gt; during the IESG review.=C2=A0 Document editors and WG cha=
irs should treat<br>
&gt;&gt;&gt; &gt; these comments just like any other last call comments.<br=
>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; This document clarifies and updates the TRILL Appointed<b=
r>
&gt;&gt;&gt; &gt;=C2=A0 Forwarder mechanism. It updates RFC 6325, updates R=
FC 7177, and<br>
&gt;&gt;&gt; &gt;=C2=A0 obsoletes RFC 6439.<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; It&#39;s a complex document which requires extra reading =
to understand<br>
&gt;&gt;&gt; &gt; the context and the interraction with other RFCs. I belie=
ve that<br>
&gt;&gt;&gt; &gt; from an OPS-DIR perspective there are issues that need to=
 be<br>
&gt;&gt;&gt; &gt; discussed before the document can be approved.<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; The main issues with the document in its current form are=
:<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; 1. The document makes consistent changes in the way TRILL=
<br>
&gt;&gt;&gt; &gt; operates. It replaces TLVs and procedures, define new one=
s,<br>
&gt;&gt;&gt; &gt; obsoletes previous mechanisms that define VLAN mapping, a=
nd<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I am not aware of any case where this draft replaces a TLV in =
the<br>
&gt;&gt;&gt; sense of requiring use of a new TLV.=C2=A0 It does provide som=
e new TLVs<br>
&gt;&gt;&gt; and procedures that are believed to be superior to or useful a=
dditions<br>
&gt;&gt;&gt; to previous ones. But I am not aware of any case where it &quo=
t;obsoletes&quot;<br>
&gt;&gt;&gt; previous provisions in the sense of prohibiting their use.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; &gt; incorporates updated material from other RFCs. There is h=
owever no<br>
&gt;&gt;&gt; &gt; indication in the text about the transition between exist=
ing<br>
&gt;&gt;&gt; &gt; deployed versions of TRILL based on RFC 6439 and related =
protocols<br>
&gt;&gt;&gt; &gt; with the current updated mechanisms. Are these backward c=
ompatible?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I don&#39;t know that much is really required to be said about=
<br>
&gt;&gt;&gt; &quot;transition&quot; when you specify an optional optimizati=
on. Since it is<br>
&gt;&gt;&gt; optional, by implication the implementer is free to use it or =
not and<br>
&gt;&gt;&gt; things will work either way. This could be stated explicitly i=
n those<br>
&gt;&gt;&gt; cases.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Much of the material in this draft comes from RFC 6439 or the =
parts of<br>
&gt;&gt;&gt; RFC 7177 that updated RFC 6439. Most of the new material is op=
tional<br>
&gt;&gt;&gt; improved behaviors.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The only mandatory new behavior is the mandatory support of th=
e link<br>
&gt;&gt;&gt; local E-L1CS flooding scope [RFC7357] specified in Section 8. =
There is<br>
&gt;&gt;&gt; material in this draft covering backwards compatibility for th=
is new<br>
&gt;&gt;&gt; mandatory behavior.=C2=A0 Section 8 already explains how to de=
termine<br>
&gt;&gt;&gt; whether or not all TRILL switches on a link support E-L1CS flo=
oding<br>
&gt;&gt;&gt; scope. The only use of E-L1CS flooding scope in this draft is =
as part<br>
&gt;&gt;&gt; of a mechanism for the DRB (Designated RBridge (TRILL switch))=
 to<br>
&gt;&gt;&gt; advertise Forwarder Appointments and, as stated in Section 2.1=
 (see<br>
&gt;&gt;&gt; paragraph at the bottom of page 8 in draft -04), if any RBridg=
e on the<br>
&gt;&gt;&gt; link does not support E-L1CS, then the DRB MUST fall back to<b=
r>
&gt;&gt;&gt; advertising those appointments in Hellos. Section 8, which man=
dates<br>
&gt;&gt;&gt; support of E-L1CS, also requires that any use of E-L1CS specif=
ied in<br>
&gt;&gt;&gt; the future must provide for backward compatibility.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; &gt; Do they need a simultaneous upgrade of the whole network?=
<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; No.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; &gt; 2. The document lacks a section or even minimal text conc=
erning<br>
&gt;&gt;&gt; &gt; operational and manageability considerations.=C2=A0 There=
 are several<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Such a section can be added but there is not much to say. For =
example,<br>
&gt;&gt;&gt; as explained below, there is very little specified in this doc=
ument to<br>
&gt;&gt;&gt; configure.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; &gt; mentions in the text concerning network managers or opera=
tor<br>
&gt;&gt;&gt; &gt; actions, but there is no indication or reference to what =
management<br>
&gt;&gt;&gt; &gt; protocols and data models are to be used for configuratio=
n,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; RFC 6325, the base TRILL protocol RFC, says TRILL switches (RB=
ridges)<br>
&gt;&gt;&gt; SHOULD support SNMPv3 and there are TRILL MIB specifications i=
n RFCs<br>
&gt;&gt;&gt; 6850 and 7784. However, there are also YANG modules underway i=
n<br>
&gt;&gt;&gt; draft-ietf-trill-yang, draft-ietf-trill-yang-oam, and<br>
&gt;&gt;&gt; draft-ietf-trill-yang-pm.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; It does not seem best for this rfc6439bis draft to change the<=
br>
&gt;&gt;&gt; implementation requirement level for SNMP or NETCONF for TRILL=
. If that<br>
&gt;&gt;&gt; were to be done, it seems like something more appropriate for =
the base<br>
&gt;&gt;&gt; TRILL YANG draft (draft-ietf-trill-yang-*) to do.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; &gt; retrieval of operational status information, or alerts. I=
 believe<br>
&gt;&gt;&gt; &gt; that these need to be added explicitly or by reference.<b=
r>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Reviewing the significant protocol additions in this draft at =
a high<br>
&gt;&gt;&gt; level:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; - There is significant material about the various ways the Des=
ignated<br>
&gt;&gt;&gt;=C2=A0 =C2=A0RBridge on a link can announce who it is selecting=
 as the Appointed<br>
&gt;&gt;&gt;=C2=A0 =C2=A0Forwarder on the link for various VLANs. The elect=
ion of the<br>
&gt;&gt;&gt;=C2=A0 =C2=A0Designated RBridge depends on a configurable prior=
ity but that<br>
&gt;&gt;&gt;=C2=A0 =C2=A0election is unchanged from RFC 7177 and in fact is=
 identical to the<br>
&gt;&gt;&gt;=C2=A0 =C2=A0election of the designated router on any IS-IS lin=
k. The decision on<br>
&gt;&gt;&gt;=C2=A0 =C2=A0which RBridges to appointer as forwarder for which=
 VLAN is out of<br>
&gt;&gt;&gt;=C2=A0 =C2=A0scope. I don&#39;t see that there is anything to c=
onfigure here, other<br>
&gt;&gt;&gt;=C2=A0 =C2=A0than RBridge priority to be DRB, which is already =
specified in other<br>
&gt;&gt;&gt;=C2=A0 =C2=A0RFCs.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; - There are some optional optimizations to the inhibition mech=
anism.<br>
&gt;&gt;&gt;=C2=A0 =C2=A0The inhibition mechanism is necessary for loop saf=
ety but any<br>
&gt;&gt;&gt;=C2=A0 =C2=A0RBridge can use or not use any of these optimizati=
ons, as they<br>
&gt;&gt;&gt;=C2=A0 =C2=A0choose, and things will work fine.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; - Port Shutdown message: There are two new configuration param=
eters<br>
&gt;&gt;&gt;=C2=A0 =C2=A0here, namely how many copies of the Port Shutdown =
message to send<br>
&gt;&gt;&gt;=C2=A0 =C2=A0and at what interval. These are listed, along with=
 units and default<br>
&gt;&gt;&gt;=C2=A0 =C2=A0value in Section 6.6.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; - FGL-VLAN mapping consistency check: As specified in RFC 7172=
, in a<br>
&gt;&gt;&gt;=C2=A0 =C2=A0TRILL campus supporting Fine Grained Labels (FGL),=
 the VLAN of a<br>
&gt;&gt;&gt;=C2=A0 =C2=A0native frame can be mapped to an FGL on ingress an=
d an FGL is mapped<br>
&gt;&gt;&gt;=C2=A0 =C2=A0to a VLAN on egress. This draft makes no changes t=
o that mechanism.<br>
&gt;&gt;&gt;=C2=A0 =C2=A0It merely provides that an RBridge performing such=
 mapping can<br>
&gt;&gt;&gt;=C2=A0 =C2=A0optionally advertise the mapping it is performing =
at a port to other<br>
&gt;&gt;&gt;=C2=A0 =C2=A0RBridges with ports on the same link which can the=
n check it for<br>
&gt;&gt;&gt;=C2=A0 =C2=A0consistency with any mapping they are performing. =
It is recommended<br>
&gt;&gt;&gt;=C2=A0 =C2=A0that the network operator be alerted to such incon=
sistency and there<br>
&gt;&gt;&gt;=C2=A0 =C2=A0is a configurable parameter for how long the incon=
sistency needs to<br>
&gt;&gt;&gt;=C2=A0 =C2=A0exist before such alert. Is it your position that =
some specific<br>
&gt;&gt;&gt;=C2=A0 =C2=A0protocol mechanism must be specified by which the =
network operator<br>
&gt;&gt;&gt;=C2=A0 =C2=A0is alerted?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt; Donald<br>
&gt;&gt;&gt; =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<wbr>=3D<br>
&gt;&gt;&gt;=C2=A0 Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 (cell=
)<br>
&gt;&gt;&gt;=C2=A0 155 Beaver Street, Milford, MA 01757 USA<br>
&gt;&gt;&gt;=C2=A0 <a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a>=
<br>
&gt;&gt;<br>
&gt;&gt;<br>
</div></div></blockquote></div><br></div>

--001a11405b4e337449054a6fac2d--


From nobody Sat Mar 11 07:49:01 2017
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 2898B129507 for <ietf@ietfa.amsl.com>; Sat, 11 Mar 2017 07:48:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.003
X-Spam-Level: 
X-Spam-Status: No, score=-0.003 tagged_above=-999 required=5 tests=[RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLi_vUpge6yz for <ietf@ietfa.amsl.com>; Sat, 11 Mar 2017 07:48:47 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 336C7129465 for <ietf@ietf.org>; Sat, 11 Mar 2017 07:48:47 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QBU8WKPNWW00OVR5@mauve.mrochek.com> for ietf@ietf.org; Sat, 11 Mar 2017 07:43:43 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QBQBR8XOKG0003XB@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 11 Mar 2017 07:43:41 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01QBU8WJOCUO0003XB@mauve.mrochek.com>
Date: Sat, 11 Mar 2017 07:41:17 -0800 (PST)
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
In-reply-to: "Your message dated Sat, 11 Mar 2017 07:12:45 +0100" <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com> <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zg9D1jz3gvC4aIOkrophBDaDUok>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, ietf@ietf.org, secdir@ietf.org, "json@ietf.org" <json@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Mar 2017 15:48:51 -0000

> On 2017-03-11 03:08, John Cowan wrote:
> >
> > On Thu, Mar 9, 2017 at 12:53 AM, Benjamin Kaduk <kaduk@mit.edu
> > <mailto:kaduk@mit.edu>> wrote:
> >
> >     If that's what's supposed to happen, it should probably be more
> >     clear, yes.  (But aren't there texts that have valid interpretations
> >     in multiple encodings?)
> >
> >
> > Not if the content is well-formed JSON and the only possible encodings
> > are UTF-8, UTF-16, and UTF-32.  It suffices to examine the first four
> > bytes of the input.  If there are no NUL bytes in the first four bytes,
> > it is UTF-8; if there are two NUL bytes, it is UTF-16; if there are
> > three NUL bytes, it is UTF-32.  This works because the grammar requires
> > the first character to be in the ASCII repertoire, and the NUL
> > *character* (U+0000) is not allowed at all.

> Good explanation. Maybe the spec should include it.

+1

This exact issue just came up in a media type review, where someone
specified a charset parameter because they weren't aware of this algorithm.

It would be very helpful to have this text in the RFC.

				Ned


From nobody Sat Mar 11 18:59:14 2017
Return-Path: <cowan@ccil.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 E2E5E129443 for <ietf@ietfa.amsl.com>; Sat, 11 Mar 2017 18:59:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ccil-org.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSGdJArg5biD for <ietf@ietfa.amsl.com>; Sat, 11 Mar 2017 18:59:04 -0800 (PST)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F15C81294EE for <ietf@ietf.org>; Sat, 11 Mar 2017 18:59:02 -0800 (PST)
Received: by mail-wr0-x231.google.com with SMTP id l37so85140730wrc.1 for <ietf@ietf.org>; Sat, 11 Mar 2017 18:59:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HTuqMJ0eIgT7tTLAXbRgrHVav8Y0LsJygzS2gF95pX0=; b=o+5VkRdFFUVJWFtbEpFKYtgpSFQamsl2Enybw0Ri+36h512oB68bgxuRMtjDlNl+KY WNm4LhTnE7jHXajLdT9qof3zWCT8Vaj6945ELRrONncDm81teEBe6p4N1zeO6oYJzGsq qLLdpDTIxOUYDAzEeAjnMUp2QrY1dfVOT2wuFhjE6xqGPizBwsK2wcMJLK835CEwk8/d s7l5+RVVSF6BRBCjyR/km6l4jwxLNrpqujOWeNLO5fpV9Z6H1CsA9hfaTfjBZvrlEwF6 8IzM4K2CG+EpIAvehqoigm1TM36s/GVPVJPbKz0/gf7A2mZ8PKjD/M0CRffGNQq5l3K4 1stA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HTuqMJ0eIgT7tTLAXbRgrHVav8Y0LsJygzS2gF95pX0=; b=pRyIT2U28C3zcVOMHzB5ajsIyyjMsWaqlppErFiBCZor3SYTwuA0wntnLbDpBnAVom iBIOtZ0iUdS/SIgMYS5d4I+OeA0Y4QzJ7097S2M545o+Llj0VlT0IlPPkRo8aUfnjysJ d4XtY/QCzCrPtGzno1lk+DQjD9kojQ1vP3y2YFRyuAopJXpVCc70bBloTuJYJEsYn9VL inVduFoBqY8SwUITXodbqnQSHu1wZOm2kdq+gWK6gS+XZVMNcUCDifCkx0U4BdT5OnPM Ei9YLOfVv5kCoWN7qrQDBV0Y3YwyZa6ZLBbQBGANZ3VAr1FduvR76Lg7+2mhTAjaxe+B jNjg==
X-Gm-Message-State: AMke39lbe23lheROpndDYA5gmW5e+qWcW7qDhVjmnOv5ytSVaX4rTEMbhyZgO/zlEItx8HUuZESC5n0d9Sm67YSX
X-Received: by 10.223.152.215 with SMTP id w81mr24691006wrb.151.1489287541232;  Sat, 11 Mar 2017 18:59:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.181.14 with HTTP; Sat, 11 Mar 2017 18:58:40 -0800 (PST)
In-Reply-To: <01QBU8WJOCUO0003XB@mauve.mrochek.com>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com> <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de> <01QBU8WJOCUO0003XB@mauve.mrochek.com>
From: John Cowan <cowan@ccil.org>
Date: Sat, 11 Mar 2017 21:58:40 -0500
Message-ID: <CAD2gp_Q4f+ZsGw_qG5c=z0GoVEJAY2fuLneODXqA9W2byJ0h+g@mail.gmail.com>
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: multipart/alternative; boundary=001a113c36a6dd285e054a7fc6ea
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0VUUveJmAhqG2107KpyPINP5HF4>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, ietf@ietf.org, secdir@ietf.org, Julian Reschke <julian.reschke@gmx.de>, "json@ietf.org" <json@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 02:59:06 -0000

--001a113c36a6dd285e054a7fc6ea
Content-Type: text/plain; charset=UTF-8

On Sat, Mar 11, 2017 at 10:41 AM, Ned Freed <ned.freed@mrochek.com> wrote:

This exact issue just came up in a media type review, where someone
> specified a charset parameter because they weren't aware of this algorithm.
>
> It would be very helpful to have this text in the RFC.


Feel free, whoever is the editor now, to add it.

-- 
John Cowan          http://vrici.lojban.org/~cowan        cowan@ccil.org
But that, he realized, was a foolish thought; as no one knew better than
he that the Wall had no other side.
        --Arthur C. Clarke, "The Wall of Darkness"


>
>                                 Ned
>

--001a113c36a6dd285e054a7fc6ea
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sat, Mar 11, 2017 at 10:41 AM, Ned Freed <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:ned.freed@mrochek.com" target=3D"_blank">ned.freed@mrochek.com=
</a>&gt;</span> wrote:</div><div class=3D"gmail_quote"><br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
This exact issue just came up in a media type review, where someone<br>
specified a charset parameter because they weren&#39;t aware of this algori=
thm.<br>
<br>
It would be very helpful to have this text in the RFC.</blockquote><div><br=
></div><div>Feel free, whoever is the editor now, to add it.</div><div><br>=
</div><div>--=C2=A0</div><div>John Cowan =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
<a href=3D"http://vrici.lojban.org/~cowan">http://vrici.lojban.org/~cowan</=
a> =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:cowan@ccil.org">cowan@ccil.=
org</a></div><div>But that, he realized, was a foolish thought; as no one k=
new better than</div><div>he that the Wall had no other side.</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 --Arthur C. Clarke, &quot;The Wall of Darkness&quo=
t;=C2=A0</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><span class=3D"gmail-HOEnZb"><font color=3D"#888888"><br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ned<br>
</font></span></blockquote></div><br></div></div>

--001a113c36a6dd285e054a7fc6ea--


From nobody Sat Mar 11 23:47:58 2017
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B0DA1294DB; Sat, 11 Mar 2017 23:47:48 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-dime-load-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148930486813.2995.11930249317187128075@ietfa.amsl.com>
Date: Sat, 11 Mar 2017 23:47:48 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6DT5sTh-6yF4CCo40x3DFUG_bnI>
Cc: draft-ietf-dime-load.all@ietf.org, dime@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 07:47:48 -0000

Reviewer: Roni Even
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dime-load-??
Reviewer: Roni Even
Review Date: 2017-03-11
IETF LC End Date: 2017-02-27
IESG Telechat date: 2017-03-16

Summary: The document is ready for publication as a standard track
RFC

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Sun Mar 12 01:06:34 2017
Return-Path: <petejson@codalogic.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9924C126D73 for <ietf@ietfa.amsl.com>; Sun, 12 Mar 2017 01:06:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level: 
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oursa9J7lF2H for <ietf@ietfa.amsl.com>; Sun, 12 Mar 2017 01:06:29 -0800 (PST)
Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 366B51293FD for <ietf@ietf.org>; Sun, 12 Mar 2017 01:06:29 -0800 (PST)
Received: (qmail 1030 invoked from network); 12 Mar 2017 08:59:10 +0000
Received: from host109-158-230-32.range109-158.btcentralplus.com (HELO ?192.168.1.72?) (109.158.230.32) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 12 Mar 2017 08:59:10 +0000
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Ned Freed <ned.freed@mrochek.com>, Julian Reschke <julian.reschke@gmx.de>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com> <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de> <01QBU8WJOCUO0003XB@mauve.mrochek.com>
From: Peter Cordell <petejson@codalogic.com>
Message-ID: <6d97dee7-7cf3-9142-aacf-f2ca4909103d@codalogic.com>
Date: Sun, 12 Mar 2017 09:06:24 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <01QBU8WJOCUO0003XB@mauve.mrochek.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gNRUkiKKzXC2qa1qfCt_v5MjPbc>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, ietf@ietf.org, secdir@ietf.org, "json@ietf.org" <json@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 09:06:30 -0000

On 11/03/2017 15:41, Ned Freed wrote:
>> On 2017-03-11 03:08, John Cowan wrote:
>> >
>> > On Thu, Mar 9, 2017 at 12:53 AM, Benjamin Kaduk <kaduk@mit.edu
>> > <mailto:kaduk@mit.edu>> wrote:
>> >
>> >     If that's what's supposed to happen, it should probably be more
>> >     clear, yes.  (But aren't there texts that have valid
>> interpretations
>> >     in multiple encodings?)
>> >
>> >
>> > Not if the content is well-formed JSON and the only possible encodings
>> > are UTF-8, UTF-16, and UTF-32.  It suffices to examine the first four
>> > bytes of the input.  If there are no NUL bytes in the first four bytes,
>> > it is UTF-8; if there are two NUL bytes, it is UTF-16; if there are
>> > three NUL bytes, it is UTF-32.  This works because the grammar requires
>> > the first character to be in the ASCII repertoire, and the NUL
>> > *character* (U+0000) is not allowed at all.
>
>> Good explanation. Maybe the spec should include it.
>
> +1
>
> This exact issue just came up in a media type review, where someone
> specified a charset parameter because they weren't aware of this algorithm.
>
> It would be very helpful to have this text in the RFC.


Although it does need slightly more detail to take into account 
endian-ness in the case of UTF-16 and -32.

The XML spec may offer some example text:

https://www.w3.org/TR/2008/REC-xml-20081126/#sec-guessing

Pete Cordell
Codalogic Ltd
Read & write XML in C++, http://www.xml2cpp.com


From nobody Sun Mar 12 01:09:59 2017
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 8F1BE1293FD; Sun, 12 Mar 2017 01:09:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRq2vriQ6M-Z; Sun, 12 Mar 2017 01:09:53 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 770C9126D73; Sun, 12 Mar 2017 01:09:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2C99lQl008734; Sun, 12 Mar 2017 10:09:47 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vgwDq3PQ6zDHsX; Sun, 12 Mar 2017 10:09:47 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <01QBU8WJOCUO0003XB@mauve.mrochek.com>
Date: Sun, 12 Mar 2017 10:09:46 +0100
X-Mao-Original-Outgoing-Id: 511002586.144963-2ff5f2a34eda08f56731e4c680bd2c78
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F2F2116-4985-4561-BFD3-24B374E4C4ED@tzi.org>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com> <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de> <01QBU8WJOCUO0003XB@mauve.mrochek.com>
To: ned+ietf@mauve.mrochek.com
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0KrjySiCrFK_PcLOVCE93VOVeTE>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, IETF <ietf@ietf.org>, secdir@ietf.org, Julian Reschke <julian.reschke@gmx.de>, "json@ietf.org" <json@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 09:09:55 -0000

On 11 Mar 2017, at 16:41, ned+ietf@mauve.mrochek.com wrote:
>=20
> It would be very helpful to have this text in the RFC.

That would be a regression.

A better change would be to remove the fiction that JSON exists in =
UTF-16 or UTF-32 forms.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sun Mar 12 01:14:37 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80DA7129B01; Sun, 12 Mar 2017 01:14:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xPwwWuK9R5zL; Sun, 12 Mar 2017 01:14:33 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC607129B00; Sun, 12 Mar 2017 01:14:32 -0800 (PST)
Received: from [192.168.178.20] ([93.217.89.49]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ld0E0-1cMlZt0Pwm-00iAfB; Sun, 12 Mar 2017 10:14:05 +0100
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Peter Cordell <petejson@codalogic.com>, Ned Freed <ned.freed@mrochek.com>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com> <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de> <01QBU8WJOCUO0003XB@mauve.mrochek.com> <6d97dee7-7cf3-9142-aacf-f2ca4909103d@codalogic.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <cbbd0224-da58-bac5-b751-4195dd7383dc@gmx.de>
Date: Sun, 12 Mar 2017 10:14:04 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <6d97dee7-7cf3-9142-aacf-f2ca4909103d@codalogic.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:EBZZbuwf0wSMyEt5vpfTrDMD2A2TLrR/v0XrY+AFn9pTUiYCtQn 1JfsTBIPy8gpy4+ZzArmk3beM13BFRcinJzwghAXdFt2GZDVvyQTfvmOs+vdUcJsH4dpqAL /hE+EDxmuv0xshk/6X3blC6gekmdD03LwLNlXc8eLsl6TTEV4apZpMoIX6G0O1RSYDnGunB S+B0OClX0XzR41rmzuU0g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:XR2BrSIL2Yo=:3bGUZ2Dop4QI8MYQmVx/xF 61IyODJT8d7ulKG3BZeDQCONozTzTQJ4MJe3W47QtEVe0GQYjt4COVoD7qQ3xrAdF6+cSiJGe bXJv6xKz6jsIgNCp9tip6C7Y2lOOyM0oEjbHhnI+33U2gvEiZ7GaRvLDOmmH5BoYZKSZ00ABV vTRXLvjTWMGBRnPp/L08c4SyVNn3tyIEg/JjzTWyJrxWIx00Lvtl7knHy1HsF5K44NRyvRl3Q jlpvRXAvNKYFTjXxSkxXHE1VmcS3HhXbVURUeDWf9EeJM9sS3O0LxBH4FChzrbDtZ56WAkHwt 7btAJKCSUeW+ufUNHVLv57swS8q/cEYge8Rwx5l3ykhxVp7hb5/FZbyQeujt89gLupTkHnfJU gDQTB2SQg61L/cIT3CQvWpXrGcF3Trv+9oxDXecrUhLUrBUX82VqCIfO7ZGgD8mVxCYec6nW8 YvX1RUEsRL6TX7BOJsWBLE+KQYLhyzT7PF3RZVR4ZDy7H1qfTQ4x/e8IHC7A4J/XSq+l/Yvm/ nJiq5cE38Xfs4g2ZSd6E6KkwnrhKF3V6kBtbGo9tm6q/k9vPSdQpztGWhOnPfSVzlKtnThKcq e3+eYG8LsY92EBSZc2NxaIQchkh2Za1exyosCQ+2Q9blvdgUENxqY+vZG67JN5zeRbKTepb3m k9RR3oTOlE3vpQOgQ12FOYr3iQlrXpSCyZSPPtVH+B9s/Z5XeVFpbsBh89eHmEwxI5kytbnav aZvaoaNVMgjZz6oRaI+L1+dvCM3GMKrkC6CEpSBQSnlTwjiwdG6O+mnZJJ+KRVF2XgeJxjl/w hH3ofg6
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2mCbst2lsXUzISwiBFqfC_t3xPw>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, ietf@ietf.org, secdir@ietf.org, "json@ietf.org" <json@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 09:14:34 -0000

On 2017-03-12 10:06, Peter Cordell wrote:
> ...
>> This exact issue just came up in a media type review, where someone
>> specified a charset parameter because they weren't aware of this
>> algorithm.
>>
>> It would be very helpful to have this text in the RFC.
>
>
> Although it does need slightly more detail to take into account
> endian-ness in the case of UTF-16 and -32.
> ...

Does anybody recall why we removed 
<https://tools.ietf.org/html/rfc4627#section-3>:

> 3.  Encoding
>
>    JSON text SHALL be encoded in Unicode.  The default encoding is
>    UTF-8.
>
>    Since the first two characters of a JSON text will always be ASCII
>    characters [RFC0020], it is possible to determine whether an octet
>    stream is UTF-8, UTF-16 (BE or LE), or UTF-32 (BE or LE) by looking
>    at the pattern of nulls in the first four octets.
>
>            00 00 00 xx  UTF-32BE
>            00 xx 00 xx  UTF-16BE
>            xx 00 00 00  UTF-32LE
>            xx 00 xx 00  UTF-16LE
>            xx xx xx xx  UTF-8

?

Best regards, Julian


From nobody Sun Mar 12 05:11:54 2017
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 782C31293EB for <ietf@ietfa.amsl.com>; Sun, 12 Mar 2017 05:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjHFd8eWQrrW for <ietf@ietfa.amsl.com>; Sun, 12 Mar 2017 05:11:45 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0F2B128E18 for <ietf@ietf.org>; Sun, 12 Mar 2017 05:11:44 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QBVHP8004000PMAR@mauve.mrochek.com> for ietf@ietf.org; Sun, 12 Mar 2017 05:06:41 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QBQBR8XOKG0003XB@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sun, 12 Mar 2017 05:06:37 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01QBVHP5YAYE0003XB@mauve.mrochek.com>
Date: Sun, 12 Mar 2017 04:56:29 -0700 (PDT)
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
In-reply-to: "Your message dated Sun, 12 Mar 2017 10:09:46 +0100" <9F2F2116-4985-4561-BFD3-24B374E4C4ED@tzi.org>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com> <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de> <01QBU8WJOCUO0003XB@mauve.mrochek.com> <9F2F2116-4985-4561-BFD3-24B374E4C4ED@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-QqMFwNfy7ySZNMnFsozQFdhhOo>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, IETF <ietf@ietf.org>, secdir@ietf.org, ned+ietf@mauve.mrochek.com, "json@ietf.org" <json@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 12:11:45 -0000

> On 11 Mar 2017, at 16:41, ned+ietf@mauve.mrochek.com wrote:
> >
> > It would be very helpful to have this text in the RFC.

> That would be a regression.

On the contrary - what you have now is incomplete if not actually broken, and
this completes/fixes it.

You have a specification that says (a) JSON can be encoded in UTF-8, UTF-16, or
UTF-32 and that (b) That no charset parameter is needed to distinguish the
charset and moreover one has "no effect". But you don't explain how why this is
the the case, or what compliant implementation do to determine the charset.

If you believe clarifying this is problemtic in some way, you need to explain
why.

> A better change would be to remove the fiction that JSON exists in UTF-16 or
> UTF-32 forms.

That's of course another way to fix the problem. But it's a far more
significant change, and I have to wonder if there is a consensus to do it.

Personally, I have no preference as to the approach that's used. But moving
forward as-is is really not acceptable.

				Ned


From nobody Sun Mar 12 05:47:24 2017
Return-Path: <rsk@gsp.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 AC2AB128DF6 for <ietf@ietfa.amsl.com>; Sun, 12 Mar 2017 05:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCBtGUP0HjL2 for <ietf@ietfa.amsl.com>; Sun, 12 Mar 2017 05:47:22 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31B65128824 for <ietf@ietf.org>; Sun, 12 Mar 2017 05:47:21 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v2CClKGo032086 for <ietf@ietf.org>; Sun, 12 Mar 2017 08:47:20 -0400 (EDT)
Date: Sun, 12 Mar 2017 08:47:20 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: The CIA mentions us
Message-ID: <20170312124720.GA13596@gsp.org>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Yns14MMK9A53mJPLNBp8VFLoNaY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 12:47:23 -0000

On Thu, Mar 09, 2017 at 10:36:07PM +0200, Jari Arkko wrote:
> 2. There is no such thing as privileged access to the good guys. It
> will leak / break / be shared.
> 
> 3. Secretly held vulnerabilities make us all less safe.


Two points:

A) Worth noting (h/t to Richard Forno):

	Rand: The Life and Times of Zero-Day Vulnerabilities and Their Exploits
	http://www.rand.org/pubs/research_reports/RR1751.html

The key findings are highly illuminating -- particularly the observation that
the median time -- the *median* time -- to develop an exploit for a zero-day
vulnerability is 22 days.

B) What one government knows, another will know soon.  There are enormous
resources available for this task and vulnerability information, unlike
some other forms of intelligence, can be immediately used with plausible
deniability and without attribution.

---rsk


From nobody Sun Mar 12 08:31:58 2017
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 59C20126BF6; Sun, 12 Mar 2017 08:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yKfHguuWtDsQ; Sun, 12 Mar 2017 08:31:50 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10C3D129509; Sun, 12 Mar 2017 08:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2CFVhYC020320; Sun, 12 Mar 2017 16:31:43 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vh4jW01q0zDHvr; Sun, 12 Mar 2017 16:31:42 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <cbbd0224-da58-bac5-b751-4195dd7383dc@gmx.de>
Date: Sun, 12 Mar 2017 16:31:42 +0100
X-Mao-Original-Outgoing-Id: 511025502.207779-be1eff5230d4761fb1f26c2a4fa3d8de
Content-Transfer-Encoding: quoted-printable
Message-Id: <38DEEE0A-EE2C-4ADA-9D7A-9DBBAEACB77E@tzi.org>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com> <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de> <01QBU8WJOCUO0003XB@mauve.mrochek.com> <6d97dee7-7cf3-9142-aacf-f2ca4909103d@codalogic.com> <cbbd0224-da58-bac5-b751-4195dd7383dc@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MVGkqLMPpjVt1lmzloQ8CW7zWe4>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, Ned Freed <ned.freed@mrochek.com>, IETF <ietf@ietf.org>, Peter Cordell <petejson@codalogic.com>, secdir@ietf.org, "json@ietf.org" <json@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 15:31:52 -0000

On 12 Mar 2017, at 10:14, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> Does anybody recall why we removed =
<https://tools.ietf.org/html/rfc4627#section-3>:

I seem to remember that the advice simply is no longer working since =
JSON was extended from 4627 to 7159.  Instead of trying to come up with =
an updated algorithm, the WG recognized that this is not a real-world =
problem.

If 7159bis is supposed to be an Internet Standard, it should focus on =
the variants that actually interoperate.  Re-encoding JSON into UTF-16 =
(or UTF-32) is not really interoperable with today=E2=80=99s =
implementations*).

Gr=C3=BC=C3=9Fe, Carsten

*) (Given the large number of JSON implementations, I don=E2=80=99t =
doubt you will find two implementations that do interoperate on this.  =
It is not the widely interoperable =E2=80=9CJSON=E2=80=9D thing, =
though.)


From nobody Sun Mar 12 14:40:52 2017
Return-Path: <weihaw@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 0B778129442 for <ietf@ietfa.amsl.com>; Sun, 12 Mar 2017 14:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ev3ECxKs9AF for <ietf@ietfa.amsl.com>; Sun, 12 Mar 2017 14:40:48 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2485A12943A for <ietf@ietf.org>; Sun, 12 Mar 2017 14:40:48 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id 126so70724996oig.3 for <ietf@ietf.org>; Sun, 12 Mar 2017 14:40:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=hrJlGwl94FYJV4T4W6put1T70vdhlCVaqDI8QgFKbRA=; b=DB3KjXejPKi7hMj2YIQE35MWtpPhveCMdzpXzFM/B1i0SEVmweuIg15U7LFeJjlUh+ QOEXpNeA89WH6fhNlaRSuT40bm5XH5Jcp9jo8dnJRRYLuoJ/dHnF78p7iLDf/E9svmXY /MK7XJHHJIdFBJ3lKzykiYRSAc/NCjI5iagsLqZAqkWMjMk3oLfL49xUlIh4W9VIoyfo 1FwyQobX0CaqaBJCuay5nbEyGfmQcw+A0PmSWkcpidq+CZ6kpMT0ihP4WJ/l6ZSGfL2X Bq7CjcskPeZ8F30wBfu86vKjg2oukBrJB/eD2/ANRqQQbZopD4LvKly98IY1nkya5GAB XGzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=hrJlGwl94FYJV4T4W6put1T70vdhlCVaqDI8QgFKbRA=; b=nGY9r0seqpnU77s1Fh+Rn3eWumbhBSxmpwk2UAgNwWDDZdCu7qlv+GeJ3egUUiiJhZ /0R2Xx0wOK2hk2j+6SDvO79z1KSEponNnAtFJVwoj0pqqU/fXhpT8jh0nRTl7So8KsyX JMJeMvAd/muftlKExNkWEwxkQejtKJrjCeVXLKiejTPfRh0FswI/zQ1a1wau574kgq0Q u9gFYWHOeQj3t6tf45HGSfiAxbVjBlu4Q6isecUQvRr2K4GHq4PBVMZcoX22X3nIXrI5 jne0Qr2zopxwq5xdAZLnR/F6OZlsP/EQE3+Ggs55L1MXSpNGOlteQubpdJeCyFawJ3Bc X0UQ==
X-Gm-Message-State: AMke39kxLYuvSPnNvIta9yI/tO1MuQhb9S02Tljc2fA3sZxg3pK1tbDy/VFXv6NK8DoZsQHnHiLRWaP5CT9+awpI
X-Received: by 10.202.226.146 with SMTP id z140mr14326118oig.166.1489354847134;  Sun, 12 Mar 2017 14:40:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.41.226 with HTTP; Sun, 12 Mar 2017 14:40:45 -0700 (PDT)
In-Reply-To: <CAAFsWK1Q=d-9E++J0Z7UyEn3mshKkbYZ9yuGX974XvU8rO0VQw@mail.gmail.com>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org> <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie> <6d114340-c9a7-e311-e6f9-0614600cafd2@cs.tcd.ie> <CAAFsWK2RMGp0jqesx3cTbN=S7p0WuhH+0AbeJuuiZPF6WCbQOQ@mail.gmail.com> <BCEFAA3C-B711-4269-81C8-4DA0E1AA7AD0@dukhovni.org> <CAAFsWK3yJ9r+6abTXZQsNsey+VcRpdtVv=Hku_54_LZ9y1T2xQ@mail.gmail.com> <B8A5967B-9C19-4167-8A20-B82DFD46A924@dukhovni.org> <00c401d298b8$616fffa0$4001a8c0@gateway.2wire.net> <CAAFsWK1Q=d-9E++J0Z7UyEn3mshKkbYZ9yuGX974XvU8rO0VQw@mail.gmail.com>
From: Wei Chuang <weihaw@google.com>
Date: Sun, 12 Mar 2017 14:40:45 -0700
Message-ID: <CAAFsWK3n=dpix1dF6_tm+ZBSqkC=+DW301HaLSg__p-0Tt0rxg@mail.gmail.com>
Subject: Re: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: IETF general list <ietf@ietf.org>, SPASM <spasm@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a11408a3aa06ba0054a8f7235"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qOckowLAqmBGp0qaY9RUkcNEaZU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 21:40:50 -0000

--001a11408a3aa06ba0054a8f7235
Content-Type: multipart/alternative; boundary=001a11408a3a9bf658054a8f7273

--001a11408a3a9bf658054a8f7273
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The latest draft 08 is up:
https://tools.ietf.org/html/draft-ietf-lamps-eai-addresses-08

The diff is:
https://tools.ietf.org/rfcdiff?url2=draft-ietf-lamps-eai-addresses-08.txt

This draft attempts to capture Viktor's name constraint verifier logic, and
illustrate the examples in the diagrams.

-Wei


On Thu, Mar 9, 2017 at 10:22 AM, Wei Chuang <weihaw@google.com> wrote:

> There seems to be a consensus here and internally to the changes that
> Viktor proposes.  We can put that in the next draft update.
>
> -Wei
>
> On Thu, Mar 9, 2017 at 1:34 AM, tom p. <daedulus@btconnect.com> wrote:
>
>> ----- Original Message -----
>> From: "Viktor Dukhovni" <ietf-dane@dukhovni.org>
>> To: <spasm@ietf.org>; "IETF general list" <ietf@ietf.org>
>> Sent: Thursday, March 09, 2017 3:19 AM
>> > On Mar 8, 2017, at 8:17 PM, Wei Chuang <weihaw@google.com> wrote:
>> >
>> > Okay.  I think the direction then is to have SmtpUTF8Name respect
>> rfc822Name name constraints and vice versa.
>>
>> Well, no, the simplest proposal on the table is for SmtpUTF8Name to
>> be *prohibited* when rfc822Name constraints are present and SmtpUTF8Name
>> constraints are not.  When both present, they can operate independently.
>>
>> <tp>
>>
>> Getting security right can be tricky as the legion of failed attempts
>> that make it to RFC testify but what you are proposing here seems so
>> simple, so obviously the right thing to do that I am puzzled, bewildered
>> even, that anyone can disagree with you.
>>
>> Tom Petch
>>
>> The verifier logic is then:
>>
>> 1. If neither rfc822Name constraints nor SmtpUTF8Name constraints
>>            are present in any CA certificate in the chain, any mixture
>> of
>>            rfc822Name and SmtpUTF8Name SAN elements is valid.
>>
>> 2. If some certificate in the chain contains *only* rfc822Name
>>    constraints, then these apply to rfc822Name SAN elements, but
>>    all SmtpUTF8Names are prohibited.
>>
>> 3. When both types of constraints are present in all CA certificates
>>            that have either type, then constraints for each SAN type are
>>    exclusively based on just the corresponding constraint type.
>>
>> 4. If some certificate in the chain contains only SmtpUTF8Name
>>      constraints then those are unavoidably at risk of bypass via
>>            rfc822Name SAN elements when processed by legacy verifiers.
>>    Therefore, this should be avoided, and the CA needs to
>>      publish rfc822Name constraints that prevent bypass.  Such
>>    constraints *need not* be equivalent (not always possible)
>>    to the desired SmtpUTF8Name constraints.  Rather, it suffices
>>    to not permit rfc822Name elements that would be prohibited
>>    if they were simply cut/pasted (with no A-label to U-label
>>            conversions) as SmtpUTF8Name elements.  It is not necessary
>>    for these to permit everything that SmtpUTF8Name permits.
>>
>> Thus for example, if SmtpUtf8Name only permits addresses in the non
>> NR-LDH
>> domain "духовный.org <http://xn--b1adqpd3ao5c.org>" (or a specific set
>> of addresses in such a domain),
>> then the corresponding rfc822Name constraint could just permit "." (or
>> the
>> reserved "invalid" TLD if that's preferable) which is not a usable email
>> domain.  This ensures that only the permitted SmtpUTF8Name SANs are used
>> and no rfc822Name SANs are used.
>>
>> If, instead the Smtp8Name constraints are excluded non-ASCII address
>> forms,
>> then since these have no literal rfc822Name equivalents, the rfc822Name
>> constraints can be omitted with the same effect.
>>
>> Only when the intention is to permit NR-LDH domains with either ASCII or
>> UTF-8 localparts (or an all-ASCII full address) do the rfc822Name and
>> SmtpUTF8Name constraints need to be fully equivalent.  This is of course
>> trivial to do.  Just cut/paste the same string into both types of
>> constraint.
>>
>> --
>> Viktor.
>>
>>
>

--001a11408a3a9bf658054a8f7273
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr">The latest draft 08 is up:<div><a href="https://tools.ietf.org/html/draft-ietf-lamps-eai-addresses-08">https://tools.ietf.org/html/draft-ietf-lamps-eai-addresses-08</a><br></div><div><br></div><div>The diff is:</div><div><a href="https://tools.ietf.org/rfcdiff?url2=draft-ietf-lamps-eai-addresses-08.txt">https://tools.ietf.org/rfcdiff?url2=draft-ietf-lamps-eai-addresses-08.txt</a><br></div><div><br></div><div>This draft attempts to capture Viktor&#39;s name constraint verifier logic, and illustrate the examples in the diagrams.</div><div><br></div><div>-Wei</div><div> </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 9, 2017 at 10:22 AM, Wei Chuang <span dir="ltr">&lt;<a href="mailto:weihaw@google.com" target="_blank">weihaw@google.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">There seems to <!--
-->be a consensus here and internally to the changes that Viktor proposes.  We can put that in the next draft update.<span class="CSS_CV_TRIMMABLE_"><font color="#888888"><div><br></div><div>-Wei</div></font></span></div><div class="CSS_CV_TRIMMABLE_"><div class="CSS_CV_ELIDED_TEXT_"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 9, 2017 at 1:34 AM, tom p. <span dir="ltr">&lt;<a href="mailto:daedulus@btconnect.com" target="_blank">daedulus@btconnect.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>----- Original Message -----<br>
From: &quot;Viktor Dukhovni&quot; &lt;<a href="mailto:ietf-dane@dukhovni.org" target="_blank">ietf-dane@dukhovni.org</a>&gt;<br>
To: &lt;<a href="mailto:spasm@ietf.org" target="_blank">spasm@ietf.org</a>&gt;; &quot;IETF general list&quot; &lt;<a href="mailto:ietf@ietf.org" target="_blank">ietf@ietf.org</a>&gt;<br>
Sent: Thursday, March 09, 2017 3:19 AM<br>
&gt; On Mar 8, 2017, at 8:17 PM, Wei Chuang &lt;<a href="mailto:weihaw@google.com" target="_blank">weihaw@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Okay.  I think the direction then is to have SmtpUTF8Name respect<br>
rfc822Name name constraints and vice versa.<br>
<br>
Well, no, the simplest proposal on the table is for SmtpUTF8Name to<br>
be *prohibited* when rfc822Name constraints are present and SmtpUTF8Name<br>
constraints are not.  When both present, they can operate independently.<br>
<br>
</span>&lt;tp&gt;<br>
<br>
Getting security right can be tricky as the legion of failed attempts<br>
that make it to RFC testify but what you are proposing here seems so<br>
simple, so obviously the right thing to do that I am puzzled, bewildered<br>
even, that anyone can disagree with you.<br>
<br>
Tom Petch<br>
<div class="m_-7944493824666316511CSS_CV_TRIMMABLE_"><div class="m_-7944493824666316511CSS_CV_ELIDED_TEXT_"><br>
The verifier logic is then:<br>
<br>
1. If neither rfc822Name constraints nor SmtpUTF8Name constraints<br>
           are present in any CA certificate in the chain, any mixture<br>
of<br>
           rfc822Name and SmtpUTF8Name SAN elements is valid.<br>
<br>
2. If some certificate in the chain contains *only* rfc822Name<br>
   constraints, then these apply to rfc822Name SAN elements, but<br>
   all SmtpUTF8Names are prohibited.<br>
<br>
3. When both types of constraints are present in all CA certificates<br>
           that have either type, then constraints for each SAN type are<br>
   exclusively based on just the corresponding constraint type.<br>
<br>
4. If some certificate in the chain contains only SmtpUTF8Name<br>
     constraints then those are unavoidably at risk of bypass via<br>
           rfc822Name SAN elements when processed by legacy verifiers.<br>
   Therefore, this should be avoided, and the CA needs to<br>
     publish rfc822Name constraints that prevent bypass.  Such<br>
   constraints *need not* be equivalent (not always possible)<br>
   to the desired SmtpUTF8Name constraints.  Rather, it suffices<br>
   to not permit rfc822Name elements that would be prohibited<br>
   if they were simply cut/pasted (with no A-label to U-label<br>
           conversions) as SmtpUTF8Name elements.  It is not necessary<br>
   for these to permit everything that SmtpUTF8Name permits.<br>
<br>
Thus for example, if SmtpUtf8Name only permits addresses in the non<br>
NR-LDH<br>
domain &quot;<a href="http://xn--b1adqpd3ao5c.org" rel="noreferrer" target="_blank">духовный.org</a>&quot; (or a specific set of addresses in such a domain),<br>
then the corresponding rfc822Name constraint could just permit &quot;.&quot; (or<br>
the<br>
reserved &quot;invalid&quot; TLD if that&#39;s preferable) which is not a usable email<br>
domain.  This ensures that only the permitted SmtpUTF8Name SANs are used<br>
and no rfc822Name SANs are used.<br>
<br>
If, instead the Smtp8Name constraints are excluded non-ASCII address<br>
forms,<br>
then since these have no literal rfc822Name equivalents, the rfc822Name<br>
constraints can be omitted with the same effect.<br>
<br>
Only when the intention is to permit NR-LDH domains with either ASCII or<br>
UTF-8 localparts (or an all-ASCII full address) do the rfc822Name and<br>
SmtpUTF8Name constraints need to be fully equivalent.  This is of course<br>
trivial to do.  Just cut/paste the same string into both types of<br>
constraint.<br>
<br>
--<br>
Viktor.<br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a11408a3a9bf658054a8f7273--

--001a11408a3aa06ba0054a8f7235
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCClXM0EpYvJoJThWe3EHGiL
ANHzuq+ewSQNKQwn4rBf0DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAzMTIyMTQwNDdaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEANNJSTLujn3Rbz0Q0kY/yltLuVX334qbp2vB6Qu+A
WJNXPwdADStnxrz0MYDCG8XPYBjltRZWkY62x1dDyzx5TAFL7GtTdblpXt+iHaQy0kku7JFhU9fh
rlS0aGVyrlXxcUzcqR+j9z1ZLNsBwj8qmlBjJRnbFL+iOl/i2Ofoh8envBAEUUacJwtQnSoy6LwO
jmucy46yl/Gc1KYEyeiB1DYRZa1W2DilalnCfYgIFqKZ7QQTzjC/I4/K5Q9GHCUsJcGTB9YelDCv
7sTruyw0Mtzcu81dTNELInCOtIwXvFNRNCW27W/xM+1wNynTEEYMP14nr0QNAAsTC1veA3kboQ==
--001a11408a3aa06ba0054a8f7235--


From nobody Sun Mar 12 16:38:21 2017
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 F131F129413; Sun, 12 Mar 2017 16:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o2ACz6TGtvvs; Sun, 12 Mar 2017 16:38:09 -0700 (PDT)
Received: from b-painless.mh.aa.net.uk (b-painless.mh.aa.net.uk [81.187.30.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 426C812940C; Sun, 12 Mar 2017 16:38:09 -0700 (PDT)
Received: from f.6.d.d.7.f.3.e.8.2.f.e.4.f.0.3.1.0.0.0.f.b.0.0.0.b.8.0.1.0.0.2.ip6.arpa ([2001:8b0:bf:1:30f4:ef28:e3f7:dd6f]) by b-painless.mh.aa.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <elwynd@dial.pipex.com>) id 1cnCae-0007SI-2h; Sun, 12 Mar 2017 23:07:52 +0000
Date: Sun, 12 Mar 2017 23:07:40 +0000
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
Message-ID: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com>
Importance: normal
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Peter Cordell <petejson@codalogic.com>, Ned Freed <ned.freed@mrochek.com>, Julian Reschke <julian.reschke@gmx.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_4565109410242090"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LGpgyQBAXMIg2J83uHKD5nQKi2g>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, ietf@ietf.org, secdir@ietf.org, "json@ietf.org" <json@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Mar 2017 23:38:12 -0000

----_com.samsung.android.email_4565109410242090
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

KHdpdGggaGFsZiBhIEdlbi1hcnQgaGF0IG9uLi4uKQpEb2VzIHRoZSBXRyByZWFsbHkgd2FudCB0
byByZXZpc2l0IHRoZSBhbmd1aXNoZWQgZGlzY3Vzc2lvbnMgdGhhdCByZXN1bHRlZCBpbiB0aGUg
Y2hhbmdlcyB0byBTZWN0aW9uIDguMSBvZiBkcmFmdC1pZXRmLWpzb24tcmZjNDYyN2JpcyBiZXR3
ZWVuIHZlcnNpb25zIDA3IGFuZCAwOCBiYWNrIGluIGxhdGUgTm92ZW1iZXIgMjAxMz8KU2VlwqBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2pzb24vY3VycmVudC9tc2cwMjA1
My5odG1sIGFuZCBtYW55LCBtYW55IG1lc3NhZ2VzIGJlb3JlIHRoaXMuCkNoZWVycyxFbHd5bgoK
ClNlbnQgZnJvbSBTYW1zdW5nIHRhYmxldC4KLS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0t
LS0tLUZyb206IFBldGVyIENvcmRlbGwgPHBldGVqc29uQGNvZGFsb2dpYy5jb20+IERhdGU6IDEy
LzAzLzIwMTcgIDA5OjA2ICAoR01UKzAwOjAwKSBUbzogTmVkIEZyZWVkIDxuZWQuZnJlZWRAbXJv
Y2hlay5jb20+LCBKdWxpYW4gUmVzY2hrZSA8anVsaWFuLnJlc2Noa2VAZ214LmRlPiBDYzogZHJh
ZnQtaWV0Zi1qc29uYmlzLXJmYzcxNTliaXMuYWxsQGlldGYub3JnLCBKb2huIENvd2FuIDxjb3dh
bkBjY2lsLm9yZz4sIGlldGZAaWV0Zi5vcmcsIHNlY2RpckBpZXRmLm9yZywganNvbkBpZXRmLm9y
ZywgQmVuamFtaW4gS2FkdWsgPGthZHVrQG1pdC5lZHU+IFN1YmplY3Q6IFJlOiBbSnNvbl0gc2Vj
ZGlyIHJldmlldyBvZiBkcmFmdC1pZXRmLWpzb25iaXMtcmZjNzE1OWJpcy0wMyAKT24gMTEvMDMv
MjAxNyAxNTo0MSwgTmVkIEZyZWVkIHdyb3RlOgo+PiBPbiAyMDE3LTAzLTExIDAzOjA4LCBKb2hu
IENvd2FuIHdyb3RlOgo+PiA+Cj4+ID4gT24gVGh1LCBNYXIgOSwgMjAxNyBhdCAxMjo1MyBBTSwg
QmVuamFtaW4gS2FkdWsgPGthZHVrQG1pdC5lZHUKPj4gPiA8bWFpbHRvOmthZHVrQG1pdC5lZHU+
PiB3cm90ZToKPj4gPgo+PiA+wqDCoMKgwqAgSWYgdGhhdCdzIHdoYXQncyBzdXBwb3NlZCB0byBo
YXBwZW4sIGl0IHNob3VsZCBwcm9iYWJseSBiZSBtb3JlCj4+ID7CoMKgwqDCoCBjbGVhciwgeWVz
LsKgIChCdXQgYXJlbid0IHRoZXJlIHRleHRzIHRoYXQgaGF2ZSB2YWxpZAo+PiBpbnRlcnByZXRh
dGlvbnMKPj4gPsKgwqDCoMKgIGluIG11bHRpcGxlIGVuY29kaW5ncz8pCj4+ID4KPj4gPgo+PiA+
IE5vdCBpZiB0aGUgY29udGVudCBpcyB3ZWxsLWZvcm1lZCBKU09OIGFuZCB0aGUgb25seSBwb3Nz
aWJsZSBlbmNvZGluZ3MKPj4gPiBhcmUgVVRGLTgsIFVURi0xNiwgYW5kIFVURi0zMi7CoCBJdCBz
dWZmaWNlcyB0byBleGFtaW5lIHRoZSBmaXJzdCBmb3VyCj4+ID4gYnl0ZXMgb2YgdGhlIGlucHV0
LsKgIElmIHRoZXJlIGFyZSBubyBOVUwgYnl0ZXMgaW4gdGhlIGZpcnN0IGZvdXIgYnl0ZXMsCj4+
ID4gaXQgaXMgVVRGLTg7IGlmIHRoZXJlIGFyZSB0d28gTlVMIGJ5dGVzLCBpdCBpcyBVVEYtMTY7
IGlmIHRoZXJlIGFyZQo+PiA+IHRocmVlIE5VTCBieXRlcywgaXQgaXMgVVRGLTMyLsKgIFRoaXMg
d29ya3MgYmVjYXVzZSB0aGUgZ3JhbW1hciByZXF1aXJlcwo+PiA+IHRoZSBmaXJzdCBjaGFyYWN0
ZXIgdG8gYmUgaW4gdGhlIEFTQ0lJIHJlcGVydG9pcmUsIGFuZCB0aGUgTlVMCj4+ID4gKmNoYXJh
Y3RlciogKFUrMDAwMCkgaXMgbm90IGFsbG93ZWQgYXQgYWxsLgo+Cj4+IEdvb2QgZXhwbGFuYXRp
b24uIE1heWJlIHRoZSBzcGVjIHNob3VsZCBpbmNsdWRlIGl0Lgo+Cj4gKzEKPgo+IFRoaXMgZXhh
Y3QgaXNzdWUganVzdCBjYW1lIHVwIGluIGEgbWVkaWEgdHlwZSByZXZpZXcsIHdoZXJlIHNvbWVv
bmUKPiBzcGVjaWZpZWQgYSBjaGFyc2V0IHBhcmFtZXRlciBiZWNhdXNlIHRoZXkgd2VyZW4ndCBh
d2FyZSBvZiB0aGlzIGFsZ29yaXRobS4KPgo+IEl0IHdvdWxkIGJlIHZlcnkgaGVscGZ1bCB0byBo
YXZlIHRoaXMgdGV4dCBpbiB0aGUgUkZDLgoKCkFsdGhvdWdoIGl0IGRvZXMgbmVlZCBzbGlnaHRs
eSBtb3JlIGRldGFpbCB0byB0YWtlIGludG8gYWNjb3VudCAKZW5kaWFuLW5lc3MgaW4gdGhlIGNh
c2Ugb2YgVVRGLTE2IGFuZCAtMzIuCgpUaGUgWE1MIHNwZWMgbWF5IG9mZmVyIHNvbWUgZXhhbXBs
ZSB0ZXh0OgoKaHR0cHM6Ly93d3cudzMub3JnL1RSLzIwMDgvUkVDLXhtbC0yMDA4MTEyNi8jc2Vj
LWd1ZXNzaW5nCgpQZXRlIENvcmRlbGwKQ29kYWxvZ2ljIEx0ZApSZWFkICYgd3JpdGUgWE1MIGlu
IEMrKywgaHR0cDovL3d3dy54bWwyY3BwLmNvbQoK

----_com.samsung.android.email_4565109410242090
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2Pih3aXRoIGhhbGYgYSBHZW4t
YXJ0IGhhdCBvbi4uLik8L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PkRvZXMgdGhlIFdHIHJlYWxs
eSB3YW50IHRvIHJldmlzaXQgdGhlIGFuZ3Vpc2hlZCBkaXNjdXNzaW9ucyB0aGF0IHJlc3VsdGVk
IGluIHRoZSBjaGFuZ2VzIHRvIFNlY3Rpb24gOC4xIG9mIGRyYWZ0LWlldGYtanNvbi1yZmM0NjI3
YmlzIGJldHdlZW4gdmVyc2lvbnMgMDcgYW5kIDA4IGJhY2sgaW4gbGF0ZSBOb3ZlbWJlciAyMDEz
PzwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+U2VlJm5ic3A7aHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbC1hcmNoaXZlL3dlYi9qc29uL2N1cnJlbnQvbXNnMDIwNTMuaHRtbCBhbmQgbWFueSwgbWFu
eSBtZXNzYWdlcyBiZW9yZSB0aGlzLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+Q2hlZXJzLDwv
ZGl2PjxkaXY+RWx3eW48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pjxi
cj48L2Rpdj48ZGl2IGlkPSJjb21wb3Nlcl9zaWduYXR1cmUiPjxkaXYgc3R5bGU9ImZvbnQtc2l6
ZTo4NSU7Y29sb3I6IzU3NTc1NyIgZGlyPSJhdXRvIj5TZW50IGZyb20gU2Ftc3VuZyB0YWJsZXQu
PC9kaXY+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zaXplOjEwMCU7Y29s
b3I6IzAwMDAwMCI+PCEtLSBvcmlnaW5hbE1lc3NhZ2UgLS0+PGRpdj4tLS0tLS0tLSBPcmlnaW5h
bCBtZXNzYWdlIC0tLS0tLS0tPC9kaXY+PGRpdj5Gcm9tOiBQZXRlciBDb3JkZWxsICZsdDtwZXRl
anNvbkBjb2RhbG9naWMuY29tJmd0OyA8L2Rpdj48ZGl2PkRhdGU6IDEyLzAzLzIwMTcgIDA5OjA2
ICAoR01UKzAwOjAwKSA8L2Rpdj48ZGl2PlRvOiBOZWQgRnJlZWQgJmx0O25lZC5mcmVlZEBtcm9j
aGVrLmNvbSZndDssIEp1bGlhbiBSZXNjaGtlICZsdDtqdWxpYW4ucmVzY2hrZUBnbXguZGUmZ3Q7
IDwvZGl2PjxkaXY+Q2M6IGRyYWZ0LWlldGYtanNvbmJpcy1yZmM3MTU5YmlzLmFsbEBpZXRmLm9y
ZywgSm9obiBDb3dhbiAmbHQ7Y293YW5AY2NpbC5vcmcmZ3Q7LCBpZXRmQGlldGYub3JnLCBzZWNk
aXJAaWV0Zi5vcmcsIGpzb25AaWV0Zi5vcmcsIEJlbmphbWluIEthZHVrICZsdDtrYWR1a0BtaXQu
ZWR1Jmd0OyA8L2Rpdj48ZGl2PlN1YmplY3Q6IFJlOiBbSnNvbl0gc2VjZGlyIHJldmlldyBvZiBk
cmFmdC1pZXRmLWpzb25iaXMtcmZjNzE1OWJpcy0wMyA8L2Rpdj48ZGl2Pjxicj48L2Rpdj48L2Rp
dj5PbiAxMS8wMy8yMDE3IDE1OjQxLCBOZWQgRnJlZWQgd3JvdGU6PGJyPiZndDsmZ3Q7IE9uIDIw
MTctMDMtMTEgMDM6MDgsIEpvaG4gQ293YW4gd3JvdGU6PGJyPiZndDsmZ3Q7ICZndDs8YnI+Jmd0
OyZndDsgJmd0OyBPbiBUaHUsIE1hciA5LCAyMDE3IGF0IDEyOjUzIEFNLCBCZW5qYW1pbiBLYWR1
ayAmbHQ7a2FkdWtAbWl0LmVkdTxicj4mZ3Q7Jmd0OyAmZ3Q7ICZsdDttYWlsdG86a2FkdWtAbWl0
LmVkdSZndDsmZ3Q7IHdyb3RlOjxicj4mZ3Q7Jmd0OyAmZ3Q7PGJyPiZndDsmZ3Q7ICZndDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgSWYgdGhhdCdzIHdoYXQncyBzdXBwb3NlZCB0byBoYXBwZW4s
IGl0IHNob3VsZCBwcm9iYWJseSBiZSBtb3JlPGJyPiZndDsmZ3Q7ICZndDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgY2xlYXIsIHllcy4mbmJzcDsgKEJ1dCBhcmVuJ3QgdGhlcmUgdGV4dHMgdGhh
dCBoYXZlIHZhbGlkPGJyPiZndDsmZ3Q7IGludGVycHJldGF0aW9uczxicj4mZ3Q7Jmd0OyAmZ3Q7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGluIG11bHRpcGxlIGVuY29kaW5ncz8pPGJyPiZndDsm
Z3Q7ICZndDs8YnI+Jmd0OyZndDsgJmd0Ozxicj4mZ3Q7Jmd0OyAmZ3Q7IE5vdCBpZiB0aGUgY29u
dGVudCBpcyB3ZWxsLWZvcm1lZCBKU09OIGFuZCB0aGUgb25seSBwb3NzaWJsZSBlbmNvZGluZ3M8
YnI+Jmd0OyZndDsgJmd0OyBhcmUgVVRGLTgsIFVURi0xNiwgYW5kIFVURi0zMi4mbmJzcDsgSXQg
c3VmZmljZXMgdG8gZXhhbWluZSB0aGUgZmlyc3QgZm91cjxicj4mZ3Q7Jmd0OyAmZ3Q7IGJ5dGVz
IG9mIHRoZSBpbnB1dC4mbmJzcDsgSWYgdGhlcmUgYXJlIG5vIE5VTCBieXRlcyBpbiB0aGUgZmly
c3QgZm91ciBieXRlcyw8YnI+Jmd0OyZndDsgJmd0OyBpdCBpcyBVVEYtODsgaWYgdGhlcmUgYXJl
IHR3byBOVUwgYnl0ZXMsIGl0IGlzIFVURi0xNjsgaWYgdGhlcmUgYXJlPGJyPiZndDsmZ3Q7ICZn
dDsgdGhyZWUgTlVMIGJ5dGVzLCBpdCBpcyBVVEYtMzIuJm5ic3A7IFRoaXMgd29ya3MgYmVjYXVz
ZSB0aGUgZ3JhbW1hciByZXF1aXJlczxicj4mZ3Q7Jmd0OyAmZ3Q7IHRoZSBmaXJzdCBjaGFyYWN0
ZXIgdG8gYmUgaW4gdGhlIEFTQ0lJIHJlcGVydG9pcmUsIGFuZCB0aGUgTlVMPGJyPiZndDsmZ3Q7
ICZndDsgKmNoYXJhY3RlciogKFUrMDAwMCkgaXMgbm90IGFsbG93ZWQgYXQgYWxsLjxicj4mZ3Q7
PGJyPiZndDsmZ3Q7IEdvb2QgZXhwbGFuYXRpb24uIE1heWJlIHRoZSBzcGVjIHNob3VsZCBpbmNs
dWRlIGl0Ljxicj4mZ3Q7PGJyPiZndDsgKzE8YnI+Jmd0Ozxicj4mZ3Q7IFRoaXMgZXhhY3QgaXNz
dWUganVzdCBjYW1lIHVwIGluIGEgbWVkaWEgdHlwZSByZXZpZXcsIHdoZXJlIHNvbWVvbmU8YnI+
Jmd0OyBzcGVjaWZpZWQgYSBjaGFyc2V0IHBhcmFtZXRlciBiZWNhdXNlIHRoZXkgd2VyZW4ndCBh
d2FyZSBvZiB0aGlzIGFsZ29yaXRobS48YnI+Jmd0Ozxicj4mZ3Q7IEl0IHdvdWxkIGJlIHZlcnkg
aGVscGZ1bCB0byBoYXZlIHRoaXMgdGV4dCBpbiB0aGUgUkZDLjxicj48YnI+PGJyPkFsdGhvdWdo
IGl0IGRvZXMgbmVlZCBzbGlnaHRseSBtb3JlIGRldGFpbCB0byB0YWtlIGludG8gYWNjb3VudCA8
YnI+ZW5kaWFuLW5lc3MgaW4gdGhlIGNhc2Ugb2YgVVRGLTE2IGFuZCAtMzIuPGJyPjxicj5UaGUg
WE1MIHNwZWMgbWF5IG9mZmVyIHNvbWUgZXhhbXBsZSB0ZXh0Ojxicj48YnI+aHR0cHM6Ly93d3cu
dzMub3JnL1RSLzIwMDgvUkVDLXhtbC0yMDA4MTEyNi8jc2VjLWd1ZXNzaW5nPGJyPjxicj5QZXRl
IENvcmRlbGw8YnI+Q29kYWxvZ2ljIEx0ZDxicj5SZWFkICZhbXA7IHdyaXRlIFhNTCBpbiBDKyss
IGh0dHA6Ly93d3cueG1sMmNwcC5jb208YnI+PGJyPjwvYm9keT48L2h0bWw+

----_com.samsung.android.email_4565109410242090--


From nobody Sun Mar 12 23:24:01 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20A69129540; Sun, 12 Mar 2017 23:23:52 -0700 (PDT)
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=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aHxwCLL0wakQ; Sun, 12 Mar 2017 23:23:51 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E161128B37; Sun, 12 Mar 2017 23:23:50 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.107.79]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LhTjQ-1cROm21uBk-00mZwW; Mon, 13 Mar 2017 07:23:22 +0100
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Elwyn Davies <elwynd@dial.pipex.com>, Peter Cordell <petejson@codalogic.com>, Ned Freed <ned.freed@mrochek.com>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de>
Date: Mon, 13 Mar 2017 07:23:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:ONAqVCTvpdU/oTq78wPt92ZoUiWczEgP+MlfZwRy2qEVtlFKnSA p1ebcexiZx5Nc33PxzOMmpeICWFJvTXl86sY0vvwt9PTFS+DUL+tJgSenbqqqo9ipcxUCL1 0e3g72J030txLwaop68Lkut4jNUgh07fOUumSc3YVIrWbNOmekZmYCCVPmIRBt8KO3hRSiG mQeKnrCNdT9s75Usbs0Eg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:8bWtMcdviHI=:tsV1/zi7YPzEWA9zPU02wZ Qn1QQMA1Z/V6Mz3s/tbuyoK6NNu1n+W26wyFligSGhq4+k4X2nA0AgTHGTQwR5ZF1ZEtwYuw4 S8boytoF9IFmUPBxR0vai/hWrjQi8xLTHhz+j7tC1gu7u8T6rSIfKiXk3T5XWUhZYlkF3mSWM RUtU4hFfy//NIS+ACroOVat2vGwtC1m2rPDHYB4m8wYeo+dJDV/uydazEXi2jGIV8QNgYfjCn vxIYkAenSBlZw1SFClmBg08nHLVnFQUt1Yo55OrTieABa/otwjCfuqpiWoRPwfu1idEz86y+0 4L7qRu4DOqYoxH3dB3YktoqG07UfI3Kp6k0P+PcMxxK9qMfrpU3vkpF5evyV9o/8Giznjuh8m P4lkM2heiorEoL4Ozr8hHnD/prZKKjFWQAwMNNy/okguAkeylTBE9RTNY1qBXplLTJOIz1auZ zvaifaa9tyUmQUXnCZQvFGCqJYr8pxiYgklSNhci8MCbagQpK60P+/8c5e+eHBD/k++9eaCM1 rHOzvU6YS1g5aUNFJJSGXyRU+Cn0DzzoDMdQ4GUMn6MwqMGUI8GvT5/cAHxEyj/D/9SdRa2dL 2Pi2mqYAQjAg3ffv3w38YxeICfGsXtQAPkBtlQe/AmS1WHl5baN59jaYWI+n9gz/YeCi9x1g9 3L8fyByb7d/lXHI6fl30pdEJIgUqkzctd4V2GoUoyb2qSJr0t3HrVhkj8Pm88MuH522KRFATH DilpeNRGsu7km+PB+2m0rEfY9APvetxg6V8ZI9kAAZP7eMW8RmZ4dj1XLK5TTkpZMfd+N/2LE 4NRozLK
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U-wr_vbMqF-WQu0ywzUdLTt-SIc>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, ietf@ietf.org, secdir@ietf.org, "json@ietf.org" <json@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 06:23:52 -0000

On 2017-03-13 00:07, Elwyn Davies wrote:
> (with half a Gen-art hat on...)
>
> Does the WG really want to revisit the anguished discussions that
> resulted in the changes to Section 8.1 of draft-ietf-json-rfc4627bis
> between versions 07 and 08 back in late November 2013?
>
> See https://www.ietf.org/mail-archive/web/json/current/msg02053.html and
> many, many messages beore this.
>
> Cheers,
> Elwyn

No, but on the other hand, we should acknowledge that apparently the 
text both about what's mandatory and how auto detection works is not as 
clear as it should.

Best regards, Julian


From nobody Mon Mar 13 01:15:06 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFC512954F; Mon, 13 Mar 2017 01:14:57 -0700 (PDT)
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=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7MoIEE3uTZNk; Mon, 13 Mar 2017 01:14:56 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B308C12954B; Mon, 13 Mar 2017 01:14:55 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.107.79]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LtmK9-1c4cIa29Jt-011E0q; Mon, 13 Mar 2017 09:14:21 +0100
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Carsten Bormann <cabo@tzi.org>
References: <20170308014823.GF30306@kduck.kaduk.org> <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com> <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de> <01QBU8WJOCUO0003XB@mauve.mrochek.com> <6d97dee7-7cf3-9142-aacf-f2ca4909103d@codalogic.com> <cbbd0224-da58-bac5-b751-4195dd7383dc@gmx.de> <38DEEE0A-EE2C-4ADA-9D7A-9DBBAEACB77E@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <b9908499-a24d-5a6c-b22e-9f2c0cfaa4a5@gmx.de>
Date: Mon, 13 Mar 2017 09:14:16 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <38DEEE0A-EE2C-4ADA-9D7A-9DBBAEACB77E@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:fWQpqIOlZcKxDu5xBlzvlzJnn26z6FzeULN6WCf50r/8/Yne2mh e1MkUm3aEJWfG+K79cVEwYHhM3XjF2TfUTPgXvUjnOeTVppMGmk6GTqMr2pfgXTqycuBp8h J1luWn3ohP+H8RICiE6aBNp7v3wddMcHfr38VppEp9K3D1OqZNX48juJL63oeofujQV5T7N 4WU42vS1URl/lOweYEoaA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:xdE/QCy07zU=:V99Oi0COQu3ylkgTUKN2Su rVXu6hlj0Lz1UbszMqWHJB37Rx9tWvBY2+yt3AjFS9+OYxQX6NUzD3ydpKafeOPfAm4myFyVc XTUJJnko3S7ImVTW7G+zfPx5euYz7EfYvGkAH1UtZd0ci4I2uYwIWfC4HBzUH+Y9A/mbQfCPj TfQ/jH5WdzafW0KMyTnC3V6z+sfT2An/9RPfFeFfe0cQfVMFaTvgAC1WZVeJBMPqMgpGN6kdJ Do9i8zYD/0LzmUbcKft/x0dkwHqfavOFhKIC37xNVVvFlrUpZMbjxRMtUzPVZpSq4dDGooi2b F/TlYtWgtk0YJ3FURoiH7EbwJ0bp3JeCqskRVfzNr9OBMucRLeNIWfr219dEQI0FZL9/9IjEY P8XWchbf76hjVCcyj0V1m9JTkcJtVTqFX+kCJGZzriRWyYe8ZlD0/fYn/IKPAIdCcNntVMwZ6 PDRycNWw1+JvIQVTcznQaimPTXNfR5/YLlB621IBjygSS/0QZfwk/jHfD5K1ij2+yRGNy1tvG sG2t+J5g02FxuFFptNTjNXHM5XBxHxAakbA7x/xdqtpaRmCbgTTobxxJ923rXDlcODTUw0fbV EtMMDYthnkPEvKtmWQvFlNt4Iz86aNhmY39UFh7QFohdM5g4k5Qy6cd1DtqeyE/VuFdLD2LOY yOewJvJsUv8Myg0KZKliiIqY03QReq3qBM3WkF8jRsMGpREFRJrrzDLvbV6SwoWljcKQUItHP 72/AmhRmbdDOWN/uL2E7GyWY62CookgZk+Tw6DoHgMXIO2+dmeWp/6O30DfoUT6ewiyxEhIQt FQVTzW9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wZO33R4Y5usJVUrOdjqPSEFltJE>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, Ned Freed <ned.freed@mrochek.com>, IETF <ietf@ietf.org>, Peter Cordell <petejson@codalogic.com>, secdir@ietf.org, "json@ietf.org" <json@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 08:14:57 -0000

On 2017-03-12 16:31, Carsten Bormann wrote:
> On 12 Mar 2017, at 10:14, Julian Reschke <julian.reschke@gmx.de> wrote:
>>
>> Does anybody recall why we removed <https://tools.ietf.org/html/rfc4627#section-3>:
>
> I seem to remember that the advice simply is no longer working since JSON was extended from 4627 to 7159.  Instead of trying to come up with an updated algorithm, the WG recognized that this is not a real-world problem.
 > ...

So the changes in RFC 7159 allow top-level strings, so we can't rely on 
the first *two* characters being US-ASCII. But we *can* rely on the 
first one being US-ASCII, no?

So the following should still be correct:

>    Since the first character of a JSON text will always be an ASCII
>    character [RFC0020], it is possible to determine whether an octet
>    stream is UTF-8, UTF-16 (BE or LE), or UTF-32 (BE or LE) by looking
>    at the pattern of nulls in the first four octets.
>
>            00 00 00 xx  UTF-32BE
>            00 xx xx xx  UTF-16BE
>            xx 00 00 00  UTF-32LE
>            xx 00 xx xx  UTF-16LE
>            xx xx xx xx  UTF-8

Best regards, Julian


From nobody Mon Mar 13 08:02:03 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 515281294AD for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 08:02:02 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kILacCdqWJzO for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 08:02:00 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91B2B129418 for <ietf@ietf.org>; Mon, 13 Mar 2017 08:02:00 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id i34so33553321qtc.0 for <ietf@ietf.org>; Mon, 13 Mar 2017 08:02:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=9PM07QpsxILhAce5y1sgHSyzPf7H0EGzCEIVWELZxy0=; b=NE0ZgXMF+Q8QFNwbuHq0OsgUsMVkFfeYKQkJWIhUMRovHLdM10iGpFzekLxXKrXimI NjvHRFFVMma4K0wTrq6OXr/BEBLLK1UMGUYVA+fGLCCurAm4/Lc09Xr1/UcQetRyc/a0 /yr7RxSy1I7wR3YEZ2l3PwAeCemk4IN7Q+84d5g+8D32JVdBc3d+UeAQFK9+3KRyLR2A 6sUJW8RcoJMoJcXp0czbBdtFnTq2hrLs4MSurn1OaQdJ6mX0MB7FXW3B+gpCLMAgeTI+ 5RIQ3Bx8bCB1jVMyXM1aSgra83wYCNFU8TWvdAbU4hTTQnhZmOJhOvHnzEe6oBohBvQ6 LLMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=9PM07QpsxILhAce5y1sgHSyzPf7H0EGzCEIVWELZxy0=; b=rHMLvdeEhXWsTkkHNvjdn5NGxeLlXa21sy19Jys5/dpXAmnmDFUEZfwnjcu7g6vOsf zRZv1gr1eZ09S/6VDXIyz2+aoiC35dduG0UKw9XeLb/46bfsLeYN/9wyS6LzwWFLuwdP CzpR+1aSEjy6j3pn45IfGgsQRyR8QvMohSCFshjUOQiM49/0/9Zyt6k0bjEvIY+kIVHV VlhZTkVlUDRDXsthKm9A7r9aXlJUd7tA5JEYuyh1mo5Hm0GaWQg2+6vVTgC04gfZobpC t9I6T3vga53oRDJ+cgOOuUYFzSJ62rlwexdMzfHIxwxhoMja7yKsHI3SjOlrfjVr2xFA 30DQ==
X-Gm-Message-State: AMke39kuITPC9R/dyCF7mjS3LvrBRb91L/gw9xuXWqffKm05ekUeA56nO4AjMT+xgASsqQ==
X-Received: by 10.200.52.65 with SMTP id v1mr35419364qtb.166.1489417319276; Mon, 13 Mar 2017 08:01:59 -0700 (PDT)
Received: from [10.0.20.202] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id j4sm12331361qkc.40.2017.03.13.08.01.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Mar 2017 08:01:58 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <CC5E2EDA-5533-4FA0-8350-CE45311DD8B4@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FDE8B84A-470E-471D-A247-E4B7464CEF07"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: The CIA mentions us
Date: Mon, 13 Mar 2017 11:01:57 -0400
In-Reply-To: <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com> <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eb7qm73aamlaTEvJtEDySEsOMkQ>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 15:02:02 -0000

--Apple-Mail=_FDE8B84A-470E-471D-A247-E4B7464CEF07
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Mar 10, 2017, at 9:02 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
> I don't think your optimistic conclusion here follows, for two
> reasons. Firstly, we've seen that the adversary here is not
> driven by economic concerns and will attack not just a weakest
> link, but all possible targets they can afford given their very
> very large budgets. [...]

> And while I do think that the actions that many people in the
> Internet community and in the IETF have taken have probably
> made pervasive monitoring harder and/or more costly, I do not
> think that's really that relevant to this particular leak. In
> this case, I think the much more interesting thing is that
> this is yet another demonstration that attack code that is
> intended to be used for attacks (as opposed to demonstration)
> is in the end hugely counter-productive. (And immoral too IMO,
> but I'd not claim that we all need to agree with that last;-)

True   OTOH, there's a good editorial in the NY Times recently that =
speaks to the points you've raised: =
https://www.nytimes.com/2017/03/09/opinion/the-truth-about-the-wikileaks-c=
ia-cache.html =
<https://www.nytimes.com/2017/03/09/opinion/the-truth-about-the-wikileaks-=
cia-cache.html>

I think the main thing is that yes, of course, a state actor with =
unlimited resources can hack every hackable device indiscriminately.   =
But widespread encryption means that they have to do that.   And doing =
that is _much_ harder than intercepting passively, and more importantly, =
it's more detectable.   I am surprised that you find my response =
optimistic.   I feel pretty cynical about the situation.   I just =
believe that we have done some things that have improved matters, and =
that's worth mentioning.


--Apple-Mail=_FDE8B84A-470E-471D-A247-E4B7464CEF07
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Mar 10, 2017, at 9:02 PM, Stephen Farrell &lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
class=3D"">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D"">I don't think your =
optimistic conclusion here follows, for two<br class=3D""><div =
class=3D""><div class=3D"">reasons. Firstly, we've seen that the =
adversary here is not<br class=3D"">driven by economic concerns and will =
attack not just a weakest<br class=3D"">link, but all possible targets =
they can afford given their very<br class=3D"">very large budgets. =
[...]</div></div></blockquote><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">And while I do think that the =
actions that many people in the<br class=3D"">Internet community and in =
the IETF have taken have probably<br class=3D"">made pervasive =
monitoring harder and/or more costly, I do not<br class=3D"">think =
that's really that relevant to this particular leak. In<br class=3D"">this=
 case, I think the much more interesting thing is that<br class=3D"">this =
is yet another demonstration that attack code that is<br =
class=3D"">intended to be used for attacks (as opposed to =
demonstration)<br class=3D"">is in the end hugely counter-productive. =
(And immoral too IMO,<br class=3D"">but I'd not claim that we all need =
to agree with that last;-)<br =
class=3D""></div></div></blockquote></div><br class=3D""><div =
class=3D"">True &nbsp; OTOH, there's a good editorial in the NY Times =
recently that speaks to the points you've raised:&nbsp;<a =
href=3D"https://www.nytimes.com/2017/03/09/opinion/the-truth-about-the-wik=
ileaks-cia-cache.html" =
class=3D"">https://www.nytimes.com/2017/03/09/opinion/the-truth-about-the-=
wikileaks-cia-cache.html</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">I think the main thing is that yes, of =
course, a state actor with unlimited resources can hack every hackable =
device indiscriminately. &nbsp; But widespread encryption means that =
they have to do that. &nbsp; And doing that is _much_ harder than =
intercepting passively, and more importantly, it's more detectable. =
&nbsp; I am surprised that you find my response optimistic. &nbsp; I =
feel pretty cynical about the situation. &nbsp; I just believe that we =
have done some things that have improved matters, and that's worth =
mentioning.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_FDE8B84A-470E-471D-A247-E4B7464CEF07--


From nobody Mon Mar 13 08:56:41 2017
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 C9E16129432; Mon, 13 Mar 2017 08:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5Czki8HfRA5; Mon, 13 Mar 2017 08:56:38 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63F381270B4; Mon, 13 Mar 2017 08:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2DFuY68002705; Mon, 13 Mar 2017 16:56:34 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vhjCk4LlrzDGt5; Mon, 13 Mar 2017 16:56:34 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp>
Date: Mon, 13 Mar 2017 16:56:33 +0100
X-Mao-Original-Outgoing-Id: 511113393.671415-a4a40423d1a75bc00add897e6d0ad1b2
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DFA075D-3F19-48B3-821D-79EA3CB4A908@tzi.org>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com> <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de> <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp>
To: =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YsjLPVfkbVgfOb8ORuUvDwn0i7c>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>, IETF <ietf@ietf.org>, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 15:56:40 -0000

+1000

Gr=C3=BC=C3=9Fe, Carsten

> On 13 Mar 2017, at 08:51, Martin J. D=C3=BCrst =
<duerst@it.aoyama.ac.jp> wrote:
>=20
> On 2017/03/13 15:23, Julian Reschke wrote:
>> On 2017-03-13 00:07, Elwyn Davies wrote:
>=20
>>> Does the WG really want to revisit the anguished discussions that
>>> resulted in the changes to Section 8.1 of draft-ietf-json-rfc4627bis
>>> between versions 07 and 08 back in late November 2013?
>>>=20
>>> See https://www.ietf.org/mail-archive/web/json/current/msg02053.html =
and
>>> many, many messages beore this.
>=20
>> No, but on the other hand, we should acknowledge that apparently the
>> text both about what's mandatory and how auto detection works is not =
as
>> clear as it should.
>=20
> It looks to me as if at the time of the above message in the WG, the =
chairs were successful in presenting a consensus, probably at a stage =
when the participants in the discussion where getting tired.
>=20
> It seems that when put in the wider context of the IETF, that =
compromise now looks somewhat shaky.
>=20
> My personal opinion is that we could try to fix this by changing the =
following:
>=20
>>>>>=20
>  JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32 [UNICODE]
>  (Section 3).  The default encoding is UTF-8, and JSON texts that are
>  encoded in UTF-8 are interoperable in the sense that they will be
>  read successfully by the maximum number of implementations; there are
>  many implementations that cannot successfully read texts in other
>  encodings (such as UTF-16 and UTF-32).
>>>>>=20
>=20
> to something like the following:
>=20
>>>>>=20
>  JSON text SHOULD be encoded in UTF-8 [UNICODE]
>  (Section 3).  JSON texts that are
>  encoded in UTF-8 are interoperable in the sense that they will be
>  read successfully by the maximum number of implementations.
>=20
>  There are
>  many implementations that cannot successfully read texts in other
>  encodings (such as UTF-16 and UTF-32). JSON text MAY be encoded in
>  UTF-16 or UTF-32 [UNICODE] (Section 3) if the sender is sure that
>  the intended recipients can read them.
>>>>>=20
>=20
> That should then go together with a MIME registration that only lists =
UTF-8.
>=20
> Regards,   Martin.
>=20
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>=20




From nobody Mon Mar 13 09:02:03 2017
Return-Path: <stefan@dilettant.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10FFF129771 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 09:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlwnHFBUlnR0 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 09:02:00 -0700 (PDT)
Received: from mailrelay2.pub.mailoutpod1-wdc1.one.com (mailrelay2.pub.mailoutpod1-wdc1.one.com [104.37.35.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD22C1297BC for <ietf@ietf.org>; Mon, 13 Mar 2017 09:02:00 -0700 (PDT)
X-HalOne-Cookie: 9db20b3b3eef183271b7f381933937b44264d427
X-HalOne-ID: 601bc2a5-0806-11e7-b39d-549f35fe4221
Received: from [10.86.247.37] (unknown [198.135.0.233]) by mailrelay1.pub.mailoutpod1-wdc1.one.com (Halon) with ESMTPSA id 601bc2a5-0806-11e7-b39d-549f35fe4221; Mon, 13 Mar 2017 16:01:58 +0000 (UTC)
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com> <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de> <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp>
From: Stefan Hagen <stefan@dilettant.eu>
Message-ID: <bf1db249-faf3-f0bd-76a4-5b73e816280e@dilettant.eu>
Date: Mon, 13 Mar 2017 17:01:52 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0uLoNnA-ezWgNgYlLMbNf98nWuo>
Cc: Benjamin Kaduk <kaduk@mit.edu>, draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 16:02:02 -0000

Yes, tired is a good match && I second the proposed change.
"Stefan"

On 13/03/17 08:51, Martin J. Dürst wrote:
> On 2017/03/13 15:23, Julian Reschke wrote:
>> On 2017-03-13 00:07, Elwyn Davies wrote:
>
>>> Does the WG really want to revisit the anguished discussions that
>>> resulted in the changes to Section 8.1 of draft-ietf-json-rfc4627bis
>>> between versions 07 and 08 back in late November 2013?
>>>
>>> See https://www.ietf.org/mail-archive/web/json/current/msg02053.html and
>>> many, many messages beore this.
>
>> No, but on the other hand, we should acknowledge that apparently the
>> text both about what's mandatory and how auto detection works is not as
>> clear as it should.
>
> It looks to me as if at the time of the above message in the WG, the
> chairs were successful in presenting a consensus, probably at a stage
> when the participants in the discussion where getting tired.
>
> It seems that when put in the wider context of the IETF, that compromise
> now looks somewhat shaky.
>
> My personal opinion is that we could try to fix this by changing the
> following:
>
>>>>>
>    JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32 [UNICODE]
>    (Section 3).  The default encoding is UTF-8, and JSON texts that are
>    encoded in UTF-8 are interoperable in the sense that they will be
>    read successfully by the maximum number of implementations; there are
>    many implementations that cannot successfully read texts in other
>    encodings (such as UTF-16 and UTF-32).
>>>>>
>
> to something like the following:
>
>>>>>
>    JSON text SHOULD be encoded in UTF-8 [UNICODE]
>    (Section 3).  JSON texts that are
>    encoded in UTF-8 are interoperable in the sense that they will be
>    read successfully by the maximum number of implementations.
>
>    There are
>    many implementations that cannot successfully read texts in other
>    encodings (such as UTF-16 and UTF-32). JSON text MAY be encoded in
>    UTF-16 or UTF-32 [UNICODE] (Section 3) if the sender is sure that
>    the intended recipients can read them.
>>>>>
>
> That should then go together with a MIME registration that only lists
> UTF-8.
>
> Regards,   Martin.
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json


From nobody Mon Mar 13 09:40:20 2017
Return-Path: <petejson@codalogic.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D0A1296E3 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 09:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.919
X-Spam-Level: 
X-Spam-Status: No, score=-0.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Duo2EEb5vPC8 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 09:40:17 -0700 (PDT)
Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED54512951F for <ietf@ietf.org>; Mon, 13 Mar 2017 09:40:16 -0700 (PDT)
Received: (qmail 27794 invoked from network); 13 Mar 2017 16:26:18 +0000
Received: from host109-158-230-32.range109-158.btcentralplus.com (HELO ?192.168.1.72?) (109.158.230.32) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 13 Mar 2017 16:26:18 +0000
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>, Ned Freed <ned.freed@mrochek.com>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com> <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de> <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp>
From: Peter Cordell <petejson@codalogic.com>
Message-ID: <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com>
Date: Mon, 13 Mar 2017 16:33:33 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1_dS6WC9JtT0WklGU6arpUIuYbM>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 16:40:18 -0000

On 13/03/2017 07:51, Martin J. Dürst wrote:
> My personal opinion is that we could try to fix this by changing the
> following:
>
>>>>>
>    JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32 [UNICODE]
>    (Section 3).  The default encoding is UTF-8, and JSON texts that are
>    encoded in UTF-8 are interoperable in the sense that they will be
>    read successfully by the maximum number of implementations; there are
>    many implementations that cannot successfully read texts in other
>    encodings (such as UTF-16 and UTF-32).
>>>>>
>
> to something like the following:
>
>>>>>
>    JSON text SHOULD be encoded in UTF-8 [UNICODE]
>    (Section 3).  JSON texts that are
>    encoded in UTF-8 are interoperable in the sense that they will be
>    read successfully by the maximum number of implementations.
>
>    There are
>    many implementations that cannot successfully read texts in other
>    encodings (such as UTF-16 and UTF-32). JSON text MAY be encoded in
>    UTF-16 or UTF-32 [UNICODE] (Section 3) if the sender is sure that
>    the intended recipients can read them.
>>>>>

My only thought is to perhaps reflect that JSON isn't only transmitted, 
and JSON can be used for file based configuration etc, (even if this 
isn't strictly IETFs concern).  So perhaps s/sender/encoder/ in the last 
sentence, plus a few other tweaks yielding something like:

     There are many implementations that cannot successfully read texts
     in other encodings (such as UTF-16 and UTF-32 [UNICODE]).  JSON
     text MAY be encoded in other encodings if the encoder is sure that
     the intended recipients can read them.

Pete.
-- 
---------------------------------------------------------------------
Pete Cordell
Codalogic Ltd
http://json-content-rules.org/
---------------------------------------------------------------------


From nobody Mon Mar 13 10:03:39 2017
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 813DB1298A3 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qXtt9VpPms5 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:03:37 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76BFA12943C for <ietf@ietf.org>; Mon, 13 Mar 2017 10:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2DH3Xk2027625; Mon, 13 Mar 2017 18:03:33 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vhkj11tX6zDGvV; Mon, 13 Mar 2017 18:03:33 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20170301210033.1672.qmail@ary.lan>
Date: Mon, 13 Mar 2017 18:03:32 +0100
X-Mao-Original-Outgoing-Id: 511117412.490087-bd9954fd7ef87f7b8f3d863c603143ba
Content-Transfer-Encoding: quoted-printable
Message-Id: <C758AD84-F7DB-4520-A497-66CFBA8A48B1@tzi.org>
References: <20170301210033.1672.qmail@ary.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ABkFXMEODrHR2-Qi35BQRV2NIGk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 17:03:38 -0000

More SPF/DKIM fun.

Just got:

  ----- The following addresses had permanent fatal errors =E2=80=94=E2=80=
=94
<REDACTED@nist.gov>
   (reason: 450 4.7.26 Service does not accept messages sent over IPv6 =
[2001:638:708:30c9::12] unless they pass either SPF or DKIM validation =
(message not signed))

Whiskey Tango Foxtrot.

So they give their mail server an IPv6 address but then don=E2=80=99t =
accept certain messages on that that they would happily accept over =
IPv4.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Mar 13 10:21:38 2017
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 AE4351298A8 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HI3Q8VPo2YIK for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:21:36 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE7DE12989F for <ietf@ietf.org>; Mon, 13 Mar 2017 10:21:36 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2DHNWuO014683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 13 Mar 2017 10:23:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1489425812; bh=5TEpKzREEu8THan97073JufY/RJ1ayssK8Y/9L/iqUU=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=Vs0P7PFyXhPLPGHedteF7HVpGsF4GTtqcYL8EJNxHueIFbclZSOVcFTcrCIfZoYsx fjjcHVyvHaSSHFNxgG4V3ekBSbozq5Kro51UjsdxF0jWxGI9b5ildxmS6CcjdtPB+k 4h8kT/lXD27Jmt1J5bLemHgI2PncGDJd88AKO8Ys=
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
To: Carsten Bormann <cabo@tzi.org>, John Levine <johnl@taugh.com>
References: <20170301210033.1672.qmail@ary.lan> <C758AD84-F7DB-4520-A497-66CFBA8A48B1@tzi.org>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5e382acb-077c-87f3-7355-aa3bf913e78c@dcrocker.net>
Date: Mon, 13 Mar 2017 10:21:20 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <C758AD84-F7DB-4520-A497-66CFBA8A48B1@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CsFpjYpCAfgSSlFZV-rbpEi39Xo>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 17:21:37 -0000

On 3/13/2017 10:03 AM, Carsten Bormann wrote:
>    (reason: 450 4.7.26 Service does not accept messages sent over IPv6 [2001:638:708:30c9::12] unless they pass either SPF or DKIM validation (message not signed))
...
> So they give their mail server an IPv6 address but then don’t accept certain messages on that that they would happily accept over IPv4.


Email abuse across the open Internet remains impressively high. 
Typically above 90% of traffic.  There is a very strong undercurrent of 
desire amongst some email-receiving operators to require all mail to be 
authenticated, in order to facilitate accountability for email streams. 
That is, to have SPF and/or DKIM tests succeed.

Some of them have the view that the transition to IPv6 is a place to 
impose this stringent policy.

In one of the anti-abuse organizations, I've tried to point out the 
problems with imposing policy changes based on transport -- independent 
of whether the policy change is a good idea -- but to no avail.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Mar 13 10:28:21 2017
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 1F52C1298CF for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWo4gDm7tG8e for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:28:19 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E5F21298C0 for <ietf@ietf.org>; Mon, 13 Mar 2017 10:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2DHSAbr016862; Mon, 13 Mar 2017 18:28:10 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vhlFQ4dTpzDGw3; Mon, 13 Mar 2017 18:28:10 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5e382acb-077c-87f3-7355-aa3bf913e78c@dcrocker.net>
Date: Mon, 13 Mar 2017 18:28:09 +0100
X-Mao-Original-Outgoing-Id: 511118889.805799-0cc49d9f4d76020e3675b7dd337f8e0e
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEAA5E62-DD3A-4D62-8E78-204C24859A73@tzi.org>
References: <20170301210033.1672.qmail@ary.lan> <C758AD84-F7DB-4520-A497-66CFBA8A48B1@tzi.org> <5e382acb-077c-87f3-7355-aa3bf913e78c@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kKQRioSxALaRHUVmM7cjHQAUuXo>
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 17:28:20 -0000

Hi Dave,

I sure understand the problem that the scarcity-based address reputation =
hack won=E2=80=99t work that well on IPv6.  But the =E2=80=9Csolution=E2=80=
=9D=E2=80=A6  And NIST isn=E2=80=99t exactly Mom and Pop=E2=80=99s Bait =
and Internet Shop.

On 13 Mar 2017, at 18:21, Dave Crocker <dhc@dcrocker.net> wrote:
>=20
> In one of the anti-abuse organizations, I've tried to point out the =
problems with imposing policy changes based on transport -- independent =
of whether the policy change is a good idea -- but to no avail.

Well, to add insult to injury, this was a DEFER code, so our mail server =
tried for five days to deliver this; of course using IPv6 all the time.

No idea whether there is code around that can react to a DEFER with a =
change of source address.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Mar 13 10:36:07 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 39C74129975; Mon, 13 Mar 2017 10:35:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <secdir@ietf.org>
Subject: Review of draft-ietf-bess-evpn-vpws-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148942655619.16823.16137723889627774034@ietfa.amsl.com>
Date: Mon, 13 Mar 2017 10:35:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Uo3Hciit5CmLkhzgzHgyvk0qQJk>
Cc: draft-ietf-bess-evpn-vpws.all@ietf.org, ietf@ietf.org, bess@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 17:35:56 -0000

Reviewer: Matthew Miller
Review result: Ready

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should
treat these comments just like any other last call comments.

Document: draft-ietf-bess-evpn-vpws-11
Reviewer: Matthew A. Miller
Review Date: 2017-03-13
IETF LC End Date: 2017-03-10
IESG Telechat date: 2017-04-13

Summary:

This document is ready for publication as a Proposed Standard.

This document describes a method of supporting VPWS using the
principles of EVPN from RFC 7432.  In essence, a profile of RFC 7432
for implementing VPWS.

Major Issues: NONE

Minor Issues: NONE

Nits: NONE



From nobody Mon Mar 13 10:43:30 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E670E129412 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=Dqer22Bh; dkim=pass (1536-bit key) header.d=taugh.com header.b=AyHBihG8
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0n8mNwsBQmxT for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:43:24 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8504D12997E for <ietf@ietf.org>; Mon, 13 Mar 2017 10:43:24 -0700 (PDT)
Received: (qmail 17519 invoked from network); 13 Mar 2017 17:43:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-id:user-agent; s=446d.58c6da3b.k1703; bh=dVSoATQfb4oukGA/u1pV2qF743V3+K7dQ2NTIhVuHmg=; b=Dqer22BhITZkSDdqmyEhhT9S026SvrTM60P4sSf9ZYVme9X7D1RPWwf2dedLD1XPRTxd7BqzUx7REv4DcFDJExYVottiNnG8ohNzOnA+aekRuvRa6Oy4l4puzfEjG6rEr4QUB1FtNj7tXVEWb1rx1EVIS14tazSoV0cLdcL5ZLcvUcaEPueGHZN5JSR1UibMy3zFPAX2U5pyJEM1Xe5nxDMnaG+JXYSoRSnkOjRZlzeQXlzd3KhJM4lxS7/d/DWF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-id:user-agent; s=446d.58c6da3b.k1703; bh=dVSoATQfb4oukGA/u1pV2qF743V3+K7dQ2NTIhVuHmg=; b=AyHBihG8Q5D29MAv07vro7YbumtiDEtWeCOFgoaCqUdes24ciL8UMSrttm08FTQaBgTF717qunplgpWyaCodGVEFVgbLLhpWi6SIHyNSkRBvTTMcggLhmetOVvQNwl/T17Cv1t9/RJSeE4HB5RnDIMTA45/ASyuVM0BFzEc0EazV4aYWHUMe1Q6LHVjkXWQGCz2xNme5Y2B5lgR0hm5BCO66DVEuN9vMl9nsTY1D+Jf5cyOliLD+cgMLtx1gyM2D
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 13 Mar 2017 17:43:22 -0000
Date: 13 Mar 2017 18:43:21 +0100
Message-ID: <alpine.OSX.2.20.1703131838100.54839@ary.local>
From: "John R Levine" <johnl@taugh.com>
To: "Carsten Bormann" <cabo@tzi.org>
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
In-Reply-To: <EEAA5E62-DD3A-4D62-8E78-204C24859A73@tzi.org>
References: <20170301210033.1672.qmail@ary.lan> <C758AD84-F7DB-4520-A497-66CFBA8A48B1@tzi.org> <5e382acb-077c-87f3-7355-aa3bf913e78c@dcrocker.net> <EEAA5E62-DD3A-4D62-8E78-204C24859A73@tzi.org>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="0-542573642-1489426949=:54839"
Content-ID: <alpine.OSX.2.20.1703131842530.54839@ary.local>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GDVzTAF6N2m96C4-ATozGIn1vr0>
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 17:43:27 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-542573642-1489426949=:54839
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Content-ID: <alpine.OSX.2.20.1703131842451.54839@ary.local>

> I sure understand the problem that the scarcity-based address reputation hack won’t work that well on IPv6.  But the “solution”…  And NIST isn’t exactly Mom and Pop’s Bait and Internet Shop.

Nor is gmail, which also requires that incoming IPv6 mail be authenticated 
with SPF or DKIM.  They know what they are doing, and they have decided 
that the amount of legit mail they will lose by doing this is 
insignificant compared to the improvement in the amount of spam and 
malware they will be able to filter.

You can complain about how stupid they are or you can upgrade your mail 
system to use authentication methods that have been IETF standards for a 
decade and get your mail delivered.  Your choice.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

PS:
> No idea whether there is code around that can react to a DEFER with a 
> change of source address.

Unless it changes to an IPv4 address, it won't help.
--0-542573642-1489426949=:54839--


From linuxwolf@outer-planes.net  Mon Mar 13 10:54:35 2017
Return-Path: <linuxwolf@outer-planes.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 9B575129992 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:54:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id koGJNoMLZKmu for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 10:54:34 -0700 (PDT)
Received: from mail-ot0-x241.google.com (mail-ot0-x241.google.com [IPv6:2607:f8b0:4003:c0f::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F9E1129981 for <ietf@ietf.org>; Mon, 13 Mar 2017 10:54:34 -0700 (PDT)
Received: by mail-ot0-x241.google.com with SMTP id x37so17063569ota.1 for <ietf@ietf.org>; Mon, 13 Mar 2017 10:54:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=wEbeRnfrEJpJCcOfo7g1t8EaTyJZIPY3KDqJZdcUzPk=; b=Zfif2koxCi00cBJulqzDvjWpIOzV9L6euL24Av4Ijo7ZS0Yrh6WNOQ0SAAnGyJDDuw 8LjBlfWv/IJzDEG7R/vDl680L9/iTmSB6UIAOltXBFJ1fWFLplm007xGNF6Tt/knN0Sc 2vZTqob98VrdG8LSjFZ36EkN1PWsEqSm9SQ9y7Ee0vGYvx42Lx9UZKFXG9G+XMk28Fbb SO96WOt0b5eCalMBH+BqH2JmO7kqbNPK+maAF6rMDkrGL+3wqlpSqaGxHotkaEvxQTYA 0/cloTgwiL+xtRK1+6JNhOCnTDrF3fyiAzmWyv8g/0H/kbjqCKgq+QK3cYCbLo2JokTc zHjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=wEbeRnfrEJpJCcOfo7g1t8EaTyJZIPY3KDqJZdcUzPk=; b=j3hnZXBFcDlfQBgrXbE8CYh9OW0k+oAIoaLCyCrin5RFFWqwzpv+wqu/d17ordafor E1gUuMDxHd3Z0nhRyvJwws9UCggboOp//bpEQ4lmW82UKObICwqI39TT5cIshFczrkS8 YJ7wtpY5ViCdMfq7XHxmTBcIisTUuQg2Jvj1g6LnVGlagXRnKaeFe9BFfDUdRXwHDhWp SM5XPBSyIvtAQrv0CHAOzB0ZAMSqMZdQ9zzH+z+fHh1qrLiuJ+U/xz6zF7Kq2yQgAgKj w1gu2h6D4QYvkO3MCX+K0qnLmXFxGJPpGJWOSR1ZuKq1785BIhzkk6V9jZU2Eb0W3PhR Lp4Q==
X-Gm-Message-State: AMke39l8lXb4+BeQii+2h6Zcth/73yi+50sSW24Y8jOcaI4ccjYW8GlworC7pU5NF5chZQ==
X-Received: by 10.157.84.10 with SMTP id j10mr16695392oth.257.1489427673447; Mon, 13 Mar 2017 10:54:33 -0700 (PDT)
Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id g10sm986961oic.16.2017.03.13.10.54.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Mar 2017 10:54:32 -0700 (PDT)
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Peter Cordell <petejson@codalogic.com>, =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>, Ned Freed <ned.freed@mrochek.com>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com> <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de> <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp> <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com>
From: "Matthew A. Miller" <linuxwolf@outer-planes.net>
Message-ID: <1e075450-d958-db9c-ae63-3cbf3733024c@outer-planes.net>
Date: Mon, 13 Mar 2017 11:54:31 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3VcLRe0FKbLrdelu3P9lctLR4SQJkGBjp"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S3eeAG-1Pocl4d0tnOTFCajvFkE>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 17:55:42 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--3VcLRe0FKbLrdelu3P9lctLR4SQJkGBjp
Content-Type: multipart/mixed; boundary="P4ru045D3n6aVvw0WOfe56vt1MQRTpI0D";
 protected-headers="v1"
From: "Matthew A. Miller" <linuxwolf@outer-planes.net>
To: Peter Cordell <petejson@codalogic.com>,
 =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>,
 Ned Freed <ned.freed@mrochek.com>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, ietf@ietf.org,
 secdir@ietf.org, "json@ietf.org" <json@ietf.org>
Message-ID: <1e075450-d958-db9c-ae63-3cbf3733024c@outer-planes.net>
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com>
 <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de>
 <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp>
 <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com>
In-Reply-To: <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com>

--P4ru045D3n6aVvw0WOfe56vt1MQRTpI0D
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 17/03/13 10:33, Peter Cordell wrote:
> On 13/03/2017 07:51, Martin J. D=C3=BCrst wrote:
>> My personal opinion is that we could try to fix this by changing the
>> following:
>>
>>>>>>
>>    JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32 [UNICODE]
>>    (Section 3).  The default encoding is UTF-8, and JSON texts that ar=
e
>>    encoded in UTF-8 are interoperable in the sense that they will be
>>    read successfully by the maximum number of implementations; there a=
re
>>    many implementations that cannot successfully read texts in other
>>    encodings (such as UTF-16 and UTF-32).
>>>>>>
>>
>> to something like the following:
>>
>>>>>>
>>    JSON text SHOULD be encoded in UTF-8 [UNICODE]
>>    (Section 3).  JSON texts that are
>>    encoded in UTF-8 are interoperable in the sense that they will be
>>    read successfully by the maximum number of implementations.
>>
>>    There are
>>    many implementations that cannot successfully read texts in other
>>    encodings (such as UTF-16 and UTF-32). JSON text MAY be encoded in
>>    UTF-16 or UTF-32 [UNICODE] (Section 3) if the sender is sure that
>>    the intended recipients can read them.
>>>>>>
>=20
> My only thought is to perhaps reflect that JSON isn't only transmitted,=

> and JSON can be used for file based configuration etc, (even if this
> isn't strictly IETFs concern).  So perhaps s/sender/encoder/ in the las=
t
> sentence, plus a few other tweaks yielding something like:
>=20
>     There are many implementations that cannot successfully read texts
>     in other encodings (such as UTF-16 and UTF-32 [UNICODE]).  JSON
>     text MAY be encoded in other encodings if the encoder is sure that
>     the intended recipients can read them.
>=20
> Pete.

/me doffs hat

I like this change myself.

/me dons hat

As I recall, the table was removed mostly because the vast majority of
implementations did not support any encoding other than UTF-8, and no
one (that I recall) reported implementing the detection table.


- m&m

Matthew A. Miller
< http://goo.gl/LM55L >


--P4ru045D3n6aVvw0WOfe56vt1MQRTpI0D--

--3VcLRe0FKbLrdelu3P9lctLR4SQJkGBjp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYxtzXAAoJEOz0ck4QngW72TMH/jkoqrQRrPao/VDYEP1PGOkc
BWzlZ0KS/UXrD2NEe0yx79A7iJaLeoLo0qLqdOXN/YJz8Cxp/iFOzAD2kFWe9hKf
82qb/vVqUSprF5gaLB3PhQ1Jdk0nLZPxR9CeuKY94atv4diV84amhkcpUpVe1Wua
OGvmstik2raeic/5eauMsX6dFgW1mifTbCKvBRlrH4nGQ7ovor+eqoua5DC72avI
t4u6buv/iLXzIZqqBj3Y2hl9meXq4KaqB024fPc25+eRps/8o9+izUFCXBAu56pA
2i3Y+YqaOktXWxaClIEJ9zCeH69sKQ8osuq7lLuJ53Ub2jbkVsFAES0N5JiWg9Y=
=jVS2
-----END PGP SIGNATURE-----

--3VcLRe0FKbLrdelu3P9lctLR4SQJkGBjp--


From nobody Mon Mar 13 10:58:46 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2433F12996B; Mon, 13 Mar 2017 10:58:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-ippm-model-based-metrics-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148942792412.9303.3309993074767595636@ietfa.amsl.com>
Date: Mon, 13 Mar 2017 10:58:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/whTVXctYsmWJWRGoOrDKbmNnaeU>
Cc: draft-ietf-ippm-model-based-metrics.all@ietf.org, ietf@ietf.org, ippm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 17:58:44 -0000

Reviewer: Robert Sparks
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ippm-model-based-metrics-10
Reviewer: Robert Sparks
Review Date: 2017-03-13
IETF LC End Date: 2017-03-14
IESG Telechat date: Not scheduled for a telechat

Status: Almost ready, but has significant issues to address before
publication as an Informational RFC

I'm guessing the goal for this document changed substantially during
its
development. The point and tone if the document changes depending on
where you are in it. I found it very difficult to read (and I did see
the
shepherd's report call out that the document has already had a strong
editorial pass).  It really feels to me that the purpose this document
is
trying to serve could be better achieved with two much shorter
documents.
Please consider pulling out the most important observations into its
own
informational document, and an experimental document that succinctly
presents the tests, the framework, and the feedback you want from
people
wo try these things.

Major issues:

There are issues with the equations in section 7.2. Please look at
the
line containing "Xa < defect_count(n) < Xb". Where is Xb defined? Was
it supposed to be Xr from further up the page? (or perhaps that Xr
should
have been Xb?

The document starts using 2119 MUSTs in section 7.3. None of the uses
are appropriate 2119 keywords - they aren't talking about protocol.
Please
rewrite the prose without using the 2119 keywords.

Section 8.2.4 seems to be missing an actual description/definition of
the 
test it is trying to talk about.


Minor issues:


The abstract says this document does not define tests. The rest of
the
document says it does. (See phrases like "The tests described in this
note")

Where the document claims it is neccessary to "suppress the effects
of
TCP congestion control", it should say "avoid the effects". The
mechanism
of using precalculated traffic patterns discussed in the document
avoids,
but does not suppress.

At the end of section 1, you call out "multiple standardized versions
of
TCP". Please clarify what you're trying to point to?

In the definition of "traffic patterns", you note that the goal is to
"mimic the range of common patterns". Consider qualifying that to
"current
common patterns", and add some discussion later in the document when
you
talk about pregenerating traffic patterns to point out that these
change
over time. 

At the next to last paragraph of section 4.1, you say "metrics have
entirely thwarted the analytic framework". I don't think that's what
you
mean. I suspect you mean to say attempts to create metrics have been
unsuccessful (I suggest you avoid the word "thwarted").

At the 3rd paragraph on page 19, you say "There is no model". Do you
mean
no model exists in the world for this, or only that this document does
not
provide a model.

I strongly object to the attempt to use "infinitesimal" to describe
the
conditions on the test network you are trying to convey. At the very
least,
you are dealing with a finite (if arbitrarily large) set of states
that
network can be in, not a continuum. You should be looking to raid
terms
from discrete mathematics instead, but I don't think even that's the
right
thing to do. Please replace the infinitesimal concept here with it's
definition (which you have to call out anyway). Just _say_ "has the
tightest available constraints that allow the tests to pass." 

Consider providing some rational for the numbers you came up with in
the
strawman in the second paragraph on page 33. 1mS seems pretty
arbitrary
otherwise. I'm not asking for you to _defend_ the choice as the right
number - just talk about why you picked it instead of something else.


Nits:

- Consider pointing to the models you are actually using in the first
  sentence of the first paragraph on page 9

- The third paragraph of the abstract is particularly hard to read.
Please
  consider breaking the compound sentences into simpler ones.

- You use "engineering test" before you say what you mean by that
(see
  sections 8.2.4 and 8.3.2 for examples)

- There are several places where you talk about tests being
inconclusive
  because the precomputed traffic was not accurately generated. Are
you
  trying to say "if you have an inconclusive test and can't otherwise
figure
  out why, look closely at your precomputed traffic", or "Double-check
your
  precomputed traffic before you run your test or risk
garbage-in/garbage
  out"?




From nobody Mon Mar 13 11:15:46 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E92D71299C0; Mon, 13 Mar 2017 11:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ussgnInrpS35; Mon, 13 Mar 2017 11:15:39 -0700 (PDT)
Received: from homiemail-a72.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57C891299B5; Mon, 13 Mar 2017 11:15:39 -0700 (PDT)
Received: from homiemail-a72.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTP id DE498A04E8C1; Mon, 13 Mar 2017 11:15:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=7GhDPymm6L2zak 9IaA5N6WJc+Qc=; b=jB4Jyp+tWcRj2Fh7/yBUtOOCEbjlAkS9QujnRvCAIH4YGK 1CLMWElg6YQ+5GvSJJyLTjmUmjMPu0g356Z/MRzDFvshdiG0wZCbI7B1jqr2PZ1N iKOmKhfyiVgOcBgBI4n5RtnhWsHBbNY8vdT2ZiNQpyCyQY/oKKP60mEJmRyK0=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTPSA id E4346A04E8C3; Mon, 13 Mar 2017 11:15:37 -0700 (PDT)
Date: Mon, 13 Mar 2017 13:15:34 -0500
From: Nico Williams <nico@cryptonector.com>
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [secdir] [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
Message-ID: <20170313181534.GD543@localhost>
References: <382aa5c8-c977-b24d-4d19-251257833b00@gmx.de> <456b4234-0d94-1033-507c-710878bb5159@gmx.de> <20170309055348.GL30306@kduck.kaduk.org> <CAD2gp_TOxcZJxwPoMhq-xp6M+Yq+tQnMUv81YNFp-ydRMpH=5w@mail.gmail.com> <bed0e331-f5fb-f24d-6207-f5a36ec9e7be@gmx.de> <01QBU8WJOCUO0003XB@mauve.mrochek.com> <6d97dee7-7cf3-9142-aacf-f2ca4909103d@codalogic.com> <cbbd0224-da58-bac5-b751-4195dd7383dc@gmx.de> <38DEEE0A-EE2C-4ADA-9D7A-9DBBAEACB77E@tzi.org> <b9908499-a24d-5a6c-b22e-9f2c0cfaa4a5@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b9908499-a24d-5a6c-b22e-9f2c0cfaa4a5@gmx.de>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mmiPi_QsJcQQl_dU8aeN5VJliOE>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, John Cowan <cowan@ccil.org>, Ned Freed <ned.freed@mrochek.com>, IETF <ietf@ietf.org>, Peter Cordell <petejson@codalogic.com>, secdir@ietf.org, "json@ietf.org" <json@ietf.org>, Carsten Bormann <cabo@tzi.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 18:15:40 -0000

On Mon, Mar 13, 2017 at 09:14:16AM +0100, Julian Reschke wrote:
> So the changes in RFC 7159 allow top-level strings, so we can't rely on the
> first *two* characters being US-ASCII. But we *can* rely on the first one
> being US-ASCII, no?

Correct.

If one OR two bytes of the first four are NULs, then the encoding is
UTF-16 (or something else or invalid):

> So the following should still be correct:
> 
> >   Since the first character of a JSON text will always be an ASCII
> >   character [RFC0020], it is possible to determine whether an octet
> >   stream is UTF-8, UTF-16 (BE or LE), or UTF-32 (BE or LE) by looking
> >   at the pattern of nulls in the first four octets.
> >
> >           00 00 00 xx  UTF-32BE
> >           00 xx xx xx  UTF-16BE
> >           xx 00 00 00  UTF-32LE
> >           xx 00 xx xx  UTF-16LE
> >           xx xx xx xx  UTF-8

Count the number of NULs in the first four bytes:

 - if zero -> UTF-8
 - if one or two -> UTF-16
 - if three -> UTF-32

Nico
-- 


From nobody Mon Mar 13 11:21:45 2017
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 EC9021294A0 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 11:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gqr3sJi_PwzC for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 11:21:42 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EF8412945E for <ietf@ietf.org>; Mon, 13 Mar 2017 11:21:42 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2DINb2u017023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 13 Mar 2017 11:23:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1489429417; bh=0AOFbJOlubmS8nlQua9OnS9jcP6dR4YsAHjow+Umxd0=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=mY2QTaoMtbu6X4V+ej9btTNyIApp3QtjLohd81ReGBBBtboOLW7A+1q3vRhSbQNwb 84SkOsWAkTwc82e8dhabd79O4NGWUG0kEVvtMIvuhmGy2Dj6ddR7kigj0CNLCneyfK 4YGHOUSLfqy8GUgAsKY8Ny473y09UIVZVZcR14Qc=
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
To: John R Levine <johnl@taugh.com>
References: <20170301210033.1672.qmail@ary.lan> <C758AD84-F7DB-4520-A497-66CFBA8A48B1@tzi.org> <5e382acb-077c-87f3-7355-aa3bf913e78c@dcrocker.net> <EEAA5E62-DD3A-4D62-8E78-204C24859A73@tzi.org> <alpine.OSX.2.20.1703131838100.54839@ary.local>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <ef9d9186-bfa2-2fd7-cb7f-0894f1620eaa@dcrocker.net>
Date: Mon, 13 Mar 2017 11:21:24 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.20.1703131838100.54839@ary.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GACU73goECejVXIv7I8AUmtU8f0>
Cc: Barry Leiba <barryleiba@computer.org>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 18:21:44 -0000

On 3/13/2017 10:43 AM, John R Levine wrote:
> You can complain about how stupid they are or you can upgrade your mail
> system to use authentication methods that have been IETF standards for a
> decade and get your mail delivered.  Your choice.


On the other hand, perhaps the IETF would consider formulating a 
suggestion to those who are embracing this policy change that they 
document it properly and publish it openly.

I suspect most/all of the adopters participate in M3AAWG and that a 
draft BCP effort from M3AAWG, submitted to the IETF either for BCP 
status or Independent Stream Informations, would be constructive.

So one might even consider having the IETF ask this to be communicated 
through the IETF/M3AAWG liaison(s)...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Mar 13 12:08:05 2017
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 3B60E12945C; Mon, 13 Mar 2017 12:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id crgrWPBgPlOC; Mon, 13 Mar 2017 12:08:01 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 875BC129A94; Mon, 13 Mar 2017 12:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2DJ7vNH006994; Mon, 13 Mar 2017 20:07:57 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vhnSY3CyjzDGxN; Mon, 13 Mar 2017 20:07:57 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <1e075450-d958-db9c-ae63-3cbf3733024c@outer-planes.net>
Date: Mon, 13 Mar 2017 20:07:56 +0100
X-Mao-Original-Outgoing-Id: 511124876.759257-e2d29302f2c69dd400e93e811df86b3f
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D76CB96-8AB6-4547-99C1-54490EC83DEF@tzi.org>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com> <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de> <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp> <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com> <1e075450-d958-db9c-ae63-3cbf3733024c@outer-planes.net>
To: "Matthew A. Miller" <linuxwolf@outer-planes.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ul3gK6yS934k2mV5PGvtVe0PcAY>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, secdir@ietf.org, IETF <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 19:08:03 -0000

On 13 Mar 2017, at 18:54, Matthew A. Miller <linuxwolf@outer-planes.net> =
wrote:
>=20
> no
> one (that I recall) reported implementing the detection table.

There even was one that implemented something for UTF-16/32: Jackson.
The author said:

"Most other
libraries just punt the problem by requiring caller to pass in Reader =
that
does byte->char decoding=E2=80=9D

(He did not say whether his code was ever exercised outside of his test =
cases :-)

He also mentioned that, by contrast, most XML libraries do implement =
auto-detection (as they should).

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Mar 13 12:14:18 2017
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 23E2612944A for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 12:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JyB0OlCcaJnc for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 12:14:16 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFA61129406 for <ietf@ietf.org>; Mon, 13 Mar 2017 12:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2DJEDPD012689; Mon, 13 Mar 2017 20:14:13 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vhnbm6RKLzDGxT; Mon, 13 Mar 2017 20:14:12 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <alpine.OSX.2.20.1703131838100.54839@ary.local>
Date: Mon, 13 Mar 2017 20:14:12 +0100
X-Mao-Original-Outgoing-Id: 511125252.12337-269b3912a596a1930927a2d5dd8dd7fd
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8793F66-E860-4CC1-80F8-D3C0B430C6AE@tzi.org>
References: <20170301210033.1672.qmail@ary.lan> <C758AD84-F7DB-4520-A497-66CFBA8A48B1@tzi.org> <5e382acb-077c-87f3-7355-aa3bf913e78c@dcrocker.net> <EEAA5E62-DD3A-4D62-8E78-204C24859A73@tzi.org> <alpine.OSX.2.20.1703131838100.54839@ary.local>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wmpRgxfcdpn3tGpyqMIssySO7oo>
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 19:14:17 -0000

On 13 Mar 2017, at 18:43, John R Levine <johnl@taugh.com> wrote:
>=20
> You can complain about how stupid they are or you can upgrade your =
mail system to use authentication methods that have been IETF standards =
for a decade and get your mail delivered.  Your choice.

The most likely outcome is that local admins will =E2=80=9Cupgrade" our =
mail system by turning off IPv6.  (We have had IPv6 deployed for some 18 =
years now.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Mar 13 12:47:12 2017
Return-Path: <ietf-dane@dukhovni.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 1592F1298AC for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 12:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zhs2hJ99MYmj for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 12:47:09 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1A4D129406 for <ietf@ietf.org>; Mon, 13 Mar 2017 12:47:08 -0700 (PDT)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id D5F1C7A330D; Mon, 13 Mar 2017 19:47:07 +0000 (UTC)
Date: Mon, 13 Mar 2017 19:47:07 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
Message-ID: <20170313194707.GF4095@mournblade.imrryr.org>
References: <20170301210033.1672.qmail@ary.lan> <C758AD84-F7DB-4520-A497-66CFBA8A48B1@tzi.org> <5e382acb-077c-87f3-7355-aa3bf913e78c@dcrocker.net> <EEAA5E62-DD3A-4D62-8E78-204C24859A73@tzi.org> <alpine.OSX.2.20.1703131838100.54839@ary.local> <A8793F66-E860-4CC1-80F8-D3C0B430C6AE@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <A8793F66-E860-4CC1-80F8-D3C0B430C6AE@tzi.org>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aMxRTa0T6m67b2LCwVAO5n1ID5w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 19:47:10 -0000

On Mon, Mar 13, 2017 at 08:14:12PM +0100, Carsten Bormann wrote:

> On 13 Mar 2017, at 18:43, John R Levine <johnl@taugh.com> wrote:

> > You can complain about how stupid they are or you can upgrade your mail
> > system to use authentication methods that have been IETF standards for a
> > decade and get your mail delivered.  Your choice.
> 
> The most likely outcome is that local admins will �upgrade" our mail system
> by turning off IPv6.  (We have had IPv6 deployed for some 18 years now.)

That's my approach at present:

    $ postconf -Mf smtp/unix
    smtp       unix  -       -       y       -       -     smtp
	-o inet_protocols=ipv4

-- 
	Viktor.


From nobody Mon Mar 13 12:52:01 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D653129481; Mon, 13 Mar 2017 12:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QydQ3BhgZX0V; Mon, 13 Mar 2017 12:51:58 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA194129453; Mon, 13 Mar 2017 12:51:57 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.107.79]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lr46Z-1cII7f2Pwp-00eZ4m; Mon, 13 Mar 2017 20:51:28 +0100
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: "Matthew A. Miller" <linuxwolf@outer-planes.net>, Peter Cordell <petejson@codalogic.com>, =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>, Ned Freed <ned.freed@mrochek.com>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com> <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de> <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp> <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com> <1e075450-d958-db9c-ae63-3cbf3733024c@outer-planes.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <cf6e35ba-6a67-4b35-d4e1-e99fee6e9f19@gmx.de>
Date: Mon, 13 Mar 2017 20:51:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1e075450-d958-db9c-ae63-3cbf3733024c@outer-planes.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:1sAicka5ZreYlgL3dmOPevOFdNLbwwASwmL592XDQhUODyR/9j0 Z55OW11qeLclxeRQ4IWhQ2Lj7++AsU3bgKXrF7nw0gKYcwY2PlHKhnSlOsNrQLr/Ufaw4Xw Lqzef12hAraov6tGWzoD5YGoLXh+u7p/VG5HBiA2nUI2sPXoEq7VdpIjVwurCDu5hPqNRbI MiKYPP4TY8iLye5i/ZScw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:m5fVRV6aOxM=:mtb318PYufka5wgDsdyaUC eoNLxhXxxmYFhcl0NDb7S+8D6eT1UiOGiftQ5cdpld/iZdYjjJAorO4yZBFI9hnkjHolfVuZa MxQA252CDYr++/5XYRhiCB0QnorN35A35HRRCXqyxMxE1xvynoPiQOOerwFS/aoyOoCi96M5m 3Ex4N0gW8YBkk9uOHUqw9gXIdL/jIwXVWrVuMUximSJYN7+bBmc3s6dwzoG6HGMqYw7fW6IwW yAo1nG6P5JTLIorVh04H5JWVNTVuHx49UDynvPddYbaVYaN1P5nD7j0KZN2vXFMlr5/cc/V4X aiJWajTjfXj0M/QNEb3yNZED2+esf6UDMxIiM6WG4isW/jyC2XTB4ZFMQ/kIcGKHWRbilHoHH Bfhb7CgUGvA38j0c/mmSH/a6/OpkT2YIheXaI03zxh4NhrQ9srdqtiiOYWqlIS4UDZmJvFBjX gkOPIdAJ7hn8AN9RiHps6Ynp6gHY4lfUZxVVItxLqr9aOcX9eJZg8MJq8EV0UqTc7Q0J+GObF YEcu1oEmqLJQt96S28Vnlblx2InUIWLZ7fFC1wEs8OSZjhwqb/sBTdf8Dc3M8z2aJ0j+ymx2s 8pVNbw891MBoUqTG/CWkzl42hVbAP2dr2Gwxl8CTUDPxTYGV7i7gDDv3bTO9esLtlAJ960/sA WYswXD+sScHd4tJfiRI99npB1I5XBkqI1W23anCaE4G2jLQWCys6iWZuymTea4OSgdN3xegQz xQU8mLDSUI0fGC4F9yvhQNx603pCJlln6nNGFTBWsthJmqntQVL34Uwvk2Lb3BVwExONCEo1z gLqqcyx
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gt9_53rTUbnmB8jk-dDxZMuRHQk>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, secdir@ietf.org, ietf@ietf.org, "json@ietf.org" <json@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 19:51:59 -0000

On 2017-03-13 18:54, Matthew A. Miller wrote:
> ...
> /me doffs hat
>
> I like this change myself.
>
> /me dons hat
>
> As I recall, the table was removed mostly because the vast majority of
> implementations did not support any encoding other than UTF-8, and no
> one (that I recall) reported implementing the detection table.
> ...

Well, if we allow UTF-16 and UTF-32 - even if we discourage their use - 
we should say how to detect those...

Alternatively we could forbid them, but that would be a normative change 
from RFC 7159.

Best regards, Julian


From nobody Mon Mar 13 12:57:16 2017
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 790DE129AE7; Mon, 13 Mar 2017 12:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d-Xc_lINaLJl; Mon, 13 Mar 2017 12:57:05 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6683812949D; Mon, 13 Mar 2017 12:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2DJv1dH015347; Mon, 13 Mar 2017 20:57:01 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vhpY91p64zDGy0; Mon, 13 Mar 2017 20:57:01 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <cf6e35ba-6a67-4b35-d4e1-e99fee6e9f19@gmx.de>
Date: Mon, 13 Mar 2017 20:57:00 +0100
X-Mao-Original-Outgoing-Id: 511127819.861928-19cd0691562856b3248a975cd733437d
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F1D1DCB-767F-490D-A425-AB5E66D51D3E@tzi.org>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com> <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de> <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp> <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com> <1e075450-d958-db9c-ae63-3cbf3733024c@outer-planes.net> <cf6e35ba-6a67-4b35-d4e1-e99fee6e9f19@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Dwdbm9gwoHCCuPnm1cX4wmCxf5c>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>, IETF <ietf@ietf.org>, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 19:57:06 -0000

On 13 Mar 2017, at 20:51, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> Well, if we allow UTF-16 and UTF-32 - even if we discourage their use =
- we should say how to detect those...

Consistency is the hobgoblin of the little minds.
(Apparently, not having that nonsense in there did not hurt for 7159?
If people want to implement something useless and cannot figure this =
stuff out, should we help them?)

Putting back any form of apparent support for UTF-16 and UTF-32 is a =
regression.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Mar 13 13:22:30 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C696E129B12 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 13:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXwwokeek4Fn for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 13:22:27 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id CFD20129AEE for <ietf@ietf.org>; Mon, 13 Mar 2017 13:22:26 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1cnWU5-0000EaC; Mon, 13 Mar 2017 21:22:25 +0100
Message-Id: <m1cnWU5-0000EaC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership. 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
In-reply-to: Your message of "13 Mar 2017 18:43:21 +0100 ." <alpine.OSX.2.20.1703131838100.54839@ary.local> 
Date: Mon, 13 Mar 2017 21:22:23 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WXrpuHpgz3utxC2R4vMgL6GJII0>
Cc: John R Levine <johnl@taugh.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 20:22:28 -0000

In your letter dated 13 Mar 2017 18:43:21 +0100 you wrote:
>Nor is gmail, which also requires that incoming IPv6 mail be authenticated 
>with SPF or DKIM.  They know what they are doing, and they have decided 
>that the amount of legit mail they will lose by doing this is 
>insignificant compared to the improvement in the amount of spam and 
>malware they will be able to filter.

That's not correct, unless gmail made an exception for my home mail server.

Getting mail delivered to gmail over IPv6 works most of the time without
ever setting up SPF or DKIM. Gmail does seem to be the single most
unreliable mail server that I know of, mostly due to their attempts
to be more strict on IPv6.

What gmail does require is reverse DNS for IPv6.


From nobody Mon Mar 13 14:05:12 2017
Return-Path: <blong@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 13DF91294DD for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 14:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5En8Ro2e-FIy for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 14:05:07 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36FDB129AF5 for <ietf@ietf.org>; Mon, 13 Mar 2017 14:05:07 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id v76so67455110ywg.0 for <ietf@ietf.org>; Mon, 13 Mar 2017 14:05:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TM58aaEjK/+H58RbvRgHhk2k/LI9Mctde3MreezyEVU=; b=MhnfAwCnxN5/Fo1Ql9jIiRkrVva9hjggoh3ouetVy7C8YhHfbg49UJqd1l/Fr6SSn7 EGG5EX2OaXj1v1eoR7wB5mswAm26Q62b/I490FfAI1hMGjP1T3lCx0wczipauhnKX2ig 4F6mAgYt2dVXYOBYBrrFkWbIvFykzC9tBRbiVPi3SVNJ/UBwUeeI89XU3zH2edQLzym7 yR6ygzs829LE26c+2zDCwrscHjitJhpOghjD0tIfJ4lRn8+AQxJeqL/4p7usMhkqqL5G NxYzPEF7AjoK4oext+gcECEGSgrnTZKY6+pmnjUQ2KySMpV/LWwipq5c9mgOGA6ilGSV eIYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TM58aaEjK/+H58RbvRgHhk2k/LI9Mctde3MreezyEVU=; b=bJg4OXaay5A4V0JywZcus03UTLhKZdwaeVFRi8XjthIvnEcyb1F66xxJ+8HGuf0g6z HwtYDgEKf3c3lo08C26KGlBLFuQxdvP1IJMG8RT8q1TmoJwh34pfLwYDPLMwUL4Y0SyQ 1CCIY+eKdND4iwpN5cZJdUpS9ceWZm4qX310wzqdddb/3czSPtrjSm6nz44nxdlccS4z /ZfQ0IXTUabWZekbH0CiBDxv3grpFwJqk5AWapFlgKqd46dfRy2rbOosefIirs04sfWm ha/o6jKY8y/UhJFM4rZKAgyVUA8HKI2FO35c/ODstWIW4w8FNSrlzAP6r9Yq2j5WMutx cj2g==
X-Gm-Message-State: AFeK/H1QNwQUz86ouEP3lHccubv99AxIfPpFNdf3J+sA82BUSpImyniiraXTHPjd2SvoPYVHqYXRwdmbSKlOWnkI
X-Received: by 10.37.192.16 with SMTP id c16mr16404234ybf.195.1489439105825; Mon, 13 Mar 2017 14:05:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.220.11 with HTTP; Mon, 13 Mar 2017 14:05:04 -0700 (PDT)
In-Reply-To: <m1cnWU5-0000EaC@stereo.hq.phicoh.net>
References: <alpine.OSX.2.20.1703131838100.54839@ary.local> <m1cnWU5-0000EaC@stereo.hq.phicoh.net>
From: Brandon Long <blong@google.com>
Date: Mon, 13 Mar 2017 14:05:04 -0700
Message-ID: <CABa8R6sgcmANj+F=8MLDAhWCphasBTJTQizFKQUd=2bieeXemA@mail.gmail.com>
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
To: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Content-Type: multipart/alternative; boundary=001a113a119ad1d433054aa310de
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nlkzFEm82S7alh54i2AvT_yCoYM>
Cc: John R Levine <johnl@taugh.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 21:05:10 -0000

--001a113a119ad1d433054aa310de
Content-Type: text/plain; charset=UTF-8

https://support.google.com/mail/answer/81126?hl=en#authentication see
"Additional guidelines for IPv6"

Right now, it's basically an OR between the two instead of AND, though as
with any rule, there are exceptions.  We also still do "best guess" style
SPF auth, so if you set your PTR records right, you may be getting SPF for
"free" from us.

And it's always subject to change based on spamminess.

If your work around is to use ip4 to send to us, that's fine.  The
percentage of spam mail on ip6 is higher than on ip4.  Our own outgoing
code makes choices on whether to use ip6 or ip4 based on expected
authentication level, and it is ugly.  I don't like ugly, but I don't like
spam either.

Brandon

On Mon, Mar 13, 2017 at 1:22 PM, Philip Homburg <pch-ietf-6@u-1.phicoh.com>
wrote:

> In your letter dated 13 Mar 2017 18:43:21 +0100 you wrote:
> >Nor is gmail, which also requires that incoming IPv6 mail be authenticated
> >with SPF or DKIM.  They know what they are doing, and they have decided
> >that the amount of legit mail they will lose by doing this is
> >insignificant compared to the improvement in the amount of spam and
> >malware they will be able to filter.
>
> That's not correct, unless gmail made an exception for my home mail server.
>
> Getting mail delivered to gmail over IPv6 works most of the time without
> ever setting up SPF or DKIM. Gmail does seem to be the single most
> unreliable mail server that I know of, mostly due to their attempts
> to be more strict on IPv6.
>
> What gmail does require is reverse DNS for IPv6.
>
>

--001a113a119ad1d433054aa310de
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><a href=3D"https://support.google.com/mail/answer/81126?hl=
=3Den#authentication">https://support.google.com/mail/answer/81126?hl=3Den#=
authentication</a> see &quot;Additional guidelines for IPv6&quot;<br><div><=
br></div><div>Right now, it&#39;s basically an OR between the two instead o=
f AND, though as with any rule, there are exceptions.=C2=A0 We also still d=
o &quot;best guess&quot; style SPF auth, so if you set your PTR records rig=
ht, you may be getting SPF for &quot;free&quot; from us.</div><div><br></di=
v><div>And it&#39;s always subject to change based on spamminess.</div><div=
><br></div><div>If your work around is to use ip4 to send to us, that&#39;s=
 fine.=C2=A0 The percentage of spam mail on ip6 is higher than on ip4.=C2=
=A0 Our own outgoing code makes choices on whether to use ip6 or ip4 based =
on expected authentication level, and it is ugly.=C2=A0 I don&#39;t like ug=
ly, but I don&#39;t like spam either.</div><div><br></div><div>Brandon</div=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Ma=
r 13, 2017 at 1:22 PM, Philip Homburg <span dir=3D"ltr">&lt;<a href=3D"mail=
to:pch-ietf-6@u-1.phicoh.com" target=3D"_blank">pch-ietf-6@u-1.phicoh.com</=
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"><span class=3D"">In =
your letter dated 13 Mar 2017 18:43:21 +0100 you wrote:<br>
&gt;Nor is gmail, which also requires that incoming IPv6 mail be authentica=
ted<br>
&gt;with SPF or DKIM.=C2=A0 They know what they are doing, and they have de=
cided<br>
&gt;that the amount of legit mail they will lose by doing this is<br>
&gt;insignificant compared to the improvement in the amount of spam and<br>
&gt;malware they will be able to filter.<br>
<br>
</span>That&#39;s not correct, unless gmail made an exception for my home m=
ail server.<br>
<br>
Getting mail delivered to gmail over IPv6 works most of the time without<br=
>
ever setting up SPF or DKIM. Gmail does seem to be the single most<br>
unreliable mail server that I know of, mostly due to their attempts<br>
to be more strict on IPv6.<br>
<br>
What gmail does require is reverse DNS for IPv6.<br>
<br>
</blockquote></div><br></div>

--001a113a119ad1d433054aa310de--


From nobody Mon Mar 13 14:21:37 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DACC129B87 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 14:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0cJonlLXQZO for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 14:21:35 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id AE8A8129B7D for <ietf@ietf.org>; Mon, 13 Mar 2017 14:21:34 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1cnXPI-0000INC; Mon, 13 Mar 2017 22:21:32 +0100
Message-Id: <m1cnXPI-0000INC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership. 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
References: <alpine.OSX.2.20.1703131838100.54839@ary.local> <m1cnWU5-0000EaC@stereo.hq.phicoh.net> <CABa8R6sgcmANj+F=8MLDAhWCphasBTJTQizFKQUd=2bieeXemA@mail.gmail.com> 
In-reply-to: Your message of "Mon, 13 Mar 2017 14:05:04 -0700 ." <CABa8R6sgcmANj+F=8MLDAhWCphasBTJTQizFKQUd=2bieeXemA@mail.gmail.com> 
Date: Mon, 13 Mar 2017 22:21:32 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4Op69gkqOpFxIr3Zt2MKSQW8EXc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 21:21:36 -0000

>If your work around is to use ip4 to send to us, that's fine.  The
>percentage of spam mail on ip6 is higher than on ip4.  Our own outgoing
>code makes choices on whether to use ip6 or ip4 based on expected
>authentication level, and it is ugly.  I don't like ugly, but I don't like
>spam either.

At the moment, my setup is identical for IPv4 and IPv6, with of course a
preference for IPv6.

If gmail would first return a 4xy then I would never notice, because
my mail server would retry over IPv4.

Unfortunately, every now and then gmail returns a 5xy for no reason on
my side. Then I resend the same e-mail from my MUA and it gets accepted.

I don't know why gmail seems to turn transient errors into permanent failures
at the SMTP level. As far as I can tell, that is unique to gmail.



From nobody Mon Mar 13 15:51:19 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20B54129684 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 15:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=MFk3yiD8; dkim=pass (1536-bit key) header.d=taugh.com header.b=GLz+yrRa
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xt-rTurmkRif for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 15:51:16 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15CEB129BDC for <ietf@ietf.org>; Mon, 13 Mar 2017 15:51:09 -0700 (PDT)
Received: (qmail 63037 invoked from network); 13 Mar 2017 22:51:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-id:user-agent; s=f63b.58c7225c.k1703; bh=Xv/8mX6Ue1TioHPj6+JNcnUkJJS6WSL7H6u7Kx4rt0M=; b=MFk3yiD8Ozlb1fSiyl+Xo482DlOQYsqYmC5IJJ1lvNviTosZjmKtg2KroGQvkbL4oUIiGEz281pdUrWP2YbtCsnxP0tVsG29UzdzBZEcuhny6saUmB+LuyBqRpMTsu9rTBegwxEBalo0JKfYA/Q7eHxe2fPvLjO76SqkDNgJEnBivSjUaEL5JJnB/OIG46NNl/UYdvZYkXOrQBO21vhdpA8d49ejqzFYBRC8bmMDqzuDEwl9kWYA5TbyPxGqEgB4
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-id:user-agent; s=f63b.58c7225c.k1703; bh=Xv/8mX6Ue1TioHPj6+JNcnUkJJS6WSL7H6u7Kx4rt0M=; b=GLz+yrRaMuoEZ1LpUyn+DFJ+nMxygwtx3KeUGVV3HYe0RBEujdaVoGXYNUgxO9UMKU8DhdeMmrRuiRNuwaeeti+9mD7gh/K/llhh7tbcs/2e9DaNoJCSJTgoVfI4QU3XTYbj2f+fb27jRnGA1I9JIiC+Tx8fKiTMQvI7ErEfoJRjKfHP3TOiOl9TP13HZrdkOqzrsZlt8248bbDYpcHRlHi9xl2agseTaGJAeRiMt2BRzbNlElVcCcV/n/jsUfjn
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 13 Mar 2017 22:51:07 -0000
Date: 13 Mar 2017 23:51:06 +0100
Message-ID: <alpine.OSX.2.20.1703132331590.54839@ary.local>
From: "John R Levine" <johnl@taugh.com>
To: "IETF general list" <ietf@ietf.org>
Subject: Do you really not care whether people accept your mail?
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="0-2120216515-1489444350=:54839"
Content-ID: <alpine.OSX.2.20.1703132332580.54839@ary.local>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t80__5lcFJqNUW74hNxTJE2wg2k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 22:51:18 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-2120216515-1489444350=:54839
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Content-ID: <alpine.OSX.2.20.1703132332581.54839@ary.local>

On Mon, 13 Mar 2017, Carsten Bormann wrote:
> The most likely outcome is that local admins will “upgrade" our mail 
> system by turning off IPv6.  (We have had IPv6 deployed for some 18 
> years now.)

On Mon, 13 Mar 2017, Philip Homburg wrote:
> Getting mail delivered to gmail over IPv6 works most of the time without
> ever setting up SPF or DKIM. Gmail does seem to be the single most
> unreliable mail server that I know of, mostly due to their attempts
> to be more strict on IPv6.

As I hope everyone knows, receiving mail requires orders of magnitude more 
work than sending it.  Even 20 years ago before spam was an issue, 
recipients had to receive it, route it, store it somewhere, filter it with 
sieve or procmail, and provide POP or IMAP for the recipient to collect 
it.  These days, with 90% of mail being spam or worse, there's another 
magnitude of work in trying to separate the real mail from the flood of 
junk.  Or try this thought experiment: how hard would it be to send a 
million messages a day from your laptop (easy), and how hard would be be 
to receive and deliver a million messages a day on that laptop 
(impossible.)

The point of authentication schemes like SPF and DKIM is to make it easier 
for recipients to tell that your mail is from you, so they can treat it 
differently from the spam.  Everywhere else, the response is OK, I would 
prefer that people get the mail I send them, I will set up authentication 
because it is not hard (SPF takes about 5 minutes), and it helps the 
people who are handling my mail with the mail system they are paying for.

I can also assure you from many conversations with large mail providers 
that you will increasingly find that recipients will conclude that if you 
can't be bothered to authenticate your mail, they can't be bothered to 
deliver it.  It's their mail system, they get to do that.

In the IETF, for some reason, people take a perverse pride in offering no 
help whatsoever to mail recipients, even when that help costs them 
nothing, and then snark and whine when the recipients have trouble dealing 
with the unauthenticated mail.  I don't understand why, but I really wish 
people would stop.  Nobody is impressed that your mail system does exactly 
what it did 20 years ago, and it gives outsiders the impression that the 
IETF is a bunch of out of touch sociopaths.

R's,
Johh
--0-2120216515-1489444350=:54839--


From nobody Mon Mar 13 16:13:24 2017
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 66B1B12962B for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 16:13:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bGO_xWuIh__1 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 16:13:18 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C5991297C3 for <ietf@ietf.org>; Mon, 13 Mar 2017 16:13:13 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id 126so85220088oig.3 for <ietf@ietf.org>; Mon, 13 Mar 2017 16:13:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=aBT4rghe5wfz/HoM84bSYGNff+z7nzuhqkBS4Q1rrZc=; b=ngEmeynIFzehTzkUjFw0FDcn2LA2g2zXThS1ktQ2Ge13i6Ycbu55bfzrVu7HN+dBlD Qumgq4C87pev0y9Cf2We9iYnYX1J+R/IGlnqRVm20/7EVigXht7r/DQXZGdnm/F3l4bd ZQz+sz0rBXrOf/gKpA5qt3rcpnby+CHg5Aw/TwXYwNdZFBr9+q3ESdXoLpSzW8vNBQMQ //0Yyt8ergj7TzcV7vJXi+V4Bfaer/XZNOHTytosf59Rj8vUGr8gs0ZPvEF/Z0VkbKr8 gWUplPUGmk7h4GimYTFM9ufDjMg6538NmRqk82sD5PkcrF8oyU4lc1PNkOjheXn8uG2W GREA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=aBT4rghe5wfz/HoM84bSYGNff+z7nzuhqkBS4Q1rrZc=; b=MfNbcmwRF6fvicEweAlWlshnMKhT4OSHDhZ815LE3UMtcN3eE2IjbioPbZAg7ZsOf/ tKTVUKUAayyDB8DbE/N0zCwr7fGd8I8N9SbnmKfXZee4/f0poDJxRVHOtnrCZ7rvR1Rw 7MaaixLRJx+pumjFUMeVE1TweroEArO9kJWjjGt3QRlfWvUBGXq2rLJYWhybElZDh8pj kpUxhssnKcazQOdWjuHZizu8IWbUcdA3CHhRaC9YXtp4Wquh+UD1nMkSnTfDPt8KSUAY QkluD2QVrqzAzxhiRLbvfMxxJKs/GMtdszPXp0W3T6mdSmico3Zv1wDhfzApf8pJJWAm C2bg==
X-Gm-Message-State: AMke39ksYILGdzZssxZ7tazJzj/kCK1KWw1IUcqaIpxrP9GY5s+SZ3pjZqmTYCUQBX6wDygNAEzyhjJhFh8K9w==
X-Received: by 10.202.73.201 with SMTP id w192mr16395054oia.85.1489446792422;  Mon, 13 Mar 2017 16:13:12 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.14.123 with HTTP; Mon, 13 Mar 2017 16:13:11 -0700 (PDT)
In-Reply-To: <CC5E2EDA-5533-4FA0-8350-CE45311DD8B4@fugue.com>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com> <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie> <CC5E2EDA-5533-4FA0-8350-CE45311DD8B4@fugue.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 13 Mar 2017 19:13:11 -0400
X-Google-Sender-Auth: qZA-rLvyGv3RlJbD5uqzH-f5XDg
Message-ID: <CAMm+Lwh4Pn39D4r+k5HQnaxtZbTkpRCmAFMg77vLRVQzKY4S7g@mail.gmail.com>
Subject: Re: The CIA mentions us
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=001a1134e4c4f96ac5054aa4da36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mCBXgxcKHF7ww7w2bTk-ZidDTVg>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 23:13:23 -0000

--001a1134e4c4f96ac5054aa4da36
Content-Type: text/plain; charset=UTF-8

I think this particular failure demonstrates the situation pretty well:
http://www.zdnet.com/article/leaked-us-military-files-exposed/

A) Without transport encryption, every network link is a potential point of
compromise via traffic analysis.

B) Without end-to-end data level encryption, every non endpoint device,
every hard drive or removable storage is a potential point of compromise

C) Without end point security, the end points are a potential point of
compromise.

D) Without trustworthy personnel, you are vulnerable to an insider threat.

The security controls you need depends on your information security assets
and your security concerns.

If you are a high level security target then you need A + B + C + D. They
are not alternatives, they are all requirements. It is really completely
unhelpful for people to suggest tackling these separable concerns
separately is 'useless'.

Just as I would not consider personnel or physical security at the same
time as end point security, I do not want to consider data level security
at the same time as end point.

To get back to the CIA leak, that 'hole you can drive a truck through' did
not actually exist when the AV package was connected to the Internet. What
we are seeing here is not a set of vulnerabilities, it is a set of research
notes being compiled by people searching for vulnerabilities that has
subsequently been exfiltrated, filtered to remove the good stuff and
dumped.

If you do end point security right, you can really be a 'PITA' to the
people trying to break these systems. So the idea that end point security
is futile is utterly misguided. If you use default deny approaches, end
point security can be very effective. But end point security really isn't
in scope for IETF unless we were to get into protocols for attestation of
trustworthy hardware or the like.


The reason I keep coming back to the data level security issue is that

1) It is in scope for IETF. Data level security protects data at rest and
in motion.

2) There have been recent expiries and are imminent pending expiries of key
IPR that makes a solution much easier.

3) It is one of the things we can fix that has the greatest security payoff.

--001a1134e4c4f96ac5054aa4da36
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default">I think this particular failu=
re demonstrates the situation pretty well:</div><div class=3D"gmail_default=
"><a href=3D"http://www.zdnet.com/article/leaked-us-military-files-exposed/=
">http://www.zdnet.com/article/leaked-us-military-files-exposed/</a><br></d=
iv><div class=3D"gmail_default"><br></div><div class=3D"gmail_default">A) W=
ithout transport encryption, every network link is a potential point of com=
promise via traffic analysis.</div><div class=3D"gmail_default"><br></div><=
div class=3D"gmail_default">B) Without end-to-end data level encryption, ev=
ery non endpoint device, every hard drive or removable storage is a potenti=
al point of compromise</div><div class=3D"gmail_default"><br></div><div cla=
ss=3D"gmail_default">C) Without end point security, the end points are a po=
tential point of compromise.</div><div class=3D"gmail_default"><br></div><d=
iv class=3D"gmail_default">D) Without trustworthy personnel, you are vulner=
able to an insider threat.</div><div class=3D"gmail_default"><br></div><div=
 class=3D"gmail_default">The security controls you need depends on your inf=
ormation security assets and your security concerns.</div><div class=3D"gma=
il_default"><br></div><div class=3D"gmail_default">If you are a high level =
security target then you need A + B + C + D. They are not alternatives, the=
y are all requirements. It is really completely unhelpful for people to sug=
gest tackling these separable concerns separately is &#39;useless&#39;.=C2=
=A0</div><div class=3D"gmail_default"><br></div><div class=3D"gmail_default=
">Just as I would not consider personnel or physical security at the same t=
ime as end point security, I do not want to consider data level security at=
 the same time as end point.</div><div class=3D"gmail_default"><br></div><d=
iv class=3D"gmail_default">To get back to the CIA leak, that &#39;hole you =
can drive a truck through&#39; did not actually exist when the AV package w=
as connected to the Internet. What we are seeing here is not a set of vulne=
rabilities, it is a set of research notes being compiled by people searchin=
g for vulnerabilities that has subsequently been exfiltrated, filtered to r=
emove the good stuff and dumped.=C2=A0</div><div class=3D"gmail_default"><b=
r></div><div class=3D"gmail_default">If you do end point security right, yo=
u can really be a &#39;PITA&#39; to the people trying to break these system=
s. So the idea that end point security is futile is utterly misguided. If y=
ou use default deny approaches, end point security can be very effective. B=
ut end point security really isn&#39;t in scope for IETF unless we were to =
get into protocols for attestation of trustworthy hardware or the like.=C2=
=A0</div><div class=3D"gmail_default"><br></div><div class=3D"gmail_default=
"><br></div><div class=3D"gmail_default">The reason I keep coming back to t=
he data level security issue is that=C2=A0</div><div class=3D"gmail_default=
"><br></div><div class=3D"gmail_default">1) It is in scope for IETF. Data l=
evel security protects data at rest and in motion.</div><div class=3D"gmail=
_default"><br></div><div class=3D"gmail_default">2) There have been recent =
expiries and are imminent pending expiries of key IPR that makes a solution=
 much easier.</div><div class=3D"gmail_default"><br></div><div class=3D"gma=
il_default">3) It is one of the things we can fix that has the greatest sec=
urity payoff.</div><div class=3D"gmail_default"><br></div><div class=3D"gma=
il_default"><br></div></div>

--001a1134e4c4f96ac5054aa4da36--


From nobody Mon Mar 13 16:31:15 2017
Return-Path: <jared@puck.nether.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 7E49B1295E9 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 16:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQQylvTYWV3V for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 16:31:12 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 67BCE129562 for <ietf@ietf.org>; Mon, 13 Mar 2017 16:31:12 -0700 (PDT)
Received: from [IPv6:2603:3015:3603:8e00:49a:b6a0:fcb1:913d] (unknown [IPv6:2603:3015:3603:8e00:49a:b6a0:fcb1:913d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 94FEF540B42; Mon, 13 Mar 2017 19:30:55 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Do you really not care whether people accept your mail?
From: Jared Mauch <jared@puck.nether.net>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <alpine.OSX.2.20.1703132331590.54839@ary.local>
Date: Mon, 13 Mar 2017 19:30:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local>
To: John R Levine <johnl@taugh.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0CdzSAW0frLEEwZ0UEV9jmywnaU>
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Mar 2017 23:31:13 -0000

> On Mar 13, 2017, at 6:51 PM, John R Levine <johnl@taugh.com> wrote:
>=20
> Nobody is impressed that your mail system does exactly what it did 20 year=
s ago, and it gives outsiders the impression that the IETF is a bunch of out=
 of touch sociopaths.

So much this above. You either conform to the norms or are the outlier. Grou=
sing on a mailing list when most of the world is using something else will g=
et you results similar to /dev/null

- jared=


From nobody Mon Mar 13 19:41:49 2017
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 1D05A129A24 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 19:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvxikPdxT7IL for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 19:41:47 -0700 (PDT)
Received: from mail-ot0-x229.google.com (mail-ot0-x229.google.com [IPv6:2607:f8b0:4003:c0f::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 481F11297EC for <ietf@ietf.org>; Mon, 13 Mar 2017 19:41:47 -0700 (PDT)
Received: by mail-ot0-x229.google.com with SMTP id i1so125164782ota.3 for <ietf@ietf.org>; Mon, 13 Mar 2017 19:41:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hwlqWSTH6x0ZRYRBsJXL4084/4pu3waySbJhsAY2DF0=; b=W79X4bDq3Zh9lMeMBpzkly8xAobyz50Dfx0QfQ1gv08yJpzs/VeiAK2Vxv3Jasuykv ZM5BcXyJcUwJhMxekM1B+ojYcTksu/8uPqx/x+vH7Uk8ySqHUrVnDwf9vUlWCUtH0Lp3 I2tmVTtuBVdwIasfMJYH14bVk0KEgeltDHQ+DRdqiJUXN8n6Xbjm6vZpsExvWAc2ACGZ LmtQ/qPK1K1jfXsBUqop0VB4OBJ6XoKAfBs32C43tUBuoAclUmKX+ZP7RxII31eQGOdT H3AXu35Z2RBkGsOkshL7SAo4pWT8XX4ygO57kxBAKxm/AVkburc1MAAdbYnY5EVrH693 V3zA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=hwlqWSTH6x0ZRYRBsJXL4084/4pu3waySbJhsAY2DF0=; b=eSfOUp7hA3A8QKAAEMfhAG21awdr8MMEsE+c8E7zpbhiO28CxrbY6pZA3i8ipVq9Qc JAfq1cGjdOwjs+jCnQD8kKH4S82bGGkwd0LkMsl+Au3PaC95peLg5GUrwnRBNtLeiu9u a5yUOCVcBCp0WbxKgfrPNmAfVeitwL913lU3dpKP9uJRNwqVnJe4N3DuXME14jvc1SU5 yy+XwOuDeiC8dLzeQYfrqPyXN/ZR5tCCo5IOcSzhbqeh+rA96MIwDPjDhqeJ7GX5TOh3 PNpzeatgLOTzcMrluaZjDwXGi7A/OZ3KC42pfaMzYijn1URr/lIbryKhf+TF87KojUeZ IVkg==
X-Gm-Message-State: AMke39lzWWOVIRXS/y4RsdojuzOMOi0/YvYdack9T+Wz/zkBby1LDL2b6m2bKdSQkzuo4MXhsz5lJZnWYaxvmQ==
X-Received: by 10.157.3.166 with SMTP id f35mr18920874otf.16.1489459306709; Mon, 13 Mar 2017 19:41:46 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.14.123 with HTTP; Mon, 13 Mar 2017 19:41:46 -0700 (PDT)
In-Reply-To: <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 13 Mar 2017 22:41:46 -0400
X-Google-Sender-Auth: girPfHC9paizhNhKF_Y6OCVoAVc
Message-ID: <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com>
Subject: Re: Do you really not care whether people accept your mail?
To: Jared Mauch <jared@puck.nether.net>
Content-Type: multipart/alternative; boundary=001a11487540e2480c054aa7c4b0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7aOvqOBOXSKjC1RIu3Qld4ddqtA>
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 02:41:48 -0000

--001a11487540e2480c054aa7c4b0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=E2=80=8BPerhaps we should just recognize the fact that SMTP does not reall=
y
support mailing lists, it never has and never will. All the kludges and
duct tape in the world won't fix what is broken here.

I read my IETF mail through gmail because, well its easiest to do that. And
I have roughly 10GB of mailing list traffic. Most of which is probably
copied 50-100 times or more.

A much more efficient approach would be to use SMTP to submit the mail and
some other protocol (POP3, RSS, IMAP, something new) to retrieve it.


Protocols do wear out and at some point it is easier to start from scratch

Build in end to end encryption while we are at it.
=E2=80=8B

--001a11487540e2480c054aa7c4b0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">=E2=
=80=8BPerhaps we should just recognize the fact that SMTP does not really s=
upport mailing lists, it never has and never will. All the kludges and duct=
 tape in the world won&#39;t fix what is broken here.</div><div class=3D"gm=
ail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-size:small">I read my IETF mail through gmail because, wel=
l its easiest to do that. And I have roughly 10GB of mailing list traffic. =
Most of which is probably copied 50-100 times or more.</div><div class=3D"g=
mail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-size:small">A much more efficient approach would be to us=
e SMTP to submit the mail and some other protocol (POP3, RSS, IMAP, somethi=
ng new) to retrieve it.</div><div class=3D"gmail_default" style=3D"font-siz=
e:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small"><=
br></div><div class=3D"gmail_default" style=3D"font-size:small">Protocols d=
o wear out and at some point it is easier to start from scratch</div><div c=
lass=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gm=
ail_default" style=3D"font-size:small">Build in end to end encryption while=
 we are at it.</div><div class=3D"gmail_default" style=3D"font-size:small">=
=E2=80=8B</div></div>

--001a11487540e2480c054aa7c4b0--


From nobody Mon Mar 13 19:56:38 2017
Return-Path: <ietf-dane@dukhovni.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 67815129AB5 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 19:56:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vawgdeYi_xeD for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 19:56:36 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EC1D1294A8 for <ietf@ietf.org>; Mon, 13 Mar 2017 19:56:35 -0700 (PDT)
Received: from [10.65.182.101] (unknown [38.86.167.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 178C77A32F1 for <ietf@ietf.org>; Tue, 14 Mar 2017 02:56:35 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Do you really not care whether people accept your mail?
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com>
Date: Mon, 13 Mar 2017 22:56:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A70563C-00FB-4F21-B6CB-44E1CF742E10@dukhovni.org>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net> <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_yVGq9nuhWOxKqOQmqL4o7Ncsh8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <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: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 02:56:37 -0000

> On Mar 13, 2017, at 10:41 PM, Phillip Hallam-Baker =
<phill@hallambaker.com> wrote:
>=20
> Perhaps we should just recognize the fact that SMTP does not really =
support mailing
> lists, it never has and never will.

This is absurd, perhaps we can recognize that Yahoo does not support =
mailing
lists, ...  SMTP works with lists just fine.

In any case, the issue at hand is not even about lists, Gmail imposes =
more
strict constraints on IPv6 senders than IPv4 senders.  For now I prefer =
to
send over IPv4 rather than reduce the deliverability of my mail when =
some
fragile "authentication" mechanism fails.  Thus no SPF, or DMARC for my
domain at present.  This trade-off is subject to periodic reassessment,
for now that's what works best for me.  Some day I may enable outbound
DKIM signing, and perhaps (much) later as a last resort SPF.  So far,
neither have been needed.

--=20
	Viktor.


From nobody Mon Mar 13 21:08:32 2017
Return-Path: <christopher.morrow@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 B3119129C55 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 21:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f22iFwopxmK2 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 21:08:30 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5938A129C59 for <ietf@ietf.org>; Mon, 13 Mar 2017 21:08:30 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id i34so47361451qtc.0 for <ietf@ietf.org>; Mon, 13 Mar 2017 21:08:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=s2UloWoQAy24Po3CXx/gZa4Ugb/gTBkXHojs+z3rck4=; b=AZJ4VJCA5snPxoKLiIKOlfN38CRUfKEhAcFXuqhNfwYOHGNiswciqqQHSqqgvfweKA i+/yX8bw0svk7eoT0WcVPtsol+Xay2OciagTkHwk+sxsof3wxbr02iRv50/0z+JvJaLg 43f+HpY6OyEtkimPMEPexlEG+Rj1O0qyb6qD/suo+YL1b9lOJVCRPQDzn+cGQTBE9GHu YHINk8zujcUF7ULqcZQtI11T6Ys2A0CVQ72l1zbIrJJ1dbbxUoFwvI1lWSPs2MP9gj+m sHF7kT3RYSHI2KLLa6uaW5vdzolhAkNDNeI+HFRZ+GwnyQgOwL7X+xkDykWzGMI316s9 ZBEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=s2UloWoQAy24Po3CXx/gZa4Ugb/gTBkXHojs+z3rck4=; b=fja0/t5CylEzNi5F1PqKP4gPlbJiFmA2wi/hMoF/ZnWRj0mP1nlVqtZqVQ6JbQ6hUq CoBBfTXJWruHC61Jf4c7Nm6E9aBtR+1cbCrpiQfroNqSHHX38RQx02TCAWkExXcTbUaU 2Qsnc+4NnLLiBxBD0IK2ecAOoVA4vCSQK9yMfIaYYcQBHKiCRVR/T71WGg+4ggmL4G8/ 8COBKMWdgF96FpAoBuwnGvR8+m8GAD2Caljmlp+VSEl2qBej+v7+ShPnN8YBM0ScOahS L3NHZkyz1bOtNrwompAleu890j5FI8kaZ6aXNMWJ4QKbjr5Q7THAkeD5eZdM4C1XYJ/A VI1A==
X-Gm-Message-State: AMke39m3c8L/nTqTYzIP3UuXgxGNO0KQwIDlG9sBQC2gsUa6qwurhX3jTNka5YwRbS8RC80kgcFWjI2RD7Ec8g==
X-Received: by 10.237.59.150 with SMTP id r22mr34927396qte.100.1489464509509;  Mon, 13 Mar 2017 21:08:29 -0700 (PDT)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.17.75 with HTTP; Mon, 13 Mar 2017 21:08:29 -0700 (PDT)
In-Reply-To: <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net> <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Tue, 14 Mar 2017 00:08:29 -0400
X-Google-Sender-Auth: y72ynovLeIcVMzV5NQwROZacjLY
Message-ID: <CAL9jLaa8ieMnT3P1xc=qRDhVkwG7JknPYbKsfDFpdNcO9GxwGQ@mail.gmail.com>
Subject: Re: Do you really not care whether people accept your mail?
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary=001a114dc346feb9ad054aa8fa51
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/287Y1ts_cQEK61V-wppCtPupNPE>
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 04:08:32 -0000

--001a114dc346feb9ad054aa8fa51
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 13, 2017 at 10:41 PM, Phillip Hallam-Baker <
phill@hallambaker.com> wrote:

> =E2=80=8BPerhaps we should just recognize the fact that SMTP does not rea=
lly
> support mailing lists, it never has and never will. All the kludges and
> duct tape in the world won't fix what is broken here.
>
>
i hear a vote for nntp..

--001a114dc346feb9ad054aa8fa51
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Mar 13, 2017 at 10:41 PM, Phillip Hallam-Baker <span dir=3D"ltr=
">&lt;<a href=3D"mailto:phill@hallambaker.com" target=3D"_blank">phill@hall=
ambaker.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div di=
r=3D"ltr"><div style=3D"font-size:small">=E2=80=8BPerhaps we should just re=
cognize the fact that SMTP does not really support mailing lists, it never =
has and never will. All the kludges and duct tape in the world won&#39;t fi=
x what is broken here.</div><div style=3D"font-size:small"><br></div></div>=
</blockquote><div><br></div><div>i hear a vote for nntp..=C2=A0</div></div>=
</div></div>

--001a114dc346feb9ad054aa8fa51--


From nobody Mon Mar 13 21:58:25 2017
Return-Path: <willi.uebelherr@riseup.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 3B9F11294BC for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 21:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYLRliwR_3I5 for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 21:58:23 -0700 (PDT)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07A1D129443 for <ietf@ietf.org>; Mon, 13 Mar 2017 21:58:23 -0700 (PDT)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 920C11A14CA for <ietf@ietf.org>; Tue, 14 Mar 2017 04:58:22 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1489467502; bh=yDYWhl/Rw61oqWJl7IIuWJ++i/BCxrec9cxFvHiIBVQ=; h=Subject:References:From:To:Date:In-Reply-To:From; b=Heh3KxTAxurpcaMBX47uo0LtWwvkhBFXPoTVpE2Qc1WqInNjbONUEsZ30YmudlDC2 SCVD36XNA9Kzxtkms+ha1Vzm2Dr4VjRL6XaBfzhdPzg0BTA8zxv2nz7aKUeqwwRrxj YbkS9NmdkMeOK5KiTKR9YUhIbykManTe5Q9GE6Yo=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id F3EB01C0084
Subject: Re: The CIA mentions us
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com> <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie> <CC5E2EDA-5533-4FA0-8350-CE45311DD8B4@fugue.com> <CAMm+Lwh4Pn39D4r+k5HQnaxtZbTkpRCmAFMg77vLRVQzKY4S7g@mail.gmail.com>
From: willi uebelherr <willi.uebelherr@riseup.net>
To: IETF discussion <ietf@ietf.org>
Message-ID: <d9b02513-fcb3-888d-8e65-831d1078c24b@riseup.net>
Date: Tue, 14 Mar 2017 01:58:05 -0300
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwh4Pn39D4r+k5HQnaxtZbTkpRCmAFMg77vLRVQzKY4S7g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dwZTlHMbN1o_3d8imQT8xBVmw20>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 04:58:24 -0000

Phillip, if you use B), you don't need A).

And how do you want to prevent traffic analysis? In a telekcommunication 
system, where all actors are privat companies and act for the state 
institutions and with a star topology, you will never be able to prvent 
any form of traffic analysis.

Your writing is a little bit naive for me.

greetings, willi



On 13/03/2017 20:13, Phillip Hallam-Baker wrote:
> I think this particular failure demonstrates the situation pretty well:
> http://www.zdnet.com/article/leaked-us-military-files-exposed/
>
> A) Without transport encryption, every network link is a potential point of
> compromise via traffic analysis.
>
> B) Without end-to-end data level encryption, every non endpoint device,
> every hard drive or removable storage is a potential point of compromise
>
> C) Without end point security, the end points are a potential point of
> compromise.
>
> D) Without trustworthy personnel, you are vulnerable to an insider threat.
>
> The security controls you need depends on your information security assets
> and your security concerns.
>
> If you are a high level security target then you need A + B + C + D. They
> are not alternatives, they are all requirements. It is really completely
> unhelpful for people to suggest tackling these separable concerns
> separately is 'useless'.
>
> Just as I would not consider personnel or physical security at the same
> time as end point security, I do not want to consider data level security
> at the same time as end point.
>
> To get back to the CIA leak, that 'hole you can drive a truck through' did
> not actually exist when the AV package was connected to the Internet. What
> we are seeing here is not a set of vulnerabilities, it is a set of research
> notes being compiled by people searching for vulnerabilities that has
> subsequently been exfiltrated, filtered to remove the good stuff and
> dumped.
>
> If you do end point security right, you can really be a 'PITA' to the
> people trying to break these systems. So the idea that end point security
> is futile is utterly misguided. If you use default deny approaches, end
> point security can be very effective. But end point security really isn't
> in scope for IETF unless we were to get into protocols for attestation of
> trustworthy hardware or the like.
>
>
> The reason I keep coming back to the data level security issue is that
>
> 1) It is in scope for IETF. Data level security protects data at rest and
> in motion.
>
> 2) There have been recent expiries and are imminent pending expiries of key
> IPR that makes a solution much easier.
>
> 3) It is one of the things we can fix that has the greatest security payoff.
>


From nobody Mon Mar 13 23:42:15 2017
Return-Path: <ynir.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 70B061293EC for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 23:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id arotvrRkqusD for <ietf@ietfa.amsl.com>; Mon, 13 Mar 2017 23:42:11 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21FB61289B0 for <ietf@ietf.org>; Mon, 13 Mar 2017 23:42:11 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id n11so56071771wma.1 for <ietf@ietf.org>; Mon, 13 Mar 2017 23:42:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=N04GFp19YA212dBKypHjG7rsLw62ujn+EwU4ejz1v8Y=; b=mIsJmfGV7XYWy8QrJxV2hbmc0aWtDRtxwK0++HaCt4AYBsgmBGQnmH5VS1HYRdmlrS WqWvg2rRF05bZSXeD+CAJ7Ko877MEMA4Bj3/xLyE5d8nibwGn0FU/RPrCuWM3UZCbkV7 BpdsIF1bBi/ZiWFz6j6vLWtkfhbvISOO7psEHUA/umClvyNRb76YXfmGoM+sw3g3E52A Xm1TCJs/ea7azuTYgo1NqWPDa5Q+4TKPmP17xBnZVvF/UEJjerQJsydvsCwzG2Zp4C9R hmMKyPR/gQz5+e+H9DbcjJaoa4gftpVvBu3JUQ4kowPU8IQWy4W454ug/oyc2pqkJt2V 8yfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=N04GFp19YA212dBKypHjG7rsLw62ujn+EwU4ejz1v8Y=; b=T1v0Zxu/vmmXjRAsFMaxpevd+uRxNd3buFkSWRvudS96ksHJuC4DnlKa6uhw3TBRuR Uex+PmuJJVP2TpXbyzOqhUPbZg1UJOkegykB/sjAKF9i/NwC1a2jX1FuDlBudt0MjasV vXBAw5SxVNJqjTq5oH0tEmFx6XI5G+mJTin/Pr9f8PQ7zCihz7gcCdwMSAnMCOzV3GCN 8xKkjUxSNokZJ1SfsXCfKsHaWVspPjktz5HIdaTZxkOGfW7nXqL1JMZuJ8JaL3ZqT33k Njk1a+UZIsACYoHRAfEZsohefko0aPj4pHE7O9hGF+KHtOc1BgS5dGyJxMeyrWC4Iptg wR8Q==
X-Gm-Message-State: AFeK/H3Slig0u7fIwQrE9y53bOeV+WeegYgiPEgrSLI8hI52951dXDbutmYsSgX0Up4IGg==
X-Received: by 10.28.172.68 with SMTP id v65mr12534632wme.49.1489473729483; Mon, 13 Mar 2017 23:42:09 -0700 (PDT)
Received: from [192.168.137.86] ([176.12.155.111]) by smtp.gmail.com with ESMTPSA id 36sm27816018wrk.57.2017.03.13.23.42.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Mar 2017 23:42:08 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <7AD4B72D-BABA-4789-9615-F6E659D09B4D@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1732CF29-8E01-4125-B3EC-1AB3C18085B7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: The CIA mentions us
Date: Tue, 14 Mar 2017 08:42:03 +0200
In-Reply-To: <d9b02513-fcb3-888d-8e65-831d1078c24b@riseup.net>
To: willi uebelherr <willi.uebelherr@riseup.net>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com> <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie> <CC5E2EDA-5533-4FA0-8350-CE45311DD8B4@fugue.com> <CAMm+Lwh4Pn39D4r+k5HQnaxtZbTkpRCmAFMg77vLRVQzKY4S7g@mail.gmail.com> <d9b02513-fcb3-888d-8e65-831d1078c24b@riseup.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PXbTZoMcCTn10cNRDjet4EhNgM8>
Cc: IETF discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 06:42:14 -0000

--Apple-Mail=_1732CF29-8E01-4125-B3EC-1AB3C18085B7
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_E0E12C86-1458-453E-A5A4-68AA74A6C7D9"


--Apple-Mail=_E0E12C86-1458-453E-A5A4-68AA74A6C7D9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi, Willi

> On 14 Mar 2017, at 6:58, willi uebelherr <willi.uebelherr@riseup.net> =
wrote:
>=20
>=20
> Phillip, if you use B), you don't need A).

Consider email. If you and I were to use PGP or S/Mime encryption nobody =
can read the content of our messages. However, without transport-layer =
(or IP-layer. I=E2=80=99m an IPsec guy) encryption between the gmail =
server and the riseup.net <http://riseup.net/> server, anyone monitoring =
the traffic can know that I am sending you an email. Protecting SMTP =
with TLS makes the connection only expose that someone of gmail is =
sending a message to someone on riseup.net <http://riseup.net/>.  And =
=E2=80=9Csomeone on gmail=E2=80=9D is close to being half the Internet. =
So you really still need A.

Of course we are still vulnerable to Google or riseup.net =
<http://riseup.net/> informing on us.  Maybe we need some (E) about =
trustworthy intermediaries.

> And how do you want to prevent traffic analysis? In a =
telekcommunication system, where all actors are privat companies and act =
for the state institutions and with a star topology, you will never be =
able to prvent any form of traffic analysis.
>=20
> Your writing is a little bit naive for me.

Well, TLS 1.3 and IPsec have some anti-traffic analysis feature, but =
there is little evidence of anyone using this effectively.

Yoav

>=20
> greetings, willi
>=20
>=20
>=20
> On 13/03/2017 20:13, Phillip Hallam-Baker wrote:
>> I think this particular failure demonstrates the situation pretty =
well:
>> http://www.zdnet.com/article/leaked-us-military-files-exposed/
>>=20
>> A) Without transport encryption, every network link is a potential =
point of
>> compromise via traffic analysis.
>>=20
>> B) Without end-to-end data level encryption, every non endpoint =
device,
>> every hard drive or removable storage is a potential point of =
compromise
>>=20
>> C) Without end point security, the end points are a potential point =
of
>> compromise.
>>=20
>> D) Without trustworthy personnel, you are vulnerable to an insider =
threat.
>>=20
>> The security controls you need depends on your information security =
assets
>> and your security concerns.
>>=20
>> If you are a high level security target then you need A + B + C + D. =
They
>> are not alternatives, they are all requirements. It is really =
completely
>> unhelpful for people to suggest tackling these separable concerns
>> separately is 'useless'.
>>=20
>> Just as I would not consider personnel or physical security at the =
same
>> time as end point security, I do not want to consider data level =
security
>> at the same time as end point.
>>=20
>> To get back to the CIA leak, that 'hole you can drive a truck =
through' did
>> not actually exist when the AV package was connected to the Internet. =
What
>> we are seeing here is not a set of vulnerabilities, it is a set of =
research
>> notes being compiled by people searching for vulnerabilities that has
>> subsequently been exfiltrated, filtered to remove the good stuff and
>> dumped.
>>=20
>> If you do end point security right, you can really be a 'PITA' to the
>> people trying to break these systems. So the idea that end point =
security
>> is futile is utterly misguided. If you use default deny approaches, =
end
>> point security can be very effective. But end point security really =
isn't
>> in scope for IETF unless we were to get into protocols for =
attestation of
>> trustworthy hardware or the like.
>>=20
>>=20
>> The reason I keep coming back to the data level security issue is =
that
>>=20
>> 1) It is in scope for IETF. Data level security protects data at rest =
and
>> in motion.
>>=20
>> 2) There have been recent expiries and are imminent pending expiries =
of key
>> IPR that makes a solution much easier.
>>=20
>> 3) It is one of the things we can fix that has the greatest security =
payoff.
>>=20
>=20


--Apple-Mail=_E0E12C86-1458-453E-A5A4-68AA74A6C7D9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi, Willi<div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 14 Mar 2017, at 6:58, willi =
uebelherr &lt;<a href=3D"mailto:willi.uebelherr@riseup.net" =
class=3D"">willi.uebelherr@riseup.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D""><br =
class=3D"">Phillip, if you use B), you don't need A).<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Consider =
email. If you and I were to use PGP or S/Mime encryption nobody can read =
the content of our messages. However, without transport-layer (or =
IP-layer. I=E2=80=99m an IPsec guy) encryption between the gmail server =
and the <a href=3D"http://riseup.net" =
class=3D"">riseup.net</a>&nbsp;server, anyone monitoring the traffic can =
know that I am sending you an email. Protecting SMTP with TLS makes the =
connection only expose that someone of gmail is sending a message to =
someone on <a href=3D"http://riseup.net" class=3D"">riseup.net</a>. =
&nbsp;And =E2=80=9Csomeone on gmail=E2=80=9D is close to being half the =
Internet. So you really still need A.</div><div><br =
class=3D""></div><div>Of course we are still vulnerable to Google or <a =
href=3D"http://riseup.net" class=3D"">riseup.net</a>&nbsp;informing on =
us. &nbsp;Maybe we need some (E) about trustworthy =
intermediaries.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">And how do you want to =
prevent traffic analysis? In a telekcommunication system, where all =
actors are privat companies and act for the state institutions and with =
a star topology, you will never be able to prvent any form of traffic =
analysis.<br class=3D""><br class=3D"">Your writing is a little bit =
naive for me.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Well, TLS 1.3 and IPsec have some anti-traffic analysis =
feature, but there is little evidence of anyone using this =
effectively.</div><div><br class=3D""></div><div>Yoav</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">greetings, willi<br class=3D""><br =
class=3D""><br class=3D""><br class=3D"">On 13/03/2017 20:13, Phillip =
Hallam-Baker wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">I =
think this particular failure demonstrates the situation pretty well:<br =
class=3D""><a =
href=3D"http://www.zdnet.com/article/leaked-us-military-files-exposed/" =
class=3D"">http://www.zdnet.com/article/leaked-us-military-files-exposed/<=
/a><br class=3D""><br class=3D"">A) Without transport encryption, every =
network link is a potential point of<br class=3D"">compromise via =
traffic analysis.<br class=3D""><br class=3D"">B) Without end-to-end =
data level encryption, every non endpoint device,<br class=3D"">every =
hard drive or removable storage is a potential point of compromise<br =
class=3D""><br class=3D"">C) Without end point security, the end points =
are a potential point of<br class=3D"">compromise.<br class=3D""><br =
class=3D"">D) Without trustworthy personnel, you are vulnerable to an =
insider threat.<br class=3D""><br class=3D"">The security controls you =
need depends on your information security assets<br class=3D"">and your =
security concerns.<br class=3D""><br class=3D"">If you are a high level =
security target then you need A + B + C + D. They<br class=3D"">are not =
alternatives, they are all requirements. It is really completely<br =
class=3D"">unhelpful for people to suggest tackling these separable =
concerns<br class=3D"">separately is 'useless'.<br class=3D""><br =
class=3D"">Just as I would not consider personnel or physical security =
at the same<br class=3D"">time as end point security, I do not want to =
consider data level security<br class=3D"">at the same time as end =
point.<br class=3D""><br class=3D"">To get back to the CIA leak, that =
'hole you can drive a truck through' did<br class=3D"">not actually =
exist when the AV package was connected to the Internet. What<br =
class=3D"">we are seeing here is not a set of vulnerabilities, it is a =
set of research<br class=3D"">notes being compiled by people searching =
for vulnerabilities that has<br class=3D"">subsequently been =
exfiltrated, filtered to remove the good stuff and<br =
class=3D"">dumped.<br class=3D""><br class=3D"">If you do end point =
security right, you can really be a 'PITA' to the<br class=3D"">people =
trying to break these systems. So the idea that end point security<br =
class=3D"">is futile is utterly misguided. If you use default deny =
approaches, end<br class=3D"">point security can be very effective. But =
end point security really isn't<br class=3D"">in scope for IETF unless =
we were to get into protocols for attestation of<br class=3D"">trustworthy=
 hardware or the like.<br class=3D""><br class=3D""><br class=3D"">The =
reason I keep coming back to the data level security issue is that<br =
class=3D""><br class=3D"">1) It is in scope for IETF. Data level =
security protects data at rest and<br class=3D"">in motion.<br =
class=3D""><br class=3D"">2) There have been recent expiries and are =
imminent pending expiries of key<br class=3D"">IPR that makes a solution =
much easier.<br class=3D""><br class=3D"">3) It is one of the things we =
can fix that has the greatest security payoff.<br class=3D""><br =
class=3D""></blockquote><br class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_E0E12C86-1458-453E-A5A4-68AA74A6C7D9--

--Apple-Mail=_1732CF29-8E01-4125-B3EC-1AB3C18085B7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYx5C8AAoJELhJCxUKWMyZqhYH/2/7Jd+bAgJXpjY0iX1mcWDt
4b9d3CanTSq9yZsB1uC7NpFIm9UibhD1/gqtFkjbflj3M7P7MaH1XE+lm0E3q2sT
l7B1HLB2wokic6TCCYOcdwMCmex3VZTIzoEkMymdxKLE0k6i/lCxJJCNCu3Xtz52
tly/TMgs5CwVrjnx2KIY5PQWslYTtbgOM6rkkYmiftooMTl7SPO3VEH1+N9tIBDQ
7D1ha7xSOBIYJVljZPed2io9qP51BIPhuQi58Wb0f8MsPt+e8JjgBv/myKCOj1NJ
HaAwoKTPPXY/Ol0WjW4cjyC1TgaPyggcReM4dj2b3Lh+ztJ7MUHMfulpST9nIw8=
=s2qt
-----END PGP SIGNATURE-----

--Apple-Mail=_1732CF29-8E01-4125-B3EC-1AB3C18085B7--


From nobody Tue Mar 14 00:43:23 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6209E12944E for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 00:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=B9qGPhvC; dkim=pass (1536-bit key) header.d=taugh.com header.b=VQOcV9tx
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y_i3gOGPov_K for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 00:43:20 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9DBF126CD8 for <ietf@ietf.org>; Tue, 14 Mar 2017 00:43:19 -0700 (PDT)
Received: (qmail 41945 invoked from network); 14 Mar 2017 07:43:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=a3d7.58c79f14.k1703; bh=DrFSkaEYlbSZYkfkifh6IFFaskG3RknuMi5U6KxSM14=; b=B9qGPhvCgswTS2bvjq/bbE+Ibz/zYMlfRTHgAY6fGzsBLu2mqD67MiQrNVhcw/cUuqx7aKcNHewINoAU79BkuRkmeIMwZkFjVsdChfz+76FJUyGgvAN2oZ8VILBLzo/uWLQJQo0/kREMLGKMnRYX57T1lfABEWCMyeGXDRfWlqH4VQCNiGzms8DpJYLyEzWC3r9WFZb9zNyUF4BU0FV7eEB98s84rHt/YLbwaO+cE2xranBrj9bfwSEZrpfNsHc1
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=a3d7.58c79f14.k1703; bh=DrFSkaEYlbSZYkfkifh6IFFaskG3RknuMi5U6KxSM14=; b=VQOcV9txEQLz3wbdaX+mOmKxDophYCFSqSqle7uOfR3iKH3q1e0ltjmfE3ZaBSGvAdORxJwb4/gl45B0NqVaQU6uUtMS655LRFg6lPci1XQFGU6GCxO1+iy4UusCeI2xy1+6pvKktHExrRwVGyNfBLWZRgNMTQyA9NFDEILpNKtc32NLl+Xrnghwjmosf8zDlUTrYsta9WgJHOwICRUSMmKFs/+0mWBKwVj9B/1wtG2UCHNIZxVWpFl+bO+Qnv3Y
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 14 Mar 2017 07:43:16 -0000
Date: 14 Mar 2017 08:43:15 +0100
Message-ID: <alpine.OSX.2.20.1703140839430.58560@ary.local>
From: "John R Levine" <johnl@taugh.com>
To: "Phillip Hallam-Baker" <phill@hallambaker.com>
Subject: Re: Do you really not care whether people accept your mail?
In-Reply-To: <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net> <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="0-403540917-1489477396=:58560"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_CBc27XNulJfcEavUpDQ7XebomY>
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 07:43:21 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-403540917-1489477396=:58560
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Mon, 13 Mar 2017, Phillip Hallam-Baker wrote:
> ​Perhaps we should just recognize the fact that SMTP does not really
> support mailing lists, ...

These complaints had nothing to do with lists or DMARC.  They were about 
sending ordinary unauthenticated mail over IPv6.  If they wanted to fix 
that problem, they could do so in 10 minutes by publishing an SPF record, 
with no other changes to the way their mail works.

R's,
John
--0-403540917-1489477396=:58560--


From nobody Tue Mar 14 01:53:20 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0351C1294C3; Tue, 14 Mar 2017 01:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ad6yHz-xtaS7; Tue, 14 Mar 2017 01:53:08 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FF96126CD8; Tue, 14 Mar 2017 01:53:08 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id A0EA27D4; Tue, 14 Mar 2017 09:53:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.205]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id RZtkjCIBmeTl; Tue, 14 Mar 2017 09:53:05 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Tue, 14 Mar 2017 09:53:06 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0DAB92003D; Tue, 14 Mar 2017 09:53:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id o9pkS3D55_bm; Tue, 14 Mar 2017 09:53:05 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3B0F52003C; Tue, 14 Mar 2017 09:53:05 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id B98803EBBBB2; Tue, 14 Mar 2017 09:53:09 +0100 (CET)
Date: Tue, 14 Mar 2017 09:53:09 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Review of draft-ietf-lmap-information-model-17
Message-ID: <20170314085308.GA54939@elstar.local>
Mail-Followup-To: Russ Housley <housley@vigilsec.com>, gen-art@ietf.org, lmap@ietf.org, ietf@ietf.org, draft-ietf-lmap-information-model.all@ietf.org
References: <148814339074.2901.10793232146724828053.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <148814339074.2901.10793232146724828053.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1kgsGzaELjPRtke9p0GBf7KRcnE>
Cc: gen-art@ietf.org, draft-ietf-lmap-information-model.all@ietf.org, ietf@ietf.org, lmap@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 08:53:11 -0000

Russ,

thanks for your review. See my response to your comments inline.

On Sun, Feb 26, 2017 at 01:09:50PM -0800, Russ Housley wrote:
> Reviewer: Russ Housley
> Review result: Almost Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
> 
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Document: draft-ietf-lmap-information-model-17
> Reviewer: Russ Housley
> Review Date: 2017-02-26
> IETF LC End Date: 2017-03-08
> IESG Telechat date: Unknown
> 
> Summary: Ready
> 
> Major Concerns:
> 
> Section 3.1 says that the pre-configuration information contains
> the certificate of the Controller or the certificate of the CA
> which issued the certificate for the Controller.  Section 3.1.1
> includes ma-preconfig-credentials.  Are these the same?

The information model on purse is somewhat unspecific about what
exactly the security credentials are. The reason is that the
information model maps to two data models today (one in the BBF and
one in the IETF). The IETF data model can be accessed over NETCONF and
RESTCONF. RESTCONF runs over HTTP/TLS while NETCONF by default runs
over SSH. As a consequence, the various credentials needed to support
the different protocols varies.

> Section 6 says that secure communication channels are needed.  This
> means
> that some components of this system (at least the Controller) must
> have
> secret keys or private keys.  I think that Section 6 should talk
> about
> which components of this system have keys and the consequences if the
> keys are not well protected.

There is a fairly large discussion of security issues in RFC 7594
and we point to them in section 6 rather than repeating them here.

   An implementation of this Information Model should support all the
   security and privacy requirements associated with the LMAP Framework
   [RFC7594].

> Minor Concerns:
> 
> The Introduction in RFC 7594 says: "There is a desire to be able
> to coordinate the execution of broadband measurements and the
> collection of measurement results across a large scale set of
> Measurement Agents (MAs)."  The Fact that LMAP is about broadband
> measurements should be stated in the first paragraph of the
> Introduction of this document.

I suggest to add a sentence including a reference to RFC 7536 so
that the 1st paragraph of the Introduction reads:

   A large-scale measurement platform is a collection of components that
   work in a coordinated fashion to perform measurements from a large
   number of vantage points.  A typical use case is the execution of
   broadband measurements [RFC7536].  The main components of a large-
   scale measurement platform are the Measurement Agents (hereafter
   MAs), the Controller(s) and the Collector(s).

> Nits:
> 
> In Section 3, the reason for the 6 categories should probably be
> placed before the list instead of several paragraphs later.

I agree, I have moved the text up (and due to some other comment we
started to call the categories 'aspects'). So the new text reads:

   The information model is divided into six aspects.  Firstly the
   grouping of information facilitates reader understanding.  Secondly,
   the particular groupings chosen are expected to map to different
   protocols or different transmissions within those protocols.

> In 3.1: s/If the MA ID is not provided at this stage then/
>          /If the MA ID is not provided at this stage, then/

fixed

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Tue Mar 14 01:54:26 2017
Return-Path: <tjc@ecs.soton.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 4252F1294F4 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 01:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hKLbdVXWiUT6 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 01:54:21 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F6C71294E0 for <ietf@ietf.org>; Tue, 14 Mar 2017 01:54:12 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2E8s1wf030524; Tue, 14 Mar 2017 08:54:01 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v2E8s1wf030524
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1489481642; bh=zX3KVJ/TD3l2at3ZsJcjK8X90nU=; h=From:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References; b=oDTpNG5l/sScwidFEiu6xQk6QXA2xm3JJMMAwxRELU9mocPdHSnX4g0K5XROrvPgM SKC+IHHmadlSytLhRPBoSNduKt2KXh7sC+3bYfz8C/3VcoestPE+bwGk77UVVUlXjs VdkbtiCkqyVn5D7wt9nQZgobrXnKzAc/kxBWwNLI=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y2D8s11720201197iB ret-id none; Tue, 14 Mar 2017 08:54:02 +0000
Received: from [10.1.11.164] (firewall-lho-ext.management.janet.ac.uk [194.82.140.195]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2E8rvZN013855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Mar 2017 08:53:58 GMT
From: Tim Chown <tjc@ecs.soton.ac.uk>
Message-ID: <EMEW3|2ae60e4618a4ca12f14a455f9eb23ec6y2D8s103tjc|ecs.soton.ac.uk|6006F740-4688-486E-84DF-FA676DDBCA00@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_05072DCA-7F0D-4E49-9600-9B270B3FF1BD"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Do you really not care whether people accept your mail?
Date: Tue, 14 Mar 2017 08:53:56 +0000
In-Reply-To: <alpine.OSX.2.20.1703140839430.58560@ary.local>
To: John R Levine <johnl@taugh.com>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net> <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com> <alpine.OSX.2.20.1703140839430.58560@ary.local> <6006F740-4688-486E-84DF-FA676DDBCA00@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y2D8s1172020119700; tid=y2D8s11720201197iB; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v2E8s1wf030524
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-TqqgI9J7g9YeyRbujTVfF7rva0>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 08:54:24 -0000

--Apple-Mail=_05072DCA-7F0D-4E49-9600-9B270B3FF1BD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 14 Mar 2017, at 07:43, John R Levine <johnl@taugh.com> wrote:
>=20
> On Mon, 13 Mar 2017, Phillip Hallam-Baker wrote:
>> =E2=80=8BPerhaps we should just recognize the fact that SMTP does not =
really
>> support mailing lists, ...
>=20
> These complaints had nothing to do with lists or DMARC.  They were =
about sending ordinary unauthenticated mail over IPv6.  If they wanted =
to fix that problem, they could do so in 10 minutes by publishing an SPF =
record, with no other changes to the way their mail works.

I must say, my chosen hosting provider, who support IPv6 very well, make =
publishing an SPF record very easy. It=E2=80=99s just a click on the =
control panel.=20

I do think though that we could probably make it clearer somewhere =
=E2=80=98official=E2=80=99 what the issues are for people signing up to =
our lists, e.g. perhaps at https://www.ietf.org/list/ =
<https://www.ietf.org/list/>.  I had a quick look and couldn=E2=80=99t =
see anything obvious there.

Tim=

--Apple-Mail=_05072DCA-7F0D-4E49-9600-9B270B3FF1BD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
14 Mar 2017, at 07:43, John R Levine &lt;<a =
href=3D"mailto:johnl@taugh.com" class=3D"">johnl@taugh.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">On Mon, 13 Mar 2017, Phillip Hallam-Baker wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D"">=E2=80=8BPerhaps we =
should just recognize the fact that SMTP does not really<br =
class=3D"">support mailing lists, ...<br class=3D""></blockquote><br =
class=3D"">These complaints had nothing to do with lists or DMARC. =
&nbsp;They were about sending ordinary unauthenticated mail over IPv6. =
&nbsp;If they wanted to fix that problem, they could do so in 10 minutes =
by publishing an SPF record, with no other changes to the way their mail =
works.<br class=3D""></div></div></blockquote></div><br class=3D""><div =
class=3D"">I must say, my chosen hosting provider, who support IPv6 very =
well, make publishing an SPF record very easy. It=E2=80=99s just a click =
on the control panel.&nbsp;</div><div class=3D""><br class=3D""></div><div=
 class=3D"">I do think though that we could probably make it clearer =
somewhere =E2=80=98official=E2=80=99 what the issues are for people =
signing up to our lists, e.g. perhaps at&nbsp;<a =
href=3D"https://www.ietf.org/list/" =
class=3D"">https://www.ietf.org/list/</a>. &nbsp;I had a quick look and =
couldn=E2=80=99t see anything obvious there.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Tim</div></body></html>=

--Apple-Mail=_05072DCA-7F0D-4E49-9600-9B270B3FF1BD--


From nobody Tue Mar 14 02:17:12 2017
Return-Path: <leifj@mnt.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 49C84129524 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 02:17:10 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mI94Au95aX_z for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 02:17:07 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75BD0129469 for <ietf@ietf.org>; Tue, 14 Mar 2017 02:17:07 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id y193so73662446lfd.3 for <ietf@ietf.org>; Tue, 14 Mar 2017 02:17:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=u7FEv2xz5UJrY+GfQH+qhI4yVq4z1EkbL0rr+fs2Kxg=; b=Xqe7TZwE3EVx+1L9tSF6NTPlDQ6Ou40IYl9gt3yKImWpdFQHtA59XTtckebdh7R4jj Z8m1Yydz+uqmocPT8XhOSnPs/ROMc2M5lpEHkPVgeM4ZLFZm4erAMtUhI1QmptfAp7Vn vxzl7yYDKHowEn7oL4y983asIDy1hWpjIbOD4icsPnKg1C+2WZpSmoBbbFBQ9AmJqk8P NF96FW4S7mXIN4oiVMmomc5Bax/LWrsjlWaZcY+/QeHm2OQSacdAFxVM+1i8iaERebTD 8ZyoJo7C5RGXoZNU66P27oXLbETLGGpNgGXm6vaERJBC44/s9FpE6hcHWdgaP25hJ+c/ fA3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=u7FEv2xz5UJrY+GfQH+qhI4yVq4z1EkbL0rr+fs2Kxg=; b=WcgF3n7OyhUVZ1KdxoWsBMZn2wBpGkUDFngFf7vxl59MVpYt5xAf5OVN4l+l65IlS3 uNZeWPzIX7BAse/TDLmEygZt1fvSZwSyWRYubds5uZHuhkR9IH4N9x4G8dUMVN81w3d1 8oizrqshmbCx+rw2paaCKkN3dGvB83J5WY+F+Kcn4txoTCoIM1ALqJLHijFSlwGgbOHn eN2tKV5HkCGxJAGmZN5PCS96zULvRxt/bOGslN0T0Zj2WMVwLZusnNagVmXqYC76h2DT Ueq7fozpQFUaIX/CxgFjVLFNc4hY6e3UpxEdrriyLBYto4yi3fG5oQCpSo7zCcnlwyAp tghQ==
X-Gm-Message-State: AMke39nz6QtCgLIGf++GuqbS2Kbwpt7bwieS+fsnKPUlxhone6XFzFtW6Via+DUmqm+dWQ==
X-Received: by 10.25.216.232 with SMTP id r101mr8628949lfi.28.1489483024972; Tue, 14 Mar 2017 02:17:04 -0700 (PDT)
Received: from ?IPv6:2001:6b0:7:1:198e:bf37:ab2a:c6df? ([2001:6b0:7:1:198e:bf37:ab2a:c6df]) by smtp.gmail.com with ESMTPSA id 187sm4165527ljf.32.2017.03.14.02.17.03 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Mar 2017 02:17:04 -0700 (PDT)
Subject: Re: Review of draft-ietf-lmap-information-model-17
To: ietf@ietf.org
References: <148814339074.2901.10793232146724828053.idtracker@ietfa.amsl.com> <20170314085308.GA54939@elstar.local>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <d8ea9f64-7558-4514-6b1f-90b5062a4060@mnt.se>
Date: Tue, 14 Mar 2017 10:17:02 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <20170314085308.GA54939@elstar.local>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xy57EIA0TQCbAC2WRPPGTCgwyoo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 09:17:10 -0000

On 2017-03-14 09:53, Juergen Schoenwaelder wrote:
> Russ,
> 
> thanks for your review. See my response to your comments inline.
> 
> On Sun, Feb 26, 2017 at 01:09:50PM -0800, Russ Housley wrote:
>> Reviewer: Russ Housley
>> Review result: Almost Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair. Please wait for direction from your
>> document shepherd or AD before posting a new version of the draft.
>>
>> For more information, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-lmap-information-model-17
>> Reviewer: Russ Housley
>> Review Date: 2017-02-26
>> IETF LC End Date: 2017-03-08
>> IESG Telechat date: Unknown
>>
>> Summary: Ready
>>
>> Major Concerns:
>>
>> Section 3.1 says that the pre-configuration information contains
>> the certificate of the Controller or the certificate of the CA
>> which issued the certificate for the Controller.  Section 3.1.1
>> includes ma-preconfig-credentials.  Are these the same?
> 
> The information model on purse is somewhat unspecific about what
> exactly the security credentials are. The reason is that the
> information model maps to two data models today (one in the BBF and
> one in the IETF). The IETF data model can be accessed over NETCONF and
> RESTCONF. RESTCONF runs over HTTP/TLS while NETCONF by default runs
> over SSH. As a consequence, the various credentials needed to support
> the different protocols varies.
> 

You keep missing my point which is this: I understand the difference
between a data model and an information model. What I don't understand
is if you need one or two credentials in the information model.

	Cheers LEif

>> Section 6 says that secure communication channels are needed.  This
>> means
>> that some components of this system (at least the Controller) must
>> have
>> secret keys or private keys.  I think that Section 6 should talk
>> about
>> which components of this system have keys and the consequences if the
>> keys are not well protected.
> 
> There is a fairly large discussion of security issues in RFC 7594
> and we point to them in section 6 rather than repeating them here.
> 
>    An implementation of this Information Model should support all the
>    security and privacy requirements associated with the LMAP Framework
>    [RFC7594].
> 
>> Minor Concerns:
>>
>> The Introduction in RFC 7594 says: "There is a desire to be able
>> to coordinate the execution of broadband measurements and the
>> collection of measurement results across a large scale set of
>> Measurement Agents (MAs)."  The Fact that LMAP is about broadband
>> measurements should be stated in the first paragraph of the
>> Introduction of this document.
> 
> I suggest to add a sentence including a reference to RFC 7536 so
> that the 1st paragraph of the Introduction reads:
> 
>    A large-scale measurement platform is a collection of components that
>    work in a coordinated fashion to perform measurements from a large
>    number of vantage points.  A typical use case is the execution of
>    broadband measurements [RFC7536].  The main components of a large-
>    scale measurement platform are the Measurement Agents (hereafter
>    MAs), the Controller(s) and the Collector(s).
> 
>> Nits:
>>
>> In Section 3, the reason for the 6 categories should probably be
>> placed before the list instead of several paragraphs later.
> 
> I agree, I have moved the text up (and due to some other comment we
> started to call the categories 'aspects'). So the new text reads:
> 
>    The information model is divided into six aspects.  Firstly the
>    grouping of information facilitates reader understanding.  Secondly,
>    the particular groupings chosen are expected to map to different
>    protocols or different transmissions within those protocols.
> 
>> In 3.1: s/If the MA ID is not provided at this stage then/
>>          /If the MA ID is not provided at this stage, then/
> 
> fixed
> 
> /js
> 


From nobody Tue Mar 14 02:43:13 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 766FD12952E for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 02:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=aJ7uDqdc; dkim=pass (1536-bit key) header.d=taugh.com header.b=J1t+o9Lj
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rnES3Oh7ZBZu for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 02:43:11 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB80E129524 for <ietf@ietf.org>; Tue, 14 Mar 2017 02:43:10 -0700 (PDT)
Received: (qmail 63931 invoked from network); 14 Mar 2017 09:43:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-id:user-agent; s=f9b9.58c7bb2a.k1703; bh=Bmgzuwx+OY1RVZdsioK+MH7aaA2l1o2x4CYjJmBC5JU=; b=aJ7uDqdcd8XGU+RQtuOC2IdVCA8PfKChmKx0i3g7eWSCzNOKYyrkigzhQOxlxoqvhzg59dbF80G7zU5USG13DPrE7+riAvp3Ep262pH/TQJxGKtrlvUm5WfXVVzJ5Y7zFYhs4xrg4IUIqR2J5xO8Rly/CS/7N/ZzJ9xnnDl1ERvlCKn/LDFEaYAMIaomib78SvIMMw2qlFudJsMtdDdG+DYJuYHzIHM7NMXeTSVK9n63UlTcangrNOHDjNTav2H7
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-id:user-agent; s=f9b9.58c7bb2a.k1703; bh=Bmgzuwx+OY1RVZdsioK+MH7aaA2l1o2x4CYjJmBC5JU=; b=J1t+o9Lj6D0981+IoARKtvJOOlA6fysD/OOLnAsUknyglMFYlDJHdYL9BEo+cR+uwawzEy2QrkY2dhgzC9TSnKcJriLupUoHEmNVn3ZOjtmsr/XWZ3HPYiNELreJjV2a29ET9NtULG3opdwHVNd2gHOjUpSMvUab7l1hXbhy5qxi1UyScLllmbSYEfcDqH1RQWI/GBxUgIkNFl/6wtNxZV4LzCoDrAmnlYBZ2Ym/8yuCyYzIU/wtynWlqSci0Glz
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 14 Mar 2017 09:43:06 -0000
Date: 14 Mar 2017 10:43:05 +0100
Message-ID: <alpine.OSX.2.20.1703141010060.59120@ary.local>
From: "John R Levine" <johnl@taugh.com>
To: "Tim Chown" <tjc@ecs.soton.ac.uk>
Subject: Re: Do you really not care whether people accept your mail?
In-Reply-To: <EMEW3|2ae60e4618a4ca12f14a455f9eb23ec6y2D8s103tjc|ecs.soton.ac.uk|6006F740-4688-486E-84DF-FA676DDBCA00@ecs.soton.ac.uk>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net> <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com> <alpine.OSX.2.20.1703140839430.58560@ary.local> <6006F740-4688-486E-84DF-FA676DDBCA00@ecs.soton.ac.uk> <EMEW3|2ae60e4618a4ca12f14a455f9eb23ec6y2D8s103tjc|ecs.soton.ac.uk|6006F740-4688-486E-84DF-FA676DDBCA00@ecs.soton.ac.uk>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="0-1127813890-1489482645=:59120"
Content-ID: <alpine.OSX.2.20.1703141011160.59120@ary.local>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-YDeOV6BeLuMkZRMnqLr4zsWd8c>
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 09:43:12 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1127813890-1489482645=:59120
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Content-ID: <alpine.OSX.2.20.1703141011161.59120@ary.local>

> I do think though that we could probably make it clearer somewhere 
> ‘official’ what the issues are for people signing up to our lists, e.g. 
> perhaps at https://www.ietf.org/list/ <https://www.ietf.org/list/>.  I 
> had a quick look and couldn’t see anything obvious there.

Once again, these complaints had nothing to do with our lists or anyone 
else's.  Carsten was complaining about sending mail to NIST, Philip about 
sending mail to Gmail.

R's,
John
--0-1127813890-1489482645=:59120--


From nobody Tue Mar 14 02:46:02 2017
Return-Path: <tjc@ecs.soton.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 2EFCC12952D for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 02:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tu8FhD1fiO9k for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 02:45:59 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B690129524 for <ietf@ietf.org>; Tue, 14 Mar 2017 02:45:59 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2E9jv52012352; Tue, 14 Mar 2017 09:45:57 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v2E9jv52012352
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1489484757; bh=BXbOAVjM0DiS0w6KRVLjuu6kS/A=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=IOaxMDH90GUdh9M/JxwRkkeQ/2AGBdbA6iflEOUl1MvL3CSeU8UvBAIYqK6VdHJiS KlTJhyILtWUAJFeOMQvV24JZ0NxPQCl5q1R9FIbrsL1zDItWQlKGCp/D68Todszh1N +xzFsozOWE7gDNIEvgBSZ+nmHu40lqZolznWS3kE=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y2D9jv1720202511Ym ret-id none; Tue, 14 Mar 2017 09:45:57 +0000
Received: from [10.1.11.164] (firewall-lho-ext.management.janet.ac.uk [194.82.140.195]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2E9jolr032199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Mar 2017 09:45:51 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Do you really not care whether people accept your mail?
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <alpine.OSX.2.20.1703141010060.59120@ary.local>
Date: Tue, 14 Mar 2017 09:45:50 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|bba7f5bce4739a47add3b4c2dd47ad62y2D9jv03tjc|ecs.soton.ac.uk|DA187B92-0D87-4D6F-9E4E-CC921277AB42@ecs.soton.ac.uk>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net> <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com> <alpine.OSX.2.20.1703140839430.58560@ary.local> <6006F740-4688-486E-84DF-FA676DDBCA00@ecs.soton.ac.uk> <EMEW3|2ae60e4618a4ca12f14a455f9eb23ec6y2D8s103tjc|ecs.soton.ac.uk|6006F740-4688-486E-84DF-FA676DDBCA00@ecs.soton.ac.uk> <alpine.OSX.2.20.1703141010060.59120@ary.local> <DA187B92-0D87-4D6F-9E4E-CC921277AB42@ecs.soton.ac.uk>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y2D9jv172020251100; tid=y2D9jv1720202511Ym; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v2E9jv52012352
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g-GmoH_cXbT1ThBiQhMgF0sPS_M>
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 09:46:01 -0000

> On 14 Mar 2017, at 09:43, John R Levine <johnl@taugh.com> wrote:
>=20
>> I do think though that we could probably make it clearer somewhere =
=E2=80=98official=E2=80=99 what the issues are for people signing up to =
our lists, e.g. perhaps at https://www.ietf.org/list/ =
<https://www.ietf.org/list/>.  I had a quick look and couldn=E2=80=99t =
see anything obvious there.
>=20
> Once again, these complaints had nothing to do with our lists or =
anyone else's.  Carsten was complaining about sending mail to NIST, =
Philip about sending mail to Gmail.

But a bit of awareness raising can=E2=80=99t hurt, can it?  And if we =
had the issue documented on an IETF page, it=E2=80=99s then easy to =
point people to that link rather than rehash the explanations.

Tim=


From nobody Tue Mar 14 03:38:54 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F051294C2 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 03:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0RP3rGBrf3WZ for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 03:38:51 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id E3E3B1293DC for <ietf@ietf.org>; Tue, 14 Mar 2017 03:38:50 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1cnjqr-0000GkC; Tue, 14 Mar 2017 11:38:49 +0100
Message-Id: <m1cnjqr-0000GkC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: Do you really not care whether people accept your mail? 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
In-reply-to: Your message of "13 Mar 2017 23:51:06 +0100 ." <alpine.OSX.2.20.1703132331590.54839@ary.local> 
Date: Tue, 14 Mar 2017 11:38:48 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E2MEG4jFQv4d7hJ-Tn0mmpl0j5I>
Cc: John R Levine <johnl@taugh.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 10:38:53 -0000

>On Mon, 13 Mar 2017, Carsten Bormann wrote:
>> The most likely outcome is that local admins will ?upgrade" our mail 
>> system by turning off IPv6.  (We have had IPv6 deployed for some 18 
>> years now.)
>
>On Mon, 13 Mar 2017, Philip Homburg wrote:
>> Getting mail delivered to gmail over IPv6 works most of the time without
>> ever setting up SPF or DKIM. Gmail does seem to be the single most
>> unreliable mail server that I know of, mostly due to their attempts
>> to be more strict on IPv6.
>
>As I hope everyone knows, receiving mail requires orders of magnitude more 
>work than sending it.  Even 20 years ago before spam was an issue, 
>recipients had to receive it, route it, store it somewhere, filter it with 
>sieve or procmail, and provide POP or IMAP for the recipient to collect 
>it.  These days, with 90% of mail being spam or worse, there's another 
>magnitude of work in trying to separate the real mail from the flood of 
>junk.  Or try this thought experiment: how hard would it be to send a 
>million messages a day from your laptop (easy), and how hard would be be 
>to receive and deliver a million messages a day on that laptop 
>(impossible.)

It is now more than 2 decades that people keep proposing FUSSP (Final
Ultimate Solution to the Spam Problem) after FUSSP.

"There is spam problem, we need to do something"
"What you propose doesn't work"
"There is spam problem, we need to do something, this is something"

Is there any point arguing against a FUSSP? By and large there isn't. 
Until spammers start exploiting the FUSSP at a large scale, there is always
a very creative argument why spammers cannot deal with this particular FUSSP.

Some FUSSPs remain small enough that spammers don't bother. So they
seem effective. Typically in those cases there are enough negative side effects
to keep them small.

>The point of authentication schemes like SPF and DKIM is to make it easier 
>for recipients to tell that your mail is from you, so they can treat it 
>differently from the spam.  Everywhere else, the response is OK, I would 
>prefer that people get the mail I send them, I will set up authentication 
>because it is not hard (SPF takes about 5 minutes), and it helps the 
>people who are handling my mail with the mail system they are paying for.

So, we have a succession of SPF, DKIM, and now DMARC that are supposed to
protect against phishing or other identity issues. Fine, I don't have a
phishing problem, so I can ignore it.

Except of course, that it doesn't take long or it becomes a FUSSP. Look
there is no spam with [insert technology du jour]. It works.

As many people have found out, if you allow a FUSSP to bypass traditional
spam filters, then spammers quickly find out. So these things just
pile up. Or, more common, just get ignored.

>I can also assure you from many conversations with large mail providers 
>that you will increasingly find that recipients will conclude that if you 
>can't be bothered to authenticate your mail, they can't be bothered to 
>deliver it.  It's their mail system, they get to do that.

So for my mail system I look at what is actually common enough that I need
to consider it.

Reverse DNS is a rather silly FUSSP, but common enough that is is required.
And by and large I like reverse DNS.

In my experience, essentially no mail gets lost if you leave out SPF, DKIM,
DMARC. The only exception is gmail that occasionally rejects e-mail. 

In the context of IPv6 we now have an additional problem. Sites that have
filters that are more strict for IPv6 than for IPv4. The obvious very 
quick workaround for many mail admins is to avoid delivering mail over IPv6.
Of course, that just increases the SPAM/HAM ratio, justifying more draconian
measures. Which in the end will just kill IPv6 as a transport for e-mail.



From nobody Tue Mar 14 04:08:02 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1726C12954D; Tue, 14 Mar 2017 04:07:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-mpls-tp-temporal-hitless-psm-13
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148948967806.12630.17780798711864289686@ietfa.amsl.com>
Date: Tue, 14 Mar 2017 04:07:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P55QbmyOL7hpU87LNPV27EyxPfA>
Cc: mpls@ietf.org, draft-ietf-mpls-tp-temporal-hitless-psm.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 11:07:58 -0000

Reviewer: Stewart Bryant
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-mpls-tp-temporal-hitless-psm-??
Reviewer: Stewart Bryant
Review Date: 2017-03-14
IETF LC End Date: 2017-03-03
IESG Telechat date: 2017-03-16

Summary: Given that the implications for the MPLS architecture and the
feasibility of a solution are currently unknown, the IESG needs to
decide whether publication at this stage is appropriate, or whether a
feasible solution should first be identified.

Major issues:

I previously raised the following two issues:

"Whilst this text describes a list of issues with the existing IETF
design, it should be remembered that the design was the best that
could be accomplished at the time within the constraints of the MPLS
architecture. So that leaves the reader with a question: do the
authors now have an insight into how a solution can now be designed to
meet the requirement,  or do the authors intend to propose a change to
the MPLS architecture, or is the intention to publish this to state
the requirements in the hope that someone will eventually propose a
solution?"

and 

"The text around Figure 8 explains the deficiency in TTL based section
of an OAM monitoring point in MPLS. However the authors give no
indication of a feasible alternative."

The authors responded by adding the following text:

"Further works are required to evaluate how proposed requirements
match with current MPLS architecture and to	identify possibile
solutions."

When RFC6371 was written the problems cited in this text were known,
and despite much work no one could identify a solution at the time.

The key question for the IESG is whether it is appropriate to publish
this requirements text when  no one has any idea of the impact on the
MPLS architecture or if there are any practical solutions to the
problems raised.

In response to the issue:

"In particular, performance monitoring measurements (e.g.  Delay
Measurement and Packet Loss  Measurement) are sensitive to these
changes."

Whilst technically true, I am not sure the impact on delay is
significant in any engineering sense. We are talking four bytes per
packet over a service that is going at 1 to 400 Gb/s. Again it is hard
to imagine a significant impact on loss. If this is a key point it
need some justification from an engineering perspective.

The authors add text:

As an example,increasing the packet lenght may impact on packet loss
due to MTU	 settings, modifying the label stack may introduce packet
loss or it may fix packet loss depending on the configuration status
so modifying network conditions.  Such changes influence packets delay
too even if, from a practical point of view, it is likely that only a
few services will experience a practical impact.

Again it is for the IESG to decide whether in the light of the
architectural and practical issues noted earlier, the problem  is
severe enough to warrant publication of this document at this stage.




From nobody Tue Mar 14 04:22:06 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DCB4127078; Tue, 14 Mar 2017 04:22:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-lamps-eai-addresses-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148949052209.12632.10288586023034172850@ietfa.amsl.com>
Date: Tue, 14 Mar 2017 04:22:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0ZnZxT2demnzsuCreRLryFFURkU>
Cc: spasm@ietf.org, ietf@ietf.org, draft-ietf-lamps-eai-addresses.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 11:22:02 -0000

Reviewer: Stewart Bryant
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-lamps-eai-addresses-??
Reviewer: Stewart Bryant
Review Date: 2017-03-14
IETF LC End Date: 2017-01-30
IESG Telechat date: 2017-03-16

Summary: I though that -6 was ready. Since then a lot of new text was
added. I have checked the diffs and as a non-specialist I cannot see
any problem with the added text, and so conclude that it is still
ready.

Major issues: None

Minor issues: None

Nits/editorial comments: None



From nobody Tue Mar 14 04:30:07 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 30A3D1294CE; Tue, 14 Mar 2017 04:30:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-hardie-privsec-metadata-insertion-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148949100616.12741.2971841858974361943@ietfa.amsl.com>
Date: Tue, 14 Mar 2017 04:30:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/whcNNS3MI7SGOaWyVrYEG9oEs9w>
Cc: ietf@ietf.org, draft-hardie-privsec-metadata-insertion.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 11:30:06 -0000

Reviewer: Stewart Bryant
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-hardie-privsec-metadata-insertion-??
Reviewer: Stewart Bryant
Review Date: 2017-03-14
IETF LC End Date: 2017-02-21
IESG Telechat date: 2017-03-16

Summary: Ready with slightly more minor nits than before.

Major issues: None

Minor issues: None

Nits/editorial comments: 

1.  Introduction
....
   exploited in the attacks document in [RFC7258] and the threats
s/document/documented/

=====

There also tensions with latency of operation.

Missing "are", although I think it should probably be "There is
tension"

=====

to restore metadat 

Should be: to restore metadata

=====


From nobody Tue Mar 14 06:59:09 2017
Return-Path: <cowan@ccil.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 19F7B1203D2 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 06:59:03 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ccil-org.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXXLG1Yjpemo for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 06:59:01 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D6891275FA for <ietf@ietf.org>; Tue, 14 Mar 2017 06:59:01 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id v186so64690063wmd.0 for <ietf@ietf.org>; Tue, 14 Mar 2017 06:59:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=92DQ99N52Mv2iShepHhQgM+fTsrrCOj13qiSSVkxp8w=; b=xJUXLSzDkpNLOU16JTwrnKOqLGmy6l3AUQuYrhVp6/mSh6gWIeQ/06IicQCgzpxUnH UWrqEgBkPCS1BlVCb10KW1o5NnDQLdzDgPXUn4HJS1RNQd0q0t1zAJbJiY2LIkanMAXd N4M2OJfYJMczhyxXdnMZu4bLmEKeX3mTyBfbsiaKkO+mjqoqDKvy6mf2L2xrtajnzzzF u0bcDuesC2mBB71xaySaEQDQbDfSFGTRnIJ2Clf2OIccdx3XUFb/XhsZ88oD2UoZjLMN Y4/B0grgTeCYg6Vx5y3rKaKPzgmAk0jcr9I5gw20wgkY3en+tqfm53UvWeHIkrh9QkJK 8YtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=92DQ99N52Mv2iShepHhQgM+fTsrrCOj13qiSSVkxp8w=; b=TlH0qjbzzzM0MtQ52qWrUO6mX18TczPPWtJGLTFiYypIlcbk8K3e2DpHress/nUjbg BwpxLtjj8KIGj3PmiVUHngFC/84Ck+ax8zywISfAwhAulI2/pF9+6Pz9ZH20B5AbTdiG 7mz/JeYz8vqq/sHZGv8IyzZR4rdCteGeNN9CI+pBQd/+L4XfWlNzHCtZpqnpuCb4vBzL nayNF9WZJLblRm5afMgU5F+XNmURXaK5OEYhIREqkuHsDzkopg0jIx6TA6YavG6ZJEN9 X89U0eCg2TAla5NkcojWkrnu/kYgTLsMIzlJLIFgbHh/yE9ZlmXhLmwmvcuN4sIFC9FA Kn/A==
X-Gm-Message-State: AFeK/H2RtdjTCTLwpumBqhCOl9EPBkDb/jnbQ4mJe5GkJbDm5Em/m4ApzQY7uVyESe4A24WyJ6+ux4bYLYz41bYG
X-Received: by 10.28.107.14 with SMTP id g14mr15885450wmc.106.1489499939764; Tue, 14 Mar 2017 06:58:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.181.14 with HTTP; Tue, 14 Mar 2017 06:58:39 -0700 (PDT)
In-Reply-To: <1F1D1DCB-767F-490D-A425-AB5E66D51D3E@tzi.org>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com> <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de> <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp> <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com> <1e075450-d958-db9c-ae63-3cbf3733024c@outer-planes.net> <cf6e35ba-6a67-4b35-d4e1-e99fee6e9f19@gmx.de> <1F1D1DCB-767F-490D-A425-AB5E66D51D3E@tzi.org>
From: John Cowan <cowan@ccil.org>
Date: Tue, 14 Mar 2017 09:58:39 -0400
Message-ID: <CAD2gp_R7raq0mzfhATTYONdowBm0HvVHFAqJqoVcLmYABrgPpA@mail.gmail.com>
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=001a11442d9ecda206054ab13aeb
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zuw2Q_ogbQwVZQT4L3uut5dLWow>
Cc: Julian Reschke <julian.reschke@gmx.de>, draft-ietf-jsonbis-rfc7159bis.all@ietf.org, secdir@ietf.org, IETF <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 13:59:03 -0000

--001a11442d9ecda206054ab13aeb
Content-Type: text/plain; charset=UTF-8

On Mon, Mar 13, 2017 at 3:57 PM, Carsten Bormann <cabo@tzi.org> wrote:

Consistency is the hobgoblin of the little minds.
>

The actual quotation says "foolish consistency".  But not all consistency
is foolish.


> (Apparently, not having that nonsense in there did not hurt for 7159?
> If people want to implement something useless and cannot figure this stuff
> out, should we help them?)
>
> Putting back any form of apparent support for UTF-16 and UTF-32 is a
> regression.
>

In my opinion, we should either take all references to UTF-16 or UTF-32
out, or add back a correct detection algorithm. UTF-8 is what is actually
interoperable, and interoperability is what RFCs are supposed to be all
about.

--

--001a11442d9ecda206054ab13aeb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Mar 13, 2017 at 3:57 PM, Carsten Bormann <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;</span> w=
rote:</div><div class=3D"gmail_quote"><br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv id=3D":1d9" class=3D"a3s aXjCH m15ac93eeec0f9dd1">Consistency is the hob=
goblin of the little minds.<br></div></blockquote><div><br></div><div>The a=
ctual quotation says &quot;foolish consistency&quot;.=C2=A0 But not all con=
sistency is foolish.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
div id=3D":1d9" class=3D"a3s aXjCH m15ac93eeec0f9dd1">
(Apparently, not having that nonsense in there did not hurt for 7159?<br>
If people want to implement something useless and cannot figure this stuff =
out, should we help them?)<br>
<br>
Putting back any form of apparent support for UTF-16 and UTF-32 is a regres=
sion.</div></blockquote></div><div class=3D"gmail_extra"><br></div>In my op=
inion, we should either take all references to UTF-16 or UTF-32 out, or add=
 back a correct detection algorithm. UTF-8 is what is actually interoperabl=
e, and interoperability is what RFCs are supposed to be all about.</div><di=
v class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">--=C2=A0</div>=
<div class=3D"gmail_extra"><br><br></div></div>

--001a11442d9ecda206054ab13aeb--


From nobody Tue Mar 14 10:52:01 2017
Return-Path: <willi.uebelherr@riseup.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 A56E312DDA6 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 10:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2Fzi4LQE_T0 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 10:51:59 -0700 (PDT)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF4F512DDA5 for <ietf@ietf.org>; Tue, 14 Mar 2017 10:51:58 -0700 (PDT)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 69D5B1A1B08 for <ietf@ietf.org>; Tue, 14 Mar 2017 17:51:58 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1489513918; bh=ZIV4oYom9mpGEDGhRcswRjM5GJs32WfBiL2rS7HYo6s=; h=Subject:References:To:From:Date:In-Reply-To:From; b=RIUQppfuow+x6tTC6KLKh8UBkhO7pdR/pS8CPCyk2fJHV/8pzdG9owBQWgAjEIiBT HICIwg86QhjSdSg/IqNCqy3Yw1YuZrQC1HIEiI8jVL9owdIWZukl8kNsdamhlWnx75 Zr/mvJRJOPwzyYRT+SyUkl5VDnQ12mGU/Usu4WH8=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id 9209F1C0128
Subject: Re: The CIA mentions us
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com> <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie> <CC5E2EDA-5533-4FA0-8350-CE45311DD8B4@fugue.com> <CAMm+Lwh4Pn39D4r+k5HQnaxtZbTkpRCmAFMg77vLRVQzKY4S7g@mail.gmail.com> <d9b02513-fcb3-888d-8e65-831d1078c24b@riseup.net> <7AD4B72D-BABA-4789-9615-F6E659D09B4D@gmail.com>
To: IETF discussion <ietf@ietf.org>
From: willi uebelherr <willi.uebelherr@riseup.net>
Message-ID: <67bbb411-0b02-2e8c-8b8e-465a44b511e0@riseup.net>
Date: Tue, 14 Mar 2017 14:51:35 -0300
MIME-Version: 1.0
In-Reply-To: <7AD4B72D-BABA-4789-9615-F6E659D09B4D@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WFIpkT5MEXqRW74Jork9bjcTUAY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 17:52:00 -0000

Dear Yoav,

i thank you very much for your answer. Maybe, in any time, i have to go 
deeper to understand all the details.

But, on the other sider side, i don't like to follow the breakdown of a 
process into parts and look only to this parts.

The same problem we have with the TOR nets or IP proxy servers for 
anonymisation. If you have access to all interconnection central points, 
you know, who communicate.

The IP header never can encrypt. The routers need the data. You can 
create high coded VPNs, but you have to connect to this.

The alternative for me is a strong net-topology in our 
telecommunication. This means, that every node is connected to his 
neighbors. Then we don't need central IXPs.

The base for that are our strong independent local networks in every 
community. And there, the people have all, what they need. And for 
dataexchange, we use the interconnection net, our InterNet.

The result is, that the most people can have her mailbox server (and all 
other server functionality) in her local network. Can connect directly 
in the net. Then it will be impossible for all this state institutions, 
to follow all this data flows. And because the people from the community 
organise her local network itself, they give this criminal institutions 
no access.

This existing telecommunication is strong organised to have on any point 
in any time the access to all dataflows. We need a system, where this 
possibility don't exist.

many thanks and greetings, willi


On 14/03/2017 03:42, Yoav Nir wrote:
> Hi, Willi
>
>> On 14 Mar 2017, at 6:58, willi uebelherr <willi.uebelherr@riseup.net> wrote:
>>
>>
>> Phillip, if you use B), you don't need A).
>
> Consider email. If you and I were to use PGP or S/Mime encryption nobody can read the content of our messages. However, without transport-layer (or IP-layer. I’m an IPsec guy) encryption between the gmail server and the riseup.net <http://riseup.net/> server, anyone monitoring the traffic can know that I am sending you an email. Protecting SMTP with TLS makes the connection only expose that someone of gmail is sending a message to someone on riseup.net <http://riseup.net/>.  And “someone on gmail” is close to being half the Internet. So you really still need A.
>
> Of course we are still vulnerable to Google or riseup.net <http://riseup.net/> informing on us.  Maybe we need some (E) about trustworthy intermediaries.
>
>> And how do you want to prevent traffic analysis? In a telekcommunication system, where all actors are privat companies and act for the state institutions and with a star topology, you will never be able to prvent any form of traffic analysis.
>>
>> Your writing is a little bit naive for me.
>
> Well, TLS 1.3 and IPsec have some anti-traffic analysis feature, but there is little evidence of anyone using this effectively.
>
> Yoav
>
>>
>> greetings, willi
>>
>>
>>
>> On 13/03/2017 20:13, Phillip Hallam-Baker wrote:
>>> I think this particular failure demonstrates the situation pretty well:
>>> http://www.zdnet.com/article/leaked-us-military-files-exposed/
>>>
>>> A) Without transport encryption, every network link is a potential point of
>>> compromise via traffic analysis.
>>>
>>> B) Without end-to-end data level encryption, every non endpoint device,
>>> every hard drive or removable storage is a potential point of compromise
>>>
>>> C) Without end point security, the end points are a potential point of
>>> compromise.
>>>
>>> D) Without trustworthy personnel, you are vulnerable to an insider threat.
>>>
>>> The security controls you need depends on your information security assets
>>> and your security concerns.
>>>
>>> If you are a high level security target then you need A + B + C + D. They
>>> are not alternatives, they are all requirements. It is really completely
>>> unhelpful for people to suggest tackling these separable concerns
>>> separately is 'useless'.
>>>
>>> Just as I would not consider personnel or physical security at the same
>>> time as end point security, I do not want to consider data level security
>>> at the same time as end point.
>>>
>>> To get back to the CIA leak, that 'hole you can drive a truck through' did
>>> not actually exist when the AV package was connected to the Internet. What
>>> we are seeing here is not a set of vulnerabilities, it is a set of research
>>> notes being compiled by people searching for vulnerabilities that has
>>> subsequently been exfiltrated, filtered to remove the good stuff and
>>> dumped.
>>>
>>> If you do end point security right, you can really be a 'PITA' to the
>>> people trying to break these systems. So the idea that end point security
>>> is futile is utterly misguided. If you use default deny approaches, end
>>> point security can be very effective. But end point security really isn't
>>> in scope for IETF unless we were to get into protocols for attestation of
>>> trustworthy hardware or the like.
>>>
>>>
>>> The reason I keep coming back to the data level security issue is that
>>>
>>> 1) It is in scope for IETF. Data level security protects data at rest and
>>> in motion.
>>>
>>> 2) There have been recent expiries and are imminent pending expiries of key
>>> IPR that makes a solution much easier.
>>>
>>> 3) It is one of the things we can fix that has the greatest security payoff.
>>>
>>
>
>


From nobody Tue Mar 14 11:50:00 2017
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 891891292F2 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 11:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level: 
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1056-bit key) reason="fail (bad RSA signature)" header.d=tndh.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IROpuoMBz02y for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 11:49:57 -0700 (PDT)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C5A2126DCA for <ietf@ietf.org>; Tue, 14 Mar 2017 11:49:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tndh.net; s=dkim;  h=Subject:Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:In-Reply-To:References:Cc:To:From; bh=Lw9n2KJngWTT7Bm3u+v1SzQCPwvrnpyOWRTU/OpGG+g=;  b=AdKpv9cDERahlzkUNZ3hJKhYLDTXQzIdXTu/TWeyYpnJ2JGKUUuR9mdLs9AFI6+oFWYlxoZHrARJ50iHmhCKuvDflf0PsN6BSs2I+WcQly/6SNptkI1DFL/ypBYTMNZlWX1y8zjGKjnKE9BrIbkmtg/XopErLhCYeLs69fgBaMfPY5LO;
Received: from express.tndh.net ([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 1cnrVZ-0004p9-N5; Tue, 14 Mar 2017 11:49:53 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Phillip Hallam-Baker'" <phill@hallambaker.com>, "'Ted Lemon'" <mellon@fugue.com>
Cc: "'Bob Hinden'" <bob.hinden@gmail.com>, "'IETF'" <ietf@ietf.org>
References: <20170307155346.fwhhpnsm4wl6zzoo@nic.fr> <CAMm+Lwh5E-NPXsVWQpK2tA8Rr+6SpvJJKxMbiks7_F1umxz2FQ@mail.gmail.com> <20170307160840.duv7wwg5sm23nrek@nic.fr> <44d06f90-0f38-f6de-8eb1-cf8262369cd5@bogus.com> <c6df6333-1a08-aa0c-c1de-55d335234f2a@si6networks.com> <alpine.LRH.2.01.1703071034050.3764@egate.xpasc.com> <CAMm+LwioHOJxDZudH8Ya9SYv5DT1fPMJ5ypDR8O5JGa4HwxPvg@mail.gmail.com> <F950C538-05E4-451B-8AC0-A42010DAA8D6@piuha.net> <56AC2362-AAF9-4103-AEC8-F4BD24288B94@piuha.net> <2B19E363-3C0C-409A-9FCE-078389B38106@fugue.com> <18048613-FD0F-419D-83AA-937D45F8900B@gmail.com> <47b7ee93-0fc7-1ae7-a3d7-cea0b4b4cd2a@cs.tcd.ie> <CC5E2EDA-5533-4FA0-8350-CE45311DD8B4@fugue.com> <CAMm+Lwh4Pn39D4r+k5HQnaxtZbTkpRCmAFMg77vLRVQzKY4S7g@mail.gmail.com>
In-Reply-To: <CAMm+Lwh4Pn39D4r+k5HQnaxtZbTkpRCmAFMg77vLRVQzKY4S7g@mail.gmail.com>
Date: Tue, 14 Mar 2017 11:49:23 -0700
Message-ID: <08b301d29cf3$b2a59df0$17f0d9d0$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH0FALxRjlZdIChSBqjnwGEOYm+4QHCMs8RAbq4Sd0BzGJ0ygHhsKGqAqgIdLABYevbEQI/GKBMARPt0AECL1WfEQLRnAoSAiud528C5pqdzQHO2VbSoH5ssFA=
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
Subject: RE: The CIA mentions us
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on express.tndh.net)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vy1tbDP42vTx-kyRa6g1n3t4xY0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 18:49:58 -0000

Phillip Hallam-Bakerwrote:
...
> The reason I keep coming back to the data level security issue is that =

>=20
> 1) It is in scope for IETF. Data level security protects data at rest =
and=20
> in motion.
>=20
> 2) There have been recent expiries and are imminent pending expiries=20
> of key IPR that makes a solution much easier.
>=20
Clearly that statement is self-contradictory. If the IPR has existed =
long enough to be at expire, the 'easier solution' has existed for a =
long time. The choice of not using it is simply a cost issue. If people =
don't believe protecting the data is worth the cost, the data will be =
exposed.

> 3) It is one of the things we can fix that has the greatest security =
payoff.
>
You can "improve" it, but you will never "fix" it. As long as humans =
have to interact with the data, there has to be a mechanism to expose =
the data, and that mechanism will always be vulnerable to compromise.

Tony



From nobody Tue Mar 14 12:09:35 2017
Return-Path: <maria.ines.robles@ericsson.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C988129665; Tue, 14 Mar 2017 12:09:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ines Robles <maria.ines.robles@ericsson.com>
To: <Iot-dir@ietf.org>
Cc: dnssd@ietf.org, ietf@ietf.org, draft-ietf-dnssd-mdns-dns-interop.all@ietf.org
Subject: Review of draft-ietf-dnssd-mdns-dns-interop-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148951856846.2289.9860804626640095928@ietfa.amsl.com>
Date: Tue, 14 Mar 2017 12:09:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1FIHY5ysa1ImsESoh1ehbzaGEtc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 19:09:29 -0000

Reviewer: Ines Robles
Review result: Ready

Hi,

I have read the draft. The document provides a description of the
requirements for a profile for label interoperation.

In IoT, networks and nodes, in general, have constrained resources.
Related to the topic of the draft in review, several aspects should be
considered from IoT point of view, such as:

- Type of devices that have insufficient resources to run DNS-SD/mDNS
[1] (Some running code [7]). The work in [2][3] depicts an
autoconfiguration scheme for the global (or local) DNS names of IoT
devices. It uses an specific DNS Name Format
(unique_id.object_identifier.OID.domain_name).

- Resource Directory (RD): A web entity that stores information about
web resources and implements the REST interfaces for registration and
lookup of resources. A mapping between CoRE Link Format attributes and
DNS-Based Service Discovery aspects (mapping ins to <Instance>,
Mapping rt to <ServiceType> and Domain mapping) is descripted in
version 9 of RD draft [4]. 

- Optimization of DNS-SD: A proposal for an optimization of DNS-SD
query using TXT records is descripted in [5].

- DNS Message Compression [6], implemented in uBonjour Contiki.

Thus, new work (or updates) is needed to set the requirements for
label interoperation in this type of environments. I understand that
this is out of scope of dns-interop draft. So, what about to add in
the dns-interop draft some text like:

"Related to constrained environments, work is ongoing such as
autoconfiguration[2], optimization of DNS-SD [5] and DNS message
compression [6] that would help to get an efficient selection of
labels for DNS and other resolution systems."

Hope that it helps.

Cheers,

Ines.


[1] https://www.ietf.org/mail-archive/web/dnssd/current/msg00589.html
[2] https://tools.ietf.org/html/draft-jeong-its-iot-dns-autoconf-01
[3] Lee, Sejun, Jaehoon Paul Jeong, and Jung-Soo Park. "DNSNA: DNS
name autoconfiguration for Internet of Things devices." Advanced
Communication Technology (ICACT), 2016 18th International Conference
on. IEEE, 2016.
[4] https://tools.ietf.org/html/draft-ietf-core-resource-directory-09
[5]
https://tools.ietf.org/html/draft-aggarwal-dnssd-optimize-query-00
[6] Klauck, Ronny, and Michael Kirsche. "Enhanced DNS message
compression-Optimizing mDNS/DNS-SD for the use in 6LoWPANs." Pervasive
Computing and Communications Workshops (PERCOM Workshops), 2013 IEEE
International Conference on. IEEE, 2013.
[7] https://github.com/Agile-IoT/awesome-open-iot#mdns--bonjour


From nobody Tue Mar 14 12:24:03 2017
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 0F2921299DC for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 12:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.022
X-Spam-Level: 
X-Spam-Status: No, score=-5.022 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cjbu21BuhtId for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 12:24:00 -0700 (PDT)
Received: from smtpde01.smtp.sap-ag.de (smtpde01.smtp.sap-ag.de [155.56.68.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDECD1299D6 for <ietf@ietf.org>; Tue, 14 Mar 2017 12:23:57 -0700 (PDT)
Received: from mail07.wdf.sap.corp (mail04.sap.corp [194.39.131.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde01.smtp.sap-ag.de (Postfix) with ESMTPS id 3vjPmX0zRkz1HPn; Tue, 14 Mar 2017 20:23:56 +0100 (CET)
X-purgate-ID: 152705::1489519436-0000521C-870FDF2C/0/0
X-purgate-size: 564
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail07.wdf.sap.corp (Postfix) with ESMTP id 3vjPmW5jY9zGpGy; Tue, 14 Mar 2017 20:23:55 +0100 (CET)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id B8D671A64A; Tue, 14 Mar 2017 20:23:55 +0100 (CET)
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
In-Reply-To: <A8793F66-E860-4CC1-80F8-D3C0B430C6AE@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
Date: Tue, 14 Mar 2017 20:23:55 +0100 (CET)
CC: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
Reply-To: mrex@sap.com
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: <20170314192355.B8D671A64A@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cyFuSQ3bJQsG98pU6okQFDgVzF4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 19:24:02 -0000

Carsten Bormann wrote:
> John R Levine <johnl@taugh.com> wrote:
>> 
>> You can complain about how stupid they are or you can upgrade
>> your mail system to use authentication methods that have been
>> IETF standards for a decade and get your mail delivered.  Your choice.
> 
> The most likely outcome is that local admins will "upgrade" our mail system
> by turning off IPv6.  (We have had IPv6 deployed for some 18 years now.)

turning off IPv6 is a surprisingly (depressingly?) successful mitigation
for a number of networking problems...

-Martin


From nobody Tue Mar 14 13:52:33 2017
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 97B671314C4 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 13:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level: 
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exJXIqh6ls3S for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 13:52:23 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 685F4129B55 for <ietf@ietf.org>; Tue, 14 Mar 2017 13:52:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D11D7BEB3; Tue, 14 Mar 2017 20:52:20 +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 2xkMFBc1IWqs; Tue, 14 Mar 2017 20:52:19 +0000 (GMT)
Received: from [10.87.48.75] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id B442ABE5D; Tue, 14 Mar 2017 20:52:18 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1489524739; bh=zz0DnIJjcyHzAxKXRIdRSq1R1SJ2iFIQ2RqJC2jjE20=; h=To:Cc:From:Subject:Date:From; b=bVROteim4zOwmDG4zI63we+H2XHi+T72IqLvLVf94XMERw+ou5kYZ1OH8xmLIwPA6 NLjGj31p2HL9NWLVsWkur+BOzNA4GgbGtKiAKQfXUGfclU8/Yesy/5ZA4t/tHtE9Z+ 7sgkL/ttCSSCgBfpEB99zp35VHn3qGojBJuRcmCw=
To: IETF-Discussion <ietf@ietf.org>
Cc: 'Dan Harkins' <dharkins@lounge.org>, Warren Kumari <warren@kumari.net>, Jouni Malinen <j@w1.fi>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Good but not-quite-trivial change in auth-48 for draft-harkins-owe
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <b3347345-3b28-7943-9f39-39e0f54ebf98@cs.tcd.ie>
Date: Tue, 14 Mar 2017 20:52:17 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5fRT0qCnlAi0lc6ibXv3BxlkRag9F33D4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cbbzBh8B6kg-HUppXMXQDFHwzd0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 20:52:27 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--5fRT0qCnlAi0lc6ibXv3BxlkRag9F33D4
Content-Type: multipart/mixed; boundary="8iEwfCarMWXAbEb7GMQeTiWGtncd1PUh2";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: IETF-Discussion <ietf@ietf.org>
Cc: 'Dan Harkins' <dharkins@lounge.org>, Warren Kumari <warren@kumari.net>,
 Jouni Malinen <j@w1.fi>
Message-ID: <b3347345-3b28-7943-9f39-39e0f54ebf98@cs.tcd.ie>
Subject: Good but not-quite-trivial change in auth-48 for draft-harkins-owe

--8iEwfCarMWXAbEb7GMQeTiWGtncd1PUh2
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

This draft [1] is currently paused in auth-48 as one
of the authors (Dan) just got some implementer feedback
(Many thanks Jouni!) that a clarification is needed.

The proposed change is to add a table explicitly calling
out how derived keys are to be used in the protocol. The
proposed NEW text is below (with an easier to view diff
at [2]) and Dan tells me that the content of the table
is about the only sensible choice and would almost be
obvious, but is much better being explicit.

I don't think myself that that change requires us to
go back to IETF last call but I've asked the RFC editor
folks to pause processing of the draft for a week or
so while we check that this change doesn't cause any
problems. If you do think that this change or handling
the change this way is problematic please let me or
the IESG know (or just reply to this;-) and we can see
how best to handle things.

If there are no problems I'll ask the RFC editor to ok
that change in a week (on Tuesday 21st).

Cheers,
S.

[1] https://datatracker.ietf.org/doc/draft-harkins-owe/
[2]
https://tools.ietf.org/rfcdiff?url1=3Dhttp://www.lounge.org/rfc-ed-8110-o=
rig.txt&url2=3Dhttp://www.lounge.org/rfc-ed-8110.txt

NEW TEXT to be added to section 4.4:

   +---------+--------------+----------+-------+------------+----------+
   |   Hash  |  Integrity   | KCK_bits |  Size |  Key-wrap  | KEK_bits |
   |         |  Algorithm   |          |   of  | Algorithm  |          |
   |         |              |          |  MIC  |            |          |
   +---------+--------------+----------+-------+------------+----------+
   | SHA-256 | HMAC-SHA-256 |   128    |   16  |  NIST AES  |   128    |
   |         |              |          |       |  Key-wrap  |          |
   | SHA-384 | HMAC-SHA-384 |   192    |   24  |  NIST AES  |   256    |
   |         |              |          |       |  Key-wrap  |          |
   | SHA-512 | HMAC-SHA-512 |   256    |   32  |  NIST AES  |   256    |
   |         |              |          |       |  Key-wrap  |          |
   +---------+--------------+----------+-------+------------+----------+

                Table 2: Integrity and Key Wrap Algorithms

   Upon completion of 802.11 association, the AP initiates the 4-way
   handshake to the client using the PMK generated above.  The 4-way
   handshake generates a key-encrypting key (KEK), a key-confirmation
   key (KCK), a message integrity code (MIC), to use for protection of
   the frames that define the 4-way handshake.  The algorithms and key
   lengths used in the 4-way handshake depend on the hash algorithm
   selected in Section 4.1 and are listed in Table 2.


--8iEwfCarMWXAbEb7GMQeTiWGtncd1PUh2--

--5fRT0qCnlAi0lc6ibXv3BxlkRag9F33D4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYyFgBAAoJEC88hzaAX42iUWEIALAz0oeuzQSa6c24uNF0I3P4
GTezACoTCPd64mZC0dWNGud2KHL77JWXMeIOsjM6FuQVcIKrQahjoLmFxfS9nh3E
1c6lbZAp6xEchyQFldetGOXgB3KMjroGRuF14c4G3iQglHopff18TWhFmwR9lqSs
pka1WJgINwmaHfn92M3xkMG+hxwu8bGej9It+W20ks1Zg8ZPjEZLvJwwprJ29Lhg
vvZnrdWiJVA41wzDqchQUQYwsiWnn51iukd0xUNg8zfi73XwU8dcEBk0N5sm3OG9
NsDlqAQDb6ThoENKzYmAeGfgfZxCENnd9lgQqGy40byf09iAudl6ho/ylzDSA24=
=W4o4
-----END PGP SIGNATURE-----

--5fRT0qCnlAi0lc6ibXv3BxlkRag9F33D4--


From nobody Tue Mar 14 15:01:59 2017
Return-Path: <acmorton@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 589AC129B70; Tue, 14 Mar 2017 15:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.997
X-Spam-Level: 
X-Spam-Status: No, score=-2.997 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUCsGoTtN7sD; Tue, 14 Mar 2017 15:01:51 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDEB5129B1D; Tue, 14 Mar 2017 15:01:50 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v2ELtGCZ012331; Tue, 14 Mar 2017 18:01:41 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049462.ppops.net-00191d01. with ESMTP id 296r1k1f3n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 14 Mar 2017 18:01:41 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v2EM1dPk012995; Tue, 14 Mar 2017 18:01:40 -0400
Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v2EM1Uhi012750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 14 Mar 2017 18:01:31 -0400
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Tue, 14 Mar 2017 22:01:19 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v2EM1JMD016954; Tue, 14 Mar 2017 17:01:19 -0500
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.178.11]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v2EM1FOB016441; Tue, 14 Mar 2017 17:01:16 -0500
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-blue.research.att.com (Postfix) with ESMTP id CD7C0F052C; Tue, 14 Mar 2017 18:01:14 -0400 (EDT)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Tue, 14 Mar 2017 18:01:14 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: "Badri.Subramanyan@ril.com" <Badri.Subramanyan@ril.com>, "kathleen.moriarty.ietf@gmail.com" <kathleen.moriarty.ietf@gmail.com>, "saag@ietf.org" <saag@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last call feedback: draft-mm-wg-effect-encrypt
Thread-Topic: Last call feedback: draft-mm-wg-effect-encrypt
Thread-Index: AQHSmEkg/clGABfaOEacwArHo1mOHqGMUL1AgAD0g4CAB6IkUA==
Date: Tue, 14 Mar 2017 22:01:14 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF25F3252D@njmtexg5.research.att.com>
References: <CAHbuEH4+bd=0PJa1rWDQN6tbeRK5vXKdbcUwsj2=zf9V8ejeDg@mail.gmail.com> <c056c07568974f37aa0366bbe8a93422@SIDC1EXMBX24.in.ril.com>
In-Reply-To: <c056c07568974f37aa0366bbe8a93422@SIDC1EXMBX24.in.ril.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.246.164]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-14_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703140168
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CTmDYRDvbt87LhH3MyuMMp_2BxM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 22:01:52 -0000

SGkgQmFkcmksDQpvbmUgZm9sbG93LXVwIHF1ZXN0aW9uIGJlbG93Og0KDQo+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEJhZHJpLlN1YnJhbWFueWFuQHJpbC5jb20gW21haWx0
bzpCYWRyaS5TdWJyYW1hbnlhbkByaWwuY29tXQ0KPiBTZW50OiBGcmlkYXksIE1hcmNoIDEwLCAy
MDE3IDI6MzUgQU0NCg0KPHNuaXA+DQoNCj4gPiBJZiB0aGUgc3RyZWFtcyBhcmUgZW5jcnlwdGVk
LCB0aGVuIHRoZSBBTEcgZmVhdHVyZSB3b3VsZCBiZSByZW5kZXJlZA0KPiANCj4gPiB1c2VsZXNz
LiBUaGlzIHdvdWxkIGxpbWl0IHRoZSBjYXBhYmlsaXR5IG9mIGFueSBuZXR3b3JrIGVsZW1lbnQg
dG8NCj4gDQo+ID4gbWFrZSBzbWFydCBwb2xpY2luZyBhbmQgcm91dGluZyBkZWNpc2lvbnMgYmFz
ZWQgb24gYXBwbGljYXRpb24gbGF5ZXINCj4gYXR0cmlidXRlcy4NCj4gDQo+IA0KPiBLYXRobGVl
biB3cm90ZToNCj4gRG8geW91IGtub3cgaWYgdGhlc2UgY2FuIHdvcmsgd2l0aCBhIDItdHVwbGUg
b3IgNS10dXBsZT8gIElzIHRoZXJlIGFuDQo+IGltcGFjdCBmcm9tIGVuY3J5cHRpb24gdmlhIFRM
UyBmb3IgaW5zdGFuY2U/ICBJZiBzbywgd2hhdCBpcyB0aGF0DQo+IGltcGFjdD8NCj4gDQo+IFtC
YWRyaV0gVGhlIHJ1bGVzIGluIG1vc3Qgb2YgdGhlIGNhc2VzIGlzIDUtdHVwbGUgdG8gYWNjdXJh
dGVseSBkZXBpY3QgYQ0KPiBmbG93LiBZZXMsIHRoZXJlIGlzIGFuIGltcGFjdCBmcm9tIGVuY3J5
cHRpb24gdmlhIFRMUyBhcyBtb3N0IG9mIHRoZQ0KPiBpbXBsZW1lbnRhdGlvbnMgb2YgQUxHIGdl
dCBpbmZvcm1hdGlvbiByZWdhcmRpbmcgc3VwcG9ydGluZyBwcm90b2NvbHMgYnkNCj4gcGFyc2lu
ZyBkYXRhLiBXaXRoIFRMUyBlbmNyeXB0aW9uLCB0aGUgQUxHIGxvc2VzIHRoZSBhYmlsaXR5IHRv
IHBhcnNlLA0KPiBoZW5jZSBnZXQgaW5mb3JtYXRpb24gb24gdGhlIHN1cHBvcnRpbmcgcHJvdG9j
b2xzLg0KPiANCj4gDQo+IEthdGhsZWVuIHdyb3RlOg0KPiBXaGF0IGlzIHVzZWQgYnkgQUxHIHRv
IGNvcnJlbGF0ZSBzdHJlYW1zPyAgVGhpcyB3b3VsZCBiZSBoZWxwZnVsIHRvDQo+IHVuZGVyc3Rh
bmQgaWYgdGhpcyBwYXJ0aWN1bGFyIG1ldGhvZCBmb3IgQUxHcyBkb2VzIGJlY29tZSAndXNlbGVz
cycNCj4gYW5kIGFsc28gdG8gZmlndXJlIG91dCBpZiBvdGhlciBvcHRpb25zIG1heSBleGlzdCB0
byBwZXJmb3JtIHRoZQ0KPiBmdW5jdGlvbnMgbmVlZGVkLg0KPiANCj4gW0JhZHJpXSBSRkMgMjY2
MywgU2VjdGlvbiAyLjkgZ2l2ZXMgaW5mb3JtYXRpb24gYWJvdXQgQUxHLiBUaGVyZSBpc27igJl0
DQo+IG9uZSBkZWZpbmVkIG1ldGhvZCB0byBpbXBsZW1lbnQgaXQgYW5kIHNvbWUgb2YgdGhlIG1l
dGhvZHMgdXNlZCBieQ0KPiB2ZW5kb3JzIGFyZSBpbmNsdWRlZCBiZWxvdy4NCj4gDQo+IDEuICBQ
YXJzZSB0aGUgY29udGVudCBvZiB0aGUgcHJpbWFyeSBzdHJlYW0gYW5kIGlkZW50aWZ5IHRoZSA1
LXR1cGxlIG9mDQo+IHRoZSBzdXBwb3J0aW5nIHN0cmVhbXMgYXMgaXQgaXMgYmVpbmcgbmVnb3Rp
YXRlZC4NCj4gDQo+IDIuIEludGVyY2VwdCBhbmQgbW9kaWZ5IHRoZSA1LXR1cGxlIGluZm9ybWF0
aW9uIG9mIHRoZSBzdXBwb3J0aW5nIHN0cmVhbQ0KPiBhcyB0aGUgaXQgaXMgYmVpbmcgbmVnb3Rp
YXRlZCBvbiB0aGUgcHJpbWFyeSBzdHJlYW0uIFRoaXMgaXMgYSBsaXR0bGUNCj4gbW9yZSBpbnRy
dXNpdmUgaW4gbmF0dXJlLg0KPiANCj4gDQpbQUNNXSANCkFmdGVyIFNyYyZEc3QgQWRkcmVzcyBh
bmQgUG9ydCwgd2hhdCBpcyB0aGUgNXRoIEVsZW1lbnQNCm9mIHRoZSA1LXR1cGxlIGluIHlvdXIg
ZXhwZXJpZW5jZT8NCg0KUHJvdG9jb2wgbnVtYmVyIGFuZCBQYWNrZXQgUHJpb3JpdHkgTWFya2lu
ZyAoRFNDUCkgYXJlIHR3byBjYW5kaWRhdGVzLi4uDQoNCmxldCB1cyBrbm93LCB0aGFua3MhDQpB
bA0KDQo=


From nobody Tue Mar 14 15:16:42 2017
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 43B0E1315A3; Tue, 14 Mar 2017 15:16:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
Cc: i2nsf@ietf.org, ietf@ietf.org, draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: Review of draft-ietf-i2nsf-problem-and-use-cases-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148952979419.24295.8210647087024239014@ietfa.amsl.com>
Date: Tue, 14 Mar 2017 15:16:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MrurpJW5aLKRORF1YNppfLDiwkM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 22:16:34 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

Document:  draft-ietf-i2nsf-problem-and-use-cases-11
Reviewer:  Dale R. Worley
Review Date:  2017-03-14
IETF LC End Date:  2017-03-22
IESG Telechat date:  [unknown]

Summary:

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

All of these nits are editorial.

1.  Introduction

   This document describes the problem statement for Interface to
   Network Security Functions (I2NSF) as well as some I2NSF use
cases.
   A summary of the state of the art in the industry and IETF which
is
   relevant to I2NSF work is documented in
   [I-D.hares-i2nsf-gap-analysis].

The content of these sentences is very good, but the construction
seems to be peculiar.  The document doesn't *describe* the problem
statement, the document *is* a statement.  Similarly,
hares-i2nsf-gap-analysis *is* a summary of the state of the art.  So
I
would use

   This document is the problem statement for Interface to Network
   Security Functions (I2NSF) as well as some I2NSF use cases.  A
   summary of the state of the art in the industry and IETF which is
   relevant to I2NSF work is [I-D.hares-i2nsf-gap-analysis].

But maybe you'll prefer to ask the RFC Editor.

   This document also briefly describes the
   following use cases summarized by
   [I-D.pastor-i2nsf-merged-use-cases]:

This sentence should start a new paragraph, as it's not connected to
the sentences before it.

3.  Problem Space

   The following sub-section describes ...

s/sub-section describes/sub-sections describe/

3.1.1.  Diverse Types of Security Functions

   NSFs by different vendors can have
   different features and have different interfaces.

It might be worth mentioning somewhere what seems to be a convention:
the document (or at least, section 3.1) is largely oriented toward
"service providers" who sell comprehensive network services
(including
security functions) to "customers", but who in turn buy security
functions from "vendors".  Perhaps this could be entered as
terminology in section 2.

The reason I mention this is that my background is as an end-user
(which is common in the IETF), so the term "service provider"
triggers
in my mind the idea "someone I buy something from".  And the term
"vendor" triggers the *same* idea.  But in this draft, the default
reader is a "service provider" and "vendor" is *not* the same thing.

This point started to confuse me at the beginning of section 3.1.6.

   Security Functions in a Demilitarized Zone (DMZ):   Examples of
this
      function are firewall/ACLs, IDS/IPS, one or all of AAA services
      NAT, forwarding proxies, and application filtering.

The phrase "one or all of AAA services NAT" seems to be incorrect.  I
suspect there's supposed to be a comma before NAT.

   Security gateways and VPN concentrators:    Examples of these
      functions are; IPsec gateways, Secure VPN concentrators that
      handle bridging secure VPNs, and Secure VPN controllers for
data
      flows.

Unless "Secure VPN" is a name in itself, "secure" shouldn't be
capitalized.

3.1.2.  Diverse Interfaces to Control and Monitor NSFs

   A challenge for monitoring is that an NSF cannot monitor what it
   cannot view.  Therefore, enabling a security function (e.g.,
firewall
   [I-D.ietf-opsawg-firewalls]) does not mean that a network is
   protected.  As such, it is necessary to have a mechanism to
monitor
   and provide execution status of NSFs to security and compliance
   management tools.  There exist various network security monitoring
   vendor-specific interfaces for forensics and troubleshooting.

This paragraph seems awkward.  Each sentence is reasonable, but the
connection between them is not clear to me.  Perhaps the third
sentence has the meaning "... it is necesary to have a mechanism
...to
verify that the NSF is seeing the traffic that is intended".

The last sentence contains "network security monitoring
vendor-specific interfaces" which is awkward.  Perhaps

   There exist various vendor-specific interfaces for network
security
   monitoring, forensics, and troubleshooting.

3.1.4.  More Demand to Control NSFs Dynamically

   The Security Service Providers ...

The capitalization of "security service providers" is inconsistent.
Some times all three words are capitalized, and some times they're
not.

3.1.5.  Demand for Multi-Tenancy to Control and Monitor NSFs

   Service providers may need several operational units to control
and
   monitor the NSFs, especially when NSFs become distributed and
   virtualized.

You may want to explain what an "operational unit" is.  As far as I
can tell, neither "unit" nor "operational" (in this sense) is used
elsewhere in this draft.

3.1.7.  Lack of Mechanism for NSFs to Utilize External Profiles

   Many security functions depend on signature files or profiles to
   perform (e.g., IPS/IDS signatures, DDos Open Threat Signaling
(DOTS)
   filters).  

I think the words "to perform" should be removed.  The sentence makes
more sense to me without those.  Or, if there is a meaning that needs
to be specified, "to perform" probably isn't the right choice.  "to
work" makes sense in this place, but is an informal usage.  Perhaps
"to function".

   Today, the construction and use of black list databases
   can be a win-win strategy for all parties involved.

"win-win strategy" is a hackneyed phrase.  This is better

   Today, the construction and use of black list databases
   can be beneficial for all parties involved.

However, it's not clear to me what additional information is carried
by "for all parties involved".  And for that matter, is "today"
important here?

I suspect that you mean something like this:

   Today, black list databases can be beneficial, and in the future
   there might be open source signatures/profiles ...

--

   (e.g., by Snort, Suricata, Bro and Kisnet)

s/Kisnet/Kismet/

"Snort, Suricata, Bro and Kisnet" reads like a reference -- I had to
look them up to discover that they are IDS software!

But there needs to be some connection between a list of IDS software
systems and "open source signatures/profiles".  Perhaps:

   Today, black list databases can be beneficial, and in the future
   there might be open source signatures/profiles distributed as part
   of IDS systems (e.g. Snort, Suricata, Bro and Kisnet).

--

   There is a need to have a standard envelope (i.e., the format) to
   allow NSFs to use external profiles.

This is awkward.  Perhaps

   There is a need to have a standard format to allow NSFs to use
   external profiles.

3.1.8.  Lack of Mechanisms to Accept External Alerts to Trigger ...

   I2NSF controller(s) would manage the changing to the affected
   policies ...

This could be simplified to "I2NSF controller(s) would change the
affected policies ...".

   By monitoring the network alerts from DDoS ...

Probably s/DDoS/DOTS/.

   ... I2NSF
   can feed an alerts analytics engine that could recognize attacks
so
   the I2NSF can enforce the appropriate policies.

Here, "I2NSF" is being used as a noun, whereas the previous usage is
that it is an adjective, and "I2NSF controller(s)" would be used.

   ... provide information to the client ...

I think this is clearer if s/the client/its clients/.  "client" is
used with two meanings, one is "customer" (e.g., in the definition of
"Bespoke"), and more commonly as "software client".  If you say "[the
controller's] clients", it is clear that you're using the second
meaning.

3.1.9.  Lack of Mechanism for Dynamic Key Distribution to NSFs

   There is a need for a controller to distribute various keys to
   distributed NSFs.  To distribute various keys, the keys must be
   created and managed.

Perhaps combine these as

   There is a need for a controller to create, manage, and distribute
   various keys to distributed NSFs.

--

   In addition, keys may be used to secure
   the protocol and messages in the core routing infrastructure (see
   [RFC4948])

Probably s/protocol/protocols/.

   If a device had an abstract key table
   maintained by security services, a device could use these keys for
   routing and seurity devices.

s/seurity/security/

Typical English usage in this situation is "it could use ...";
because
"it" is the subject of the second clause, it is presupposed to be the
same as the subject of the first clause.

   Conceptually, there must be an interface defined for routing/
   signaling protocols to make requests for automated key management
   when it is being used, and to notify the protocols when keys
become
   available in the key table.  One potential use of such an
interface
   is to manage IPsec security associations on SDN networks.

I think you need to add a subject in "... and for XXX to notify the
protocols ..." for clarity, the omitted noun could be "interface" or
"protocols".

The last sentence seems redundant, as security associations have been
discussed at the beginning of 3.1.9.  Is there a particular reason to
point out IPsec at this point (since many secured protocols need
keys)?

       If protocols share
       common mechanisms for authentication (e.g., TCP Authentication
       Option [RFC5925]), then the same mapping may be reused.

This sentence starts with "protocols [that] share common mechanisms"
but then mentions only one protocol.  Do you mean

       If several protocols share a
       common mechanism for authentication (e.g., TCP Authentication
       Option [RFC5925]), then the same mapping may be used for all
       usages of that mechanism.

--

   3.  Automated Key management needs to support both symmetric keys
and
       group keys via the abstract key service provided by items 1
and
       2.

s/Key/key/

I think "via the abstract key service provided by items 1 and 2" is
redundant here.

3.2.  Challenges Facing Customers

   o  Which critical communications are to be preserved during
critical
      events and which hosts are continue service,

"are continue service" seems to be incorrect in some way.

   o  What signaling information is passed to a controller that during
a
      Distributed Denial of Service in order to ask for mitigation
      services (within the scope DOTS working group),

"that" should be removed, I think.

3.2.2.  Today's Control Requests are Vendor Specific

   Without a standard technical
   standard interface that provides a clear technical
characterization,
   the service provider faces many challenges:

Should "standard technical standard interface" be "standard
interface"
or "standardized interface"?

   No standard technical characterization, APIs, or Interface

I think you want a colon after this phrase to parallel the other
items
in the list.

   Managing by scripts de-jour:    The current practices rely upon
the
      use of scripts that generate other scripts which automatically
run
      to upload or download configuration changes, log information
and
      other things.  These scripts have to be adjusted each time an
      implementation from a different vendor technology is enabled on
a
      provider side.

The phrase "on a provider side" doesn't read well.  Perhaps "by a
service provider"?

3.3.  Lack of Standard Interface to Inject Feedback to NSF

   The following sub-section describes the problems and challenges
   facing customers and security service providers when some or all
of
   the security functions are no longer physically hosted by the
   customer's adminstrative domain.

s/adminstrative/administrative/

   As more sophisticated threats arise, enterprises, vendors, and
   service providers have to rely on each other to achieve optimal
   protection.  Cyber Threat Alliance (CTA,
   http://cyberthreatalliance.org/) is one of those initiatives that
aim
   at combining efforts conducted by multiple organizations.

This paragraph doesn't fit well in the flow of the text.  The second
sentence seems like it's basically a reference, and the link should
be
put down in the references.  But I think the point resembles the
discussion in 3.1.7, that you want to enable organizations to pass
among themselves new profiles, which the customers or service
providers can insert into NSFs in a simple way.  Perhaps

   As more sophisticated threats arise, protection will depend
   on enterprises, vendors, and service providers being able to
   cooperate to develop optimal profiles, e.g., through initiatives
   like [CTA].  

and then combine with the paragraph which follows:

   The standard interface to provide security profiles to the NSF
should
   interwork with the formats which exchange security profiles
between
   organizations.

3.5.  Difficulty to Validate Policies across Multiple Domains

   As discussed in the previous four sections, both service providers
...

Probably s/sections/sub-sections/.

   ... and customers have needs to express policies and profiles ...

s/needs/need/

   This section and the next section (section 3.6) xamine what ...

s/xamine/examine/

(Have you spell-checked this draft?)

   ... happens in two specific network scnearios: ...

s/scnearios/scenarios/

   a) multi-domain control of
   security devices hosted on virtual and non-virtual ...

There is a noun missing after "virtual and non-virtual".

   Hosted security service may instantiate NSFs in Virtual Machines
   ...

You probably don't want to capitalize "virtual machines" here.

   To
   set-up this cross-domain service, the security controller must be
   able to communicate with NSFs and/or controllers within its domain
   and across domains to negatiate for the services needed.

s/set-up/set up/  ("set up" is a verb (more or less), "set-up" is the
action of setting up or the thing which is set up.)

s/negatiate/negotiate/

3.6.  Software-Defined Networks

   Software-Defined Networks have changed the landscape of data
center
   designs by introducing overlay networks deployed over ToR switches
   that connect to a hypervisor.

You probably should spell out "ToR switch"; "top of rack switch" is
not yet listed in Wikipedia as a meaning of "ToR".

4.1.  Basic Framework

   Integrity of the NSF:   by ensuring that the NSF is not
compromised;

   Isolation:   by ensuring the execution of the NSF is
self-contained
      for privacy requirements in multi-tenancy scenarios.

   Provenance of NSF:    Customers may need to be provided with
strict
      guarantees about the origin of the NSF, its status (e.g.,
      available, idle, down, and others), and feedback mechanisms so
      that a customer may be able to check that a given NSF or set of
      NSFs properly conform to the the customer's requirements and
      subsequent configuration tasks.

The punctuation and capitalization is inconsistent between the list
items here.  I suggest changing the first two to (more or less)
sentences:

   Integrity of the NSF:   Ensuring that the NSF is not compromised.

   Isolation:   Ensuring the execution of the NSF is self-contained
      for privacy requirements in multi-tenancy scenarios.

Probably s/Provenance of NSF/Provenance of the NSF/.

   In order to achieve this, the security controller may collect
   security measurements and share them with an independent and
trusted
   third party (via Interface 1) in order to allow for attestation of
   NSF functions using the third party added information.

Would this really be via Interface 1?  It looks like Interface 1 only
goes to the customer's client, not a 3rd party service, and it is
used
for passing security requests.  This is made clearer in the next
paragraph, but it would probably be better to only say that there
needs to be an interface to 3rd parties for services like this, and
it
may be a variant of Interface 1 or it may be a distinct interface.

4.2.  Access Networks

   Figure 3 shows how these virtual
   access nodes for different types of customers connect connect
through
   virtual access nodes an NSF.

s/connect connect/connect/

The grammar of the sentence needs fixing also somewhere near "nodes
an
NSF".

   These use cases define the interaction between the operator and
the
   vNSFs through automated interfaces, typically by means of
Business-
   to-Business (B2B) communications.

Is "Business-to-Business (B2B) communications" a technical term?  It
doesn't seem to me to convey any additional information, since most
of
the usages envision that NSFs may be provided by outside vendors, so
pretty much any communication with an NSF may be business-to-business
communication.

   Service Provider:   Service requests for policies that protect ...

There isn't a "Service Provider" illustrated in the figure.  I assume
that the Service Provider looks much like the other three cases,
since
those look very much like each other, but some sort of illustration
should be provided.  Especially if the Service Provider has further
customers (presumably further to the left in the figure), that would
be a more complex architecture.

   ... may want to get
   their dedicated NSFs (most likely vNSFs) for direct control
purposes.

This is rather informal usage.  Perhaps better:

   ... may want to contract separately for dedicated NSFs ...

--

   In this case, here are the steps to associate vNSFs to specific
   customers:

There are two cases discussed in the paragraph before this sentence,
and it's not obvious which one this sentence is connected to via "In
this case".  Or does it apply to both?  If it applies to the second
case only, I suggest splitting the last two sentences off as a
separate paragraph.  If this sentence applies to all cases in this
subsection, I suggest removing "In this case".

4.3.  Cloud Data Center Scenario

   The on-demand, dynamic nature of security service delivery
   essentially encourages that the network security "devices" be in
   software or virtual form factors, rather than in a physical
appliance
   form.

I think you want to s/form factors/forms/.  (The phrase "form factor"
seems to be abused to mean many things.)

   Another example is that IPS/
   IDS services for investment banking and non-banking traffic may be
   separated for regulatory reasons.

Is "investment banking" specific here, or does this statement also
apply to "banking" generally?  Or is "non-banking traffic" really
"non-investment-banking traffic" (in which case calling it "other
traffic" is probably better)?

4.3.2.  Firewall Policy Deployment Automation

   Even though most vendors support similar firewall features, the
   actual rule configuration keywords are different from vendors to
   vendors, making it difficult for automation.

Probably s/actual rule/specific rule/ or even just "specific".

4.3.3.  Client-Specific Security Policy in Cloud VPNs

   Clients of service provider-operated cloud data centers not only
need
   to secure Virtual Private Networks (VPNs), but also [X] virtual
security
   functions that apply the clients' security policies.  

There's an understood verb at the location marked [X].  I think it's
supposed to be "to secure", and if so, the usage is correct.  But
it's
hard to read, so I think it would be better to not omit the verb.

4.4.  Preventing Distributed DoS, Malware and Botnet attacks

   Many networks such as Internet of
   Things (IoT) networks, Information-Centric Networks (ICN), Content
   Delivery Networks (CDN), Voice over IP packet networks (VoIP), and
   Voice over LTE (VoLTE) are also exposed to such attacks.

This seems to be just a specialization of the preceding sentences.
Does it add more information?  (E.g., perhaps there are special
considerations for each of these types of networks, in which case it
might be useful to state that.)

4.5.  Regulatory and Compliance Security Policies

   Organizations are not only supposed to protect their networks
against
   attacks, but they should also adhere to various industry
regulations:

It's probably better to s/should also/must also/!

7.  Security Considerations

   Having a secure access to control and monitor NSFs is crucial for
   hosted security services.

Probably s/a secure/secure/.

   Therefore, proper secure communication
   channels have to be carefully specified for carrying controlling
and
   monitoring traffic between the NSFs and their management entity
(or
   entities).

I think you can condense this to "management entity(ies)", but you
probably should talk to the RFC Editor about it.

   In addition, the Flow security policies specified by customers can
   conflict with providers' internal security policies which may
allow
   unauthorized traffic or unauthorized changes to flow polices (e.g.
   customers changing flow policies that do not belong to them).

I don't think you want to capitalize "flow" here.

It's not clear to me what "which may allow unauthorized ..." applies
to.  It seems like there's an important issue in just

   In addition, the Flow security policies specified by customers can
   conflict with providers' internal security policies

It seems that solving I2NSF requires a clear understanding of how the
customer's policies and the provider's policies interact.  (I would
think something is allowed only if both policies allow it, but the
reality may be more complex.)

The rest of the sentence seems redundant given the discussion in the
rest of document.

   Therefore, it is crucial to have proper AAA [RFC2904] to authorize
   access to the network and access to the I2NSF management stream.

It seems to me that this is a rather generalized need for I2NSF, and
not connected to the previous sentences.  So I would omit "Therefore"
and put it as a separate paragraph.

[END]



From nobody Tue Mar 14 16:54:38 2017
Return-Path: <blong@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 F25EA129BD4 for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 16:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EnTSdYj7qS2o for <ietf@ietfa.amsl.com>; Tue, 14 Mar 2017 16:54:35 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90972129BCD for <ietf@ietf.org>; Tue, 14 Mar 2017 16:54:35 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id v198so972510ywc.2 for <ietf@ietf.org>; Tue, 14 Mar 2017 16:54:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=h6maKXPdc6I1QFz98jUsK5E3OEANo7ifdEVY2QT0iTk=; b=FyBTxAmf+vTDk+B5P3wTNGT306CxwbOtBUb0apRpDSXATk0O7SeGpP+Vya5/N0agUe NU9u8loDt32guA+BgG9R5AuG1pjR5gb/bpyPkvh0ulTV4xaDorGdgEFSdr29zqFHYQQj RISa32ELvfFKphQZfub1ypROqJqC5+bJrCaC9MVSs9ONaOLOWX304p4dno5EGZ9g5UKH iajYB82ku4UOhnEw+uR4bXYGnRaox2ISLkUeUVhc6Y2QscCqYQaOWrPKYIz6c9rwR5ei KapEWvFmgzdx+5BJv86NIJeHRxA3OtnLJyR0bKosRMFHtQx+C1LTGrt6i6jHi3AtL5Yp odzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=h6maKXPdc6I1QFz98jUsK5E3OEANo7ifdEVY2QT0iTk=; b=eleZNLpeFGKecyVaYJuu6SnoeDJKnSp+e5Osy3OEMprSNB7x1ZVJFHtIz70hShfhdn YghI6sujT0Ujls8LnDb2yE3uE8nuTk6MS0X6QPitaxQjekQkGTq6XSIw7gfCKP4NsUuC QnFDfY4WB1KMPdXPJr3BpgW6fSMT5SXWMsjfTe4ztnLpTbQ+d4XgKNBmfJjhzecKv8lK BgV98xewxO8S0k4HOv1wu4mkm4PDliFhhx5D3GAFf+hTndh1kV0l2ZSNh07kpM6cDbOo GJASkErZqH7UZ8yH4t6WllBQFZOfHTa2YLg7Pir4r/MhWfdBaUX4Y+hyD0Fv/lp8pGeo GCew==
X-Gm-Message-State: AFeK/H0IFUoQSeM+hWA2qNDt/WbyWC1HZq7c3CmPfT1WF8kDEyEHI7NV7dgBnBYJFzV4LDwHg5Ev2J5h3ICPH6DZ
X-Received: by 10.37.192.16 with SMTP id c16mr233526ybf.195.1489535674406; Tue, 14 Mar 2017 16:54:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.220.11 with HTTP; Tue, 14 Mar 2017 16:54:33 -0700 (PDT)
In-Reply-To: <m1cnjqr-0000GkC@stereo.hq.phicoh.net>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <m1cnjqr-0000GkC@stereo.hq.phicoh.net>
From: Brandon Long <blong@google.com>
Date: Tue, 14 Mar 2017 16:54:33 -0700
Message-ID: <CABa8R6v+ymVRef5_7vCso2xDNAy2XtsAtRP78dbVFcaprFG3iw@mail.gmail.com>
Subject: Re: Do you really not care whether people accept your mail?
To: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Cc: IETF <ietf@ietf.org>, John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=001a113a119ac14d4f054ab98c99
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZJ5uow2y99zzPMdeIGy6j7SFPek>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Mar 2017 23:54:37 -0000

--001a113a119ac14d4f054ab98c99
Content-Type: text/plain; charset=UTF-8

On Tue, Mar 14, 2017 at 3:38 AM, Philip Homburg <pch-ietf-6@u-1.phicoh.com>
wrote:

>
> In my experience, essentially no mail gets lost if you leave out SPF, DKIM,
> DMARC. The only exception is gmail that occasionally rejects e-mail.
>

"no mail gets lost" != "gmail occasionally rejects my mail"


> In the context of IPv6 we now have an additional problem. Sites that have
> filters that are more strict for IPv6 than for IPv4. The obvious very
> quick workaround for many mail admins is to avoid delivering mail over
> IPv6.
> Of course, that just increases the SPAM/HAM ratio, justifying more
> draconian
> measures. Which in the end will just kill IPv6 as a transport for e-mail.
>

Do you imagine that you may be making different choices than others?

There are plenty of senders, in fact the vast majority by volume, who are
perfectly fine with authenticating their mail.  And many of them send over
IPv6.  This may be a speed bump, but it is not the death of IPv6 for email
transport.

There is no FUSSP, but there are many things which help make the problem
tractable.

Brandon

--001a113a119ac14d4f054ab98c99
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Mar 14, 2017 at 3:38 AM, Philip Homburg <span dir=3D"ltr">&lt;<=
a href=3D"mailto:pch-ietf-6@u-1.phicoh.com" target=3D"_blank">pch-ietf-6@u-=
1.phicoh.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
In my experience, essentially no mail gets lost if you leave out SPF, DKIM,=
<br>
DMARC. The only exception is gmail that occasionally rejects e-mail.<br></b=
lockquote><div><br></div><div>&quot;no mail gets lost&quot; !=3D &quot;gmai=
l occasionally rejects my mail&quot;</div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
In the context of IPv6 we now have an additional problem. Sites that have<b=
r>
filters that are more strict for IPv6 than for IPv4. The obvious very<br>
quick workaround for many mail admins is to avoid delivering mail over IPv6=
.<br>
Of course, that just increases the SPAM/HAM ratio, justifying more draconia=
n<br>
measures. Which in the end will just kill IPv6 as a transport for e-mail.<b=
r></blockquote><div><br></div><div>Do you imagine that you may be making di=
fferent choices than others?</div><div><br></div><div>There are plenty of s=
enders, in fact the vast majority by volume, who are perfectly fine with au=
thenticating their mail.=C2=A0 And many of them send over IPv6.=C2=A0 This =
may be a speed bump, but it is not the death of IPv6 for email transport.</=
div><div><br></div><div>There is no FUSSP, but there are many things which =
help make the problem tractable.</div><div><br></div><div>Brandon</div></di=
v></div></div>

--001a113a119ac14d4f054ab98c99--


From nobody Tue Mar 14 19:47:22 2017
Return-Path: <suresh.krishnan@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 2CFE212940C; Tue, 14 Mar 2017 19:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCELpv5bVM0E; Tue, 14 Mar 2017 19:47:18 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF25129452; Tue, 14 Mar 2017 19:47:18 -0700 (PDT)
X-AuditID: c618062d-d73ff700000009d8-3d-58c8bc457bc5
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by  (Symantec Mail Security) with SMTP id C6.AE.02520.54CB8C85; Wed, 15 Mar 2017 05:00:05 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0319.002; Tue, 14 Mar 2017 22:47:10 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>, 6man WG <ipv6@ietf.org>
CC: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv71giYAPcbUKK9ywM4gSjvg==
Date: Wed, 15 Mar 2017 02:47:06 +0000
Message-ID: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_935C0C0C-E7E4-489E-B3E7-4CA2A452A3C8"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnkeLIzCtJLcpLzFFi42KZXLonXNd1z4kIg8f/9C1evb3GZvFs43wW i5dn3zM5MHssWfKTKYAxissmJTUnsyy1SN8ugStj172fbAVLXSpWnVzA2sB40K6LkZNDQsBE 4siht8wgtpDAekaJvi9FXYxcQPZyIHvHLFaQBBtQ0Yadn5lAbBEBG4mZu3rB4swCkRInHi5g A7GFBVwknu7dwQZR4ymxbuNhFghbT6Lj8RawOIuAqsSS9y1AvRwcvAL2Ek9PhIGEGQXEJL6f WsMEMVJc4taT+UwQt4lIPLx4mg3CFpV4+fgfK4StJPHx93x2kDuZBaYwSkzvXwn2AK+AoMTJ mU9YJjAKzUIyaxayullI6iCKtCWWLXwNFOcAsnUkJi9khAibSrw++hHKtpaY8esgG4StKDGl +yH7AkaOVYwcpcUFObnpRgabGIFRckyCTXcH4/3pnocYBTgYlXh4C1hPRAixJpYVV+YeYlQB an20YfUFRimWvPy8VCUR3jsLgdK8KYmVValF+fFFpTmpxYcYpTlYlMR541bfDxcSSE8sSc1O TS1ILYLJMnFwSjUwSvk3inxzNin2P5T0Of7qwgVCQkejCm+pH3I5VRiQvefVB0mrPR8aKpa3 MS+asaT7dOGTlfvWsyZl33tTcnTRqocalktm63F79KyZdFX9V9u5Mt8WBp2mHNUfa18zbf74 5c+6BJvdwbXTvbM+zRcr6ypqK/I4+O5kjZif1U1/ZpYlsU6n+xIWKLEUZyQaajEXFScCACc/ ShSaAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0it68EdnBDs73uxpmzIQqlMw-fE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 02:47:20 -0000

--Apple-Mail=_935C0C0C-E7E4-489E-B3E7-4CA2A452A3C8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks to everyone who commented during the IETF Last Call of =
draft-ietf-6man-rfc2460bis-08. The IETF last call discussion for this =
draft was mainly focused around the text in Section 4 that discusses the =
handling of extension headers. The biggest concern raised was that the =
current text is ambiguous on whether header insertion is allowed on =
intermediate nodes or not. There were some people arguing that an =
explicit prohibition is not necessary as the text is already clear, =
while others believed that explicitly listing the prohibitions will =
minimize any misunderstandings in the future. There was also a small =
number of people who wanted to explicitly allow header insertion and =
describe how to do it, but this was clearly out of scope for this draft =
(but may be in scope for future work in 6man). Overall, no one argued =
against the fact that the intent of the text in RFC2460 was to forbid =
insertion of extension headers on any other node but the source of the =
packet.  The only argument made against adding clarifying text was that =
the text was already clear. Given this, I believe there is consensus to =
add explicit text about header insertion into the draft before it =
progresses further. I have discussed this with the editor and the =
document shepherd and would like to propose the following text change.

OLD (from -08):

 The insertion of Extension Headers by any node other than the source
 of the packet causes serious problems.  Two examples include breaking
 the integrity checks provided by the Authentication Header Integrity
 [RFC4302], and breaking Path MTU Discovery which can result in ICMP
 error messages being sent to the source of the packet that did not
 insert the header, rather than the node that inserted the header.

 One approach to avoid these problems is to encapsulate the packet
 using another IPv6 header and including the additional extension
 header after the first IPv6 header, for example, as defined in
 [RFC2473]

 With one exception, extension headers are not processed by any node
 along a packet's delivery path, until the packet reaches the node (or
 each of the set of nodes, in the case of multicast) identified in the
 Destination Address field of the IPv6 header...

NEW:

 With one exception, extension headers are not examined, processed,
 inserted, or deleted by any node along a packet's delivery path,
 until the packet reaches the node (or each of the set of nodes, in
 the case of multicast) identified in the Destination Address field of
 the IPv6 header...

Please feel free to comment either privately or on list if you have any =
concerns with this resolution going forward.

Regards
Suresh

P.S.: There were also other editorial issues that were raised during =
last call and they should be addressed in the next version of the draft=

--Apple-Mail=_935C0C0C-E7E4-489E-B3E7-4CA2A452A3C8
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzE1MDI0NzA4WjAjBgkqhkiG9w0B
CQQxFgQUAv2xWnWCZyHpTgpC7rM83TaGStwwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQCG9kLryOY3qXOX8wMx4FfU0lf2qFws1K8CZWsjojirzod1gUWCvtjPBOeSxqO+
WZFZzaa2oY5nVohLInFcZwVJnIrTPU0WmpeQYd3uivKHsHCg+t2osW90z7oLSytPIeS15nuooZ5W
Yr8KTLU4p1qRacwJJ2nFp1HXPoLZDE5zd+ghymG5Au5Egb1z4QZA5ujy6uiMAsMmFODrVSPbiGh2
HaOK/euui4aoevexquNXA1ben5SNq0gyy1eySnTJbWn0G262Q4NGbaOOSOirpYBEYep62s+Selh+
iWeCgii4xfmKmHAobJS6zcU1PnyTe2uE7nY/RqriKwWRDcxkOhipAAAAAAAA

--Apple-Mail=_935C0C0C-E7E4-489E-B3E7-4CA2A452A3C8--


From nobody Wed Mar 15 03:32:31 2017
Return-Path: <tjc@ecs.soton.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 BB0AE129A9F; Wed, 15 Mar 2017 03:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id roeHxj5Ex1Cs; Wed, 15 Mar 2017 03:32:22 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1F44129AAA; Wed, 15 Mar 2017 03:32:21 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2FAWGBN024369; Wed, 15 Mar 2017 10:32:16 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v2FAWGBN024369
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1489573937; bh=22tYXeBBj4WhjWt778H1NPIDgEY=; h=From:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References; b=ARbIlG6+NnbTaXErwuFV/STMNrnSaJyMwsBVmf5cIw4Od+SdF12AXgEPLD7UlPpwP QyXasVr3GOAFgHVThpsCCygK/1mfarqo2EG5HU8djnedScwX9KfEUYFUdYX0EHJWSm L5bv5RxCcw7dxBQF52w7K4F/zPOcoIKc1pc2uAK0=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y2EAWG1640403462z3 ret-id none; Wed, 15 Mar 2017 10:32:16 +0000
Received: from [10.1.11.164] (firewall-lho-ext.management.janet.ac.uk [194.82.140.195]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2FAWB4D002316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Mar 2017 10:32:11 GMT
From: Tim Chown <tjc@ecs.soton.ac.uk>
Message-ID: <EMEW3|3d7f89a896697bb5f0f1b013499e85eey2EAWG03tjc|ecs.soton.ac.uk|C77E403A-4902-4ED0-ADF2-879FC08C6C16@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A8FB0ECA-1BD9-4521-9700-E6CFD83556CA"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Review of draft-ietf-dnssd-mdns-dns-interop-04
Date: Wed, 15 Mar 2017 10:32:11 +0000
In-Reply-To: <148951856846.2289.9860804626640095928@ietfa.amsl.com>
Cc: Iot-dir@ietf.org, dnssd@ietf.org, ietf@ietf.org, draft-ietf-dnssd-mdns-dns-interop.all@ietf.org
To: Ines Robles <maria.ines.robles@ericsson.com>, Ralph Droms <rdroms.ietf@gmail.com>
References: <148951856846.2289.9860804626640095928@ietfa.amsl.com> <C77E403A-4902-4ED0-ADF2-879FC08C6C16@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y2EAWG164040346200; tid=y2EAWG1640403462z3; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=6:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v2FAWGBN024369
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NyEYu7HI1HHz5hyQneu6KcQ39QQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 10:32:25 -0000

--Apple-Mail=_A8FB0ECA-1BD9-4521-9700-E6CFD83556CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Ines,

Many thanks for this review.

As you=E2=80=99ve implictly noted, the focus of =
draft-ietf-dnssd-mdns-dns-interop-04 is interoperability of the labels =
used, primarily between unicast and multicast DNS.

You raise some very good points about the efficiency of mDNS/DNS-SD, =
particularly in constrained environments. This isn=E2=80=99t something =
we=E2=80=99ve covered in any detail as yet in the dnssd WG, aside from =
draft-aggarwal-dnssd-optimize-query-00 being presented a few IETFs ago, =
but DNS-SD in mesh networks is in our charter =
(https://datatracker.ietf.org/wg/dnssd/charter/ =
<https://datatracker.ietf.org/wg/dnssd/charter/>). To date we=E2=80=99ve =
focused on enterprise and home networks as managed and unmanaged =
multi-link IP environments.=20

It would be useful to explore potential issues with DNS-SD in =
constrained environments further. Is there someone who might be at =
Chicago and able to raise this issue in our meeting, briefly?  We could =
make some time for this topic. That might then help seed further work.

Tim (dnssd co-chair)

> On 14 Mar 2017, at 19:09, Ines Robles <maria.ines.robles@ericsson.com> =
wrote:
>=20
> Reviewer: Ines Robles
> Review result: Ready
>=20
> Hi,
>=20
> I have read the draft. The document provides a description of the
> requirements for a profile for label interoperation.
>=20
> In IoT, networks and nodes, in general, have constrained resources.
> Related to the topic of the draft in review, several aspects should be
> considered from IoT point of view, such as:
>=20
> - Type of devices that have insufficient resources to run DNS-SD/mDNS
> [1] (Some running code [7]). The work in [2][3] depicts an
> autoconfiguration scheme for the global (or local) DNS names of IoT
> devices. It uses an specific DNS Name Format
> (unique_id.object_identifier.OID.domain_name).
>=20
> - Resource Directory (RD): A web entity that stores information about
> web resources and implements the REST interfaces for registration and
> lookup of resources. A mapping between CoRE Link Format attributes and
> DNS-Based Service Discovery aspects (mapping ins to <Instance>,
> Mapping rt to <ServiceType> and Domain mapping) is descripted in
> version 9 of RD draft [4].=20
>=20
> - Optimization of DNS-SD: A proposal for an optimization of DNS-SD
> query using TXT records is descripted in [5].
>=20
> - DNS Message Compression [6], implemented in uBonjour Contiki.
>=20
> Thus, new work (or updates) is needed to set the requirements for
> label interoperation in this type of environments. I understand that
> this is out of scope of dns-interop draft. So, what about to add in
> the dns-interop draft some text like:
>=20
> "Related to constrained environments, work is ongoing such as
> autoconfiguration[2], optimization of DNS-SD [5] and DNS message
> compression [6] that would help to get an efficient selection of
> labels for DNS and other resolution systems."
>=20
> Hope that it helps.
>=20
> Cheers,
>=20
> Ines.
>=20
>=20
> [1] https://www.ietf.org/mail-archive/web/dnssd/current/msg00589.html
> [2] https://tools.ietf.org/html/draft-jeong-its-iot-dns-autoconf-01
> [3] Lee, Sejun, Jaehoon Paul Jeong, and Jung-Soo Park. "DNSNA: DNS
> name autoconfiguration for Internet of Things devices." Advanced
> Communication Technology (ICACT), 2016 18th International Conference
> on. IEEE, 2016.
> [4] https://tools.ietf.org/html/draft-ietf-core-resource-directory-09
> [5]
> https://tools.ietf.org/html/draft-aggarwal-dnssd-optimize-query-00
> [6] Klauck, Ronny, and Michael Kirsche. "Enhanced DNS message
> compression-Optimizing mDNS/DNS-SD for the use in 6LoWPANs." Pervasive
> Computing and Communications Workshops (PERCOM Workshops), 2013 IEEE
> International Conference on. IEEE, 2013.
> [7] https://github.com/Agile-IoT/awesome-open-iot#mdns--bonjour
>=20


--Apple-Mail=_A8FB0ECA-1BD9-4521-9700-E6CFD83556CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Ines,<div class=3D""><br class=3D""></div><div =
class=3D"">Many thanks for this review.</div><div class=3D""><br =
class=3D""></div><div class=3D"">As you=E2=80=99ve implictly noted, the =
focus of&nbsp;draft-ietf-dnssd-mdns-dns-interop-04 is interoperability =
of the labels used, primarily between unicast and multicast =
DNS.</div><div class=3D""><br class=3D""></div><div class=3D"">You raise =
some very good points about the efficiency of mDNS/DNS-SD, particularly =
in constrained environments. This isn=E2=80=99t something we=E2=80=99ve =
covered in any detail as yet in the dnssd WG, aside from =
draft-aggarwal-dnssd-optimize-query-00 being presented a few IETFs ago, =
but DNS-SD in mesh networks is in our charter (<a =
href=3D"https://datatracker.ietf.org/wg/dnssd/charter/" =
class=3D"">https://datatracker.ietf.org/wg/dnssd/charter/</a>). To date =
we=E2=80=99ve focused on enterprise and home networks as managed and =
unmanaged multi-link IP environments.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">It would be useful to explore potential =
issues with DNS-SD in constrained environments further. Is there someone =
who might be at Chicago and able to raise this issue in our meeting, =
briefly? &nbsp;We could make some time for this topic. That might then =
help seed further work.</div><div class=3D""><br class=3D""><div =
class=3D"">
<div class=3D"">Tim (dnssd co-chair)</div><div class=3D""><br =
class=3D""></div></div><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 14 Mar 2017, at 19:09, Ines Robles &lt;<a =
href=3D"mailto:maria.ines.robles@ericsson.com" =
class=3D"">maria.ines.robles@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Reviewer: Ines Robles<br class=3D"">Review result: Ready<br =
class=3D""><br class=3D"">Hi,<br class=3D""><br class=3D"">I have read =
the draft. The document provides a description of the<br =
class=3D"">requirements for a profile for label interoperation.<br =
class=3D""><br class=3D"">In IoT, networks and nodes, in general, have =
constrained resources.<br class=3D"">Related to the topic of the draft =
in review, several aspects should be<br class=3D"">considered from IoT =
point of view, such as:<br class=3D""><br class=3D"">- Type of devices =
that have insufficient resources to run DNS-SD/mDNS<br class=3D"">[1] =
(Some running code [7]). The work in [2][3] depicts an<br =
class=3D"">autoconfiguration scheme for the global (or local) DNS names =
of IoT<br class=3D"">devices. It uses an specific DNS Name Format<br =
class=3D"">(unique_id.object_identifier.OID.domain_name).<br =
class=3D""><br class=3D"">- Resource Directory (RD): A web entity that =
stores information about<br class=3D"">web resources and implements the =
REST interfaces for registration and<br class=3D"">lookup of resources. =
A mapping between CoRE Link Format attributes and<br class=3D"">DNS-Based =
Service Discovery aspects (mapping ins to &lt;Instance&gt;,<br =
class=3D"">Mapping rt to &lt;ServiceType&gt; and Domain mapping) is =
descripted in<br class=3D"">version 9 of RD draft [4]. <br class=3D""><br =
class=3D"">- Optimization of DNS-SD: A proposal for an optimization of =
DNS-SD<br class=3D"">query using TXT records is descripted in [5].<br =
class=3D""><br class=3D"">- DNS Message Compression [6], implemented in =
uBonjour Contiki.<br class=3D""><br class=3D"">Thus, new work (or =
updates) is needed to set the requirements for<br class=3D"">label =
interoperation in this type of environments. I understand that<br =
class=3D"">this is out of scope of dns-interop draft. So, what about to =
add in<br class=3D"">the dns-interop draft some text like:<br =
class=3D""><br class=3D"">"Related to constrained environments, work is =
ongoing such as<br class=3D"">autoconfiguration[2], optimization of =
DNS-SD [5] and DNS message<br class=3D"">compression [6] that would help =
to get an efficient selection of<br class=3D"">labels for DNS and other =
resolution systems."<br class=3D""><br class=3D"">Hope that it helps.<br =
class=3D""><br class=3D"">Cheers,<br class=3D""><br class=3D"">Ines.<br =
class=3D""><br class=3D""><br class=3D"">[1] <a =
href=3D"https://www.ietf.org/mail-archive/web/dnssd/current/msg00589.html"=
 =
class=3D"">https://www.ietf.org/mail-archive/web/dnssd/current/msg00589.ht=
ml</a><br class=3D"">[2] <a =
href=3D"https://tools.ietf.org/html/draft-jeong-its-iot-dns-autoconf-01" =
class=3D"">https://tools.ietf.org/html/draft-jeong-its-iot-dns-autoconf-01=
</a><br class=3D"">[3] Lee, Sejun, Jaehoon Paul Jeong, and Jung-Soo =
Park. "DNSNA: DNS<br class=3D"">name autoconfiguration for Internet of =
Things devices." Advanced<br class=3D"">Communication Technology =
(ICACT), 2016 18th International Conference<br class=3D"">on. IEEE, =
2016.<br class=3D"">[4] <a =
href=3D"https://tools.ietf.org/html/draft-ietf-core-resource-directory-09"=
 =
class=3D"">https://tools.ietf.org/html/draft-ietf-core-resource-directory-=
09</a><br class=3D"">[5]<br class=3D""><a =
href=3D"https://tools.ietf.org/html/draft-aggarwal-dnssd-optimize-query-00=
" =
class=3D"">https://tools.ietf.org/html/draft-aggarwal-dnssd-optimize-query=
-00</a><br class=3D"">[6] Klauck, Ronny, and Michael Kirsche. "Enhanced =
DNS message<br class=3D"">compression-Optimizing mDNS/DNS-SD for the use =
in 6LoWPANs." Pervasive<br class=3D"">Computing and Communications =
Workshops (PERCOM Workshops), 2013 IEEE<br class=3D"">International =
Conference on. IEEE, 2013.<br class=3D"">[7] =
https://github.com/Agile-IoT/awesome-open-iot#mdns--bonjour<br =
class=3D""><br class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_A8FB0ECA-1BD9-4521-9700-E6CFD83556CA--


From nobody Wed Mar 15 03:56:56 2017
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 9924B129B1D for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 03:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21vw7jW67Gkc for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 03:56:53 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 77433129B36 for <ietf@ietf.org>; Wed, 15 Mar 2017 03:56:52 -0700 (PDT)
Received: (qmail 6791 invoked from network); 15 Mar 2017 10:58:10 -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; 15 Mar 2017 10:58:10 -0000
To: "ietf@ietf.org" <ietf@ietf.org>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Operational feedback on PMTUD
Message-ID: <cef9e432-e6a8-5f90-f61d-67278561cb2f@necom830.hpcl.titech.ac.jp>
Date: Wed, 15 Mar 2017 19:56:46 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mwfmQJKN2K2ZLUQyM9JtzAQxKJU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 10:56:54 -0000

Hi all;

Just a procedural question.

Though rfc2026 says:

    A specification for which significant implementation and successful
    operational experience has been obtained may be elevated to the
    Internet Standard level.  An Internet Standard (which may simply be
    referred to as a Standard) is characterized by a high degree of
    technical maturity and by a generally held belief that the specified
    protocol or service provides significant benefit to the Internet
    community.

does rfc1981bis qualify?

It seems to me that rfc1981 operationally failed and rfc4821 was
developed, which means PMTUD can be IS only when rfc4821 become IS.

Or, do I misunderstand something?

						Masataka Ohta


From nobody Wed Mar 15 04:00:27 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB8DE129B55 for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 04:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LeydrvLSkumm for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 04:00:25 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9B1129B4B for <ietf@ietf.org>; Wed, 15 Mar 2017 04:00:24 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1co6fG-0000FQC; Wed, 15 Mar 2017 12:00:22 +0100
Message-Id: <m1co6fG-0000FQC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: Do you really not care whether people accept your mail? 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <m1cnjqr-0000GkC@stereo.hq.phicoh.net> <CABa8R6v+ymVRef5_7vCso2xDNAy2XtsAtRP78dbVFcaprFG3iw@mail.gmail.com> 
In-reply-to: Your message of "Tue, 14 Mar 2017 16:54:33 -0700 ." <CABa8R6v+ymVRef5_7vCso2xDNAy2XtsAtRP78dbVFcaprFG3iw@mail.gmail.com> 
Date: Wed, 15 Mar 2017 12:00:20 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Vq63ovitGfPlX2f3yKrY34bAAzc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 11:00:27 -0000

>On Tue, Mar 14, 2017 at 3:38 AM, Philip Homburg <pch-ietf-6@u-1.phicoh.com>
>wrote:
>
>>
>> In my experience, essentially no mail gets lost if you leave out SPF, DKIM,
>> DMARC. The only exception is gmail that occasionally rejects e-mail.
>>
>
>"no mail gets lost" != "gmail occasionally rejects my mail"

What I meant to write is that when I take all e-mail targets that I send e-mail
to, leaving out gmail, then sending mail without SPF, DKIM, DMARC works just
fine.

Gmail is an exception because it seems that gmail is broken if you deliver
mail without SPF, etc. over IPv6 to gmail. That's unique to gmail.

So if your outgoing mail doesn't have SPF, etc. and you do have IPv6, then
you have to think about what to do with gmail.

In any case, that's my experience.

In some sense it is amazing how reliable e-mail is. E-mail seems to be
reliable enough that gmail rejecting the occasional e-mail immediately
makes it the most unreliable e-mail provider (for my e-mail). 
That's also an amazing success story.

>> In the context of IPv6 we now have an additional problem. Sites that have
>> filters that are more strict for IPv6 than for IPv4. The obvious very
>> quick workaround for many mail admins is to avoid delivering mail over
>> IPv6.
>> Of course, that just increases the SPAM/HAM ratio, justifying more
>> draconian
>> measures. Which in the end will just kill IPv6 as a transport for e-mail.
>
>Do you imagine that you may be making different choices than others?

Imagine that some will be making different chocies than me, yes.

>There are plenty of senders, in fact the vast majority by volume, who are
>perfectly fine with authenticating their mail.  And many of them send over
>IPv6.  This may be a speed bump, but it is not the death of IPv6 for email
>transport.

It is likely that a few big providers together will make up the vast majority
of e-mail volume.

However, gmail (or in fact any I send mail to) has not made SPF, etc.
mandatory. So if gmail would make DMARC mandatory for IPv4, that would
signal something.

Maybe gmail can publish some graphs, contrasting the percentage of 
mail that arrives over IPv6 to IPv6 adoption for other google services?



From nobody Wed Mar 15 04:20:31 2017
Return-Path: <prvs=240434f47=Badri.Subramanyan@ril.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4293A129BBB; Wed, 15 Mar 2017 04:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level: 
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k1FTI_iZjwsj; Wed, 15 Mar 2017 04:20:22 -0700 (PDT)
Received: from gwsmtp010.ril.com (unknown [203.199.41.20]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 866FB129BAB; Wed, 15 Mar 2017 04:20:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.36,168,1486405800"; d="scan'208";a="378324604"
From: <Badri.Subramanyan@ril.com>
To: <acmorton@att.com>, <kathleen.moriarty.ietf@gmail.com>, <saag@ietf.org>, <ietf@ietf.org>
Subject: RE: Last call feedback: draft-mm-wg-effect-encrypt
Thread-Topic: Last call feedback: draft-mm-wg-effect-encrypt
Thread-Index: AQHSmEkdymufh+be8EG0ggEJbV3WwqGMUL1AgAD0g4CAB0r5AIABOrxA
Date: Wed, 15 Mar 2017 11:20:11 +0000
Message-ID: <0d728d3f894c4d0a9f16bd6a21088818@SIDC1EXMBX24.in.ril.com>
References: <CAHbuEH4+bd=0PJa1rWDQN6tbeRK5vXKdbcUwsj2=zf9V8ejeDg@mail.gmail.com> <c056c07568974f37aa0366bbe8a93422@SIDC1EXMBX24.in.ril.com> <4D7F4AD313D3FC43A053B309F97543CF25F3252D@njmtexg5.research.att.com>
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CF25F3252D@njmtexg5.research.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VHn8iu_kF-m6Wt_wRRHZRUAQCTg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 11:20:24 -0000

QWwsDQoNCglJbiBteSBleHBlcmllbmNlLCBwcm90b2NvbCBoYXMgYmVlbiB0aGUgNXRoIHR1cGxl
IGFsb25nIHdpdGggU291cmNlIGFuZCBEZXN0aW5hdGlvbiBJUCBhZGRyZXNzIGFuZCBwb3J0cy4N
Cg0KVGhhbmtzLA0KQmFkcmkNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IE1P
UlRPTiwgQUxGUkVEIEMgKEFMKSBbbWFpbHRvOmFjbW9ydG9uQGF0dC5jb21dIA0KU2VudDogVHVl
c2RheSwgTWFyY2ggMTQsIDIwMTcgNTowMSBQTQ0KVG86IEJhZHJpIFN1YnJhbWFueWFuIDxCYWRy
aS5TdWJyYW1hbnlhbkByaWwuY29tPjsga2F0aGxlZW4ubW9yaWFydHkuaWV0ZkBnbWFpbC5jb207
IHNhYWdAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCkNjOiBzdGVwaGVuLmZhcnJlbGxAY3MudGNk
LmllDQpTdWJqZWN0OiBSRTogTGFzdCBjYWxsIGZlZWRiYWNrOiBkcmFmdC1tbS13Zy1lZmZlY3Qt
ZW5jcnlwdA0KDQpIaSBCYWRyaSwNCm9uZSBmb2xsb3ctdXAgcXVlc3Rpb24gYmVsb3c6DQoNCj4g
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQmFkcmkuU3VicmFtYW55YW5Acmls
LmNvbSBbbWFpbHRvOkJhZHJpLlN1YnJhbWFueWFuQHJpbC5jb21dDQo+IFNlbnQ6IEZyaWRheSwg
TWFyY2ggMTAsIDIwMTcgMjozNSBBTQ0KDQo8c25pcD4NCg0KPiA+IElmIHRoZSBzdHJlYW1zIGFy
ZSBlbmNyeXB0ZWQsIHRoZW4gdGhlIEFMRyBmZWF0dXJlIHdvdWxkIGJlIHJlbmRlcmVkDQo+IA0K
PiA+IHVzZWxlc3MuIFRoaXMgd291bGQgbGltaXQgdGhlIGNhcGFiaWxpdHkgb2YgYW55IG5ldHdv
cmsgZWxlbWVudCB0bw0KPiANCj4gPiBtYWtlIHNtYXJ0IHBvbGljaW5nIGFuZCByb3V0aW5nIGRl
Y2lzaW9ucyBiYXNlZCBvbiBhcHBsaWNhdGlvbiBsYXllcg0KPiBhdHRyaWJ1dGVzLg0KPiANCj4g
DQo+IEthdGhsZWVuIHdyb3RlOg0KPiBEbyB5b3Uga25vdyBpZiB0aGVzZSBjYW4gd29yayB3aXRo
IGEgMi10dXBsZSBvciA1LXR1cGxlPyAgSXMgdGhlcmUgYW4gDQo+IGltcGFjdCBmcm9tIGVuY3J5
cHRpb24gdmlhIFRMUyBmb3IgaW5zdGFuY2U/ICBJZiBzbywgd2hhdCBpcyB0aGF0IA0KPiBpbXBh
Y3Q/DQo+IA0KPiBbQmFkcmldIFRoZSBydWxlcyBpbiBtb3N0IG9mIHRoZSBjYXNlcyBpcyA1LXR1
cGxlIHRvIGFjY3VyYXRlbHkgZGVwaWN0IA0KPiBhIGZsb3cuIFllcywgdGhlcmUgaXMgYW4gaW1w
YWN0IGZyb20gZW5jcnlwdGlvbiB2aWEgVExTIGFzIG1vc3Qgb2YgdGhlIA0KPiBpbXBsZW1lbnRh
dGlvbnMgb2YgQUxHIGdldCBpbmZvcm1hdGlvbiByZWdhcmRpbmcgc3VwcG9ydGluZyBwcm90b2Nv
bHMgDQo+IGJ5IHBhcnNpbmcgZGF0YS4gV2l0aCBUTFMgZW5jcnlwdGlvbiwgdGhlIEFMRyBsb3Nl
cyB0aGUgYWJpbGl0eSB0byANCj4gcGFyc2UsIGhlbmNlIGdldCBpbmZvcm1hdGlvbiBvbiB0aGUg
c3VwcG9ydGluZyBwcm90b2NvbHMuDQo+IA0KPiANCj4gS2F0aGxlZW4gd3JvdGU6DQo+IFdoYXQg
aXMgdXNlZCBieSBBTEcgdG8gY29ycmVsYXRlIHN0cmVhbXM/ICBUaGlzIHdvdWxkIGJlIGhlbHBm
dWwgdG8gDQo+IHVuZGVyc3RhbmQgaWYgdGhpcyBwYXJ0aWN1bGFyIG1ldGhvZCBmb3IgQUxHcyBk
b2VzIGJlY29tZSAndXNlbGVzcycNCj4gYW5kIGFsc28gdG8gZmlndXJlIG91dCBpZiBvdGhlciBv
cHRpb25zIG1heSBleGlzdCB0byBwZXJmb3JtIHRoZSANCj4gZnVuY3Rpb25zIG5lZWRlZC4NCj4g
DQo+IFtCYWRyaV0gUkZDIDI2NjMsIFNlY3Rpb24gMi45IGdpdmVzIGluZm9ybWF0aW9uIGFib3V0
IEFMRy4gVGhlcmUgaXNu4oCZdCANCj4gb25lIGRlZmluZWQgbWV0aG9kIHRvIGltcGxlbWVudCBp
dCBhbmQgc29tZSBvZiB0aGUgbWV0aG9kcyB1c2VkIGJ5IA0KPiB2ZW5kb3JzIGFyZSBpbmNsdWRl
ZCBiZWxvdy4NCj4gDQo+IDEuICBQYXJzZSB0aGUgY29udGVudCBvZiB0aGUgcHJpbWFyeSBzdHJl
YW0gYW5kIGlkZW50aWZ5IHRoZSA1LXR1cGxlIA0KPiBvZiB0aGUgc3VwcG9ydGluZyBzdHJlYW1z
IGFzIGl0IGlzIGJlaW5nIG5lZ290aWF0ZWQuDQo+IA0KPiAyLiBJbnRlcmNlcHQgYW5kIG1vZGlm
eSB0aGUgNS10dXBsZSBpbmZvcm1hdGlvbiBvZiB0aGUgc3VwcG9ydGluZyANCj4gc3RyZWFtIGFz
IHRoZSBpdCBpcyBiZWluZyBuZWdvdGlhdGVkIG9uIHRoZSBwcmltYXJ5IHN0cmVhbS4gVGhpcyBp
cyBhIA0KPiBsaXR0bGUgbW9yZSBpbnRydXNpdmUgaW4gbmF0dXJlLg0KPiANCj4gDQpbQUNNXQ0K
QWZ0ZXIgU3JjJkRzdCBBZGRyZXNzIGFuZCBQb3J0LCB3aGF0IGlzIHRoZSA1dGggRWxlbWVudCBv
ZiB0aGUgNS10dXBsZSBpbiB5b3VyIGV4cGVyaWVuY2U/DQoNClByb3RvY29sIG51bWJlciBhbmQg
UGFja2V0IFByaW9yaXR5IE1hcmtpbmcgKERTQ1ApIGFyZSB0d28gY2FuZGlkYXRlcy4uLg0KDQps
ZXQgdXMga25vdywgdGhhbmtzIQ0KQWwNCg0KIkNvbmZpZGVudGlhbGl0eSBXYXJuaW5nOiBUaGlz
IG1lc3NhZ2UgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgaW50ZW5kZWQgb25seSBmb3IgdGhlIHVz
ZSBvZiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50KHMpLiANCmFyZSBjb25maWRlbnRpYWwgYW5kIG1h
eSBiZSBwcml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LiB5
b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSANCnJldmlldy4gcmUtdHJhbnNtaXNzaW9u
LiBjb252ZXJzaW9uIHRvIGhhcmQgY29weS4gY29weWluZy4gY2lyY3VsYXRpb24gb3Igb3RoZXIg
dXNlIG9mIHRoaXMgbWVzc2FnZSBhbmQgYW55IGF0dGFjaG1lbnRzIGlzIA0Kc3RyaWN0bHkgcHJv
aGliaXRlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudC4gcGxlYXNlIG5v
dGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5IGJ5IHJldHVybiBlbWFpbC4gDQphbmQgZGVsZXRl
IHRoaXMgbWVzc2FnZSBhbmQgYW55IGF0dGFjaG1lbnRzIGZyb20geW91ciBzeXN0ZW0uDQoNClZp
cnVzIFdhcm5pbmc6IEFsdGhvdWdoIHRoZSBjb21wYW55IGhhcyB0YWtlbiByZWFzb25hYmxlIHBy
ZWNhdXRpb25zIHRvIGVuc3VyZSBubyB2aXJ1c2VzIGFyZSBwcmVzZW50IGluIHRoaXMgZW1haWwu
IA0KVGhlIGNvbXBhbnkgY2Fubm90IGFjY2VwdCByZXNwb25zaWJpbGl0eSBmb3IgYW55IGxvc3Mg
b3IgZGFtYWdlIGFyaXNpbmcgZnJvbSB0aGUgdXNlIG9mIHRoaXMgZW1haWwgb3IgYXR0YWNobWVu
dC4iCg==


From nobody Wed Mar 15 07:38:00 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A5121315A7; Wed, 15 Mar 2017 07:37:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
Cc: ipsec@ietf.org, draft-ietf-ipsecme-rfc4307bis.all@ietf.org, ietf@ietf.org
Subject: Review of draft-ietf-ipsecme-rfc4307bis-17
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148958867307.4072.14018084445475450669@ietfa.amsl.com>
Date: Wed, 15 Mar 2017 07:37:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LIGfbaIr6iayqF2N64OAXRv6XdM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 14:37:53 -0000

Reviewer: Pete Resnick
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ipsecme-rfc4307bis-17
Reviewer: Pete Resnick
Review Date: 2017-03-15
IETF LC End Date: 2017-01-31
IESG Telechat date: 2017-03-16

Summary:

Ready

Major issues:

None

Minor issues:

None

Nits/editorial comments: 

While using MUST, SHOULD, and MAY as nouns and adjectives causes me a
twitch, this document is just fine. There's a typo in the first
paragraph of 1.2.


From nobody Wed Mar 15 08:35:08 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB101316A5 for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 08:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.795
X-Spam-Level: 
X-Spam-Status: No, score=-4.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9VM8wqHxjDmP for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 08:35:06 -0700 (PDT)
Received: from homiemail-a32.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A7E51316A4 for <ietf@ietf.org>; Wed, 15 Mar 2017 08:35:06 -0700 (PDT)
Received: from homiemail-a32.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTP id CDAF46001106; Wed, 15 Mar 2017 08:35:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=FiQ1UfR1OPDJOE EomKf2MS/cm/o=; b=E3pjB3U1F+olGEy/Ry/VrRVLwOBn1lkieuzpoZOaUuan90 00FCzID48bvP388NqAdT6Af4eMBA35jmtPHUzegkn87YCK0N1b4k66KIbmwJJ2G+ c8rhzNkS5m45RRx63lO1bZLvUPQYVje8rtnVhjGk6Fw1BU78zhe97w+F3NDis=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTPSA id 7383F6001104; Wed, 15 Mar 2017 08:35:05 -0700 (PDT)
Date: Wed, 15 Mar 2017 10:35:03 -0500
From: Nico Williams <nico@cryptonector.com>
To: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Cc: ietf@ietf.org
Subject: Re: Do you really not care whether people accept your mail?
Message-ID: <20170315153502.GA7490@localhost>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <m1cnjqr-0000GkC@stereo.hq.phicoh.net> <CABa8R6v+ymVRef5_7vCso2xDNAy2XtsAtRP78dbVFcaprFG3iw@mail.gmail.com> <m1co6fG-0000FQC@stereo.hq.phicoh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m1co6fG-0000FQC@stereo.hq.phicoh.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gWM_7uA9auxXJUvZLKdpiHSKY3E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 15:35:08 -0000

On Wed, Mar 15, 2017 at 12:00:20PM +0100, Philip Homburg wrote:
> >On Tue, Mar 14, 2017 at 3:38 AM, Philip Homburg <pch-ietf-6@u-1.phicoh.com>
> >wrote:
> >> In my experience, essentially no mail gets lost if you leave out SPF, DKIM,
> >> DMARC. The only exception is gmail that occasionally rejects e-mail.
> >
> >"no mail gets lost" != "gmail occasionally rejects my mail"
> 
> What I meant to write is that when I take all e-mail targets that I send e-mail
> to, leaving out gmail, then sending mail without SPF, DKIM, DMARC works just
> fine.
> 
> Gmail is an exception because it seems that gmail is broken if you deliver
> mail without SPF, etc. over IPv6 to gmail. That's unique to gmail.

The problem is twofold: a) gmail has a huge number of mailboxes, so if
you can't deliver to them without SPF/DKIM/DMARC, then your mail truly
is broken, b) they could be setting the rule, so that even if you don't
mind (a), you soon will feel the pain.

> So if your outgoing mail doesn't have SPF, etc. and you do have IPv6, then
> you have to think about what to do with gmail.

As a user, when I send email, I don't want to think about this sort of
thing.  An admin has to think about this sort of thing, and it's looking
a lot like email is nowhere near the relatively easy service to run that
it was in the 90s.

> In some sense it is amazing how reliable e-mail is. E-mail seems to be
> reliable enough that gmail rejecting the occasional e-mail immediately
> makes it the most unreliable e-mail provider (for my e-mail). 
> That's also an amazing success story.

Well, I adore email, and email lists.  Screw the haters.  But it's true
that we have a problem, and if we don't manage it then email will be
obsolete and I'll be sad.

> >Do you imagine that you may be making different choices than others?
> 
> Imagine that some will be making different chocies than me, yes.

Balkanizing email doesn't sound very good to me.

Nico
-- 


From nobody Wed Mar 15 08:45:00 2017
Return-Path: <sean@sn3rd.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50621316AD for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 08:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B7HSGl2q1rWs for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 08:44:46 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DAE9124234 for <ietf@ietf.org>; Wed, 15 Mar 2017 08:44:44 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id r45so15410837qte.3 for <ietf@ietf.org>; Wed, 15 Mar 2017 08:44:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UMC4X0VcFpkDrEcjCW/8BanOfuix6BICYMcm4Kxikx0=; b=AtQ69pv6dMO4xtuLPN6CeLvsbhmqtZi5q9BCVozQ/tgWnFi1bDXJrRvpcPjtqavQti 4xmhFkNPfalsN85vj8ywQl6njbodqw4rn6MZLByOA3VBh7KTKmAjXw8TG87vB0cetYYA BePfON+gzHcV+tUyNtaNyvCLVDgjb142z82VE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UMC4X0VcFpkDrEcjCW/8BanOfuix6BICYMcm4Kxikx0=; b=SKVWblHeXnaHvYtYceny9Ye/dswtXyIo8OpBSEJy+gHbmI/mPfpILozOPhK7jsjXD4 8oI8e6HAY43+5ev9Llz9vq0UfPyB/Irj5Y8K6ru73txxKmhAwkKcBklb1IgqIQBjxHAT jdyimjj7WIGfqiAnzu0NRCFdp7+/brJ56ZYQjlMBElDOxTXWmZtwHDa2OHRqyDkykAcG GWFG9l3EFOn3/+LUupTv/qfvVkbQzlEM8qKJC2fPf1gu/YLLhRiMt3fBVCD6FYnAxaTY q6iRmC/iScNsc7KPhTOizKNrT4PiEHYqsLyr0LA805mBS/MHfqwSO4deuXkX2RXuQcAM E2sg==
X-Gm-Message-State: AFeK/H18AzA2oP6EvjhRgAQCpquDwGaKAyE7RpnZ0pXQpXBjHxx3pETnTU5tcsEUI8vHpA==
X-Received: by 10.200.45.57 with SMTP id n54mr3704923qta.212.1489592683248; Wed, 15 Mar 2017 08:44:43 -0700 (PDT)
Received: from [172.16.0.18] ([96.231.230.131]) by smtp.gmail.com with ESMTPSA id q11sm1536236qkh.16.2017.03.15.08.44.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Mar 2017 08:44:41 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Review of draft-ietf-sidr-bgpsec-pki-profiles-21
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <148844379373.7077.11693707774114284535.idtracker@ietfa.amsl.com>
Date: Wed, 15 Mar 2017 11:44:40 -0400
Cc: ops-dir@ietf.org, draft-ietf-sidr-bgpsec-pki-profiles.all@ietf.org, ietf@ietf.org, sidr@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <54D7584B-B009-4461-8499-8E7717220867@sn3rd.com>
References: <148844379373.7077.11693707774114284535.idtracker@ietfa.amsl.com>
To: Shucheng LIU <liushucheng@huawei.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/R7A7a1PLtIReCI1SlpmaAo7x9IM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 15:44:48 -0000

> On Mar 2, 2017, at 03:36, Shucheng LIU <liushucheng@huawei.com> wrote:
>=20
> ** Editorial **
>=20
> *Section 4
>=20
>> BGPsec Router Certificates always include the BGPsec Rouer EKU
>>    value; therefore, request without the value result in
> certificates
>>    with the value; and,
>=20
> s/Rouer/Router

Thanks! If the RFC editor misses this I=E2=80=99ll make sure that it =
gets fixed up in AUTH48.

spt=


From nobody Wed Mar 15 08:55:14 2017
Return-Path: <sprevidi@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 D78AE1316A8; Wed, 15 Mar 2017 08:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oUd8llH42SHy; Wed, 15 Mar 2017 08:55:09 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73A0F1315AE; Wed, 15 Mar 2017 08:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8814; q=dns/txt; s=iport; t=1489593309; x=1490802909; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yIRAFpwkzabIqarhAmkAHQUnNJ+vI6HfxkGQaS2uQgY=; b=NjVvPyec0FzTR3thk3OrIf9apDX2k3hu4XRXYDUZoJYYZaw8H/VkeCPB SS0Q+fWT7f0AAraw0xHxSnPqe85RUv1zaSIxTsDVbXw9sqR9PwhvLUqXK K3ryf2J302CFrA1jP9fzAOMPO3WYa/HYJsFD3kXyNo3M4nkUW4l0AsyXC c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CAAgCoY8lY/4cNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgycqYYEKB4NZig2RNx+VPIIOHwuFeAIaglQ/GAECAQEBAQEBAWs?= =?us-ascii?q?ohRUBAQEBAgEBASEROgsFCwIBCBgCAhEVAgICJQsVEAIEDgWJeAgOriyCJopfA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBC4VDggUIgmKEVD+CRy6CMQWJG5MoAYo?= =?us-ascii?q?diB2Be4UligWTRgEfOIEEWBVBEQGERR2BY3WIJYENAQEB?=
X-IronPort-AV: E=Sophos;i="5.36,169,1486425600"; d="scan'208";a="398503292"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Mar 2017 15:55:01 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v2FFt16h030618 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 15 Mar 2017 15:55:01 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 15 Mar 2017 11:55:00 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Wed, 15 Mar 2017 11:55:00 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
CC: "ietf@ietf.org" <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnaSAxRLtjcu1EUaNXmYCyEu8gw==
Date: Wed, 15 Mar 2017 15:55:00 +0000
Message-ID: <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com>
In-Reply-To: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.226.30]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1D37C893B235B34F801F8198029EAA03@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ade9QyRKyMZjWFxb5-b_fGM6PUg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 15:55:12 -0000

U3VyZXNoLA0KDQpJIGFwcHJlY2lhdGUgeW91ciBlZmZvcnQgYW5kIEnigJltIG9idmlvdXNseSBp
bnRlcmVzdGVkIGludG8gZmluZGluZyBhIHdheSBvdXQgZnJvbSB0aGlzIGlzc3VlLg0KDQpUbyBt
eSB2aWV3LCBkdWUgdG8gdGhlIHdvcmsgdGhhdCBoYXMgYmVlbiBpbml0aWF0ZWQgaW4gZHJhdC1p
ZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBhbmQgcmVjZW50bHkgaW4gZHJhZnQtZmls
c2ZpbHMtc3J2Ni1uZXR3b3JrLXByb2dyYW1taW5nLCB0aGUgY3VycmVudCB0ZXh0IG9mIFJGQzI0
NjAgKGkuZS4sIG5vdCB0aGUg4oCcYmlz4oCdIHZlcnNpb24pIGlzIGdvb2QgZW5vdWdoLg0KDQpS
RkMyNDYwIHNlY3Rpb24gNCBzdGF0ZXM6DQoNCiAgIFdpdGggb25lIGV4Y2VwdGlvbiwgZXh0ZW5z
aW9uIGhlYWRlcnMgYXJlIG5vdCBleGFtaW5lZCBvciBwcm9jZXNzZWQNCiAgIGJ5IGFueSBub2Rl
IGFsb25nIGEgcGFja2V0J3MgZGVsaXZlcnkgcGF0aCwgdW50aWwgdGhlIHBhY2tldCByZWFjaGVz
DQogICB0aGUgbm9kZSAob3IgZWFjaCBvZiB0aGUgc2V0IG9mIG5vZGVzLCBpbiB0aGUgY2FzZSBv
ZiBtdWx0aWNhc3QpDQogICBpZGVudGlmaWVkIGluIHRoZSBEZXN0aW5hdGlvbiBBZGRyZXNzIGZp
ZWxkIG9mIHRoZSBJUHY2IGhlYWRlci4NCg0KTm93LCBSRkMyNDYwIGhhcyBiZWVuIHdyaXR0ZW4g
YWxtb3N0IDIwIHllYXJzIGFnbyBhbmQgc2luY2UgdGhlbiwgYm90aCB0ZWNobm9sb2d5IGFuZCBu
ZXR3b3JrIG9wZXJhdG9ycyByZXF1aXJlbWVudHMgaGF2ZSBldm9sdmVkLg0KDQpXZSBkbyBoYXZl
IHRvZGF5IHVzZSBjYXNlcyB3aGVyZSBub3Qgb25seSB0aGUgc291cmNlIG9mIGEgcGFja2V0IHNo
b3VsZCBiZSBhbGxvd2VkIHRvIGluc2VydCBhIGhlYWRlciBidXQgYWxzbyB0aGUgc291cmNlIOKA
nGRvbWFpbuKAnSBvZiBhIHBhY2tldC4gSeKAmWxsIHRyeSB0byBleHBsYWluLg0KDQpJbiBhIGRv
bWFpbiBjb250cm9sbGVkIGJ5IGEgc2luZ2xlIG9yZ2FuaXphdGlvbiAodHlwaWNhbGx5IHRoZSBz
ZXQgb2YgQVNzIHVuZGVyIGNvbnRyb2wgb2YgdGhlIHNhbWUgb3BlcmF0b3IpIGEgcGFja2V0IGVu
dGVycyBhdCB0aGUgZWRnZSB3aGVyZSB0aGUgaW5ncmVzcyBub2RlIGFwcGxpZXMgYSBwb2xpY3kg
cmVzdWx0ZWQgaW50byBhbiBhZGRpdGlvbmFsIG91dGVyIGlwdjYgaGVhZGVyIHRoYXQgbWF5IG9y
IG1heSBub3QgY29udGFpbiBhbiBleHRlbnNpb24gaGVhZGVyLiBCb3R0b20gbGluZSwgdGhlIG91
dGVyIGhlYWRlciBtZWFucyB0aGF0IG5vdywgaXQgaXMgYSBORVcgcGFja2V0LCBvcmlnaW5hdGVk
IGJ5IHRoZSBpbmdyZXNzIG5vZGUsIHdpdGggU0EvREEgcmVwcmVzZW50aW5nIHRoZSBub2RlcyB0
aGF0IGFyZSBpbnNpZGUgdGhlIG9wZXJhdG9yIGRvbWFpbi4gVGhlcmVmb3JlLCB3ZSBjYW4gc2F5
IHRoYXQgdGhpcyBuZXcgcGFja2V0IChmb3JtZWQgYnkgYW4gb3V0ZXIgaGVhZGVyIGFuZCBlbmNh
cHN1bGF0ZWQgb3JpZ2luYWwgcGFja2V0KSBpcyBub3cgb3duZWQgYnkgdGhlIG9wZXJhdG9yIGFu
ZCB3aGF0ZXZlciB0aGUgb3BlcmF0b3IgZG9lcyB3aXRoIHRoaXMgcGFja2V0Og0KDQouIFRoZSBw
YWNrZXQgTVVTVCBsZWF2ZSB0aGUgb3BlcmF0b3IgbmV0d29yayBpbiB0aGUgZXhhY3Qgc2FtZSBz
aGFwZS9mb3JtYXQgYXMgaXQgZW50ZXJlZCAoaS5lLjogb3V0ZXIgZW5jYXBzdWxhdGlvbiByZW1v
dmVkKS4NCi4gVGhlIG91dGVyIGhlYWRlciBNQVkgY2hhbmdlIHdoaWxlIGluIHRyYW5zaXQgaW4g
dGhlIG9wZXJhdG9y4oCZcyBkb21haW4uIE1vcmVvdmVyLCBhIGhlYWRlciBNQVkgYmUgaW5zZXJ0
ZWQgd2hpbGUgaW5zaWRlIHRoZSBvcGVyYXRvcuKAmXMgZG9tYWluIChrbm93aW5nIHRoYXQgb3V0
ZXIgaGVhZGVyIGFuZCBhbnkgb3RoZXIgaW5zZXJ0ZWQgaGVhZGVyIHdvdWxkIGJlIHJlbW92ZWQg
YXQgZWdyZXNzKS4gVGhpcyBtZWFucyB0aGF0IGFuIFNSSCBNQVkgYmUgaW5zZXJ0ZWQgYXQgdGhl
IHNhbWUgdGltZSB0aGUgb3V0ZXIgaGVhZGVyIGlzIGFkZGVkIGJ1dCBpdCBjYW4gYWxzbyBiZSB0
aGF0IHRoZSBpbmdyZXNzIGFkZHMgdGhlIG91dGVyIGhlYWRlciBhbmQgc29tZSBvdGhlciBub2Rl
IGluc2VydHMgYW4gU1JIIChlLmcuOiBmYXN0IHJlcm91dGUgd2l0aGluIG9wZXJhdG9y4oCZcyBp
bmZyYXN0cnVjdHVyZSkuDQouIFdoaWxlIGluIHRyYW5zaXQsIHRoZSBvcGVyYXRvciBuZXR3b3Jr
IG11c3QgaGFuZGxlIGFzcGVjdHMgbGlrZSBNVFUgcHJvcGVybHksIHRha2luZyBpbnRvIGFjY291
bnQgdGhlIGluY3JlYXNlZCBzaXplIG9mIHRoZSBwYWNrZXQuDQoNClNvLCB0aGlzIHVzZSBjYXNl
IGVubGFyZ2UgdGhlIHJ1bGUgZm9yIGhlYWRlciBpbnNlcnRpb24uDQoNCk9yaWdpbmFsbHkgUkZD
MjQ2MCBzdGF0ZWQgdGhhdCBvbmx5IHRoZSBzb3VyY2Ugb2YgdGhlIHBhY2tldCBpcyBlbnRpdGxl
ZCB0byBhZGQgYW4gRUguIE5vdyB3ZeKAmXJlIGdvaW5nIHRvIHByb3Bvc2UgdGhhdCB0aGUgc291
cmNlIOKAnGRvbWFpbuKAnSBvZiB0aGUgcGFja2V0IGlzIGFsbG93ZWQgdG8gaW5zZXJ0IEVIcy4g
VGhlIHNvdXJjZSBkb21haW4gYmVpbmcgdGhlIHNldCBvZiBub2RlcyAoaW5jbHVkaW5nIHRoZSBp
bmdyZXNzIG5vZGUgYWRkaW5nIHRoZSBvdXRlciBoZWFkZXIpIHVuZGVyIGNvbW1vbiBhZG1pbmlz
dHJhdGlvbi4gVGhpcyBhbHNvIGltcGxpZXMgdGhhdCB3aGVuIHRoZSBwYWNrZXQgbGVhdmVzIHRo
ZSBkb21haW4sIGl0IG11c3QgcmVjb3ZlciBpdHMgb3JpZ2luYWwgZm9ybWF0L3NoYXBlLg0KDQpJ
biBvcmRlciB0byBoYXZlIGEgbW9yZSBwcm9kdWN0aXZlIGRpc2N1c3Npb24sIHdlIGFyZSB3cml0
aW5nIGEgZHJhZnQgb24gaGVhZGVyIGluc2VydGlvbiB0aGF0IHdpbGwgYmUgc3VibWl0dGVkIGFz
IHNvb24gYXMgdGhlIHdpbmRvd3MgcmUtb3BlbiAoZHVyaW5nIGlldGYgd2VlaykuDQoNCkluIHRo
ZSBtZWFuIHRpbWUsIEkgdGhpbmsgaXQgaXMgd2F5IHRvbyBwcmVtYXR1cmUgdG8gY29tZSB0byBj
b25jbHVzaW9uIG9uIHdoYXQgdGV4dCBzaG91bGQgYmUgdXNlZCBmb3IgUkZDMjQ2MGJpcyBhbmQg
SSByZWNvbW1lbmQgdGhhdCB0aGUgY3VycmVudCB0ZXh0IGlzIGxlZnQgdW5jaGFuZ2VkIHVudGls
IHdlIGZpZ3VyZWQgb3V0IHdoYXQgdG8gZG8gd2l0aCBFSCBpbnNlcnRpb24uDQoNClRoYW5rcy4N
CnMuDQoNCg0KPiBPbiBNYXIgMTUsIDIwMTcsIGF0IDM6NDcgQU0sIFN1cmVzaCBLcmlzaG5hbiA8
c3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbT4gd3JvdGU6DQo+IA0KPiBUaGFua3MgdG8gZXZl
cnlvbmUgd2hvIGNvbW1lbnRlZCBkdXJpbmcgdGhlIElFVEYgTGFzdCBDYWxsIG9mIGRyYWZ0LWll
dGYtNm1hbi1yZmMyNDYwYmlzLTA4LiBUaGUgSUVURiBsYXN0IGNhbGwgZGlzY3Vzc2lvbiBmb3Ig
dGhpcyBkcmFmdCB3YXMgbWFpbmx5IGZvY3VzZWQgYXJvdW5kIHRoZSB0ZXh0IGluIFNlY3Rpb24g
NCB0aGF0IGRpc2N1c3NlcyB0aGUgaGFuZGxpbmcgb2YgZXh0ZW5zaW9uIGhlYWRlcnMuIFRoZSBi
aWdnZXN0IGNvbmNlcm4gcmFpc2VkIHdhcyB0aGF0IHRoZSBjdXJyZW50IHRleHQgaXMgYW1iaWd1
b3VzIG9uIHdoZXRoZXIgaGVhZGVyIGluc2VydGlvbiBpcyBhbGxvd2VkIG9uIGludGVybWVkaWF0
ZSBub2RlcyBvciBub3QuIFRoZXJlIHdlcmUgc29tZSBwZW9wbGUgYXJndWluZyB0aGF0IGFuIGV4
cGxpY2l0IHByb2hpYml0aW9uIGlzIG5vdCBuZWNlc3NhcnkgYXMgdGhlIHRleHQgaXMgYWxyZWFk
eSBjbGVhciwgd2hpbGUgb3RoZXJzIGJlbGlldmVkIHRoYXQgZXhwbGljaXRseSBsaXN0aW5nIHRo
ZSBwcm9oaWJpdGlvbnMgd2lsbCBtaW5pbWl6ZSBhbnkgbWlzdW5kZXJzdGFuZGluZ3MgaW4gdGhl
IGZ1dHVyZS4gVGhlcmUgd2FzIGFsc28gYSBzbWFsbCBudW1iZXIgb2YgcGVvcGxlIHdobyB3YW50
ZWQgdG8gZXhwbGljaXRseSBhbGxvdyBoZWFkZXIgaW5zZXJ0aW9uIGFuZCBkZXNjcmliZSBob3cg
dG8gZG8gaXQsIGJ1dCB0aGlzIHdhcyBjbGVhcmx5IG91dCBvZiBzY29wZSBmb3IgdGhpcyBkcmFm
dCAoYnV0IG1heSBiZSBpbiBzY29wZSBmb3IgZnV0dXJlIHdvcmsgaW4gNm1hbikuIE92ZXJhbGws
IG5vIG9uZSBhcmd1ZWQgYWdhaW5zdCB0aGUgZmFjdCB0aGF0IHRoZSBpbnRlbnQgb2YgdGhlIHRl
eHQgaW4gUkZDMjQ2MCB3YXMgdG8gZm9yYmlkIGluc2VydGlvbiBvZiBleHRlbnNpb24gaGVhZGVy
cyBvbiBhbnkgb3RoZXIgbm9kZSBidXQgdGhlIHNvdXJjZSBvZiB0aGUgcGFja2V0LiAgVGhlIG9u
bHkgYXJndW1lbnQgbWFkZSBhZ2FpbnN0IGFkZGluZyBjbGFyaWZ5aW5nIHRleHQgd2FzIHRoYXQg
dGhlIHRleHQgd2FzIGFscmVhZHkgY2xlYXIuIEdpdmVuIHRoaXMsIEkgYmVsaWV2ZSB0aGVyZSBp
cyBjb25zZW5zdXMgdG8gYWRkIGV4cGxpY2l0IHRleHQgYWJvdXQgaGVhZGVyIGluc2VydGlvbiBp
bnRvIHRoZSBkcmFmdCBiZWZvcmUgaXQgcHJvZ3Jlc3NlcyBmdXJ0aGVyLiBJIGhhdmUgZGlzY3Vz
c2VkIHRoaXMgd2l0aCB0aGUgZWRpdG9yIGFuZCB0aGUgZG9jdW1lbnQgc2hlcGhlcmQgYW5kIHdv
dWxkIGxpa2UgdG8gcHJvcG9zZSB0aGUgZm9sbG93aW5nIHRleHQgY2hhbmdlLg0KPiANCj4gT0xE
IChmcm9tIC0wOCk6DQo+IA0KPiBUaGUgaW5zZXJ0aW9uIG9mIEV4dGVuc2lvbiBIZWFkZXJzIGJ5
IGFueSBub2RlIG90aGVyIHRoYW4gdGhlIHNvdXJjZQ0KPiBvZiB0aGUgcGFja2V0IGNhdXNlcyBz
ZXJpb3VzIHByb2JsZW1zLiAgVHdvIGV4YW1wbGVzIGluY2x1ZGUgYnJlYWtpbmcNCj4gdGhlIGlu
dGVncml0eSBjaGVja3MgcHJvdmlkZWQgYnkgdGhlIEF1dGhlbnRpY2F0aW9uIEhlYWRlciBJbnRl
Z3JpdHkNCj4gW1JGQzQzMDJdLCBhbmQgYnJlYWtpbmcgUGF0aCBNVFUgRGlzY292ZXJ5IHdoaWNo
IGNhbiByZXN1bHQgaW4gSUNNUA0KPiBlcnJvciBtZXNzYWdlcyBiZWluZyBzZW50IHRvIHRoZSBz
b3VyY2Ugb2YgdGhlIHBhY2tldCB0aGF0IGRpZCBub3QNCj4gaW5zZXJ0IHRoZSBoZWFkZXIsIHJh
dGhlciB0aGFuIHRoZSBub2RlIHRoYXQgaW5zZXJ0ZWQgdGhlIGhlYWRlci4NCj4gDQo+IE9uZSBh
cHByb2FjaCB0byBhdm9pZCB0aGVzZSBwcm9ibGVtcyBpcyB0byBlbmNhcHN1bGF0ZSB0aGUgcGFj
a2V0DQo+IHVzaW5nIGFub3RoZXIgSVB2NiBoZWFkZXIgYW5kIGluY2x1ZGluZyB0aGUgYWRkaXRp
b25hbCBleHRlbnNpb24NCj4gaGVhZGVyIGFmdGVyIHRoZSBmaXJzdCBJUHY2IGhlYWRlciwgZm9y
IGV4YW1wbGUsIGFzIGRlZmluZWQgaW4NCj4gW1JGQzI0NzNdDQo+IA0KPiBXaXRoIG9uZSBleGNl
cHRpb24sIGV4dGVuc2lvbiBoZWFkZXJzIGFyZSBub3QgcHJvY2Vzc2VkIGJ5IGFueSBub2RlDQo+
IGFsb25nIGEgcGFja2V0J3MgZGVsaXZlcnkgcGF0aCwgdW50aWwgdGhlIHBhY2tldCByZWFjaGVz
IHRoZSBub2RlIChvcg0KPiBlYWNoIG9mIHRoZSBzZXQgb2Ygbm9kZXMsIGluIHRoZSBjYXNlIG9m
IG11bHRpY2FzdCkgaWRlbnRpZmllZCBpbiB0aGUNCj4gRGVzdGluYXRpb24gQWRkcmVzcyBmaWVs
ZCBvZiB0aGUgSVB2NiBoZWFkZXIuLi4NCj4gDQo+IE5FVzoNCj4gDQo+IFdpdGggb25lIGV4Y2Vw
dGlvbiwgZXh0ZW5zaW9uIGhlYWRlcnMgYXJlIG5vdCBleGFtaW5lZCwgcHJvY2Vzc2VkLA0KPiBp
bnNlcnRlZCwgb3IgZGVsZXRlZCBieSBhbnkgbm9kZSBhbG9uZyBhIHBhY2tldCdzIGRlbGl2ZXJ5
IHBhdGgsDQo+IHVudGlsIHRoZSBwYWNrZXQgcmVhY2hlcyB0aGUgbm9kZSAob3IgZWFjaCBvZiB0
aGUgc2V0IG9mIG5vZGVzLCBpbg0KPiB0aGUgY2FzZSBvZiBtdWx0aWNhc3QpIGlkZW50aWZpZWQg
aW4gdGhlIERlc3RpbmF0aW9uIEFkZHJlc3MgZmllbGQgb2YNCj4gdGhlIElQdjYgaGVhZGVyLi4u
DQo+IA0KPiBQbGVhc2UgZmVlbCBmcmVlIHRvIGNvbW1lbnQgZWl0aGVyIHByaXZhdGVseSBvciBv
biBsaXN0IGlmIHlvdSBoYXZlIGFueSBjb25jZXJucyB3aXRoIHRoaXMgcmVzb2x1dGlvbiBnb2lu
ZyBmb3J3YXJkLg0KPiANCj4gUmVnYXJkcw0KPiBTdXJlc2gNCj4gDQo+IFAuUy46IFRoZXJlIHdl
cmUgYWxzbyBvdGhlciBlZGl0b3JpYWwgaXNzdWVzIHRoYXQgd2VyZSByYWlzZWQgZHVyaW5nIGxh
c3QgY2FsbCBhbmQgdGhleSBzaG91bGQgYmUgYWRkcmVzc2VkIGluIHRoZSBuZXh0IHZlcnNpb24g
b2YgdGhlIGRyYWZ0LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gSUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGlu
ZyBsaXN0DQo+IGlwdjZAaWV0Zi5vcmcNCj4gQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXB2Ng0KPiAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQo=


From nobody Wed Mar 15 08:57:35 2017
Return-Path: <rsk@gsp.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 81B491316A8 for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 08:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BQfd_3W--0FT for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 08:57:32 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 343121315AE for <ietf@ietf.org>; Wed, 15 Mar 2017 08:57:32 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v2FFvUWg013186 for <ietf@ietf.org>; Wed, 15 Mar 2017 11:57:30 -0400 (EDT)
Date: Wed, 15 Mar 2017 11:57:30 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Do you really not care whether people accept your mail?
Message-ID: <20170315155730.GA32535@gsp.org>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <A373006B-DB4F-468A-A3D1-0ED07BD98B35@puck.nether.net> <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+LwgME0QjqYN65a5+Arv4DH=-=pnNLPT65TKYKM4cm=7WsA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C-kT0evXHEvyCbtWkdmG8pwrbtA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 15:57:33 -0000

On Mon, Mar 13, 2017 at 10:41:46PM -0400, Phillip Hallam-Baker wrote:
> ???Perhaps we should just recognize the fact that SMTP does not really
> support mailing lists, it never has and never will. All the kludges and
> duct tape in the world won't fix what is broken here.
> 
> I read my IETF mail through gmail because, well its easiest to do that. And
> I have roughly 10GB of mailing list traffic. Most of which is probably
> copied 50-100 times or more.

I disgree.  I have about 260G of mailing list, newsgroup, and RSS traffic
(both of which latter two can be coerced into mbox format, making it
possible to use the same tools on them) and I have no problem managing
it, searching it, using it.  I think it's just a matter of selecting
the right approach, including the right tools.

Mailing lists are clearly the best mechanism for group collaboration
that we have (I'll enumerate my reasons for that if necessary) and it
would be a major strategic error to move away from because they're not
handled well at the moment by some hastily-deployed technologies that
failed to fully take them into account.

---rsk


From nobody Wed Mar 15 09:16:58 2017
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 8392D1316EF; Wed, 15 Mar 2017 09:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sy2-BJG3Vi0S; Wed, 15 Mar 2017 09:16:55 -0700 (PDT)
Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DF221316DF; Wed, 15 Mar 2017 09:16:55 -0700 (PDT)
Received: by mail-io0-x241.google.com with SMTP id f103so3438980ioi.2; Wed, 15 Mar 2017 09:16:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=k8AKD/ic+Z/Rl8U0gVP1nnucq5l9rr2MKlSwGfLTsH0=; b=L+02JaxDGNwyTEPtAR5YJGlcwEjNeOq4F7lKI9CtiT7RYy2DhPHqT4YEAevKybq5Qm SeCGmHCBc5xEcjBoA0o9fm328dHfqw1m/rVD8c4A+7CnCUrkhVn596GneTgp8X0KNcpT 2VoHHz2yRCCQD8KXWiAVBkWKemvRy7rDxqYoDqSgCRiO8bOjcqQMZMcHVnyMpMN7Jd5K QmGZxWSAP/r0W61PQavrb2Iu/j4fWLGjldUpcDclaMw11I4RoPq/HGANwa+9Pj7h09KX eToOr6CxnQxgjKiIE+oDsQ0+mPFM0jEhclR2eK7OdXXRXIBMcNWZqiwCbFWZqpeccDdn IAjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=k8AKD/ic+Z/Rl8U0gVP1nnucq5l9rr2MKlSwGfLTsH0=; b=uTPRur52hE548gI8sQDVfBREdDprAfK6hJFaKBZlfeM9YjbfbgpyYxU5jSBchuyzMA NP+BfrYOPcjD/gznTEHr4xTYTAAgmhAKDKvnrRqtu9i7F7W5IxmmolIfxGmL6iNbUx/5 C0/M77NBoj/IlPEJSPk7q7PwgxwLX04+lQLtwcNu8PkKDM91ceDeqXsGY9FQ9q3xM6Kf 01SR09JKeBOFoBdej4s5cSOPcrnOSUFneg6urJ1dJSeio9T5vDUFgAu6j7U6MNdDaZSY ocOITb+RiKbaRUck2tkO12qCLIpFFyi3b/412Zx8WS2VhgOrjgmD+3hEf/bClZxAVWzg VXag==
X-Gm-Message-State: AFeK/H3k+w0jZccnlMXkvqq3+FsKpY5p7DWI3VJ1bkRrPRCFivSaNuXuFl54+bhmED+zLw==
X-Received: by 10.107.135.136 with SMTP id r8mr5728744ioi.36.1489594609564; Wed, 15 Mar 2017 09:16:49 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id b126sm1666577ioa.55.2017.03.15.09.16.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Mar 2017 09:16:49 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com>
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com>
Date: Thu, 16 Mar 2017 05:16:55 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DC_CVFrs7M0dLdWfJSgrqVqti1A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 16:16:57 -0000

Stefano,
On 16/03/2017 04:55, Stefano Previdi (sprevidi) wrote:
...
> In the mean time, I think it is way too premature to come to conclusion on what text should be used for RFC2460bis and I recommend that the current text is left unchanged until we figured out what to do with EH insertion.

I believe that we have figured it out: extension header insertion is harmful to Internet interoperability.

I fully agree with Suresh's understanding of the rough consensus.

   Brian


From nobody Wed Mar 15 09:21:49 2017
Return-Path: <tim.chown@jisc.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 06F1F13170A for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 09:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xhMgvyrboCx7 for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 09:21:45 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EF4D131708 for <ietf@ietf.org>; Wed, 15 Mar 2017 09:21:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1489594903; bh=o6YtjseSoo95+W9dh710zYYYwlt7CAxZ8M4C/3JBMoA=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To:Content-ID:MIME-Version:Content-Type:Content-Transfer-Encoding; b=hnWd0gs4R5acIiz5CVi/qW8PCQJF81oJ0qXmAVB/9NJFNAzHnhN927m2z0iwGzr5PVPhAYg7LLqhSbkURP2BB+EafK7qawKfasS1phoRgr3EnMOlZhBiXgBZ+xOYUQ2ECFTL5HQPDYQXpQoJnnXHrt0JCC+lH8K3WrNwvkUjQ4I=
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-he1eur02lp0184.outbound.protection.outlook.com [213.199.180.184]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-99-63W5PtfBMreF5JfEyzGsNQ-1; Wed, 15 Mar 2017 16:21:36 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1138.eurprd07.prod.outlook.com (10.163.188.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.977.5; Wed, 15 Mar 2017 16:21:34 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::59f7:b9fe:6ca:9476]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::59f7:b9fe:6ca:9476%14]) with mapi id 15.01.0977.010; Wed, 15 Mar 2017 16:21:34 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "Suresh Krishnan" <suresh.krishnan@ericsson.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv71giYAPcbUKK9ywM4gSjvqGWDpMAgAAGIICAAAFLgA==
Date: Wed, 15 Mar 2017 16:21:34 +0000
Message-ID: <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com>
In-Reply-To: <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [194.82.140.195]
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1138; 7:2IW+zL5ZcNcooPBquPK05yQrSXMjt4XyZoQ8MLfkMu+O57L1RHH7A0SW8toSxVkb6BviJ+khxXsP+frLcDaDsfCBGR1ZqKN1Mx1e72KqN/4LVPB6IL9BCi583l1IrR5WoUC25K/3blG3HSqjdFtMyAhiqyDBMVcEEtRK0x3Z2szbT4wHIRR+CvDkg9uMbBx0eKMyEhFgLTVUwBIUFVxJrGjJn38wG2h/AxCmMTBNsju/OWOObX0fa7iemVKZ2xxCkEGmKKiNjh23HxelriO8iahTedCPasf27TOjx9T4LScdLt1XLKn688c6+yu0j654j9fnajXaayeZVzLEEAT89Q==; 20:XC9fMcbLLLEvhozQPQruaGBja7QpomRZub1P/h0PZebSDew0NTBqmkKLhjwKGGiOba8kqKE1kzP/KuuQq3cdYHWikRTJG9Ozw0FPOVGVEdv29BBPkyzUDLH6gYMdIdXL79iZ1tFpA0rId1YA9FCUGirmJ+afysYd2xr/c4Mya8I=
x-ms-office365-filtering-correlation-id: 38f7abdc-7212-42b3-1ac6-08d46bbf5914
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254022); SRVR:AM3PR07MB1138; 
x-microsoft-antispam-prvs: <AM3PR07MB1138E0E00B2F7664202CFECED6270@AM3PR07MB1138.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123564025)(20161123562025)(20161123555025)(20161123560025)(20161123558025)(6072148); SRVR:AM3PR07MB1138; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1138; 
x-forefront-prvs: 02475B2A01
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39450400003)(24454002)(6246003)(74482002)(6512007)(33656002)(230783001)(99286003)(86362001)(76176999)(4326008)(53936002)(39060400002)(110136004)(38730400002)(2900100001)(229853002)(2906002)(7736002)(54906002)(50986999)(6486002)(6506006)(5250100002)(189998001)(3660700001)(42882006)(6436002)(3280700002)(66066001)(82746002)(2950100002)(83716003)(5660300001)(36756003)(6916009)(53546007)(57306001)(81166006)(8676002)(8936002)(3846002)(102836003)(6116002)(50226002)(305945005)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1138; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <D4186B0CE530E349BF20820C8EE606F2@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2017 16:21:34.2276 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1138
X-MC-Unique: 63W5PtfBMreF5JfEyzGsNQ-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ltI3zc-yQ_JlGBV9x4rKOeQ7Qdc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 16:21:48 -0000

SGksDQoNCj4gT24gMTUgTWFyIDIwMTcsIGF0IDE2OjE2LCBCcmlhbiBFIENhcnBlbnRlciA8YnJp
YW4uZS5jYXJwZW50ZXJAZ21haWwuY29tPiB3cm90ZToNCj4gDQo+IFN0ZWZhbm8sDQo+IE9uIDE2
LzAzLzIwMTcgMDQ6NTUsIFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIHdyb3RlOg0KPiAuLi4N
Cj4+IEluIHRoZSBtZWFuIHRpbWUsIEkgdGhpbmsgaXQgaXMgd2F5IHRvbyBwcmVtYXR1cmUgdG8g
Y29tZSB0byBjb25jbHVzaW9uIG9uIHdoYXQgdGV4dCBzaG91bGQgYmUgdXNlZCBmb3IgUkZDMjQ2
MGJpcyBhbmQgSSByZWNvbW1lbmQgdGhhdCB0aGUgY3VycmVudCB0ZXh0IGlzIGxlZnQgdW5jaGFu
Z2VkIHVudGlsIHdlIGZpZ3VyZWQgb3V0IHdoYXQgdG8gZG8gd2l0aCBFSCBpbnNlcnRpb24uDQo+
IA0KPiBJIGJlbGlldmUgdGhhdCB3ZSBoYXZlIGZpZ3VyZWQgaXQgb3V0OiBleHRlbnNpb24gaGVh
ZGVyIGluc2VydGlvbiBpcyBoYXJtZnVsIHRvIEludGVybmV0IGludGVyb3BlcmFiaWxpdHkuDQo+
IA0KPiBJIGZ1bGx5IGFncmVlIHdpdGggU3VyZXNoJ3MgdW5kZXJzdGFuZGluZyBvZiB0aGUgcm91
Z2ggY29uc2Vuc3VzLg0KDQpJIGFsc28gYWdyZWUgd2l0aCBTdXJlc2jigJlzIGFwcHJhaXNhbC4g
DQoNClRpbQ==


From nobody Wed Mar 15 09:32:26 2017
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B3A131710; Wed, 15 Mar 2017 09:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42t7DUzo6sB8; Wed, 15 Mar 2017 09:32:10 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDE221316A1; Wed, 15 Mar 2017 09:32:08 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id r136so11539630vke.1; Wed, 15 Mar 2017 09:32:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EMntoE2nKmGHrWGxrIudCapKucB3AOF2JY9i1VNKD+w=; b=uumxWlB+bWcLcreVO4JWCYjuWAmAc9J5wVnvIxpKeBr5M0kaAust2TUoEVlWL7UzIt Y9pyxf46BZqOVro59BOuGD4Xw6uG73wzbRNN0EC6GI1TYDJEkWIRS1z7mthP8l2NCON+ /tDjtFl9KGx53OubOv0uMICQH3y1QUkKoF9SmtUZKvObwD+giWc3/R8nMmRyiLSGS7k6 eFsRr0jItmlBkpnu3A6ZXm1ESt2P2EN6Ll83H3yExzb+99t3SeDAm9QnAie/76ziBOZ5 x9wIx2ORwMzIOyMn56rPK95tioRg4Wv5yjgc0TUpWKFXbQ19adimBTP0zgYMV+442RkH i+Pw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EMntoE2nKmGHrWGxrIudCapKucB3AOF2JY9i1VNKD+w=; b=bfubUaan8K/IN6E//Xj3hTVJSb7mzn1lkNsBb5KAxSxQV/OcMxP5DsJTj6LMj9qnAV tCm2mzyrtQS12u6pHCpKy7epfm9ICeXj0iy4afJLZLtbu3R7fOxMJCRe3gF9eWb0AWsa Zo8n9AZGENdkAoqu6PWj2M7xmB/enccFHbnw4HUdPfFEcxg7TC2wTEsyQqKj0KHZJSkK RcQJ6OugtB8lf3jbxDdxmtZJ7xS2qmrswtq/+4iR8s5w2XB5auzTAn085xyaJKxq9Sg8 ng62ExrZn5/tBUFZQ+hhkkGxWNVycvoV7VmTBb0AuTbmbgleeGn7KMQdjoy6oDFNUjhw 1+6g==
X-Gm-Message-State: AFeK/H3i+3RSgrUJnFMT/eVbqhFWJLXAIxMXpRH8Ba26Gx3nr6zUEQ5hX7JBmCotJFcrctJcKjRww3lWfIt6PA==
X-Received: by 10.31.72.67 with SMTP id v64mr1395895vka.37.1489595527979; Wed, 15 Mar 2017 09:32:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.85.130 with HTTP; Wed, 15 Mar 2017 09:32:07 -0700 (PDT)
In-Reply-To: <EMEW3|3d7f89a896697bb5f0f1b013499e85eey2EAWG03tjc|ecs.soton.ac.uk|C77E403A-4902-4ED0-ADF2-879FC08C6C16@ecs.soton.ac.uk>
References: <C77E403A-4902-4ED0-ADF2-879FC08C6C16@ecs.soton.ac.uk> <148951856846.2289.9860804626640095928@ietfa.amsl.com> <EMEW3|3d7f89a896697bb5f0f1b013499e85eey2EAWG03tjc|ecs.soton.ac.uk|C77E403A-4902-4ED0-ADF2-879FC08C6C16@ecs.soton.ac.uk>
From: Ines  Robles <mariainesrobles@googlemail.com>
Date: Wed, 15 Mar 2017 13:32:07 -0300
Message-ID: <CAP+sJUfEUNXrbhqsvAfTNTL-fvYhMEPcAxDXoTfVKPii4bXaMw@mail.gmail.com>
Subject: Re: [IoT-DIR] Review of draft-ietf-dnssd-mdns-dns-interop-04
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: Ines Robles <maria.ines.robles@ericsson.com>, Ralph Droms <rdroms.ietf@gmail.com>,  dnssd@ietf.org, ietf <ietf@ietf.org>, "iot-dir@ietf.org" <Iot-dir@ietf.org>,  draft-ietf-dnssd-mdns-dns-interop.all@ietf.org,  peter van der Stok <stokcons@xs4all.nl>
Content-Type: multipart/alternative; boundary=001a114db19e4dea24054ac77c0b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2bq6_-GXeNGD2D5u9sXoZPEAicw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 16:32:14 -0000

--001a114db19e4dea24054ac77c0b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Tim,

We (Peter van der Stok and me ) are willing to present it.

How much time would we have? We might need 10 min, but we can adapt it to
less time though, since the agenda is already full.

Thank you,

Peter and Ines.

2017-03-15 7:32 GMT-03:00 Tim Chown <tjc@ecs.soton.ac.uk>:

> Hi Ines,
>
> Many thanks for this review.
>
> As you=E2=80=99ve implictly noted, the focus of draft-ietf-dnssd-mdns-dns=
-interop-04
> is interoperability of the labels used, primarily between unicast and
> multicast DNS.
>
> You raise some very good points about the efficiency of mDNS/DNS-SD,
> particularly in constrained environments. This isn=E2=80=99t something we=
=E2=80=99ve
> covered in any detail as yet in the dnssd WG, aside from
> draft-aggarwal-dnssd-optimize-query-00 being presented a few IETFs ago,
> but DNS-SD in mesh networks is in our charter (
> https://datatracker.ietf.org/wg/dnssd/charter/). To date we=E2=80=99ve fo=
cused on
> enterprise and home networks as managed and unmanaged multi-link IP
> environments.
>
> It would be useful to explore potential issues with DNS-SD in constrained
> environments further. Is there someone who might be at Chicago and able t=
o
> raise this issue in our meeting, briefly?  We could make some time for th=
is
> topic. That might then help seed further work.
>
> Tim (dnssd co-chair)
>
> On 14 Mar 2017, at 19:09, Ines Robles <maria.ines.robles@ericsson.com>
> wrote:
>
> Reviewer: Ines Robles
> Review result: Ready
>
> Hi,
>
> I have read the draft. The document provides a description of the
> requirements for a profile for label interoperation.
>
> In IoT, networks and nodes, in general, have constrained resources.
> Related to the topic of the draft in review, several aspects should be
> considered from IoT point of view, such as:
>
> - Type of devices that have insufficient resources to run DNS-SD/mDNS
> [1] (Some running code [7]). The work in [2][3] depicts an
> autoconfiguration scheme for the global (or local) DNS names of IoT
> devices. It uses an specific DNS Name Format
> (unique_id.object_identifier.OID.domain_name).
>
> - Resource Directory (RD): A web entity that stores information about
> web resources and implements the REST interfaces for registration and
> lookup of resources. A mapping between CoRE Link Format attributes and
> DNS-Based Service Discovery aspects (mapping ins to <Instance>,
> Mapping rt to <ServiceType> and Domain mapping) is descripted in
> version 9 of RD draft [4].
>
> - Optimization of DNS-SD: A proposal for an optimization of DNS-SD
> query using TXT records is descripted in [5].
>
> - DNS Message Compression [6], implemented in uBonjour Contiki.
>
> Thus, new work (or updates) is needed to set the requirements for
> label interoperation in this type of environments. I understand that
> this is out of scope of dns-interop draft. So, what about to add in
> the dns-interop draft some text like:
>
> "Related to constrained environments, work is ongoing such as
> autoconfiguration[2], optimization of DNS-SD [5] and DNS message
> compression [6] that would help to get an efficient selection of
> labels for DNS and other resolution systems."
>
> Hope that it helps.
>
> Cheers,
>
> Ines.
>
>
> [1] https://www.ietf.org/mail-archive/web/dnssd/current/msg00589.html
> [2] https://tools.ietf.org/html/draft-jeong-its-iot-dns-autoconf-01
> [3] Lee, Sejun, Jaehoon Paul Jeong, and Jung-Soo Park. "DNSNA: DNS
> name autoconfiguration for Internet of Things devices." Advanced
> Communication Technology (ICACT), 2016 18th International Conference
> on. IEEE, 2016.
> [4] https://tools.ietf.org/html/draft-ietf-core-resource-directory-09
> [5]
> https://tools.ietf.org/html/draft-aggarwal-dnssd-optimize-query-00
> [6] Klauck, Ronny, and Michael Kirsche. "Enhanced DNS message
> compression-Optimizing mDNS/DNS-SD for the use in 6LoWPANs." Pervasive
> Computing and Communications Workshops (PERCOM Workshops), 2013 IEEE
> International Conference on. IEEE, 2013.
> [7] https://github.com/Agile-IoT/awesome-open-iot#mdns--bonjour
>
>
>
> _______________________________________________
> IoT-DIR mailing list
> IoT-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/iot-dir
>
>

--001a114db19e4dea24054ac77c0b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Tim,<div><br></div><div><div>We (Peter van der Stok and=
 me ) are willing to present it.<br></div><div><br></div><div>How much time=
 would we have? We might need 10 min, but we can adapt it to less time thou=
gh, since the agenda is already full.</div><div><br></div><div>Thank you,</=
div><div><br></div><div>Peter and Ines.</div></div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">2017-03-15 7:32 GMT-03:00 Tim Chown <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank">t=
jc@ecs.soton.ac.uk</a>&gt;</span>:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div s=
tyle=3D"word-wrap:break-word">Hi Ines,<div><br></div><div>Many thanks for t=
his review.</div><div><br></div><div>As you=E2=80=99ve implictly noted, the=
 focus of=C2=A0draft-ietf-dnssd-mdns-dns-<wbr>interop-04 is interoperabilit=
y of the labels used, primarily between unicast and multicast DNS.</div><di=
v><br></div><div>You raise some very good points about the efficiency of mD=
NS/DNS-SD, particularly in constrained environments. This isn=E2=80=99t som=
ething we=E2=80=99ve covered in any detail as yet in the dnssd WG, aside fr=
om draft-aggarwal-dnssd-optimize-<wbr>query-00 being presented a few IETFs =
ago, but DNS-SD in mesh networks is in our charter (<a href=3D"https://data=
tracker.ietf.org/wg/dnssd/charter/" target=3D"_blank">https://datatracker.i=
etf.org/<wbr>wg/dnssd/charter/</a>). To date we=E2=80=99ve focused on enter=
prise and home networks as managed and unmanaged multi-link IP environments=
.=C2=A0</div><div><br></div><div>It would be useful to explore potential is=
sues with DNS-SD in constrained environments further. Is there someone who =
might be at Chicago and able to raise this issue in our meeting, briefly?=
=C2=A0 We could make some time for this topic. That might then help seed fu=
rther work.</div><div><br><div>
<div>Tim (dnssd co-chair)</div><div><br></div></div><div><div class=3D"h5">=
<div><blockquote type=3D"cite"><div>On 14 Mar 2017, at 19:09, Ines Robles &=
lt;<a href=3D"mailto:maria.ines.robles@ericsson.com" target=3D"_blank">mari=
a.ines.robles@ericsson.<wbr>com</a>&gt; wrote:</div><br class=3D"m_-1436081=
088930297685Apple-interchange-newline"><div><div>Reviewer: Ines Robles<br>R=
eview result: Ready<br><br>Hi,<br><br>I have read the draft. The document p=
rovides a description of the<br>requirements for a profile for label intero=
peration.<br><br>In IoT, networks and nodes, in general, have constrained r=
esources.<br>Related to the topic of the draft in review, several aspects s=
hould be<br>considered from IoT point of view, such as:<br><br>- Type of de=
vices that have insufficient resources to run DNS-SD/mDNS<br>[1] (Some runn=
ing code [7]). The work in [2][3] depicts an<br>autoconfiguration scheme fo=
r the global (or local) DNS names of IoT<br>devices. It uses an specific DN=
S Name Format<br>(unique_id.object_identifier.<wbr>OID.domain_name).<br><br=
>- Resource Directory (RD): A web entity that stores information about<br>w=
eb resources and implements the REST interfaces for registration and<br>loo=
kup of resources. A mapping between CoRE Link Format attributes and<br>DNS-=
Based Service Discovery aspects (mapping ins to &lt;Instance&gt;,<br>Mappin=
g rt to &lt;ServiceType&gt; and Domain mapping) is descripted in<br>version=
 9 of RD draft [4]. <br><br>- Optimization of DNS-SD: A proposal for an opt=
imization of DNS-SD<br>query using TXT records is descripted in [5].<br><br=
>- DNS Message Compression [6], implemented in uBonjour Contiki.<br><br>Thu=
s, new work (or updates) is needed to set the requirements for<br>label int=
eroperation in this type of environments. I understand that<br>this is out =
of scope of dns-interop draft. So, what about to add in<br>the dns-interop =
draft some text like:<br><br>&quot;Related to constrained environments, wor=
k is ongoing such as<br>autoconfiguration[2], optimization of DNS-SD [5] an=
d DNS message<br>compression [6] that would help to get an efficient select=
ion of<br>labels for DNS and other resolution systems.&quot;<br><br>Hope th=
at it helps.<br><br>Cheers,<br><br>Ines.<br><br><br>[1] <a href=3D"https://=
www.ietf.org/mail-archive/web/dnssd/current/msg00589.html" target=3D"_blank=
">https://www.ietf.org/mail-<wbr>archive/web/dnssd/current/<wbr>msg00589.ht=
ml</a><br>[2] <a href=3D"https://tools.ietf.org/html/draft-jeong-its-iot-dn=
s-autoconf-01" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-jeo=
ng-its-iot-dns-<wbr>autoconf-01</a><br>[3] Lee, Sejun, Jaehoon Paul Jeong, =
and Jung-Soo Park. &quot;DNSNA: DNS<br>name autoconfiguration for Internet =
of Things devices.&quot; Advanced<br>Communication Technology (ICACT), 2016=
 18th International Conference<br>on. IEEE, 2016.<br>[4] <a href=3D"https:/=
/tools.ietf.org/html/draft-ietf-core-resource-directory-09" target=3D"_blan=
k">https://tools.ietf.org/html/<wbr>draft-ietf-core-resource-<wbr>directory=
-09</a><br>[5]<br><a href=3D"https://tools.ietf.org/html/draft-aggarwal-dns=
sd-optimize-query-00" target=3D"_blank">https://tools.ietf.org/html/<wbr>dr=
aft-aggarwal-dnssd-optimize-<wbr>query-00</a><br>[6] Klauck, Ronny, and Mic=
hael Kirsche. &quot;Enhanced DNS message<br>compression-Optimizing mDNS/DNS=
-SD for the use in 6LoWPANs.&quot; Pervasive<br>Computing and Communication=
s Workshops (PERCOM Workshops), 2013 IEEE<br>International Conference on. I=
EEE, 2013.<br>[7] <a href=3D"https://github.com/Agile-IoT/awesome-open-iot#=
mdns--bonjour" target=3D"_blank">https://github.com/Agile-IoT/<wbr>awesome-=
open-iot#mdns--bonjour</a><br><br></div></div></blockquote></div><br></div>=
</div></div></div><br>______________________________<wbr>_________________<=
br>
IoT-DIR mailing list<br>
<a href=3D"mailto:IoT-DIR@ietf.org">IoT-DIR@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/iot-dir" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/iot-dir</a><=
br>
<br></blockquote></div><br></div></div>

--001a114db19e4dea24054ac77c0b--


From nobody Wed Mar 15 09:33:39 2017
Return-Path: <John_Leddy@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 E27BF131710; Wed, 15 Mar 2017 09:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJihrUvtmIRy; Wed, 15 Mar 2017 09:33:36 -0700 (PDT)
Received: from vaadcmhout01.cable.comcast.com (vaadcmhout01.cable.comcast.com [96.114.28.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01A5E1316A1; Wed, 15 Mar 2017 09:33:35 -0700 (PDT)
X-AuditID: 60721c4b-957ff700000006b0-02-58c96cdd6ec3
Received: from VAADCEX42.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by  (SMTP Gateway) with SMTP id B7.A1.01712.DDC69C85; Wed, 15 Mar 2017 12:33:34 -0400 (EDT)
Received: from VAADCEX41.cable.comcast.com (147.191.103.218) by VAADCEX42.cable.comcast.com (147.191.103.219) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 15 Mar 2017 12:33:32 -0400
Received: from VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268]) by VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268%19]) with mapi id 15.00.1263.000; Wed, 15 Mar 2017 12:33:32 -0400
From: "Leddy, John" <John_Leddy@comcast.com>
To: Tim Chown <Tim.Chown@jisc.ac.uk>, Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnaSAxRLtjcu1EUaNXmYCyEu8g6GWVuWAgAABTAD//8BKAA==
Date: Wed, 15 Mar 2017 16:33:32 +0000
Message-ID: <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk>
In-Reply-To: <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.115.73.253]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6B5658A0B408DE478EE7BA7F06511FEB@cable.comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBIsWRmVeSWpSXmKPExsWSUOxpoXs/52SEwYSJTBZtF/cxWbx6e43N 4tnG+SwWL8++Z7JYv/sRk0Xfz8dsDmweU35vZPXYOesuu8eSJT+ZPFb+vsIWwBLFZZOSmpNZ llqkb5fAlbHv2hPGglVcFYfnfWFrYOzg6mLk5JAQMJHYt/kEWxcjF4eQwEwmiR/rvzJCOIcY JdpaW6AyJxklHmx4zgbSwiagIzFj2jVWEFtEIFzi8ad2ZpAiZoETjBLLJu1nB0kIC3hITNp0 jQWiyFNi3cbDULaTxOQ3+8BqWARUJVbOvwdm8wq4SNx71QNWIyRwk1Hi91oJEJtTwE5i/qdf TCA2o4CYxPdTa8BsZgFxiVtP5jNB/CAgsWTPeWYIW1Ti5eN/YMeJCuhJPLx3kxUiriNx9voT RgjbQGLr0n0sELaixL4PK4B6OYBmakqs36UPMd5B4vCPB6wQtqLElO6HUGcKSpyc+QSqVVzi 8JEdrBMYpWchuWgWwqRZSCbNQjJpFpJJCxhZVzHKlSUmpiTnZuSXlhgY6iUnJuWk6iXn5yYn FpeA6E2MoPRQJOO9g3HdT/dDjAIcjEo8vN9DTkYIsSaWFVfmAqOKg1lJhLctCyjEm5JYWZVa lB9fVJqTWnyIUZqDRUmc95LI6gghgfTEktTs1NSC1CKYLBMHp1QDoxK39Q/zFVeWhxt0L16+ 1rd+wpvCw/z/7NebrTD85VG2IJKnPXfaK7UQA67/qbUcPVvMStcvzmf5JPropLp3Jc8FYYfu TqVI98Q9/jNL2X4lue/Y+dvDfQKzr3WF6KmOUGXryQ8YYuceZ3IWnGTl1sO49qzTBK+lSoz7 eU7O9+zhivTxeOyuxFKckWioxVxUnAgA0wR6fAsDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bwBKaq0nfVlfz3YU43d-DoiGxGU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 16:33:38 -0000

RG9lcyB0aGlzIG1lYW4gdGhhdCBvbmx5IG1pZGRsZSBib3hlcywgbm90IGNvdmVyZWQgYnkgdGhl
IGFyY2hpdGVjdHVyZSBjb3VsZCBpbnNlcnQgYW4gZXh0ZW5zaW9uIGhlYWRlciBmb3IgdXNlIHdp
dGhpbiB0aGUgZG9tYWluPw0KDQpKb2huDQoNCk9uIDMvMTUvMTcsIDEyOjIxIFBNLCAiaWV0ZiBv
biBiZWhhbGYgb2YgVGltIENob3duIiA8aWV0Zi1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBv
ZiBUaW0uQ2hvd25AamlzYy5hYy51az4gd3JvdGU6DQoNCiAgICBIaSwNCiAgICANCiAgICA+IE9u
IDE1IE1hciAyMDE3LCBhdCAxNjoxNiwgQnJpYW4gRSBDYXJwZW50ZXIgPGJyaWFuLmUuY2FycGVu
dGVyQGdtYWlsLmNvbT4gd3JvdGU6DQogICAgPiANCiAgICA+IFN0ZWZhbm8sDQogICAgPiBPbiAx
Ni8wMy8yMDE3IDA0OjU1LCBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKSB3cm90ZToNCiAgICA+
IC4uLg0KICAgID4+IEluIHRoZSBtZWFuIHRpbWUsIEkgdGhpbmsgaXQgaXMgd2F5IHRvbyBwcmVt
YXR1cmUgdG8gY29tZSB0byBjb25jbHVzaW9uIG9uIHdoYXQgdGV4dCBzaG91bGQgYmUgdXNlZCBm
b3IgUkZDMjQ2MGJpcyBhbmQgSSByZWNvbW1lbmQgdGhhdCB0aGUgY3VycmVudCB0ZXh0IGlzIGxl
ZnQgdW5jaGFuZ2VkIHVudGlsIHdlIGZpZ3VyZWQgb3V0IHdoYXQgdG8gZG8gd2l0aCBFSCBpbnNl
cnRpb24uDQogICAgPiANCiAgICA+IEkgYmVsaWV2ZSB0aGF0IHdlIGhhdmUgZmlndXJlZCBpdCBv
dXQ6IGV4dGVuc2lvbiBoZWFkZXIgaW5zZXJ0aW9uIGlzIGhhcm1mdWwgdG8gSW50ZXJuZXQgaW50
ZXJvcGVyYWJpbGl0eS4NCiAgICA+IA0KICAgID4gSSBmdWxseSBhZ3JlZSB3aXRoIFN1cmVzaCdz
IHVuZGVyc3RhbmRpbmcgb2YgdGhlIHJvdWdoIGNvbnNlbnN1cy4NCiAgICANCiAgICBJIGFsc28g
YWdyZWUgd2l0aCBTdXJlc2jigJlzIGFwcHJhaXNhbC4gDQogICAgDQogICAgVGltDQoNCg==


From nobody Wed Mar 15 09:47:11 2017
Return-Path: <dafranke@akamai.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BAD3013171A; Wed, 15 Mar 2017 09:47:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Daniel Franke <dafranke@akamai.com>
To: <secdir@ietf.org>
Cc: draft-ietf-pce-stateful-sync-optimizations.all@ietf.org, pce@ietf.org, ietf@ietf.org
Subject: Review of draft-ietf-pce-stateful-sync-optimizations-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148959642972.14125.7359898996904258228@ietfa.amsl.com>
Date: Wed, 15 Mar 2017 09:47:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mGlG64mKzvioIpEZJ98lr-Zj3Cg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 16:47:10 -0000

Reviewer: Daniel Franke
Review result: Has Issues

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

I believe this document is READY WITH a minor ISSUE addressed below.
The Security Considerations section of this document, along with its
companion draft-ietf-pce-stateful-pce-18, appears to do a thorough job
of enumerating the ways in which the newly-introduced message types
can contribute to the ability of misbehaving PCCs and PCEs to disrupt
each other, with consequences that generally strike me as acceptable.
It duly recommends that PCEP be run over an authenticated channel to
prevent these messages from being spoofed by a third party.

I am unsure how this final recommendation is going to be implemented
in practice. RFC 5440 characterizes channel security for PCEP as a
work-in-progress as of 2009, and I lack sufficient familiarity with
this area to know if the status quo has improved since then in
practice. The TCP authentication option, cited in RFC 5440 as WIP, is
now RFC 5925, but I don't know whether anyone actually uses it for
this application. TLS is mentioned as another alternative, but
existing standards documents give insufficient instruction on how to
implement this interoperably, since there is no mention of port
allocations, a STARTTLS scheme, an ALPN identification sequence, or
anything else that would explain how to go about initiating the TLS
session. It looks like draft-ietf-pce-pceps intends to rectify this.

Addressing whatever deficiencies exist in PCEP security mechanisms
obviously falls well outside the scope of this particular document to
address. Even if the administrator fails to provide channel security
for PCEP as recommended, adding support for stateful sync
optimizations will not leave the network meaningfully worse-off than
it was already. However -- and here's the ISSUE -- as Alvaro Retana
already sort of touched on, the introduction of the Speaker Entity ID
TLV means that implementation of stateful sync optimizations can't be
entirely agnostic with respect to the choice of channel security
mechanism. Implementations need to verify that the Speaker Entity ID
is consistent with the cryptographic identity of the channel peer in
order to prevent one PCC from spoofing the identity of another. Until
PCEP channel security matures a bit I'm not how much concrete advice
we can give implementers on how to do this properly, but somewhere in
the document there should at least be an observation that this check
should be present.

I also second Retana's desire for greater consistency between this
document, draft-ietf-pce-stateful-pce, and RFC 5440 as to which
channel security mechanisms are recommended and/or required.

PS - sorry about the last minute review.


From nobody Wed Mar 15 10:16:34 2017
Return-Path: <jinmei.tatuya@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 6C27D13172A; Wed, 15 Mar 2017 10:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CuDOGKnRKCOb; Wed, 15 Mar 2017 10:16:24 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7375131728; Wed, 15 Mar 2017 10:16:24 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id 1so18521323qkl.3; Wed, 15 Mar 2017 10:16:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=Hx+7cXVMfWsVpJoyiKAvDjfdqJ1yxC0flytf4nDJgVk=; b=RQYA61w+SPnbOd8gDM74a2DKWuqUx9myV6Sm3S2SL1Xr+JOJYCIytXK1j6E7wvemuG 8XhsPu/F0L37ogjV/NDkxqYxWCd7/ye9ogSOUcyt958varwBWQmnZ70thjmI/G7RjG5o gNAm5VhfmI7s4VC8HsSTcjR8hRxPVo0UdY1RgidJUZG6ricgBEU+a1jrmeWlddbUroxQ IWI2caD3m+i3D9M6XwWEZMYCCIFNwhFLQ5uTB1p2P/nUts3cDQ+rjxrawld9dPgGHIVK mEBU16DGlSKHtyl+RTBYZXtLiG0t7ctds3I15+MJrEY+dRiNvSu/gzFqsFs769soOkTh 4UCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=Hx+7cXVMfWsVpJoyiKAvDjfdqJ1yxC0flytf4nDJgVk=; b=bqyaCKfIweBnSCIUo1r+4ZShXyUIoC2WXvH/FiURdhyqw07cpuJPixq6UNyKBCTTm2 Fy8bvn4Kw39v+HZ4/UhEw69NDZ//YGYwDqtro6csfu+cqrDLySywO7I1hm4SXV8Wqx2j +nCcIjuNmRtDHiOnFZ8CKp5ZXiDOK5JQI8LOyTvQu6Xfjnjgd+Qw91yv8inxNt85fS7/ q82vPVWOzHjZkWmThwVLl/5oQSvcZLcnRegkPWBSwVFCyOze1V9EIpfJmQRoKBMlz6Jm ikQmllIzwBlLtYHvUQUjcFcNOKnndOoDYCksQyBY9GxYk0fI+TmJE7iqqrwYW9ZCGKsY 33Qg==
X-Gm-Message-State: AFeK/H3DQzd1lUzNVDtLMNVR9QJiJygqWe9YuUWPbLnme82zBPjPGJIcoj1pQYVougk/v8Z94qcWP0CpfUpkfA==
X-Received: by 10.55.146.135 with SMTP id u129mr3716542qkd.219.1489598183727;  Wed, 15 Mar 2017 10:16:23 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.61.204 with HTTP; Wed, 15 Mar 2017 10:16:23 -0700 (PDT)
In-Reply-To: <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Wed, 15 Mar 2017 10:16:23 -0700
X-Google-Sender-Auth: cRRNJV4d-w5NpKk5sr53nQgZm8Q
Message-ID: <CAJE_bqe7jxywepBahnmRPzm+oHY32+80bujGktxsieLdk+CRYQ@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>,  Suresh Krishnan <suresh.krishnan@ericsson.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AhO1h1coUPXRbcCvlPMDNYT_sVc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 17:16:26 -0000

At Thu, 16 Mar 2017 05:16:55 +1300,
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> > In the mean time, I think it is way too premature to come to conclusion=
 on what text should be used for RFC2460bis and I recommend that the curren=
t text is left unchanged until we figured out what to do with EH insertion.
>
> I believe that we have figured it out: extension header insertion is harm=
ful to Internet interoperability.
>
> I fully agree with Suresh's understanding of the rough consensus.

I also support Suresh's proposal.

BTW,

At Wed, 15 Mar 2017 15:55:00 +0000,
"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> wrote:

>> Originally RFC2460 stated that only the source of the packet is
>> entitled to add an EH. Now we=E2=80=99re going to propose that the sourc=
e
>> =E2=80=9Cdomain=E2=80=9D of the packet is allowed to insert EHs. [...]
>>
>> In order to have a more productive discussion, we are writing a
>> draft on header insertion that will be submitted as soon as the
>> windows re-open (during ietf week).

IMHO this plan explains exactly why we rather need to make it more
explicit in rfc2460bis that this version of spec does not assume EH to
be inserted or deleted except at the source node (not "domain").  I'm
totally open to the discussion of possible extensions with the concept
of "source domain".  But it should be fair to say it will take time,
at least for months, and quite likely more than a year.  If we keep
the rfc2460bis text "ambiguous" in the meantime, we'll leave the risk
that it's interpreted more loosely and someone develops an
implementation that violates the assumption more casually.  To me,
it's more responsible to be more explicit in the current specification
to prevent further accidental misunderstanding unless and until we
have the possible revised conditions.

--
JINMEI, Tatuya


From nobody Wed Mar 15 10:58:03 2017
Return-Path: <daniel.voyer@bell.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 3600013175C; Wed, 15 Mar 2017 10:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.697
X-Spam-Level: 
X-Spam-Status: No, score=-4.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q4GJHgzNIybm; Wed, 15 Mar 2017 10:57:58 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93EDC13175A; Wed, 15 Mar 2017 10:57:57 -0700 (PDT)
Received: from [85.158.136.35] by server-5.bemta-5.messagelabs.com id 7D/D7-29481-3A089C85; Wed, 15 Mar 2017 17:57:55 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrJKsWRWlGSWpSXmKPExsXi7PqsVXdxw8k Ig9X35Sxevb3GZvFs43wWi5dn3zNZrN/9iMlixpyf7A6sHlN+b2T1+PX1KpvHkiU/mQKYo1gz 85LyKxJYM6YtXsZa8E6s4vj59cwNjF+Euhg5OSQE/CR6L11j62Lk4hAS2MsoseHEGSYI5wajx PkLM1ghnNOMEuc6pgJlODjYBHQk5ryQB+kWETCVOD/jPDOIzSxwhFGi+bEHiC0s4CExadM1Fo gaT4l1Gw9D2VYSU14eZgWxWQRUJf5t/8kGMpIXKP5zgh1IWEigQGLp7LVg5ZwCthI3p3aBlTM KiEl8P7WGCWKVuMStJ/OZIB4QkFiyB+IECQFRiZeP/7FC2AYSW5fuY4GoN5B4f24+1JnaEssW vgazeQUEJU7OfMICUS8pcXDFDRaIGxQl5t16ywLx+jxGiYlb29ghiuwl/l/6wTiBUWoWkjtmI dkxC8mOWUh2LGBkWcWoUZxaVJZapGtooZdUlJmeUZKbmJmja2hgqpebWlycmJ6ak5hUrJecn7 uJERjlDECwg7Fpu+chRkkOJiVRXpXckxFCfEn5KZUZicUZ8UWlOanFhxhlODiUJHhL64FygkW p6akVaZk5wHQDk5bg4FES4bUHSfMWFyTmFmemQ6ROMSpKifOuBkkIgCQySvPg2mAp7hKjrJQw LyPQIUI8BalFuZklqPKvGMU5GJWEeUNApvBk5pXATX8FtJgJaPHbDydAFpckIqSkGhhNZROYU 1JV78450jDB7cKTSgvPrMvXF4nZ3quzbQ+10q0TO/T848GJZ/LULX7tiKuV/dDvKtG57OtPQb O9N1e9vqrjN1NpWW5FxFWR8v8tz+5P9arvCv8gcm/K0sMbvdyazTZK7pv0cOv0ytxvPfO0uaz yzpdnr5U4//ak9J2iGWYN7GaiO9cpsRRnJBpqMRcVJwIA2EU5Y2wDAAA=
X-Env-Sender: daniel.voyer@bell.ca
X-Msg-Ref: server-14.tower-125.messagelabs.com!1489600671!71930018!6
X-Originating-IP: [67.69.230.133]
X-StarScan-Received: 
X-StarScan-Version: 9.2.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29394 invoked from network); 15 Mar 2017 17:57:55 -0000
Received: from tls.exchange.bell.ca (HELO Tls.exchange.bell.ca) (67.69.230.133) by server-14.tower-125.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 15 Mar 2017 17:57:55 -0000
X-CrossPremisesHeadersFilteredBySendConnector: EX13EDGE02-WYN.bell.corp.bce.ca
Received: from DG2MBX03-WYN.bell.corp.bce.ca (198.235.102.32) by EX13EDGE02-WYN.bell.corp.bce.ca (198.235.68.44) with Microsoft SMTP Server id 15.0.1210.3; Wed, 15 Mar 2017 13:57:31 -0400
Received: from DG2MBX03-WYN.bell.corp.bce.ca (2002:8eb6:1215::8eb6:1215) by DG2MBX03-WYN.bell.corp.bce.ca (2002:8eb6:1215::8eb6:1215) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 15 Mar 2017 13:57:37 -0400
Received: from DG2MBX03-WYN.bell.corp.bce.ca ([fe80::c841:4444:5043:4356]) by DG2MBX03-WYN.bell.corp.bce.ca ([fe80::c841:4444:5043:4356%23]) with mapi id 15.00.1210.000; Wed, 15 Mar 2017 13:57:37 -0400
From: "Voyer, Daniel" <daniel.voyer@bell.ca>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
CC: Suresh Krishnan <suresh.krishnan@ericsson.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv71giYAPcbUKK9ywM4gSjvqGWUaEA///fNVw=
Date: Wed, 15 Mar 2017 17:57:37 +0000
Message-ID: <F067FF8F-0D1D-4590-9618-90FE0706BC24@bell.ca>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com>, <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com>
In-Reply-To: <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Received-SPF: SoftFail (EX13EDGE02-WYN.bell.corp.bce.ca: domain of transitioning daniel.voyer@bell.ca discourages use of 198.235.102.32 as permitted sender)
X-OrganizationHeadersPreserved: EX13EDGE02-WYN.bell.corp.bce.ca
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UTJ0VStvQDtHxvs1nZXLKFru0js>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 17:58:01 -0000

> We do have today use cases where not only the source of a packet should b=
e allowed to insert a header but also the source =93domain=94 of a packet. =
I=92ll try to explain.
>=20
> In a domain controlled by a single organization (typically the set of ASs=
 under control of the same operator) a packet enters at the edge where the =
ingress node applies a policy resulted into an additional outer ipv6 header=
 that may or may not contain an extension header. Bottom line, the outer he=
ader means that now, it is a NEW packet, originated by the ingress node, wi=
th SA/DA representing the nodes that are inside the operator domain. Theref=
ore, we can say that this new packet (formed by an outer header and encapsu=
lated original packet) is now owned by the operator and whatever the operat=
or does with this packet:
>=20
> . The packet MUST leave the operator network in the exact same shape/form=
at as it entered (i.e.: outer encapsulation removed).
> . The outer header MAY change while in transit in the operator=92s domain=
. Moreover, a header MAY be inserted while inside the operator=92s domain (=
knowing that outer header and any other inserted header would be removed at=
 egress). This means that an SRH MAY be inserted at the same time the outer=
 header is added but it can also be that the ingress adds the outer header =
and some other node inserts an SRH (e.g.: fast reroute within operator=92s =
infrastructure).
> . While in transit, the operator network must handle aspects like MTU pro=
perly, taking into account the increased size of the packet.
DV: I concur with this explanation & needs.
>=20
> Originally RFC2460 stated that only the source of the packet is entitled =
to add an EH. Now we=92re going to propose that the source =93domain=94 of =
the packet is allowed to insert EHs. The source domain being the set of nod=
es (including the ingress node adding the outer header) under common admini=
stration. This also implies that when the packet leaves the domain, it must=
 recover its original format/shape.
>=20
> In order to have a more productive discussion, we are writing a draft on =
header insertion that will be submitted as soon as the windows re-open (dur=
ing ietf week).
>=20
> In the mean time, I think it is way too premature to come to conclusion o=
n what text should be used for RFC2460bis and I recommend that the current =
text is left unchanged until we figured out what to do with EH insertion.

DV: I support this recommendation, especially that there will be a document=
 submitted in 2 weeks, stated here, that will add more context. Which posit=
ion the WG good discussion.

> Thanks.
> s.
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Wed Mar 15 11:13:28 2017
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 29259131775; Wed, 15 Mar 2017 11:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yrELJmRGY_mr; Wed, 15 Mar 2017 11:13:19 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02B47131773; Wed, 15 Mar 2017 11:13:18 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2FICOpe013839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Mar 2017 11:12:25 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com>
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <51747194-64e8-5957-167d-3132185039b3@isi.edu>
Date: Wed, 15 Mar 2017 11:12:25 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WMWBZR3VtLFrqrTdfmd6UtobhfI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 18:13:21 -0000

Stefano,

Your case below falls under the "acting on behalf of the endpoint"
approach, IMO.

I'm comfortable with the current proposed resolution, which IMO allows
for enterprises to "create" the IP header in whatever distributed system
they want.

The only rule is simple: that enterprise must act like a host in total,
i.e., it must follow node requirements.

If you do that, then nobody will care how you implement header creation.

Joe


On 3/15/2017 8:55 AM, Stefano Previdi (sprevidi) wrote:
> Suresh,
>
> I appreciate your effort and I=E2=80=99m obviously interested into find=
ing a way out from this issue.
>
> To my view, due to the work that has been initiated in drat-ietf-6man-s=
egment-routing-header and recently in draft-filsfils-srv6-network-program=
ming, the current text of RFC2460 (i.e., not the =E2=80=9Cbis=E2=80=9D ve=
rsion) is good enough.
>
> RFC2460 section 4 states:
>
>    With one exception, extension headers are not examined or processed
>    by any node along a packet's delivery path, until the packet reaches=

>    the node (or each of the set of nodes, in the case of multicast)
>    identified in the Destination Address field of the IPv6 header.
>
> Now, RFC2460 has been written almost 20 years ago and since then, both =
technology and network operators requirements have evolved.
>
> We do have today use cases where not only the source of a packet should=
 be allowed to insert a header but also the source =E2=80=9Cdomain=E2=80=9D=
 of a packet. I=E2=80=99ll try to explain.
>
> In a domain controlled by a single organization (typically the set of A=
Ss under control of the same operator) a packet enters at the edge where =
the ingress node applies a policy resulted into an additional outer ipv6 =
header that may or may not contain an extension header. Bottom line, the =
outer header means that now, it is a NEW packet, originated by the ingres=
s node, with SA/DA representing the nodes that are inside the operator do=
main. Therefore, we can say that this new packet (formed by an outer head=
er and encapsulated original packet) is now owned by the operator and wha=
tever the operator does with this packet:
>
> . The packet MUST leave the operator network in the exact same shape/fo=
rmat as it entered (i.e.: outer encapsulation removed).
> . The outer header MAY change while in transit in the operator=E2=80=99=
s domain. Moreover, a header MAY be inserted while inside the operator=E2=
=80=99s domain (knowing that outer header and any other inserted header w=
ould be removed at egress). This means that an SRH MAY be inserted at the=
 same time the outer header is added but it can also be that the ingress =
adds the outer header and some other node inserts an SRH (e.g.: fast rero=
ute within operator=E2=80=99s infrastructure).
> . While in transit, the operator network must handle aspects like MTU p=
roperly, taking into account the increased size of the packet.
>
> So, this use case enlarge the rule for header insertion.
>
> Originally RFC2460 stated that only the source of the packet is entitle=
d to add an EH. Now we=E2=80=99re going to propose that the source =E2=80=
=9Cdomain=E2=80=9D of the packet is allowed to insert EHs. The source dom=
ain being the set of nodes (including the ingress node adding the outer h=
eader) under common administration. This also implies that when the packe=
t leaves the domain, it must recover its original format/shape.
>
> In order to have a more productive discussion, we are writing a draft o=
n header insertion that will be submitted as soon as the windows re-open =
(during ietf week).
>
> In the mean time, I think it is way too premature to come to conclusion=
 on what text should be used for RFC2460bis and I recommend that the curr=
ent text is left unchanged until we figured out what to do with EH insert=
ion.
>
> Thanks.
> s.
>
>
>> On Mar 15, 2017, at 3:47 AM, Suresh Krishnan <suresh.krishnan@ericsson=
=2Ecom> wrote:
>>
>> Thanks to everyone who commented during the IETF Last Call of draft-ie=
tf-6man-rfc2460bis-08. The IETF last call discussion for this draft was m=
ainly focused around the text in Section 4 that discusses the handling of=
 extension headers. The biggest concern raised was that the current text =
is ambiguous on whether header insertion is allowed on intermediate nodes=
 or not. There were some people arguing that an explicit prohibition is n=
ot necessary as the text is already clear, while others believed that exp=
licitly listing the prohibitions will minimize any misunderstandings in t=
he future. There was also a small number of people who wanted to explicit=
ly allow header insertion and describe how to do it, but this was clearly=
 out of scope for this draft (but may be in scope for future work in 6man=
). Overall, no one argued against the fact that the intent of the text in=
 RFC2460 was to forbid insertion of extension headers on any other node b=
ut the source of the packet.  The only argument made against adding clari=
fying text was that the text was already clear. Given this, I believe the=
re is consensus to add explicit text about header insertion into the draf=
t before it progresses further. I have discussed this with the editor and=
 the document shepherd and would like to propose the following text chang=
e.
>>
>> OLD (from -08):
>>
>> The insertion of Extension Headers by any node other than the source
>> of the packet causes serious problems.  Two examples include breaking
>> the integrity checks provided by the Authentication Header Integrity
>> [RFC4302], and breaking Path MTU Discovery which can result in ICMP
>> error messages being sent to the source of the packet that did not
>> insert the header, rather than the node that inserted the header.
>>
>> One approach to avoid these problems is to encapsulate the packet
>> using another IPv6 header and including the additional extension
>> header after the first IPv6 header, for example, as defined in
>> [RFC2473]
>>
>> With one exception, extension headers are not processed by any node
>> along a packet's delivery path, until the packet reaches the node (or
>> each of the set of nodes, in the case of multicast) identified in the
>> Destination Address field of the IPv6 header...
>>
>> NEW:
>>
>> With one exception, extension headers are not examined, processed,
>> inserted, or deleted by any node along a packet's delivery path,
>> until the packet reaches the node (or each of the set of nodes, in
>> the case of multicast) identified in the Destination Address field of
>> the IPv6 header...
>>
>> Please feel free to comment either privately or on list if you have an=
y concerns with this resolution going forward.
>>
>> Regards
>> Suresh
>>
>> P.S.: There were also other editorial issues that were raised during l=
ast call and they should be addressed in the next version of the draft---=
-----------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------



From nobody Wed Mar 15 11:14:44 2017
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 E81E0131776; Wed, 15 Mar 2017 11:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aQlbJFYPRYd; Wed, 15 Mar 2017 11:14:36 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB8B9131765; Wed, 15 Mar 2017 11:14:36 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2FIE8Pf014148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Mar 2017 11:14:10 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: "Leddy, John" <John_Leddy@comcast.com>, Tim Chown <Tim.Chown@jisc.ac.uk>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk> <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com>
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu>
Date: Wed, 15 Mar 2017 11:14:10 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6vKqGxdAEBI0ItN1KIXnrRrNbHo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 18:14:38 -0000

On 3/15/2017 9:33 AM, Leddy, John wrote:
> Does this mean that only middle boxes, not covered by the architecture could insert an extension header for use within the domain?
Please see my recent post about Stefano's issue. IMO, any opaque
(distributed) system that acts like a host can follow the host (node)
requirements.

The instant that system is not opaque or fails to act like a single
host, it becomes noncompliant.

Joe



From nobody Wed Mar 15 11:48:57 2017
Return-Path: <fgont.si6networks@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 3047C1317BC; Wed, 15 Mar 2017 11:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fGsGeVsMkIQH; Wed, 15 Mar 2017 11:48:49 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C44E21317B0; Wed, 15 Mar 2017 11:48:48 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id n21so19985791qta.1; Wed, 15 Mar 2017 11:48:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=/c5YxBQESe9wUc9UE6eQAQLEXC3hZiY9BRVTZEI/R4M=; b=THKmNrvq64yi35SPzr3py67ULKdGf8P6h+1XBAT4e5xqQEREU5HmeAOntkuk39UiFW mOOkhpPk0+SvzKRo/7bZnyPHBUDnV7HZf8JLI/f0VRr7juYJmEulnzoyW7/TPuPKpB07 1tCsmORAZ0pgBMSHQo+nEoTBKrfiVvX3OZjITIRpFnpTyOdVw1yHcRlAu1asz4/cTdGL 60dccrEyjsTuC+L36v3hrX09byrVbOyF3Hyfgs/mOY9t9xUmGHO39cluIWAugPcfccjk CNYnpxYl8Y6yDhMPJdkmIv1V8rXDRik9cc4ZzPo1K3ETBtkTk71Pyl9mmYxwwBsnvJp4 SZwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=/c5YxBQESe9wUc9UE6eQAQLEXC3hZiY9BRVTZEI/R4M=; b=fRTM9JHDbuOUx5S4M71lC15Aio14UZCTcbAIs6nC0LBr60D8oZ58qktAXEb1cn73JP DiIQ0F8dKqmpeRqQtIem36mtFwwXZ0fvNOVthcOHiF8wGTFDBZVuZy12TXnRtPdgIgBZ r5KY2NcBgZPhKhf5w6UJGli+Dq9R5Ms+oJmT5pyb/Ot2eHSsx+/Zk/JbJuXJnn3rDX44 3YddpG00eTOaBgY+owHc08ud3JQK1AHhTkdizhG3PLOYlTnAhkBCRQldn3usQFcGWOcm 7aqtqIVJTN8MWzx63ZW3xFJmibFtWtX/Fl1yDFrfE8TArHotQlCa8Mc4hVfeezED2GY1 FkiA==
X-Gm-Message-State: AFeK/H13uVNPXprXvdt/oufMSQXeSofCkto+gEnAVqpOt8v6TZIC53bKJFsFbQ0ZmM2A5RcM3Kd9sJBluIXEzA==
X-Received: by 10.237.42.109 with SMTP id k42mr4680057qtf.52.1489603727993; Wed, 15 Mar 2017 11:48:47 -0700 (PDT)
MIME-Version: 1.0
Sender: fgont.si6networks@gmail.com
Received: by 10.140.17.213 with HTTP; Wed, 15 Mar 2017 11:48:47 -0700 (PDT)
Received: by 10.140.17.213 with HTTP; Wed, 15 Mar 2017 11:48:47 -0700 (PDT)
In-Reply-To: <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Date: Wed, 15 Mar 2017 15:48:47 -0300
X-Google-Sender-Auth: lSWIJwTFL0OmLPaDgC4voHHYSc4
Message-ID: <CAFQ9LJJ5NXx9WTxSvHpP9QJ-KoByq5URMG+U2MO9xi5+QUhTBw@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: ietf@ietf.org, 6man Mailing List <ipv6@ietf.org>,  "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a114239121037d7054ac965e9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cIWcX-U9JAQY0wc3egglhp9SAVM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 18:48:50 -0000

--001a114239121037d7054ac965e9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

+1


El 15/3/2017 13:17, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
escribi=C3=B3:

> Stefano,
> On 16/03/2017 04:55, Stefano Previdi (sprevidi) wrote:
> ...
> > In the mean time, I think it is way too premature to come to conclusion
> on what text should be used for RFC2460bis and I recommend that the curre=
nt
> text is left unchanged until we figured out what to do with EH insertion.
>
> I believe that we have figured it out: extension header insertion is
> harmful to Internet interoperability.
>
> I fully agree with Suresh's understanding of the rough consensus.
>
>    Brian
>
>

--001a114239121037d7054ac965e9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">+1<div dir=3D"auto"><br></div></div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">El 15/3/2017 13:17, &quot;Brian E Carp=
enter&quot; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carp=
enter@gmail.com</a>&gt; escribi=C3=B3:<br type=3D"attribution"><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">Stefano,<br>
On 16/03/2017 04:55, Stefano Previdi (sprevidi) wrote:<br>
...<br>
&gt; In the mean time, I think it is way too premature to come to conclusio=
n on what text should be used for RFC2460bis and I recommend that the curre=
nt text is left unchanged until we figured out what to do with EH insertion=
.<br>
<br>
I believe that we have figured it out: extension header insertion is harmfu=
l to Internet interoperability.<br>
<br>
I fully agree with Suresh&#39;s understanding of the rough consensus.<br>
<br>
=C2=A0 =C2=A0Brian<br>
<br>
</blockquote></div></div>

--001a114239121037d7054ac965e9--


From nobody Wed Mar 15 11:59:29 2017
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 A345B1317C4; Wed, 15 Mar 2017 11:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5CvrN5SPTKBx; Wed, 15 Mar 2017 11:59:25 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7F7B1317B6; Wed, 15 Mar 2017 11:59:25 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id z13so26950965iof.2; Wed, 15 Mar 2017 11:59:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Ws6E1ZoldqSknOCCnwZETYm/BULceeEuOtraiX3XFcY=; b=WJlIJijpV8QSOi3uBfekk2iNSoIYyrCr000BTtHXYEnqf678otwjr2Gm87SrvBLAgJ Kq7y2PIw0oidr9I9giGN6mR3LR4pIPvwanfot0rnUJ9nLV/hLXOu+5XLbt2EvpXygOtm 1yJCro1jVdoFZ88xB4oaZIs9FC5JqOr6SyaHgrH4QWEy3ScYyeR3qK8X8iuNfCiUVCWF jSXH/5e9pMXWXH9V3Js7GmZ0Xa5hf27veGIURx1LpJG+H4n8D4T7247V1ivL698nlGtd dmnEoRBGO7bzSuNtPeIoJqDPESrrgT/2i71xaA1RGJPE1cbVTVy9tFrFBVy0RiY+fhgF YUHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Ws6E1ZoldqSknOCCnwZETYm/BULceeEuOtraiX3XFcY=; b=TZ8Hs10K/Hc6peGXtMkb6FzgvLKzXn6f6spQcd6JLjLsSeGKUQcXMzmZeJwjLyGTjf 56pQIIA4yl4oEDh6Qz70f5eM90nuT0MR7HFfqKbVIbY1HTeziI9pWYDUUprpAVI4rRbd kVaKGs/bSzu4+azLMlhi5dlZbonQUPo3RyXNKJH7n2mzhDWqcOvOeIT8lxT8z3jEunSh 3RIG3QDz5854w5oAOunj3iSsbtHVJ8T4xWhaXk9ktv6ge8hz/ubnJsunZ61tvEBnK0Jo PJUP39zNi+HHy7o3zbGXXz65f7B78IxCmH+dKXSZJHCk41tGIexGrwtnBlmGWy1P9vEA 1tCA==
X-Gm-Message-State: AFeK/H0Citk4edN09Jhb5gXWImJ5eZ4uur+R3oQZj8efcQp7CpBnH4QSrQZZKXmQfQJXJw==
X-Received: by 10.107.2.201 with SMTP id 192mr6547803ioc.81.1489604365107; Wed, 15 Mar 2017 11:59:25 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id i189sm538611ita.23.2017.03.15.11.59.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Mar 2017 11:59:24 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Joe Touch <touch@isi.edu>, "Leddy, John" <John_Leddy@comcast.com>, Tim Chown <Tim.Chown@jisc.ac.uk>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk> <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com> <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu>
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com>
Date: Thu, 16 Mar 2017 07:59:31 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cJzpMgXMNajL579UqfJTsE48b0Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 18:59:28 -0000

On 16/03/2017 07:14, Joe Touch wrote:
> 
> 
> On 3/15/2017 9:33 AM, Leddy, John wrote:
>> Does this mean that only middle boxes, not covered by the architecture could insert an extension header for use within the domain?
> Please see my recent post about Stefano's issue. IMO, any opaque
> (distributed) system that acts like a host can follow the host (node)
> requirements.
> 
> The instant that system is not opaque or fails to act like a single
> host, it becomes noncompliant.

That's the point. That's why the 6man WG shot down proposals to play
intra-domain tricks with the flow label a few years ago, and they
didn't even break PMTUD or IPsec/AH.

In another form, the answer to John is that there are no protocol police,
so what consenting adults do inside their own networks simply isn't an
issue that an Internet-wide spec can or should address. And for sure, the
spec for IPvN for any value of N is an Internet-wide spec.

If Stefano and colleagues describe how private domains can perform tricks
that MUST NOT be exported to the Internet, that is fine. Whether that
becomes a standards track document or an Independent Submission RFC is
another question. But IMHO it is completely orthogonal to the rough
consensus on 2460bis.

    Brian


From nobody Wed Mar 15 12:46:37 2017
Return-Path: <willi.uebelherr@riseup.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 F0D0C1317D9 for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 12:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s1xAwXrmd5IK for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 12:46:23 -0700 (PDT)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AC1F13177F for <ietf@ietf.org>; Wed, 15 Mar 2017 12:46:23 -0700 (PDT)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 5C7BA1A2105; Wed, 15 Mar 2017 19:46:21 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1489607182; bh=B94C8dUELmCnwkTmNLz/Z6Ix5PJGVi2+ckCmeupUaFs=; h=Subject:References:From:To:Cc:Date:In-Reply-To:From; b=sNj8qbLY3WZClueGzE/Ez7w+D2u32oAVYbM2KtUTPCoQbfk4Y6oslc07zNsjap/GI mPV+9te7aVUOfCKLZo8hl8rc9qbzHQPHsp1bYpHJvpzEX4rB4Uob+Xg7/yuf8l4lYO jdCMPerUtwXq1LDLRDETS4N8zTOYSCI02bYqqawc=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id BB64D1C2545
Subject: Fwd: Web Foundation responds to India consultation on net neutrality
References: <http://webfoundation.org/?p=12811@localhost.localdomain>
From: willi uebelherr <willi.uebelherr@riseup.net>
To: ISOC Internet Policy <internetpolicy@elists.isoc.org>, IGF gov <governance@lists.igcaucus.org>
Cc: IETF discussion <ietf@ietf.org>, IRTF discuss <irtf-discuss@irtf.org>, IRTF gaia <gaia@irtf.org>, IGF dc <dc@intgovforum.org>, IGF dc ctu <dc_connectingtheunconnected@intgovforum.org>, IGF dc civ <values@coreinternetvalues.org>
X-Forwarded-Message-Id: <http://webfoundation.org/?p=12811@localhost.localdomain>
Message-ID: <5774aa9c-3c04-4722-6486-3c4ae5e82dca@riseup.net>
Date: Wed, 15 Mar 2017 16:45:52 -0300
MIME-Version: 1.0
In-Reply-To: <http://webfoundation.org/?p=12811@localhost.localdomain>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6V-6m_9gqFZmDV_r5nzK9XAcx9I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 19:46:26 -0000

Dear friends,

this email i received from the Web Foundation. It is a very good 
contribution to our discussions to net neutrality in a concrete environment.

many greetings, willi
Asuncion, Paraguay


-------- Forwarded Message --------
Subject: Web Foundation responds to India consultation on net neutrality
Date: 	Wed, 15 Mar 2017 14:21:52 +0000
From: 	Web Foundation <>

Web Foundation responds to India consultation on net neutrality

Net neutrality — the principle that all internet traffic be treated 
equally — is fundamental to our mission to deliver digital equality — a 
world where everyone has the same rights and opportunities online. Why? 
If dominant content providers can pay to have their traffic prioritised, 
it risks harming competition and innovation, while limiting freedom of 
expression. If governments block or censor content that they do not 
agree with, it hurts free speech and democracy.

Today, in partnership with the Digital Empowerment Foundation 
<https://defindia.org/>(DEF), the Web Foundation has made a submission 
<http://webfoundation.org/docs/2017/03/WFDEFResponsetoTRAIcallforcommentsonNN-Mar14-FINAL.pdf> 
to an important consultation on net neutrality in India. Responding to 
questions from Telecom Regulatory Authority of India (TRAI), the Web 
Foundation and DEF have jointly made four key recommendations:

*1) Consider introducing a no-fee basic data allowance*
Today, mobile broadband penetration is India is estimated to be less 
than 10% (GSMA Intelligence Q4 2016). Addressing this challenge will 
require innovative interventions which should be encouraged by the 
government. However, we argue that interventions to provide access for 
low-income and/or marginalised communities must also adhere to net 
neutrality principles, as they should for all Indians. Previous attempts 
in India include zero-rating programmes which restricted users to a 
limited set of sites or services, and these proved controversial. 
Meanwhile, research 
<http://1e8q3q16vyc81g8l3h3md6q5f5e.wpengine.netdna-cdn.com/wp-content/uploads/2016/05/MeasuringImpactsofMobileDataServices_ResearchBrief2.pdf>by 
the Alliance for Affordable Internet has suggested such zero rating 
initiatives are not effective in bringing new users online, and that 
users would rather have free access to the whole internet, even if it is 
limited by time or data allocation. Our joint suggestion is for TRAI to 
explore ways to provide a basic monthly data allowance. Other countries, 
such as Colombia 
<http://a4ai.org/affordability-report/report/2017/#which_countries_top_the_2017_adi?>, 
are already experimenting with such policies: given the size of India’s 
market and the country’s global influence, the successful implementation 
of such an initiative could be world-leading and transformative.

*2) Encourage TSPs to make detailed information available on important 
areas such as quality of service and network neutrality compliance— in 
open data formats wherever possible*
In order for regulators, citizens and civil society to monitor progress 
and ensure traffic management practices abide by net neutrality 
guidelines, detailed information that can easily be analysed is needed. 
For this reason, we propose that TSPs be required to make detailed, 
technical filings with TRAI either quarterly or bi-annually, and to post 
the results on their websites too. Wherever feasible, this information 
should be released as open data 
<https://blog.okfn.org/2013/10/03/defining-open-data/>— free for anyone 
to reuse or analyse — in order to maximise transparency and accountability.

*3) Don’t ban paid service-specific data bundles *—*unless there is a 
relationship between mobile operators and content providers*
We argue that application-specific traffic discrimination should not be 
allowed. However, one exception is the case of service-specific data 
bundles — where TSPs charge different rates for access to certain sites 
or applications. Such bundles can be a good way for operators to respond 
to customer demand and devise innovative ways for more people to connect 
and communicate affordably. As such, we recommend that they should be 
encouraged, with any complaints dealt with on a case-by-case basis. The 
caveats, of course, are if there is a commercial relationship between 
TSPs and the sites or applications included in the bundle or if the 
content is not available on a non-exclusive basis to all TSPs; in such 
cases, we believe that service-specific data bundles should not be allowed.

*4) Consider creating a dedicated advisory committee on net neutrality 
*—*with representatives from government, business and civil society*
It is clear that net neutrality is a vital issue. Preserving and 
enhancing it will help Indian entrepreneurs and established businesses 
alike, and can help millions more to connect affordably. Yet it is also 
a complex issue, which will continue to shift and evolve over time. For 
this reason, we recommend that TRAI considers establishing a dedicated 
advisory committee on net neutrality, made up of representatives from 
business, government, academia and civil society. One of the most 
important mandates of this committee would be to explore the 
implications of emerging technologies on the principles of network 
neutrality, which TRAI should revisit every two years to allow for agile 
policy design. We do not envision this body as one that can take actions 
in case of any violation of network neutrality. However, the committee 
would be able to make recommendations directly to TRAI.

/The Web Foundation also made a submission to TRAI’s previous 
consultation on net neutrality in 2015, which can be //accessed here/ 
<http://webfoundation.org/2015/04/net-neutrality-india/>/. /

/The Digital Empowerment Foundation’s’ previous submissions can be 
accessed below:/

   * /////Submission on Consultation Paper on Differential pricing for
     Data Services/
 
<http://www.internetrights.in/wp-content/uploads/2014/11/Submission-on-Differential-Pricing_CounterComments_Digital-Empowerment-Foundation.pdf>
   * /////Submission on Consultation Paper on OTT Services/
 
<http://www.internetrights.in/wp-content/uploads/2017/03/net_neutrality_def.pdf>
   * /////Submission on Consultation on Free Data Provision/
 
<http://www.internetrights.in/wp-content/uploads/2017/03/DEF_Comments-on-Free-Data-Consultation-Paper_Final.pdf>
   * /////Submission on Pre-Consultation Paper on net Neutrality/
 
<http://www.internetrights.in/wp-content/uploads/2017/03/DEF_Comments-on-NN-Pre-Consultation-Paper.pdf>

For updates on net neutrality and other issues, follow us on twitter at 
@webfoundation <http://twitter.com/webfoundation> and sign up to our 
mailing list <http://eepurl.com/WxB9j>


From nobody Wed Mar 15 13:34:42 2017
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 E046C131826; Wed, 15 Mar 2017 13:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bgaQyHwoU87P; Wed, 15 Mar 2017 13:34:34 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 012F71315A7; Wed, 15 Mar 2017 13:34:33 -0700 (PDT)
Received: from [128.9.184.222] ([128.9.184.222]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v2FKYFrQ021996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Mar 2017 13:34:15 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Leddy, John" <John_Leddy@comcast.com>, Tim Chown <Tim.Chown@jisc.ac.uk>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk> <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com> <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu> <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com>
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <39a51f77-a89f-2a22-dd9b-af8255a4aa25@isi.edu>
Date: Wed, 15 Mar 2017 13:34:15 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rvMsureWg7h3l9NmZ7hYG9YUHFQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 20:34:35 -0000

Agreed.

Joe


On 3/15/2017 11:59 AM, Brian E Carpenter wrote:
> On 16/03/2017 07:14, Joe Touch wrote:
>>
>> On 3/15/2017 9:33 AM, Leddy, John wrote:
>>> Does this mean that only middle boxes, not covered by the architecture could insert an extension header for use within the domain?
>> Please see my recent post about Stefano's issue. IMO, any opaque
>> (distributed) system that acts like a host can follow the host (node)
>> requirements.
>>
>> The instant that system is not opaque or fails to act like a single
>> host, it becomes noncompliant.
> That's the point. That's why the 6man WG shot down proposals to play
> intra-domain tricks with the flow label a few years ago, and they
> didn't even break PMTUD or IPsec/AH.
>
> In another form, the answer to John is that there are no protocol police,
> so what consenting adults do inside their own networks simply isn't an
> issue that an Internet-wide spec can or should address. And for sure, the
> spec for IPvN for any value of N is an Internet-wide spec.
>
> If Stefano and colleagues describe how private domains can perform tricks
> that MUST NOT be exported to the Internet, that is fine. Whether that
> becomes a standards track document or an Independent Submission RFC is
> another question. But IMHO it is completely orthogonal to the rough
> consensus on 2460bis.
>
>     Brian


From nobody Wed Mar 15 13:39:39 2017
Return-Path: <markzzzsmith@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 D1189131827; Wed, 15 Mar 2017 13:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level: 
X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eVjRl2TDWQuj; Wed, 15 Mar 2017 13:39:30 -0700 (PDT)
Received: from mail-ua0-x235.google.com (mail-ua0-x235.google.com [IPv6:2607:f8b0:400c:c08::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8374D1315A7; Wed, 15 Mar 2017 13:39:30 -0700 (PDT)
Received: by mail-ua0-x235.google.com with SMTP id 72so15285013uaf.3; Wed, 15 Mar 2017 13:39:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LDzdPKwtU2L7kdWIFxVhAgLtziivGxboU2IdORfil0s=; b=FYqgt4AZEPig3nXIyqnTEbdVlPaXokyT5A23zlKyoLbZCjBW5n3c1gt8qhKmxJUBb5 vLBnEaEgd7bab32wX9+6FLtyBRtigiSbtmWuZDlg/06nktc5EBRDZX512Ah4Xm9h0oYa ipyudZWlq2g2dLUyPL6W8xcBWybV54QIiE+XRS/FUMCh0tusjv8IL1rU7rv3W3gmS645 /x4C8NwEIaI0p1evnt963pxlK01dBSrinuz/zc2afm6Y7zxzrU95fKd1uhwHqh9Jb2di rbZjBBE5Odcuk57fVRdVQ18vnj5N3bQJkLrmRxcdvtH01TRsvt+asmkFNEMKxSKjS2O4 taUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LDzdPKwtU2L7kdWIFxVhAgLtziivGxboU2IdORfil0s=; b=l9DD0UZHLai+ssaAlLqgbJffIhrXI+Q59BA86a8QaqnD42EcuzCkzVwQZFil4yn6fn 6wJgWaDvyTfv4W85i+RKbBr0lzGHKzN8ffmtV+A01O1IyqB6Gl4R3Nsa8csrvGao2AEp rsOpN+ZWZotfDcmz2oxiKveDeG65RLs6edamPegH1FEO7fZpXxUngUKESIT3+8FRlmif h0LymlqbiUnbFxWZzVkomlVIRor5/Gsyo11lxpE/Nt3P05jistjKerPg0LcQ6lF8fBWr sTTKUgXn50uGY6UID/dVZHjZia+QOAmKzn3e8h90cmHcNMTellzwLSyp6I1UwzqqyMTU 7Xcg==
X-Gm-Message-State: AFeK/H10VTVRHtmfyLgisMexC0CI6Gd8HVvHILSTd0T3XgX9xa0WLkOKtb2S0+m0SxI9QCpr6/cmvC9/awARfA==
X-Received: by 10.159.40.226 with SMTP id d89mr2160544uad.98.1489610369643; Wed, 15 Mar 2017 13:39:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.142.207 with HTTP; Wed, 15 Mar 2017 13:38:58 -0700 (PDT)
In-Reply-To: <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 16 Mar 2017 07:38:58 +1100
Message-ID: <CAO42Z2w623z=As6a1t2CLaO+pwOyvckvw9AOxG-mn=cVy-h--g@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>,  Suresh Krishnan <suresh.krishnan@ericsson.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WSFM-5T5J4SPrqw1hu5w7Q0yq8E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 20:39:32 -0000

On 16 March 2017 at 03:16, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> Stefano,
> On 16/03/2017 04:55, Stefano Previdi (sprevidi) wrote:
> ...
>> In the mean time, I think it is way too premature to come to conclusion on what text should be used for RFC2460bis and I recommend that the current text is left unchanged until we figured out what to do with EH insertion.
>
> I believe that we have figured it out: extension header insertion is harmful to Internet interoperability.

I and others were going to work on an ID describing why, however the
other co-authors seem to have disappeared. I'll start putting together
what I have over the next week.


Regards,
Mark.


>
> I fully agree with Suresh's understanding of the rough consensus.
>
>    Brian
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Wed Mar 15 16:32:06 2017
Return-Path: <tim.chown@jisc.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 9809E12E872 for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 16:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QwWawFNUBW8N for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 16:32:03 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6403E12E858 for <ietf@ietf.org>; Wed, 15 Mar 2017 16:32:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1489620721; bh=iOoSbw2B1yB8vbmfNH74zQQotgi7HFhucth64OWQsts=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To:Content-ID:MIME-Version:Content-Type:Content-Transfer-Encoding; b=X/5ex0k7MdmA2uTrgPH9JWJS5WrKeKGx9ELSTVKLeGQ3CHo2VO0KbmqaCXPToFc4vvPKG+9XqDyYyfYKYYFCwW3OLHBtRRqM32x/yN8vz93i6yo6UnkG+Ha9vWe4zugCkBwdgq2heaqwYaH03I0/XcnZCGhFUP7tmgc02gYyQIE=
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01lp0177.outbound.protection.outlook.com [213.199.154.177]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-103-wqu_9MEZNvqiDxvMYcdTQg-1; Wed, 15 Mar 2017 23:30:25 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.977.5; Wed, 15 Mar 2017 23:30:23 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::59f7:b9fe:6ca:9476]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::59f7:b9fe:6ca:9476%14]) with mapi id 15.01.0977.013; Wed, 15 Mar 2017 23:30:23 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Joe Touch <touch@isi.edu>, "Leddy, John" <John_Leddy@comcast.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv71giYAPcbUKK9ywM4gSjvqGWDpMAgAAGIICAAAFLgIAAA1kAgAAcHgCAAAysgIAAS6oA
Date: Wed, 15 Mar 2017 23:30:23 +0000
Message-ID: <401F52B1-3D41-4174-9425-50571B2D0B9E@jisc.ac.uk>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk> <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com> <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu> <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com>
In-Reply-To: <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:a88:d510:1101:7904:94e8:362f:9092]
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1140; 7:dihn/He7cQCpi1nURC6r3PBslY2Pms+OaOWKjeAzrGo81H3Zu5bRvmZWhv93X0rOVLKsZxhYftiE7kTDZ5/64JBoiD9iyxkhGX8dJ+6gFPEhxzVcaEWwCt1uBl/hGq7zWTcOUYifu5eCtxNAdRCMqi6NpiUSUZVKmQacxsRztmlwjMBzuF+mpW0bIr4MxlrUz3cS1FcgoCyBgNLwzEBd93G/WuKvzDp1nceRsn+A6uz8kfgPToWHtI9N7LoR/rZjglDJFMR2AAqTHgo2UeBUobcJAyNGTIX+R0JpJK2hujY96EY6w9g08bZpbfDbs2JvtLBFanNxvnPm6kQ79UI49A==; 20:qHt0jwp4T45imEgrrhH9sEvDMzs2zTHzKEz91dnpExF7gyeDToV9qC8NS70UdwWF34YEXLPRe68tfMi2+5m/mGzMsJlCd1/SrAA8z0HDjg6UgnDN7z6XbSPfPvjBPs1Rh3zyiPQZ22zFeBxK+U5Ja2ESo+jaHolgRi3b1/n4Nuk=
x-ms-office365-filtering-correlation-id: 197ee99c-1ca4-4075-fe1d-08d46bfb40fc
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM3PR07MB1140;
x-microsoft-antispam-prvs: <AM3PR07MB1140B3542EC1E4AE5AB975D6D6270@AM3PR07MB1140.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317)(17755550239193);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123562025)(20161123560025)(20161123555025)(20161123558025)(20161123564025)(6072148); SRVR:AM3PR07MB1140; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1140; 
x-forefront-prvs: 02475B2A01
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39450400003)(24454002)(377454003)(82746002)(36756003)(229853002)(6486002)(83716003)(6116002)(53936002)(33656002)(102836003)(230783001)(2906002)(3280700002)(3660700001)(5250100002)(53546007)(189998001)(2900100001)(74482002)(93886004)(4326008)(7736002)(305945005)(6916009)(42882006)(6512007)(99286003)(54906002)(50226002)(57306001)(6436002)(6506006)(86362001)(39060400002)(81166006)(8676002)(50986999)(76176999)(8936002)(38730400002)(6246003)(110136004)(2950100002)(5660300001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1140; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <E37A3E4B1B556B4F8DF4F58AC8785B13@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2017 23:30:23.5866 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1140
X-MC-Unique: wqu_9MEZNvqiDxvMYcdTQg-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cZ9AT3UG96HPMfK4ETUvWIc4-cU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Mar 2017 23:32:05 -0000

> On 15 Mar 2017, at 18:59, Brian E Carpenter <brian.e.carpenter@gmail.com>=
 wrote:
>=20
> On 16/03/2017 07:14, Joe Touch wrote:
>>=20
>>=20
>> On 3/15/2017 9:33 AM, Leddy, John wrote:
>>> Does this mean that only middle boxes, not covered by the architecture =
could insert an extension header for use within the domain?
>> Please see my recent post about Stefano's issue. IMO, any opaque
>> (distributed) system that acts like a host can follow the host (node)
>> requirements.
>>=20
>> The instant that system is not opaque or fails to act like a single
>> host, it becomes noncompliant.
>=20
> That's the point. That's why the 6man WG shot down proposals to play
> intra-domain tricks with the flow label a few years ago, and they
> didn't even break PMTUD or IPsec/AH.
>=20
> In another form, the answer to John is that there are no protocol police,
> so what consenting adults do inside their own networks simply isn't an
> issue that an Internet-wide spec can or should address. And for sure, the
> spec for IPvN for any value of N is an Internet-wide spec.
>=20
> If Stefano and colleagues describe how private domains can perform tricks
> that MUST NOT be exported to the Internet, that is fine. Whether that
> becomes a standards track document or an Independent Submission RFC is
> another question. But IMHO it is completely orthogonal to the rough
> consensus on 2460bis.

Exactly.

Tim


From nobody Wed Mar 15 17:22:10 2017
Return-Path: <jari.arkko@piuha.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 0BF2312E870; Wed, 15 Mar 2017 17:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjXJfZlRS8ha; Wed, 15 Mar 2017 17:21:55 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A592A12ECEB; Wed, 15 Mar 2017 17:21:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8E46C2CCC1; Thu, 16 Mar 2017 02:21:53 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MFfwtPNYTiIA; Thu, 16 Mar 2017 02:21:53 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id B4DF42CC5E; Thu, 16 Mar 2017 02:21:50 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: Review of draft-ietf-lmap-information-model-17
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_CB8F321D-D12E-4739-87AA-32F20AFB3153"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148814339074.2901.10793232146724828053.idtracker@ietfa.amsl.com>
Date: Thu, 16 Mar 2017 09:21:48 +0900
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-lmap-information-model.all@ietf.org, IETF <ietf@ietf.org>, lmap@ietf.org
Message-Id: <391122AA-5077-4208-AD6A-4104BDAAEDA0@piuha.net>
References: <148814339074.2901.10793232146724828053.idtracker@ietfa.amsl.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xzkC38k0BSs9Y0MGmlGooRqpwfk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 00:21:57 -0000

--Apple-Mail=_CB8F321D-D12E-4739-87AA-32F20AFB3153
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Thanks for your review, Russ. For what it is worth, I agree with your =
comment/question about the credentials. It is fine to have different =
arrangements for different situations, but Russ=92s question was really =
not about that but whether the CA information mentioned earlier is a =
part of a specific part of the information model (ma-credentials). I =
think that deserves clarification.

Jari


--Apple-Mail=_CB8F321D-D12E-4739-87AA-32F20AFB3153
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYydqcAAoJEM80gCTQU46qIncP/1nkY97exXg32sKClJYWiNAS
Z+m0lpOuWO1VFGq/t1yO+aNzD/OQ9x/F/HGUydNlBwSY9Soynxuh+rB9O1GubD8E
/5e6Cs+yv6VXx3iGAAsCBrqK+4rFAfzSmukenabcXWpeJgAqCec0nAxfro2ethK6
c842wq0cPl0wi6Rugse1VcCnt9dJOn80oUXziO1qaYuYt5LGwJ88Y9XXujBwACyl
cRY/MX+y1t66ZRiL3DJTKY+XG7nqsB+sYRdUsq3K3wyZ1OwJNuJvCmuCeb1A/4px
WOA/l5PPYFYx+CYjoarA6QQ12aSq3rNiShY3EOROxTTQ5O84B/wIPdMzb2yRoU+1
f+LijEfXx3fpZEbZcphLAXeV4bQN7kra3t41ogowswrVx4b98OmjemZsoYs6Ue0F
VNBkQupupssf3iNmgPQR0+AkEVT5y8Q9cRJnA4nhzeKy6U7Spk6m8dKydeGPwWgY
8t283RzmNNpkJzMV+B0dnITtQyK/XtUc53/gNb6qFzLem5/xXuAiU9T2Bx/Ol4Ht
ZQrj2hIqg/N6LdG/e3h9fmWfb2gbmydcv7qBCZzY8P3C6J9KBsz2GVF+xHGr1pGj
qloIyXMmDQ3ck7j1VXOgHfSTtAh+/2NgpM6knfOxNXYuzOBBH+51/7bMxMl+Twiw
OlFS0uY5PPfyCHtlWYo0
=7cXd
-----END PGP SIGNATURE-----

--Apple-Mail=_CB8F321D-D12E-4739-87AA-32F20AFB3153--


From nobody Wed Mar 15 17:54:08 2017
Return-Path: <blong@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 B08C112EAA1 for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 17:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YEZVSXdmFz5s for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 17:54:05 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0631D12EA81 for <ietf@ietf.org>; Wed, 15 Mar 2017 17:54:05 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id o4so22096129ywd.3 for <ietf@ietf.org>; Wed, 15 Mar 2017 17:54:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nGN29pxc1COte6DWuNsdO02sRAb4uTHPrPIMQz8rKmM=; b=AwR7cven7kL80KJq5REzSo8R1pBIh0ufyY6Pqi04+zaeMNvPyeHu491w0A/I19WB/A nQOr8Bou0BJXrXDKccP5WdeLTeKRDo5U+g28sXUD98G1tTZXpE/WsB9XiNXvQBhNYEtH lb4l5TzY+SVFf4dE2EEx/DZIyVK1XfFBOxDSyW0mNpW8UgmLrWxs+aKxI9WVC5oTJfDI bek4LwQVwS6BFTZo0fsNG69cGRFilYctiy6kLoCLJAYGRcGmWULlLhtwUVhXiULz5dT4 CB3OSt1V5bz5UopBbTr6yfC0sS5spQ0bHOjG+S8DOVNK7MQkB/t7AksWdbo1is+zhHgF rpzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nGN29pxc1COte6DWuNsdO02sRAb4uTHPrPIMQz8rKmM=; b=Y2a3rnQ42qfa4wQODUOqPMpxjNPcIjn+pmbszunM/JSEkkCruirDpJcB2GeEdBwGMz zmqN1S3SRihUp3z17Zihp7i3qhz7Ay0kd8qBukE51pxQbnEeCZWLb2MLLA3XFzQJkRC6 OGGo1/cv2XArwbeErW7eCFLXWbqGb6jhWtD75GrAmnXHQbSz7Brrr8XJ0DgdPZ4AbITn 5sOXMKUxR1L7VOLcCl1plmuaIuaghYly45FyIPvLYsgUopRyLK8n7PVZ/Jt/x3LepIs7 DrXBT28BnD/xavJzxpLLcIALhVN5ZOzPkYialyLfhXoIXTecfIpxj+uHQP0olK/nhPbF nsEA==
X-Gm-Message-State: AFeK/H2ONlZpTnbVYLnxBY02yI6aEevDhy8+wnpXMrf15gzLH2UXES/AeYoAOUpl/u644tpTPvxa2UG2uQ9MmpS5
X-Received: by 10.37.192.16 with SMTP id c16mr625030ybf.195.1489625643525; Wed, 15 Mar 2017 17:54:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.220.11 with HTTP; Wed, 15 Mar 2017 17:54:02 -0700 (PDT)
In-Reply-To: <20170315153502.GA7490@localhost>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <m1cnjqr-0000GkC@stereo.hq.phicoh.net> <CABa8R6v+ymVRef5_7vCso2xDNAy2XtsAtRP78dbVFcaprFG3iw@mail.gmail.com> <m1co6fG-0000FQC@stereo.hq.phicoh.net> <20170315153502.GA7490@localhost>
From: Brandon Long <blong@google.com>
Date: Wed, 15 Mar 2017 17:54:02 -0700
Message-ID: <CABa8R6u_cU3wrzzcfrn-BHLxCx9EnM3R9usb73FSgTHOvcoWoA@mail.gmail.com>
Subject: Re: Do you really not care whether people accept your mail?
To: Nico Williams <nico@cryptonector.com>
Cc: Philip Homburg <pch-ietf-6@u-1.phicoh.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113a119a55215e054ace7fdf
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Emikb421DneQsijdfjdudjESn_s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 00:54:07 -0000

--001a113a119a55215e054ace7fdf
Content-Type: text/plain; charset=UTF-8

On Wed, Mar 15, 2017 at 8:35 AM, Nico Williams <nico@cryptonector.com>
wrote:

> On Wed, Mar 15, 2017 at 12:00:20PM +0100, Philip Homburg wrote:
> > >On Tue, Mar 14, 2017 at 3:38 AM, Philip Homburg <
> pch-ietf-6@u-1.phicoh.com>
> > >wrote:
> > >> In my experience, essentially no mail gets lost if you leave out SPF,
> DKIM,
> > >> DMARC. The only exception is gmail that occasionally rejects e-mail.
> > >
> > >"no mail gets lost" != "gmail occasionally rejects my mail"
> >
> > What I meant to write is that when I take all e-mail targets that I send
> e-mail
> > to, leaving out gmail, then sending mail without SPF, DKIM, DMARC works
> just
> > fine.
> >
> > Gmail is an exception because it seems that gmail is broken if you
> deliver
> > mail without SPF, etc. over IPv6 to gmail. That's unique to gmail.
>
> The problem is twofold: a) gmail has a huge number of mailboxes, so if
> you can't deliver to them without SPF/DKIM/DMARC, then your mail truly
> is broken, b) they could be setting the rule, so that even if you don't
> mind (a), you soon will feel the pain.
>
> > So if your outgoing mail doesn't have SPF, etc. and you do have IPv6,
> then
> > you have to think about what to do with gmail.
>
> As a user, when I send email, I don't want to think about this sort of
> thing.  An admin has to think about this sort of thing, and it's looking
> a lot like email is nowhere near the relatively easy service to run that
> it was in the 90s.
>

Do you run spam filters on your mail server today? Do you run an open relay?
Does your mail client support html email?  How about MIME?

Yes, running a mail server today is not like it was 25 years ago.


> > >Do you imagine that you may be making different choices than others?
> >
> > Imagine that some will be making different chocies than me, yes.
>
> Balkanizing email doesn't sound very good to me.


Is it balkanizing email to require five minutes to set up an SPF record?
Not setting it up is a choice to be on the outside.

Imagine if instead they were refusing to add an IPv6 address to their mail
server, so they wouldn't ever be able to send to an IPv6 only MX.  Who is
making the choice to balkanize then?

Brandon

--001a113a119a55215e054ace7fdf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Mar 15, 2017 at 8:35 AM, Nico Williams <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:nico@cryptonector.com" target=3D"_blank">nico@cryptonector.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"=
">On Wed, Mar 15, 2017 at 12:00:20PM +0100, Philip Homburg wrote:<br>
&gt; &gt;On Tue, Mar 14, 2017 at 3:38 AM, Philip Homburg &lt;<a href=3D"mai=
lto:pch-ietf-6@u-1.phicoh.com">pch-ietf-6@u-1.phicoh.com</a>&gt;<br>
&gt; &gt;wrote:<br>
&gt; &gt;&gt; In my experience, essentially no mail gets lost if you leave =
out SPF, DKIM,<br>
&gt; &gt;&gt; DMARC. The only exception is gmail that occasionally rejects =
e-mail.<br>
&gt; &gt;<br>
&gt; &gt;&quot;no mail gets lost&quot; !=3D &quot;gmail occasionally reject=
s my mail&quot;<br>
&gt;<br>
&gt; What I meant to write is that when I take all e-mail targets that I se=
nd e-mail<br>
&gt; to, leaving out gmail, then sending mail without SPF, DKIM, DMARC work=
s just<br>
&gt; fine.<br>
&gt;<br>
&gt; Gmail is an exception because it seems that gmail is broken if you del=
iver<br>
&gt; mail without SPF, etc. over IPv6 to gmail. That&#39;s unique to gmail.=
<br>
<br>
</span>The problem is twofold: a) gmail has a huge number of mailboxes, so =
if<br>
you can&#39;t deliver to them without SPF/DKIM/DMARC, then your mail truly<=
br>
is broken, b) they could be setting the rule, so that even if you don&#39;t=
<br>
mind (a), you soon will feel the pain.<br>
<span class=3D""><br>
&gt; So if your outgoing mail doesn&#39;t have SPF, etc. and you do have IP=
v6, then<br>
&gt; you have to think about what to do with gmail.<br>
<br>
</span>As a user, when I send email, I don&#39;t want to think about this s=
ort of<br>
thing.=C2=A0 An admin has to think about this sort of thing, and it&#39;s l=
ooking<br>
a lot like email is nowhere near the relatively easy service to run that<br=
>
it was in the 90s.<br></blockquote><div><br></div><div>Do you run spam filt=
ers on your mail server today? Do you run an open relay?</div><div>Does you=
r mail client support html email?=C2=A0 How about MIME?</div><div><br></div=
><div>Yes, running a mail server today is not like it was 25 years ago.</di=
v><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
&gt; &gt;Do you imagine that you may be making different choices than other=
s?<br>
&gt;<br>
&gt; Imagine that some will be making different chocies than me, yes.<br>
<br>
</span>Balkanizing email doesn&#39;t sound very good to me.</blockquote><di=
v><br></div><div>Is it balkanizing email to require five minutes to set up =
an SPF record?=C2=A0 Not setting it up is a choice to be on the outside.</d=
iv><div><br></div><div>Imagine if instead they were refusing to add an IPv6=
 address to their mail server, so they wouldn&#39;t ever be able to send to=
 an IPv6 only MX.=C2=A0 Who is making the choice to balkanize then?</div><d=
iv><br></div><div>Brandon</div></div></div></div>

--001a113a119a55215e054ace7fdf--


From nobody Wed Mar 15 18:12:24 2017
Return-Path: <xing@cernet.edu.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEAC712F28B; Wed, 15 Mar 2017 18:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v5FTHjV83DML; Wed, 15 Mar 2017 18:12:14 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp11.tsinghua.edu.cn [166.111.204.35]) by ietfa.amsl.com (Postfix) with ESMTP id CD99412F274; Wed, 15 Mar 2017 18:12:13 -0700 (PDT)
Received: from [10.235.130.16] (unknown [58.200.235.59]) by app3 (Coremail) with SMTP id DMxvpgDn7u5e5slYCalDAg--.6843S2; Thu, 16 Mar 2017 09:12:06 +0800 (CST)
Message-ID: <58C9E662.6060100@cernet.edu.cn>
Date: Thu, 16 Mar 2017 09:12:02 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Joe Touch <touch@isi.edu>, "Leddy, John" <John_Leddy@comcast.com>,  Tim Chown <Tim.Chown@jisc.ac.uk>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>,  6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk> <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com> <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu> <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com>
In-Reply-To: <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com>
Content-Type: multipart/alternative; boundary="------------030700070707020503000404"
X-CM-TRANSID: DMxvpgDn7u5e5slYCalDAg--.6843S2
X-Coremail-Antispam: 1UD129KBjvJXoW7WrW8Kry7Gw4rKr4xJr4rGrg_yoW8Xw15pr Waqry7tr1DJF1xJr48Jw18Xr1vqrW5Kr47WF18tryrAw1UArnF9r1Utry8WryjkryFqw1U tr4UWF1DG3W8XrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUySb7Iv0xC_KF4lb4IE77IF4wAFF20E14v26r4j6ryUM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2z4x0Y4vE2Ix0cI8IcVAFwI0_Jr0_JF4l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Jr0_ Gr1l84ACjcxK6I8E87Iv67AKxVWUJVW8JwA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_Gr0_Gr 1UM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAqjxCE14ACF2xKxwAqx4xG6I8vx48I 62xC7I0kMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4I kC6x0Yz7v_Jr0_Gr1lF7xvr2IY64vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMxkIecxEwVAF wVWkMxAIw28IcxkI7VAKI48JMI8I3I0E5I8CrVAFwI0_JrI_JrWlx2IqxVCjr7xvwVAFwI 0_JrI_JrWlx4CE17CEb7AF67AKxVWUAVWUtwCIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE 14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8JwCI42IY6xAIw20EY4v20x vaj40_WFyUJVCq3wCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14v2 6r1j6r4UYxBIdaVFxhVjvjDU0xZFpf9x0UUjR-UUUUUU=
X-CM-SenderInfo: p0lqwqxfhu0vvwohv3gofq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CS4hWQURSMkwOxyzC_WbyC4uVVQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 01:12:22 -0000

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

Brian E Carpenter ??:
> On 16/03/2017 07:14, Joe Touch wrote:
>   
>> On 3/15/2017 9:33 AM, Leddy, John wrote:
>>     
>>> Does this mean that only middle boxes, not covered by the architecture could insert an extension header for use within the domain?
>>>       
>> Please see my recent post about Stefano's issue. IMO, any opaque
>> (distributed) system that acts like a host can follow the host (node)
>> requirements.
>>
>> The instant that system is not opaque or fails to act like a single
>> host, it becomes noncompliant.
>>     
>
> That's the point. That's why the 6man WG shot down proposals to play
> intra-domain tricks with the flow label a few years ago, and they
> didn't even break PMTUD or IPsec/AH.
>
> In another form, the answer to John is that there are no protocol police,
> so what consenting adults do inside their own networks simply isn't an
> issue that an Internet-wide spec can or should address. And for sure, the
> spec for IPvN for any value of N is an Internet-wide spec.
>
> If Stefano and colleagues describe how private domains can perform tricks
> that MUST NOT be exported to the Internet, that is fine. Whether that
> becomes a standards track document or an Independent Submission RFC is
> another question. But IMHO it is completely orthogonal to the rough
> consensus on 2460bis.
>
>   

+1, xing

>     Brian
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>   


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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Brian E Carpenter &#20889;&#36947;:
<blockquote cite="mid:ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com"
 type="cite">
  <pre wrap="">On 16/03/2017 07:14, Joe Touch wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">
On 3/15/2017 9:33 AM, Leddy, John wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">Does this mean that only middle boxes, not covered by the architecture could insert an extension header for use within the domain?
      </pre>
    </blockquote>
    <pre wrap="">Please see my recent post about Stefano's issue. IMO, any opaque
(distributed) system that acts like a host can follow the host (node)
requirements.

The instant that system is not opaque or fails to act like a single
host, it becomes noncompliant.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
That's the point. That's why the 6man WG shot down proposals to play
intra-domain tricks with the flow label a few years ago, and they
didn't even break PMTUD or IPsec/AH.

In another form, the answer to John is that there are no protocol police,
so what consenting adults do inside their own networks simply isn't an
issue that an Internet-wide spec can or should address. And for sure, the
spec for IPvN for any value of N is an Internet-wide spec.

If Stefano and colleagues describe how private domains can perform tricks
that MUST NOT be exported to the Internet, that is fine. Whether that
becomes a standards track document or an Independent Submission RFC is
another question. But IMHO it is completely orthogonal to the rough
consensus on 2460bis.

  </pre>
</blockquote>
<br>
+1, xing<br>
<br>
<blockquote cite="mid:ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com"
 type="cite">
  <pre wrap="">    Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>
Administrative Requests: <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a>
--------------------------------------------------------------------

  </pre>
</blockquote>
<br>
</body>
</html>

--------------030700070707020503000404--


From nobody Wed Mar 15 22:12:36 2017
Return-Path: <liushucheng@huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E7002120227; Wed, 15 Mar 2017 22:12:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Shucheng LIU <liushucheng@huawei.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-dime-agent-overload.all@ietf.org, dime@ietf.org, ietf@ietf.org
Subject: Review of draft-ietf-dime-agent-overload-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148964114787.14141.11366451118403466758@ietfa.amsl.com>
Date: Wed, 15 Mar 2017 22:12:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Dla84N4Qd-VdW_qd8k0sWwhPXA4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 05:12:28 -0000

Reviewer: Shucheng LIU
Review result: Has Nits

Hi all,

(Sorry for being late that I reviewed this draft with a printed one on
my flight to home last month, however, I left paper there…)
I have reviewed draft-ietf-dime-agent-overload-08 as part of the
Operational directorate's ongoing effort to review all IETF documents
being processed by the IESG.  These comments were written with the
intent of improving the operational aspects of the IETF drafts.
Comments that are not addressed in last call may be included in AD
reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

“This specification documents an extension to RFC 7683 (Diameter
   Overload Indication Conveyance (DOIC)) base solution.  The
extension
   defines the Peer overload report type.  The initial use case for
the
   Peer report is the handling of occurrences of overload of a
Diameter
   agent.”

My overall view of the document is 'Ready with nits' for publication.


** Technical **
No.


** Editorial **

*Section 2, page 4
>    A RFC6733 Diameter Client, an RFC6733 Diameter Server, and
RFC6733
>       Diameter Agent.

s/ RFC6733/ [RFC6733]
Similar changes should also be made in this section to get consistent
with section 1 and the last sentence in section 2(therein you were
using [RFC6733]).


* Section 3.1.1, page 4:

>                              +-+    +-+    +-+
>                               |c|----|a|----|s|
>                              +-+    +-+    +-+

Though I can easily guess what does “c, a, s” mean here, I still
suggest to put full words or at least add a sentence below the figure
to explain.
The same issue should be fixed in all the figures below in entire
section 3.

 
* Section 3.1.2, page 6:

>   In the case where one of the agents in the above scenario becomes
>   overloaded

s/ scenario becomes/ scenarios become

If I understand correctly , here you were referring to two scenarios
above?

>   When the client has an active and a standby connection to the two
>   agents then an alternative strategy for responding to an overload
>   report from an agent is to change to standby connection to active
and
>   route all traffic through the new active connection.

I would suggest to split this sentence in case of misunderstanding.


* Section 3.1.3, page 7:

>  Handling of overload of one or both of agents a11 or a12 in this
case
>   is equivalent to that discussed in section 2.2.

Tried hard to find section 2.2, but there is no such section.


* Section 5.1.1, page 8:

>   When sending a Diameter request a DOIC node that supports the
>    OC_PEER_REPORT feature MUST include in the OC-Supported-Features
AVP
>    an OC-Feature-Vector AVP with the OC_PEER_REPORT bit set.

Full name of AVP should be put into terminology.



From nobody Thu Mar 16 01:08:29 2017
Return-Path: <leifj@mnt.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 5358F126E3A for <ietf@ietfa.amsl.com>; Thu, 16 Mar 2017 01:08:28 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N8gUgKggoqZL for <ietf@ietfa.amsl.com>; Thu, 16 Mar 2017 01:08:26 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BAF3126D74 for <ietf@ietf.org>; Thu, 16 Mar 2017 01:08:26 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id a6so16703311lfa.0 for <ietf@ietf.org>; Thu, 16 Mar 2017 01:08:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=8K3gXHd0IkERV3PjaCnw12S+Xhj7djSqSz0g/Qwts3s=; b=vQJqkd8C2w/1Rj4gMUuah2VoZ1J1g3/EeCFLStvGObfCX5YPWu28JzV+y2inszLsEi Uny1/oXQDIaxHPJINe2DvVvbSVFV/GUomnqVTpex9WFgYxUf6C7AyuvqtZcoEowgVZhW sLybNZZMnl60skIvxCkMs491q+wf6xV34osA5LnYfBQhrvL348dXGTKAAiSYZpmxv2CL 1fV6YXAExZGPoEXycIXxot9UUyimKo5Ga0r4SooRxKxoCBaup0tyDOoOkDZwoIYcGDTE YSiA/paqRxD4wHwcrshgBq4uc/3IW/3H874bPqTGQHRGrwLBrm/jdy9jxeWP06xrN6fp 1RxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=8K3gXHd0IkERV3PjaCnw12S+Xhj7djSqSz0g/Qwts3s=; b=F2GG7HrSZHKUD/fao5MRpboUsinbEq5LVzkhhBNg+ACIWUEhe82HSb/GuKXYotMGeW nBDq/gY2gS2ovSf7+a56MmNsmKRl5x0tUglWx9izW/2iqKRvcYOSakO5iaGMHx3kNT4a gqNKo3Wn4D6oJ6vpUyvNwEFmhOe6e7IKcBPVJe0SIgbeJSDeIIk8D5GBEJNPTUgJv20T Y80xW2PiTZQqHTEVjP6Q6o4MgJqZD3GlJvi1j4xBi+WDKdEW5oNCGj0FKk8xaRFnrv4F AnX03l4iCtl9sLMay4GRtTKRmzOS0YldC86et+TM0CSYzazcVxQ7XYFE+7jzKrgXmXob ZoOw==
X-Gm-Message-State: AFeK/H3ewo8LY7csiFQruDxjwXPMePCRFQ1Sa0j05Idv4ZgCYD3jYFzrkOE4yz4+DARg0Q==
X-Received: by 10.25.208.11 with SMTP id h11mr2381264lfg.150.1489651704502; Thu, 16 Mar 2017 01:08:24 -0700 (PDT)
Received: from ?IPv6:2001:6b0:7:1:e556:a13f:a9f6:aead? ([2001:6b0:7:1:e556:a13f:a9f6:aead]) by smtp.gmail.com with ESMTPSA id 3sm759285ljj.16.2017.03.16.01.08.23 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Mar 2017 01:08:23 -0700 (PDT)
Subject: Re: Review of draft-ietf-lmap-information-model-17
To: ietf@ietf.org
References: <148814339074.2901.10793232146724828053.idtracker@ietfa.amsl.com> <391122AA-5077-4208-AD6A-4104BDAAEDA0@piuha.net>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <50cf0939-edc9-cb78-2b30-31e8bc757d1f@mnt.se>
Date: Thu, 16 Mar 2017 09:08:15 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <391122AA-5077-4208-AD6A-4104BDAAEDA0@piuha.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vvRVqOxsBNci3bklGLqSMhITnP5K9vJkl"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YJb-DaGrgpUJylBrSdpvTZUV2fk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 08:08:28 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--vvRVqOxsBNci3bklGLqSMhITnP5K9vJkl
Content-Type: multipart/mixed; boundary="NkMvlI4ntBsepWbTeglGvOs6oProAqoMl";
 protected-headers="v1"
From: Leif Johansson <leifj@mnt.se>
To: ietf@ietf.org
Message-ID: <50cf0939-edc9-cb78-2b30-31e8bc757d1f@mnt.se>
Subject: Re: Review of draft-ietf-lmap-information-model-17
References: <148814339074.2901.10793232146724828053.idtracker@ietfa.amsl.com>
 <391122AA-5077-4208-AD6A-4104BDAAEDA0@piuha.net>
In-Reply-To: <391122AA-5077-4208-AD6A-4104BDAAEDA0@piuha.net>

--NkMvlI4ntBsepWbTeglGvOs6oProAqoMl
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable



On 2017-03-16 01:21, Jari Arkko wrote:
> Thanks for your review, Russ. For what it is worth, I agree with your c=
omment/question about the credentials. It is fine to have different arran=
gements for different situations, but Russ=92s question was really not ab=
out that but whether the CA information mentioned earlier is a part of a =
specific part of the information model (ma-credentials). I think that des=
erves clarification.
>=20
> Jari
>=20

This was exactly the point I was also trying to make.


--NkMvlI4ntBsepWbTeglGvOs6oProAqoMl--

--vvRVqOxsBNci3bklGLqSMhITnP5K9vJkl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAljKR/YACgkQ8Jx8FtbMZndCKgCfVL7CNeUKwF74NqoZOGt06c8z
nmEAoMlYS23uCKpj293YD8XpHm5/Fisi
=CEbN
-----END PGP SIGNATURE-----

--vvRVqOxsBNci3bklGLqSMhITnP5K9vJkl--


From nobody Thu Mar 16 01:11:57 2017
Return-Path: <otroan@employees.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 B22D2126DC2; Thu, 16 Mar 2017 01:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5K_FmcqlljU; Thu, 16 Mar 2017 01:11:53 -0700 (PDT)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id AE46F126D74; Thu, 16 Mar 2017 01:11:53 -0700 (PDT)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 16 Mar 2017 08:11:53 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 20418D788D; Thu, 16 Mar 2017 01:11:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=f5Stg+JQioF3tqQnqPXCD9XVPzA=; b= We5tm+PMLgR9GatR5VNCd7gp8glhbPrnj1hPYTmLBMQim7jpn6WDntgyXmMFhPdG zkFA6ROZTMvQLp9F5hdvyQlOsPww3dgF5/sXS32qtYwUbZom8woDOoIuGIe8zteR uFBgqOQlt0tydcy2vr2dteYF8fwU/KJdRAnACCyz3bo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=MvfZcjKojiq/M/qe+utmmzX f4OqQnREX/vBqx7VotxvchfISldBe+PIK4t48neP8tkdIWFKQPpRaY+tJala7dWw AG2EV3tn6HDdQwJneoW5ap8F39VAdgHE4WV/osv0vPhXkPj8hMdBAhHNLEprcGdy NbpOmXtPlbMSBTdJhPkI=
Received: from h.hanazo.no (219.103.92.62.static.cust.telenor.com [62.92.103.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id B6A54D788B; Thu, 16 Mar 2017 01:11:52 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id A66EE9EFB05D; Thu, 16 Mar 2017 09:11:49 +0100 (CET)
From: otroan@employees.org
Message-Id: <CC433743-852B-4D87-9DFC-2BBCC4470917@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_28D39F10-C370-4AEF-AE52-948019DCA92E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Date: Thu, 16 Mar 2017 09:11:48 +0100
In-Reply-To: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com>
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>,  Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>, 6man WG <ipv6@ietf.org>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZYKJjCXAZvP3-SiPL6RyD_LFDdM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 08:11:56 -0000

--Apple-Mail=_28D39F10-C370-4AEF-AE52-948019DCA92E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Guys,

Please hold your horses. The AD has made the call. I don't think we need =
to have a poll on that.

Cheers,
Ole

> On 15 Mar 2017, at 03:47, Suresh Krishnan =
<suresh.krishnan@ericsson.com> wrote:
>=20
> Thanks to everyone who commented during the IETF Last Call of =
draft-ietf-6man-rfc2460bis-08. The IETF last call discussion for this =
draft was mainly focused around the text in Section 4 that discusses the =
handling of extension headers. The biggest concern raised was that the =
current text is ambiguous on whether header insertion is allowed on =
intermediate nodes or not. There were some people arguing that an =
explicit prohibition is not necessary as the text is already clear, =
while others believed that explicitly listing the prohibitions will =
minimize any misunderstandings in the future. There was also a small =
number of people who wanted to explicitly allow header insertion and =
describe how to do it, but this was clearly out of scope for this draft =
(but may be in scope for future work in 6man). Overall, no one argued =
against the fact that the intent of the text in RFC2460 was to forbid =
insertion of extension headers on any other node but the source of the =
packet.  The only argument made against adding clarifying text was that =
the text was already clear. Given this, I believe there is consensus to =
add explicit text about header insertion into the draft before it =
progresses further. I have discussed this with the editor and the =
document shepherd and would like to propose the following text change.
>=20
> OLD (from -08):
>=20
> The insertion of Extension Headers by any node other than the source
> of the packet causes serious problems.  Two examples include breaking
> the integrity checks provided by the Authentication Header Integrity
> [RFC4302], and breaking Path MTU Discovery which can result in ICMP
> error messages being sent to the source of the packet that did not
> insert the header, rather than the node that inserted the header.
>=20
> One approach to avoid these problems is to encapsulate the packet
> using another IPv6 header and including the additional extension
> header after the first IPv6 header, for example, as defined in
> [RFC2473]
>=20
> With one exception, extension headers are not processed by any node
> along a packet's delivery path, until the packet reaches the node (or
> each of the set of nodes, in the case of multicast) identified in the
> Destination Address field of the IPv6 header...
>=20
> NEW:
>=20
> With one exception, extension headers are not examined, processed,
> inserted, or deleted by any node along a packet's delivery path,
> until the packet reaches the node (or each of the set of nodes, in
> the case of multicast) identified in the Destination Address field of
> the IPv6 header...
>=20
> Please feel free to comment either privately or on list if you have =
any concerns with this resolution going forward.
>=20
> Regards
> Suresh
>=20
> P.S.: There were also other editorial issues that were raised during =
last call and they should be addressed in the next version of the =
draft--------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_28D39F10-C370-4AEF-AE52-948019DCA92E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYykjFAAoJEL7aWKiYQt92ANkQAIG+LC51vSPBg1F6Sk25s2MM
8hOj40Od5dZqSJ0J5D9dJNA+SPg4N7nuy/Pu/3hPeMITwkr46dn2BaUMoNPEFu8z
3p8RGFLbcrlf7rUJJojrfGLy54ceU6K7VnVsbiJGOUBrLgvGh1DgGTt+u8XBXs2Q
c+3zFHsFhXi2hNORohSzDcGbreQFsp07nQEzfIw/rGttU/ciCP6m7+fooxsXxKYf
1NRNqYlsfstrX3FUboY3Jo5Of8OCEoJ60Vb55rvigCoWV2v8x2TnU0PhCFIoDyy8
E3txO5eHvYumNSU0pgS7kjvVum19Fyzyjr3sn/WpfxjptfU9ircK6AxNfLygbM4X
ScdjbT/ynJQ8iXKGbZhxQ5kns17piqgBNF1zsjeqUq+uYkhRbvPAF04vgTtvWgcv
x1Zlaob1F4VY/d681NcNQN1YPT2r3frEJo5TyCV50yqUBXFn+BswxMYI0+IPTn6B
X4F6OKLafjmezYoJ8cpvHWDxm1XdUrM0tVZvPTp44L8DWPqIBoDGj/tid6OxktXn
v5DFqmni83fWjeqK4RwUwxlWnop+a9qs+YTqi9aH37shqj4L9yar6Lp3G9oYp+7n
emhJBH8NjFvC0RA6FMNMkNEALc+Sdzs2HIqEWBlNjd7a07sQcDfLtAFezicaGWCD
0ikeWS30msTvni5aP1vj
=J14L
-----END PGP SIGNATURE-----

--Apple-Mail=_28D39F10-C370-4AEF-AE52-948019DCA92E--


From nobody Thu Mar 16 02:46:15 2017
Return-Path: <lionel.morand@orange.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 20E0D1273B1; Thu, 16 Mar 2017 02:46:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Lionel Morand <lionel.morand@orange.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-pce-stateful-pce.all@ietf.org, pce@ietf.org, ietf@ietf.org
Subject: Review of draft-ietf-pce-stateful-pce-18
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148965756308.14230.13426886469262710918@ietfa.amsl.com>
Date: Thu, 16 Mar 2017 02:46:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VC9Bc_6uCZIXn7aWEiUGQCmOnh0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 09:46:03 -0000

Reviewer: Lionel Morand
Review result: Has Issues

I have reviewed this document as part of the Operational directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written with the intent of improving the
operational aspects of the IETF drafts. Comments that are not
addressed in last call may be included in AD reviews during the IESG
review.  Document editors and WG chairs should treat these comments
just like any other last call comments. 

I've pointed out some "issues" that might not be real issues for
people involved in PCE but that could be at least clarified for
readers of this document. Detailed comments are provided below.

Regards,

Lionel

********************
2.  Terminology

   This document uses the following terms defined in [RFC5440]: PCC,
   PCE, PCEP Peer, PCEP Speaker.

   This document uses the following terms defined in [RFC4655]: TED.

   This document uses the following terms defined in [RFC3031]: LSP.

   This document uses the following terms defined in
   [I-D.ietf-pce-stateful-pce-app]: Stateful PCE, Passive Stateful
PCE,
   Active Stateful PCE, Delegation, LSP State Database.

[LM] I didn't find a clear definition of the LSP state, except through
the definition of the LSP State database in ietf-pce-stateful-pce-app,
i.e.

   The second is the LSP
   State Database (LSP-DB), in which a PCE stores attributes of all
   active LSPs in the network, such as their paths through the
network,
   bandwidth/resource usage, switching types and LSP constraints.

As this document heavily relies on this LSP state concept, it could be
useful to (re-)define it in this document or to find a 
correct reference for it.


3.2.  Objectives

   The objectives for the protocol extensions to support stateful PCE
   described in this document are as follows:

[...]

   o  Allow a PCC to delegate control of its LSPs to an active
stateful
      PCE such that a given LSP is under the control of a single PCE
at
      any given time.  A PCC may revoke this delegation at any time
      during the lifetime of the LSP.  If LSP delegation is revoked
      while the PCEP session is up, the PCC MUST notify the PCE about
      the revocation.  A PCE may return an LSP delegation at any
point
      during the lifetime of the PCEP session.

[LM] I'm assuming that the PCE returning the delegation has also to
notify the PCC. If so, maybe:
     
     "the If LSP delegation is returned by the PCE while the PCEP 
      session is up, the PCE MUST notify the PCE about the
revocation."

[LM] the bullet point could be then splitted into two bullets, one for
PCC, one for PCE.

5.4.  Capability Advertisement

   During PCEP Initialization Phase, PCEP Speakers (PCE or PCC)
   advertise their support of stateful PCEP extensions.  A PCEP
Speaker
   includes the "Stateful PCE Capability" TLV, described in
   Section 7.1.1, in the OPEN Object to advertise its support for
PCEP
   stateful extensions.  The Stateful Capability TLV includes the
'LSP
   Update' Flag that indicates whether the PCEP Speaker supports LSP
   parameter updates.

   The presence of the Stateful PCE Capability TLV in PCC's OPEN
Object
   indicates that the PCC is willing to send LSP State Reports
whenever
   LSP parameters or operational status changes.

   The presence of the Stateful PCE Capability TLV in PCE's OPEN
message
   indicates that the PCE is interested in receiving LSP State
Reports
   whenever LSP parameters or operational status changes.

[LM] is it "willing/interested for" or just a capability indication?
It is not the same thing from a procedure point of view.

   The PCEP extensions for stateful PCEs MUST NOT be used if one or
both
   PCEP Speakers have not included the Stateful PCE Capability TLV in
   their respective OPEN message.  If the PCEP Speaker on the PCC
   supports the extensions of this draft but did not advertise this
   capability, then upon receipt of PCUpd message from the PCE, it
MUST
   generate a PCErr with error-type 19 (Invalid Operation),
error-value
   2 (Attempted LSP Update Request if the stateful PCE capability was
   not advertised)(see Section 8.5) and it SHOULD terminate the PCEP
   session.  If the PCEP Speaker on the PCE supports the extensions
of
   this draft but did not advertise this capability, then upon
receipt
   of a PCRpt message from the PCC, it MUST generate a PCErr with
error-
   type 19 (Invalid Operation), error-value 5 (Attempted LSP State
   Report if active stateful PCE capability was not advertised) (see
   Section 8.5) and it SHOULD terminate the PCEP session. 

[LM] why the recommendation for closing the session if an explicit
error is sent back? The session could remain open i.e. except stateful
PCEP extensions,everything else would be fine. If the session
termination is the right thing to do, as we are in a clear error case
(as the PCEP speaker should not send the report or the update), the
SHOULD should probably be a MUST hee. 

[LM] Is there any reason to use a specific error in such a case? The
PCE could just behave as a PCE not supporting the feature. Why is it
important for the supporting PCEP speaker to make the difference? The
generic behavior described in RFC5440 is not enough?

[LM] active/passive mode are not  advertized in PCEP.
s/if active stateful PCE capability was not advertised/if stateful PCE
capability was not advertised

>From RFC5440: "6.9.  Reception of Unknown Messages

   A PCEP implementation that receives an unrecognized PCEP message
MUST
   send a PCErr message with Error-value=2 (capability not
supported).

   If a PCC/PCE receives unrecognized messages at a rate equal or
   greater than MAX-UNKNOWN-MESSAGES unknown message requests per
   minute, the PCC/PCE MUST send a PCEP CLOSE message with close
   value="Reception of an unacceptable number of unknown PCEP
message".
   A RECOMMENDED value for MAX-UNKNOWN-MESSAGES is 5.  The PCC/PCE
MUST
   close the TCP session and MUST NOT send any further PCEP messages
on
   the PCEP session."

[LM] If it is the case, the error handling would be the same between a
PCEP speaker supporting the feature but not advertizing it and a PCEP
speaker not supporting the feature. And it would not be possible
possible to use the specific error responses to infer the capability
supported by the other node.

   Note that even if the update
   capability has not been advertised, a PCE can still accept LSP
Status
   Reports from a PCC and build and maintain an up to date view of
the
   state of the PCC's LSPs.

[LM] I don't undersand. Is it not in contradiction with
  
  "If the PCEP Speaker on the PCE supports the extensions of
   this draft but did not advertise this capability, then upon
receipt
   of a PCRpt message from the PCC, it MUST generate a PCErr with
error-
   type 19 (Invalid Operation), error-value 5 (Attempted LSP State
   Report if active stateful PCE capability was not advertised) (see
   Section 8.5) and it SHOULD terminate the PCEP session."

Or does it mean that there is another way than PCRpt message for the
PCC to send LSP status reports to the PCE?

[LM] In this section, it is not described how non-supporting PCEP
speaker will hanlded the new TLV. It could be said that unrecognized
TLVs will be ignored (as per RFC5440) and OPEN messages will be
handled as per RFC5440 (if the comment above is accepted).

[LM] Would it be useful to discover (using another TLV) whether the
PCE is an active/passive stateful PCE, as in IGP-based capabilities
discovery mechanism?

5.5.  IGP Extensions for Stateful PCE Capabilities Advertisement

   When PCCs are LSRs participating in the IGP (OSPF or IS-IS), and
PCEs
   are either LSRs or servers also participating in the IGP, an
   effective mechanism for PCE discovery within an IGP routing domain
   consists of utilizing IGP advertisements.  

[...]

   Note that while active and passive stateful PCE capabilities may
be
   advertised during discovery, PCEP Speakers that wish to use
stateful
   PCEP MUST negotiate stateful PCEP capabilities during PCEP session
   setup, as specified in the current document.  A PCC MAY initiate
   stateful PCEP capability negotiation at PCEP session setup even if
it
   did not receive any IGP PCE capability advertisements.
 
[LM] As said above, an as stated in section 5.4:
  "The PCEP extensions for stateful PCEs MUST NOT be used if one or
both
   PCEP Speakers have not included the Stateful PCE Capability TLV in
   their respective OPEN message."

What is the real added-value of this IGP-based mechanism? Only to be
able to identify active PCE/passive PCE mode?

5.6.  State Synchronization

[LM] "State" could be misleading. "LSP State Sync" would be more
approriate/accurate I think.

   The purpose of State Synchronization is to provide a
checkpoint-in-
   time state replica of a PCC's LSP state in a PCE.  State
   Synchronization is performed immediately after the Initialization
   phase ([RFC5440]).

   During State Synchronization, a PCC first takes a snapshot of the
   state of its LSPs state, then sends the snapshot to a PCE in a
   sequence of LSP State Reports.  Each LSP State Report sent during
   State Synchronization has the SYNC Flag in the LSP Object set to
1.
   The set of LSPs for which state is synchronized with a PCE is
   determined by advertised stateful PCEP capabilities and PCC's
local
   configuration (see more details in Section 9.1).

[LM] It seems that :

   "The set of LSPs for which state is synchronized"

should be:

   "The set of LSPs for which state is to be synchronized"

[LM] I don't see how the "advertised stateful PCEP capabilities" have
an effect on the set of LSP to synchronize. The capabilities adv is
only used to discover stateful PCE capabilities and see if the related
PCEP extensions can be used. The identification of the LSPs to
synchronize seems to be only based on policies configured in the PCC.

   The end of synchronization marker is a PCRpt message with the SYNC
   Flag set to 0 for an LSP Object with PLSP-ID equal to the reserved
   value 0 (see Section 7.3).  In this case, the LSP Object SHOULD
NOT
   include the SYMBOLIC-PATH-NAME TLV and SHOULD include the LSP-
   IDENTIFIERS TLV with the special value of all zeroes.  The PCRpt
   message MUST include an empty ERO as its intended path and SHOULD
NOT
   include the optional RRO object for its actual path.

[LM] What is the reason for the use of "SHOULD" here, instead of
"MUST"?

   If the PCC has
   no state to synchronize, it SHOULD only send the end of
   synchronization marker.

[LM] Is it when there is no active LSP? If it is, it could be useful
to clarify it. And it is maybe not so related to the text just before.
It could be clarified in a separate paragraph.

   A PCE SHOULD NOT send PCUpd messages to a PCC before State
   Synchronization is complete.  A PCC SHOULD NOT send PCReq messages
to
   a PCE before State Synchronization is complete.  This is to allow
the
   PCE to get the best possible view of the network before it starts
   computing new paths.

[LM] it is obviously assumed that this requirement is true for PCC/PCE
explicitly advertizing support of stateful PCE capability.

   If the PCC encounters a problem which prevents it from completing
the
   state transfer, it MUST send a PCErr message with error-type 20
(LSP
   State Synchronization Error) and error-value 5 (indicating an
   internal PCC error) to the PCE and terminate the session.

[LM] s/state transfer/LSP state synchornization

5.7.1.  Delegating an LSP

   A PCC delegates an LSP to a PCE by setting the Delegate flag in
LSP
   State Report to 1.  If the PCE does not accept the LSP Delegation,
it
   MUST immediately respond with an empty LSP Update Request which
has
   the Delegate flag set to 0.  If the PCE accepts the LSP
Delegation,
   it MUST set the Delegate flag to 1 when it sends an LSP Update
   Request for the delegated LSP (note that this may occur at a later
   time).  The PCE MAY also immediately acknowledge a delegation by
   sending an empty LSP Update Request which has the Delegate flag
set
   to 1.

[LM] if the delegation is not aceepted by the PCE, I assume that the
PCC should not set the Delegate flag in subsequent LSP state report.
If it is, this could be clarified somewhere in this section.

[..]

   Note that for an LSP to remain delegated to a PCE, the PCC MUST
set
   the Delegate flag to 1 on each LSP Status Report sent to the PCE.

[LM] s/each LSP Status Report/each LSP State Report for this LSP.

5.7.2.1.  Explicit Revocation

   When a PCC decides that a PCE is no longer permitted to modify an
   LSP, it revokes that LSP's delegation to the PCE.  A PCC may
revoke
   an LSP delegation at any time during the LSP's life time.  A PCC
   revoking an LSP delegation MAY immediately clear the LSP state
   provided by the PCE, but to avoid traffic loss, it SHOULD do so in
a
   make-before-break fashion.

[LM] After PCE delegation revocation, is there really a requirement
for LSP state clean-up? The revocation is used to remove the
authorization of LSP state update to the PCE but I don't see why the
PCC would clear LSP state after revocation. The LSP state can be
updated using operator-defined default parameters, right?

   If the PCC has received but not yet acted
   on PCUpd messages from the PCE for the LSP whose delegation is
being
   revoked, then it SHOULD ignore these PCUpd messages when
processing
   the message queue.  All effects of all messages for which
processing
   started before the revocation took place MUST be allowed to
complete
   and the result MUST be given the same treatment as any LSP that
had
   been previously delegated to the PCE (e.g. the state MAY be
   immediately cleared).  

[LM] If I correctly understood the text above, after revocation of the
PCE delegation,
- any PCUpd should be rejected and not ignored
- the LSP state(s) that was delegated to the PCE cannot be changed
until all the messages in the message queue have been processed. 

If I'm correct, the text above could be clarified.  

   Any further PCUpd messages from the PCE are
   handled according to the PCUpd procedures described in this
document.

[LM] Not understood. Further PCUpd "will result in the PCC sending a
PCErr message" as said after the figure.

5.7.2.2.  Revocation on Redelegation Timeout

   When a PCC's PCEP session with a PCE terminates unexpectedly, the
PCC
   MUST wait the time interval specified in Redelegation Timeout
   Interval before revoking LSP delegations to that PCE and
attempting
   to redelegate LSPs to an alternate PCE.  If a PCEP session with
the
   original PCE can be reestablished before the Redelegation Timeout
   Interval timer expires, LSP delegations to the PCE remain intact.

[LM] In case of PCEP session interruption, is there a requirement for
the PCE to update delegated LSP states in order to ensure the
synchronization between states in the PCE and in the PCC? 

   Likewise, when a PCC's PCEP session with a PCE terminates
   unexpectedly, the PCC MUST wait for the State Timeout Interval
before
   flushing any LSP state associated with that PCE.

[LM] it should be clarified that the "flushing" applies only if there
is no other PCE. Otherwise, see section 5.7.4

   Note that the State
   Timeout Interval timer may expire before the PCC has redelegated
the
   LSPs to another PCE, for example if a PCC is not connected to any
   active stateful PCE or if no connected active stateful PCE accepts
   the delegation.  

[LM] Not sure to understand. Is it "if a PCC is not connected to any
OTHER active stateful PCE or if no OTHER connected active stateful PCE
accepts the delegation?

   In this case, the PCC MUST flush any LSP state set
   by the PCE upon expiration of the State Timeout Interval and
revert
   to operator-defined default parameters or behaviors.  This
operation
   SHOULD be done in a make-before-break fashion.

[LM] I think it is important to make the distinction between PCC with
only one PCE and PCC with N PCE. The "Note that" could be put in a
separate section.

   The State Timeout Interval MUST be greater than or equal to the
   Redelegation Timeout Interval and MAY be set to infinity (meaning
   that until the PCC specifically takes action to change the
parameters
   set by the PCE, they will remain intact).

[LM] reading "the State Timeout Interval timer may expire before the
PCC has redelegated the LSPs to another PCE" could be understood as
STI timer < RTI timer. And here, it is stated STI timer >= RTI timer.
Depending on the clarification on the previous comment, this text
could be also clarified (or not)

5.7.3.  Returning a Delegation

   In order to keep a delegation, a PCE MUST set the Delegate flag to
1
   on each LSP Update Request sent to the PCC.  A PCE that no longer
   wishes to update an LSP's parameters SHOULD return the LSP
delegation
   back to the PCC by sending an empty LSP Update Request which has
the
   Delegate flag set to 0.  If a PCC receives an LSP Update Request
with
   the Delegate flag set to 0 (whether the LSP Update Request is
empty
   or not), it MUST treat this as a delegation return.

                     +-+-+                    +-+-+
                     |PCC|                    |PCE|
                     +-+-+                    +-+-+
                       |                        |
                       |---PCRpt, Delegate=1--->| LSP delegated
                       |            .           |
                       |            .           |
                       |            .           |
                       |<--PCUpd, Delegate=0----| Delegation returned
                       |                        |
                       |---PCRpt, Delegate=0--->| No delegation for
LSP
                       |                        |

                     Figure 6: Returning a Delegation

   If a PCC cannot delegate an LSP to a PCE (for example, if a PCC is
   not connected to any active stateful PCE or if no connected active
   stateful PCE accepts the delegation), the LSP delegation on the
PCC
   will time out within a configurable Redelegation Timeout Interval
and
   the PCC MUST flush any LSP state set by a PCE at the expiration of
   the State Timeout Interval.

[LM] same comment: is it "for example, if a PCC is not connected to
any OTHER active stateful PCE or if no OTHER connected active stateful
PCE accepts the delegation"?

[LM] "the PCC MUST flush any LSP state set" should be completed by
"and revert to operator-defined default parameters or behaviors",
right?

5.7.5.  Redelegation on PCE Failure

[...]

   If the PCE crashes but recovers within the Redelegation Timeout,
both
   the delegation state and the LSP state are kept intact.

[LM] "Recover" here seems to be associated with the PCEP session (as
linked to the Redelegation Timeout), not with the LSP states
maintained by the PCE.

[LM] How can the PCC be ensured that the PCE has not been impacted by
the stop/restart and that LSP states are intact? Is there any need for
a sanity check?

   If the PCE crashes but does not recover within the Redelegation
   Timeout, the delegation state is returned to the PCC.  If the PCC
can
   redelegate the LSPs to another PCE, and that PCE accepts the
   delegations, there will be no change in LSP state.  If the PCC
cannot
   redelegate the LSPs to another PCE, then upon expiration of the
State
   Timeout Interval, the state set by the PCE is flushed, which may
   cause change in the LSP state.

[LM] the last sentence is difficult to understand. How to understand
"flush the state MAY cause change in the LSP state"? It would like
talking about two different states in the PCC.
[LM] about "flushed", should we add "and revert to operator-defined
default parameters or behaviors"?

[...]

   If there is a standby PCE, the Redelegation Timeout may be set to
0
   through policy on the PCC, causing the LSPs to be redelegated
   immediately to the PCC, which can delegate them immediately to the
   standby PCE.  Assuming the State Timeout Interval is greater than
the
   Redelegation Timeout, and assuming the standby PCE takes similar
   decisions as the failed PCE, the LSP state will be kept intact.

[LM] the first "assuming" is not an assumption but a requirement,
according to "The State Timeout Interval MUST be greater than or equal
to the Redelegation Timeout Interval"

5.8.1.  Passive Stateful PCE Path Computation Request/Response

                     +-+-+                    +-+-+
                     |PCC|                    |PCE|
                     +-+-+                    +-+-+
                       |                        |
   1) Path computation |----- PCReq message --->|
      request sent to  |                        |2) Path computation
      PCE              |                        |   request received,
                       |                        |   path computed
                       |                        |
                       |<---- PCRep message ----|3) Computed paths
                       |     (Positive reply)   |   sent to the PCC
                       |     (Negative reply)   |
   4) LSP Status change|                        |
      event            |                        |
                       |                        |
   5) LSP Status Report|----- PCRpt message --->|
      sent to all      |            .           |
      stateful PCEs    |            .           |
                       |            .           |
   6) Repeat for each  |----- PCRpt message --->|
      LSP status change|                        |
                       |                        |

     Figure 7: Passive Stateful PCE Path Computation Request/Response

[LM] in the figure, please use "state" instead of "status"


7.1.  OPEN Object

   This document defines one new optional TLVs for use in the OPEN
   Object.

s/one new optional TLVs/one new optional TLV

7.2.  SRP Object

   The SRP (Stateful PCE Request Parameters) object MUST be carried
   within PCUpd messages and MAY be carried within PCRpt and PCErr
   messages.  The SRP object is used to correlate between update
   requests sent by the PCE and the error reports and state reports
sent
   by the PCC.

[LM] Should we add the following text at the end of the section?

  "Optional TLVs may be included within the SRP object body. The 
   specification of such TLVs is outside the scope of this document."

7.3.  LSP Object

[...]

   TLVs that may be included in the LSP Object are described in the
   following sections.

[LM] I think that it is possible to add extra optional TLV, not
defined in this document. This should be clarified if I'm correct.


From nobody Thu Mar 16 03:44:41 2017
Return-Path: <stewart.bryant@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 16435127444; Thu, 16 Mar 2017 03:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h3tDprjE1uiX; Thu, 16 Mar 2017 03:44:37 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EC861273E2; Thu, 16 Mar 2017 03:44:37 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id n11so108386372wma.1; Thu, 16 Mar 2017 03:44:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=6Hle2NEUjspCa6SAq+Wf3RpZV4sBgRqnRhmyya9oUf4=; b=ut6DwppRkeuwP/WuU+0hhpcqS/Le7LGogcU7+Qld/eDQdIsBD963sPM7mhOBxEInAR 7ZZTr5TNTcLCZUvPQV6AJI1B32uQykl+0F6pyEwLTT9MaXoeWRHoC+I/M0nyBjNVW5+Y ExDW4if7YU1nDOhQEInaaKoS32s4xad98s/uvgcaI4bosic7IWXSk3ORr5xXQSCW47RC zr3wgkcYAbSzXR/66w/zRM6bnTJRrRSyHle7dI6w46CvfG7kXgpmNtYyn//OWeAEd1/j rIZRYTl+bQJMdxtEqp4FKC7T7RjdckOc/dKVOv6aSLzQblZS4NtQz4khHxTRCJDa9iDw 4MXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=6Hle2NEUjspCa6SAq+Wf3RpZV4sBgRqnRhmyya9oUf4=; b=ZCKx+heEJRDFD3btE4SUKbRq339w8AimprSKURC4J9f/8SO6VzxONdCdn4bmDRXV5m sxatBz41eSdcMDa02Fq+LH16WkebpakZp2JFEO+LQKhScc7nywn972gGZ5KEHs4jVUC2 huw3KyKQ+wuX2Ij4+9MPG37Eif0Q5M4laUk55NQGSNoPOqthteA9ukyACJnnCq1rITk8 /rz8t0TTQmTos0l2f4Kd1E0UcJHSyzMWlGL/R1QXxeIZzeFlf+8RVSkvgbVLzg6m0pj/ k/3aLhS/pJZGVN8BwyhX9y9ELdU7zGiTj10CeP8mjQzM5O5m13BKh5C4Iw3vn+gDS0lM 9hkQ==
X-Gm-Message-State: AFeK/H1ErMCOv1iDtjDhe3fvAn+UWX4+YuOBavugVdVMK/aSd6Ln5TD/T0/+Gr45tuxpYA==
X-Received: by 10.28.230.83 with SMTP id d80mr8419999wmh.18.1489661076045; Thu, 16 Mar 2017 03:44:36 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id b199sm3828273wmb.13.2017.03.16.03.44.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Mar 2017 03:44:35 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Tim Chown <Tim.Chown@jisc.ac.uk>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk> <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com> <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu> <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com> <401F52B1-3D41-4174-9425-50571B2D0B9E@jisc.ac.uk>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Leddy, John" <John_Leddy@comcast.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <6d51de4b-3a9d-0f34-1cd2-5bb30caed75e@gmail.com>
Date: Thu, 16 Mar 2017 10:44:35 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <401F52B1-3D41-4174-9425-50571B2D0B9E@jisc.ac.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bmIPrLVQvs8w8f1gZ2_4taMSpj4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 10:44:39 -0000

> In another form, the answer to John is that there are no protocol police,
> so what consenting adults do inside their own networks simply isn't an
> issue that an Internet-wide spec can or should address.

That is not quite true, the inability to gain an IANA allocated 
codepoint can make long
term private deployments very difficult, either for the protocol 
squatting on a codepoint
because they could not get one allocated, or to the deployment of a new 
protocol
legitimately allocated a conflicting codepoint.

- Stewart





From nobody Thu Mar 16 05:41:12 2017
Return-Path: <John_Leddy@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 79589129482; Thu, 16 Mar 2017 05:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ApmzxNyddbHB; Thu, 16 Mar 2017 05:40:59 -0700 (PDT)
Received: from vaadcmhout01.cable.comcast.com (vaadcmhout01.cable.comcast.com [96.114.28.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC39C129464; Thu, 16 Mar 2017 05:40:57 -0700 (PDT)
X-AuditID: 60721c4b-93fff700000006b0-67-58ca87d6b9bc
Received: from VAADCEX48.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by  (SMTP Gateway) with SMTP id 86.69.01712.7D78AC85; Thu, 16 Mar 2017 08:40:56 -0400 (EDT)
Received: from VAADCEX41.cable.comcast.com (147.191.103.218) by VAADCEX48.cable.comcast.com (147.191.103.225) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 16 Mar 2017 08:40:54 -0400
Received: from VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268]) by VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268%19]) with mapi id 15.00.1263.000; Thu, 16 Mar 2017 08:40:53 -0400
From: "Leddy, John" <John_Leddy@comcast.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Tim Chown <Tim.Chown@jisc.ac.uk>, Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnaSAxRLtjcu1EUaNXmYCyEu8g6GWVuWAgAABTAD//8BKAIAAXywAgAAMrICAAEuugIAAvF6A///dbwA=
Date: Thu, 16 Mar 2017 12:40:53 +0000
Message-ID: <DE16D91D-AE7B-4D3C-B8EA-0CB644FB96BD@cable.comcast.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk> <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com> <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu> <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com> <401F52B1-3D41-4174-9425-50571B2D0B9E@jisc.ac.uk> <6d51de4b-3a9d-0f34-1cd2-5bb30caed75e@gmail.com>
In-Reply-To: <6d51de4b-3a9d-0f34-1cd2-5bb30caed75e@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.115.73.252]
Content-Type: text/plain; charset="utf-8"
Content-ID: <9DBCF6E95FD0C846BD8BD6D2A9CC8E6C@cable.comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFIsWRmVeSWpSXmKPExsWSUOxpoXuj/VSEwaaV6hZtF/cxWbx6e43N 4tnG+SwWL8++Z7JYv/sRk8WpB4kWfT8fszmwe0z5vZHVY+esu+weS5b8ZPJY+fsKWwBLFJdN SmpOZllqkb5dAlfG2ju7GAveiFa8/yTVwLhEtIuRg0NCwETi1AueLkYuDiGBmUwSU1/8YINw DjFKLLjzjAXCOckocbN5D3MXIycHm4COxIxp11hBEiICTYwSn8/3MIM4zAInGCWm3WtlBKkS FvCQmLTpGguILSLgKbFu42EWkH0iAkkSL/5Wg4RZBFQlXi97xgZi8wq4SHTebWMCsYUE7jNL LH8oDGJzCthKbG/aCjaSUUBM4vupNWA1zALiEreezAezJQQEJJbsOc8MYYtKvHz8jxXEFhXQ k3h47yYrRFxH4uz1J4wQtoHE1qX7WCBsRYl/s9eDncYsoCmxfpc+xHgHiZs9DewQtqLElO6H 7BBnCkqcnPkEqlVc4vCRHawTGKVnIbloFsKkWUgmzUIyaRaSSQsYWVcxypUlJqYk52bkl5YY GOolJyblpOol5+cmJxaXgOhNjKAUUSTjvYNx3U/3Q4wCHIxKPLzu4acihFgTy4orc4FRxcGs JMLrlgoU4k1JrKxKLcqPLyrNSS0+xCjNwaIkzntJZHWEkEB6YklqdmpqQWoRTJaJgxOYFswj i/SdJU9Nn23r0PItfdP12y9XxG5zjjVvP1X7ZR6joHx3wGTVbSVSe+fIpoTsC+h+XsW/Z7nd /wP266f/YZL+P/vchXV3PeIrnjREbvLZ2j9XJnvpk5rlz1gu/mncc/jjpOTCkhchjOcOaUvd Wit52knOdaP51/0skwo2X499orC08vm/x0FKLMUZiYZazEXFiQAS/JsdDQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a8rQG8GINvJI3fOrmRGSXh0iPpw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 12:41:01 -0000

VGhhbmtzIFN0ZXdhcnQsDQoNClRoaXMgcmVhbGx5IHN1cHBvcnRzIG15IHBvaW50IGFuZCBob3Bl
ZnVsbHkgbm90IHRoZSBpbnRlbnQgb3IgcmVzdWx0IG9mIHRoZSBkaXNjdXNzaW9ucyBoZXJlLg0K
DQpXZSBhcmUgdHJ5aW5nIHRvIHdvcmsgdGhyb3VnaCB0aGUgSUVURiBwcm9jZXNzIHRvIGNvbWUg
dXAgd2l0aCBzdGFuZGFyZHMgYW5kIHNvbHV0aW9ucyB0aGF0IGFkZHJlc3MgcmVhbCBvcGVyYXRp
b25hbCBjaGFsbGVuZ2VzIGZhY2VkIGluIGRlcGxveW1lbnRzLiAgRm9yIG9wZXJhdG9ycywgZGVh
bGluZyB3aXRoIGxlZ2FjeSBhbmQgbWlncmF0aW9ucyBhcmUgYSBiaWcgY2hhbGxlbmdlLg0KDQpX
aXNoaW5nIHRoZXNlIGlzc3VlcyBhd2F5IGFuZCBhcyBhIHJlc3VsdCBoYXZpbmcgbm9uLXN0YW5k
YXJkIGZ1bmN0aW9uYWxpdHkgaW4g4oCcbWlkZGxlIGJveGVz4oCdIHRoYXQgYXJlIGlnbm9yZWQg
aW4gdGhlIGFyY2hpdGVjdHVyZSBpcyBub3QgcHJvZHVjdGl2ZS4gIE5BVHMgYXJlIGEgd2F5IG9m
IGxpZmUsIGRhcmsgc3BhY2UgaXMgYmVpbmcgZGVwbG95ZWQgYnkgb3RoZXIgb3BlcmF0b3JzLCDi
gJxDbG91ZOKAnS9ORlYvU2VydmljZUNoYWluaW5nIGFyZSBhY3RpdmUgYXJlYXM7IHR1bm5lbHMs
IHR1bm5lbHMgZXZlcnl3aGVyZSAtIFBNVFUgaXMgYWx3YXlzIGFuIGlzc3VlLiAg4oCcVHVydGxl
cyBhbmQgVHVubmVscyBhbGwgdGhlIHdheSBkb3du4oCdLg0KDQpXZSBhcmUgdmVyeSBhZ2dyZXNz
aXZlbHkgbWlncmF0aW5nIHRvIGEgVjYgaW5mcmFzdHJ1Y3R1cmUsIGJ1dCB0aGVyZSBpcyBhIGxh
cmdlIGFtb3VudCBvZiBvbGQgbGVnYWN5IHN5c3RlbXMvYXBwbGljYXRpb25zL3NlcnZpY2VzIHRo
YXQgbmVlZCB0byBiZSBhZGRyZXNzZWQuICBBdCB0aGUgc2FtZSB0aW1lIHRoZSBhbGx1cmUgb2Yg
4oCcQ2xvdWTigJ0gYXR0cmFjdHMgc3lzdGVtcyB0aGF0IHNob3VsZCBuZXZlciBiZSBtb3ZlZCB3
aXRob3V0IGJlaW5nIHJlLWFyY2hpdGVjdGVkIGFuZCB0aGUgdmlydHVhbGl6YXRpb24gZW52aXJv
bm1lbnRzIGZ1bGx5IHN1cHBvcnRpbmcgVjYgKGJvdGggVmVuZG9ycyBhbmQgT3BlblNvdXJjZSkg
4oCTIGJ1dCB0aGV5IGRvIG1vdmUgYW5kIHZlbmRvcnMgaGVscCBtYWtlIHRoYXQgcG9zc2libGUu
DQoNCkhvcGVmdWxseSB3ZSBjYW4ga2VlcCB0aGUgZGlzY3Vzc2lvbnMgZ29pbmcgYW5kIGtlZXAg
dG9vbHMgYXZhaWxhYmxlIHVudGlsIHdlIGtub3cgd2UgaGF2ZSBzb2x1dGlvbnMgdG8gZGVhbCBh
bGwgdGhlIGFjdGl2aXR5IGhhcHBlbmluZyBvdXRzaWRlIGEgY2xlYW4gZW5kLXRvLWVuZCBBcmNo
aXRlY3R1cmUsDQoNCkpvaG4NCg0KDQoNCk9uIDMvMTYvMTcsIDY6NDQgQU0sICJTdGV3YXJ0IEJy
eWFudCIgPHN0ZXdhcnQuYnJ5YW50QGdtYWlsLmNvbT4gd3JvdGU6DQoNCiAgICA+IEluIGFub3Ro
ZXIgZm9ybSwgdGhlIGFuc3dlciB0byBKb2huIGlzIHRoYXQgdGhlcmUgYXJlIG5vIHByb3RvY29s
IHBvbGljZSwNCiAgICA+IHNvIHdoYXQgY29uc2VudGluZyBhZHVsdHMgZG8gaW5zaWRlIHRoZWly
IG93biBuZXR3b3JrcyBzaW1wbHkgaXNuJ3QgYW4NCiAgICA+IGlzc3VlIHRoYXQgYW4gSW50ZXJu
ZXQtd2lkZSBzcGVjIGNhbiBvciBzaG91bGQgYWRkcmVzcy4NCiAgICANCiAgICBUaGF0IGlzIG5v
dCBxdWl0ZSB0cnVlLCB0aGUgaW5hYmlsaXR5IHRvIGdhaW4gYW4gSUFOQSBhbGxvY2F0ZWQgDQog
ICAgY29kZXBvaW50IGNhbiBtYWtlIGxvbmcNCiAgICB0ZXJtIHByaXZhdGUgZGVwbG95bWVudHMg
dmVyeSBkaWZmaWN1bHQsIGVpdGhlciBmb3IgdGhlIHByb3RvY29sIA0KICAgIHNxdWF0dGluZyBv
biBhIGNvZGVwb2ludA0KICAgIGJlY2F1c2UgdGhleSBjb3VsZCBub3QgZ2V0IG9uZSBhbGxvY2F0
ZWQsIG9yIHRvIHRoZSBkZXBsb3ltZW50IG9mIGEgbmV3IA0KICAgIHByb3RvY29sDQogICAgbGVn
aXRpbWF0ZWx5IGFsbG9jYXRlZCBhIGNvbmZsaWN0aW5nIGNvZGVwb2ludC4NCiAgICANCiAgICAt
IFN0ZXdhcnQNCiAgICANCiAgICANCiAgICANCiAgICANCiAgICANCiAgICANCg0K


From nobody Thu Mar 16 06:27:57 2017
Return-Path: <vijay.gurbani@nokia.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5041294E0; Thu, 16 Mar 2017 06:27:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Vijay Gurbani <vijay.gurbani@nokia.com>
To: <gen-art@ietf.org>
Cc: lmap@ietf.org, ietf@ietf.org, draft-ietf-lmap-yang.all@ietf.org
Subject: Review of draft-ietf-lmap-yang-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148967086350.14253.11599284040763992866@ietfa.amsl.com>
Date: Thu, 16 Mar 2017 06:27:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pf2o6Kw8_S09E0vm_EXh6Yc-ujk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 13:27:44 -0000

Reviewer: Vijay Gurbani
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-lmap-yang-??
Reviewer: Vijay Gurbani
Review Date: 2017-03-16
IETF LC End Date: 2017-03-08
IESG Telechat date: 2017-03-16

Summary: Ready as a Proposed Standard.

Major issues: 0

Minor issues: 0

Nits/editorial comments: 1

Nits:
- S3: s/devided/divided/ 



From nobody Thu Mar 16 07:04:09 2017
Return-Path: <jari.arkko@piuha.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 466721294E5; Thu, 16 Mar 2017 07:04:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8HEyOWOoOUAP; Thu, 16 Mar 2017 07:04:05 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D2791129516; Thu, 16 Mar 2017 07:04:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 268CF2CFD8; Thu, 16 Mar 2017 16:04:00 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uU9zqfSEx29X; Thu, 16 Mar 2017 16:03:59 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id ACFE62CC5E; Thu, 16 Mar 2017 16:03:57 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: Review of draft-ietf-mpls-tp-temporal-hitless-psm-13
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_0801213D-FB08-47E9-A3F7-8480FFA07C95"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148948967806.12630.17780798711864289686@ietfa.amsl.com>
Date: Thu, 16 Mar 2017 23:03:56 +0900
Cc: gen-art@ietf.org, mpls@ietf.org, draft-ietf-mpls-tp-temporal-hitless-psm.all@ietf.org, ietf@ietf.org
Message-Id: <EF80A550-F872-498E-A1C8-9F48CC92F6F8@piuha.net>
References: <148948967806.12630.17780798711864289686@ietfa.amsl.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zy0cUN8d7HvXShtcT_mZgiq0BYU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 14:04:07 -0000

--Apple-Mail=_0801213D-FB08-47E9-A3F7-8480FFA07C95
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your substantial comments, Stewart.

Are there any comments from the authors or the WG otherwise?

Jari


--Apple-Mail=_0801213D-FB08-47E9-A3F7-8480FFA07C95
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYyptNAAoJEM80gCTQU46q8CgP/18jqzXBxbL51u4E+lErjdsO
VHQYS99AlNMKpDYlkBRmzBaotRA1YelJwrGz7rXWuNTPQkCrRyPEJUEOcUsFD8id
Nj4SuefNTwAzYnYW+aftuBSZjtlkxQzynNrEpp/Bi6BNv9AfLb+GkF+XeaEi9XXD
KWjCfA63xt0lLsCpWxJcEL9P1AowdlDaxRpWR4GHoaA8A5U8HnvK8+cLnwFBYlg9
/SVVHblhM3Qv3ynIrWcNM/kFL+RJi/WskYVPHzkFyYpSEbJ5mwadh4f288uwlk1L
ZdY+kkFjNOqNe6unOWevjmfABOsowOjaiAlyd5mSStpuvTxwUzBD7tjy+zmoQPBn
bOg/emWufEdo9gNqEFjM6bSX7C7PkFaxehHK0fkm5Fa34Mo4I9l1JhYNIAMQzd/k
Ky1pwT9EnqouVShP9IFs9Ps5QRbymlijTwJw+8AXERSmbrW+pAMZRmyzzmiKJDpm
cAgtFUoA7WGGCJ60hY6w0OmXGhtsh+QvZeq/BKrRNpG2uU2UEY7e9hVQREabyf+a
s+NnvJXjIFgCklNZr/zLukzq3fPf44qaLXP6zV8oatl2Pkf43pTrz/kn11QkueNZ
dzkdGFPWad+PXBrm4FSGMk5f/InNpTxGysA9h+1AfO1tgPCto9RsykO8xZ0oNXiH
GppM5JCsSRNYYoV2Oo6w
=pzmG
-----END PGP SIGNATURE-----

--Apple-Mail=_0801213D-FB08-47E9-A3F7-8480FFA07C95--


From nobody Thu Mar 16 07:21:29 2017
Return-Path: <arleen.elliott@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 4A49912950B; Thu, 16 Mar 2017 07:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UF1GxQmd_aac; Thu, 16 Mar 2017 07:21:25 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9EF3129530; Thu, 16 Mar 2017 07:21:25 -0700 (PDT)
X-AuditID: c6180641-c53ff70000000a06-76-58ca590d2681
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by  (Symantec Mail Security) with SMTP id AD.4E.02566.D095AC85; Thu, 16 Mar 2017 10:21:18 +0100 (CET)
Received: from EUSAAMB104.ericsson.se ([147.117.188.121]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0319.002; Thu, 16 Mar 2017 10:21:23 -0400
From: Arleen Elliott <arleen.elliott@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF Agenda <agenda@ietf.org>
Subject: RE: IETF 98 Final Agenda
Thread-Topic: IETF 98 Final Agenda
Thread-Index: AQHSlHvpwMYa5gN2QUO1JFWlviE3iKGXmJHg
Date: Thu, 16 Mar 2017 14:21:23 +0000
Message-ID: <6725F56E17A2A342B4470C49E21B05FA68CC5C77@eusaamb104.ericsson.se>
References: <148858548925.15899.17612125269091849059.idtracker@ietfa.amsl.com>
In-Reply-To: <148858548925.15899.17612125269091849059.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrNLMWRmVeSWpSXmKPExsUyuXRPuC5f5KkIg63v1S1+vQuyeLZxPosD k8eSJT+ZAhijuGxSUnMyy1KL9O0SuDLuLtjAVPCIo+LBhgWsDYxHOLoYOTkkBEwkrv2fw9rF yMUhJLCeUeL3vRNQznJGiU2b9jGBVLEJGEls3jQPzBYRcJKYcnw2cxcjB4ewgKLE90slEGEl iVeb+9kgbCOJC1+nMILYLAKqEsdOdrCD2LwCvhLNKw8zg9hCAn4SkzatAqvhFPCX+PvlJQuI zSggJvH91BqwVcwC4hK3nsxngjhUQGLJnvPMELaoxMvH/1ghbCWJOa+vgZ3DLKApsX6XPkSr osSU7odQawUlTs58wjKBUWQWkqmzEDpmIemYhaRjASPLKkaO0uKCnNx0I8NNjMAgPybB5riD cW+v5yFGAQ5GJR7eDXInI4RYE8uKK3MPMUpwMCuJ8MbNPhUhxJuSWFmVWpQfX1Sak1p8iFGa g0VJnPd6yP1wIYH0xJLU7NTUgtQimCwTB6dUA6Od/isNZfOV6S9nFp19sNq2Z8PR0tdrm1Q7 vy241CPi/rfjqEmL61ej/arTWz+yOzRerfnVY3vZpeDL575/jw/FJsxfovHz75avDPNEdmQe +9Sp/3xBzYbZBsrvZwkn3D93xjppwjabpO8TNCf+26/sVfdz39cal7RCz28bG5XWv5xxvO3n 7qKdSizFGYmGWsxFxYkAHOd8zm4CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EeVPHpDMGR5TmGOGyiNAJzdhX_k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 14:21:27 -0000

SGF2ZSB0aGVyZSBiZWVuIGFueSBjaGFuZ2VzIHRvIHRoZSBhZ2VuZGEgc2luY2UgdGhpcyBvbmUg
d2FzIHB1Ymxpc2hlZD8NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IElFVEYt
QW5ub3VuY2UgW21haWx0bzppZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFs
ZiBPZiBJRVRGIEFnZW5kYQ0KU2VudDogRnJpZGF5LCBNYXJjaCAwMywgMjAxNyA2OjU4IFBNDQpU
bzogSUVURiBBbm5vdW5jZW1lbnQgTGlzdCA8aWV0Zi1hbm5vdW5jZUBpZXRmLm9yZz4NCkNjOiA5
OGFsbEBpZXRmLm9yZw0KU3ViamVjdDogSUVURiA5OCBGaW5hbCBBZ2VuZGENCg0KSUVURiA5OCAt
IENoaWNhZ28sIElMLCBVU0ENCk1hcmNoIDI2LTMxLCAyMDE3DQoNClRoZSBmaW5hbCBhZ2VuZGEg
aXMgbm93IGF2YWlsYWJsZS4NCg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5n
Lzk4L2FnZW5kYS5odG1sDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL21lZXRpbmcvOTgv
YWdlbmRhLnR4dA0KDQpXaGlsZSB0aGlzIGlzIGNvbnNpZGVyZWQgdGhlIGZpbmFsIGFnZW5kYSBm
b3IgcHJpbnRpbmcsIGNoYW5nZXMgbWF5IGJlIG1hZGUgdG8gdGhlIGFnZW5kYSB1cCB1bnRpbCBh
bmQgZHVyaW5nIHRoZSBtZWV0aW5nLiBVcGRhdGVzIHdpbGwgYmUgcmVmbGVjdGVkIG9uIHRoZSB3
ZWIgdmVyc2lvbnMgb2YgdGhlIGFnZW5kYS4gDQoNCkluZm9ybWF0aW9uIGFib3V0IElFVEYgOTgg
aW4gQ2hpY2FnbyBjYW4gYmUgZm91bmQgaGVyZTogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWVldGlu
Zy85OC9pbmRleC5odG1sDQoNCg==


From nobody Thu Mar 16 13:24:11 2017
Return-Path: <nomcom-chair-2016@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E9656129A4C; Thu, 16 Mar 2017 13:24:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2016 <nomcom-chair-2016@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: NomCom 2016-2017: ART AD II (Vacancy 2017)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <148969584985.14225.680735720891410647.idtracker@ietfa.amsl.com>
Date: Thu, 16 Mar 2017 13:24:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_p6lozLPoK3sZOHex0cjSJo1vUM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Mar 2017 20:24:10 -0000

All -

The NomCom is pleased to announce that Adam Roach (Mozilla) has been
selected to serve as the interim ART AD filling the term left vacant by
Alissa Cooper. The IAB approved our selection on March 15, 2017.

The NomCom found that with his history of contributions and 
participation in the area Adam has a skill set  that will compliment the 
current sitting Area Directors. We recognize that this appoint adds an 
additional Mozilla employee to the IESG and increases Mozilla 
representation overall in IETF leadership but we did not find this to be a 
blocking consideration given his qualifications. History has shown that the 
individual ADs and the IESG as a whole manage for these relationships 
very effectively.

Lucy Lynch
NomCom Chair 2016-2017


From nobody Thu Mar 16 17:01:31 2017
Return-Path: <marka@isc.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 76C1C129B7D for <ietf@ietfa.amsl.com>; Thu, 16 Mar 2017 17:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OG-ssTm3IgPd for <ietf@ietfa.amsl.com>; Thu, 16 Mar 2017 17:01:28 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1856D129B74 for <ietf@ietf.org>; Thu, 16 Mar 2017 17:01:28 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id B198D24AE42; Fri, 17 Mar 2017 00:00:04 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 2F58A16007E; Fri, 17 Mar 2017 00:00:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id DB9BD160076; Fri, 17 Mar 2017 00:00:03 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id eT5sRAe61LFA; Fri, 17 Mar 2017 00:00:03 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 564EC160086; Fri, 17 Mar 2017 00:00:03 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 2B90D66F211F; Fri, 17 Mar 2017 10:59:59 +1100 (EST)
To: Arleen Elliott <arleen.elliott@ericsson.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <148858548925.15899.17612125269091849059.idtracker@ietfa.amsl.com> <6725F56E17A2A342B4470C49E21B05FA68CC5C77@eusaamb104.ericsson.se>
Subject: Re: IETF 98 Final Agenda
In-reply-to: Your message of "Thu, 16 Mar 2017 14:21:23 -0000." <6725F56E17A2A342B4470C49E21B05FA68CC5C77@eusaamb104.ericsson.se>
Date: Fri, 17 Mar 2017 10:59:59 +1100
Message-Id: <20170316235959.2B90D66F211F@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o_1sQOf_7vzl3z3cnjkwtvUoVh0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 00:01:29 -0000

In message <6725F56E17A2A342B4470C49E21B05FA68CC5C77@eusaamb104.ericsson.se>, A
rleen Elliott writes:
> Have there been any changes to the agenda since this one was published?

Changes are noted on the agenda when they occur.  There is also
usually a message sent to all registered attendees about agenda
changes.  Most changes happen after the meeting has started.

If you are attending remotely you can still register for no cost
and receive the update messages.

https://datatracker.ietf.org/meeting/96/agenda.html shows lots of
agenda changes (canellations and rescheduling) if you want to see
what to look for.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Mar 16 17:50:31 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C080129BA1; Thu, 16 Mar 2017 17:50:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: dnsop@ietf.org, ietf@ietf.org, draft-ietf-dnsop-nsec-aggressiveuse.all@ietf.org
Subject: Review of draft-ietf-dnsop-nsec-aggressiveuse-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148971181501.14209.5886051803265267418@ietfa.amsl.com>
Date: Thu, 16 Mar 2017 17:50:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t5auIkRvNhjEoth1_H3c_fhAU2A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 00:50:15 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dnsop-nsec-aggressiveuse-??
Reviewer: Joel Halpern
Review Date: 2017-03-16
IETF LC End Date: 2017-03-27
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as a Proposed
Standard.

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:  N/A



From nobody Thu Mar 16 21:53:25 2017
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 6D8F6129BEF for <ietf@ietfa.amsl.com>; Thu, 16 Mar 2017 21:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.396
X-Spam-Level: 
X-Spam-Status: No, score=-5.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MiASr_Gd6MJ7 for <ietf@ietfa.amsl.com>; Thu, 16 Mar 2017 21:53:20 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85C86129BF5 for <ietf@ietf.org>; Thu, 16 Mar 2017 21:53:20 -0700 (PDT)
Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2H4n5TR073357 for <ietf@ietf.org>; Fri, 17 Mar 2017 00:53:17 -0400
Received: from e16.ny.us.ibm.com (e16.ny.us.ibm.com [129.33.205.206]) by mx0b-001b2d01.pphosted.com with ESMTP id 297pv3ryd6-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 17 Mar 2017 00:53:17 -0400
Received: from localhost by e16.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, 17 Mar 2017 00:53:16 -0400
Received: from b01cxnp22036.gho.pok.ibm.com (9.57.198.26) by e16.ny.us.ibm.com (146.89.104.203) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 17 Mar 2017 00:53:14 -0400
Received: from b01ledav006.gho.pok.ibm.com (b01ledav006.gho.pok.ibm.com [9.57.199.111]) by b01cxnp22036.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v2H4rD2P55050266 for <ietf@ietf.org>; Fri, 17 Mar 2017 04:53:14 GMT
Received: from b01ledav006.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2B621AC048 for <ietf@ietf.org>; Fri, 17 Mar 2017 00:53:07 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav006.gho.pok.ibm.com (Postfix) with ESMTPS id E5769AC043 for <ietf@ietf.org>; Fri, 17 Mar 2017 00:53:06 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v2H4rCN1005753 for <ietf@ietf.org>; Fri, 17 Mar 2017 00:53:12 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v2H4rCYo005735 for ietf@ietf.org; Fri, 17 Mar 2017 00:53:12 -0400
From: narten@us.ibm.com
Date: Fri, 17 Mar 2017 00:53:12 -0400
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-TM-AS-GCONF: 00
x-cbid: 17031704-0024-0000-0000-0000021B21DE
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006796; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000206; SDB=6.00834962; UDB=6.00410100; IPR=6.00612617;  BA=6.00005215; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014686; XFM=3.00000013; UTC=2017-03-17 04:53:14
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17031704-0025-0000-0000-000042A121B9
Message-Id: <201703170453.v2H4rCYo005735@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-17_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=89 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703170040
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5OxGHkHsDBYYvwOrUto62D4yBp8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 04:53:23 -0000

Total of 118 messages in the last 7 days.
 
script run at: Fri Mar 17 00:53:07 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.78% |    8 |  5.00% |    59472 | cabo@tzi.org
  3.39% |    4 |  4.36% |    51871 | phill@hallambaker.com
  4.24% |    5 |  3.48% |    41373 | julian.reschke@gmx.de
  3.39% |    4 |  2.91% |    34630 | johnl@taugh.com
  3.39% |    4 |  2.67% |    31796 | jari.arkko@piuha.net
  3.39% |    4 |  2.50% |    29763 | pch-ietf-6@u-1.phicoh.com
  3.39% |    4 |  2.37% |    28233 | stewart.bryant@gmail.com
  2.54% |    3 |  3.11% |    37042 | tjc@ecs.soton.ac.uk
  2.54% |    3 |  3.07% |    36566 | willi.uebelherr@riseup.net
  2.54% |    3 |  2.95% |    35047 | blong@google.com
  2.54% |    3 |  2.61% |    31111 | cowan@ccil.org
  2.54% |    3 |  2.36% |    28035 | touch@isi.edu
  1.69% |    2 |  2.39% |    28455 | badri.subramanyan@ril.com
  0.85% |    1 |  2.96% |    35179 | dromasca@gmail.com
  1.69% |    2 |  1.89% |    22544 | tim.chown@jisc.ac.uk
  1.69% |    2 |  1.89% |    22433 | stephen.farrell@cs.tcd.ie
  1.69% |    2 |  1.80% |    21462 | mellon@fugue.com
  1.69% |    2 |  1.77% |    21037 | leifj@mnt.se
  1.69% |    2 |  1.65% |    19674 | john_leddy@comcast.com
  1.69% |    2 |  1.49% |    17697 | brian.e.carpenter@gmail.com
  0.85% |    1 |  2.31% |    27442 | lionel.morand@orange.com
  1.69% |    2 |  1.43% |    17054 | nico@cryptonector.com
  0.85% |    1 |  2.24% |    26650 | worley@ariadne.com
  1.69% |    2 |  1.35% |    16117 | petejson@codalogic.com
  1.69% |    2 |  1.28% |    15243 | dhc@dcrocker.net
  1.69% |    2 |  1.28% |    15187 | ned+ietf@mauve.mrochek.com
  0.85% |    1 |  2.08% |    24736 | weihaw@google.com
  1.69% |    2 |  1.17% |    13864 | rsk@gsp.org
  1.69% |    2 |  1.14% |    13616 | ietf-dane@dukhovni.org
  1.69% |    2 |  0.91% |    10867 | jmh@joelhalpern.com
  0.85% |    1 |  1.61% |    19194 | ynir.ietf@gmail.com
  0.85% |    1 |  1.56% |    18567 | d3e3e3@gmail.com
  0.85% |    1 |  1.54% |    18315 | mariainesrobles@googlemail.com
  0.85% |    1 |  1.31% |    15620 | suresh.krishnan@ericsson.com
  0.85% |    1 |  1.22% |    14471 | sprevidi@cisco.com
  0.85% |    1 |  1.15% |    13660 | elwynd@dial.pipex.com
  0.85% |    1 |  1.00% |    11950 | linuxwolf@outer-planes.net
  0.85% |    1 |  0.99% |    11815 | otroan@employees.org
  0.85% |    1 |  0.98% |    11710 | joelja@bogus.com
  0.85% |    1 |  0.98% |    11632 | narten@us.ibm.com
  0.85% |    1 |  0.98% |    11620 | xing@cernet.edu.cn
  0.85% |    1 |  0.97% |    11587 | daniel.voyer@bell.ca
  0.85% |    1 |  0.95% |    11352 | j.schoenwaelder@jacobs-university.de
  0.85% |    1 |  0.86% |    10279 | acmorton@att.com
  0.85% |    1 |  0.81% |     9681 | jinmei@wide.ad.jp
  0.85% |    1 |  0.81% |     9647 | bob.hinden@gmail.com
  0.85% |    1 |  0.81% |     9582 | fgont@si6networks.com
  0.85% |    1 |  0.80% |     9503 | rjsparks@nostrum.com
  0.85% |    1 |  0.76% |     9034 | morrowc.lists@gmail.com
  0.85% |    1 |  0.76% |     9018 | mcr+ietf@sandelman.ca
  0.85% |    1 |  0.73% |     8663 | stefan@dilettant.eu
  0.85% |    1 |  0.73% |     8636 | markzzzsmith@gmail.com
  0.85% |    1 |  0.71% |     8456 | alh-ietf@tndh.net
  0.85% |    1 |  0.71% |     8395 | dave@cridland.net
  0.85% |    1 |  0.67% |     7972 | sean@sn3rd.com
  0.85% |    1 |  0.66% |     7820 | arleen.elliott@ericsson.com
  0.85% |    1 |  0.65% |     7788 | dafranke@akamai.com
  0.85% |    1 |  0.63% |     7553 | liushucheng@huawei.com
  0.85% |    1 |  0.62% |     7429 | marka@isc.org
  0.85% |    1 |  0.61% |     7264 | maria.ines.robles@ericsson.com
  0.85% |    1 |  0.59% |     7076 | mrex@sap.com
  0.85% |    1 |  0.54% |     6459 | jared@puck.nether.net
  0.85% |    1 |  0.53% |     6348 | mohta@necom830.hpcl.titech.ac.jp
  0.85% |    1 |  0.47% |     5559 | presnick@qti.qualcomm.com
  0.85% |    1 |  0.47% |     5542 | nomcom-chair-2016@ietf.org
  0.85% |    1 |  0.46% |     5531 | linuxwolf+ietf@outer-planes.net
  0.85% |    1 |  0.46% |     5427 | vijay.gurbani@nokia.com
  0.85% |    1 |  0.45% |     5380 | ron.even.tlv@gmail.com
--------+------+--------+----------+------------------------
100.00% |  118 |100.00% |  1189731 | Total


From nobody Fri Mar 17 07:48:22 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E3EE129461 for <ietf@ietfa.amsl.com>; Fri, 17 Mar 2017 07:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-2WEUWAJrSV for <ietf@ietfa.amsl.com>; Fri, 17 Mar 2017 07:48:18 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A176126C23 for <ietf@ietf.org>; Fri, 17 Mar 2017 07:48:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id E387330048E for <ietf@ietf.org>; Fri, 17 Mar 2017 10:48:17 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id RoGdQlcOnFeW for <ietf@ietf.org>; Fri, 17 Mar 2017 10:48:16 -0400 (EDT)
Received: from [10.5.245.234] (wsip-98-172-24-238.dc.dc.cox.net [98.172.24.238]) by mail.smeinc.net (Postfix) with ESMTPSA id 9D1B9300261; Fri, 17 Mar 2017 10:48:16 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-mmusic-dtls-sdp-22.txt> (Using the SDP Offer/Answer Mechanism for DTLS) to Proposed Standard
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <148975668560.14209.10746850325933103667.idtracker@ietfa.amsl.com>
Date: Fri, 17 Mar 2017 10:48:16 -0400
Cc: draft-ietf-mmusic-dtls-sdp.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E31D7AB4-9EA6-4AF7-B42C-DE74AB9320D2@vigilsec.com>
References: <148975668560.14209.10746850325933103667.idtracker@ietfa.amsl.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OwBHfayEwcF-8RfKBgLK5AKvx-s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 14:48:20 -0000

Since this document is going to be standards-track, I think the contact =
for the dtls-id registration should be the IESG instead of the author.

Russ


> On Mar 17, 2017, at 9:18 AM, The IESG <iesg-secretary@ietf.org> wrote:
>=20
>=20
> The IESG has received a request from the Multiparty Multimedia Session
> Control WG (mmusic) to consider the following document:
> - 'Using the SDP Offer/Answer Mechanism for DTLS'
>  <draft-ietf-mmusic-dtls-sdp-22.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 2017-04-06. 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
>   This document defines the SDP offer/answer procedures for =
negotiating
>   and establishing a DTLS association.  The document also defines the
>   criteria for when a new DTLS association must be established.  The
>   document updates RFC 5763 and RFC 7345, by replacing common SDP
>   offer/answer procedures with a reference to this specification.
>=20
>   This document defines a new SDP media-level attribute, 'dtls-id'.
>=20
>=20
>=20
>=20
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-dtls-sdp/
>=20
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-dtls-sdp/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
>=20
>=20


From nobody Fri Mar 17 08:09:42 2017
Return-Path: <christer.holmberg@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 DAD17129464; Fri, 17 Mar 2017 08:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZtfTdO5Re3Yz; Fri, 17 Mar 2017 08:09:38 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 942B3129479; Fri, 17 Mar 2017 08:09:37 -0700 (PDT)
X-AuditID: c1b4fb3a-3a3ff70000000839-b1-58cbfc2e6eb1
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by  (Symantec Mail Security) with SMTP id 66.70.02105.E2CFBC85; Fri, 17 Mar 2017 16:09:35 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.56]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0319.002; Fri, 17 Mar 2017 16:09:33 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
CC: "draft-ietf-mmusic-dtls-sdp.all@ietf.org" <draft-ietf-mmusic-dtls-sdp.all@ietf.org>
Subject: Re: Last Call: <draft-ietf-mmusic-dtls-sdp-22.txt> (Using the SDP Offer/Answer Mechanism for DTLS) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mmusic-dtls-sdp-22.txt> (Using the SDP Offer/Answer Mechanism for DTLS) to Proposed Standard
Thread-Index: AQHSny2G/Jo6UUkvO0arE4nfgiDciKGZNCWA
Date: Fri, 17 Mar 2017 15:09:32 +0000
Message-ID: <D4F1C8CE.19FD0%christer.holmberg@ericsson.com>
References: <148975668560.14209.10746850325933103667.idtracker@ietfa.amsl.com> <E31D7AB4-9EA6-4AF7-B42C-DE74AB9320D2@vigilsec.com>
In-Reply-To: <E31D7AB4-9EA6-4AF7-B42C-DE74AB9320D2@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <EE05381DE43BFD47BA89570422D7786C@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMIsWRmVeSWpSXmKPExsUyM2J7lK7+n9MRBmsfWVjsuLuDzeLVi5vs Fs82zmdxYPZYsuQnk8eqO19YA5iiuGxSUnMyy1KL9O0SuDJ6dj1hKWgVqGg+vYu1gfEPTxcj J4eEgInE8941jF2MXBxCAusYJR5/6GIDSQgJLGaUuLIxqouRg4NNwEKi+582SFhEwFbi8aJD LCA2s0CkRNeTx2C9wgJNjBLL1/9lgihqZpTYuEMRpFdEwEjiwQEfkDCLgKpE+6sbYCW8AtYS S5vmMEKsamGU2HW4AKScU8BB4uPxBJAwo4CYxPdTa5ggVolL3HoynwniZAGJJXvOM0PYohIv H/9jBbFFBfQklj9fAxVXlPj4ah8jRK+BxPtz85khbGuJLavvQcW1JZYtfM0McY6gxMmZT1gm MIrPQrJuFpL2WUjaZyFpn4WkfQEj6ypG0eLU4uLcdCMjvdSizOTi4vw8vbzUkk2MwKg7uOW3 1Q7Gg88dDzEKcDAq8fB++Hk6Qog1say4MvcQowQHs5II79QPQCHelMTKqtSi/Pii0pzU4kOM 0hwsSuK8ZivvhwsJpCeWpGanphakFsFkmTg4pRoY4wOubZPM23RrHotq0ie/GwblmXPu8f38 fv/dhmt/XOy5eF3N5FvFV8b8iLutxGXqeM2H/6z4qb4/eVOlms8cFpcNiRR48rDfw4G36VvJ rOerK5v3lzLbNgqmZFrOfvp0/upHK+3Cb2VyiU1YtC/7W8iCZ2KFwsweMkXB10zLxIO0rrjN e+SkxFKckWioxVxUnAgAIhocILYCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nAUyth3e7wQSiNDuKKpZhUNwQqI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 15:09:40 -0000

Hi,

>Since this document is going to be standards-track, I think the contact
>for the dtls-id registration should be the IESG instead of the author.

Personally I don=B9t have a strong preference, but there are a number of
similar RFCs where the author is listed. A 30 second search gives me RFC
4853, RFC 4574=8A

In another RFC (sorry, I closed the browser tab and forgot the number) the
WG chair mail address was listed.

So, it seems like there is no strict rule.

Regards,

Christer



>> On Mar 17, 2017, at 9:18 AM, The IESG <iesg-secretary@ietf.org> wrote:
>>=20
>>=20
>> The IESG has received a request from the Multiparty Multimedia Session
>> Control WG (mmusic) to consider the following document:
>> - 'Using the SDP Offer/Answer Mechanism for DTLS'
>>  <draft-ietf-mmusic-dtls-sdp-22.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 2017-04-06. 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
>>   This document defines the SDP offer/answer procedures for negotiating
>>   and establishing a DTLS association.  The document also defines the
>>   criteria for when a new DTLS association must be established.  The
>>   document updates RFC 5763 and RFC 7345, by replacing common SDP
>>   offer/answer procedures with a reference to this specification.
>>=20
>>   This document defines a new SDP media-level attribute, 'dtls-id'.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-dtls-sdp/
>>=20
>> IESG discussion can be tracked via
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-dtls-sdp/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>>=20
>>=20
>


From nobody Fri Mar 17 08:23:28 2017
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 B6C6712949A; Fri, 17 Mar 2017 08:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1EgsATnquOln; Fri, 17 Mar 2017 08:23:26 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2087D12945D; Fri, 17 Mar 2017 08:23:26 -0700 (PDT)
Received: from [10.0.1.39] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v2HFNLV3068431 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 17 Mar 2017 10:23:22 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.39]
From: "Ben Campbell" <ben@nostrum.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
Cc: "Russ Housley" <housley@vigilsec.com>, IETF <ietf@ietf.org>, "draft-ietf-mmusic-dtls-sdp.all@ietf.org" <draft-ietf-mmusic-dtls-sdp.all@ietf.org>
Subject: Re: Last Call: <draft-ietf-mmusic-dtls-sdp-22.txt> (Using the SDP Offer/Answer Mechanism for DTLS) to Proposed Standard
Date: Fri, 17 Mar 2017 10:23:22 -0500
Message-ID: <180882E9-1B76-4D67-9316-6DED119C5B36@nostrum.com>
In-Reply-To: <D4F1C8CE.19FD0%christer.holmberg@ericsson.com>
References: <148975668560.14209.10746850325933103667.idtracker@ietfa.amsl.com> <E31D7AB4-9EA6-4AF7-B42C-DE74AB9320D2@vigilsec.com> <D4F1C8CE.19FD0%christer.holmberg@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TRWm5bok66GYozBGRGBqd3C0naY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 15:23:28 -0000

(as an individual)

I recognize we have not been consistent, but I also favor using the IESG 
address for this sort of thing. It's one of the least ephemeral contacts 
we have. Individuals change addresses and responsibilities. Some people 
use WG lists, but we have more than one WG list kept open way beyond its 
otherwise useful life because of registrations that pointed to it.

Thanks!

Ben.

On 17 Mar 2017, at 10:09, Christer Holmberg wrote:

> Hi,
>
>> Since this document is going to be standards-track, I think the 
>> contact
>> for the dtls-id registration should be the IESG instead of the 
>> author.
>
> Personally I don¹t have a strong preference, but there are a number 
> of
> similar RFCs where the author is listed. A 30 second search gives me 
> RFC
> 4853, RFC 4574Š
>
> In another RFC (sorry, I closed the browser tab and forgot the number) 
> the
> WG chair mail address was listed.
>
> So, it seems like there is no strict rule.
>
> Regards,
>
> Christer
>
>
>
>>> On Mar 17, 2017, at 9:18 AM, The IESG <iesg-secretary@ietf.org> 
>>> wrote:
>>>
>>>
>>> The IESG has received a request from the Multiparty Multimedia 
>>> Session
>>> Control WG (mmusic) to consider the following document:
>>> - 'Using the SDP Offer/Answer Mechanism for DTLS'
>>>  <draft-ietf-mmusic-dtls-sdp-22.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 2017-04-06. 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 defines the SDP offer/answer procedures for 
>>> negotiating
>>>   and establishing a DTLS association.  The document also defines 
>>> the
>>>   criteria for when a new DTLS association must be established.  The
>>>   document updates RFC 5763 and RFC 7345, by replacing common SDP
>>>   offer/answer procedures with a reference to this specification.
>>>
>>>   This document defines a new SDP media-level attribute, 'dtls-id'.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-dtls-sdp/
>>>
>>> IESG discussion can be tracked via
>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-dtls-sdp/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>>
>>>
>>


From nobody Fri Mar 17 08:30:41 2017
Return-Path: <christer.holmberg@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 750D4129479; Fri, 17 Mar 2017 08:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kT_nNGqq6VUj; Fri, 17 Mar 2017 08:30:37 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4ED2B1294A0; Fri, 17 Mar 2017 08:30:37 -0700 (PDT)
X-AuditID: c1b4fb25-0b71498000002d78-93-58cc011b8f80
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by  (Symantec Mail Security) with SMTP id 99.60.11640.B110CC85; Fri, 17 Mar 2017 16:30:35 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.56]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0319.002; Fri, 17 Mar 2017 16:30:08 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>, "draft-ietf-mmusic-dtls-sdp.all@ietf.org" <draft-ietf-mmusic-dtls-sdp.all@ietf.org>
Subject: Re: Last Call: <draft-ietf-mmusic-dtls-sdp-22.txt> (Using the SDP Offer/Answer Mechanism for DTLS) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mmusic-dtls-sdp-22.txt> (Using the SDP Offer/Answer Mechanism for DTLS) to Proposed Standard
Thread-Index: AQHSny2G/Jo6UUkvO0arE4nfgiDciKGZNCWA///hkACAACQYgA==
Date: Fri, 17 Mar 2017 15:29:46 +0000
Message-ID: <D4F1CE1D.19FDF%christer.holmberg@ericsson.com>
References: <148975668560.14209.10746850325933103667.idtracker@ietfa.amsl.com> <E31D7AB4-9EA6-4AF7-B42C-DE74AB9320D2@vigilsec.com> <D4F1C8CE.19FD0%christer.holmberg@ericsson.com> <180882E9-1B76-4D67-9316-6DED119C5B36@nostrum.com>
In-Reply-To: <180882E9-1B76-4D67-9316-6DED119C5B36@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C11BFCACEDFFBC44844E6B00CA727E78@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPIsWRmVeSWpSXmKPExsUyM2K7k64045kIgzXPxS3md55mt9hxdweb xasXN9ktnm2cz+LA4rFkyU8mj1k7n7B4rLrzhTWAOYrLJiU1J7MstUjfLoEro/XVZMaCFrmK j08nMTYwLpDtYuTkkBAwkbj1/wxbFyMXh5DAOkaJGyc3sEM4ixkldiw/ydTFyMHBJmAh0f1P G6RBREBJ4nnzVhYQm1lgGqPEgln+IPXCAk2MEsvX/2WCKGpmlNi4QxHCdpLoun2VDcRmEVCV +PH3GpjNK2At8WdGEzPEsteMEvtW3gJr5hSwl5j78TUziM0oICbx/dQaJoht4hK3nsxngjhb QGLJnvPMELaoxMvH/1hBbFEBPYnlz9dAxRUlPr7axwjyALOApsT6XfoQY6wlJq+7zQ5hK0pM 6X7IDnGPoMTJmU9YJjCKz0KybRZC9ywk3bOQdM9C0r2AkXUVo2hxanFSbrqRsV5qUWZycXF+ nl5easkmRmA0HtzyW3UH4+U3jocYBTgYlXh4P/w8HSHEmlhWXJl7iFGCg1lJhHfqB6AQb0pi ZVVqUX58UWlOavEhRmkOFiVxXrOV98OFBNITS1KzU1MLUotgskwcnFINjFYXVh7beOTX05cC xTOy5jc1/xJV0upO5n2Y9nPHXfXnM2flTfp98qrtX/8j6w7oS6rc5Si8aS389rLLk/efGb6L zF/L2PrgpARrfMm5q9LyLd3zb+2rzU32T9Ljn5hSuPvPjyL+qIilCUv05vrveu0f2udqmZZ1 kEO3135a/TbbM5ZJapatM5RYijMSDbWYi4oTATzV8GDCAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9Tum4zFb2Tbt2cPBCB0okqwI-58>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 15:30:39 -0000

SGksDQoNCkkgd2lsbCBjaGFuZ2UgaXQgdG8gdGhlIElFU0cgYWRkcmVzcyA6KQ0KDQpSZWdhcmRz
LA0KDQpDaHJpc3Rlcg0KDQpPbiAxNy8wMy8xNyAxNzoyMywgIkJlbiBDYW1wYmVsbCIgPGJlbkBu
b3N0cnVtLmNvbT4gd3JvdGU6DQoNCj4oYXMgYW4gaW5kaXZpZHVhbCkNCj4NCj5JIHJlY29nbml6
ZSB3ZSBoYXZlIG5vdCBiZWVuIGNvbnNpc3RlbnQsIGJ1dCBJIGFsc28gZmF2b3IgdXNpbmcgdGhl
IElFU0cNCj5hZGRyZXNzIGZvciB0aGlzIHNvcnQgb2YgdGhpbmcuIEl0J3Mgb25lIG9mIHRoZSBs
ZWFzdCBlcGhlbWVyYWwgY29udGFjdHMNCj53ZSBoYXZlLiBJbmRpdmlkdWFscyBjaGFuZ2UgYWRk
cmVzc2VzIGFuZCByZXNwb25zaWJpbGl0aWVzLiBTb21lIHBlb3BsZQ0KPnVzZSBXRyBsaXN0cywg
YnV0IHdlIGhhdmUgbW9yZSB0aGFuIG9uZSBXRyBsaXN0IGtlcHQgb3BlbiB3YXkgYmV5b25kIGl0
cw0KPm90aGVyd2lzZSB1c2VmdWwgbGlmZSBiZWNhdXNlIG9mIHJlZ2lzdHJhdGlvbnMgdGhhdCBw
b2ludGVkIHRvIGl0Lg0KPg0KPlRoYW5rcyENCj4NCj5CZW4uDQo+DQo+T24gMTcgTWFyIDIwMTcs
IGF0IDEwOjA5LCBDaHJpc3RlciBIb2xtYmVyZyB3cm90ZToNCj4NCj4+IEhpLA0KPj4NCj4+PiBT
aW5jZSB0aGlzIGRvY3VtZW50IGlzIGdvaW5nIHRvIGJlIHN0YW5kYXJkcy10cmFjaywgSSB0aGlu
ayB0aGUNCj4+PiBjb250YWN0DQo+Pj4gZm9yIHRoZSBkdGxzLWlkIHJlZ2lzdHJhdGlvbiBzaG91
bGQgYmUgdGhlIElFU0cgaW5zdGVhZCBvZiB0aGUNCj4+PiBhdXRob3IuDQo+Pg0KPj4gUGVyc29u
YWxseSBJIGRvbsK5dCBoYXZlIGEgc3Ryb25nIHByZWZlcmVuY2UsIGJ1dCB0aGVyZSBhcmUgYSBu
dW1iZXINCj4+IG9mDQo+PiBzaW1pbGFyIFJGQ3Mgd2hlcmUgdGhlIGF1dGhvciBpcyBsaXN0ZWQu
IEEgMzAgc2Vjb25kIHNlYXJjaCBnaXZlcyBtZQ0KPj4gUkZDDQo+PiA0ODUzLCBSRkMgNDU3NMWg
DQo+Pg0KPj4gSW4gYW5vdGhlciBSRkMgKHNvcnJ5LCBJIGNsb3NlZCB0aGUgYnJvd3NlciB0YWIg
YW5kIGZvcmdvdCB0aGUgbnVtYmVyKQ0KPj4gdGhlDQo+PiBXRyBjaGFpciBtYWlsIGFkZHJlc3Mg
d2FzIGxpc3RlZC4NCj4+DQo+PiBTbywgaXQgc2VlbXMgbGlrZSB0aGVyZSBpcyBubyBzdHJpY3Qg
cnVsZS4NCj4+DQo+PiBSZWdhcmRzLA0KPj4NCj4+IENocmlzdGVyDQo+Pg0KPj4NCj4+DQo+Pj4+
IE9uIE1hciAxNywgMjAxNywgYXQgOToxOCBBTSwgVGhlIElFU0cgPGllc2ctc2VjcmV0YXJ5QGll
dGYub3JnPg0KPj4+PiB3cm90ZToNCj4+Pj4NCj4+Pj4NCj4+Pj4gVGhlIElFU0cgaGFzIHJlY2Vp
dmVkIGEgcmVxdWVzdCBmcm9tIHRoZSBNdWx0aXBhcnR5IE11bHRpbWVkaWENCj4+Pj4gU2Vzc2lv
bg0KPj4+PiBDb250cm9sIFdHIChtbXVzaWMpIHRvIGNvbnNpZGVyIHRoZSBmb2xsb3dpbmcgZG9j
dW1lbnQ6DQo+Pj4+IC0gJ1VzaW5nIHRoZSBTRFAgT2ZmZXIvQW5zd2VyIE1lY2hhbmlzbSBmb3Ig
RFRMUycNCj4+Pj4gIDxkcmFmdC1pZXRmLW1tdXNpYy1kdGxzLXNkcC0yMi50eHQ+IGFzIFByb3Bv
c2VkIFN0YW5kYXJkDQo+Pj4+DQo+Pj4+IFRoZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNpc2lv
biBpbiB0aGUgbmV4dCBmZXcgd2Vla3MsIGFuZA0KPj4+PiBzb2xpY2l0cw0KPj4+PiBmaW5hbCBj
b21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29tbWVudHMg
dG8NCj4+Pj4gdGhlDQo+Pj4+IGlldGZAaWV0Zi5vcmcgbWFpbGluZyBsaXN0cyBieSAyMDE3LTA0
LTA2LiBFeGNlcHRpb25hbGx5LCBjb21tZW50cw0KPj4+PiBtYXkNCj4+Pj4gYmUNCj4+Pj4gc2Vu
dCB0byBpZXNnQGlldGYub3JnIGluc3RlYWQuIEluIGVpdGhlciBjYXNlLCBwbGVhc2UgcmV0YWlu
IHRoZQ0KPj4+PiBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0
ZWQgc29ydGluZy4NCj4+Pj4NCj4+Pj4gQWJzdHJhY3QNCj4+Pj4NCj4+Pj4NCj4+Pj4gICBUaGlz
IGRvY3VtZW50IGRlZmluZXMgdGhlIFNEUCBvZmZlci9hbnN3ZXIgcHJvY2VkdXJlcyBmb3INCj4+
Pj4gbmVnb3RpYXRpbmcNCj4+Pj4gICBhbmQgZXN0YWJsaXNoaW5nIGEgRFRMUyBhc3NvY2lhdGlv
bi4gIFRoZSBkb2N1bWVudCBhbHNvIGRlZmluZXMNCj4+Pj4gdGhlDQo+Pj4+ICAgY3JpdGVyaWEg
Zm9yIHdoZW4gYSBuZXcgRFRMUyBhc3NvY2lhdGlvbiBtdXN0IGJlIGVzdGFibGlzaGVkLiAgVGhl
DQo+Pj4+ICAgZG9jdW1lbnQgdXBkYXRlcyBSRkMgNTc2MyBhbmQgUkZDIDczNDUsIGJ5IHJlcGxh
Y2luZyBjb21tb24gU0RQDQo+Pj4+ICAgb2ZmZXIvYW5zd2VyIHByb2NlZHVyZXMgd2l0aCBhIHJl
ZmVyZW5jZSB0byB0aGlzIHNwZWNpZmljYXRpb24uDQo+Pj4+DQo+Pj4+ICAgVGhpcyBkb2N1bWVu
dCBkZWZpbmVzIGEgbmV3IFNEUCBtZWRpYS1sZXZlbCBhdHRyaWJ1dGUsICdkdGxzLWlkJy4NCj4+
Pj4NCj4+Pj4NCj4+Pj4NCj4+Pj4NCj4+Pj4gVGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYQ0K
Pj4+PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW1tdXNpYy1k
dGxzLXNkcC8NCj4+Pj4NCj4+Pj4gSUVTRyBkaXNjdXNzaW9uIGNhbiBiZSB0cmFja2VkIHZpYQ0K
Pj4+PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW1tdXNpYy1k
dGxzLXNkcC9iYWxsb3QvDQo+Pj4+DQo+Pj4+DQo+Pj4+IE5vIElQUiBkZWNsYXJhdGlvbnMgaGF2
ZSBiZWVuIHN1Ym1pdHRlZCBkaXJlY3RseSBvbiB0aGlzIEktRC4NCj4+Pj4NCj4+Pj4NCj4+Pj4N
Cj4+Pj4NCj4+Pg0KDQo=


From nobody Fri Mar 17 10:06:55 2017
Return-Path: <rraszuk@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 440CC1294D7; Fri, 17 Mar 2017 10:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ci80OPErU3q3; Fri, 17 Mar 2017 10:06:52 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B52BF1294E2; Fri, 17 Mar 2017 10:06:51 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id p64so69590993qke.1; Fri, 17 Mar 2017 10:06:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=huimbzT9igR/bgBFRaprpyktSNkywhaUOls6goEODII=; b=aYvZh/NEigMsn21ealOIviDnh2Jw4bqAs7w8ekDpX4CjYBgOzZ0qHKaQMvyxi0g04A goucK6da+ruFduj63TCb+vVC3iyY+x3sW4QPXC2UD79tstsH7g0f4biSWdos1REoGvyz xGBsEExDluTsw/1vSkRmpQnjBRVUpwXkhV7PR7Ke+nkbDtXOUD+RWpb0AY3YJ9i5lU2s geLemNQdnXdP9c1411eDsLK4M8AGNj1ljIiJiPBdqM2ffceClvTrUOKqsaZStlu3XdTW AQF8PQUHx23mLYxTIzdjfUl2YXPJN0t5n9YhoMwujynTtHi8m7D8j89F1BZJPId88CwL SiBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=huimbzT9igR/bgBFRaprpyktSNkywhaUOls6goEODII=; b=L5O0tEJnOwnRlKJchCNllTxI4BaBcD4XobYSAflDLWa5DreWp9+SW3lvm62rpyzvwZ Kt9FYexMhYGNMURznwgQ0xJy2baTkqcEwXIBVGhJKJIVweAY4vIAwe/X4dF8mmndFARN xxZjSZVtZtT4qa6oBSUxbUxftie9GJRtCs+bQJHuZ+RyUW5N5BlOHfMOvyFqXeM39xSs Ll7bp+daazwdku8ybtG3yEJsF1VJgu5g+WOhSuXTcHQFpwZzmlMOVUiMNqmRV5K9eojh 5dM0u3mI0PLQG0Xhh8Wv1T3+thV9i+0PNKSRDWmP7Ox852HPapMIfGelHOZULTVcBh2B iVPA==
X-Gm-Message-State: AFeK/H3V3G8e2xy998Emhi7u0NOfwadGysqnXQ3ZJOxSwFe0vvYJ9XE5itZadPACt06/7QMAF/VXDPbVjGH44A==
X-Received: by 10.55.18.158 with SMTP id 30mr15235848qks.123.1489770410840; Fri, 17 Mar 2017 10:06:50 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.140.42.181 with HTTP; Fri, 17 Mar 2017 10:06:50 -0700 (PDT)
In-Reply-To: <DE16D91D-AE7B-4D3C-B8EA-0CB644FB96BD@cable.comcast.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <37ED3E78-B23A-4D29-8597-5A63236129B1@cisco.com> <887bd0f0-32a5-56f1-9ac9-703ecb97a760@gmail.com> <80D8FFF0-2674-48A7-A935-11681F5C5A4D@jisc.ac.uk> <A67E1C07-282B-4422-A2FF-86F6CACBD775@cable.comcast.com> <ab7c95a5-9776-24b5-7c26-4c5987d4c948@isi.edu> <ed2f5144-52fb-dda5-1fb4-62be1625b341@gmail.com> <401F52B1-3D41-4174-9425-50571B2D0B9E@jisc.ac.uk> <6d51de4b-3a9d-0f34-1cd2-5bb30caed75e@gmail.com> <DE16D91D-AE7B-4D3C-B8EA-0CB644FB96BD@cable.comcast.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 17 Mar 2017 18:06:50 +0100
X-Google-Sender-Auth: yQdN172Lkto47_f-fiWIUpf3rA4
Message-ID: <CA+b+ER=6dXLiwvLJa84uvpVeH0daGnZ-06P16JD0UutTrbUYyA@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: "Leddy, John" <John_Leddy@comcast.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Tim Chown <Tim.Chown@jisc.ac.uk>, Brian E Carpenter <brian.e.carpenter@gmail.com>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1146f48222a79f054af03437
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VCEfrca8RLAaksSvRnsuiidzZdI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 17:06:54 -0000

--001a1146f48222a79f054af03437
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

All,

This is very interesting thread indeed.

I think header insertion at *any* network element be it host, router,
service chain device is highly desired. IPv6 deployments will be much more
successful if we clear any obstacles which otherwise prevent it from
delivering required by customers and operators functionality.

And I would state that this should be not only limited to one's own IGP or
BGP domain. It should be legal Internet wide.

Today Internet as a entire system lacks tools to accomplish path
engineering, fast connectivity restoration, p2mp delivery of content etc
... Some of those are possible with MPLS based tools however as we all know
MPLS has no NNI and does not really work across domains. Here we stand very
close to have a chance to fix it.

And if one would forbid by spec the header insertion performed by network
elements what's the alternative ... IPv6 in IPv6 encapsulation which may
suffer with even more overhead yet will still require IANA allocation of
SRH type as well as TLV codepoints as effectively encapsulating network
element will be acting as IPv6 sender.

Concluding I do hope that we can try to collectively make IPv6 protocol
flexible enough to satisfy customer and operator's requirements what in
turn will enrich and speed up IPv6 global adoption.

Kind regards,
Robert.


On Thu, Mar 16, 2017 at 1:40 PM, Leddy, John <John_Leddy@comcast.com> wrote=
:

> Thanks Stewart,
>
> This really supports my point and hopefully not the intent or result of
> the discussions here.
>
> We are trying to work through the IETF process to come up with standards
> and solutions that address real operational challenges faced in
> deployments.  For operators, dealing with legacy and migrations are a big
> challenge.
>
> Wishing these issues away and as a result having non-standard
> functionality in =E2=80=9Cmiddle boxes=E2=80=9D that are ignored in the a=
rchitecture is not
> productive.  NATs are a way of life, dark space is being deployed by othe=
r
> operators, =E2=80=9CCloud=E2=80=9D/NFV/ServiceChaining are active areas; =
tunnels, tunnels
> everywhere - PMTU is always an issue.  =E2=80=9CTurtles and Tunnels all t=
he way
> down=E2=80=9D.
>
> We are very aggressively migrating to a V6 infrastructure, but there is a
> large amount of old legacy systems/applications/services that need to be
> addressed.  At the same time the allure of =E2=80=9CCloud=E2=80=9D attrac=
ts systems that
> should never be moved without being re-architected and the virtualization
> environments fully supporting V6 (both Vendors and OpenSource) =E2=80=93 =
but they
> do move and vendors help make that possible.
>
> Hopefully we can keep the discussions going and keep tools available unti=
l
> we know we have solutions to deal all the activity happening outside a
> clean end-to-end Architecture,
>
> John
>
>
>
> On 3/16/17, 6:44 AM, "Stewart Bryant" <stewart.bryant@gmail.com> wrote:
>
>     > In another form, the answer to John is that there are no protocol
> police,
>     > so what consenting adults do inside their own networks simply isn't
> an
>     > issue that an Internet-wide spec can or should address.
>
>     That is not quite true, the inability to gain an IANA allocated
>     codepoint can make long
>     term private deployments very difficult, either for the protocol
>     squatting on a codepoint
>     because they could not get one allocated, or to the deployment of a n=
ew
>     protocol
>     legitimately allocated a conflicting codepoint.
>
>     - Stewart
>
>
>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--001a1146f48222a79f054af03437
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">All,</div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></div>=
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">This is very interesting thread indeed.=C2=A0</div><div =
class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fon=
t-size:small"><br></div><div class=3D"gmail_default" style=3D"font-family:a=
rial,helvetica,sans-serif;font-size:small">I think header insertion at *any=
* network element be it host, router, service chain device is highly desire=
d. IPv6 deployments will be much more successful if we clear any obstacles =
which otherwise prevent it from delivering required by customers and operat=
ors functionality.=C2=A0</div><div class=3D"gmail_default" style=3D"font-fa=
mily:arial,helvetica,sans-serif;font-size:small"><br></div><div class=3D"gm=
ail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:smal=
l">And I would state that this should be not only limited to one&#39;s own =
IGP or BGP domain. It should be legal Internet wide.=C2=A0</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,=
helvetica,sans-serif;font-size:small">Today Internet as a entire system lac=
ks tools to accomplish path engineering, fast connectivity restoration, p2m=
p delivery of content etc ... Some of those are possible with MPLS based to=
ols however as we all know MPLS has no NNI and does not really work across =
domains. Here we stand very close to have a chance to fix it.=C2=A0</div><d=
iv class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;=
font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-famil=
y:arial,helvetica,sans-serif;font-size:small">And if one would forbid by sp=
ec the header insertion performed by network elements what&#39;s the altern=
ative ... IPv6 in IPv6 encapsulation which may suffer with even more overhe=
ad yet will still require IANA allocation of SRH type as well as TLV codepo=
ints as effectively encapsulating network element will be acting as IPv6 se=
nder.</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetic=
a,sans-serif;font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small">Concluding I do=
 hope that we can try to collectively make IPv6 protocol flexible enough to=
 satisfy customer and operator&#39;s requirements what in turn will enrich =
and speed up IPv6 global adoption.</div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div =
class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fon=
t-size:small">Kind regards,</div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif;font-size:small">Robert.</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small"><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Thu, Mar 16, 2017 at 1:40 PM, Leddy, John <span dir=3D"ltr">&lt;=
<a href=3D"mailto:John_Leddy@comcast.com" target=3D"_blank">John_Leddy@comc=
ast.com</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">Thanks Stew=
art,<br>
<br>
This really supports my point and hopefully not the intent or result of the=
 discussions here.<br>
<br>
We are trying to work through the IETF process to come up with standards an=
d solutions that address real operational challenges faced in deployments.=
=C2=A0 For operators, dealing with legacy and migrations are a big challeng=
e.<br>
<br>
Wishing these issues away and as a result having non-standard functionality=
 in =E2=80=9Cmiddle boxes=E2=80=9D that are ignored in the architecture is =
not productive.=C2=A0 NATs are a way of life, dark space is being deployed =
by other operators, =E2=80=9CCloud=E2=80=9D/NFV/ServiceChaining are active =
areas; tunnels, tunnels everywhere - PMTU is always an issue.=C2=A0 =E2=80=
=9CTurtles and Tunnels all the way down=E2=80=9D.<br>
<br>
We are very aggressively migrating to a V6 infrastructure, but there is a l=
arge amount of old legacy systems/applications/services that need to be add=
ressed.=C2=A0 At the same time the allure of =E2=80=9CCloud=E2=80=9D attrac=
ts systems that should never be moved without being re-architected and the =
virtualization environments fully supporting V6 (both Vendors and OpenSourc=
e) =E2=80=93 but they do move and vendors help make that possible.<br>
<br>
Hopefully we can keep the discussions going and keep tools available until =
we know we have solutions to deal all the activity happening outside a clea=
n end-to-end Architecture,<br>
<br>
John<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
On 3/16/17, 6:44 AM, &quot;Stewart Bryant&quot; &lt;<a href=3D"mailto:stewa=
rt.bryant@gmail.com">stewart.bryant@gmail.com</a>&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 &gt; In another form, the answer to John is that there are no=
 protocol police,<br>
=C2=A0 =C2=A0 &gt; so what consenting adults do inside their own networks s=
imply isn&#39;t an<br>
=C2=A0 =C2=A0 &gt; issue that an Internet-wide spec can or should address.<=
br>
<br>
=C2=A0 =C2=A0 That is not quite true, the inability to gain an IANA allocat=
ed<br>
=C2=A0 =C2=A0 codepoint can make long<br>
=C2=A0 =C2=A0 term private deployments very difficult, either for the proto=
col<br>
=C2=A0 =C2=A0 squatting on a codepoint<br>
=C2=A0 =C2=A0 because they could not get one allocated, or to the deploymen=
t of a new<br>
=C2=A0 =C2=A0 protocol<br>
=C2=A0 =C2=A0 legitimately allocated a conflicting codepoint.<br>
<br>
=C2=A0 =C2=A0 - Stewart<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">-----------------------=
-------<wbr>------------------------------<wbr>--------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr=
>listinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
</div></div></blockquote></div><br></div>

--001a1146f48222a79f054af03437--


From nobody Fri Mar 17 10:24:26 2017
Return-Path: <ietf@rozanak.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13ACE1294FF for <ietf@ietfa.amsl.com>; Fri, 17 Mar 2017 10:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9E_HYKp1YQb4 for <ietf@ietfa.amsl.com>; Fri, 17 Mar 2017 10:24:24 -0700 (PDT)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AE731294EF for <ietf@ietf.org>; Fri, 17 Mar 2017 10:24:24 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 1A49F25CA1D6 for <ietf@ietf.org>; Fri, 17 Mar 2017 17:24:22 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.rozanak.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kEYPKlMNXbBO for <ietf@ietf.org>; Fri, 17 Mar 2017 18:24:21 +0100 (CET)
Received: from localhost.localdomain (unknown [85.195.101.213]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id 591BC25CA0BB for <ietf@ietf.org>; Fri, 17 Mar 2017 18:24:21 +0100 (CET)
To: "ietf@ietf.org" <ietf@ietf.org>
From: Hosnieh Rafiee <ietf@rozanak.com>
Subject: anybody working on Socks5 RFC
Message-ID: <7200841d-320f-3752-03ab-f723d34383a4@rozanak.com>
Date: Fri, 17 Mar 2017 18:24:20 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------B3075C47394730FC0A9038B4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OB9X5BBNXHYvGUKxY1tw_luMWmo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 17:24:25 -0000

This is a multi-part message in MIME format.
--------------B3075C47394730FC0A9038B4
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hello,

Is there anybody who is still active in the area of Socks5 RFC?

If so please send just reply to me and not to IETF group.

Thanks,

Best,

Hosnieh


--------------B3075C47394730FC0A9038B4
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><font size="-1"><font face="Times New Roman, Times, serif">Hello,</font></font></p>
    <p>Is there anybody who is still active in the area of Socks5 RFC?</p>
    <p>If so please send just reply to me and not to IETF group.</p>
    <p>Thanks,</p>
    <p>Best,</p>
    <p>Hosnieh<br>
    </p>
  </body>
</html>

--------------B3075C47394730FC0A9038B4--


From nobody Fri Mar 17 11:18:09 2017
Return-Path: <jrmitche@puck.nether.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D207A129524; Fri, 17 Mar 2017 11:18:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jon Mitchell <jrmitche@puck.nether.net>
To: <ops-dir@ietf.org>
Cc: draft-ietf-rtcweb-overview.all@ietf.org, rtcweb@ietf.org, ietf@ietf.org
Subject: Review of draft-ietf-rtcweb-overview-18
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148977468781.13113.11027871370786405378@ietfa.amsl.com>
Date: Fri, 17 Mar 2017 11:18:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JVPlBHiIutRdAQZghPmTF2MhnmE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 18:18:08 -0000

Reviewer: Jon Mitchell
Review result: Ready

I have reviewed this document as part of the Operational directorate's

ongoing effort to review all IETF documents being processed by the
IESG.  These 
comments were written with the intent of improving the operational
aspects of the 
IETF drafts. Comments that are not addressed in last call may be
included in AD reviews 
during the IESG review.  Document editors and WG chairs should treat
these comments 
just like any other last call comments. 

This document is an overall of the WebRTC protocols that are
considered a "minimum" set to claim compliance with the standard the
draft sets forth.  As far as I can tell, no new protocols or
implementation details are contained in the draft and operational
concerns largely are covered (or not) by the many referenced protocol
specifications within it.  Therefore, I believe this draft is Ready,
although there is some question in my mind of whether this is actually
a standards track versus best current practice document as
interoperability from the standpoint of this document seems to not
require any new on the wire negotiation (outside of each individual's
protocols negotiations).



From nobody Fri Mar 17 12:01:08 2017
Return-Path: <jrmitche@puck.nether.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 86D6C1294E6; Fri, 17 Mar 2017 12:01:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jon Mitchell <jrmitche@puck.nether.net>
To: <ops-dir@ietf.org>
Cc: draft-ietf-ippm-twamp-time-format.all@ietf.org, ietf@ietf.org, ippm@ietf.org
Subject: Review of draft-ietf-ippm-twamp-time-format-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148977726052.13049.17633302885192133866@ietfa.amsl.com>
Date: Fri, 17 Mar 2017 12:01:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6Z8opCvk0G4A4L9RtsJDSRlLf2I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 19:01:01 -0000

Reviewer: Jon Mitchell
Review result: Has Nits

I have reviewed this document as part of the Operational directorate's

ongoing effort to review all IETF documents being processed by the
IESG.  These 
comments were written with the intent of improving the operational
aspects of the 
IETF drafts. Comments that are not addressed in last call may be
included in AD reviews 
during the IESG review.  Document editors and WG chairs should treat
these comments 
just like any other last call comments. 

Ready with Nits - this draft adds the ability to use PTP timestamps as
an alternative to NTP timestamps for active performance measurement
protocols OWAMP and TWAMP.  Although this draft does a good job of
discussing interoperability for both sides of the session having or
not having support for this operational capability, in several places
it states that if a send/receiver support this capability it must be
set to 1 in the flags.  However, only for TWAMP Light mode, this seems
configurable.  This may just be my interpretation, but it probably
should state that local implementations MAY provide a configurable
knob to not negotiate PTPv2 timestamps in section 2.1 and 2.2 even if
the capability is supported by the implementation.



From nobody Fri Mar 17 14:56:46 2017
Return-Path: <bob.hinden@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 BEA2D12961E; Fri, 17 Mar 2017 14:56:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AwfqNDeAW8SS; Fri, 17 Mar 2017 14:56:35 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C7CE129626; Fri, 17 Mar 2017 14:56:34 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id y76so75354600qkb.0; Fri, 17 Mar 2017 14:56:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=aaDJaIdB3AmHu1Z0+1Tg1YVMA1lfCjrYd7zUyOJbwZs=; b=DQVLFA6zli2AgkEM9gDRGrhoGm8SjqiHqIoz23E5IdvxlrN0mf1k2Drlb/jhEQyEFq 686tqSwuS3/8mQnO74j5mXiWqjzT4GKT4f2dKN8G2Mgn0L2QuB2QUtaMi5hhmLySo59G /GKJwoFn8ESN45IqPc8a0yTcZy4FFvlUU1J9TxMOk86N8BKlEVvWXhQRAEBKRktjx/WM MKNHZRUVg5Re424+ry7tFthq+u/gxw9isYZflmdR6xqxmVjgqj1oju5FbrNoyhy+WSdU f7gA3Sq/o/nDc9rWf/MDBZ6WTQ1+hFW+5r4xgA0amcYJQH6qq04AjNQ/2VJAwHDJchWk 3Z9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=aaDJaIdB3AmHu1Z0+1Tg1YVMA1lfCjrYd7zUyOJbwZs=; b=VI0rG+Uiyds0uklVTFeLeInJeVX9Vyb+CBjPrlh7Y7TRM4MAq6Ysu5NxkcwkP3TtMs AUS79tG9IafDTL+Kity5kt6caG4qEpugYqTDok2v3ahQ6WU/zA2IOqTIeGRWn9ri99X7 91Goqd1vccqglhkJOma9vfQOD0G4RE3tgmGNylxEmPkJRJOhIMyxTbtwtVsyjzbYnXPX iYnvvDU0NVjZnRrR4xvjXFKJ8TT5PTyZrRlR6KlCY4V4tg0nSl3oja4KGUxJmwLV/nQS LWTjuETHWrjGqGmy1eQUUIzpp8dytWE18iCadCIdznOgLH2sskHYRCHvmomsHtqxl/Hq JDgQ==
X-Gm-Message-State: AFeK/H2+gVr9eu8tiDqkaZUPwesoeSkCleYGR19WD6rhWfwwyBzP1ctqfKswEChMB2PsJw==
X-Received: by 10.55.33.8 with SMTP id h8mr15192051qkh.223.1489787793386; Fri, 17 Mar 2017 14:56:33 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id 44sm6840438qts.15.2017.03.17.14.56.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Mar 2017 14:56:31 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <804AA9E4-A643-47A3-9FCC-DA1C450E7FB1@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E17C0248-7CD7-4F06-8996-DB275E127C05"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Fri, 17 Mar 2017 14:56:28 -0700
In-Reply-To: <58A33D08.4090505@erg.abdn.ac.uk>
Cc: Bob Hinden <bob.hinden@gmail.com>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
To: gorry@erg.abdn.ac.uk
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UJ767suFE9wKPkOnkP6LnRC9ung>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 21:56:38 -0000

--Apple-Mail=_E17C0248-7CD7-4F06-8996-DB275E127C05
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Gorry,

Thanks for the detailed review.

Several of the reviews have suggested significant changes to this =
document.  The working group was trying to make a few changes to bring =
it into alignment with some changes to rfc2460bis (based on updating =
documents).  It was not attempting a major rewrite when advancing it to =
Internet Standard.  The alternative that the working group discussed was =
to file errata on RFC1981 and leave it to a future document update.

I don=E2=80=99t think many of these changes can be done and still =
advance it to Internet Standard. If we can=E2=80=99t advance the current =
document, then the w.g. may want to just do the errata and withdraw the =
advancement request.  Of course, if people want to work on a revision of =
IPv6 Path MTU Discovery, it would be welcomed, but it won=E2=80=99t be =
able to advanced to Internet Standard.

Comments below.

Thanks,
Bob



> On Feb 14, 2017, at 9:23 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk> =
wrote:
>=20
>=20
> I have some late transport comments on this ID. The update seems to =
retain a lot of thinking that is really historical and I'd really =
encourage people to look again to making the document uptodate.
>=20
> Detailed comments follow.
>=20
> Best wishes,
>=20
> Gorry
>=20
> ----
> The following text strikes me as a little odd in an update:
> " Moreover, TCP implementations that follow the "slow-
>   start" congestion-avoidance algorithm [CONG] typically calculate and
>   cache several other values derived from the PMTU.  It may be simpler
>   to receive asynchronous notification when the PMTU changes, so that
>   these variables may be updated.=E2=80=9D
> - A modern TCP caches at least some path information in the TCB, why =
start with this clause at all:
> "Moreover, TCP implementations that follow the "slow start" =
congestion-avoidance algorithm [CONG] typically calculate and=E2=80=9D
> and simply replace this with something like:
> "TCP implementations=E2=80=9D?
> =E2=80=94=E2=80=94

To clarify, you are suggesting to replace it with:

   TCP implementations typically cache several other values derived
   from the PMTU.  It may be simpler to receive asynchronous =
notification when
   the PMTU changes, so that these variables may be updated.

I think that is editorial, and OK to change.  The paragraph will read:

   The TCP layer must track the PMTU for the path(s) in use by a
   connection; it should not send segments that would result in packets
   larger than the PMTU.  A simple implementation could ask the IP layer
   for this value each time it created a new segment, but this could be
   inefficient.  TCP implementation typically cache several other values
   derived from the PMTU.  It may be simpler to receive asynchronous
   notification when the PMTU changes, so that these variables may be
   updated.
>=20
> The following text also seems to not reflect a modern TCP stack:
> " It is sufficient
>   to treat this as any other dropped segment, and wait until the
>   retransmission timer expires to cause retransmission of the =
segment.=E2=80=9D
> (and following 3 paras).
> Could this be replaced by text that does not exclude modern =
retransmission methods:
> " It is sufficient
>   to treat this in the same way as any other dropped segment, and
>   will be recovered by normal retransmission methods.=E2=80=9D

Yes, resulting in:

   When a Packet Too Big message is received, it implies that a packet
   was dropped by the node that sent the ICMP message.  It is sufficient
   to treat this in the same way as any other dropped segment, and will
   be recovered by normal retransmission methods.  If the Path MTU
   Discovery process requires several steps to find the PMTU of the full
   path, this could delay the connection by many round-trip times.


> =E2=80=94
> There is a block of text that describes retransmission triggered by =
ICMPv6.
> Has this code been implemented in modern releases of TCP?:
> "   Alternatively, the retransmission could be done in immediate =
response
>   to a notification that the Path MTU has changed, but only for the
>   specific connection specified by the Packet Too Big message.=E2=80=9D
> - It seems to expose a number of attack vectors that really should not =
be exposed!!

Are you suggesting remove this text?  Following this text, there are two =
notes.


> ---
> The discussion of NFS may still be a reasonable historic example, but =
to be current it should really refer also to NFSv4/TCP as utlising the =
MTU discovery provided by TCP, since UDP-based NFS is no longer a key =
application.
> =E2=80=94

I was planning to update the reference to NFS to RFC7530.   I could add =
text that says something like:

   It is recommended that NFS running over TCP utilize the MTU discovery
   provided by TCP.

Other suggestions?

> There is no mention that paths including tunnels can eat ICMPv6 PTB =
messages on the tunnel segment, blackholing them, which prevents =
reaching the destination.

As noted above, I think adding discussion about tunnels is out of scope =
of this effort.

> ---
> I think the security consideration is naive!

Suggestions?

>=20
> This statement in particular seems to open DOS vulnerability:
> "
>  When a node receives a Packet Too Big message, it MUST reduce its
>   estimate of the PMTU for the relevant path, based on the value of =
the
>   MTU field in the message."
> - Introdueces a significant vulnerability.  A rogue PTB message that =
reduces the PMTU to a minimum, can result in a path too small to carry =
an encapsulated packet. (Recently noted by Fernando Gont).

Suggestions?

>=20
> Moreover, other layers view ICMP messages with suspicion and have long =
noted the need to check ICMP payload and match only packets that relate =
to actual 5-tuples in use (effectively reducing vulnerability to =
off-path attacks). For example, the Guidelines for UDP, rfc5405bis, =
state:
>=20
> " Applications SHOULD appropriately validate the payload of ICMP
>   messages to ensure these are received in response to transmitted
>   traffic (i.e., a reported error condition that corresponds to a UDP
>   datagram actually sent by the application). =E2=80=A6=E2=80=9C
> - clearly handling this in IP-layer tunnels can be troublesome, but =
that's a problem that should be described, not obscured.

I could add something like the following as a new second paragraph in =
Section 4 Protocol Requirements:

  Protocols SHOULD appropriately validate the payload of ICMPv6 PTB
  messages to ensure these are received in response to transmitted
  traffic (i.e., a reported error condition that corresponds to a UDP
  datagram actually sent by the application).

or similar.


> =E2=80=94=E2=80=94
>=20
> I=E2=80=99d finally  like to add my concerns about the understatement =
of the value of PLPMTUD, which seems to not reflect the recommendations =
to use this method:
> =E2=80=9C  It defines a method for Packetization Layer Path
>   MTU Discovery (PLPMTUD) designed for use over paths where delivery =
of
>   ICMP messages to a host is not assured.=E2=80=9D
> This  seems under-stating the value and recommendations to deploy =
PLMTUD, compared with current transport-area recommendations, for =
instance, the UDP Guidelines provide much more on this important design =
consideration:


The w.g. spent a lot of time on this paragraph.  The intent was to point =
to it, but not into detail of how it worked, nor make it a new =
requirement.  There was some discussion that adding more detail about =
the relationship between PTMUD and PLPMTUD in the ongoing update to IPv6 =
Node Requirements would be helpful.


>=20
> "   Packetization Layer Path MTU Discovery (PLPMTUD) [RFC4821] does =
not
>   rely upon network support for ICMP messages and is therefore
>   considered more robust than standard PMTUD.  It is not susceptible =
to
>   "black holing" of ICMP message.  To operate, PLPMTUD requires =
changes
>   to the way the transport is used, both to transmit probe packets, =
and
>   to account for the loss or success of these probes.  This updates =
not
>   only the PMTU algorithm, it also impacts loss recovery, congestion
>   control, etc.  These updated mechanisms can be implemented within a
>   connection-oriented transport (e.g., TCP, SCTP, DCCP), but are not a
>   part of UDP, but this type of feedback is not typically present for
>   unidirectional applications."
>=20
> ----
>=20
> The examples used in the definition of  "upper layer" and "link" also =
makes this document appear as historic, rather than a new RFC!

As noted above, I think there would be support for a rewrite if some =
folks wanted to take that on.




--Apple-Mail=_E17C0248-7CD7-4F06-8996-DB275E127C05
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYzFuNAAoJEK7rdBF357uojAUH/09MvHP44Q3jQZ/TCpw4SSrH
7iQwuddxtEiaK2x1aFXdxsxPw9y0S7RqPyfo2gbMs03zgmg7Jqz0S2LpvPM/Pql1
Pm64clbqKPaWSiMOW5m3Z34aF0uZ94PkhQn7OtKN304bdXpw2u+yCTsKmtiQjcX7
z7wAW6v9407CWbmA4ZeMEVYw0vul8sxad4IWGIXLRqLkfeMSSuOFZimSFg5CDNpR
jGgUA+GpSQc3IjpmqgJ9hQb1u3PfTKBRT1hiTWwgt8W1uKvr5UQqvc0O8gne6bKK
bMGpWmuwvzUkOFgJXCyy86N9BE/YLFidK3luUJ4cNKc0bFETCSmUhOs7B2TZ+wQ=
=mCAV
-----END PGP SIGNATURE-----

--Apple-Mail=_E17C0248-7CD7-4F06-8996-DB275E127C05--


From nobody Fri Mar 17 14:57:08 2017
Return-Path: <bob.hinden@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 27E9D12961E; Fri, 17 Mar 2017 14:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xelQRPdz89TN; Fri, 17 Mar 2017 14:56:49 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C54EF12962E; Fri, 17 Mar 2017 14:56:48 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id x35so73256646qtc.2; Fri, 17 Mar 2017 14:56:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=VV/zRiqaKOTK3FoqUkNYsCUNj95vvTOF0DMGRtbeYD0=; b=j/GcySico+4veVdwWIKd1kEv994/CEmVPWESe1/m9Wt2Py0AoNR/NhgBp1o7Kz4QAB MDLqeIMssDpnwT/XCNHNgOZO1MSoGyo7bW6Sc7XHsOSoz6uRhkEmcN39oGc0afzcPTJM bMNB0ssy37BRJwaUABUNy1op6Bgze8LKAdDT8YkiC651NpJ9BgyZMBRLRKBlmbms9Job ui0T2HNvGaAe3zx/FG+PxzxQPEOrdLgFnGu1JlPMEBzyEEnBLUoyV92oLL/P+OoXTBVy GGsq5XMWRYZQbwplEvC3xi8QbzdllFLxbJj4xRy9pvzU7udXWQJK4QDNa46M1aqMCqOR u8/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=VV/zRiqaKOTK3FoqUkNYsCUNj95vvTOF0DMGRtbeYD0=; b=gSE2H0mwHROmZr4uHxfY1C/RlF9aMVr3L9nqVaSt8nMjgdKoj0m21LS4oZ0i9ausLc OQ8g1ZcPTN4C0xlIFbILvASMWjBSblcEQXmOfwSKsvvCA+SiEOy0izrUZDn74xgX/PMd 4jIHHpSiCd/PBABp1cFNg5IM0m8yub3jCG1ZZ+C8j9xb0/GiI5gXzF2pHR19wjElNpGk afB4MmzqpYwYLUibFc5oAZhQCMIqrHZjLEYt4S1YxZPEOG/WgfKbEelOVTRWRcYq6eRF Uch7GxfRVfUdTkYa25WJH9uheh9Ieww06hEVX+f/QlUU7BaO8S0urpTlqpHUg3tkVl1g bssg==
X-Gm-Message-State: AFeK/H3x2F9QT2Fwe3/VOrRX8rTw4HjbNhqOnaK1Pf9UMewk2ZK6ln8Trqj8+v+VdmEn2A==
X-Received: by 10.237.38.194 with SMTP id q60mr17076314qtd.84.1489787807709; Fri, 17 Mar 2017 14:56:47 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id 44sm6840438qts.15.2017.03.17.14.56.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Mar 2017 14:56:46 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B4891142-9A32-490E-8AAE-8A8206A40649"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Review of draft-ietf-6man-rfc1981bis-04
Date: Fri, 17 Mar 2017 14:56:45 -0700
In-Reply-To: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, gen-art@ietf.org, IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
To: Stewart Bryant <stewart@g3ysx.org.uk>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rR5U7J-dUFwMV7QMehDBvALCSB0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Mar 2017 21:57:02 -0000

--Apple-Mail=_B4891142-9A32-490E-8AAE-8A8206A40649
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Stewart,

Thanks for the detailed review.  I am responding after reading the email =
thread that resulted, some issues were closed.

Several of the reviews have suggested significant changes to this =
document.  The working group was trying to make a few changes to bring =
it into alignment with some changes to rfc2460bis (based on updating =
documents).  It was not attempting a major rewrite when advancing it to =
Internet Standard.  The alternative that the working group discussed was =
to file errata on RFC1981 and leave it to a future document update.

I don=E2=80=99t think many of these changes can be done and still =
advance it to Internet Standard. If we can=E2=80=99t advance the current =
document, then the w.g. may want to just do the errata and withdraw the =
advancement request.  Of course, if people want to work on a revision of =
IPv6 Path MTU Discovery, it would be welcomed, but it won=E2=80=99t be =
able to advanced to Internet Standard.

Comments below.

Thanks,
Bob


> On Feb 9, 2017, at 7:19 AM, Stewart Bryant <stewart@g3ysx.org.uk> =
wrote:
>=20
> Reviewer: Stewart Bryant
> Review result: Almost Ready
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-6man-rfc1981bis-04
> Reviewer: Stewart Bryant
> Review Date: 9/Feb/2017
> IETF LC End Date: 1/Mar/2017
> IESG Telechat date: unknown
>=20
> Summary: This draft is on the right track but has open issues,
> described in the review.
>=20
> This review together with the lengthy discussion on the IETF list
> suggest that this draft has a number of issues that need to be
> addressed  before publication.
>=20
> I wonder if we would best serve both our future and our heritage
> if we declared RFC1981 as historic, and either left the idea there,
> or declared it as historic and wrote a new text from a clean start?
>=20
>=20

I think this was closed in the email thread.


> Major issues:
>=20
> Nits points out a number of faults with the document, but the only
> one of substance is:
>=20
> The text has a lot of RFC2119 language, but no RFC2119 declaration.
>=20
> The document could use a thorough RFC2119 scrub

Based on in an earlier another review, our AD suggested an update to =
Shepard Writeup instead of adding something to the document.  It says:

   This document is an update to RFC1981 that was published prior to
   RFC2119 being published.  Consequently while it does use =
"should/must"
   style language in upper and lower case, the document does not cite =
the
   RFC2119 definitions.  Since the changes in this update were very
   limited, the w.g. concluded to not change any of this language.


>=20
> The document lists the three original authors one with an affiliation
>=20
> change, but no email addresses. Has this been agreed with the
> original
> authors, and have arrangements been put in place for the RFC editor
> to process auth48?

I contacted the original authors and they didn=E2=80=99t express any =
interest in being involved in this update.  They haven=E2=80=99t =
participated in the IETF for many years.  I can contact them during =
AUTH48, or the AD can override this requirement for this document.

>=20
> It is concerning that the draft does not talk in any detail about
> how modern ECMP works, i.e. using the five tuple, and noting that
> the PMTU may be different depending on the transport layer port
> numbers.
>=20

I think this is out of scope.


> Given that a very large fraction of packets will traverse an MPLS
> network at some point, I am surprised that there is no text talking
> about the importance of providing support for this feature in the
> MPLS domain. RFC3988 talks to this point, but is only experimental.
>=20

I think this was closed in the email thread.

> =3D=3D=3D=3D=3D=3D
>=20
>   If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>   could use the flow id as the local representation of a path.
> Packets
>   sent to a particular destination but belonging to different flows
> may
>   use different paths, with the choice of path depending on the flow
>   id.  This approach will result in the use of optimally sized
> packets
>   on a per-flow basis, providing finer granularity than PMTU values
>   maintained on a per-destination basis.
>=20
> SB> How widely is flow-id supported in networks? I thought that the
> SB> current position was that it was unreliable as an ECMP indicator
> SB> and thus routers tended to glean information from the packet
> themselves.

I think this was closed in the email thread.

>=20
> =3D=3D=3D=3D=3D=3D
>=20
>      Note: if the original packet contained a Routing header, the
>      Routing header should be used to determine the location of the
>      destination address within the original packet.  If Segments
> Left
>      is equal to zero, the destination address is in the Destination
>      Address field in the IPv6 header.  If Segments Left is greater
>      than zero, the destination address is the last address
>      (Address[n]) in the Routing header.
>=20
> SB> So this has the effect that a traffic engineered packet and
> SB> a non-traffic engineered packet will have the lower of the
> SB> two PMTUs. This was all harmless when source routing was a
> curiosity
> SB> as far as mainstream networking was concerned, but may be
> SB> more of a problem as a result of the SPRING work.

I think the onus is on SPRING to make sure it doesn=E2=80=99t break =
existing mechanisms.

>=20
> =3D=3D=3D=3D=3D=3D=3D
>=20
>=20
> 5.3.  Purging stale PMTU information
>=20
>   Internetwork topology is dynamic; routes change over time.  While
> the
>   local representation of a path may remain constant, the actual
>   path(s) in use may change.  Thus, PMTU information cached by a
> node
>   can become stale.
>=20
>   If the stale PMTU value is too large, this will be discovered
> almost
>   immediately once a large enough packet is sent on the path.  No
> such
>   mechanism exists for realizing that a stale PMTU value is too
> small,
>   so an implementation should "age" cached values.  When a PMTU
> value
>   has not been decreased for a while (on the order of 10 minutes),
> the
>   PMTU estimate should be set to the MTU of the first-hop link, and
> the
>   packetization layers should be notified of the change.  This will
>   cause the complete Path MTU Discovery process to take place again.
>=20
> SB> Should that be an RFC2119 SHOULD?
> SB> The impact of this advice is going to be a disruption to what
> might
> SB> be a critical service every 10 mins.
> SB> Should there be some advice along the lines of noting the
> SB> importance of service delivery as part of deciding whether to
> SB> test for bigger PMTU vs improving efficiency?
>=20
> =3D=3D=3D=3D=3D=3D=3D
>=20
>=20
> Minor issues:
>=20
>   IPv6 defines a standard mechanism for a node to discover the
>   PMTU of an arbitrary path.
>=20
> SB> Do you mean "This document defines ....."? Otherwise this needs
> SB> a reference.

Will fix.

>=20
> =3D=3D=3D=3D=3D=3D=3D
>=20
>   An extension to Path MTU Discovery defined in this document can be
>   found in [RFC4821].  It defines a method for Packetization Layer
> Path
> SB> Rather than have the reader figure out what "It" is, perhaps
> SB> s/It/RFC4821/

The w.g. noodled on this text for a long time.  I think the =E2=80=9Cit=E2=
=80=9D is clear, but will change to RFC4821.


> =3D=3D=3D=3D=3D=3D=3D
>=20
>=20
>   Upon receipt of such a
>   message, the source node reduces its assumed PMTU for the path
> based
>   on the MTU of the constricting hop as reported in the Packet Too
> Big
>   message.
>=20
> SB> We should perhaps state up front that this procedure
> SB> hunts for the worst case of the ECMP set associated with the
> SB> ingress nodes PMTU classifier.

I think getting into ECMP is out of scope for moving this to IS.


> =3D=3D=3D=3D=3D=3D=3D
>=20
>   If a node receives a Packet Too Big message reporting a next-hop
> MTU
>   that is less than the IPv6 minimum link MTU, it should discard it.
>=20
> SB> Should that be an RFC2119 SHOULD?

See note above.

> =3D=3D=3D=3D=3D=3D=3D
>=20
> 5.2.  Storing PMTU information
>=20
>   Ideally, a PMTU value should be associated with a specific path
>   traversed by packets exchanged between the source and destination
>   nodes.  However, in most cases a node will not have enough
>   information to completely and accurately identify such a path.
>   Rather, a node must associate a PMTU value with some local
>   representation of a path.  It is left to the implementation to
> select
>   the local representation of a path.
>=20
> SB> Is it worth noting the five tuple since that is how a lot of
> SB> load balancers work?

I think getting into ECMP is out of scope for moving this to IS.

> =3D=3D=3D=3D=3D=3D=3D
>=20
>   The set of paths in use to a
>   particular destination is expected to be small, in many cases
>   consisting of a single path.
>=20
> SB> I am not sure that remains true in modern networks.

Do we have any data on this?  I wonder if there will be much difference =
in the PMTU in this case.

> =3D=3D=3D=3D=3D=3D=3D
>=20
>   One approach to implementing PMTU aging is to associate a
> timestamp
>   field with a PMTU value.  This field is initialized to a
> "reserved"
>   value, indicating that the PMTU is equal to the MTU of the first
> hop
>   link.  Whenever the PMTU is decreased in response to a Packet Too
> Big
>   message, the timestamp is set to the current time.
>=20
>   Once a minute, a timer-driven procedure runs through all cached
> PMTU
>   values, and for each PMTU whose timestamp is not "reserved" and is
>   older than the timeout interval:
>=20
>   -  The PMTU estimate is set to the MTU of the first hop link.
>=20
>   -  The timestamp is set to the "reserved" value.
>=20
>   -  Packetization layers using this path are notified of the
> increase.
>=20
>=20
> SB> Such detailed implementation advice is uncommon in modern RFCs. It
> has
> SB> the disadvantage of de-facto standardizing something that should
> be left to
> SB> the innovation of the implementer.

Can you point to any harm this has caused?  It is very widely =
implemented.

>=20
> =3D=3D=3D=3D=3D=3D=3D
>=20
> 5.4.  TCP layer actions
>=20
> SB> TCP implementations have moved on a lot since this section was
> SB> written. Is this still current best practise?
>=20
> =3D=3D=3D=3D=3D=3D=3D
>=20
> 5.5.  Issues for other transport protocols
>=20
>   Some transport protocols (such as ISO TP4 [ISOTP]) are not allowed
> to
>   repacketize when doing a retransmission.
>=20
> SB> How much TP4 is there going over IPv6? Doesn't this example
> SB> show the IETF as not being in the modern age?


I have no information one way or another.  I have heard there is some =
TP4 on airplanes, may they will move it to IPv6 :-)

>=20
> =3D=3D=3D=3D=3D=3D=3D
>=20
> Nits/editorial comments:
>=20
>   upper layer         a protocol layer immediately above IPv6.
>                       Examples are transport protocols such as TCP
> and
>                       UDP, control protocols such as ICMP, routing
>                       protocols such as OSPF, and internet or lower-
>                       layer protocols being "tunneled" over (i.e.,
>                       encapsulated in) IPv6 such as IPX, AppleTalk,
> or
>                       IPv6 itself.
>=20
> SB> Everything in the list above is in the well known list, except
> SB> IPX, so technically it needs expansion. However it might be nice
> SB> to use some modern example in common use.

I will add a reference to IPX.  The best reference I have found to IPX =
is:

       Novell, Inc., "Advanced NetWare V2.1 Internetwork Packet Exchange
       Protocol (IPX) with Asynchronous Event Scheduler (AES)", October
       1986.

Please suggest something better.


> =3D=3D=3D=3D=3D=3D=3D
>=20
>   link                a communication facility or medium over which
>                       nodes can communicate at the link layer, i.e.,
>                       the layer immediately below IPv6.  Examples
> are
>                       Ethernets (simple or bridged); PPP links;
> X.25,
>                       Frame Relay, or ATM networks; and internet (or
>                       higher) layer "tunnels", such as tunnels over
>                       IPv4 or IPv6 itself.
>=20
> SB> Technically X.25 needs a reference, since it is not "well known=E2=80=
=9D

Will add a reference, if you think it is necessary.

> =3D=3D=3D=3D=3D=3D=3D
>=20
>   path                the set of links traversed by a packet between
> a
>                       source node and a destination node.
>=20
> SB> Is it a set of links, or a set of links and nodes?

I think the current text is OK.

>=20
> =3D=3D=3D=3D=3D=3D=3D=3D
>=20
>    the value of MMS_S, the "maximum send transport-message size".
> SB> The modern convention is full-name(abbreviation)

I don=E2=80=99t follow this.

>=20
> =3D=3D=3D=3D=3D=3D=3D=3D
>=20
>   The Sun Network File System (NFS) uses a Remote Procedure Call
> (RPC)
>   protocol [RPC] that, when used over UDP, in many cases will
> generate
>   payloads that must be fragmented even for the first-hop link.
> This
>   might improve performance in certain cases, but it is known to
> cause
>   reliability and performance problems, especially when the client
> and
>   server are separated by routers.
>=20
> SB> Perhaps this should point to RFC7530 (the current NFS Spec),
> assuming
> SB> the behaviour description is still correct.

Will do.

>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>   The former can be accomplished by associating a flag with the
> path;
>   when a packet is sent on a path with this flag set, the IP layer
> does
>   not send packets larger than the IPv6 minimum link MTU.
>=20
> SB> We do not normally give this level of implementation advice

I think it varies a lot.

>=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=

>=20
>=20
>=20


--Apple-Mail=_B4891142-9A32-490E-8AAE-8A8206A40649
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYzFudAAoJEK7rdBF357uoUyUH/2woOWoFtDbAFeegeqdFq1/g
D0HY5duq6FJeM6TmjxNz7OsaQmfCjAhW9unQl4LR8ma384vFziqjt2S8XrYWFtSp
s6L4WHXg8u47Xysft4sjSqK9CbqaERKFRFC8b+S6WsCfP6xHxwn2RvUGfD5S+4Ub
G+dkzOpvnPstT+97rPFFCq3px5Ztl7kd7CKgp2z8zoHi5nbSV2adIH6Eciq4bo8d
owk37ZrC22IuHLbjEHAKevTE/hsQSVnRR2TbO6IPP9Bt0T80ZtalDfVTg6OP/vuN
V8cH+Ded8eKLti9WNaAerQxYeK9r0dBWTRqdTjAchLoqpnEvDT8tvJk5DhjNWh8=
=0Tht
-----END PGP SIGNATURE-----

--Apple-Mail=_B4891142-9A32-490E-8AAE-8A8206A40649--


From nobody Sat Mar 18 05:03:27 2017
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 61CFA127011 for <ietf@ietfa.amsl.com>; Sat, 18 Mar 2017 05:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CgteLz1jytWR for <ietf@ietfa.amsl.com>; Sat, 18 Mar 2017 05:03:21 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 227AA126C2F for <ietf@ietf.org>; Sat, 18 Mar 2017 05:03:20 -0700 (PDT)
Received: (qmail 47209 invoked from network); 18 Mar 2017 12:04:36 -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; 18 Mar 2017 12:04:36 -0000
Subject: Re: Operational feedback on PMTUD
To: ietf@ietf.org
References: <cef9e432-e6a8-5f90-f61d-67278561cb2f@necom830.hpcl.titech.ac.jp>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <40fb8d3d-927b-a7e1-a724-fe332a4a10ca@necom830.hpcl.titech.ac.jp>
Date: Sat, 18 Mar 2017 21:03:11 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <cef9e432-e6a8-5f90-f61d-67278561cb2f@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=iso-2022-jp; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qr8DBzgl8fwqUbi_NFIB5zoc1Hs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Mar 2017 12:03:25 -0000

I wrote:

> Just a procedural question.
>
> Though rfc2026 says:
>
>    A specification for which significant implementation and successful
>    operational experience has been obtained may be elevated to the
>    Internet Standard level.  An Internet Standard (which may simply be
>    referred to as a Standard) is characterized by a high degree of
>    technical maturity and by a generally held belief that the specified
>    protocol or service provides significant benefit to the Internet
>    community.
>
> does rfc1981bis qualify?

But, no response yet.

> It seems to me that rfc1981 operationally failed

For example, see my presentation at APNIC32

	How Path MTU Discovery Doesn't work
	https://meetings.apnic.net/__data/assets/file/0018/38214/pathMTU.pdf

as a proof accepted by operational community that rfc1981 style
PMTUD has been, is and will continue to be failing.

							Masataka Ohta


From nobody Sat Mar 18 21:29:46 2017
Return-Path: <jrmitche@puck.nether.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B69129477; Sat, 18 Mar 2017 21:29:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jon Mitchell <jrmitche@puck.nether.net>
To: <ops-dir@ietf.org>
Cc: draft-ietf-homenet-dot.all@ietf.org, homenet@ietf.org, ietf@ietf.org
Subject: Review of draft-ietf-homenet-dot-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148989778041.21449.11458841609929936240@ietfa.amsl.com>
Date: Sat, 18 Mar 2017 21:29:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sdVNOanLqurhif0yW0IXzm3AqNs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Mar 2017 04:29:40 -0000

Reviewer: Jon Mitchell
Review result: Has Issues

I have reviewed this document as part of the Operational directorate's

ongoing effort to review all IETF documents being processed by the
IESG.  These 
comments were written with the intent of improving the operational
aspects of the 
IETF drafts. Comments that are not addressed in last call may be
included in AD reviews 
during the IESG review.  Document editors and WG chairs should treat
these comments 
just like any other last call comments. 

Overall - document has issues, could likely benefit from further
reviews.  This document was asked for early review by with a specific
request instructions to look at in context of RFC6761 definition of
special use domain names as well as from the operational implications
of having an unsigned root zone.  Having read the document and a
number of related works that I found useful in understanding further
the implications of this document (such as those laid out by
draft-ietf-dnsop-sutld-ps-03), I think it would be useful for this
document to go through an additional further early review by dnsop
working group directly, however here is my non-DNS expert feedback:

This document does spell out handling for .homenet as required by
RFC6761, specifically in Section 3 of the draft, and does seem to
adequately fit under the definition of a special used domain name,
primarily only based on the difference of user experience with the
domain (criteria #1).  That said, I have several concerns with the
wording in this draft regarding criteria in this section, here they
are in the same numbered list as in the draft (and as required by
RFC6761).

1.  This does not adequately identify that users should not treat
.homenet like any other domain name in the sense that entries in this
top level domain are pretty much guaranteed to be non-unique, and
likely this will pose general confusion, service reachability, as well
as security concerns that are somewhat glossed over as well in the
security considerations section of the draft.

2.  All though this states that applications should not consider
.homenet domain has having an elevation of security, user facing
applications may want to actually notify users of the special behavior
of this domain and the fact that it is more insecure as the names are
not globally unique and using them outside of the local networking
environment will likely have unexpected results.  Further applications
are pretty much guaranteed to not be able to have certificate based
trust of the hosts at this domain since they are not globally unique.

3.  No issues with section wording which basically prescribes no
difference from normal DNS behavior, although this section is a bit
verbose about how a host gets it's nameservers, which seems
unnecessary.

4.  This section is a bit confusing as it says that .homenet is
effectively a locally served zone as described by RFC6303, but then
there is no request for IANA to add this to the locally served zones
registry which was established by that RFC, not to mention that
registry does not currently contain any non reverse zones today.  My
reading is that homenet's desired behavior for this and section 5 are
similar to the description of the .test domain handling in RFC6761,
and I'm curious (not familiar with history or timing of the two
documents) that none of the domain handling in RFC6761 defer to
RFC6303 for specification handling like .homenet tries to do here.

5 and 6.  Similar concern as above, wonder why same wording as
prescribed for .test domain in RFC6761 is not used for .homenet

7.  No concerns.

Concerns with security considerations - user surprise (and threat) is
something that is basically being designed into this use case, as well
as is the need to disable DNSSEC and some of the ability to use
certain types of certificate based application security that relies on
CA trust based on names.  This doesn't feel adequately called out.

IANA considerations - as described below section doesn't mention
locally served zone registry, although it's unclear as described above
whether or not that's really the behavior desired.



From nobody Sun Mar 19 17:20:12 2017
Return-Path: <suresh.krishnan@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 8A1A7129434; Sun, 19 Mar 2017 17:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZxX7H0ytN_g; Sun, 19 Mar 2017 17:20:00 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0F6412702E; Sun, 19 Mar 2017 17:20:00 -0700 (PDT)
X-AuditID: c6180641-c3fff70000000a06-a8-58ced9d3cf7f
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by  (Symantec Mail Security) with SMTP id ED.9F.02566.3D9DEC85; Sun, 19 Mar 2017 20:19:51 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0319.002; Sun, 19 Mar 2017 20:19:54 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>, 6man WG <ipv6@ietf.org>
Subject: IETF Last Call conclusion for draft-ietf-6man-rfc4291bis-07
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc4291bis-07
Thread-Index: AQHSoQ+vtzlHxC1V3kSVc+LLDJ9iTA==
Date: Mon, 20 Mar 2017 00:19:49 +0000
Message-ID: <4892552B-1467-480C-8BFF-CE468D85221D@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_23B4D3B3-BFCD-4CCC-AC7E-9A57F4CFB460"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyuXRPoO71m+ciDM6uYLR4tnE+i8XLs++Z HJg8liz5yRTAGMVlk5Kak1mWWqRvl8CVcWPOA8aCNtOKu5MusDcwLjLqYuTkkBAwkWh9N5m9 i5GLQ0hgPaNEz7IlrCAJIYHljBKrZuaA2GxARRt2fmYCsUUEbCRm7uoFquHgEBZwkZh3Owwi 7CnR9vEIK4StJzH5ZScziM0ioCrRsr0RLM4rYC/xY/YUNhCbUUBM4vupNWAjmQXEJW49mc8E cY+IxMOLp9kgbFGJl4//sULYShJzXl9jBrmTWWAKo8TfhjvsEEMFJU7OfMIygVFwFpJZs5DV zUJSB1GkLbFs4WvmWUA/MAvoSExeyAgRNpV4ffQjlG0tMePXQTYIW1FiSvdD9gWMHKsYOUqL C3Jy040MNzECY+CYBJvjDsa9vZ6HGAU4GJV4eD/MORchxJpYVlyZe4hRBaj10YbVFxilWPLy 81KVRHiFeM5HCPGmJFZWpRblxxeV5qQWH2KU5mBREue9HnI/XEggPbEkNTs1tSC1CCbLxMEp 1cBYdPThd1sbr0PtXLsjsh1P/9KY6B50z2d6X6N47ZY8HcH/28Sr3BOYj0uv/uewrOqh69oH Ufvu9G1kUXJNCm5m7Squl114UsImy17lRXuz5hQmnm2VW/8LS5sqf2r/8iN0U4HkD9WrKRxy JYXMrq/cGn59X2XYcqz0AMNsvp3OThpnHx/236/EUpyRaKjFXFScCACaYNdfiQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XiD1s4TNLeTYmAHKVU6cg2QMbzA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 00:20:02 -0000

--Apple-Mail=_23B4D3B3-BFCD-4CCC-AC7E-9A57F4CFB460
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all,
 Thanks to everyone who commented during the IETF Last Call of =
draft-ietf-6man-rfc4291bis-07. The IETF last call discussion for this =
draft was passionate (and sometimes heated). The discussion was mainly =
focused on the 64-bit boundary in IPv6 addressing and the associated =
text in Section 2.4. I have had a lot of private one to one and group =
discussions with several folks who had commented and contributed text =
suggestions to get a better idea of their concerns. There seems to be a =
strong divide between parts of the community on whether this restriction =
should stay or be relaxed. Looking at the viewpoints expressed and how =
wide apart they are, it has become clear that there is a lack of =
consensus to advance the current draft as Internet Standard. Based on =
this lack of consensus, I have decided to return the draft back to the =
working group to continue discussion.

Thanks
Suresh=

--Apple-Mail=_23B4D3B3-BFCD-4CCC-AC7E-9A57F4CFB460
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzIwMDAxOTUxWjAjBgkqhkiG9w0B
CQQxFgQUPhz5nZag4/gk0lDrGZlMqRjjhSMwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQBbTu3YBpc0rFVPfbnQaHoOtofzuXnc6IPL27rDVTnjAnDIhfptjYF24mLwDzrn
Bv2jAWYEJdx8KMgH0s3A1IBmT1Ufzgljbz8e+XRSd3fr87Pa6ERqIGvt2DUyIuOfU3/utV+DQ9o6
OuW0FnmKGzJk35DR9a85j7sSrHR/MqjIafI4Di1QqGbDWidhx2n7ospVRTm1MODqXZrZQ9hB/sOC
zg2WBxWz57KaSEll5G2wpGlgu4HfSKgSVmPulTkshGEPlf+gvAXMb9nzn2oXX2ibh/IHVwcYAD0s
VuNmt92doGjVIzHW/r2bUpzxEiKWRSLDYcgC8yrFsF+B0kqWwEagAAAAAAAA

--Apple-Mail=_23B4D3B3-BFCD-4CCC-AC7E-9A57F4CFB460--


From nobody Sun Mar 19 20:23:05 2017
Return-Path: <suresh.krishnan@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 3734D12953C for <ietf@ietfa.amsl.com>; Sun, 19 Mar 2017 20:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1sfvOs-Z3JWW for <ietf@ietfa.amsl.com>; Sun, 19 Mar 2017 20:23:02 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2FD8129539 for <ietf@ietf.org>; Sun, 19 Mar 2017 20:23:01 -0700 (PDT)
X-AuditID: c618062d-d5fff700000009d8-6d-58cf5c55251a
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by  (Symantec Mail Security) with SMTP id C0.C2.02520.55C5FC85; Mon, 20 Mar 2017 05:36:38 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0319.002; Sun, 19 Mar 2017 23:23:00 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Operational feedback on PMTUD
Thread-Topic: Operational feedback on PMTUD
Thread-Index: AQHSnXrlIiuO0bxsS0ehhjpJGMRNeaGax1KAgAKTNwA=
Date: Mon, 20 Mar 2017 03:22:39 +0000
Message-ID: <B092BBEE-E707-436A-BF94-BCF232A6C067@ericsson.com>
References: <cef9e432-e6a8-5f90-f61d-67278561cb2f@necom830.hpcl.titech.ac.jp> <40fb8d3d-927b-a7e1-a724-fe332a4a10ca@necom830.hpcl.titech.ac.jp>
In-Reply-To: <40fb8d3d-927b-a7e1-a724-fe332a4a10ca@necom830.hpcl.titech.ac.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_07F7CD4B-5F32-420E-AD02-72A2B537713F"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMIsWRmVeSWpSXmKPExsUyuXRPlG5YzPkIg9+tkhbPNs5nsdh90MiB yWPJkp9MHhNbdzEGMEVx2aSk5mSWpRbp2yVwZdxa5FawJqVi6ZNv7A2MbdFdjJwcEgImEqu+ bGYDsYUE1jNK3Jwn1MXIBWQvZ5SY/quNFSTBBlS0YednJhBbBMi+snULWJxZQFni6aY5YHFh AS2JnZ9WsUDUaEvM/PqLGcK2kmho/8DexcjBwSKgKnF/px1ImFfAXmLNujXsELsmMkosX3QT bA6ngJ9E94SFYAcxCohJfD+1hglil7jErSfzmSCOFpF4ePE0G4QtKvHy8T9WCFtJYs7ra8wg Q5kFpjBK9H3YwQaxTVDi5MwnLBMYRWYhmTULWd0sJHUQRUkS/w6fZoawtSWWLXwNZWtK7O9e zoIpriHR+W0iK4RtKvH66EdGCNtaYsavg2wQtqLElO6H7AsYuVcxcpQWF+TkphsZbGIERucx CTbdHYz3p3seYhTgYFTi4S3gPR8hxJpYVlyZe4hRBaj10YbVFxilWPLy81KVRHjNPIHSvCmJ lVWpRfnxRaU5qcWHGKU5WJTEeeNW3w8XEkhPLEnNTk0tSC2CyTJxcEo1MG5uiLCI5EnefWH2 6oR7973u+y87fuZv/Iyd4jpKB3022C7lTD3R8mBxcNS5Mp+LUZUSEtP79x31Dly49LzgTYYf 8ZtnP59pFrHW+NH25buu77jCGum/ijWkUDMkR6e8zPva9N4t98vTxSY+ZD29+cnyHpO7/7Zt CLb5u5bjteyDzyZzfzXNMGNSYinOSDTUYi4qTgQAbqRAOtYCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Tk3Bp5A2i8GnfTkT-axmza-TYoI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 03:23:04 -0000

--Apple-Mail=_07F7CD4B-5F32-420E-AD02-72A2B537713F
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_86CD212F-098E-4871-90D4-B6908DCA869C"


--Apple-Mail=_86CD212F-098E-4871-90D4-B6908DCA869C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Ohta-san,
  Thanks for your comment.

> On Mar 18, 2017, at 8:03 AM, Masataka Ohta =
<mohta@necom830.hpcl.titech.ac.jp> wrote:
>=20
> I wrote:
>=20
>> Just a procedural question.
>>=20
>> Though rfc2026 says:
>>=20
>>   A specification for which significant implementation and successful
>>   operational experience has been obtained may be elevated to the
>>   Internet Standard level.  An Internet Standard (which may simply be
>>   referred to as a Standard) is characterized by a high degree of
>>   technical maturity and by a generally held belief that the =
specified
>>   protocol or service provides significant benefit to the Internet
>>   community.
>>=20
>> does rfc1981bis qualify?
>=20
> But, no response yet.

In all fairness, your message was received two weeks after the end of a =
four week IETF last call (March 1). The editor and the shepherd are busy =
going through the responses received during the last call period trying =
to converge on text change proposals.

>=20
>> It seems to me that rfc1981 operationally failed
>=20
> For example, see my presentation at APNIC32
>=20
> 	How Path MTU Discovery Doesn't work
> 	=
https://meetings.apnic.net/__data/assets/file/0018/38214/pathMTU.pdf
>=20
> as a proof accepted by operational community that rfc1981 style
> PMTUD has been, is and will continue to be failing.

I went through the presentation (very interesting) and it looks like you =
are talking about multicast PMTUD. Your point about ICMP filtering =
breaking PMTUD is valid has been raised many times during the last call. =
It has not really been *quantified* though (i.e. how much ICMPv6 =
filtering is there on the Internet). One piece of work (from 2012) that =
I am aware of

=
http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-thesis=
.pdf =
<http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-thesi=
s.pdf>

did a fairly large scale study using RIPE Atlas probes (~1000 vantage =
points for IPv4 and ~400 vantage points for IPv6) that showed that =
ICMPv4 was filtered for between 4-6% of the paths while ICMPv6 was =
filtered for only 0.77-1.07% of the paths. I would like to know if there =
is any more recent measurement information that indicates ICMPv6 is not =
workable on the Internet. That would certainly help me judge whether =
1981bis will qualify or not in the =E2=80=9Csuccessful operational =
experience=E2=80=9D.

Thanks
Suresh


--Apple-Mail=_86CD212F-098E-4871-90D4-B6908DCA869C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Ohta-san,<div class=3D"">&nbsp; Thanks for your =
comment.</div><div class=3D""><br class=3D""></div><div =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Mar 18, 2017, at 8:03 AM, Masataka Ohta &lt;<a =
href=3D"mailto:mohta@necom830.hpcl.titech.ac.jp" =
class=3D"">mohta@necom830.hpcl.titech.ac.jp</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">I =
wrote:<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">Just a procedural question.<br class=3D""><br class=3D"">Though=
 rfc2026 says:<br class=3D""><br class=3D""> &nbsp;&nbsp;A specification =
for which significant implementation and successful<br class=3D""> =
&nbsp;&nbsp;operational experience has been obtained may be elevated to =
the<br class=3D""> &nbsp;&nbsp;Internet Standard level. &nbsp;An =
Internet Standard (which may simply be<br class=3D""> =
&nbsp;&nbsp;referred to as a Standard) is characterized by a high degree =
of<br class=3D""> &nbsp;&nbsp;technical maturity and by a generally held =
belief that the specified<br class=3D""> &nbsp;&nbsp;protocol or service =
provides significant benefit to the Internet<br class=3D""> =
&nbsp;&nbsp;community.<br class=3D""><br class=3D"">does rfc1981bis =
qualify?<br class=3D""></blockquote><br class=3D"">But, no response =
yet.<br class=3D""></div></div></blockquote><div><br class=3D""></div>In =
all fairness, your message was received two weeks after the end of a =
four week IETF last call (March 1). The editor and the shepherd are busy =
going through the responses received during the last call period trying =
to converge on text change proposals.</div><div><br class=3D""><blockquote=
 type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">It seems to me that =
rfc1981 operationally failed<br class=3D""></blockquote><br class=3D"">For=
 example, see my presentation at APNIC32<br class=3D""><br =
class=3D""><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>How Path MTU Discovery Doesn't work<br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><a =
href=3D"https://meetings.apnic.net/__data/assets/file/0018/38214/pathMTU.p=
df" =
class=3D"">https://meetings.apnic.net/__data/assets/file/0018/38214/pathMT=
U.pdf</a><br class=3D""><br class=3D"">as a proof accepted by =
operational community that rfc1981 style<br class=3D"">PMTUD has been, =
is and will continue to be failing.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>I =
went through the presentation (very interesting) and it looks like you =
are talking about multicast PMTUD. Your point about ICMP filtering =
breaking PMTUD is valid has been raised many times during the last call. =
It has not really been *quantified* though (i.e. how much ICMPv6 =
filtering is there on the Internet). One piece of work (from 2012) that =
I am aware of</div><div><br class=3D""></div><div><a =
href=3D"http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-ms=
c-thesis.pdf" =
class=3D"">http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes=
-msc-thesis.pdf</a></div><div><br class=3D""></div><div>did a fairly =
large scale study using RIPE Atlas probes (~1000 vantage points for IPv4 =
and ~400 vantage points for IPv6) that showed that ICMPv4 was filtered =
for between 4-6% of the paths while ICMPv6 was filtered for only =
0.77-1.07% of the paths. I would like to know if there is any more =
recent measurement information that indicates ICMPv6 is not workable on =
the Internet. That would certainly help me judge whether 1981bis will =
qualify or not in the =E2=80=9Csuccessful operational =
experience=E2=80=9D.</div><div><br class=3D""></div></div>Thanks</div><div=
 class=3D"">Suresh</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_86CD212F-098E-4871-90D4-B6908DCA869C--

--Apple-Mail=_07F7CD4B-5F32-420E-AD02-72A2B537713F
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzIwMDMyMjM3WjAjBgkqhkiG9w0B
CQQxFgQULoQe9/cFtxxq6sRYLIySOyaQmrMwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQCZSb5k1MCtmT3HUsoHryPYVTsnxeguXAJxfi6oSl0XbFI363HuFxLIsdfUbPg8
O3KN9mkrlW6jwRiY42fpmVKSw8//Zlb3cv7RAqRgBWHc1ZuB29jwiNN+Kl0x+3sDcXI7uIjG1Dar
1gMyAJF9lmEfGPQ4lmlePxxN3Hnovl10nK37iPTUaoq2cejSwmiBhGxDYSanqmK/Y6t/3fROs8lN
zcb16jRC/TG1YhVRdu7HrTvS7ekEKPIgoIQtpdUJJGg5hvqYuwoxGBCWeCcl8YmX0m0K4MHohHoI
6ErzkHJOCTa+ottwpBFGSEJr07OroWww/f3NrYrwRqif2uaXEEqfAAAAAAAA

--Apple-Mail=_07F7CD4B-5F32-420E-AD02-72A2B537713F--


From nobody Sun Mar 19 22:50:39 2017
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 ED1EF129645 for <ietf@ietfa.amsl.com>; Sun, 19 Mar 2017 22:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rQfe9eAh-Pzg for <ietf@ietfa.amsl.com>; Sun, 19 Mar 2017 22:50:34 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 2B3F3129646 for <ietf@ietf.org>; Sun, 19 Mar 2017 22:50:31 -0700 (PDT)
Received: (qmail 71297 invoked from network); 20 Mar 2017 05:51:45 -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; 20 Mar 2017 05:51:45 -0000
Subject: Re: Operational feedback on PMTUD
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <cef9e432-e6a8-5f90-f61d-67278561cb2f@necom830.hpcl.titech.ac.jp> <40fb8d3d-927b-a7e1-a724-fe332a4a10ca@necom830.hpcl.titech.ac.jp> <B092BBEE-E707-436A-BF94-BCF232A6C067@ericsson.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <0bd405cc-c7d4-cbba-a9ab-22748299ea3e@necom830.hpcl.titech.ac.jp>
Date: Mon, 20 Mar 2017 14:50:29 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <B092BBEE-E707-436A-BF94-BCF232A6C067@ericsson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tkss9Fc5wpIiRcu3mVfqoTOLT4c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 05:50:37 -0000

Suresh Krishnan wrote:

>>> Though rfc2026 says:
>>>
>>> A specification for which significant implementation and
>>> successful operational experience has been obtained may be
>>> elevated to the Internet Standard level.  An Internet Standard
>>> (which may simply be referred to as a Standard) is characterized
>>> by a high degree of technical maturity and by a generally held
>>> belief that the specified protocol or service provides
>>> significant benefit to the Internet community.
>>>
>>> does rfc1981bis qualify?

> In all fairness, your message was received two weeks after the end of
> a four week IETF last call (March 1). The editor and the shepherd are
> busy going through the responses received during the last call period
> trying to converge on text change proposals.

So, I can judge that text changes won't resolve operational failures.

Note that I'm not proposing any text change.

Though I now recognize text of rfc1981bis is wrong (ICMPv6-based
PMTUD works even if ICMPv6 packets are sometimes lost, because of
retransmissions by upper layer connection) and rfc1981bis PMTUD
fails with some upper layer connection (e.g. some IoT device
may use connection with retransmission intervals of 20 minutes),
that is not my point on this thread.

But, it should be noted that such failures could be found
with extensive operational experiences on paketization
layer PMTUD, which is one of a reason why PMTUD can be
IS only after packetization layer PMTUD gains much
operational experience and becomes IS.

>> For example, see my presentation at APNIC32
>>
>> How Path MTU Discovery Doesn't work
>> https://meetings.apnic.net/__data/assets/file/0018/38214/pathMTU.pdf

> I went through the presentation (very interesting) and it looks like
> you are talking about multicast PMTUD.

No, as I wrote on page 12:

    Or, as it is already a violation, simply
    – stop generating any ICMP
    – filter all the ICMP
    – “it’s against an RFC” is not a valid criticism

unicast PMTUD is also proven to fail.

Note that destination address of an IPv6 packet in an ICMPv6 PTB
is more than 64B away from the beginning of the IMCPv6 PTB packet
but some network processor can filter packets based only on the
first 64B of a packet, which is why:

    Or, as it is already a violation, simply
    – filter all the ICMP

will be a likely case.

 > Your point about ICMP
> filtering breaking PMTUD is valid has been raised many times during
> the last call.

Yes, for example, on 2017/02/02 9:37 (GMT), Eggert, Lars wrote:

    Given that ICMP delivery cannot be assured over the vast majority
    of paths in the current Internet, should this document make a
    recommendation to implement RFC4821?

so, at least he thinks:

    ICMP delivery cannot be assured over the vast majority
    of paths in the current Internet

 > It has not really been *quantified* though (i.e. how
> much ICMPv6 filtering is there on the Internet).

Do you really think so? Then, that's enough to stop the
draft become IS.

Onus of proof is on those who want to make something IS.

 > One piece of work
> (from 2012) that I am aware of
 >
 > 
http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-thesis.pdf

I'm afraid it is too old. After 2012, those who are not enthusiastic
to deploy IPv6 start deploying it, which means they don't mind
filtering ICMP PTB so much.

Moreover,

>  did a fairly large scale study using RIPE Atlas probes (~1000
> vantage points for IPv4 and ~400 vantage points for IPv6) that showed
> that ICMPv4 was filtered for between 4-6% of the paths while ICMPv6
> was filtered for only 0.77-1.07% of the paths.

0.77~1.07% among ~400 points means 4 or 5 points, too small number
of samples to make statistic variation negligibly small.

> I would like to know
> if there is any more recent measurement information that indicates
> ICMPv6 is not workable on the Internet. That would certainly help me
> judge whether 1981bis will qualify or not in the “successful
> operational experience”.

The more important point of rfc2026 is:

    the specified protocol or service provides
    significant benefit to the Internet community.

and 1% failure possibility is bad enough.

							Masataka Ohta


From nobody Mon Mar 20 02:46:40 2017
Return-Path: <denis@ovsienko.info>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 774C9129A20; Mon, 20 Mar 2017 02:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.797
X-Spam-Level: 
X-Spam-Status: No, score=-4.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ovsienko.info
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTwlWGqBNnHN; Mon, 20 Mar 2017 02:46:37 -0700 (PDT)
Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com [135.84.80.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BF85129A04; Mon, 20 Mar 2017 02:46:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1490003158;  s=zohomail; d=ovsienko.info; i=denis@ovsienko.info; h=Date:From:To:Cc:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; l=6118; bh=MBxEWAU50LNMCUVW0hcH+LJb9Wd/fYfPHskJZHDxim0=; b=cGpHH2Bjb7ZjbGJGur7sV8JvU3A/7R0+okL6/8ObNz3iHHVWgsLxayPgKmyMBbf0 3+A0DM1s98LC2aoljYKMClAjjEZZ+FCnE9HvwwMWEfhFdR98fU1OkZkNnq7ZDo7aDqN H6FNFEO1vTxO7DIivdQgjbKRNNaxe40xVwV/AIJI=
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 14900031585801.5719841635071816; Mon, 20 Mar 2017 02:45:58 -0700 (PDT)
Date: Mon, 20 Mar 2017 09:45:58 +0000
From: Denis Ovsienko <denis@ovsienko.info>
To: <ietf@ietf.org>
Cc: "IETF-Announce" <ietf-announce@ietf.org>,  <draft-ietf-sipcore-status-unwanted@ietf.org>,  <ben@nostrum.com>,  <sipcore@ietf.org>, "Adam Roach" <adam@nostrum.com>,  <sipcore-chairs@ietf.org>
Message-ID: <15aeb1be62a.11b35bf8267637.2121189919710903185@ovsienko.info>
In-Reply-To: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Wsi__oCh6wEpNd9MQH6e_CFfC2E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 09:46:39 -0000

Dear IETF members,

if you can stop the publication below, please stop it now. If you cannot but know someone who can stop it, please ask them now to stop it. There is little time left because the last call for it ends tomorrow.

The goal of IETF is to make Internet better but this document is about to make it worse. A principle of IETF is rough consensus but this document and the implementations arising from it will be toxic for consensus.

This situation is effectively a test of how much sense we have.

============ Forwarded message ============
>From : <denis@ovsienko.info>
To : <draft-ietf-sipcore-status-unwanted.all@ietf.org>
Date : Fri, 17 Mar 2017 16:21:13 +0000
Subject : Re: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
============ Forwarded message ============
 > ---- On Wed, 08 Mar 2017 00:23:06 +0000 The IESG wrote ----  
 > >  
 > >The IESG has received a request from the Session Initiation Protocol Core  
 > >WG (sipcore) to consider the following document:  
 > >- 'A SIP Response Code for Unwanted Calls'  
 > > <draft-ietf-sipcore-status-unwanted-04.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 2017-03-21. 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 defines the 666 (Unwanted) SIP response code, allowing  
 > > called parties to indicate that the call or message was unwanted.  
 > > SIP entities may use this information to adjust how future calls from  
 > > this calling party are handled for the called party or more broadly.  
 > >  
 >  
 > Dear fellow IETF contributors, 
 >  
 > Though draft-ietf-sipcore-status-unwanted is as far in its development as in a last call, there is a point that I believe to be important enough to be raised now. The matter is, it would be very wrong to publish this document with the SIP message code assigned as the number of the beast. 
 >  
 > First of all, this would be wrong because of the end users. The proposed status code will be exposed to the end user base of SIP, which is so large that even a fraction of it is still a large number of real people, so specific consequences must be considered. 
 >  
 > If you mind people that take the Bible and its teachings seriously, it will be easy for them to see it as a personal insult if their phone receives and displays the message as it is proposed, as well as if their phone sends such a message on their behalf. This is not specific to SIP, the same conflict may be caused by a snail mail post, except in real-time communications people have less time to think and step back from the situation. 
 >  
 > As an additional consideration, the document implies that the user receiving the "unwanted" call has a good reason and the user placing the call does not have it, as in spam calls. In the real everyday world it may also be the different way around, for instance, someone may be avoiding calls due to problems with debt, job, alcohol, drugs, whatever, and that someone will just use the biggest "blacklist" button their phone can offer, just because they fail to think. There are other situations where this message code will be used as a handy tool for insulting genuine callers. 
 >  
 > It would be best here not to pour any more gas into this flame, moreover that professional spammers and phishers don't really care how exactly the call was terminated. Whatever status code was returned, they will continue calling numbers from the list until the end of the shift. So this feature as it is proposed may make more damage to normal people rather than to those who seem to be originally targeted. 
 >  
 > Then, if the document gets published and implemented as it is and starts causing grief, eventually people will want to know how the number of the beast got assigned to the message, they will look the document up and see: 
 >  
 > "The particular response code number was chosen to reflect the distaste felt by many upon receiving such calls." 
 >  
 > Which reads "We just needed some number, so we had chosen the number of the beast to make this new feature look cool. We acknowledge this number conveys some particular concept to many people but we deliberately disregard any future side effects." 
 >  
 > This is the only way I can read it, and the only way many other people will be able to read it. This is a fact, please deal with it while you can. 
 >  
 > Hopefully this helps to explain another important aspect. 
 >  
 > Besides the end users, there is the technical audience, both inside and outside of IETF. This audience expects a certain level of professionalism from IETF Standard Track publications. By not meeting those expectations this publication would disappoint the engineers too and lower their motivation to contribute. Simply put, the number of people that think "IETF has less respect to its intended audience than I used to think. They don't make Internet better, they are whim-driven, now that I know it, I better stay away." will increase. And they will actually stay away regardless if things improve afterwards. 
 >  
 > It may seem excess, but let me remind that the world is full of people who are mentally unwell and are on the verge of losing control, to the bad luck of poor strangers that happen to be around at the time. Often it is a tiny thing that finally tips their mind over. You cannot do much about this fact. But you can avoid introducing another potential last straw with an IETF label on it. 
 >  
 > To sum it up, the current revision of the I-D is going to increase the long-term risk of damage to IETF if it is published. I am asking you to change the codepoint to an ordinary nondescript number or to cancel the publication soonest possible. 
 >  
 > Thank you. 
 >  
 > --  
 >  Denis Ovsienko 

-- 
    Denis Ovsienko



From nobody Mon Mar 20 07:23:18 2017
Return-Path: <worley@alum.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 8D155131496 for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 07:23:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tjsl7WNEnIAq for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 07:23:10 -0700 (PDT)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A474131449 for <ietf@ietf.org>; Mon, 20 Mar 2017 07:23:07 -0700 (PDT)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-06v.sys.comcast.net with SMTP id pyCZc7Awxk7AGpyDCcYTps; Mon, 20 Mar 2017 14:23:06 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-19v.sys.comcast.net with SMTP id pyDAcHsmya1xFpyDBcXvG4; Mon, 20 Mar 2017 14:23:06 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v2KEN2Vn022969; Mon, 20 Mar 2017 10:23:02 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v2KEN1ZU022955; Mon, 20 Mar 2017 10:23:01 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Denis Ovsienko <denis@ovsienko.info>
Cc: ietf@ietf.org, sipcore@ietf.org
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
In-Reply-To: <15aeb1be62a.11b35bf8267637.2121189919710903185@ovsienko.info> (denis@ovsienko.info)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 20 Mar 2017 10:23:00 -0400
Message-ID: <87o9ww2fjv.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfKSCUUSaD+JbirTCA7mY+3vOrGqk/ncosy0rt+0sn/YZ0BqMLtTRKYCXIPBlAC2YYB0V9lb/SxANfrJsP7pacpYuSayzcBZobPcg84FV4grij8PHDFpQ UkGUxQvF8JWK9PRKZGI0MyG2uNVCP7hZvwX//liwQOMXzLnJFnOtqww1o/Sq+vA9/agWOvyzzixJc3R/toeiFRZ9EOwifXNS3fU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gO84ORgAVF0_hZ1p6O6EeRwAZbw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 14:23:11 -0000

Denis Ovsienko <denis@ovsienko.info> writes:
> If you mind people that take the Bible and its teachings seriously, it
> will be easy for them to see it as a personal insult if their phone
> receives and displays the message as it is proposed, as well as if
> their phone sends such a message on their behalf. This is not specific
> to SIP, the same conflict may be caused by a snail mail post, except
> in real-time communications people have less time to think and step
> back from the situation. 
 
That seems to be a valid consideration to me:  Embedding
culturally/religiously/politically symbolic identifiers in a protocol in
a way that end users will at least occasionally see is probably not a
good idea.  It's clear even to me that a flippant reference to the
Prophet is asking for trouble, and it seems like we should take
references to the Number of the Beast seriously, given its long history
as a politically powerful symbol.

> As an additional consideration, the document implies that the user
> receiving the "unwanted" call has a good reason and the user placing
> the call does not have it, as in spam calls.

I'm not current on the document, but my understanding is that it makes
clear that the response code is *in the opinion of the recipient* and
must be interpreted as such.  And indeed, that the recipient may have
triggered the response accidentally.

> Besides the end users, there is the technical audience, both inside
> and outside of IETF. This audience expects a certain level of
> professionalism from IETF Standard Track publications. By not meeting
> those expectations this publication would disappoint the engineers too
> and lower their motivation to contribute. Simply put, the number of
> people that think "IETF has less respect to its intended audience than
> I used to think. They don't make Internet better, they are
> whim-driven, now that I know it, I better stay away." will
> increase. And they will actually stay away regardless if things
> improve afterwards. 
 
I think the evidence is that seriousness is not required to attract
technical talent to the IETF.  (See RFCs 439, 527, 748, 968, 1097, 1149,
1216, 1217, 1313, 1437, 1438, 1605, 1606, 1607, 1776, 1882, 1924, 1925,
1926, 1927, 2100, 2321, 2322, 2323, 2324, 2325, 2410, 2549, 2550, 2551,
2795, 3091, 3092, 3093, 3251, 3252, 3514, 3751, 4041, 4042, 4824, 5241,
5242, 5513, 5514, 5841, 5984, 6214, 6217, 6592, 6593, 6919, 6921, 7168,
7169, 7511, and 7514.)  However, there might be a public relations
problem concerning management, politicians, etc.

Dale


From nobody Mon Mar 20 09:05:12 2017
Return-Path: <rsk@gsp.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 BAD6E1294CF for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 09:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ArGqTBviIwH4 for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 09:05:08 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAC96127A91 for <ietf@ietf.org>; Mon, 20 Mar 2017 09:05:07 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v2KG56NU026155 for <ietf@ietf.org>; Mon, 20 Mar 2017 12:05:06 -0400 (EDT)
Date: Mon, 20 Mar 2017 12:05:05 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
Message-ID: <20170320160505.GA31903@gsp.org>
References: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com> <6.2.5.6.2.20170227103644.0cccd7a0@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20170227103644.0cccd7a0@elandnews.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LJoRyle6i_11QAaqkkDzSlUcTrg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 16:05:11 -0000

On Mon, Feb 27, 2017 at 10:56:47AM -0800, S Moonesamy wrote:
> This is the third time that the IAOC has solicited input on a proposed
> statement concerning privacy.  There wasn't any reply to the questions which
> was sent about the second proposed statement.
> 
> Could the IAOC please provide a reply to the questions which were asked
> previously?

I haven't seen any replies to comments made here this time around -- my
apologies to everyone if they've been presented and I'm overlooking them.

---rsk


From nobody Mon Mar 20 10:00:35 2017
Return-Path: <stewart.bryant@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 488281314EA; Mon, 20 Mar 2017 10:00:23 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Atz5LKr1yITU; Mon, 20 Mar 2017 10:00:17 -0700 (PDT)
Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7BFF1314EB; Mon, 20 Mar 2017 10:00:10 -0700 (PDT)
Received: by mail-wr0-x22a.google.com with SMTP id u48so96587174wrc.0; Mon, 20 Mar 2017 10:00:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=vr7v4fxuJaoyAL9kXg13j+/wZL4Jazj4Po+eAS00wDs=; b=qRF3CLZ8NJAnEmrZlx6UAki6ZAhzuDIJCPyhKRaRh2l9H6CIh9SCeKdYBVi6pjjSq1 wvE9a0QjG/oq5l2ycOKupRiWdfmQjSQbqxKYt6yY/xgqxufXzvsG/6n8vJ45LFq97+jS hB3ZlGGPNT9E3IqChH+XKrEb0PYPJZR2iEuHXZfTGuxzZVD8Ro1QRgEa3aGZ108dkIqw DwDR7WSv2JQknlUoaDPk0Fj74KzTD9mFF0HSroaRhScjmDTdsBS6Yr4lFkGA0VgSVErb h6nHu+720u0cyqOTBr+EWi83SSZljqMwe7hKaco+Pgey8Yu+0NsU7awvC01SIVe1RLHM DxJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=vr7v4fxuJaoyAL9kXg13j+/wZL4Jazj4Po+eAS00wDs=; b=eYMEH4QsOUTGE2clzRLyEqVsEYZv/Pr8Gjpk7I3aNkVcEv3V+96ejuCPWq46G3SHcO 0wMa0Jw2Mq0fOkN7SHDUgNI42i/Wfjd/mkgxFteCDEpZjmF2HB53UYOEnbEmJuo6Ywav O25oYE1jD44T388pl1CBdhMHflRP2VTy3Q+nGq+XXr52hUfd5cX9yUQKkLmjODjOZHEa RtKxFoH/XxiGqGAMPjVvtIWsxYtZSVcYI4uDqWUT2wWeyyGQypcFEGnRGIT828dUJlhJ 12afR4sj7kEQEcUTKfMWVi/Cq+P90nFg7PyK8X8ZoFNWVkVca/J9OIuObQOhft+Rmp34 OKzw==
X-Gm-Message-State: AFeK/H3ws7WzwniPcph4F+ZQiYaIOj/EuW4vUlB+xLuSBml7XQWYV3T9xW0knNh7ARQKKg==
X-Received: by 10.223.172.101 with SMTP id v92mr29313481wrc.49.1490029208977;  Mon, 20 Mar 2017 10:00:08 -0700 (PDT)
Received: from [172.16.2.119] (91.75.134.77.rev.sfr.net. [77.134.75.91]) by smtp.gmail.com with ESMTPSA id r8sm21421475wrb.33.2017.03.20.10.00.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Mar 2017 10:00:08 -0700 (PDT)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Bob Hinden <bob.hinden@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com>
Cc: IPv6 List <ipv6@ietf.org>, gen-art@ietf.org, IETF <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <d1d37fe1-8298-02c2-990b-6e9c9e699888@gmail.com>
Date: Mon, 20 Mar 2017 17:00:08 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com>
Content-Type: multipart/alternative; boundary="------------D16124D1E89C620CFECE780A"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-pkOlBih8qdcQTps0x20540eeGY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 17:00:23 -0000

This is a multi-part message in MIME format.
--------------D16124D1E89C620CFECE780A
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit



On 17/03/2017 21:56, Bob Hinden wrote:
> Hi Stewart,
>
> Thanks for the detailed review.  I am responding after reading the email thread that resulted, some issues were closed.
>
> Several of the reviews have suggested significant changes to this document.  The working group was trying to make a few changes to bring it into alignment with some changes to rfc2460bis (based on updating documents).  It was not attempting a major rewrite when advancing it to Internet Standard.  The alternative that the working group discussed was to file errata on RFC1981 and leave it to a future document update.

That might be the way to go.

At the end of the day it is an IESG decision, but I was somewhat 
disquieted by the number of issues and
comments raised across the set of reviewers.

When we elevate a document to standard we are saying that it represents 
a fully baked idea that has no
significant defects. The question given the level of comments is does 
this meet that bar?

>
> I don’t think many of these changes can be done and still advance it to Internet Standard. If we can’t advance the current document, then the w.g. may want to just do the errata and withdraw the advancement request.  Of course, if people want to work on a revision of IPv6 Path MTU Discovery, it would be welcomed, but it won’t be able to advanced to Internet Standard.
Given the level of discussion, I would think that the WG should 
seriously consider a revised version clearing
up the full set of issues raised in discussion.

Responses in line

Best Regards

Stewart

>
> Comments below.
>
> Thanks,
> Bob
>
>
>> On Feb 9, 2017, at 7:19 AM, Stewart Bryant <stewart@g3ysx.org.uk> wrote:
>>
>> Reviewer: Stewart Bryant
>> Review result: Almost Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-6man-rfc1981bis-04
>> Reviewer: Stewart Bryant
>> Review Date: 9/Feb/2017
>> IETF LC End Date: 1/Mar/2017
>> IESG Telechat date: unknown
>>
>> Summary: This draft is on the right track but has open issues,
>> described in the review.
>>
>> This review together with the lengthy discussion on the IETF list
>> suggest that this draft has a number of issues that need to be
>> addressed  before publication.
>>
>> I wonder if we would best serve both our future and our heritage
>> if we declared RFC1981 as historic, and either left the idea there,
>> or declared it as historic and wrote a new text from a clean start?
>>
>>
> I think this was closed in the email thread.
OK
>
>
>> Major issues:
>>
>> Nits points out a number of faults with the document, but the only
>> one of substance is:
>>
>> The text has a lot of RFC2119 language, but no RFC2119 declaration.
>>
>> The document could use a thorough RFC2119 scrub
> Based on in an earlier another review, our AD suggested an update to Shepard Writeup instead of adding something to the document.  It says:
>
>     This document is an update to RFC1981 that was published prior to
>     RFC2119 being published.  Consequently while it does use "should/must"
>     style language in upper and lower case, the document does not cite the
>     RFC2119 definitions.  Since the changes in this update were very
>     limited, the w.g. concluded to not change any of this language.
This is really an IESG decision.

>
>> The document lists the three original authors one with an affiliation
>>
>> change, but no email addresses. Has this been agreed with the
>> original
>> authors, and have arrangements been put in place for the RFC editor
>> to process auth48?
> I contacted the original authors and they didn’t express any interest in being involved in this update.  They haven’t participated in the IETF for many years.  I can contact them during AUTH48, or the AD can override this requirement for this document.

So long as you have an arrangement in place that is acceptable to the 
RFC Editor and IESG.

>> It is concerning that the draft does not talk in any detail about
>> how modern ECMP works, i.e. using the five tuple, and noting that
>> the PMTU may be different depending on the transport layer port
>> numbers.
>>
> I think this is out of scope.

So long as PMTU is bound to the five tuple (which I think it is), then 
the mechanism works, but given the
prevalence of ECMP (pretty much every packet going across the core will 
be sujected to it) I don't think
I agree that a discussion is out of scope.

>
>
>> Given that a very large fraction of packets will traverse an MPLS
>> network at some point, I am surprised that there is no text talking
>> about the importance of providing support for this feature in the
>> MPLS domain. RFC3988 talks to this point, but is only experimental.
>>
> I think this was closed in the email thread.

It was ruled out of scope on the basis that tunnel were out of scope, 
but this tunnel type does need
some special consideration, particularly as nearly every packet crossing 
the Internet goes across
this tunnel type a number of times in its passage.

For me it is ore a question of providing the best advice to the reader, 
rather than minimising change.

>
>> ======
>>
>>    If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>    could use the flow id as the local representation of a path.
>> Packets
>>    sent to a particular destination but belonging to different flows
>> may
>>    use different paths, with the choice of path depending on the flow
>>    id.  This approach will result in the use of optimally sized
>> packets
>>    on a per-flow basis, providing finer granularity than PMTU values
>>    maintained on a per-destination basis.
>>
>> SB> How widely is flow-id supported in networks? I thought that the
>> SB> current position was that it was unreliable as an ECMP indicator
>> SB> and thus routers tended to glean information from the packet
>> themselves.
> I think this was closed in the email thread.
>
>> ======
>>
>>       Note: if the original packet contained a Routing header, the
>>       Routing header should be used to determine the location of the
>>       destination address within the original packet.  If Segments
>> Left
>>       is equal to zero, the destination address is in the Destination
>>       Address field in the IPv6 header.  If Segments Left is greater
>>       than zero, the destination address is the last address
>>       (Address[n]) in the Routing header.
>>
>> SB> So this has the effect that a traffic engineered packet and
>> SB> a non-traffic engineered packet will have the lower of the
>> SB> two PMTUs. This was all harmless when source routing was a
>> curiosity
>> SB> as far as mainstream networking was concerned, but may be
>> SB> more of a problem as a result of the SPRING work.
> I think the onus is on SPRING to make sure it doesn’t break existing mechanisms.

.. or really doesn't break them any more than they discussion on this 
draft suggests that they are
already broken.

>
>> =======
>>
>>
>> 5.3.  Purging stale PMTU information
>>
>>    Internetwork topology is dynamic; routes change over time.  While
>> the
>>    local representation of a path may remain constant, the actual
>>    path(s) in use may change.  Thus, PMTU information cached by a
>> node
>>    can become stale.
>>
>>    If the stale PMTU value is too large, this will be discovered
>> almost
>>    immediately once a large enough packet is sent on the path.  No
>> such
>>    mechanism exists for realizing that a stale PMTU value is too
>> small,
>>    so an implementation should "age" cached values.  When a PMTU
>> value
>>    has not been decreased for a while (on the order of 10 minutes),
>> the
>>    PMTU estimate should be set to the MTU of the first-hop link, and
>> the
>>    packetization layers should be notified of the change.  This will
>>    cause the complete Path MTU Discovery process to take place again.
>>
>> SB> Should that be an RFC2119 SHOULD?
>> SB> The impact of this advice is going to be a disruption to what
>> might
>> SB> be a critical service every 10 mins.
>> SB> Should there be some advice along the lines of noting the
>> SB> importance of service delivery as part of deciding whether to
>> SB> test for bigger PMTU vs improving efficiency?
>>
>> =======
>>
>>
>> Minor issues:
>>
>>    IPv6 defines a standard mechanism for a node to discover the
>>    PMTU of an arbitrary path.
>>
>> SB> Do you mean "This document defines ....."? Otherwise this needs
>> SB> a reference.
> Will fix.
>
>> =======
>>
>>    An extension to Path MTU Discovery defined in this document can be
>>    found in [RFC4821].  It defines a method for Packetization Layer
>> Path
>> SB> Rather than have the reader figure out what "It" is, perhaps
>> SB> s/It/RFC4821/
> The w.g. noodled on this text for a long time.  I think the “it” is clear, but will change to RFC4821.
>
>
>> =======
>>
>>
>>    Upon receipt of such a
>>    message, the source node reduces its assumed PMTU for the path
>> based
>>    on the MTU of the constricting hop as reported in the Packet Too
>> Big
>>    message.
>>
>> SB> We should perhaps state up front that this procedure
>> SB> hunts for the worst case of the ECMP set associated with the
>> SB> ingress nodes PMTU classifier.
> I think getting into ECMP is out of scope for moving this to IS.

Yes, but I don't think you should set elevation to standard above 
providing the best advice, which
is what seems to be proposed here.

>
>
>> =======
>>
>>    If a node receives a Packet Too Big message reporting a next-hop
>> MTU
>>    that is less than the IPv6 minimum link MTU, it should discard it.
>>
>> SB> Should that be an RFC2119 SHOULD?
> See note above.
>
>> =======
>>
>> 5.2.  Storing PMTU information
>>
>>    Ideally, a PMTU value should be associated with a specific path
>>    traversed by packets exchanged between the source and destination
>>    nodes.  However, in most cases a node will not have enough
>>    information to completely and accurately identify such a path.
>>    Rather, a node must associate a PMTU value with some local
>>    representation of a path.  It is left to the implementation to
>> select
>>    the local representation of a path.
>>
>> SB> Is it worth noting the five tuple since that is how a lot of
>> SB> load balancers work?
> I think getting into ECMP is out of scope for moving this to IS.
>
>> =======
>>
>>    The set of paths in use to a
>>    particular destination is expected to be small, in many cases
>>    consisting of a single path.
>>
>> SB> I am not sure that remains true in modern networks.
> Do we have any data on this?  I wonder if there will be much difference in the PMTU in this case.
In a well managed network the point is probably moot since all paths 
should have the same PMTU except
under error conditions, but the path set can be quite large, and 
certainly more that a single path.

>> =======
>>
>>    One approach to implementing PMTU aging is to associate a
>> timestamp
>>    field with a PMTU value.  This field is initialized to a
>> "reserved"
>>    value, indicating that the PMTU is equal to the MTU of the first
>> hop
>>    link.  Whenever the PMTU is decreased in response to a Packet Too
>> Big
>>    message, the timestamp is set to the current time.
>>
>>    Once a minute, a timer-driven procedure runs through all cached
>> PMTU
>>    values, and for each PMTU whose timestamp is not "reserved" and is
>>    older than the timeout interval:
>>
>>    -  The PMTU estimate is set to the MTU of the first hop link.
>>
>>    -  The timestamp is set to the "reserved" value.
>>
>>    -  Packetization layers using this path are notified of the
>> increase.
>>
>>
>> SB> Such detailed implementation advice is uncommon in modern RFCs. It
>> has
>> SB> the disadvantage of de-facto standardizing something that should
>> be left to
>> SB> the innovation of the implementer.
> Can you point to any harm this has caused?  It is very widely implemented.

It tends to result in people treating the example complete with any 
artifacts as normative. Which gives
implementors less scope for optimisation, and can result in restrictions 
beyond the true intent of the
WG.

Now I am not sure if there is a problem here, but I think it is bad 
practise in general.

>
>> =======
>>
>> 5.4.  TCP layer actions
>>
>> SB> TCP implementations have moved on a lot since this section was
>> SB> written. Is this still current best practise?
>>
>> =======
>>
>> 5.5.  Issues for other transport protocols
>>
>>    Some transport protocols (such as ISO TP4 [ISOTP]) are not allowed
>> to
>>    repacketize when doing a retransmission.
>>
>> SB> How much TP4 is there going over IPv6? Doesn't this example
>> SB> show the IETF as not being in the modern age?
>
> I have no information one way or another.  I have heard there is some TP4 on airplanes, may they will move it to IPv6 :-)
It really depends on whether the goal is to elevate what was originally 
written or to provide best current
advice.

>
>> =======
>>
>> Nits/editorial comments:
>>
>>    upper layer         a protocol layer immediately above IPv6.
>>                        Examples are transport protocols such as TCP
>> and
>>                        UDP, control protocols such as ICMP, routing
>>                        protocols such as OSPF, and internet or lower-
>>                        layer protocols being "tunneled" over (i.e.,
>>                        encapsulated in) IPv6 such as IPX, AppleTalk,
>> or
>>                        IPv6 itself.
>>
>> SB> Everything in the list above is in the well known list, except
>> SB> IPX, so technically it needs expansion. However it might be nice
>> SB> to use some modern example in common use.
> I will add a reference to IPX.  The best reference I have found to IPX is:
>
>         Novell, Inc., "Advanced NetWare V2.1 Internetwork Packet Exchange
>         Protocol (IPX) with Asynchronous Event Scheduler (AES)", October
>         1986.
>
> Please suggest something better.

I stand by my original view that we should use modern examples and leave 
it to the IESG to
decide which path they prefer.

>
>
>> =======
>>
>>    link                a communication facility or medium over which
>>                        nodes can communicate at the link layer, i.e.,
>>                        the layer immediately below IPv6.  Examples
>> are
>>                        Ethernets (simple or bridged); PPP links;
>> X.25,
>>                        Frame Relay, or ATM networks; and internet (or
>>                        higher) layer "tunnels", such as tunnels over
>>                        IPv4 or IPv6 itself.
>>
>> SB> Technically X.25 needs a reference, since it is not "well known”
> Will add a reference, if you think it is necessary.
>
>> =======
>>
>>    path                the set of links traversed by a packet between
>> a
>>                        source node and a destination node.
>>
>> SB> Is it a set of links, or a set of links and nodes?
> I think the current text is OK.
>
>> ========
>>
>>     the value of MMS_S, the "maximum send transport-message size".
>> SB> The modern convention is full-name(abbreviation)
> I don’t follow this.

A really minor point. A RFC usually expresses this as

    the maximum send transport-message size (MMS_S), but that is a house style thing.





>
>> ========
>>
>>    The Sun Network File System (NFS) uses a Remote Procedure Call
>> (RPC)
>>    protocol [RPC] that, when used over UDP, in many cases will
>> generate
>>    payloads that must be fragmented even for the first-hop link.
>> This
>>    might improve performance in certain cases, but it is known to
>> cause
>>    reliability and performance problems, especially when the client
>> and
>>    server are separated by routers.
>>
>> SB> Perhaps this should point to RFC7530 (the current NFS Spec),
>> assuming
>> SB> the behaviour description is still correct.
> Will do.
>
>> =========
>>
>>    The former can be accomplished by associating a flag with the
>> path;
>>    when a packet is sent on a path with this flag set, the IP layer
>> does
>>    not send packets larger than the IPv6 minimum link MTU.
>>
>> SB> We do not normally give this level of implementation advice
> I think it varies a lot.
OK

>
>> ========================
>>
>>
>>
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--------------D16124D1E89C620CFECE780A
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 17/03/2017 21:56, Bob Hinden wrote:<br>
    </div>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">Hi Stewart,

Thanks for the detailed review.  I am responding after reading the email thread that resulted, some issues were closed.

Several of the reviews have suggested significant changes to this document.  The working group was trying to make a few changes to bring it into alignment with some changes to rfc2460bis (based on updating documents).  It was not attempting a major rewrite when advancing it to Internet Standard.  The alternative that the working group discussed was to file errata on RFC1981 and leave it to a future document update.</pre>
    </blockquote>
    <br>
    That might be the way to go.<br>
    <br>
    At the end of the day it is an IESG decision, but I was somewhat
    disquieted by the number of issues and<br>
    comments raised across the set of reviewers.<br>
    <br>
    When we elevate a document to standard we are saying that it
    represents a fully baked idea that has no <br>
    significant defects. The question given the level of comments is
    does this meet that bar?<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">

I don’t think many of these changes can be done and still advance it to Internet Standard. If we can’t advance the current document, then the w.g. may want to just do the errata and withdraw the advancement request.  Of course, if people want to work on a revision of IPv6 Path MTU Discovery, it would be welcomed, but it won’t be able to advanced to Internet Standard.</pre>
    </blockquote>
    Given the level of discussion, I would think that the WG should
    seriously consider a revised version clearing<br>
    up the full set of issues raised in discussion.<br>
    <br>
    Responses in line<br>
    <br>
    Best Regards<br>
    <br>
    Stewart<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">

Comments below.

Thanks,
Bob


</pre>
      <blockquote type="cite">
        <pre wrap="">On Feb 9, 2017, at 7:19 AM, Stewart Bryant <a class="moz-txt-link-rfc2396E" href="mailto:stewart@g3ysx.org.uk">&lt;stewart@g3ysx.org.uk&gt;</a> wrote:

Reviewer: Stewart Bryant
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<a class="moz-txt-link-rfc2396E" href="https://trac.ietf.org/trac/gen/wiki/GenArtfaq">&lt;https://trac.ietf.org/trac/gen/wiki/GenArtfaq&gt;</a>.

Document: draft-ietf-6man-rfc1981bis-04
Reviewer: Stewart Bryant
Review Date: 9/Feb/2017
IETF LC End Date: 1/Mar/2017
IESG Telechat date: unknown

Summary: This draft is on the right track but has open issues,
described in the review.

This review together with the lengthy discussion on the IETF list
suggest that this draft has a number of issues that need to be
addressed  before publication.

I wonder if we would best serve both our future and our heritage
if we declared RFC1981 as historic, and either left the idea there,
or declared it as historic and wrote a new text from a clean start?


</pre>
      </blockquote>
      <pre wrap="">
I think this was closed in the email thread.</pre>
    </blockquote>
    OK<br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">


</pre>
      <blockquote type="cite">
        <pre wrap="">Major issues:

Nits points out a number of faults with the document, but the only
one of substance is:

The text has a lot of RFC2119 language, but no RFC2119 declaration.

The document could use a thorough RFC2119 scrub
</pre>
      </blockquote>
      <pre wrap="">
Based on in an earlier another review, our AD suggested an update to Shepard Writeup instead of adding something to the document.  It says:

   This document is an update to RFC1981 that was published prior to
   RFC2119 being published.  Consequently while it does use "should/must"
   style language in upper and lower case, the document does not cite the
   RFC2119 definitions.  Since the changes in this update were very
   limited, the w.g. concluded to not change any of this language.
</pre>
    </blockquote>
    This is really an IESG decision. <br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">
The document lists the three original authors one with an affiliation

change, but no email addresses. Has this been agreed with the
original
authors, and have arrangements been put in place for the RFC editor
to process auth48?
</pre>
      </blockquote>
      <pre wrap="">
I contacted the original authors and they didn’t express any interest in being involved in this update.  They haven’t participated in the IETF for many years.  I can contact them during AUTH48, or the AD can override this requirement for this document.
</pre>
    </blockquote>
    <br>
    So long as you have an arrangement in place that is acceptable to
    the RFC Editor and IESG.<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">
</pre>
      <blockquote type="cite">
        <pre wrap="">
It is concerning that the draft does not talk in any detail about
how modern ECMP works, i.e. using the five tuple, and noting that
the PMTU may be different depending on the transport layer port
numbers.

</pre>
      </blockquote>
      <pre wrap="">
I think this is out of scope.</pre>
    </blockquote>
    <br>
    So long as PMTU is bound to the five tuple (which I think it is),
    then the mechanism works, but given the<br>
    prevalence of ECMP (pretty much every packet going across the core
    will be sujected to it) I don't think<br>
    I agree that a discussion is out of scope. <br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">


</pre>
      <blockquote type="cite">
        <pre wrap="">Given that a very large fraction of packets will traverse an MPLS
network at some point, I am surprised that there is no text talking
about the importance of providing support for this feature in the
MPLS domain. RFC3988 talks to this point, but is only experimental.

</pre>
      </blockquote>
      <pre wrap="">
I think this was closed in the email thread.</pre>
    </blockquote>
    <br>
    It was ruled out of scope on the basis that tunnel were out of
    scope, but this tunnel type does need<br>
    some special consideration, particularly as nearly every packet
    crossing the Internet goes across<br>
    this tunnel type a number of times in its passage.<br>
    <br>
    <tt>For me it is ore a question of providing the best advice to the
      reader, rather than minimising change.<br>
      <br>
    </tt>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">======

  If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
  could use the flow id as the local representation of a path.
Packets
  sent to a particular destination but belonging to different flows
may
  use different paths, with the choice of path depending on the flow
  id.  This approach will result in the use of optimally sized
packets
  on a per-flow basis, providing finer granularity than PMTU values
  maintained on a per-destination basis.

SB&gt; How widely is flow-id supported in networks? I thought that the
SB&gt; current position was that it was unreliable as an ECMP indicator
SB&gt; and thus routers tended to glean information from the packet
themselves.
</pre>
      </blockquote>
      <pre wrap="">
I think this was closed in the email thread.

</pre>
      <blockquote type="cite">
        <pre wrap="">
======

     Note: if the original packet contained a Routing header, the
     Routing header should be used to determine the location of the
     destination address within the original packet.  If Segments
Left
     is equal to zero, the destination address is in the Destination
     Address field in the IPv6 header.  If Segments Left is greater
     than zero, the destination address is the last address
     (Address[n]) in the Routing header.

SB&gt; So this has the effect that a traffic engineered packet and
SB&gt; a non-traffic engineered packet will have the lower of the
SB&gt; two PMTUs. This was all harmless when source routing was a
curiosity
SB&gt; as far as mainstream networking was concerned, but may be
SB&gt; more of a problem as a result of the SPRING work.
</pre>
      </blockquote>
      <pre wrap="">
I think the onus is on SPRING to make sure it doesn’t break existing mechanisms.</pre>
    </blockquote>
    <br>
    .. or really doesn't break them any more than they discussion on
    this draft suggests that they are<br>
    already broken.<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">
=======


5.3.  Purging stale PMTU information

  Internetwork topology is dynamic; routes change over time.  While
the
  local representation of a path may remain constant, the actual
  path(s) in use may change.  Thus, PMTU information cached by a
node
  can become stale.

  If the stale PMTU value is too large, this will be discovered
almost
  immediately once a large enough packet is sent on the path.  No
such
  mechanism exists for realizing that a stale PMTU value is too
small,
  so an implementation should "age" cached values.  When a PMTU
value
  has not been decreased for a while (on the order of 10 minutes),
the
  PMTU estimate should be set to the MTU of the first-hop link, and
the
  packetization layers should be notified of the change.  This will
  cause the complete Path MTU Discovery process to take place again.

SB&gt; Should that be an RFC2119 SHOULD?
SB&gt; The impact of this advice is going to be a disruption to what
might
SB&gt; be a critical service every 10 mins.
SB&gt; Should there be some advice along the lines of noting the
SB&gt; importance of service delivery as part of deciding whether to
SB&gt; test for bigger PMTU vs improving efficiency?

=======


Minor issues:

  IPv6 defines a standard mechanism for a node to discover the
  PMTU of an arbitrary path.

SB&gt; Do you mean "This document defines ....."? Otherwise this needs
SB&gt; a reference.
</pre>
      </blockquote>
      <pre wrap="">
Will fix.

</pre>
      <blockquote type="cite">
        <pre wrap="">
=======

  An extension to Path MTU Discovery defined in this document can be
  found in [RFC4821].  It defines a method for Packetization Layer
Path
SB&gt; Rather than have the reader figure out what "It" is, perhaps
SB&gt; s/It/RFC4821/
</pre>
      </blockquote>
      <pre wrap="">
The w.g. noodled on this text for a long time.  I think the “it” is clear, but will change to RFC4821.


</pre>
      <blockquote type="cite">
        <pre wrap="">=======


  Upon receipt of such a
  message, the source node reduces its assumed PMTU for the path
based
  on the MTU of the constricting hop as reported in the Packet Too
Big
  message.

SB&gt; We should perhaps state up front that this procedure
SB&gt; hunts for the worst case of the ECMP set associated with the
SB&gt; ingress nodes PMTU classifier.
</pre>
      </blockquote>
      <pre wrap="">
I think getting into ECMP is out of scope for moving this to IS.</pre>
    </blockquote>
    <br>
    Yes, but I don't think you should set elevation to standard above
    providing the best advice, which<br>
    is what seems to be proposed here.<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">


</pre>
      <blockquote type="cite">
        <pre wrap="">=======

  If a node receives a Packet Too Big message reporting a next-hop
MTU
  that is less than the IPv6 minimum link MTU, it should discard it.

SB&gt; Should that be an RFC2119 SHOULD?
</pre>
      </blockquote>
      <pre wrap="">
See note above.

</pre>
      <blockquote type="cite">
        <pre wrap="">=======

5.2.  Storing PMTU information

  Ideally, a PMTU value should be associated with a specific path
  traversed by packets exchanged between the source and destination
  nodes.  However, in most cases a node will not have enough
  information to completely and accurately identify such a path.
  Rather, a node must associate a PMTU value with some local
  representation of a path.  It is left to the implementation to
select
  the local representation of a path.

SB&gt; Is it worth noting the five tuple since that is how a lot of
SB&gt; load balancers work?
</pre>
      </blockquote>
      <pre wrap="">
I think getting into ECMP is out of scope for moving this to IS.

</pre>
      <blockquote type="cite">
        <pre wrap="">=======

  The set of paths in use to a
  particular destination is expected to be small, in many cases
  consisting of a single path.

SB&gt; I am not sure that remains true in modern networks.
</pre>
      </blockquote>
      <pre wrap="">
Do we have any data on this?  I wonder if there will be much difference in the PMTU in this case.
</pre>
    </blockquote>
    In a well managed network the point is probably moot since all paths
    should have the same PMTU except<br>
    under error conditions, but the path set can be quite large, and
    certainly more that a single path.<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">
</pre>
      <blockquote type="cite">
        <pre wrap="">=======

  One approach to implementing PMTU aging is to associate a
timestamp
  field with a PMTU value.  This field is initialized to a
"reserved"
  value, indicating that the PMTU is equal to the MTU of the first
hop
  link.  Whenever the PMTU is decreased in response to a Packet Too
Big
  message, the timestamp is set to the current time.

  Once a minute, a timer-driven procedure runs through all cached
PMTU
  values, and for each PMTU whose timestamp is not "reserved" and is
  older than the timeout interval:

  -  The PMTU estimate is set to the MTU of the first hop link.

  -  The timestamp is set to the "reserved" value.

  -  Packetization layers using this path are notified of the
increase.


SB&gt; Such detailed implementation advice is uncommon in modern RFCs. It
has
SB&gt; the disadvantage of de-facto standardizing something that should
be left to
SB&gt; the innovation of the implementer.
</pre>
      </blockquote>
      <pre wrap="">
Can you point to any harm this has caused?  It is very widely implemented.</pre>
    </blockquote>
    <br>
    It tends to result in people treating the example complete with any
    artifacts as normative. Which gives<br>
    implementors less scope for optimisation, and can result in
    restrictions beyond the true intent of the <br>
    WG.<br>
    <br>
    Now I am not sure if there is a problem here, but I think it is bad
    practise in general.<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">
=======

5.4.  TCP layer actions

SB&gt; TCP implementations have moved on a lot since this section was
SB&gt; written. Is this still current best practise?

=======

5.5.  Issues for other transport protocols

  Some transport protocols (such as ISO TP4 [ISOTP]) are not allowed
to
  repacketize when doing a retransmission.

SB&gt; How much TP4 is there going over IPv6? Doesn't this example
SB&gt; show the IETF as not being in the modern age?
</pre>
      </blockquote>
      <pre wrap="">

I have no information one way or another.  I have heard there is some TP4 on airplanes, may they will move it to IPv6 :-)</pre>
    </blockquote>
    It really depends on whether the goal is to elevate what was
    originally written or to provide best current<br>
    advice.<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">
=======

Nits/editorial comments:

  upper layer         a protocol layer immediately above IPv6.
                      Examples are transport protocols such as TCP
and
                      UDP, control protocols such as ICMP, routing
                      protocols such as OSPF, and internet or lower-
                      layer protocols being "tunneled" over (i.e.,
                      encapsulated in) IPv6 such as IPX, AppleTalk,
or
                      IPv6 itself.

SB&gt; Everything in the list above is in the well known list, except
SB&gt; IPX, so technically it needs expansion. However it might be nice
SB&gt; to use some modern example in common use.
</pre>
      </blockquote>
      <pre wrap="">
I will add a reference to IPX.  The best reference I have found to IPX is:

       Novell, Inc., "Advanced NetWare V2.1 Internetwork Packet Exchange
       Protocol (IPX) with Asynchronous Event Scheduler (AES)", October
       1986.

Please suggest something better.</pre>
    </blockquote>
    <br>
    I stand by my original view that we should use modern examples and
    leave it to the IESG to<br>
    decide which path they prefer.<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">


</pre>
      <blockquote type="cite">
        <pre wrap="">=======

  link                a communication facility or medium over which
                      nodes can communicate at the link layer, i.e.,
                      the layer immediately below IPv6.  Examples
are
                      Ethernets (simple or bridged); PPP links;
X.25,
                      Frame Relay, or ATM networks; and internet (or
                      higher) layer "tunnels", such as tunnels over
                      IPv4 or IPv6 itself.

SB&gt; Technically X.25 needs a reference, since it is not "well known”
</pre>
      </blockquote>
      <pre wrap="">
Will add a reference, if you think it is necessary.

</pre>
      <blockquote type="cite">
        <pre wrap="">=======

  path                the set of links traversed by a packet between
a
                      source node and a destination node.

SB&gt; Is it a set of links, or a set of links and nodes?
</pre>
      </blockquote>
      <pre wrap="">
I think the current text is OK.

</pre>
      <blockquote type="cite">
        <pre wrap="">
========

   the value of MMS_S, the "maximum send transport-message size".
SB&gt; The modern convention is full-name(abbreviation)
</pre>
      </blockquote>
      <pre wrap="">
I don’t follow this.</pre>
    </blockquote>
    <br>
    A really minor point. A RFC usually expresses this as <br>
    <pre wrap="">   the maximum send transport-message size (MMS_S), but that is a house style thing.</pre>
    <br>
    <br>
    <br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">
========

  The Sun Network File System (NFS) uses a Remote Procedure Call
(RPC)
  protocol [RPC] that, when used over UDP, in many cases will
generate
  payloads that must be fragmented even for the first-hop link.
This
  might improve performance in certain cases, but it is known to
cause
  reliability and performance problems, especially when the client
and
  server are separated by routers.

SB&gt; Perhaps this should point to RFC7530 (the current NFS Spec),
assuming
SB&gt; the behaviour description is still correct.
</pre>
      </blockquote>
      <pre wrap="">
Will do.

</pre>
      <blockquote type="cite">
        <pre wrap="">
=========

  The former can be accomplished by associating a flag with the
path;
  when a packet is sent on a path with this flag set, the IP layer
does
  not send packets larger than the IPv6 minimum link MTU.

SB&gt; We do not normally give this level of implementation advice
</pre>
      </blockquote>
      <pre wrap="">
I think it varies a lot.</pre>
    </blockquote>
    OK<br>
    <br>
    <blockquote
      cite="mid:5BABA19D-58F8-44AE-BF18-9A0B9CCADED4@gmail.com"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">
========================



</pre>
      </blockquote>
      <pre wrap="">
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Gen-art mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gen-art@ietf.org">Gen-art@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/gen-art">https://www.ietf.org/mailman/listinfo/gen-art</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------D16124D1E89C620CFECE780A--


From nobody Mon Mar 20 10:34:38 2017
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 15376128796; Mon, 20 Mar 2017 10:34:37 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00O3YpLDvO9C; Mon, 20 Mar 2017 10:34:35 -0700 (PDT)
Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C585113151A; Mon, 20 Mar 2017 10:34:32 -0700 (PDT)
Received: by mail-ot0-x22d.google.com with SMTP id x37so137184493ota.2; Mon, 20 Mar 2017 10:34:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=I3ThuwvUgMr7itw4Scto8NgiHSTbKyyBrrt+/rTojgA=; b=lwZOWK6lMvsYIGtdKSq3DCSa5lYPAuBpQTB2T/xOloiyUqL0ofyCrNLPvsjPeAr1YM apsJAfnsgd7eHSjqIlFXRwTmTkpidEG6YYlT4oLaDO0hlG6xipdFDx/rAuIwQBydVfPO M8rBwH/mae74z6kfasP8dbH9vNlDJjNr+na7DV27Tt3UmokjDuQ7sfFDhrCaSVNiyPGq yLRG+Z2YzKamMV4sTuQ+4+f1IedKQhddhJr30gyHGO4X78iuDA6sdKRp1ttHVQJ8auvH Ji7vDWeowO/vxUQhMcEazLmhX20TGMgjTpOn91n6CROmM2AbjdknFQx+i/RSf8ep8tQm MQ+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=I3ThuwvUgMr7itw4Scto8NgiHSTbKyyBrrt+/rTojgA=; b=DJ7nGM3Y9s1ncgdXpDWXp0WImF9uFyH8rwqDXhsDJnJmmM33UnwnDqBVgFobVzdwq1 T09MRQ9ThZlNIvkC13wqNqriXnlDm0O8Xm0EbJJQPc74N9Fr3ewlbRaYe623mb3xkgVu vu9tRY0IfV2rN+X+5ub0gCtGTh/gry5enLZolfRzuZnMNgmXIXkfEJ3HQyUzM7a0G3Mk u/0BKvqZCpDUqwJdLBXXKRjLcSaGgWh8G9hJlH5Smbw88zms3yJQ0SyXm3KdvKj1vU/8 +XPxIMIRbyrTUfI/EpGUir04ixrwapxNJAYqaubbZ3NI8gZKd2UeCuhRFFaaCAzq0D+4 8XjQ==
X-Gm-Message-State: AFeK/H272nMioSgHHRP6u3v7mUg9eBRtutrtqo7y28JCC5w7VtvyvSnH70t66MF1V+Ew4ffUCgJYt+Lxk2MI3g==
X-Received: by 10.157.1.247 with SMTP id e110mr14679849ote.40.1490031272239; Mon, 20 Mar 2017 10:34:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.21.21 with HTTP; Mon, 20 Mar 2017 10:34:31 -0700 (PDT)
In-Reply-To: <148977726052.13049.17633302885192133866@ietfa.amsl.com>
References: <148977726052.13049.17633302885192133866@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 20 Mar 2017 12:34:31 -0500
Message-ID: <CA+RyBmWLezQVyq+d5OZD3fM5-4EN-qCVTAJ-_LGX+4KmKUCTWA@mail.gmail.com>
Subject: Re: Review of draft-ietf-ippm-twamp-time-format-05
To: Jon Mitchell <jrmitche@puck.nether.net>
Cc: ops-dir@ietf.org, draft-ietf-ippm-twamp-time-format.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c03b82aafa92f054b2cf057
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jFKVhlhjhxnPJKQ332392jXxMTo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 17:34:37 -0000

--94eb2c03b82aafa92f054b2cf057
Content-Type: text/plain; charset=UTF-8

Hi Jon,
thank you for kind consideration of the draft and thoughtful comment.
Indeed, TWAMP Test, and the time stamp format to be used, may be controlled
by means other than TWAMP Control, e.g., local configurable knob exposed
via data model or CLI. I'll work on text updates for the next version.

Regards,
Greg

On Fri, Mar 17, 2017 at 2:01 PM, Jon Mitchell <jrmitche@puck.nether.net>
wrote:

> Reviewer: Jon Mitchell
> Review result: Has Nits
>
> I have reviewed this document as part of the Operational directorate's
>
> ongoing effort to review all IETF documents being processed by the
> IESG.  These
> comments were written with the intent of improving the operational
> aspects of the
> IETF drafts. Comments that are not addressed in last call may be
> included in AD reviews
> during the IESG review.  Document editors and WG chairs should treat
> these comments
> just like any other last call comments.
>
> Ready with Nits - this draft adds the ability to use PTP timestamps as
> an alternative to NTP timestamps for active performance measurement
> protocols OWAMP and TWAMP.  Although this draft does a good job of
> discussing interoperability for both sides of the session having or
> not having support for this operational capability, in several places
> it states that if a send/receiver support this capability it must be
> set to 1 in the flags.  However, only for TWAMP Light mode, this seems
> configurable.  This may just be my interpretation, but it probably
> should state that local implementations MAY provide a configurable
> knob to not negotiate PTPv2 timestamps in section 2.1 and 2.2 even if
> the capability is supported by the implementation.
>
>
>

--94eb2c03b82aafa92f054b2cf057
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Jon,<div>thank you for kind consideration of the draft =
and thoughtful comment. Indeed, TWAMP Test, and the time stamp format to be=
 used, may be controlled by means other than TWAMP Control, e.g., local con=
figurable knob exposed via data model or CLI. I&#39;ll work on text updates=
 for the next version.</div><div><br></div><div>Regards,</div><div>Greg</di=
v></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, M=
ar 17, 2017 at 2:01 PM, Jon Mitchell <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:jrmitche@puck.nether.net" target=3D"_blank">jrmitche@puck.nether.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">Reviewer: Jon Mitchell<=
br>
Review result: Has Nits<br>
<br>
I have reviewed this document as part of the Operational directorate&#39;s<=
br>
<br>
ongoing effort to review all IETF documents being processed by the<br>
IESG.=C2=A0 These<br>
comments were written with the intent of improving the operational<br>
aspects of the<br>
IETF drafts. Comments that are not addressed in last call may be<br>
included in AD reviews<br>
during the IESG review.=C2=A0 Document editors and WG chairs should treat<b=
r>
these comments<br>
just like any other last call comments.<br>
<br>
Ready with Nits - this draft adds the ability to use PTP timestamps as<br>
an alternative to NTP timestamps for active performance measurement<br>
protocols OWAMP and TWAMP.=C2=A0 Although this draft does a good job of<br>
discussing interoperability for both sides of the session having or<br>
not having support for this operational capability, in several places<br>
it states that if a send/receiver support this capability it must be<br>
set to 1 in the flags.=C2=A0 However, only for TWAMP Light mode, this seems=
<br>
configurable.=C2=A0 This may just be my interpretation, but it probably<br>
should state that local implementations MAY provide a configurable<br>
knob to not negotiate PTPv2 timestamps in section 2.1 and 2.2 even if<br>
the capability is supported by the implementation.<br>
<br>
<br>
</blockquote></div><br></div>

--94eb2c03b82aafa92f054b2cf057--


From nobody Mon Mar 20 12:10:33 2017
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C09131694; Mon, 20 Mar 2017 12:10:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: Opening IETF 99 Registration
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.2
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149003703165.25066.1887983242127531088.idtracker@ietfa.amsl.com>
Date: Mon, 20 Mar 2017 12:10:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/guLbCFjyG5kLSeMzI-hFn-oZNZ0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 19:10:32 -0000

Registration for IETF 99 in Prague, Czech Republic will open on Wednesday, March 29 at 07:00 PDT, 09:00 CDT, 16:00 CEST. Worldwide times at https://timeanddate.com/s/37rk. An announcement opening registration will be made at that time.

Hotel reservations will also be open.

Letters of Invitation may be requested during registration.

- IETF Secretariat


From nobody Mon Mar 20 12:57:33 2017
Return-Path: <mahoney@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 241971293D8; Mon, 20 Mar 2017 12:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5bvRG-9lvax; Mon, 20 Mar 2017 12:57:29 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCBE6126C0F; Mon, 20 Mar 2017 12:57:29 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v2KJvOWe044840 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 20 Mar 2017 14:57:24 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be mutabilis-2.local
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: "Dale R. Worley" <worley@ariadne.com>, Denis Ovsienko <denis@ovsienko.info>
References: <87o9ww2fjv.fsf@hobgoblin.ariadne.com>
Cc: sipcore@ietf.org, ietf@ietf.org, draft-ietf-sipcore-status-unwanted.all@ietf.org
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <7a26ee02-acb8-b6d3-6b9c-83232dd9bf47@nostrum.com>
Date: Mon, 20 Mar 2017 14:57:24 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <87o9ww2fjv.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_Mo6Q8Lmw84VQzID7geibhzml54>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 19:57:32 -0000

For some background - there was quite a bit of DISPATCH WG discussion on 
the use of the 666 response code to indicate that a call is unwanted, 
but it revolved around the use of a 6xx type of response vs. a 4xx 
response code.

How the choice might be presented to the end user was also discussed, 
although SIPCORE and DISPATCH WGs don't focus on GUI stuff. When the end 
user receives a call, they could select a "Block Caller" button on their 
cell phone just like they can select "Send to Voice Mail". The 
application on the phone would then generate the 666 response code, but 
the app would be very unlikely to show this code to the end user. On the 
caller's end, their app may not show them anything more than their call 
failed. Realistically, the response code would be seen only in diagnostics.

I took a look through the IETF archives for other uses of 666. 666 comes 
up occasionally in mailing list discussions as a foo/bar-type 
placeholder. RFC 7999 specifies the BGP community BLACKHOLE and its 
value, where "the low-order two octets in decimal are 666, a value 
commonly associated with BGP blackholing among network operators."

That said, there's plenty of space in the SIP 6xx response code range 
for an alternate response code to be selected if we think this will 
likely make end users uncomfortable.

Regards,

Jean

On 3/20/17 9:23 AM, Dale R. Worley wrote:
> Denis Ovsienko <denis@ovsienko.info> writes:
>> If you mind people that take the Bible and its teachings seriously, it
>> will be easy for them to see it as a personal insult if their phone
>> receives and displays the message as it is proposed, as well as if
>> their phone sends such a message on their behalf. This is not specific
>> to SIP, the same conflict may be caused by a snail mail post, except
>> in real-time communications people have less time to think and step
>> back from the situation.
>
> That seems to be a valid consideration to me:  Embedding
> culturally/religiously/politically symbolic identifiers in a protocol in
> a way that end users will at least occasionally see is probably not a
> good idea.  It's clear even to me that a flippant reference to the
> Prophet is asking for trouble, and it seems like we should take
> references to the Number of the Beast seriously, given its long history
> as a politically powerful symbol.
>
>> As an additional consideration, the document implies that the user
>> receiving the "unwanted" call has a good reason and the user placing
>> the call does not have it, as in spam calls.
>
> I'm not current on the document, but my understanding is that it makes
> clear that the response code is *in the opinion of the recipient* and
> must be interpreted as such.  And indeed, that the recipient may have
> triggered the response accidentally.
>
>> Besides the end users, there is the technical audience, both inside
>> and outside of IETF. This audience expects a certain level of
>> professionalism from IETF Standard Track publications. By not meeting
>> those expectations this publication would disappoint the engineers too
>> and lower their motivation to contribute. Simply put, the number of
>> people that think "IETF has less respect to its intended audience than
>> I used to think. They don't make Internet better, they are
>> whim-driven, now that I know it, I better stay away." will
>> increase. And they will actually stay away regardless if things
>> improve afterwards.
>
> I think the evidence is that seriousness is not required to attract
> technical talent to the IETF.  (See RFCs 439, 527, 748, 968, 1097, 1149,
> 1216, 1217, 1313, 1437, 1438, 1605, 1606, 1607, 1776, 1882, 1924, 1925,
> 1926, 1927, 2100, 2321, 2322, 2323, 2324, 2325, 2410, 2549, 2550, 2551,
> 2795, 3091, 3092, 3093, 3251, 3252, 3514, 3751, 4041, 4042, 4824, 5241,
> 5242, 5513, 5514, 5841, 5984, 6214, 6217, 6592, 6593, 6919, 6921, 7168,
> 7169, 7511, and 7514.)  However, there might be a public relations
> problem concerning management, politicians, etc.
>
> Dale
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>


From nobody Mon Mar 20 14:58:28 2017
Return-Path: <aaron.falk@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 96D361293FD; Mon, 20 Mar 2017 14:58:26 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w5JQO16LV0bF; Mon, 20 Mar 2017 14:58:12 -0700 (PDT)
Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB4BB1276AF; Mon, 20 Mar 2017 14:58:06 -0700 (PDT)
Received: by mail-qk0-x244.google.com with SMTP id v127so19890723qkb.1; Mon, 20 Mar 2017 14:58:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version; bh=p5BUGN4v2MVViMPHqCbfzQEC5W7WKlSxjK9zWhWgS6E=; b=j+JJU9oKt+8T5NXMjEQjiNL9YPJyyNbrU+k82EfL3YTqYlV1MqEaQsn8Qu3BLIx1wf a6OHqZ1T7niayZno5cmXQOArUQpjgZYM9VtMzsZ/MuywKTjB0tf5rtCRSoHSfiFessZI zvPK0GgszQkf0uEfyGm8F75HeqPZXLWaVE7thNBJUiiUGxZXxuPH4/2QkBqLI+2wv3bJ liP4RYYLhsHw8DqaSIL1yUN9YGYNJJXnWH7Tz2QscoBf67n5rEACk71N5yktPkXb8gEy dg02IEfwsU1XYZwEijAfEo9xMhnmfAAoj1e2XIt7LldMZ8A4ewaRMIZC376lE3V7bfXW wyXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version; bh=p5BUGN4v2MVViMPHqCbfzQEC5W7WKlSxjK9zWhWgS6E=; b=ZfdCjhl0VwlSSEbl6pdff6T7rBN94KfFvmf0+0nhI6YAgPP3NBlaf9CQpVL1mdMpB7 gAX+x9YL/y0tn5c7C8NQTqh+QXSRYNFY0m7/GQ91wThNS/J8afGCc41E2pXiJSnSQTiB N/r3rrsct/PBQ5Jvx7ulJs0CpEndRWnpgpoWq3ULUbcaetv6GQpI4/5pNJAsa/DKoT+Z febuZphmHBF5tWcpNpzN9YkrY3oEhNqy348Q+5CVXfEllA54LMHuUSb203HFHlt4d1KG dXh8FFPmeOKGCzQt6oCuSkVQ4OPMzJCbKUoxfq29d5c5GWR5RapBFdEoOkvHTwEsGC4Y kdcQ==
X-Gm-Message-State: AFeK/H37QO2pZTxypYhzsnhAsEOLSBjGC2pPVRTCBiWgp8eVDPlsHYMsjqJgediUPLB7xA==
X-Received: by 10.55.128.66 with SMTP id b63mr30678246qkd.297.1490047085468; Mon, 20 Mar 2017 14:58:05 -0700 (PDT)
Received: from [172.19.36.8] ([2001:4878:8000:60:e0f3:afff:cbce:7d92]) by smtp.gmail.com with ESMTPSA id q11sm13241777qtb.2.2017.03.20.14.58.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Mar 2017 14:58:04 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, 98attendees@ietf.org
Subject: final cfp: Bad Attitude PechaKucha in Chicago
Date: Mon, 20 Mar 2017 17:58:04 -0400
Message-ID: <A5ED488C-88CD-4474-AFD8-CF5C667B82D9@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_D69E62DA-FB31-450E-9845-5FBE7117FF89_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tsw_rm0f2AsILket2ho5N7e_52s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 21:58:26 -0000

--=_MailMate_D69E62DA-FB31-450E-9845-5FBE7117FF89_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

This is a heads-up that I=E2=80=99m planning to arrange for another Pecha=
Kucha =

event at IETF-98 in Chicago.  (Sorry for the repeat announcement.)

A Pecha Kucha is a lightning-talk presentation format, originating in =

Japan, where a speaker presents 20 image-only slides that are each on =

the screen for 20 seconds and advance automatically.  With each talk =

lasting for 6:40, it has the feature of forcing presentations -- good or =

bad -- to be focused and brief.  This is an unofficial event. Topics are =

encouraged to be a IETF-related and satirical or controversial in some =

way, although not mean-spirited.  Anyone can participate in this social =

event.  Video from the Berlin and Seoul PKs can be found =

[here](http://snaggletooth.akam.ai).

Format Details:

* Presentation slots are open to all, assigned first come, first served.
* To reserve a presentation slot, send a name and title to =

aaron.falk@gmail.com and receive confirmation.
* Presenters must agree to adhere to the Pecha Kucha format (20 slides, =

primarily image-only, automatically advancing every 20 seconds).
* There are lots of online tutorials and suggestions for how to make a =

good Pecha Kucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

[[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pecha=
=2Ehtml)], =

[[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].
--=_MailMate_D69E62DA-FB31-450E-9845-5FBE7117FF89_=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">This is a heads-up that I=E2=80=99m planning to arrange f=
or another PechaKucha event at IETF-98 in Chicago.  (Sorry for the repeat=
 announcement.)</p>

<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin and Seoul PKs can be found <a href=3D"ht=
tp://snaggletooth.akam.ai" style=3D"color:#3983C4">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#3983C4">aaron.falk@gmail.com<=
/a> and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#3983C4">1</a>], [<a href=3D"http://blog.indezine.com/20=
12/05/10-tips-to-create-and-present-pecha.html" style=3D"color:#3983C4">2=
</a>], [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha=
-kucha/" style=3D"color:#3983C4">3</a>].</li>
</ul>
</div>
</div>
</body>
</html>

--=_MailMate_D69E62DA-FB31-450E-9845-5FBE7117FF89_=--


From nobody Mon Mar 20 17:08:06 2017
Return-Path: <worley@alum.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 6A2BC131498 for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 17:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LoQaNYAbMPAt for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 17:08:03 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B09A12940E for <ietf@ietf.org>; Mon, 20 Mar 2017 17:08:03 -0700 (PDT)
Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-10v.sys.comcast.net with SMTP id q7Ktc9ryd61D9q7LGcVALL; Tue, 21 Mar 2017 00:08:02 +0000
Received: from hobgoblin.ariadne.com ([24.60.114.4]) by resomta-ch2-06v.sys.comcast.net with SMTP id q7LEc8QwbeyvGq7LFcoObV; Tue, 21 Mar 2017 00:08:02 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v2L080o0020143; Mon, 20 Mar 2017 20:08:00 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v2L07xvl020140; Mon, 20 Mar 2017 20:07:59 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: "A. Jean Mahoney" <mahoney@nostrum.com>
Cc: denis@ovsienko.info, sipcore@ietf.org, ietf@ietf.org, draft-ietf-sipcore-status-unwanted.all@ietf.org
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
In-Reply-To: <7a26ee02-acb8-b6d3-6b9c-83232dd9bf47@nostrum.com> (mahoney@nostrum.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 20 Mar 2017 20:07:59 -0400
Message-ID: <878tnz331c.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfEdKgm6BZvS+7a8y/t0gZPj6WzgBhkkgUXoA8KYqU/KYKVw/wLdTxur/m8hwN5e+JhjIZ2B651p/zi4fQnKK82YApwvq+mSnLpCv2uGl8SZzSZ+nhaIQ ZKHi5apXwpe7uJxy+5dz1/vq8sy+vlKzjt3Unfw6gK0PxV+TEpnriavQ2VLEizVJrNbHAQgPoVU8hnTa33yYodQd4+r3RTwYH+tZECBOZeeWawxGCRkEtzr6 SbNrKndWd05ElDDdTzcR+lDUAku47FkfoTrJuzd70cjVKhLooZp6Zb1El+LSXD9meKvxwd3zU0XrwzRUpKRQ7w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PGGlgZ3Z2W2WQUfIt8NvzMG39Yc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 00:08:04 -0000

"A. Jean Mahoney" <mahoney@nostrum.com> writes:
> That said, there's plenty of space in the SIP 6xx response code range 
> for an alternate response code to be selected if we think this will 
> likely make end users uncomfortable.

I must say that the alternative that comes immediately to my mind is
"668: The Neighbor of the Beast".

Dale


From nobody Mon Mar 20 19:38:40 2017
Return-Path: <paul.kyzivat@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 7C4121316E9 for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 19:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kQLSmInDzpG for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 19:38:36 -0700 (PDT)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 785111316E7 for <ietf@ietf.org>; Mon, 20 Mar 2017 19:38:35 -0700 (PDT)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-06v.sys.comcast.net with SMTP id q9gncL5gMl4eqq9gwcv8mW; Tue, 21 Mar 2017 02:38:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1490063914; bh=mRxwEEzXGRhMxVnKcRwlHwfJMLm0vVJUeBkhH+as3bw=; h=Received:Received:From:Subject:To:Message-ID:Date:MIME-Version: Content-Type; b=OYcqt7gP9jUiGVVcSJD3XmW4XHLDBIEcu8fy1nCLWHje9zW0LpZa/Zh5fFHGxmPjk z31IzH/DX57fmrlYZFIQomSiEXk5Hvh91Ifau8Pv50ZePzRRFZnMsLdaSS5tZ3Lbaf WPlfvBRN4qd/8id057PnaoM6HSf5ooyQ4l1q02JzZ3xLoSJkhGnriTbIHw8GlOBdVA UmzrDU5SumlMm2KsIPpIl3JJroK1N/W+nSZlkAuJkNI6UAHj5Yqzii73zzHJBmb2aA 5ddEh9/I6n0ftZviTA2OfYZgFmXqcNzlPgFXIBF7ApElTSqXyiguFNkhHnWMWGTQEj rSZwiGoLMSF6Q==
Received: from [192.168.1.110] ([24.62.227.142]) by resomta-ch2-19v.sys.comcast.net with SMTP id q9gvcRM03ngy3q9gwcKUst; Tue, 21 Mar 2017 02:38:34 +0000
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: "ietf@ietf.org" <ietf@ietf.org>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <15aeb1be62a.11b35bf8267637.2121189919710903185@ovsienko.info>
Message-ID: <d0768a84-410a-0acb-fd1a-b8f666eff18f@comcast.net>
Date: Mon, 20 Mar 2017 22:38:33 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <15aeb1be62a.11b35bf8267637.2121189919710903185@ovsienko.info>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfP/FyL2vmzu8a/nFEBpBOjCQvTXCDPveTYHYMLQVrzsw1VrCUN3a9WZf/yu1C1Xv5k7a3CdA5ZtTm2ilDKXay6OrOnad9oxisleLAnFXzy036tJ9VH+a fVyn8NjVJObQKuO+0iAjnnfnpgQd6/cSW+4S0njnwjgr1tIDUtcfO11d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5C_1QQxleORJLRerSEceUPGwE7w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 02:38:38 -0000

Denis,

Do you have any expertise with SIP? I don't recall ever seeing your name 
before. Your comments exhibit a profound misunderstanding of it.

SIP response codes are almost never displayed to end users. For that 
matter they aren't even typically exposed to *operators* of SIP-based 
systems. Only when people are diagnosing signaling problems within the 
network are they visible. So the basic premise of your objection is 
ill-founded.

	Sincerely,
	Paul Kyzivat

On 3/20/17 5:45 AM, Denis Ovsienko wrote:
> Dear IETF members,
>
> if you can stop the publication below, please stop it now. If you cannot but know someone who can stop it, please ask them now to stop it. There is little time left because the last call for it ends tomorrow.
>
> The goal of IETF is to make Internet better but this document is about to make it worse. A principle of IETF is rough consensus but this document and the implementations arising from it will be toxic for consensus.
>
> This situation is effectively a test of how much sense we have.
>
> ============ Forwarded message ============
>>From : <denis@ovsienko.info>
> To : <draft-ietf-sipcore-status-unwanted.all@ietf.org>
> Date : Fri, 17 Mar 2017 16:21:13 +0000
> Subject : Re: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
> ============ Forwarded message ============
>  > ---- On Wed, 08 Mar 2017 00:23:06 +0000 The IESG wrote ----
>  > >
>  > >The IESG has received a request from the Session Initiation Protocol Core
>  > >WG (sipcore) to consider the following document:
>  > >- 'A SIP Response Code for Unwanted Calls'
>  > > <draft-ietf-sipcore-status-unwanted-04.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 2017-03-21. 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 defines the 666 (Unwanted) SIP response code, allowing
>  > > called parties to indicate that the call or message was unwanted.
>  > > SIP entities may use this information to adjust how future calls from
>  > > this calling party are handled for the called party or more broadly.
>  > >
>  >
>  > Dear fellow IETF contributors,
>  >
>  > Though draft-ietf-sipcore-status-unwanted is as far in its development as in a last call, there is a point that I believe to be important enough to be raised now. The matter is, it would be very wrong to publish this document with the SIP message code assigned as the number of the beast.
>  >
>  > First of all, this would be wrong because of the end users. The proposed status code will be exposed to the end user base of SIP, which is so large that even a fraction of it is still a large number of real people, so specific consequences must be considered.
>  >
>  > If you mind people that take the Bible and its teachings seriously, it will be easy for them to see it as a personal insult if their phone receives and displays the message as it is proposed, as well as if their phone sends such a message on their behalf. This is not specific to SIP, the same conflict may be caused by a snail mail post, except in real-time communications people have less time to think and step back from the situation.
>  >
>  > As an additional consideration, the document implies that the user receiving the "unwanted" call has a good reason and the user placing the call does not have it, as in spam calls. In the real everyday world it may also be the different way around, for instance, someone may be avoiding calls due to problems with debt, job, alcohol, drugs, whatever, and that someone will just use the biggest "blacklist" button their phone can offer, just because they fail to think. There are other situations where this message code will be used as a handy tool for insulting genuine callers.
>  >
>  > It would be best here not to pour any more gas into this flame, moreover that professional spammers and phishers don't really care how exactly the call was terminated. Whatever status code was returned, they will continue calling numbers from the list until the end of the shift. So this feature as it is proposed may make more damage to normal people rather than to those who seem to be originally targeted.
>  >
>  > Then, if the document gets published and implemented as it is and starts causing grief, eventually people will want to know how the number of the beast got assigned to the message, they will look the document up and see:
>  >
>  > "The particular response code number was chosen to reflect the distaste felt by many upon receiving such calls."
>  >
>  > Which reads "We just needed some number, so we had chosen the number of the beast to make this new feature look cool. We acknowledge this number conveys some particular concept to many people but we deliberately disregard any future side effects."
>  >
>  > This is the only way I can read it, and the only way many other people will be able to read it. This is a fact, please deal with it while you can.
>  >
>  > Hopefully this helps to explain another important aspect.
>  >
>  > Besides the end users, there is the technical audience, both inside and outside of IETF. This audience expects a certain level of professionalism from IETF Standard Track publications. By not meeting those expectations this publication would disappoint the engineers too and lower their motivation to contribute. Simply put, the number of people that think "IETF has less respect to its intended audience than I used to think. They don't make Internet better, they are whim-driven, now that I know it, I better stay away." will increase. And they will actually stay away regardless if things improve afterwards.
>  >
>  > It may seem excess, but let me remind that the world is full of people who are mentally unwell and are on the verge of losing control, to the bad luck of poor strangers that happen to be around at the time. Often it is a tiny thing that finally tips their mind over. You cannot do much about this fact. But you can avoid introducing another potential last straw with an IETF label on it.
>  >
>  > To sum it up, the current revision of the I-D is going to increase the long-term risk of damage to IETF if it is published. I am asking you to change the codepoint to an ordinary nondescript number or to cancel the publication soonest possible.
>  >
>  > Thank you.
>  >
>  > --
>  >  Denis Ovsienko
>


From nobody Mon Mar 20 19:39:19 2017
Return-Path: <pkyzivat@alum.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 8E4A61316E5 for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 19:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GGklKy6i-NZc for <ietf@ietfa.amsl.com>; Mon, 20 Mar 2017 19:39:16 -0700 (PDT)
Received: from alum-mailsec-scanner-8.mit.edu (alum-mailsec-scanner-8.mit.edu [18.7.68.20]) by ietfa.amsl.com (Postfix) with ESMTP id CB14C1316D9 for <ietf@ietf.org>; Mon, 20 Mar 2017 19:39:15 -0700 (PDT)
X-AuditID: 12074414-7efff70000002bfd-35-58d0925044d7
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 2E.99.11261.15290D85; Mon, 20 Mar 2017 22:39:15 -0400 (EDT)
Received: from [192.168.1.110] (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id v2L2dCgs012000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Mon, 20 Mar 2017 22:39:12 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: ietf@ietf.org
References: <87o9ww2fjv.fsf@hobgoblin.ariadne.com>
Message-ID: <1c157c1e-fd0f-79af-3f25-e0b5fa68f9c8@alum.mit.edu>
Date: Mon, 20 Mar 2017 22:39:11 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <87o9ww2fjv.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKIsWRmVeSWpSXmKPExsUixO6iqBs86UKEwezL/BbPNs5ncWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxo3TZ9gKzghWvJg2j62B8S9vFyMnh4SAicTLBe1MXYxcHEIC O5gkJq7fAOW8ZJJo37WNDaSKTUBLYs6h/ywgCWGBXkaJZ5M6gBIcHCICghIHH1uC1AgJGEks v3SLCSTMK2Av0XQnAyTMIqAq0bK5hwnEFhVIk3iy7QcjiM0L1Hly5hMWkHJOAWOJ6cfkQcLM ArYSd+buZoaw5SW2v53DPIGRbxaSjllIymYhKVvAyLyKUS4xpzRXNzcxM6c4NVm3ODkxLy+1 SNdCLzezRC81pXQTIyTERHYwHjkpd4hRgINRiYd3xZXzEUKsiWXFlbmHGCU5mJREeat8L0QI 8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuF17QPK8aYkVlalFuXDpKQ5WJTEeb8tVvcTEkhPLEnN Tk0tSC2CycpwcChJ8N6fANQoWJSanlqRlplTgpBm4uAEGc4DNLwVpIa3uCAxtzgzHSJ/ilGX Y8bHA2+YhFjy8vNSpcR5RScCFQmAFGWU5sHNgaWGV4ziQG8J834HGcUDTCtwk14BLWECWrLs xhmQJSWJCCmpBsbIdIePN8veXRK92StVeblKKEdk1em9Mhs+u1+077O/+uGN/pv0iIfMzxfu 3XFoqgLjLG3Wr1Ybz5zOXSmxd9GTu2uioljC+K03bJILEPab9CktctKkrjtzE+LL1p47duBQ /M8Ct1Rp89mthflbSua9/O7z6lDK2Rd/FDgfNW/db8OcGZ4gMbdYiaU4I9FQi7moOBEAJXs+ L+gCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wTQzwJJ_Ah12FHkysMj3HzI8YUE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 02:39:18 -0000

On 3/20/17 10:23 AM, Dale R. Worley wrote:
> Denis Ovsienko <denis@ovsienko.info> writes:
>> If you mind people that take the Bible and its teachings seriously, it
>> will be easy for them to see it as a personal insult if their phone
>> receives and displays the message as it is proposed, as well as if
>> their phone sends such a message on their behalf. This is not specific
>> to SIP, the same conflict may be caused by a snail mail post, except
>> in real-time communications people have less time to think and step
>> back from the situation.
>
> That seems to be a valid consideration to me:  Embedding
> culturally/religiously/politically symbolic identifiers in a protocol in
> a way that end users will at least occasionally see is probably not a
> good idea.  It's clear even to me that a flippant reference to the
> Prophet is asking for trouble, and it seems like we should take
> references to the Number of the Beast seriously, given its long history
> as a politically powerful symbol.

I don't find it reasonable to cater to superstitious beliefs. (E.g. 
omitting the 13th floor from a building.)

OTOH, I will agree that the choice of 666 as the response code here was 
not incidental - it clearly was chosen with that "Number of the Beast" 
connotation in mind. In that sense the choice was gratuitous.

The requirement is that the number be of the form 6nn, and that it be 
one that has not already been assigned a meaning within the protocol. 
The process for assigning specific values for new response codes is ad hoc:

- sometimes the next unassigned value is assigned,
- sometimes sub-ranges are reserved for related values,
- sometimes a value is assigned based on a similar value
   in another category. (E.g. 406 and 606).

None of these would lead to 666 being an obvious choice in this case.

Hence, I would not object to choosing a different value based on such 
criteria.

BUT, should there ever be a need to assign another value in the 6nn 
range, and there is some rational reason (other than to explicitly 
reference the Number of the Beast), then I would strenuously object to 
objections based on this connotation of that particular value.

	Sincerely,
	Paul Kyzivat


From nobody Tue Mar 21 01:03:20 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2793D12964F; Tue, 21 Mar 2017 01:03:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yoav Nir <ynir.ietf@gmail.com>
To: <secdir@ietf.org>
Cc: draft-ietf-aqm-codel.all@ietf.org, ietf@ietf.org, aqm@ietf.org
Subject: Review of draft-ietf-aqm-codel-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149008338604.24977.6083947817909590331@ietfa.amsl.com>
Date: Tue, 21 Mar 2017 01:03:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6MblCHMaBFTMeyReM8IEBESxcGg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 08:03:06 -0000

Reviewer: Yoav Nir
Review result: Has Nits

Hi,

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

The document describes the CoDel (controlled delay) framework for
reducing bufferbloat. It does a good job of describing the problem,
outlining the solution and providing both a description of the
algorithm (including pseudo-code) and linking to real world
implementations. 

Two nits:

1. A lot of terms are used long before they are explained, such as
Estimator, Sojourn time, Interval (BTW: if this is a moving interval
the spec should probably say so). When reading sections 3 I concluded
that the document was aimed at peopel who already knew all these terms
and didn't need definitions, but then reading section 5 gave me a lot
of a-ha moments about what I had read previously.

2. The security considerations section says "There are no specific
security exposures associated with CoDel."  CoDel is about dropping
packets, so immediately I have to think how I could subvert a router
running CoDel to drop other people's packets. Perhaps it is fine to
say that there are no known attacks on CoDel and no steps necessary to
mitigate such, but I think it's tempting fate and hackers to say that
CoDel has no security exposures.


From nobody Tue Mar 21 07:42:21 2017
Return-Path: <adam@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 4ADAF12995F for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 07:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n2fDszNncQtM for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 07:42:18 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 443ED12948C for <ietf@ietf.org>; Tue, 21 Mar 2017 07:42:18 -0700 (PDT)
Received: from Orochi.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v2LEgCfB049247 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 21 Mar 2017 09:42:14 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Orochi.local
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, ietf@ietf.org
References: <87o9ww2fjv.fsf@hobgoblin.ariadne.com> <1c157c1e-fd0f-79af-3f25-e0b5fa68f9c8@alum.mit.edu>
From: Adam Roach <adam@nostrum.com>
Message-ID: <e7f63696-129c-f9cc-feea-0b661e026f38@nostrum.com>
Date: Tue, 21 Mar 2017 09:42:07 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1c157c1e-fd0f-79af-3f25-e0b5fa68f9c8@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HjCYJE7iJyvRxMpDHtSjIJ9r7AI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 14:42:20 -0000

On 3/20/17 21:39, Paul Kyzivat wrote:
> OTOH, I will agree that the choice of 666 as the response code here 
> was not incidental - it clearly was chosen with that "Number of the 
> Beast" connotation in mind. In that sense the choice was gratuitous. 


I would argue "mnemonic" rather than "gratuitous" -- similar to the 
"451" response code selected by RFC 7725.

/a


From nobody Tue Mar 21 07:54:06 2017
Return-Path: <spencerdawkins.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 63059127011 for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 07:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89tjrJ59wYOA for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 07:54:02 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F33D1299C3 for <ietf@ietf.org>; Tue, 21 Mar 2017 07:53:45 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id o4so111541539ywd.3 for <ietf@ietf.org>; Tue, 21 Mar 2017 07:53:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+8ifNtxBWP2A0R1M6z0M2EuX0atfDzixX3ps8SVCR+4=; b=iZni8dSgIAqp75sYZhauxwxxyg2d/OhXbT6LFXskjArCQK1Aptf91lQ1SHyTRDXwPC unnvm5j9PML/2pUjISDKs+UMEraMFdmxrbBBkVN0SfBwLeZUCuGPIY9kjmpdwWL/TbBo dQNmSnMTnJQiq6itDh7FcA3BLDIuDzSpJxUvFw45r8+eqrk9aDWQlIHc6toYfUoDCJgl MD+F1tnUfJw00lNAcV1K2nvXyC0ybkWBG2+G0ZU/IpZJOKG91QVWrBMv4ibk8EWIHsNS qLYn4d7WfySclNyXMG/RJ3TUTSadwO/NwrA+j0xSG9LaIVTVoYoo3dZzNbiA5JLaLngq qEtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+8ifNtxBWP2A0R1M6z0M2EuX0atfDzixX3ps8SVCR+4=; b=cBSVaKDpNrLttUuzdpP8SNBY6cZeQejI/7FL9oTISmR0M6cXGMhb0wn4ubbqa6gqu7 yw7/QPklbJ7I7TyeWPqKtR01sc/gAgoeNqq2RxesXJ8lu6loXnEu81wlTNNqgW7Njk38 Ggm9tYH2hp1d59txIF/nL4IvyhfQmNszwjM2mQ6EK3oVO78j9t7yU/xE6SneYGc6wf5B qPenMeaPtD/qZqfMw0sZqSUmwjBe4YvOnY8WkQULanaAPXEXkjZK+EzLYy7CpBS3sMFq mY1G6gnTwo3KK1CVe2CLFFUDuOJjEFGuReW3sxaL79J+XWmJKCOY8jJj7Dv92O7okXQ5 nmEw==
X-Gm-Message-State: AFeK/H1cibRknsrisXOH02XRw9OtzSABN/SH2UxNtWMAFy6abVgZwOZ0dj81TOgX2J1KTCqdfGYaUp1doybqSA==
X-Received: by 10.13.204.88 with SMTP id o85mr19264093ywd.347.1490108024394; Tue, 21 Mar 2017 07:53:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.73.129 with HTTP; Tue, 21 Mar 2017 07:53:43 -0700 (PDT)
Received: by 10.37.73.129 with HTTP; Tue, 21 Mar 2017 07:53:43 -0700 (PDT)
In-Reply-To: <e7f63696-129c-f9cc-feea-0b661e026f38@nostrum.com>
References: <87o9ww2fjv.fsf@hobgoblin.ariadne.com> <1c157c1e-fd0f-79af-3f25-e0b5fa68f9c8@alum.mit.edu> <e7f63696-129c-f9cc-feea-0b661e026f38@nostrum.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 21 Mar 2017 09:53:43 -0500
Message-ID: <CAKKJt-fPtZ4vKT5COv7cXELhzdWb4vT2ewigquNYwuwobzBGWg@mail.gmail.com>
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: Adam Roach <adam@nostrum.com>
Cc: ietf@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=001a11482484789b24054b3ecf8b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FM0FvV66SyLx1qeyb27bLdgzK3M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 14:54:04 -0000

--001a11482484789b24054b3ecf8b
Content-Type: text/plain; charset=UTF-8

Fwiw,

On Mar 21, 2017 09:42, "Adam Roach" <adam@nostrum.com> wrote:

On 3/20/17 21:39, Paul Kyzivat wrote:

> OTOH, I will agree that the choice of 666 as the response code here was
> not incidental - it clearly was chosen with that "Number of the Beast"
> connotation in mind. In that sense the choice was gratuitous.
>


I would argue "mnemonic" rather than "gratuitous" -- similar to the "451"
response code selected by RFC 7725.


My canonical example of a mnemonic integer selection would be the choice of
"RFC 1984" forIAB and IESG Statement on Cryptographic Technology and the
Internet(https://datatracker.ietf.org/doc/rfc1984/).

Spencer

--001a11482484789b24054b3ecf8b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Fwiw,<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mar 21, 2017 09:42, &quot;Adam Roach&quot; &lt;<a href=
=3D"mailto:adam@nostrum.com">adam@nostrum.com</a>&gt; wrote:<br type=3D"att=
ribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text">On 3/20/17 21=
:39, Paul Kyzivat wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
OTOH, I will agree that the choice of 666 as the response code here was not=
 incidental - it clearly was chosen with that &quot;Number of the Beast&quo=
t; connotation in mind. In that sense the choice was gratuitous. <br>
</blockquote>
<br>
<br></div>
I would argue &quot;mnemonic&quot; rather than &quot;gratuitous&quot; -- si=
milar to the &quot;451&quot; response code selected by RFC 7725.</blockquot=
e></div></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">My canoni=
cal example of a mnemonic integer selection would be the choice of &quot;RF=
C 1984&quot; for<h2 style=3D"line-height:1.1;margin-top:21px;margin-bottom:=
10.5px"><span style=3D"font-weight:normal">IAB and IESG Statement on Crypto=
graphic Technology and the Internet</span></h2>(<a href=3D"https://datatrac=
ker.ietf.org/doc/rfc1984/">https://datatracker.ietf.org/doc/rfc1984/</a>).<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto">Spencer</div></div>

--001a11482484789b24054b3ecf8b--


From nobody Tue Mar 21 08:50:52 2017
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 57054129AB6; Tue, 21 Mar 2017 08:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.02
X-Spam-Level: 
X-Spam-Status: No, score=-7.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-4Gaw8-XuXm; Tue, 21 Mar 2017 08:50:28 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CBE41294AF; Tue, 21 Mar 2017 08:50:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490111421; x=1521647421; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=tsRl5NYOvjEn2/FzpJOd34ru5uPfLszQrij2J1p4QPM=; b=qOd2jimYokLF129ETcV2LmXYo26aF856VzF85tkFqEwDYrNIC92r/LaM Ss3ocgcWK2WzzPU8i4UQtpuJKy4I29XZIqH7NkjyDw9DMVu/iHoBi4urM JV6Y+KzDHP9vFuMxH/Y9LDNA0wyk7FTcymu+Rylc1JcCtrtViqUb/rA0v g=;
X-IronPort-AV: E=Sophos;i="5.36,198,1486454400";  d="scan'208,217";a="367202202"
Received: from unknown (HELO ironmsg02-L.qualcomm.com) ([10.53.140.109]) by wolverine02.qualcomm.com with ESMTP; 21 Mar 2017 08:50:19 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8474"; a="889593651"
X-MGA-submission: =?us-ascii?q?MDEoF+InG7h0SkbWffbqB85amB+WZZbWsfszXI?= =?us-ascii?q?DMlZfrfU7PoRwzShRNMplvtNZd/BlbDfjJ9dZrLzxxM+IyaggVwy+JGZ?= =?us-ascii?q?HUZkK6NW+IcNfeCZuAJDzIW7KP++KSDCZxgJdu+BdhLzLfsr9VI3ZNBg?= =?us-ascii?q?Xp?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Mar 2017 08:50:18 -0700
Received: from [10.64.124.243] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 21 Mar 2017 08:49:56 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <ietf@ietf.org>
CC: <draft-ietf-sipcore-status-unwanted@ietf.org>, <ben@nostrum.com>, <sipcore@ietf.org>, Adam Roach <adam@nostrum.com>, <sipcore-chairs@ietf.org>
Subject: Re: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
Date: Tue, 21 Mar 2017 10:49:54 -0500
Message-ID: <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com>
In-Reply-To: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_248277D9-D4E8-447F-B38B-F126A560CB0A_="
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01C.na.qualcomm.com (10.85.0.83) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PaC_P5dFY1EKET4OHBcdkHXH8yY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 15:50:32 -0000

--=_MailMate_248277D9-D4E8-447F-B38B-F126A560CB0A_=
Content-Type: text/plain; format=flowed; markup=markdown

I'm sorry to say that I do not think this mechanism is well thought out, 
I think it actually causes active harm to interoperability, and I think 
this document should be abandoned for a better (and simpler) solution to 
the problem, which I describe below.

I will note that I have not been following the discussion of this 
document except for it's introduction at the last plenary meeting, but I 
(and others) did give comments at that time that as far as I can tell 
were not taken into account. I did review the thread on the sipcore list 
regarding the difference between the new code and the 603 code. That 
thread does not address my concerns, and in fact in some way reinforces 
it. I have not reviewed other discussion on the list.

The purported purpose of this 666 mechanism is to allow additional 
semantics to be expressed beyond a simple 603 (Decline). That is a fine 
desire. However, instead of adding decent semantics to declining a call, 
666 adds only one additional bit of information to 603, and that one bit 
ends up causing more semantic ambiguity: The user has still declined the 
call (just as 603 would have), and has added that the call is *somehow* 
unwanted (so a provider *could* act to prevent such calls in the 
future), but the user has not indicated the *reason* they indicate the 
call is unwanted. Is it because they want to add this calling party to a 
call block list? Is it that they want to reject all calls of this 
particular class (cf. draft-ietf-sipcore-callinfo-spam)? Is there some 
other handling that would be appropriate given the particular reason the 
user has rejected the call? The best a provider is going to be able to 
do is guess. The document admits the ambiguity in the semantics, saying 
that the provider will have to use heuristics to guess at what the user 
really wants. We should not be introducing a new mechanism that only 
adds to the semantic ambiguity and might end up with results that the 
user might specifically not want in a particular case. What I think was 
really intended all along was to have un-upgraded implementations treat 
these rejections just like 603, but add some semantics that upgraded 
implementations can use to determine what ought to be done in the 
future.

The right solution, IMO, is to simply add a header to the 603 response 
that indicates what the user means by their declining, and gives a real 
indication of how handle such calls in the future. Call it 
"Decline-Type" for argument sake. Just like the Retry-After header adds 
semantics to indicate when the caller might want to try an identical 
call again, this new header will indicate that the user never wants a 
call from this particular caller again (e.g., "Decline-Type: 
block-caller", which the service provider can definitively use to add 
the caller to a block list), or that this caller and every caller with a 
similar type should be rejected (e.g. "Decline-Type: block-caller-type; 
type=political", which the provider could definitively use to reject 
similar calls in the future), etc.. With this, there's no need for a 
bunch of MAYs such that appear in section 4, you get an extensible 
mechanism that could be used by any 603 response. You also get the added 
bonus that un-upgraded entities will continue to treat this just like 
every other 603 without a Retry-After header, which is exactly what you 
want.

To be clear, the three things I am concerned about are:

1. The 666 mechanism leaves the decision of what is meant by "unwanted" 
to the provider, which will inevitably cause data loss through the use 
of heuristics. Adding a header to the 603 response is an extensible 
mechanism that could capture the single semantic bit of 666 *and any 
future semantics that one wishes to add*, without requiring the provider 
to guess. The provider gets definitive information that it can act on.

2. The 666 mechanism limits the implementation of the mechanism to a 
1-button choice and requires additional standardization work to use a 
different UI. Clearly 666 was designed around something akin to a "SPAM" 
button in the UI. But what if I want a field in my address book that 
says, "Permanently block this particular caller" (say, my ex-boyfriend 
or my annoying neighbor)? I don't want to indicate that these are spam 
calls because I don't want my provider applying heuristics to them. I 
want to send back a 603 with a header that says, "Block these whenever 
you see them, but only for me." I can think of all sorts of 
other-than-one-button UIs that someone might want to implement. 666 is 
tied to a particular UI. 603 with a header is extensible.

3. The 666 mechanism will be treated as a 600 "Busy" error by 
un-upgraded callers and/or providers. That might imply to some 
implementations that they should try to re-dial (e.g., the provider 
using the auto-redial feature) or to engage in other poor behavior. 603 
with no Retry-After header already has a semantic of "The call was 
rejected and I'm not telling you when a good time to call back is", so 
there is some hope that an un-upgraded caller is more likely to do the 
right thing.

Given the admittedly restricted review of the WG archive that I did, I 
didn't see anything to indicate that the WG fully considered the 
implications of 666 that I have outlined above. This is not simply a 
design preference; I believe the design of the proposed mechanism 
doesn't accomplish the goal and actually does some harm. Overall, 666 
damages interoperability by introducing an ambiguous piece of 
information, which will lead to potential data loss (i.e., improperly 
applied heuristics), and will require adding a header in the future in 
order to accomplish the real goal. Adding a header is a simple 
mechanism, accomplishes the desired task, has extensibility, and doesn't 
cause the problems that 666 does. Please reconsider this, drop this 
document, and replace it by adding real semantics to the 603 response 
with an extensible header. It's a quick document to write (a bunch of 
the text in the current document can be reused) and it will not suffer 
the problems that 666 introduces. Otherwise, we're going to be right 
back where were when we started, needing to add a mechanism so that the 
user can really indicate what they mean. This is the wrong solution.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

On 7 Mar 2017, at 18:23, The IESG wrote:

> The IESG has received a request from the Session Initiation Protocol 
> Core
> WG (sipcore) to consider the following document:
> - 'A SIP Response Code for Unwanted Calls'
>   <draft-ietf-sipcore-status-unwanted-04.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 2017-03-21. 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 defines the 666 (Unwanted) SIP response code, 
> allowing
>    called parties to indicate that the call or message was unwanted.
>    SIP entities may use this information to adjust how future calls 
> from
>    this calling party are handled for the called party or more 
> broadly.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unwanted/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unwanted/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.

--=_MailMate_248277D9-D4E8-447F-B38B-F126A560CB0A_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">I'm sorry to say that I do not think this mechanism is we=
ll thought out, I think it actually causes active harm to interoperabilit=
y, and I think this document should be abandoned for a better (and simple=
r) solution to the problem, which I describe below.</p>

<p dir=3D"auto">I will note that I have not been following the discussion=
 of this document except for it's introduction at the last plenary meetin=
g, but I (and others) did give comments at that time that as far as I can=
 tell were not taken into account. I did review the thread on the sipcore=
 list regarding the difference between the new code and the 603 code. Tha=
t thread does not address my concerns, and in fact in some way reinforces=
 it. I have not reviewed other discussion on the list.</p>

<p dir=3D"auto">The purported purpose of this 666 mechanism is to allow a=
dditional semantics to be expressed beyond a simple 603 (Decline). That i=
s a fine desire. However, instead of adding decent semantics to declining=
 a call, 666 adds only one additional bit of information to 603, and that=
 one bit ends up causing more semantic ambiguity: The user has still decl=
ined the call (just as 603 would have), and has added that the call is <e=
m>somehow</em> unwanted (so a provider <em>could</em> act to prevent such=
 calls in the future), but the user has not indicated the <em>reason</em>=
 they indicate the call is unwanted. Is it because they want to add this =
calling party to a call block list? Is it that they want to reject all ca=
lls of this particular class (cf. draft-ietf-sipcore-callinfo-spam)? Is t=
here some other handling that would be appropriate given the particular r=
eason the user has rejected the call? The best a provider is going to be =
able to do is guess. The document admits the ambiguity in the semantics, =
saying that the provider will have to use heuristics to guess at what the=
 user really wants. We should not be introducing a new mechanism that onl=
y adds to the semantic ambiguity and might end up with results that the u=
ser might specifically not want in a particular case. What I think was re=
ally intended all along was to have un-upgraded implementations treat the=
se rejections just like 603, but add some semantics that upgraded impleme=
ntations can use to determine what ought to be done in the future.</p>

<p dir=3D"auto">The right solution, IMO, is to simply add a header to the=
 603 response that indicates what the user means by their declining, and =
gives a real indication of how handle such calls in the future. Call it "=
Decline-Type" for argument sake. Just like the Retry-After header adds se=
mantics to indicate when the caller might want to try an identical call a=
gain, this new header will indicate that the user never wants a call from=
 this particular caller again (e.g., "Decline-Type: block-caller", which =
the service provider can definitively use to add the caller to a block li=
st), or that this caller and every caller with a similar type should be r=
ejected (e.g. "Decline-Type: block-caller-type; type=3Dpolitical", which =
the provider could definitively use to reject similar calls in the future=
), etc.. With this, there's no need for a bunch of MAYs such that appear =
in section 4, you get an extensible mechanism that could be used by any 6=
03 response. You also get the added bonus that un-upgraded entities will =
continue to treat this just like every other 603 without a Retry-After he=
ader, which is exactly what you want.</p>

<p dir=3D"auto">To be clear, the three things I am concerned about are:</=
p>

<ol>
<li value=3D"1"><p dir=3D"auto">The 666 mechanism leaves the decision of =
what is meant by "unwanted" to the provider, which will inevitably cause =
data loss through the use of heuristics. Adding a header to the 603 respo=
nse is an extensible mechanism that could capture the single semantic bit=
 of 666 <em>and any future semantics that one wishes to add</em>, without=
 requiring the provider to guess. The provider gets definitive informatio=
n that it can act on.</p></li>
<li value=3D"2"><p dir=3D"auto">The 666 mechanism limits the implementati=
on of the mechanism to a 1-button choice and requires additional standard=
ization work to use a different UI. Clearly 666 was designed around somet=
hing akin to a "SPAM" button in the UI. But what if I want a field in my =
address book that says, "Permanently block this particular caller" (say, =
my ex-boyfriend or my annoying neighbor)? I don't want to indicate that t=
hese are spam calls because I don't want my provider applying heuristics =
to them. I want to send back a 603 with a header that says, "Block these =
whenever you see them, but only for me." I can think of all sorts of othe=
r-than-one-button UIs that someone might want to implement. 666 is tied t=
o a particular UI. 603 with a header is extensible.</p></li>
<li value=3D"3"><p dir=3D"auto">The 666 mechanism will be treated as a 60=
0 "Busy" error by un-upgraded callers and/or providers. That might imply =
to some implementations that they should try to re-dial (e.g., the provid=
er using the auto-redial feature) or to engage in other poor behavior. 60=
3 with no Retry-After header already has a semantic of "The call was reje=
cted and I'm not telling you when a good time to call back is", so there =
is some hope that an un-upgraded caller is more likely to do the right th=
ing.</p></li>
</ol>

<p dir=3D"auto">Given the admittedly restricted review of the WG archive =
that I did, I didn't see anything to indicate that the WG fully considere=
d the implications of 666 that I have outlined above. This is not simply =
a design preference; I believe the design of the proposed mechanism doesn=
't accomplish the goal and actually does some harm. Overall, 666 damages =
interoperability by introducing an ambiguous piece of information, which =
will lead to potential data loss (i.e., improperly applied heuristics), a=
nd will require adding a header in the future in order to accomplish the =
real goal. Adding a header is a simple mechanism, accomplishes the desire=
d task, has extensibility, and doesn't cause the problems that 666 does. =
Please reconsider this, drop this document, and replace it by adding real=
 semantics to the 603 response with an extensible header. It's a quick do=
cument to write (a bunch of the text in the current document can be reuse=
d) and it will not suffer the problems that 666 introduces. Otherwise, we=
're going to be right back where were when we started, needing to add a m=
echanism so that the user can really indicate what they mean. This is the=
 wrong solution.</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>

<p dir=3D"auto">On 7 Mar 2017, at 18:23, The IESG wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">The IESG has received a request from the Session Initiati=
on Protocol Core<br>
WG (sipcore) to consider the following document:<br>
- 'A SIP Response Code for Unwanted Calls'<br>
  &lt;draft-ietf-sipcore-status-unwanted-04.txt&gt; as Proposed Standard<=
/p>

<p dir=3D"auto">The IESG plans to make a decision in the next few weeks, =
and solicits<br>
final comments on this action. Please send substantive comments to the<br=
>
<a href=3D"mailto:ietf@ietf.org" style=3D"color:#777">ietf@ietf.org</a> m=
ailing lists by 2017-03-21. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org" style=3D"color:#777">iesg@ietf.o=
rg</a> instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.</p>

<p dir=3D"auto">Abstract</p>

<p dir=3D"auto">This document defines the 666 (Unwanted) SIP response cod=
e, allowing<br>
   called parties to indicate that the call or message was unwanted.<br>
   SIP entities may use this information to adjust how future calls from<=
br>
   this calling party are handled for the called party or more broadly.</=
p>

<p dir=3D"auto">The file can be obtained via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unw=
anted/" style=3D"color:#777">https://datatracker.ietf.org/doc/draft-ietf-=
sipcore-status-unwanted/</a></p>

<p dir=3D"auto">IESG discussion can be tracked via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unw=
anted/ballot/" style=3D"color:#777">https://datatracker.ietf.org/doc/draf=
t-ietf-sipcore-status-unwanted/ballot/</a></p>

<p dir=3D"auto">No IPR declarations have been submitted directly on this =
I-D.</p>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_248277D9-D4E8-447F-B38B-F126A560CB0A_=--


From nobody Tue Mar 21 09:15:36 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49CFF129B47 for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 09:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xqNeoikbEPUi for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 09:15:32 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7E41129B5C for <ietf@ietf.org>; Tue, 21 Mar 2017 09:15:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v2LGF0fO024418; Tue, 21 Mar 2017 09:15:00 -0700
Received: from XCH15-05-09.nw.nos.boeing.com (xch15-05-09.nw.nos.boeing.com [137.136.239.211]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v2LGEsvV023982 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK) for <ietf@ietf.org>; Tue, 21 Mar 2017 09:14:54 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-05-09.nw.nos.boeing.com (2002:8988:efd3::8988:efd3) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 21 Mar 2017 09:14:52 -0700
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 21 Mar 2017 09:14:52 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "ietf@ietf.org" <ietf@ietf.org>
CC: "Saccone, Gregory T" <Gregory.T.Saccone@boeing.com>
Subject: Seeking IETF input for the future Aeronautical Telecommunications Network
Thread-Topic: Seeking IETF input for the future Aeronautical Telecommunications Network
Thread-Index: AdKiXaw6VVzQ3bbpSLyDri5D3e/6lw==
Date: Tue, 21 Mar 2017 16:14:52 +0000
Message-ID: <869b049340ac42e38d212fda37b8f066@XCH15-06-08.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w7ypAGO7oHVpjV-VkPv-gPKerP8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 16:15:34 -0000

This message is an open note to the flying public.

The International Civil Aviation Organization (ICAO) (http://www.icao.int)
is responsible for establishing Standards and Recommended Practices for
worldwide civil aviation. ICAO is currently developing standards for an
Aeronautical Telecommunications Network based on Internet Protocol
Services (ATN/IPS) for the future worldwide Air Traffic Management
(ATM) system.

ATN/IPS is an IPv6-based service intended for Air Traffic Controller (ATC)
to pilot and other airline and operational safety-type communications.
The service must therefore provide the highest possible levels of security,
integrity and reliability even as aircraft move between different data link
attachment points. The service must also be affordable, highly available
and fault tolerant.

ICAO envisions an overlay network for secure and mobile IPv6 services
while leveraging existing infrastructure where possible for cost savings.
The ATN/IPS service will therefore require a simple core routing system
that can maintain pervasive IPv6 services even across mobility events. We
therefore offer this document titled:

 "A Simple BGP-based Mobile Routing System for the Aeronautical
  Telecommunications Network"

as a routing solution candidate. We welcome input from the flying public,
since the future ATN/IPS service will apply to long-term worldwide civil
aviation ATM services. We look forward to your comments.

Fred Templin
fred.l.templin@boeing.com

-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of inte=
rnet-drafts@ietf.org
Sent: Monday, March 13, 2017 11:04 AM
To: i-d-announce@ietf.org
Subject: I-D Action: draft-templin-atn-bgp-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


        Title           : A Simple BGP-based Mobile Routing System for the =
Aeronautical Telecommunications Network
        Author          : Fred L. Templin
	Filename        : draft-templin-atn-bgp-00.txt
	Pages           : 14
	Date            : 2017-03-13

Abstract:
   The International Civil Aviation Organization (ICAO) is investigating
   mobile routing solutions for a worldwide Aeronautical
   Telecommunications Network with Internet Protocol Services (ATN/IPS).
   The ATN/IPS will eventually replace existing communication services
   with an IPv6-based service supporting pervasive Air Traffic
   Management (ATM) for Air Traffic Controllers (ATC), Airline
   Operations Controllers (AOC), and all commercial aircraft worldwide.
   This informational document describes a simple mobile routing service
   based on mature industry standards to address the ATN/IPS
   requirements.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-templin-atn-bgp/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-templin-atn-bgp-00


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

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 nobody Tue Mar 21 09:17:52 2017
Return-Path: <Henning.Schulzrinne@fcc.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCBC129B38; Tue, 21 Mar 2017 09:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.61
X-Spam-Level: 
X-Spam-Status: No, score=-0.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fccoffice.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gxBERvS4Ui7v; Tue, 21 Mar 2017 09:17:46 -0700 (PDT)
Received: from mx0b-0024ed01.pphosted.com (mx0b-0024ed01.pphosted.com [148.163.153.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BCF212995F; Tue, 21 Mar 2017 09:17:18 -0700 (PDT)
Received: from pps.filterd (m0102174.ppops.net [127.0.0.1]) by mx0b-0024ed01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2LGDpqp029524; Tue, 21 Mar 2017 16:17:15 GMT
Received: from gcc01-dm2-obe.outbound.protection.outlook.com (mail-dm2gcc01lp0050.outbound.protection.outlook.com [23.103.198.50]) by mx0b-0024ed01.pphosted.com with ESMTP id 298x2etch5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 21 Mar 2017 16:17:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fccoffice.onmicrosoft.com; s=selector1-fcc-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=40HLLg4mGSBGniO73cPEMaDO3w+jgB3RLb/b90ymTpc=; b=jWPXpf7V/Wxj00QaYsqYW7XU/VLJNJnO86JOJjOV43+xSddmW9YbYkBvEWjKj5HfaSnOOXjGQc+aWW12TfC2Xds67dRr0lFucuRRin5HlwacguYOrs9cXMOv5pe9ddmJVCRn2+EoX4Xl45YRTrerHGUQ5oxdTmTAeLsi8L08baU=
Received: from BY1PR09MB0631.namprd09.prod.outlook.com (10.160.110.19) by BY1PR09MB0632.namprd09.prod.outlook.com (10.160.110.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.977.11; Tue, 21 Mar 2017 16:17:05 +0000
Received: from BY1PR09MB0631.namprd09.prod.outlook.com ([10.160.110.19]) by BY1PR09MB0631.namprd09.prod.outlook.com ([10.160.110.19]) with mapi id 15.01.0977.020; Tue, 21 Mar 2017 16:17:06 +0000
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-ietf-sipcore-status-unwanted@ietf.org" <draft-ietf-sipcore-status-unwanted@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>
Subject: RE: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
Thread-Index: AQHSl6Iq2il9S89Skk6DXPjEXEA7BqGfhkwAgAACiiA=
Date: Tue, 21 Mar 2017 16:17:05 +0000
Message-ID: <BY1PR09MB0631F94D0B74E498ECCF3A4DEA3D0@BY1PR09MB0631.namprd09.prod.outlook.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com>
In-Reply-To: <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: qti.qualcomm.com; dkim=none (message not signed) header.d=none;qti.qualcomm.com; dmarc=none action=none header.from=fcc.gov;
x-originating-ip: [192.104.54.21]
x-microsoft-exchange-diagnostics: 1; BY1PR09MB0632; 7:5Clsj+FykMgrlJ6G1oQYX1tAltxUVsCWgyyV0cDPfm6C/wd3WzeTFzWWJeyCSLipJzZZGvz9WPG1bG8F6eYmwu16D894D1jZObsoLVFzHaGcODTZCCZ9A9XYhZuHYznGLUGbvIskuucdBn6nv1dSQf17LS2NUC96I7LItikGKCJDMzVo7b62kSgr1TKOzZJGuvZs34kfKmtYP0jHh5gWKlH21jC4Uvc4oV7fkJClOj+HyYiPGhTrH2pRbduqmK3hEzeJwQkO4E/LfcgeQufEypnpzLiXlqxOTyiPLlcRr7LhEB0BxT8m0m7A1Vs2u4CHkllPwlYZAJIq6rNltfGfjA==
x-ms-office365-filtering-correlation-id: 4c08bd21-9c69-46c7-e4ca-08d47075b7aa
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075); SRVR:BY1PR09MB0632; 
x-microsoft-antispam-prvs: <BY1PR09MB0632B91189319D5567E59BE0EA3D0@BY1PR09MB0632.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(120809045254105)(788757137089)(21748063052155); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123558025)(20161123555025)(20161123560025)(20161123564025)(20161123562025)(6072148); SRVR:BY1PR09MB0632; BCL:0; PCL:0; RULEID:; SRVR:BY1PR09MB0632; 
x-forefront-prvs: 02530BD3AA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39450400003)(24454002)(377454003)(33656002)(54356999)(50986999)(76176999)(230783001)(102836003)(790700001)(3846002)(6116002)(66066001)(25786009)(8676002)(966004)(2900100001)(86362001)(38730400002)(7696004)(6306002)(6246003)(53936002)(606005)(19609705001)(74316002)(3280700002)(7736002)(5660300001)(5890100001)(2501003)(7906003)(122556002)(4326008)(6436002)(2906002)(8936002)(81166006)(53546009)(2950100002)(54906002)(99286003)(55016002)(3660700001)(77096006)(6506006)(236005)(9686003)(54896002)(229853002)(189998001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR09MB0632; H:BY1PR09MB0631.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY1PR09MB0631F94D0B74E498ECCF3A4DEA3D0BY1PR09MB0631namp_"
MIME-Version: 1.0
X-OriginatorOrg: fcc.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Mar 2017 16:17:05.8465 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72970aed-3669-4ca8-b960-dd016bc72973
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR09MB0632
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-21_12:, , signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3k0ZGEhkVHDl3g2OztCshRL1XQI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 16:17:50 -0000

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

Pete,

I believe we discussed several of these issues in the meeting and the early=
 in-person discussion, but the discussion was never quite focused, so it's =
probably easy to miss in the archives. My take of the discussion was that a=
 simple mechanism that reflects plausible and likely UI approaches was pref=
erable to a more complex mechanism. Nothing prevents adding information to =
the 'unwanted' status code in the future, should there be a need. As you in=
dicate, the Call-Info labeling may well inform such an effort.

Yes, the idea was to model the (apparently near-universal) notions of the e=
mail spam button. Indeed, early phone UIs that are emerging do seem to take=
 the same approach, such as the Google Android dialer UI. It offers exactly=
 one option - swipe up to accept and a red (X) button to block calls like t=
hat.

The goal was never to create a full-fledged API for rejecting classes of ca=
lls or otherwise controlling the behavior of voice spam filters. I don't th=
ink that's appropriate for a call response as that would seem to be better =
done via a web interface or other API-based configuration option. For examp=
le, such web UIs may offer more in-depth options such as "no charities, exc=
ept X" or "no surveys except those labeled as high-quality by trusted organ=
ization Y". I don't think we are anywhere close to knowing what this should=
 be.

My sense is that, given UI and user patience limitations, no deployed syste=
m actually uses the Retry-After header, so all 603's seen in the wild are d=
evoid of this indicator.

In practice, users will only be willing to spend a limited amount of time o=
n feedback for unwanted calls. Analytics will be much better in sorting out=
 the "annoying ex" from "annoying time share seller" than asking users to f=
ill out a survey after the call - the former will be indicated by exactly o=
ne person only, the latter by hundreds or thousands. For what it's worth, t=
he same potential problems exists in email, but doesn't seem to have caused=
 any actual problems for spam filters since the statistical signature looks=
 quite different.

Adding parameters to existing status codes can be done, but that seems more=
 a matter of design taste. After all, we could then dispense with all speci=
fic codes and just use 100, 200, 400, 500 and 600, each with headers attach=
ed. This has not been the SIP design approach in the past. I don't see the =
problem with a new status code - we routinely add them and the mechanism of=
 handling unknown ones are quite clear.

Henning

From: Pete Resnick [mailto:presnick@qti.qualcomm.com]
Sent: Tuesday, March 21, 2017 11:50 AM
To: ietf@ietf.org
Cc: draft-ietf-sipcore-status-unwanted@ietf.org; ben@nostrum.com; sipcore@i=
etf.org; Adam Roach <adam@nostrum.com>; sipcore-chairs@ietf.org
Subject: Re: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP =
Response Code for Unwanted Calls) to Proposed Standard


I'm sorry to say that I do not think this mechanism is well thought out, I =
think it actually causes active harm to interoperability, and I think this =
document should be abandoned for a better (and simpler) solution to the pro=
blem, which I describe below.

I will note that I have not been following the discussion of this document =
except for it's introduction at the last plenary meeting, but I (and others=
) did give comments at that time that as far as I can tell were not taken i=
nto account. I did review the thread on the sipcore list regarding the diff=
erence between the new code and the 603 code. That thread does not address =
my concerns, and in fact in some way reinforces it. I have not reviewed oth=
er discussion on the list.

The purported purpose of this 666 mechanism is to allow additional semantic=
s to be expressed beyond a simple 603 (Decline). That is a fine desire. How=
ever, instead of adding decent semantics to declining a call, 666 adds only=
 one additional bit of information to 603, and that one bit ends up causing=
 more semantic ambiguity: The user has still declined the call (just as 603=
 would have), and has added that the call is somehow unwanted (so a provide=
r could act to prevent such calls in the future), but the user has not indi=
cated the reason they indicate the call is unwanted. Is it because they wan=
t to add this calling party to a call block list? Is it that they want to r=
eject all calls of this particular class (cf. draft-ietf-sipcore-callinfo-s=
pam)? Is there some other handling that would be appropriate given the part=
icular reason the user has rejected the call? The best a provider is going =
to be able to do is guess. The document admits the ambiguity in the semanti=
cs, saying that the provider will have to use heuristics to guess at what t=
he user really wants. We should not be introducing a new mechanism that onl=
y adds to the semantic ambiguity and might end up with results that the use=
r might specifically not want in a particular case. What I think was really=
 intended all along was to have un-upgraded implementations treat these rej=
ections just like 603, but add some semantics that upgraded implementations=
 can use to determine what ought to be done in the future.

The right solution, IMO, is to simply add a header to the 603 response that=
 indicates what the user means by their declining, and gives a real indicat=
ion of how handle such calls in the future. Call it "Decline-Type" for argu=
ment sake. Just like the Retry-After header adds semantics to indicate when=
 the caller might want to try an identical call again, this new header will=
 indicate that the user never wants a call from this particular caller agai=
n (e.g., "Decline-Type: block-caller", which the service provider can defin=
itively use to add the caller to a block list), or that this caller and eve=
ry caller with a similar type should be rejected (e.g. "Decline-Type: block=
-caller-type; type=3Dpolitical", which the provider could definitively use =
to reject similar calls in the future), etc.. With this, there's no need fo=
r a bunch of MAYs such that appear in section 4, you get an extensible mech=
anism that could be used by any 603 response. You also get the added bonus =
that un-upgraded entities will continue to treat this just like every other=
 603 without a Retry-After header, which is exactly what you want.

To be clear, the three things I am concerned about are:

1.    The 666 mechanism leaves the decision of what is meant by "unwanted" =
to the provider, which will inevitably cause data loss through the use of h=
euristics. Adding a header to the 603 response is an extensible mechanism t=
hat could capture the single semantic bit of 666 and any future semantics t=
hat one wishes to add, without requiring the provider to guess. The provide=
r gets definitive information that it can act on.

2.    The 666 mechanism limits the implementation of the mechanism to a 1-b=
utton choice and requires additional standardization work to use a differen=
t UI. Clearly 666 was designed around something akin to a "SPAM" button in =
the UI. But what if I want a field in my address book that says, "Permanent=
ly block this particular caller" (say, my ex-boyfriend or my annoying neigh=
bor)? I don't want to indicate that these are spam calls because I don't wa=
nt my provider applying heuristics to them. I want to send back a 603 with =
a header that says, "Block these whenever you see them, but only for me." I=
 can think of all sorts of other-than-one-button UIs that someone might wan=
t to implement. 666 is tied to a particular UI. 603 with a header is extens=
ible.

3.    The 666 mechanism will be treated as a 600 "Busy" error by un-upgrade=
d callers and/or providers. That might imply to some implementations that t=
hey should try to re-dial (e.g., the provider using the auto-redial feature=
) or to engage in other poor behavior. 603 with no Retry-After header alrea=
dy has a semantic of "The call was rejected and I'm not telling you when a =
good time to call back is", so there is some hope that an un-upgraded calle=
r is more likely to do the right thing.

Given the admittedly restricted review of the WG archive that I did, I didn=
't see anything to indicate that the WG fully considered the implications o=
f 666 that I have outlined above. This is not simply a design preference; I=
 believe the design of the proposed mechanism doesn't accomplish the goal a=
nd actually does some harm. Overall, 666 damages interoperability by introd=
ucing an ambiguous piece of information, which will lead to potential data =
loss (i.e., improperly applied heuristics), and will require adding a heade=
r in the future in order to accomplish the real goal. Adding a header is a =
simple mechanism, accomplishes the desired task, has extensibility, and doe=
sn't cause the problems that 666 does. Please reconsider this, drop this do=
cument, and replace it by adding real semantics to the 603 response with an=
 extensible header. It's a quick document to write (a bunch of the text in =
the current document can be reused) and it will not suffer the problems tha=
t 666 introduces. Otherwise, we're going to be right back where were when w=
e started, needing to add a mechanism so that the user can really indicate =
what they mean. This is the wrong solution.

pr
--
Pete Resnick http://www.qualcomm.com/~presnick/<https://urldefense.proofpoi=
nt.com/v2/url?u=3Dhttp-3A__www.qualcomm.com_-257Epresnick_&d=3DDwMFAg&c=3Dy=
0h0omCe0jAUGr4gAQ02Fw&r=3DFJcVoDkWM5EiVcV0ReX8lDU1XeHIYRHfarpk4MK59RE&m=3DZ=
smZFFMTXYB11wQOAzumSkgmvAzLj_2Hn4Z58HTMBvE&s=3DtlEJ9fjpmuZLfEjlkXtf4tDxw4Bn=
i6wK1arhT_2Zddg&e=3D>
Qualcomm Technologies, Inc. - +1 (858)651-4478

On 7 Mar 2017, at 18:23, The IESG wrote:

The IESG has received a request from the Session Initiation Protocol Core
WG (sipcore) to consider the following document:
- 'A SIP Response Code for Unwanted Calls'
<draft-ietf-sipcore-status-unwanted-04.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<mailto:ietf@ietf.org> mailing lists by 2017-03-21. Exceptiona=
lly, comments may be
sent to iesg@ietf.org<mailto:iesg@ietf.org> instead. In either case, please=
 retain the
beginning of the Subject line to allow automated sorting.

Abstract

This document defines the 666 (Unwanted) SIP response code, allowing
called parties to indicate that the call or message was unwanted.
SIP entities may use this information to adjust how future calls from
this calling party are handled for the called party or more broadly.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unwanted/<https:=
//urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf.org_doc_d=
raft-2Dietf-2Dsipcore-2Dstatus-2Dunwanted_&d=3DDwMFAg&c=3Dy0h0omCe0jAUGr4gA=
Q02Fw&r=3DFJcVoDkWM5EiVcV0ReX8lDU1XeHIYRHfarpk4MK59RE&m=3DZsmZFFMTXYB11wQOA=
zumSkgmvAzLj_2Hn4Z58HTMBvE&s=3Dhy8D0YsflQHIyKQiWo_fdbP4Ah_Ej6vFervxifuVyJU&=
e=3D>

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unwanted/ballot/=
<https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf.or=
g_doc_draft-2Dietf-2Dsipcore-2Dstatus-2Dunwanted_ballot_&d=3DDwMFAg&c=3Dy0h=
0omCe0jAUGr4gAQ02Fw&r=3DFJcVoDkWM5EiVcV0ReX8lDU1XeHIYRHfarpk4MK59RE&m=3DZsm=
ZFFMTXYB11wQOAzumSkgmvAzLj_2Hn4Z58HTMBvE&s=3DkX6Ocb3l9f7SR-kaqL7gkLgF0bj11s=
m1YalrviswYQY&e=3D>

No IPR declarations have been submitted directly on this I-D.

--_000_BY1PR09MB0631F94D0B74E498ECCF3A4DEA3D0BY1PR09MB0631namp_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",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
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:744769095;
	mso-list-template-ids:-1811143942;}
@list l0:level1 lfo3
	{mso-level-start-at:2;}
@list l0:level1 lfo4
	{mso-level-start-at:3;}
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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Pete,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">I believe we discussed several of the=
se issues in the meeting and the early in-person discussion, but the discus=
sion was never quite focused, so it&#8217;s probably
 easy to miss in the archives. My take of the discussion was that a simple =
mechanism that reflects plausible and likely UI approaches was preferable t=
o a more complex mechanism. Nothing prevents adding information to the &#82=
16;unwanted&#8217; status code in the future,
 should there be a need. As you indicate, the Call-Info labeling may well i=
nform such an effort.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Yes, the idea was to model the (appar=
ently near-universal) notions of the email spam button. Indeed, early phone=
 UIs that are emerging do seem to take the same
 approach, such as the Google Android dialer UI. It offers exactly one opti=
on &#8211; swipe up to accept and a red (X) button to block calls like that=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">The goal was never to create a full-f=
ledged API for rejecting classes of calls or otherwise controlling the beha=
vior of voice spam filters. I don&#8217;t think that&#8217;s
 appropriate for a call response as that would seem to be better done via a=
 web interface or other API-based configuration option. For example, such w=
eb UIs may offer more in-depth options such as &#8220;no charities, except =
X&#8221; or &#8220;no surveys except those labeled
 as high-quality by trusted organization Y&#8221;. I don&#8217;t think we a=
re anywhere close to knowing what this should be.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">My sense is that, given UI and user p=
atience limitations, no deployed system actually uses the Retry-After heade=
r, so all 603&#8217;s seen in the wild are devoid of
 this indicator.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">In practice, users will only be willi=
ng to spend a limited amount of time on feedback for unwanted calls. Analyt=
ics will be much better in sorting out the &#8220;annoying
 ex&#8221; from &#8220;annoying time share seller&#8221; than asking users =
to fill out a survey after the call &#8211; the former will be indicated by=
 exactly one person only, the latter by hundreds or thousands. For what it&=
#8217;s worth, the same potential problems exists in email, but
 doesn&#8217;t seem to have caused any actual problems for spam filters sin=
ce the statistical signature looks quite different.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Adding parameters to existing status =
codes can be done, but that seems more a matter of design taste. After all,=
 we could then dispense with all specific codes
 and just use 100, 200, 400, 500 and 600, each with headers attached. This =
has not been the SIP design approach in the past. I don&#8217;t see the pro=
blem with a new status code &#8211; we routinely add them and the mechanism=
 of handling unknown ones are quite clear.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Henning<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Pete Resnick [mailto:presnick@=
qti.qualcomm.com]
<br>
<b>Sent:</b> Tuesday, March 21, 2017 11:50 AM<br>
<b>To:</b> ietf@ietf.org<br>
<b>Cc:</b> draft-ietf-sipcore-status-unwanted@ietf.org; ben@nostrum.com; si=
pcore@ietf.org; Adam Roach &lt;adam@nostrum.com&gt;; sipcore-chairs@ietf.or=
g<br>
<b>Subject:</b> Re: Last Call: &lt;draft-ietf-sipcore-status-unwanted-04.tx=
t&gt; (A SIP Response Code for Unwanted Calls) to Proposed Standard<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">I'm sorry to sa=
y that I do not think this mechanism is well thought out, I think it actual=
ly causes active harm to interoperability, and I think this document should=
 be abandoned for a better (and simpler) solution
 to the problem, which I describe below.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">I will note tha=
t I have not been following the discussion of this document except for it's=
 introduction at the last plenary meeting, but I (and others) did give comm=
ents at that time that as far as I can tell
 were not taken into account. I did review the thread on the sipcore list r=
egarding the difference between the new code and the 603 code. That thread =
does not address my concerns, and in fact in some way reinforces it. I have=
 not reviewed other discussion on
 the list.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">The purported p=
urpose of this 666 mechanism is to allow additional semantics to be express=
ed beyond a simple 603 (Decline). That is a fine desire. However, instead o=
f adding decent semantics to declining a call,
 666 adds only one additional bit of information to 603, and that one bit e=
nds up causing more semantic ambiguity: The user has still declined the cal=
l (just as 603 would have), and has added that the call is
<em><span style=3D"font-family:&quot;Arial&quot;,sans-serif">somehow</span>=
</em> unwanted (so a provider
<em><span style=3D"font-family:&quot;Arial&quot;,sans-serif">could</span></=
em> act to prevent such calls in the future), but the user has not indicate=
d the
<em><span style=3D"font-family:&quot;Arial&quot;,sans-serif">reason</span><=
/em> they indicate the call is unwanted. Is it because they want to add thi=
s calling party to a call block list? Is it that they want to reject all ca=
lls of this particular class (cf. draft-ietf-sipcore-callinfo-spam)?
 Is there some other handling that would be appropriate given the particula=
r reason the user has rejected the call? The best a provider is going to be=
 able to do is guess. The document admits the ambiguity in the semantics, s=
aying that the provider will have
 to use heuristics to guess at what the user really wants. We should not be=
 introducing a new mechanism that only adds to the semantic ambiguity and m=
ight end up with results that the user might specifically not want in a par=
ticular case. What I think was really
 intended all along was to have un-upgraded implementations treat these rej=
ections just like 603, but add some semantics that upgraded implementations=
 can use to determine what ought to be done in the future.<o:p></o:p></span=
></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">The right solut=
ion, IMO, is to simply add a header to the 603 response that indicates what=
 the user means by their declining, and gives a real indication of how hand=
le such calls in the future. Call it &quot;Decline-Type&quot;
 for argument sake. Just like the Retry-After header adds semantics to indi=
cate when the caller might want to try an identical call again, this new he=
ader will indicate that the user never wants a call from this particular ca=
ller again (e.g., &quot;Decline-Type:
 block-caller&quot;, which the service provider can definitively use to add=
 the caller to a block list), or that this caller and every caller with a s=
imilar type should be rejected (e.g. &quot;Decline-Type: block-caller-type;=
 type=3Dpolitical&quot;, which the provider could
 definitively use to reject similar calls in the future), etc.. With this, =
there's no need for a bunch of MAYs such that appear in section 4, you get =
an extensible mechanism that could be used by any 603 response. You also ge=
t the added bonus that un-upgraded
 entities will continue to treat this just like every other 603 without a R=
etry-After header, which is exactly what you want.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">To be clear, th=
e three things I am concerned about are:<o:p></o:p></span></p>
<p style=3D"margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2"><!=
[if !supportLists]><span style=3D"font-family:&quot;Arial&quot;,sans-serif"=
><span style=3D"mso-list:Ignore">1.<span style=3D"font:7.0pt &quot;Times Ne=
w Roman&quot;">&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-family:&quot;Arial&quot;=
,sans-serif">The 666 mechanism leaves the decision of what is meant by &quo=
t;unwanted&quot; to the provider, which will inevitably cause data loss thr=
ough the use of heuristics. Adding a header to the 603
 response is an extensible mechanism that could capture the single semantic=
 bit of 666
<em><span style=3D"font-family:&quot;Arial&quot;,sans-serif">and any future=
 semantics that one wishes to add</span></em>, without requiring the provid=
er to guess. The provider gets definitive information that it can act on.<o=
:p></o:p></span></p>
<p style=3D"margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo3"><!=
[if !supportLists]><span style=3D"font-family:&quot;Arial&quot;,sans-serif"=
><span style=3D"mso-list:Ignore">2.<span style=3D"font:7.0pt &quot;Times Ne=
w Roman&quot;">&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-family:&quot;Arial&quot;=
,sans-serif">The 666 mechanism limits the implementation of the mechanism t=
o a 1-button choice and requires additional standardization work to use a d=
ifferent UI. Clearly 666 was designed around
 something akin to a &quot;SPAM&quot; button in the UI. But what if I want =
a field in my address book that says, &quot;Permanently block this particul=
ar caller&quot; (say, my ex-boyfriend or my annoying neighbor)? I don't wan=
t to indicate that these are spam calls because I don't
 want my provider applying heuristics to them. I want to send back a 603 wi=
th a header that says, &quot;Block these whenever you see them, but only fo=
r me.&quot; I can think of all sorts of other-than-one-button UIs that some=
one might want to implement. 666 is tied to
 a particular UI. 603 with a header is extensible.<o:p></o:p></span></p>
<p style=3D"margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo4"><!=
[if !supportLists]><span style=3D"font-family:&quot;Arial&quot;,sans-serif"=
><span style=3D"mso-list:Ignore">3.<span style=3D"font:7.0pt &quot;Times Ne=
w Roman&quot;">&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-family:&quot;Arial&quot;=
,sans-serif">The 666 mechanism will be treated as a 600 &quot;Busy&quot; er=
ror by un-upgraded callers and/or providers. That might imply to some imple=
mentations that they should try to re-dial (e.g., the
 provider using the auto-redial feature) or to engage in other poor behavio=
r. 603 with no Retry-After header already has a semantic of &quot;The call =
was rejected and I'm not telling you when a good time to call back is&quot;=
, so there is some hope that an un-upgraded
 caller is more likely to do the right thing.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Given the admit=
tedly restricted review of the WG archive that I did, I didn't see anything=
 to indicate that the WG fully considered the implications of 666 that I ha=
ve outlined above. This is not simply a design
 preference; I believe the design of the proposed mechanism doesn't accompl=
ish the goal and actually does some harm. Overall, 666 damages interoperabi=
lity by introducing an ambiguous piece of information, which will lead to p=
otential data loss (i.e., improperly
 applied heuristics), and will require adding a header in the future in ord=
er to accomplish the real goal. Adding a header is a simple mechanism, acco=
mplishes the desired task, has extensibility, and doesn't cause the problem=
s that 666 does. Please reconsider
 this, drop this document, and replace it by adding real semantics to the 6=
03 response with an extensible header. It's a quick document to write (a bu=
nch of the text in the current document can be reused) and it will not suff=
er the problems that 666 introduces.
 Otherwise, we're going to be right back where were when we started, needin=
g to add a mechanism so that the user can really indicate what they mean. T=
his is the wrong solution.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">pr<br>
-- <br>
Pete Resnick <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3=
A__www.qualcomm.com_-257Epresnick_&amp;d=3DDwMFAg&amp;c=3Dy0h0omCe0jAUGr4gA=
Q02Fw&amp;r=3DFJcVoDkWM5EiVcV0ReX8lDU1XeHIYRHfarpk4MK59RE&amp;m=3DZsmZFFMTX=
YB11wQOAzumSkgmvAzLj_2Hn4Z58HTMBvE&amp;s=3DtlEJ9fjpmuZLfEjlkXtf4tDxw4Bni6wK=
1arhT_2Zddg&amp;e=3D">
<span style=3D"color:#3983C4">http://www.qualcomm.com/~presnick/</span></a>=
<br>
Qualcomm Technologies, Inc. - &#43;1 (858)651-4478<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">On 7 Mar 2017, =
at 18:23, The IESG wrote:<o:p></o:p></span></p>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">T=
he IESG has received a request from the Session Initiation Protocol Core<br=
>
WG (sipcore) to consider the following document:<br>
- 'A SIP Response Code for Unwanted Calls'<br>
&lt;draft-ietf-sipcore-status-unwanted-04.txt&gt; as Proposed Standard<o:p>=
</o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">T=
he IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org"><span style=3D"color:#777777">ietf@ietf.or=
g</span></a> mailing lists by 2017-03-21. Exceptionally, comments may be<br=
>
sent to <a href=3D"mailto:iesg@ietf.org"><span style=3D"color:#777777">iesg=
@ietf.org</span></a> instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.<o:p></o:p></span>=
</p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">A=
bstract<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">T=
his document defines the 666 (Unwanted) SIP response code, allowing<br>
called parties to indicate that the call or message was unwanted.<br>
SIP entities may use this information to adjust how future calls from<br>
this calling party are handled for the called party or more broadly.<o:p></=
o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">T=
he file can be obtained via<br>
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatrack=
er.ietf.org_doc_draft-2Dietf-2Dsipcore-2Dstatus-2Dunwanted_&amp;d=3DDwMFAg&=
amp;c=3Dy0h0omCe0jAUGr4gAQ02Fw&amp;r=3DFJcVoDkWM5EiVcV0ReX8lDU1XeHIYRHfarpk=
4MK59RE&amp;m=3DZsmZFFMTXYB11wQOAzumSkgmvAzLj_2Hn4Z58HTMBvE&amp;s=3Dhy8D0Ys=
flQHIyKQiWo_fdbP4Ah_Ej6vFervxifuVyJU&amp;e=3D"><span style=3D"color:#777777=
">https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unwanted/</spa=
n></a><o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">I=
ESG discussion can be tracked via<br>
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatrack=
er.ietf.org_doc_draft-2Dietf-2Dsipcore-2Dstatus-2Dunwanted_ballot_&amp;d=3D=
DwMFAg&amp;c=3Dy0h0omCe0jAUGr4gAQ02Fw&amp;r=3DFJcVoDkWM5EiVcV0ReX8lDU1XeHIY=
RHfarpk4MK59RE&amp;m=3DZsmZFFMTXYB11wQOAzumSkgmvAzLj_2Hn4Z58HTMBvE&amp;s=3D=
kX6Ocb3l9f7SR-kaqL7gkLgF0bj11sm1YalrviswYQY&amp;e=3D"><span style=3D"color:=
#777777">https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unwante=
d/ballot/</span></a><o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">N=
o IPR declarations have been submitted directly on this I-D.<o:p></o:p></sp=
an></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>

--_000_BY1PR09MB0631F94D0B74E498ECCF3A4DEA3D0BY1PR09MB0631namp_--


From nobody Tue Mar 21 09:24:43 2017
Return-Path: <ranjitkav0811@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 2A655129B44; Tue, 21 Mar 2017 09:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5SXScKkQScPN; Tue, 21 Mar 2017 09:24:33 -0700 (PDT)
Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09C38129AEE; Tue, 21 Mar 2017 09:24:33 -0700 (PDT)
Received: by mail-pg0-x234.google.com with SMTP id n190so96145139pga.0; Tue, 21 Mar 2017 09:24:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MPg2VpPwONNfp5aXVphyuIc6FqBpUbwA/irI1/OWpVI=; b=kROf5eYipkycsVTIahUCOkEQNI8hKYCJ20MsByJbEHaty56zzoTsrT4IPPoldMVxvW /u/VxqM/Itz6ZvH4utFVOdCpBJKFw5nFXTJWFY5igeRFWvnt46K05OdW9hsm0ZKVUZgR Qrwmy9AWegW68Bl2+wP5gDa9wmuqPkf9zL6D2J/u7RTal4618xQLe0yKDRNqxu72Lfkb dHxI6m6ImHyHzsGnFBefeQja7zjd3aczCdikE0LGp1HyjMD5hPIS4Txh6xuq3XpR1yjZ 914Oc3dFFvxpT35JGRjCgD0lW/Snn5B9ceyqgf0h0skqF4jRiE19ttZzvOX3bLDsmPGm mRUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MPg2VpPwONNfp5aXVphyuIc6FqBpUbwA/irI1/OWpVI=; b=kMDbviHRtizCWrRqaf6ICLvUByprom5EKE044VvAZKo497ACYUfnLCzUWCnp85rNKx bdKRWsVJbpXNrODcxl+u9O5Onbc/H/uRsLOHf3ynTuftbyh5xI7ykXNjTK6HsLt05BB6 xzOkAh5IG9dPGJz6vllN4NT8T5vqlkgKw8qVSNQOaDrae5Ru/mq1vrOHeg1p0Z+HhMnX MenVcVINWK6hgY/1ZHmnH10D5h6pI3asvUNWP6z27z+aD47nMlIqBP0lmQA+i4utkDsF YFxeWMXstWInHRjTyZQRP7pZ4t4JywYd2he3dQMQ76XFBqolhMC7pZpw7OU1NkusY2dy 42UQ==
X-Gm-Message-State: AFeK/H1U5qNWL8pLwIR/MMZAT9rzxhWPjaKihnESwt2DmtIVc1Ik3c5WKTlVXg88ehdGZC7PbN1UJGhuFPazvw==
X-Received: by 10.98.65.211 with SMTP id g80mr40742763pfd.187.1490113472646; Tue, 21 Mar 2017 09:24:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.166.166 with HTTP; Tue, 21 Mar 2017 09:24:32 -0700 (PDT)
In-Reply-To: <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com>
From: Ranjit Avasarala <ranjitkav0811@gmail.com>
Date: Tue, 21 Mar 2017 11:24:32 -0500
Message-ID: <CA+CMEWeW4JtspJXueShWwfpNDt=291NWEX0EUgH0xv2T3xJ7Xw@mail.gmail.com>
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: ietf@ietf.org, ben@nostrum.com, sipcore-chairs@ietf.org,  SIPCORE <sipcore@ietf.org>, draft-ietf-sipcore-status-unwanted@ietf.org
Content-Type: multipart/alternative; boundary=94eb2c0babe0366644054b40142f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lfXnoKo3nxRwPeN582ma2cY0krs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 16:24:36 -0000

--94eb2c0babe0366644054b40142f
Content-Type: text/plain; charset=UTF-8

Hi Pete
y
I quite agree with you.  Instead of proposing a new response code like 666,
it would be better to add or rather propose a new header and add it to 603
response.

Regards
Ranjit


On Tue, Mar 21, 2017 at 10:49 AM, Pete Resnick <presnick@qti.qualcomm.com>
wrote:

> I'm sorry to say that I do not think this mechanism is well thought out, I
> think it actually causes active harm to interoperability, and I think this
> document should be abandoned for a better (and simpler) solution to the
> problem, which I describe below.
>
> I will note that I have not been following the discussion of this document
> except for it's introduction at the last plenary meeting, but I (and
> others) did give comments at that time that as far as I can tell were not
> taken into account. I did review the thread on the sipcore list regarding
> the difference between the new code and the 603 code. That thread does not
> address my concerns, and in fact in some way reinforces it. I have not
> reviewed other discussion on the list.
>
> The purported purpose of this 666 mechanism is to allow additional
> semantics to be expressed beyond a simple 603 (Decline). That is a fine
> desire. However, instead of adding decent semantics to declining a call,
> 666 adds only one additional bit of information to 603, and that one bit
> ends up causing more semantic ambiguity: The user has still declined the
> call (just as 603 would have), and has added that the call is *somehow*
> unwanted (so a provider *could* act to prevent such calls in the future),
> but the user has not indicated the *reason* they indicate the call is
> unwanted. Is it because they want to add this calling party to a call block
> list? Is it that they want to reject all calls of this particular class
> (cf. draft-ietf-sipcore-callinfo-spam)? Is there some other handling that
> would be appropriate given the particular reason the user has rejected the
> call? The best a provider is going to be able to do is guess. The document
> admits the ambiguity in the semantics, saying that the provider will have
> to use heuristics to guess at what the user really wants. We should not be
> introducing a new mechanism that only adds to the semantic ambiguity and
> might end up with results that the user might specifically not want in a
> particular case. What I think was really intended all along was to have
> un-upgraded implementations treat these rejections just like 603, but add
> some semantics that upgraded implementations can use to determine what
> ought to be done in the future.
>
> The right solution, IMO, is to simply add a header to the 603 response
> that indicates what the user means by their declining, and gives a real
> indication of how handle such calls in the future. Call it "Decline-Type"
> for argument sake. Just like the Retry-After header adds semantics to
> indicate when the caller might want to try an identical call again, this
> new header will indicate that the user never wants a call from this
> particular caller again (e.g., "Decline-Type: block-caller", which the
> service provider can definitively use to add the caller to a block list),
> or that this caller and every caller with a similar type should be rejected
> (e.g. "Decline-Type: block-caller-type; type=political", which the provider
> could definitively use to reject similar calls in the future), etc.. With
> this, there's no need for a bunch of MAYs such that appear in section 4,
> you get an extensible mechanism that could be used by any 603 response. You
> also get the added bonus that un-upgraded entities will continue to treat
> this just like every other 603 without a Retry-After header, which is
> exactly what you want.
>
> To be clear, the three things I am concerned about are:
>
>    1.
>
>    The 666 mechanism leaves the decision of what is meant by "unwanted"
>    to the provider, which will inevitably cause data loss through the use of
>    heuristics. Adding a header to the 603 response is an extensible mechanism
>    that could capture the single semantic bit of 666 *and any future
>    semantics that one wishes to add*, without requiring the provider to
>    guess. The provider gets definitive information that it can act on.
>    2.
>
>    The 666 mechanism limits the implementation of the mechanism to a
>    1-button choice and requires additional standardization work to use a
>    different UI. Clearly 666 was designed around something akin to a "SPAM"
>    button in the UI. But what if I want a field in my address book that says,
>    "Permanently block this particular caller" (say, my ex-boyfriend or my
>    annoying neighbor)? I don't want to indicate that these are spam calls
>    because I don't want my provider applying heuristics to them. I want to
>    send back a 603 with a header that says, "Block these whenever you see
>    them, but only for me." I can think of all sorts of other-than-one-button
>    UIs that someone might want to implement. 666 is tied to a particular UI.
>    603 with a header is extensible.
>    3.
>
>    The 666 mechanism will be treated as a 600 "Busy" error by un-upgraded
>    callers and/or providers. That might imply to some implementations that
>    they should try to re-dial (e.g., the provider using the auto-redial
>    feature) or to engage in other poor behavior. 603 with no Retry-After
>    header already has a semantic of "The call was rejected and I'm not telling
>    you when a good time to call back is", so there is some hope that an
>    un-upgraded caller is more likely to do the right thing.
>
> Given the admittedly restricted review of the WG archive that I did, I
> didn't see anything to indicate that the WG fully considered the
> implications of 666 that I have outlined above. This is not simply a design
> preference; I believe the design of the proposed mechanism doesn't
> accomplish the goal and actually does some harm. Overall, 666 damages
> interoperability by introducing an ambiguous piece of information, which
> will lead to potential data loss (i.e., improperly applied heuristics), and
> will require adding a header in the future in order to accomplish the real
> goal. Adding a header is a simple mechanism, accomplishes the desired task,
> has extensibility, and doesn't cause the problems that 666 does. Please
> reconsider this, drop this document, and replace it by adding real
> semantics to the 603 response with an extensible header. It's a quick
> document to write (a bunch of the text in the current document can be
> reused) and it will not suffer the problems that 666 introduces. Otherwise,
> we're going to be right back where were when we started, needing to add a
> mechanism so that the user can really indicate what they mean. This is the
> wrong solution.
>
> pr
> --
> Pete Resnick http://www.qualcomm.com/~presnick/
> Qualcomm Technologies, Inc. - +1 (858)651-4478 <(858)%20651-4478>
>
> On 7 Mar 2017, at 18:23, The IESG wrote:
>
> The IESG has received a request from the Session Initiation Protocol Core
> WG (sipcore) to consider the following document:
> - 'A SIP Response Code for Unwanted Calls'
> <draft-ietf-sipcore-status-unwanted-04.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 2017-03-21. 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 defines the 666 (Unwanted) SIP response code, allowing
> called parties to indicate that the call or message was unwanted.
> SIP entities may use this information to adjust how future calls from
> this calling party are handled for the called party or more broadly.
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unwanted/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-
> unwanted/ballot/
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>
>

--94eb2c0babe0366644054b40142f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Pete<div>y</div><div>I quite agree with you.=C2=A0 Inst=
ead of proposing a new response code like 666, it would be better to add or=
 rather propose a new header and add it to 603 response. =C2=A0</div><div><=
br></div><div>Regards</div><div>Ranjit</div><div><br></div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Mar 21, 2017 at 10:=
49 AM, Pete Resnick <span dir=3D"ltr">&lt;<a href=3D"mailto:presnick@qti.qu=
alcomm.com" target=3D"_blank">presnick@qti.qualcomm.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><u></u>




<div>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">I&#39;m sorry to say that I do not think this mechanism is =
well thought out, I think it actually causes active harm to interoperabilit=
y, and I think this document should be abandoned for a better (and simpler)=
 solution to the problem, which I describe below.</p>

<p dir=3D"auto">I will note that I have not been following the discussion o=
f this document except for it&#39;s introduction at the last plenary meetin=
g, but I (and others) did give comments at that time that as far as I can t=
ell were not taken into account. I did review the thread on the sipcore lis=
t regarding the difference between the new code and the 603 code. That thre=
ad does not address my concerns, and in fact in some way reinforces it. I h=
ave not reviewed other discussion on the list.</p>

<p dir=3D"auto">The purported purpose of this 666 mechanism is to allow add=
itional semantics to be expressed beyond a simple 603 (Decline). That is a =
fine desire. However, instead of adding decent semantics to declining a cal=
l, 666 adds only one additional bit of information to 603, and that one bit=
 ends up causing more semantic ambiguity: The user has still declined the c=
all (just as 603 would have), and has added that the call is <em>somehow</e=
m> unwanted (so a provider <em>could</em> act to prevent such calls in the =
future), but the user has not indicated the <em>reason</em> they indicate t=
he call is unwanted. Is it because they want to add this calling party to a=
 call block list? Is it that they want to reject all calls of this particul=
ar class (cf. draft-ietf-sipcore-callinfo-<wbr>spam)? Is there some other h=
andling that would be appropriate given the particular reason the user has =
rejected the call? The best a provider is going to be able to do is guess. =
The document admits the ambiguity in the semantics, saying that the provide=
r will have to use heuristics to guess at what the user really wants. We sh=
ould not be introducing a new mechanism that only adds to the semantic ambi=
guity and might end up with results that the user might specifically not wa=
nt in a particular case. What I think was really intended all along was to =
have un-upgraded implementations treat these rejections just like 603, but =
add some semantics that upgraded implementations can use to determine what =
ought to be done in the future.</p>

<p dir=3D"auto">The right solution, IMO, is to simply add a header to the 6=
03 response that indicates what the user means by their declining, and give=
s a real indication of how handle such calls in the future. Call it &quot;D=
ecline-Type&quot; for argument sake. Just like the Retry-After header adds =
semantics to indicate when the caller might want to try an identical call a=
gain, this new header will indicate that the user never wants a call from t=
his particular caller again (e.g., &quot;Decline-Type: block-caller&quot;, =
which the service provider can definitively use to add the caller to a bloc=
k list), or that this caller and every caller with a similar type should be=
 rejected (e.g. &quot;Decline-Type: block-caller-type; type=3Dpolitical&quo=
t;, which the provider could definitively use to reject similar calls in th=
e future), etc.. With this, there&#39;s no need for a bunch of MAYs such th=
at appear in section 4, you get an extensible mechanism that could be used =
by any 603 response. You also get the added bonus that un-upgraded entities=
 will continue to treat this just like every other 603 without a Retry-Afte=
r header, which is exactly what you want.</p>

<p dir=3D"auto">To be clear, the three things I am concerned about are:</p>

<ol>
<li value=3D"1"><p dir=3D"auto">The 666 mechanism leaves the decision of wh=
at is meant by &quot;unwanted&quot; to the provider, which will inevitably =
cause data loss through the use of heuristics. Adding a header to the 603 r=
esponse is an extensible mechanism that could capture the single semantic b=
it of 666 <em>and any future semantics that one wishes to add</em>, without=
 requiring the provider to guess. The provider gets definitive information =
that it can act on.</p></li>
<li value=3D"2"><p dir=3D"auto">The 666 mechanism limits the implementation=
 of the mechanism to a 1-button choice and requires additional standardizat=
ion work to use a different UI. Clearly 666 was designed around something a=
kin to a &quot;SPAM&quot; button in the UI. But what if I want a field in m=
y address book that says, &quot;Permanently block this particular caller&qu=
ot; (say, my ex-boyfriend or my annoying neighbor)? I don&#39;t want to ind=
icate that these are spam calls because I don&#39;t want my provider applyi=
ng heuristics to them. I want to send back a 603 with a header that says, &=
quot;Block these whenever you see them, but only for me.&quot; I can think =
of all sorts of other-than-one-button UIs that someone might want to implem=
ent. 666 is tied to a particular UI. 603 with a header is extensible.</p></=
li>
<li value=3D"3"><p dir=3D"auto">The 666 mechanism will be treated as a 600 =
&quot;Busy&quot; error by un-upgraded callers and/or providers. That might =
imply to some implementations that they should try to re-dial (e.g., the pr=
ovider using the auto-redial feature) or to engage in other poor behavior. =
603 with no Retry-After header already has a semantic of &quot;The call was=
 rejected and I&#39;m not telling you when a good time to call back is&quot=
;, so there is some hope that an un-upgraded caller is more likely to do th=
e right thing.</p></li>
</ol>

<p dir=3D"auto">Given the admittedly restricted review of the WG archive th=
at I did, I didn&#39;t see anything to indicate that the WG fully considere=
d the implications of 666 that I have outlined above. This is not simply a =
design preference; I believe the design of the proposed mechanism doesn&#39=
;t accomplish the goal and actually does some harm. Overall, 666 damages in=
teroperability by introducing an ambiguous piece of information, which will=
 lead to potential data loss (i.e., improperly applied heuristics), and wil=
l require adding a header in the future in order to accomplish the real goa=
l. Adding a header is a simple mechanism, accomplishes the desired task, ha=
s extensibility, and doesn&#39;t cause the problems that 666 does. Please r=
econsider this, drop this document, and replace it by adding real semantics=
 to the 603 response with an extensible header. It&#39;s a quick document t=
o write (a bunch of the text in the current document can be reused) and it =
will not suffer the problems that 666 introduces. Otherwise, we&#39;re goin=
g to be right back where were when we started, needing to add a mechanism s=
o that the user can really indicate what they mean. This is the wrong solut=
ion.</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"colo=
r:#3983c4" target=3D"_blank">http://www.qualcomm.com/~<wbr>presnick/</a><br=
>
Qualcomm Technologies, Inc. - <a href=3D"tel:(858)%20651-4478" value=3D"+18=
586514478" target=3D"_blank">+1 (858)651-4478</a></p>

<p dir=3D"auto">On 7 Mar 2017, at 18:23, The IESG wrote:</p>

<blockquote style=3D"border-left:2px solid #777;color:#777;margin:0 0 5px;p=
adding-left:5px">
<p dir=3D"auto">The IESG has received a request from the Session Initiation=
 Protocol Core<br>
WG (sipcore) to consider the following document:<br>
- &#39;A SIP Response Code for Unwanted Calls&#39;<br>
  &lt;draft-ietf-sipcore-status-<wbr>unwanted-04.txt&gt; as Proposed Standa=
rd</p>

<p dir=3D"auto">The IESG plans to make a decision in the next few weeks, an=
d solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org" style=3D"color:#777" target=3D"_blank">iet=
f@ietf.org</a> mailing lists by 2017-03-21. Exceptionally, comments may be<=
br>
sent to <a href=3D"mailto:iesg@ietf.org" style=3D"color:#777" target=3D"_bl=
ank">iesg@ietf.org</a> instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.</p>

<p dir=3D"auto">Abstract</p>

<p dir=3D"auto">This document defines the 666 (Unwanted) SIP response code,=
 allowing<br>
   called parties to indicate that the call or message was unwanted.<br>
   SIP entities may use this information to adjust how future calls from<br=
>
   this calling party are handled for the called party or more broadly.</p>

<p dir=3D"auto">The file can be obtained via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unwan=
ted/" style=3D"color:#777" target=3D"_blank">https://datatracker.ietf.org/<=
wbr>doc/draft-ietf-sipcore-status-<wbr>unwanted/</a></p>

<p dir=3D"auto">IESG discussion can be tracked via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-sipcore-status-unwan=
ted/ballot/" style=3D"color:#777" target=3D"_blank">https://datatracker.iet=
f.org/<wbr>doc/draft-ietf-sipcore-status-<wbr>unwanted/ballot/</a></p>

<p dir=3D"auto">No IPR declarations have been submitted directly on this I-=
D.</p>
</blockquote>
</div>
</div>
</div>

<br>______________________________<wbr>_________________<br>
sipcore mailing list<br>
<a href=3D"mailto:sipcore@ietf.org">sipcore@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/sipcore</a><=
br>
<br></blockquote></div><br></div>

--94eb2c0babe0366644054b40142f--


From nobody Tue Mar 21 09:30:13 2017
Return-Path: <ietfjournal@isoc.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 55F3B12AF6E; Mon, 20 Mar 2017 04:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L3CF35sM9aV1; Mon, 20 Mar 2017 04:38:03 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0074.outbound.protection.outlook.com [104.47.34.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 274E9129C73; Mon, 20 Mar 2017 04:38:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=zluKOeNE65iIiRFI1xhinx3oS8+02IjJ3jVk8JMNmHc=; b=KkYk42eN5hgF0QzAZR/Yv53jOmnkMvgG6xCKdEcjKZL8JmnBxhdSk9RBx93Aa84iA6ekRAtBeN90Nsf6BeK65rpBDoDmKmf0we3ygC91yINjY1UeN4/X4G3nz/kWIuncWo07E4hJDS04hFqbiYek3CF+LlwfaV3qOIzycd3zcgM=
Authentication-Results: isoc.org; dkim=none (message not signed) header.d=none;isoc.org; dmarc=none action=none header.from=isoc.org;
Received: from [192.168.3.80] (81.2.114.177) by DM5PR06MB2636.namprd06.prod.outlook.com (10.168.199.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.977.11; Mon, 20 Mar 2017 11:37:59 +0000
From: IETF Journal <ietfjournal@isoc.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Mon, 20 Mar 2017 11:37:57 +0000
Subject: IETF Journal: Latest issue now available
Message-ID: <B026C48B-01A0-4F83-9D9D-A748CCA623AA@isoc.org>
To: IETF Journal <ietfjournal@isoc.org>
X-Mailer: Apple Mail (2.3259)
X-Originating-IP: [81.2.114.177]
X-ClientProxiedBy: HE1PR0402CA0011.eurprd04.prod.outlook.com (10.175.27.21) To DM5PR06MB2636.namprd06.prod.outlook.com (10.168.199.9)
X-MS-Office365-Filtering-Correlation-Id: e1c9fd4e-699c-425c-7285-08d46f85909c
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DM5PR06MB2636;
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2636; 3:lZZst+snTlMOyor7fuKXJEECQIuqQBPVHDsjCF8myus8bCIXrbdOlnuR9cSIyErI7r7VXHh159RAikh/Hm4qSG0MgTKplOFzS0XqMRo/1QPxDucyrML7tY8WdCGphiRk6MbBJRm0KXHFIUhidIkQ5yCuLhIT3TeBg/Gtab98Ui1dHSoPEaQquqRJMn/0Fzn4KS0o3SJfb2fGfL8+r0V8i2l/al16oytVzQT7kobOmn+J3dbGWiIgI4gg4Dbp2wKt7t4oE8s84sX/568zRaG0jQ==; 25:9tL6zX0D+pG3bQZg7UBBDt3MSrjZKMDCeol6YBBNvtVeBJsBddP8cXmmz3GdwNt+V5Jvpvs070WygGiXLiTpKUJet7coqaoBXjE7Nwmi9BBId6UFzvmwdRHnZusB2KR0TH+mmLeWvjwEQZV8lRugkXfeuwezXAAopCdlE3351j3jiZQB41Pcu93NksGJknkp6gtYdJMguM/GC4mc+koEtdWQopVJT6cDpiQRy0ZNUkoR953T77DcXbV3aHTXC/YN5acKXPCmRFAFVfGC74/xsYYBZ9eCuAG/Az4Qj9Z9cYWqJcMt7Lz8j0uCYVvPySSAq0DAhdNbY2WcSvjozk9i9ieVAzj0/Vb7gvIulvhreTy+aHK7QtE9fWJDEnySWEvBx8p7AzbZlTXjPjAoMncEZXjXFkxReCU8RDialgpHDEYgC8HA9kvsmXRffFiSG0/d0TT9zX3/omkhhACYJNvq/A==
X-LD-Processed: 89f84dfb-7285-4810-bc4d-8b9b5794554f,ExtAddr
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2636; 31:+qJ4KO0xIv25TZ/+YxT+vgV2Oo0UKy13n5Ascpj9i2sQ3CMaL/3BTiLhY/VU4gwhJDtZInQ6I7WfMOVBkd0mjsuLnx0K2KTj1TiS0ZJlfB0KBg9TCy4U8t3t5yxsecBP+IEBg9mMBm+RMjlGmdN0oQ0fC7hNYZ6Slr/J2Nc4e5BndgW++MQgvS9RMdBGQGG4XdiSPaqqOcUdMIriNAtWRf+5yDSI39Y9ata7YUqylzU=; 20:udFTqlT8GdZIsjas/ftm3c7fWSUdN3Z+Ix1uxSSgs0WpYhvG1JoYIsh02eeCDLVQe4df9ZdcxUyuIHatYnlIE2HOP16OyAsnMZC3gl0++r53cEfdOq4Q1wapusqEUYck0ZWizAzHq1S/ItheEqMfitTAEQl1DxfvLcuWSYDFofbQb39/4HwXqb7s3p72OhvqJP4ckqUcK/JMrZHX2OjxPLSDcIVbRGUjGw5cttjtEy9N1jpW2nZ+30Ww6dDzF1Hkgnngla8a8pQ9hHjswcwvvDOdisIqe3bMczateD+TFwejtPvhQhPIBybdfKw+9jVdJFhvZrBUkmeltm2CizbBsEEhaubbrtUyyg8VZc+DRIiCtldPf/sYR7mVPQ1wfpU3HbdSe+Wiwg/cX+8j/ds3m8E537bcHn4KmGl7sBvz2kqRk6fCdWsuSvfhvdyFZaDDj5+ZUluO5FXs7yOh9yx/eytNCjPW/NMnMipnstLjgKKmuhHoeI9CbgV6Rr5vsLFL
X-Microsoft-Antispam-PRVS: <DM5PR06MB2636C135A8C558BEE088317DC73A0@DM5PR06MB2636.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(148322886591682)(209352067349851)(81227570615382)(5213294742642)(64217206974132);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041248)(20161123555025)(20161123562025)(20161123558025)(20161123560025)(20161123564025)(6072148); SRVR:DM5PR06MB2636; BCL:0; PCL:0; RULEID:; SRVR:DM5PR06MB2636; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2636; 4:OhV3kTSlV+LHaoxqk9Lp9suIytovMZqyrqVmFupl9WbL4OAUXDp3SX1tgFoSJj7QKxZ5bu0V7wMgSyBVynkeGNqZM2zs3UkIxuGCghHQeus0wfeZsK45ybfK8mnC7QQR9QqhutdU1BPfQoN7kuNXk3fxJMIkAptkpHWGPivmIeWAH4FebToa1UlDsI2BJpjl9lEGk8M15xwq3Nh1NBpVCaaI1pIVYWeK47ZzlaWS4NOmWj4zApJjTNvHNXo1i+2C8AzE/SaAmnq6MyfY+AEabiPY3tDEbGruR7wYCwMe+N0qXYJoU9l0Z8A70tFVlvA+WtzIwvY+fJ5SNFyKS/8yUZhqWrjeK20wMybKFJzLDSNZvTO08NMlmcIEMBgzo177Nf7533BZYInjxp27vblXDiFvYE1KqpaM+NrCeXNHhrIkKIa6NfbnFwqdlUvkqzxXp/XmQ8/7F/hR+sZKhbe38/CbY28kNQ8+X9wSrXAXFNBm5YEVtq/Hz210P/n25ngSDB9D/x9wS2eWLQAkPov5IEsHbcRbxj4CXH8ENCtwJen7UQIaWo5IxtNyN0nPORaDDd2LT0CaHCkXORB5FeERQ7AXe7ZzeBgi+e9T2v43eNMcKryrRxkikPTFP7pTwTafTikM35jbZsYC2cbFF+wdP/HA5xj3QXDOzg/i6SZstjUEphVfcyVLqAkyWkImQhw2zA2bfch8lbWNwbzuf+3/1NsAIMu0KBAXZLWYPgMskYDLOrDlX5cjOzrY2BHCOHhJsZzXqx7gqHoYloUfPlymTv+AVSFhcw0RBVw4lxtsJpE=
X-Forefront-PRVS: 02524402D6
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(6049001)(39450400003)(31014005)(66654002)(189998001)(36756003)(110136004)(2906002)(33656002)(8746002)(38730400002)(6862004)(5660300001)(117156001)(305945005)(86362001)(47776003)(90366009)(53936002)(57306001)(81166006)(7736002)(25786008)(6200100001)(6486002)(66066001)(77096006)(50986999)(42186005)(6306002)(8676002)(3846002)(50226002)(23676002)(6116002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR06MB2636; H:[192.168.3.80]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2636; 23:YGWezq1Ieq1eA6LhCYsJmxTFGxHjZtxLIHueoJ/aS98G7Ue87IS4nBJxx4kVdeiuqYNW0JBncAAuflYMx7S5CqrvILeuEL1T9Bj7g5YF+Nb1iZStv78GfxLtH2cG33aS7mXyfYEf4zOUWcNXJEp1nYu1WocpNWoziMs9YNej0XUlXNJtIafU63kygT7/mgA4NTkLN6G14t7L7hFOI7WsyRTFGWo5IeI+D9DCqUvi/MADprvGkTWxI43FLA5foPDLGY3EhO2g52in3CUQOoS325/D7ROHsolKh6i3MLRwhxIIVm9tQqba4TCGzAQlxUgP02C6BGPeWuGpyoTYZ8wZtA6xH3dwBub8sjQAHvXuM8zkDzdtXXaqzJun3KdK44vrzc4Ges2q0eCIziMXLecKRqbfUrwe+LH5Jhz6MkO6+wZ6F1xd7CRGhAhMtThclhsgksVnQb0Q0URvlYRwWsGwmdPzosWWnJcK1TQxj6AVxe8+1DBvub2uurEfeKBq1JBbrzq5at1ZAhlcTn1jj9Ht6RVSlBcJF4B32iNFr88ZVR+TphOznAyptrh5vdsbLVRElo29OStk07OiYnfa4p5xg/7K862A9J2oB8t/sk+HsY59MaLx7Hw2I5A1J7ZuidmH6koERgkZ8ylic3hlYwn0qaI/+QtHPyCUgOgDWkvdMt/2gAzcWVZjhvu18Ed8joLSps0KHOR96gIkvZuQtgj8wCk9D2W9xepStHkWvv8FM+lUEYMtn3EiTo4ZUy0sj/mRuADUfuGCjkXP8znsai9/3hdgRcEUlVa9i7emqlHTi4qKjL/22RI7pUHW4/VtCG/G4F1axnaNSytZ1r4D+O711bUWdc1h1NdWTuimZp++70mUJS3Sar483fWYxna0ZUXCUO7zEJGSwy7RN10NwMXdwoxhbDFVzAwLOcHGjrtvwfDJrwff1VTI+4HtEOOWchFe
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2636; 6:EUCu2tWR3priFLnWTZdHOB5WGVunhqJZyLTA8OYNAyll/gBPLg0gltwBAPlDtRnym0qrX0+S+yJuTaW6hljAIv/Xw9hdcjJizjHHZI0sLVQqZJZ8yEhOamnWI6/SepUbji2htDjKCYX3g+8YksLesRiDlVk8x/l5nf4spIt7cnp1jJrjmAQeQ6hqxDVZLP9P1HKh8XXKH0ntrnFfdc7gXmT0nsnH/+HD9d9z80er/QicO0pmLqnJG+hKePamsBgVYaVzEHGIFr5rGpy4FABBiRbTqcsMdH61YsCKmeWj6EewnP/jl31tYfRaIPv3Y2oa4pAqbACjGAXQYdCptk9G5UGWqSD7kbnPFknZiDqRxHOnQPPmyVT28D8Vht+7/oGXLt9G5r8u2LbhAEKLhGQgHg==; 5:Sw6L0g5nH4ynwXZ5gfWntiEeVFd30IzwDrJvdWgw6pq7my+IcfBuyzLuaLXxPF6029NeccpmDiI3JKJkjdPMgMJsmK5bDfdVq2rjkJK5epF8zl7ttwLCZju5s5cu92L5FbN/Vf1O+kw/AkZev1GHYq3C7zemWLjEYt8g55YGy/w=; 24:5XLrlyIbO5mBR9Yu/OM64UFvotpXN6K69enMzgBscqwZZ+edZkkHmhUTxzOclFHeSTo+8aPkdSu0UDhGodOOcUH07l80hWX7e6lJUtl15v0=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2636; 7:Rwn82CI8M9C+9rrVCkDGTL4q1Ln9zjzOINnd7RD73xRqEBC1bYz/lYPI2Lu0pc1VBLJyPEWxDBraLamyjaSPNuvDtahLENF1Qpr4FisNJLnbqN2or4GXf2URXDFkjBTLnOsKYPbm0gAcG14mebcMu5tEG5G/tf48RKgbQWz3f6+ZRK5FFWhj4HQziT3nYbc1KnOyAoF3MXuA58cQ+KW4kIqHbJxnkm0UQ+ZWlCgLRH0HCPmiM/WhKlJCqq6zBY/e0pDed10B+apMRcvUj7Mm7A/DX+xMwSyhbQU0x1S/8KUObJPCvmMUg7PDr4E+vOtGxKz7v4RtTAVidYLZ+i5I1g==
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Mar 2017 11:37:59.8463 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB2636
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ooBpA8N3tbeAY7djqrbbigES1O0>
X-Mailman-Approved-At: Tue, 21 Mar 2017 09:30:12 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Mar 2017 11:38:05 -0000

The latest issue of the IETF Journal (Volume 12, Issue 3) is now =
available online:

	<https://www.ietfjournal.org/journal-issues/march-2017/>

Our cover article is a manifesto of why Internet-enabled businesses =
should care about the open standards and open source communities. We =
present the first two of a series of interviews with IETF leadership, in =
this case outgoing IETF chair Jari Arkko and his successor Alissa =
Cooper.

Also in this issue, you=E2=80=99ll learn about CodeStand, a new =
initiative that matches developers with coding projects related to IETF =
activity.

We have several Working Group and BoF updates, a summary of the pre-IETF =
Hackathon, and an article about the Internet Society briefing panel on =
the topic: The I in IoT: Implications for a Global Open Internet.

You can read this issue online or download the full issue in PDF format. =
You can also keep up to date with the latest issue by subscribing to the =
IETF Journal as an email edition or have it delivered to your postal =
address in hardcopy.

IETF Journal is on Facebook (www.facebook.com/ietfjournal/) and Twitter =
(@ietfjournal).

Hardcopies will be available as usual at the upcoming IETF 98 meeting in =
Chicago, Illinois.

Many thanks to all our contributors. Please send any comments or =
suggestions for future issues to ietfjournal@isoc.org.

 =E2=80=94 Mat


Mat Ford
Managing Editor
IETF Journal
<https://www.ietfjournal.org/>


From nobody Tue Mar 21 09:48:51 2017
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 AB7B41294E5; Tue, 21 Mar 2017 09:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level: 
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iIgDdNzdBTDj; Tue, 21 Mar 2017 09:48:46 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20097.outbound.protection.outlook.com [40.107.2.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93347129B83; Tue, 21 Mar 2017 09:48:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Zai18D3SedBHbjStZsMNAHzUBjZMOl6KHy1Nd/rhi+E=; b=bxflH63+se+UiOQn2Vbi8KAtqeA+I1WU99GTNg0DA6JnJikB2PzE2044JnQosdF6i9azaumZvu812TXCgCQsmBt4rYXkni3qC3awY6izpRYT2504KuvzV/yawJ3iDXsUGxir8/qJTXZc5JyXzt7tveJ9rkJmJ3uLuQsn67j+t6M=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.185.203.75) by DB5PR07MB1560.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::10) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.991.4; Tue, 21 Mar 2017 16:48:38 +0000
Message-ID: <011901d2a262$c59162e0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
CC: <rtgwg-chairs@ietf.org>, <draft-ietf-rtgwg-yang-key-chain@ietf.org>
References: <148976778864.13097.8837542947858587684.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-ietf-rtgwg-yang-key-chain-15.txt> (Routing Key Chain YANG Data Model) to Proposed Standard
Date: Tue, 21 Mar 2017 16:44:52 +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.185.203.75]
X-ClientProxiedBy: VI1PR0802CA0021.eurprd08.prod.outlook.com (2603:10a6:800:aa::31) To DB5PR07MB1560.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::10)
X-MS-Office365-Filtering-Correlation-Id: 8e988e26-a379-4632-db9e-08d4707a1fca
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DB5PR07MB1560;
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 3:s0ifRV0tK8tPYlpvpdSydtEgB17huZMzPZg/uQ5PDj7IB/coYkIfh+SCfWR9A3lYBs8WHH0neoEUiW/ZdzsVshV8RDx91IPBVtQFJkCLfNjNl146CXxMp50usEF0rGYj+daP5QEN7X6NYtt3aNmOQmuVygtMEBaodKI5CJguxAdxnrZkZjP3D162+ojszhL4ahKl8ClHc2CIL1+439x+9WaCsiPoiqYn7SDPrVyM7cTV5O0YtzvrAYWzWDPPCwHdcHrh+pHC+jy6sAPpgS7PDw==; 25:lRVt8yLRkQZdHJibt/BfPdb19Hbh+GB6EQ5fA+wCVhrHg+9dt9BT56S4tdXvwfmovYYF6Rbu/+5kt731XzZ1PIRIygfTeKxq9KbnAppB9MSExVQBetOkrzz4GAme8I9DgRDkaSNDk4AoFq1UcFrxcDIJpUMV0dEM6pzOcDEaBaMkVCmvt4kI7M16P+qV8v9k6lLWE40E9q8c2vUu89BaY+d1avaItYtWBhhR7bU4wIlhfBdw7NyQIAvB++oDAB4OY2lwIEcHOg6yw0WIHzxV/mMzHd4MHWlWQpd5qNX5p2dgZfFswbq7enroFcOxLluVSIOCKCrzdtOZAhqN4uDhp6d4XrK9ieGm6PWQe+L5tx6bWekzD6IQzUxVVJjQutgwMzQYljhnevei7HSYIgetWBSVr8OaT/Prb9qYeoMzMQbXnsfWr5kM0mv+REnibuR9qjLT4Qtg+aq+0vSWY40CgQ==
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 31:VHi20aRRkSWhFhRFUmHaK1OIEKWFi772ToWnaCRd3LFdBHTHSQolvQMG7MsLFVKnFo1RdbIVVBTPkrjIID4L55IU0P0udkcQyp3rD9F2jtoNEDqfDMj1oZXA4pDG/8V3bp6+BQwGUznbO+F6lUXHbRvEsDdj/aSSk/SVdWSyqStIpxCXu16Y56rfnDiv4jBm5eiNQMewQcWkIG3umx3DABnfKI0xXPOxhzrTC1hU++8HluvGs9tyPFLVrt4rbviBoP/7bX/3FD81l7phDEdrMw==
X-Microsoft-Antispam-PRVS: <DB5PR07MB1560807E74A2AC80413B2282C63D0@DB5PR07MB1560.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(278428928389397)(120809045254105)(131327999870524); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123558025)(20161123562025)(20161123560025)(20161123555025)(20161123564025)(6072148); SRVR:DB5PR07MB1560; BCL:0; PCL:0; RULEID:; SRVR:DB5PR07MB1560; 
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 4:pCLeIrDNX4+pqe6g1X3gE1fR6Ru+K+CMmFKND2QNjbXFroRVHoSQV+0tx2a9lOrn6cXUT/8o7pYJqXpV0RHF09aPD4seBg/fJX/tZLRTiKE4rqFZq00Fk00ogt8FifkExPkDWeNDlZXycUJBO+LyAx15MMq9/QN6QAleeOW2YA41ylyJ6704/045NaPoVO9RZ8rweGJ4nAiFkPts/wg/878kPqQhjcAIzg2toHkFIbzYmtdn9yA9cXN6aCzs5iRFPJurW60l0MOXMY+SRUqEfLxeiKB4gVRFhdLe6llA+v1rPHG5cp/+/pouummTSni3fy7vYZL8ZT6b6Wom8sS/UlSBbGCXZMJFecXu8SbZgmh+KCdCAZs79taeHo9rXQwSY1khV4ETTsAm3MolAtE6arxvo4ymRZsYMVaDE4SBo05NQrkEZNX9piA3YS9Y/c73KYLm8qNvYlFgLLqLWIHqBKdgdZNvJjhI4eWkGJQOvOh+ajYU7F38NEeyEN8Oij4lE6zOREqdriDHIcxmDNgtxFv6QvopRkGXGjbzsTaI+aBdkhYy066iMORm8AmqswsKG32mr6G+/PyuO1/sbNXgAgN2OzEtbAZvf9EID3dWCE5VjgoNEeYNVawHN2HB81O5LE4y3IuNdTsjAdCHXzfyR9MKzUb7Reghgm+H22Ovz9O/bFT7Skez8bgP1I2m+PhC7aAr/cJchoqujLIapao8JrmVjopEDM+0A5pYqmeAOdw=
X-Forefront-PRVS: 02530BD3AA
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39450400003)(13464003)(377454003)(6916009)(5660300001)(110136004)(6666003)(81816999)(76176999)(6486002)(189998001)(8676002)(50986999)(81686999)(450100002)(4720700003)(6116002)(6496005)(229853002)(230700001)(4326008)(6246003)(54906002)(6306002)(1556002)(38730400002)(53936002)(44736005)(9686003)(3846002)(23756003)(2351001)(7736002)(305945005)(2906002)(62236002)(84392002)(66066001)(47776003)(44716002)(42186005)(61296003)(86362001)(116806002)(230783001)(81166006)(50466002)(50226002)(33646002)(25786009); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR07MB1560; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; DB5PR07MB1560; 23:cm8Jqbsc4kWkXVdRfD2gRrwseoBGk2viQVJ2T48?= =?iso-8859-1?Q?inT6VRWISb10pWQGBK2ZFcyDmNpb+R3kjvVxp+JpKaF9Ddylb4M4vBzVz/?= =?iso-8859-1?Q?Z4Q7RxS0giR2FiJs0RsqxCyqs7aj2I3UV1AjP9QeNjIHCyVv8f9VlaBMtf?= =?iso-8859-1?Q?pueyWbKVw3MoO/V9qCXzlp/qWjdJWjhRKX5UNymdK8nLrQUwqqwObDqHJg?= =?iso-8859-1?Q?RJwz2aBvbCgSaxUN7LJIswYGlKEWorYOWM3H0A3WQxJdEmAZPKq2XUchjz?= =?iso-8859-1?Q?XHbuwuIodILxwvoKwMJWE3YvwH7eBUn9Y6yHXRPEGqtoblu593xbQzDKj5?= =?iso-8859-1?Q?m2tZX6aQx+V7VOzQsV3nQi5gtsqQkuMVV79T5SAhzNq/KJpEbtMAlo2Dsg?= =?iso-8859-1?Q?gnCwnnHloHFTE3ejCCDNZ9LC/kPO7LF2bB7Ek0O3ROvuxSuYMqrFGoq4qZ?= =?iso-8859-1?Q?6Ig5v+LB8/KR+r+C9GtqbWTdqV6LhjcRDIWtN3rn7d4p5mWTFlgW7j5eX8?= =?iso-8859-1?Q?aSQBSXANda59N9sGcpBae5Jt7McBc26+Aqim63wbApgcc3Y81IF25CfzWI?= =?iso-8859-1?Q?SqVDXVhMnhiDNfda4Up/JG2dtID6JajgWJkjiuh4VivxUMWXjItGm2ujkg?= =?iso-8859-1?Q?9Ul6I8OrYGo0hoDuzKtyR0IWKuFe5Own7uLBR1a+QiemtX/UOLFTBG3NTp?= =?iso-8859-1?Q?8BWPZY8rtbzLBcyHcon+nZZ+v4VZPpZoo6D0Wmyl77gz4qPh8kwEuF56fM?= =?iso-8859-1?Q?uIhxCuE30koYvde8R/QdZ8cRm2ZlcwXZmWylUpTewefu22cv4b9IJHH9BP?= =?iso-8859-1?Q?rbSnLzw7x7LrDwdZAxiJ6wpCLd5DGxLoFK83ynbTzXb6kUa9iWOLrtrx9k?= =?iso-8859-1?Q?bwOPA+n6YG3OilzgmtvCQ/pmf2hghmbIXfghWxh4QhaCG/HXMMCtDHi/IQ?= =?iso-8859-1?Q?tmS945qAc0cDaipvci/R//BlJc1nAlFArzWd5GZ41mNYiUwc+uc23lpxZe?= =?iso-8859-1?Q?EC0U71ehxvd2LnH/eVLX9WpzY1lGYc0HJ8UfNHXpWHfrur5d9NnP3oJ3oA?= =?iso-8859-1?Q?5zmi2oFI+cfumV+1nI7LYvXY2Zps2Yei2mpMKkPr2/0KgDXHsu8gAaEhwz?= =?iso-8859-1?Q?N1GOEny0w24LPlnSmxjz0bORQfsm49lIuEWcxdaQBPQKgFSIRY6Zh3xH4+?= =?iso-8859-1?Q?MvmyWofx6Yhgmji9biPQRENFB1gwpzwNR1+X5km1kaVOlK6z6Z2jNy1d2v?= =?iso-8859-1?Q?JrPDBtHYjZAlInSxOW4kel/ntd57pDRege8MLlSM/9nyy4iRO1K6aFp5/Q?= =?iso-8859-1?Q?O8=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 6:fA8GBYTchJBwvCz9A+v+xygcBsVj1LqToP19WD9v5MDKW6ERinlOJdGBrD9n2BomsFq58zshJ1Kdrb5MthynDIDHsZpHaX2r4FF1vPWZdw6nY32akaTHFiHO2cD1liW7ugYKwMCkmKVYGbxqY5yTZEun8qMLgHhiW/98eMKcTjM2mLMmrcYrdsXdb5SdVDkTDEJ06S6nxTvMQ5Oe33QbntE5uIxOPpNZu94U/yW84pqK+NEH4Ty8KZL1bKUcpqcCPLxvzWtYRw+CLeQ+aYX+7ZXL/g5zI1SOkH+8RgxvxMO2+/SQGqHiqPdqF2+wlJdNt8oHMX400ccNHvFqkA7/M2UcYhBaMoz4fAND2Ec1f+5/+bOAbjy5sVoIuKVK7p4CUHdmhkfBmOY/ZwvfWNrF1Q==; 5:Zk9AHa1Sgz61xH4SEZ3XPcWRg07ab2mDjYi/0iytDqxlnTqjgy+Xlkg4AQ+sKP8hOyowp8M+0E4HU1lZYVgYKLrOf8jC4RZ4uCgZLlZ1zbLoJiGbccQdiqlbmQ1/OJcjRtGpzuiJ/xMFQt3hNvVbQA==; 24:umYcNMVHSH6typ+BcdA/BvWI4up+ypTyx59h+hbdU07G9EeIXRLPMhVXsUlG2HSRkIv8HoGR1QxD9hHRig2YLssq4417+ErF7LhiLBg//q8=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 7:Z2oYbmOJ5VJQTi4UJxdJnzlsDd3nH1wRb2dbDbAZUwPNCTjw/97Fdv3xyk3hpYBp8CLv2uYzS4xz6nq5ecWcK+p/tOyNaQoYYQmCbeITPDhB88x5mxnUHhgOv3+69yvIdOa/oWzWWAAzADLEy9CCWH99COeHkgOZYBcwHvBCzvo64DvDi7yZ5QbNT1egrwwyVSvnXHe9UGrYJVd8XDyEeQPIeJkAVy/MbufXHbNNwjbg7av2QP3ANsKOn2Fbj6fQiAxKIJL/VWz6tZNPDUjxaB2y3g1Ixiwz+f9a/cA4pyppGfHi1nVN2UxaHZa6A5YR2NiLJ2hG4NKepGgq2rtAdA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Mar 2017 16:48:38.2587 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1560
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g20_M4hGZI1qRPo3Ry3IHTW4LLA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 16:48:50 -0000

Why does this I-D make no mention of YANG 1.1, which has been around for
a while now (albeit not superseding YANG 1.0)?

Has the YANG module been validated against YANG 1.1?

Tom Petch


----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
Sent: Friday, March 17, 2017 4:23 PM


>
> The IESG has received a request from the Routing Area Working Group WG
> (rtgwg) to consider the following document:
> - 'Routing Key Chain YANG Data Model'
>   <draft-ietf-rtgwg-yang-key-chain-15.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 2017-04-07. 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 key chain YANG data model.  A key chain
>    is a list of elements each containing a key string, send lifetime,
>    accept lifetime, and algorithm (authentication or encryption).  By
>    properly overlapping the send and accept lifetimes of multiple key
>    chain elements, key strings and algorithms may be gracefully
updated.
>    By representing them in a YANG data model, key distribution can be
>    automated.  Key chains are commonly used for routing protocol
>    authentication and other applications.  In some applications, the
>    protocols do not use the key chain element key directly, but rather
a
>    key derivation function is used to derive a short-lived key from
the
>    key chain element key (e.g., the Master Keys used in the TCP
>    Authentication Option.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/
>
> IESG discussion can be tracked via
>
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>


From nobody Tue Mar 21 09:52:17 2017
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 46F93129C04; Tue, 21 Mar 2017 09:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 65RoKLSLE9Nd; Tue, 21 Mar 2017 09:52:07 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AAE8129C06; Tue, 21 Mar 2017 09:51:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490115106; x=1521651106; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=60YZ6R8AXRqUNtD1v8/K/pk4ClW+mDESFp+CYUyptS0=; b=DuEBxut/13X0qt0jXUUzGwvSiHbseULyu4tkvb/I9HkF6utFMoiqyJkb e4nXloOXkph8wvOgTwNOximRLj2e4Mbjw/cmT9xNGfORC948s5Z4rUEOx 77SkEzsLdwAUqeI7gTTruYhdRfxWPaQj8Bh6jqIROICJhcJf6Oa3aIBd7 w=;
X-IronPort-AV: E=Sophos;i="5.36,200,1486454400"; d="scan'208";a="271792141"
Received: from unknown (HELO Ironmsg04-L.qualcomm.com) ([10.53.140.111]) by wolverine01.qualcomm.com with ESMTP; 21 Mar 2017 09:51:45 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8474"; a="1313103308"
X-MGA-submission: =?us-ascii?q?MDHb44LJFXKNOubnsvcd/dTKGwNS1+NITaeTwi?= =?us-ascii?q?XIQo9TtH6TWVaFs9YDkY2TM5eodFtr51//hw7VsM5wMlaGAniKUI3EmE?= =?us-ascii?q?mI8TPilNHUX6Gvigo/6JQHvfZdsCLKpzQ68nZ0RlqwHaRzbcSb78J3jZ?= =?us-ascii?q?R5?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Mar 2017 09:51:45 -0700
Received: from [10.64.124.243] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 21 Mar 2017 09:51:44 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-sipcore-status-unwanted@ietf.org" <draft-ietf-sipcore-status-unwanted@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
Date: Tue, 21 Mar 2017 11:51:42 -0500
Message-ID: <8443007A-60F0-4AB6-80EC-DD20368D61EA@qti.qualcomm.com>
In-Reply-To: <BY1PR09MB0631F94D0B74E498ECCF3A4DEA3D0@BY1PR09MB0631.namprd09.prod.outlook.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com> <BY1PR09MB0631F94D0B74E498ECCF3A4DEA3D0@BY1PR09MB0631.namprd09.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01E.na.qualcomm.com (10.85.0.31) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-RBIto1Nm5wBDUA0lswozsZxFzc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 16:52:10 -0000

Just replying to the points in your message (trimming as I go along):

On 21 Mar 2017, at 11:17, Henning Schulzrinne wrote:

> My take of the discussion was that a simple mechanism that reflects 
> plausible and likely UI approaches was preferable to a more complex 
> mechanism.

First, there is nothing complex about adding a header that says, 
"Decline-Type: spam" to 603. It is extremely simple, accomplishes 
exactly the same result, reflects the one envisioned plausible and 
likely UI, and has the added advantage of extensibility.

> Nothing prevents adding information to the 'unwanted' status code in 
> the future, should there be a need. As you indicate, the Call-Info 
> labeling may well inform such an effort.

The problem there is that you then will have two different ways of 
expressing "spam", adding yet more ambiguity. It means that the 
implementer has to know whether they're talking to a 666 implementation 
that does or does not know about the additional parameter to understand 
what the behavior will be. We've constantly faced this problem in IMAP 
over the years and it's made for horrible implementations.

Better to do the simple thing first and not end up with two incompatible 
ways to do the same thing in the future.

> Yes, the idea was to model the (apparently near-universal) notions of 
> the email spam button.

Simply achievable with 603 and "Decline-Type: spam". The only additional 
complexity is to create the IANA registry for future decline types. I'm 
only suggesting this document defining the one right now.

> The goal was never to create a full-fledged API for rejecting classes 
> of calls or otherwise controlling the behavior of voice spam filters.

Nor am I proposing such an API. Sure, pieces of this (and Call-Info 
labeling) might be useful for such a thing later, but I have no interest 
in such a thing now.

> In practice, users will only be willing to spend a limited amount of 
> time on feedback for unwanted calls.

Again, the mechanism I propose does not add to that limited time. It 
functions, in that scenario, exactly like 666. The difference is only in 
extensibility (and avoids the potential pitfalls I mentioned earlier).

> Adding parameters to existing status codes can be done, but that seems 
> more a matter of design taste.

As I said quite clearly, it's not a design matter. Using a separate 
status code to mean "decline, with additional semantics" has side 
effects, because you already have a status code for decline. Please 
re-read my explanation.

> After all, we could then dispense with all specific codes and just use 
> 100, 200, 400, 500 and 600, each with headers attached.

No, that absolutely does not follow. A layered approach of status codes 
for broader semantic values and headers for specialized processing works 
incredibly well. The problem arises when you introduce a status code 
that does not give the basic processing engine enough information to go 
on.

What you want in this case is to have the default behavior be "decline", 
as per the status code, and then have some side processing to figure out 
whether to deposit information into a spam analysis engine, or hand it 
off to some other process that does different sorts of things, based on 
the additional semantic information in the header. That's a good 
division of labor.

> I don't see the problem with a new status code - we routinely add them 
> and the mechanism of handling unknown ones are quite clear.

Please see my earlier comments on this particular status code: It 
increases semantic ambiguity, it increases the possibility for data 
loss, and it limits future extensibility.

Again, it's not clear that you've fully understood and considered what I 
wrote.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Tue Mar 21 09:59:35 2017
Return-Path: <adam@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 C957D127201; Tue, 21 Mar 2017 09:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BTL0lAzEhr68; Tue, 21 Mar 2017 09:59:31 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09BB312708C; Tue, 21 Mar 2017 09:59:30 -0700 (PDT)
Received: from Orochi.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v2LGxTTL063091 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 21 Mar 2017 11:59:30 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Orochi.local
Subject: Re: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com>
Cc: draft-ietf-sipcore-status-unwanted@ietf.org, ben@nostrum.com, sipcore@ietf.org, sipcore-chairs@ietf.org
From: Adam Roach <adam@nostrum.com>
Message-ID: <534047ad-8971-88ec-3d16-254c766bbfa3@nostrum.com>
Date: Tue, 21 Mar 2017 11:59:23 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary="------------D0FB48B24F913B613ECBEA3B"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Gz5kpWyPVGIEb5S5G8pnXSTkgYo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 16:59:34 -0000

This is a multi-part message in MIME format.
--------------D0FB48B24F913B613ECBEA3B
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 3/21/17 10:49, Pete Resnick wrote:
>
> 1.
>
>     The 666 mechanism leaves the decision of what is meant by
>     "unwanted" to the provider, which will inevitably cause data loss
>     through the use of heuristics. Adding a header to the 603 response
>     is an extensible mechanism that could capture the single semantic
>     bit of 666 /and any future semantics that one wishes to add/,
>     without requiring the provider to guess. The provider gets
>     definitive information that it can act on.
>

The problem is that the semantics of 666 are backwards from the 
semantics of 603.

603 means "there is an issue with the disposition of the *called* party 
that prevents completing the call."

666 means "there is an issue with the disposition of the *calling* party 
that prevents completing the call."

You're proposing conflating the two semantics, which necessarily 
introduces more ambiguity, not less.

Carrier determination of how to handle these codes is, as with any 
nuisance communication mitigation, going to necessarily be based on 
heuristics to avoid accidental blacklisting, intentional blowback, and 
the inevitable gaming of the system by bad actors. You imply that the 
application of heuristics is an unwanted side effect of the system, when 
it in fact the primary goal.

In terms of being able to provide gradation between types of unwanted 
calls, the application of a header -- as you propose -- to provide such 
indication seems like a fine idea. I will point out one caveat and make 
one observation. The caveat is that it would be harmful to add this 
header in a way that reverses the sense of a response code, such as 
making 603 bear on the calling party rather than the called party; so 
such an indication would need to be on a new response code, such as the 
one currently proposed in draft-ietf-sipcore-status-unwanted. The 
observation is that this mechanism can be added to this new status at a 
later date, in a modular fashion and in a backwards compatible way. In 
other words: your proposed enhancement is *nice*, but it does not 
preclude publishing the mechanism currently described.

> 2.
>
>     The 666 mechanism limits the implementation of the mechanism to a
>     1-button choice and requires additional standardization work to
>     use a different UI. Clearly 666 was designed around something akin
>     to a "SPAM" button in the UI. But what if I want a field in my
>     address book that says, "Permanently block this particular caller"
>     (say, my ex-boyfriend or my annoying neighbor)? I don't want to
>     indicate that these are spam calls because I don't want my
>     provider applying heuristics to them. I want to send back a 603
>     with a header that says, "Block these whenever you see them, but
>     only for me." I can think of all sorts of other-than-one-button
>     UIs that someone might want to implement. 666 is tied to a
>     particular UI. 603 with a header is extensible.
>

That kind of persistent, hard-state user account configuration *really* 
isn't a reasonable kind of thing to do with a SIP status code (not least 
of all because you would need some mechanism for reviewing and managing 
such a list; and whatever that mechanism is could just as readily be 
used for adding entries). If you feel the need to pursue the somewhat 
related problem space of a network-assisted blocklist, we have a variety 
of tools we could bring to bear, such as XCAP. That's a separable 
problem, though, and I think that tangling it up with spam mitigation is 
a huge mistake.

I'll also point out that devices are perfectly capable of handling this 
feature locally without any assistance from the network, so I'm not sure 
how much value would be added by defining a network-hosted version of 
the service. The overarching point, though, is that a SIP response code 
is absolutely the wrong approach for doing so.

> 3.
>
>     The 666 mechanism will be treated as a 600 "Busy" error by
>     un-upgraded callers and/or providers. That might imply to some
>     implementations that they should try to re-dial (e.g., the
>     provider using the auto-redial feature) or to engage in other poor
>     behavior. 603 with no Retry-After header already has a semantic of
>     "The call was rejected and I'm not telling you when a good time to
>     call back is", so there is some hope that an un-upgraded caller is
>     more likely to do the right thing.
>

This is really reaching, and I think is based on a misperception of how 
SIP clients actually work when they receive 6xx responses. Taken to its 
logical conclusion, if we accept your assertion then we can't ever 
define a new 6xx-class SIP response code for fear that such codes "might 
imply to some implementations that they should try to re-dial (e.g., the 
provider using the auto-redial feature) or to engage in other poor 
behavior."


/a


--------------D0FB48B24F913B613ECBEA3B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 3/21/17 10:49, Pete Resnick wrote:<br>
    </div>
    <blockquote
      cite="mid:E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com"
      type="cite">
      <ol>
        <li value="1">
          <p dir="auto">The 666 mechanism leaves the decision of what is
            meant by "unwanted" to the provider, which will inevitably
            cause data loss through the use of heuristics. Adding a
            header to the 603 response is an extensible mechanism that
            could capture the single semantic bit of 666 <em>and any
              future semantics that one wishes to add</em>, without
            requiring the provider to guess. The provider gets
            definitive information that it can act on.</p>
        </li>
      </ol>
    </blockquote>
    <br>
    The problem is that the semantics of 666 are backwards from the
    semantics of 603.<br>
    <br>
    603 means "there is an issue with the disposition of the *called*
    party that prevents completing the call."<br>
    <br>
    666 means "there is an issue with the disposition of the *calling*
    party that prevents completing the call."<br>
    <br>
    You're proposing conflating the two semantics, which necessarily
    introduces more ambiguity, not less.<br>
    <br>
    Carrier determination of how to handle these codes is, as with any
    nuisance communication mitigation, going to necessarily be based on
    heuristics to avoid accidental blacklisting, intentional blowback,
    and the inevitable gaming of the system by bad actors. You imply
    that the application of heuristics is an unwanted side effect of the
    system, when it in fact the primary goal.<br>
    <br>
    In terms of being able to provide gradation between types of
    unwanted calls, the application of a header -- as you propose -- to
    provide such indication seems like a fine idea. I will point out one
    caveat and make one observation. The caveat is that it would be
    harmful to add this header in a way that reverses the sense of a
    response code, such as making 603 bear on the calling party rather
    than the called party; so such an indication would need to be on a
    new response code, such as the one currently proposed in
    draft-ietf-sipcore-status-unwanted. The observation is that this
    mechanism can be added to this new status at a later date, in a
    modular fashion and in a backwards compatible way. In other words:
    your proposed enhancement is *nice*, but it does not preclude
    publishing the mechanism currently described.<br>
    <br>
    <blockquote
      cite="mid:E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com"
      type="cite">
      <ol>
        <li value="2">
          <p dir="auto">The 666 mechanism limits the implementation of
            the mechanism to a 1-button choice and requires additional
            standardization work to use a different UI. Clearly 666 was
            designed around something akin to a "SPAM" button in the UI.
            But what if I want a field in my address book that says,
            "Permanently block this particular caller" (say, my
            ex-boyfriend or my annoying neighbor)? I don't want to
            indicate that these are spam calls because I don't want my
            provider applying heuristics to them. I want to send back a
            603 with a header that says, "Block these whenever you see
            them, but only for me." I can think of all sorts of
            other-than-one-button UIs that someone might want to
            implement. 666 is tied to a particular UI. 603 with a header
            is extensible.</p>
        </li>
      </ol>
    </blockquote>
    <br>
    That kind of persistent, hard-state user account configuration
    *really* isn't a reasonable kind of thing to do with a SIP status
    code (not least of all because you would need some mechanism for
    reviewing and managing such a list; and whatever that mechanism is
    could just as readily be used for adding entries). If you feel the
    need to pursue the somewhat related problem space of a
    network-assisted blocklist, we have a variety of tools we could
    bring to bear, such as XCAP. That's a separable problem, though, and
    I think that tangling it up with spam mitigation is a huge mistake.<br>
    <br>
    I'll also point out that devices are perfectly capable of handling
    this feature locally without any assistance from the network, so I'm
    not sure how much value would be added by defining a network-hosted
    version of the service. The overarching point, though, is that a SIP
    response code is absolutely the wrong approach for doing so.<br>
    <br>
    <blockquote
      cite="mid:E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com"
      type="cite">
      <ol>
        <li value="3">
          <p dir="auto">The 666 mechanism will be treated as a 600
            "Busy" error by un-upgraded callers and/or providers. That
            might imply to some implementations that they should try to
            re-dial (e.g., the provider using the auto-redial feature)
            or to engage in other poor behavior. 603 with no Retry-After
            header already has a semantic of "The call was rejected and
            I'm not telling you when a good time to call back is", so
            there is some hope that an un-upgraded caller is more likely
            to do the right thing.</p>
        </li>
      </ol>
    </blockquote>
    <p><br>
    </p>
    <p>This is really reaching, and I think is based on a misperception
      of how SIP clients actually work when they receive 6xx responses.
      Taken to its logical conclusion, if we accept your assertion then
      we can't ever define a new 6xx-class SIP response code for fear
      that such codes "might imply to some implementations that they
      should try to re-dial (e.g., the provider using the auto-redial
      feature) or to engage in other poor behavior."</p>
    <p><br>
    </p>
    <p>/a<br>
    </p>
  </body>
</html>

--------------D0FB48B24F913B613ECBEA3B--


From nobody Tue Mar 21 10:05:58 2017
Return-Path: <alan.b.johnston@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 589CF129BE8; Tue, 21 Mar 2017 10:05:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K7BVY5XW_2hY; Tue, 21 Mar 2017 10:05:53 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35009129BEE; Tue, 21 Mar 2017 10:05:52 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id l37so116142083wrc.1; Tue, 21 Mar 2017 10:05:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Ub7QC53Wt5L8CoDE2nbSKHCRs/uUl26anHfKfRX2dd4=; b=dyj10meKR/92v7Lgi9w/NnlzkoftL0bhfXyfpoGGuCTbLN8Lh1io7cZ3HlL3vwhDvO JquOoRRFsFSa6OYPut1UwNXp3tHsCKKWjZ2lWDk2hEt5s0T7Tt6wokeRWhffUj13tdv2 SCYk0FOGnfJjd7IpEBX/pcmdQ2Ca6PSBIfj0lgr1QJlCqDKC+Gt5Z/4EX6IqgkkeYNJA jm3S0YvbzQgwOhzps1w3AJmPAKHlgbKBrEEWpYALRJUM2gzUc/7PnTqcYUl0KCm9cxPc IxsmSIhY4SDQRF51n1p0nk5S3cBNaAJROlPA/T3JSKUbSz6FynOU2MePFDj40fHMbe2X taZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Ub7QC53Wt5L8CoDE2nbSKHCRs/uUl26anHfKfRX2dd4=; b=B4lqHxg2imYFWHXmaIL7t1W3nsxx8oJx/gKD02g06pP8fbC5qqSiwF8IjxitM0Rn9/ DF8cLQBnMdFWWBh9HN7sUEEj9N9UJTNmLcUzJQniT4XznqHoz/cxEIc0hcXBVIVAlGZW LJ9sUOmtrA7VNIJrMT5BkMsAdbwkyHfeSMJY9U/toFWBSIhtrxNppyuEOJFKOHspMIA/ McFDuEIftpHvpjFFF65QzjMhOYDt97mIPZguwSUJlaq4APwtsNr3XgWVvDxgbNXCyynh lcd+jBAm/79zB0LGBklLsykt4EQPQi2QootW8TpLcl8TlQHqMhlayqLbcOYvSB5nKtY5 W4iA==
X-Gm-Message-State: AFeK/H2dvkr43rHqbdwlGQ1C/5z2Kq8cQ8+9Br+SlwvqcikGeRaK+I/XdeW0iPHbKlCz7ClN1PtO4YyWtZbNZg==
X-Received: by 10.223.153.168 with SMTP id y37mr30756346wrb.193.1490115950608;  Tue, 21 Mar 2017 10:05:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.177.146 with HTTP; Tue, 21 Mar 2017 10:05:49 -0700 (PDT)
In-Reply-To: <8443007A-60F0-4AB6-80EC-DD20368D61EA@qti.qualcomm.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com> <BY1PR09MB0631F94D0B74E498ECCF3A4DEA3D0@BY1PR09MB0631.namprd09.prod.outlook.com> <8443007A-60F0-4AB6-80EC-DD20368D61EA@qti.qualcomm.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
Date: Tue, 21 Mar 2017 10:05:49 -0700
Message-ID: <CAKhHsXHDoDnO_NBOpMsyKxfY9-oKqnjE9z9SgvXnpmOTJPfDpQ@mail.gmail.com>
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>, "sipcore@ietf.org" <sipcore@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "draft-ietf-sipcore-status-unwanted@ietf.org" <draft-ietf-sipcore-status-unwanted@ietf.org>
Content-Type: multipart/alternative; boundary=f403045f546ee907b2054b40a767
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AjTWZqKN7ynfld8fkvtwo56XG_o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 17:05:56 -0000

--f403045f546ee907b2054b40a767
Content-Type: text/plain; charset=UTF-8

Pete,

Joining this conversation late - apologies if it has already been discussed.

If you are proposing using a SIP response code  603 and with a header field
Decline-Type: spam, the problem with this is that in SIP, failure responses
(non-2xx) are delivered hop-by-hop and not end-to-end.  This means that
although the first hop (proxy) will get the Decline-Type:spam header field,
any future hops will not.  Instead, they will just get the 603.

A different response code such as 666 will be conveyed end-to-end, so every
proxy and the calling UA will get the semantics.

- Alan -

On Tue, Mar 21, 2017 at 9:51 AM, Pete Resnick <presnick@qti.qualcomm.com>
wrote:

> Just replying to the points in your message (trimming as I go along):
>
> On 21 Mar 2017, at 11:17, Henning Schulzrinne wrote:
>
> My take of the discussion was that a simple mechanism that reflects
>> plausible and likely UI approaches was preferable to a more complex
>> mechanism.
>>
>
> First, there is nothing complex about adding a header that says,
> "Decline-Type: spam" to 603. It is extremely simple, accomplishes exactly
> the same result, reflects the one envisioned plausible and likely UI, and
> has the added advantage of extensibility.
>
> Nothing prevents adding information to the 'unwanted' status code in the
>> future, should there be a need. As you indicate, the Call-Info labeling may
>> well inform such an effort.
>>
>
> The problem there is that you then will have two different ways of
> expressing "spam", adding yet more ambiguity. It means that the implementer
> has to know whether they're talking to a 666 implementation that does or
> does not know about the additional parameter to understand what the
> behavior will be. We've constantly faced this problem in IMAP over the
> years and it's made for horrible implementations.
>
> Better to do the simple thing first and not end up with two incompatible
> ways to do the same thing in the future.
>
> Yes, the idea was to model the (apparently near-universal) notions of the
>> email spam button.
>>
>
> Simply achievable with 603 and "Decline-Type: spam". The only additional
> complexity is to create the IANA registry for future decline types. I'm
> only suggesting this document defining the one right now.
>
> The goal was never to create a full-fledged API for rejecting classes of
>> calls or otherwise controlling the behavior of voice spam filters.
>>
>
> Nor am I proposing such an API. Sure, pieces of this (and Call-Info
> labeling) might be useful for such a thing later, but I have no interest in
> such a thing now.
>
> In practice, users will only be willing to spend a limited amount of time
>> on feedback for unwanted calls.
>>
>
> Again, the mechanism I propose does not add to that limited time. It
> functions, in that scenario, exactly like 666. The difference is only in
> extensibility (and avoids the potential pitfalls I mentioned earlier).
>
> Adding parameters to existing status codes can be done, but that seems
>> more a matter of design taste.
>>
>
> As I said quite clearly, it's not a design matter. Using a separate status
> code to mean "decline, with additional semantics" has side effects, because
> you already have a status code for decline. Please re-read my explanation.
>
> After all, we could then dispense with all specific codes and just use
>> 100, 200, 400, 500 and 600, each with headers attached.
>>
>
> No, that absolutely does not follow. A layered approach of status codes
> for broader semantic values and headers for specialized processing works
> incredibly well. The problem arises when you introduce a status code that
> does not give the basic processing engine enough information to go on.
>
> What you want in this case is to have the default behavior be "decline",
> as per the status code, and then have some side processing to figure out
> whether to deposit information into a spam analysis engine, or hand it off
> to some other process that does different sorts of things, based on the
> additional semantic information in the header. That's a good division of
> labor.
>
> I don't see the problem with a new status code - we routinely add them and
>> the mechanism of handling unknown ones are quite clear.
>>
>
> Please see my earlier comments on this particular status code: It
> increases semantic ambiguity, it increases the possibility for data loss,
> and it limits future extensibility.
>
> Again, it's not clear that you've fully understood and considered what I
> wrote.
>
> pr
> --
> Pete Resnick <http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

--f403045f546ee907b2054b40a767
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Pete,<div><br></div><div>Joining this conversation late - =
apologies if it has already been discussed.</div><div><br></div><div>If you=
 are proposing using a SIP response code=C2=A0<span style=3D"font-size:12.8=
px">=C2=A0</span><span style=3D"font-size:12.8px">603 and with a header fie=
ld Decline-Type: spam, the problem with this is that in SIP, failure respon=
ses (non-2xx) are delivered hop-by-hop and not end-to-end.=C2=A0 This means=
 that although the first hop (proxy) will get the Decline-Type:spam header =
field, any future hops will not.=C2=A0 Instead, they will just get the 603.=
</span></div><div><span style=3D"font-size:12.8px"><br></span></div><div><s=
pan style=3D"font-size:12.8px">A different response code such as 666 will b=
e conveyed end-to-end, so every proxy and the calling UA will get the seman=
tics.</span></div><div><span style=3D"font-size:12.8px"><br></span></div><d=
iv><span style=3D"font-size:12.8px">- Alan -</span></div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Mar 21, 2017 at 9:5=
1 AM, Pete Resnick <span dir=3D"ltr">&lt;<a href=3D"mailto:presnick@qti.qua=
lcomm.com" target=3D"_blank">presnick@qti.qualcomm.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">Just replying to the points in your mes=
sage (trimming as I go along):<br>
<br>
On 21 Mar 2017, at 11:17, Henning Schulzrinne wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
My take of the discussion was that a simple mechanism that reflects plausib=
le and likely UI approaches was preferable to a more complex mechanism.<br>
</blockquote>
<br>
First, there is nothing complex about adding a header that says, &quot;Decl=
ine-Type: spam&quot; to 603. It is extremely simple, accomplishes exactly t=
he same result, reflects the one envisioned plausible and likely UI, and ha=
s the added advantage of extensibility.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Nothing prevents adding information to the &#39;unwanted&#39; status code i=
n the future, should there be a need. As you indicate, the Call-Info labeli=
ng may well inform such an effort.<br>
</blockquote>
<br>
The problem there is that you then will have two different ways of expressi=
ng &quot;spam&quot;, adding yet more ambiguity. It means that the implement=
er has to know whether they&#39;re talking to a 666 implementation that doe=
s or does not know about the additional parameter to understand what the be=
havior will be. We&#39;ve constantly faced this problem in IMAP over the ye=
ars and it&#39;s made for horrible implementations.<br>
<br>
Better to do the simple thing first and not end up with two incompatible wa=
ys to do the same thing in the future.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Yes, the idea was to model the (apparently near-universal) notions of the e=
mail spam button.<br>
</blockquote>
<br>
Simply achievable with 603 and &quot;Decline-Type: spam&quot;. The only add=
itional complexity is to create the IANA registry for future decline types.=
 I&#39;m only suggesting this document defining the one right now.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The goal was never to create a full-fledged API for rejecting classes of ca=
lls or otherwise controlling the behavior of voice spam filters.<br>
</blockquote>
<br>
Nor am I proposing such an API. Sure, pieces of this (and Call-Info labelin=
g) might be useful for such a thing later, but I have no interest in such a=
 thing now.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In practice, users will only be willing to spend a limited amount of time o=
n feedback for unwanted calls.<br>
</blockquote>
<br>
Again, the mechanism I propose does not add to that limited time. It functi=
ons, in that scenario, exactly like 666. The difference is only in extensib=
ility (and avoids the potential pitfalls I mentioned earlier).<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Adding parameters to existing status codes can be done, but that seems more=
 a matter of design taste.<br>
</blockquote>
<br>
As I said quite clearly, it&#39;s not a design matter. Using a separate sta=
tus code to mean &quot;decline, with additional semantics&quot; has side ef=
fects, because you already have a status code for decline. Please re-read m=
y explanation.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
After all, we could then dispense with all specific codes and just use 100,=
 200, 400, 500 and 600, each with headers attached.<br>
</blockquote>
<br>
No, that absolutely does not follow. A layered approach of status codes for=
 broader semantic values and headers for specialized processing works incre=
dibly well. The problem arises when you introduce a status code that does n=
ot give the basic processing engine enough information to go on.<br>
<br>
What you want in this case is to have the default behavior be &quot;decline=
&quot;, as per the status code, and then have some side processing to figur=
e out whether to deposit information into a spam analysis engine, or hand i=
t off to some other process that does different sorts of things, based on t=
he additional semantic information in the header. That&#39;s a good divisio=
n of labor.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I don&#39;t see the problem with a new status code - we routinely add them =
and the mechanism of handling unknown ones are quite clear.<br>
</blockquote>
<br>
Please see my earlier comments on this particular status code: It increases=
 semantic ambiguity, it increases the possibility for data loss, and it lim=
its future extensibility.<br>
<br>
Again, it&#39;s not clear that you&#39;ve fully understood and considered w=
hat I wrote.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
pr<br>
-- <br>
Pete Resnick &lt;<a href=3D"http://www.qualcomm.com/~presnick/" rel=3D"nore=
ferrer" target=3D"_blank">http://www.qualcomm.com/~pres<wbr>nick/</a>&gt;<b=
r>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><br>
<br>
______________________________<wbr>_________________<br>
sipcore mailing list<br>
<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/sipcore</a><=
br>
</font></span></blockquote></div><br></div>

--f403045f546ee907b2054b40a767--


From nobody Tue Mar 21 10:14:22 2017
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 26F99129B77; Tue, 21 Mar 2017 10:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WRz5tiLLfDu6; Tue, 21 Mar 2017 10:14:13 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3963E127A91; Tue, 21 Mar 2017 10:14:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490116453; x=1521652453; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=VkTHXixnoPd0BsX4WO0cK84qBGMN3fNK0KDGUFbicPY=; b=ugCODPSTJVAekgVA2uJE25RPYdgMnlpfSdZbtzQXbB/v+pEQbVuDCHQr S5Q93kQXb0KzTsxnRna35EKu2nppbbeG+zeEMq06XCvgi+mceFb3Ocr8R 80Tr+DBQtHA1W5fBw+oiC2SOVsPj8KY7ssLl1liHAsgRdTtnfblf7fbf3 Y=;
X-IronPort-AV: E=Sophos;i="5.36,200,1486454400"; d="scan'208";a="271794905"
Received: from unknown (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by wolverine01.qualcomm.com with ESMTP; 21 Mar 2017 10:14:12 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8474"; a="1331864765"
X-MGA-submission: =?us-ascii?q?MDH8TuiKXuK3ojrZjclgI+0ag5l4C+ltcldzol?= =?us-ascii?q?2ICO/Tq2i+f/a7OUfktp/OB7WzdSjIhE+cYBfK35gyr4vxNuHl3jKSaE?= =?us-ascii?q?KWhben1C5D4E5JCfa4ydj6UDuThpzD5+3AMrwYNNzmKZRURlX90rLfsm?= =?us-ascii?q?70?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Mar 2017 10:14:12 -0700
Received: from [10.64.124.243] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 21 Mar 2017 10:14:11 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Adam Roach <adam@nostrum.com>
CC: <ietf@ietf.org>, <draft-ietf-sipcore-status-unwanted@ietf.org>, <ben@nostrum.com>, <sipcore@ietf.org>, <sipcore-chairs@ietf.org>
Subject: Re: Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
Date: Tue, 21 Mar 2017 12:14:10 -0500
Message-ID: <13DC441F-FFC0-4E00-8CB4-4DBBF8423420@qti.qualcomm.com>
In-Reply-To: <534047ad-8971-88ec-3d16-254c766bbfa3@nostrum.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com> <534047ad-8971-88ec-3d16-254c766bbfa3@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01G.na.qualcomm.com (10.85.0.33) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X7U1H9OFwL4nSZOb72RUF3a8ZpA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 17:14:15 -0000

Just on a couple of small points:

On 21 Mar 2017, at 11:59, Adam Roach wrote:

> The problem is that the semantics of 666 are backwards from the 
> semantics of 603.
>
> 603 means "there is an issue with the disposition of the *called* 
> party that prevents completing the call."

That's not how 603 is described in 3261. It can be used to express that 
"the user explicitly does not wish to ... participate." Whether that's 
based on being in the shower or not liking the number in the caller id 
or something else, it expresses the called party's decision not to take 
the call.

> 666 means "there is an issue with the disposition of the *calling* 
> party that prevents completing the call."

That's not how the mechanism is described in this document. It is not 
that you send back 666 when the system determines something about the 
calling party; you send back 666 when the called party says something 
(in this case "SPAM!") that indicates that the called party declined the 
call.

I disagree that the semantics are different.

> ...I think is based on a misperception of how SIP clients actually 
> work when they receive 6xx responses.

I think this is a fair criticism insofar as I agree that either 666 or a 
header on 603 will work equally in today's usage scenarios. My only 
response is that I have rosy glasses looking to future advances that 
might make us regret having painted ourselves into a corner.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Tue Mar 21 10:43:06 2017
Return-Path: <tasveren@sonusnet.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 579C6129BDB for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 10:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=sonusnetworks.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2R_UPhyb2HKq for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 10:43:02 -0700 (PDT)
Received: from us-smtp-delivery-126.mimecast.com (us-smtp-delivery-126.mimecast.com [63.128.21.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4FB9129BF9 for <ietf@ietf.org>; Tue, 21 Mar 2017 10:43:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SonusNetworks.onmicrosoft.com; s=selector1-sonusnet-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LRHDBykAdGHU7XPnVHFVHUDeLM5cInBQ1P5xb1h4wp0=; b=vP0x96G9an8yzbohmhYViJQ6+0YYC1Vu+4XMdxwbNptxjyRd6iTbxAzNbfl21hNoS6cQ/OdgoUCTz87n0947mWLpjl06SgNRDtgGkzWZUSrEjHkMfxmMHxTSK3WhYbJuH4ZObGKepbAC4EHgRn9M3/Jl3C/OO7maCcENJE72P5k=
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02lp0087.outbound.protection.outlook.com [207.46.163.87]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-154-tcSZ-m-fP0qe7YYRJUmlRA-1; Tue, 21 Mar 2017 13:41:16 -0400
Received: from CY1PR03MB2348.namprd03.prod.outlook.com (10.166.207.147) by CY1PR03MB2346.namprd03.prod.outlook.com (10.166.207.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.12; Tue, 21 Mar 2017 17:41:14 +0000
Received: from CY1PR03MB2348.namprd03.prod.outlook.com ([10.166.207.147]) by CY1PR03MB2348.namprd03.prod.outlook.com ([10.166.207.147]) with mapi id 15.01.0947.020; Tue, 21 Mar 2017 17:41:14 +0000
From: "Asveren, Tolga" <tasveren@sonusnet.com>
To: Adam Roach <adam@nostrum.com>, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "ben@nostrum.com" <ben@nostrum.com>, "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>, "draft-ietf-sipcore-status-unwanted@ietf.org" <draft-ietf-sipcore-status-unwanted@ietf.org>
Subject: RE: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
Thread-Topic: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
Thread-Index: AQHSl6JN/iwWLY4Mt0+M1X82mOsOtaGfhkwAgAATaoCAAAs0QA==
Date: Tue, 21 Mar 2017 17:41:14 +0000
Message-ID: <CY1PR03MB23484A2E5BA8F065A090761CB23D0@CY1PR03MB2348.namprd03.prod.outlook.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com> <534047ad-8971-88ec-3d16-254c766bbfa3@nostrum.com>
In-Reply-To: <534047ad-8971-88ec-3d16-254c766bbfa3@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [73.29.18.75]
x-ms-office365-filtering-correlation-id: 511e81d9-9378-4578-fa84-08d4708178c9
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075); SRVR:CY1PR03MB2346; 
x-microsoft-exchange-diagnostics: 1; CY1PR03MB2346; 7:NjSJbCj3RvSLpZXgVp6nvO8ICOSQheC0UvllWEI+4dur4wji+hy8OZcS01re1JHqSu63jgUu8lVYl9m8JDshU1jmBOg9eDE/YLw6JDQzKTmwEsSKPqoTzHs11gjc2OrEuWlkzZzODZUaawkas/kXR7aXKta9TIBcTu1S39ZOOQP2uxne/uo80NeSsfgZOFWqO24iGxLjJxaf1iuEc/ErmFwd5bHo1lSW/z5hz8SuIKY0gERrnC8h69hqTTyN3hYIQRsGJrL/5o+u0BvluWYw5KdkOvnZEd0bYB62n2e0ybHsCw+oM+BVPvSmh9TFRijsZaovNntMU19DegyDyOaeLw==; 20:Lh0xpkzQtWd6g5Gi/Ln/HoFRDYKitSpmGy4Xg9+Oo5gSA86C0Qw86LdPH9fVAmQyE9Nf130Hp9XlvhKt0pDGr2d6BmhLDCfmllMRVYhZhOWrmGqWlMqT/Wf69yZpcDEzUF0ZtdFigT7nQqYrD12RGpjZNqy1QRzlOOecZEISwOc=
x-microsoft-antispam-prvs: <CY1PR03MB23466303F5676D9E356BE996B23D0@CY1PR03MB2346.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123555025)(20161123564025)(20161123562025)(20161123560025)(20161123558025)(6072148); SRVR:CY1PR03MB2346; BCL:0; PCL:0; RULEID:; SRVR:CY1PR03MB2346; 
x-forefront-prvs: 02530BD3AA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39450400003)(377454003)(24454002)(51444003)(81166006)(76176999)(74316002)(7736002)(5660300001)(9686003)(55016002)(33656002)(8936002)(6436002)(25786009)(2900100001)(8676002)(2906002)(2950100002)(3660700001)(54896002)(86362001)(54356999)(99286003)(6246003)(6306002)(50986999)(3280700002)(7696004)(66066001)(229853002)(4326008)(54906002)(6116002)(102836003)(77096006)(189998001)(38730400002)(2501003)(122556002)(230783001)(53546009)(53936002)(790700001)(6506006)(3846002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR03MB2346; H:CY1PR03MB2348.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: sonusnet.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Mar 2017 17:41:14.2824 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR03MB2346
X-MC-Unique: tcSZ-m-fP0qe7YYRJUmlRA-1
Content-Type: multipart/alternative; boundary="_000_CY1PR03MB23484A2E5BA8F065A090761CB23D0CY1PR03MB2348namp_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EMr7I6-JXb7ac-lc8Uv_M4SEyaA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 17:43:04 -0000

--_000_CY1PR03MB23484A2E5BA8F065A090761CB23D0CY1PR03MB2348namp_
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

RldJVyAoYW5kIGNvbnNpZGVyaW5nIHRoYXQgd2UgbWF5IGVuZCB1cCB3aXRoIGEg4oCccm91Z2gg
Y29uc2Vuc3Vz4oCdKSwgSSBhZ3JlZSB3aXRoIEFkYW3igJlzIGFuYWx5c2lzIGJlbG93Lg0KDQpT
bywgb3ZlcmFsbCBJIGRvIG5vdCB0aGluayBhbnkgY2hhbmdlcyBhcmUgbmVlZGVkIGluIHRoZSBk
cmFmdCBhbmQgaXQgY2FuIHByb2NlZWQgdG8gYmVjb21lIGEgUkZDLg0KDQpUaGFua3MsDQpUb2xn
YQ0KDQpGcm9tOiBzaXBjb3JlIFttYWlsdG86c2lwY29yZS1ib3VuY2VzQGlldGYub3JnXSBPbiBC
ZWhhbGYgT2YgQWRhbSBSb2FjaA0KU2VudDogVHVlc2RheSwgTWFyY2ggMjEsIDIwMTcgMTI6NTkg
UE0NClRvOiBQZXRlIFJlc25pY2sgPHByZXNuaWNrQHF0aS5xdWFsY29tbS5jb20+OyBpZXRmQGll
dGYub3JnDQpDYzogYmVuQG5vc3RydW0uY29tOyBzaXBjb3JlLWNoYWlyc0BpZXRmLm9yZzsgc2lw
Y29yZUBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1zaXBjb3JlLXN0YXR1cy11bndhbnRlZEBpZXRmLm9y
Zw0KU3ViamVjdDogUmU6IFtzaXBjb3JlXSBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLXNpcGNvcmUt
c3RhdHVzLXVud2FudGVkLTA0LnR4dD4gKEEgU0lQIFJlc3BvbnNlIENvZGUgZm9yIFVud2FudGVk
IENhbGxzKSB0byBQcm9wb3NlZCBTdGFuZGFyZA0KDQpPbiAzLzIxLzE3IDEwOjQ5LCBQZXRlIFJl
c25pY2sgd3JvdGU6DQoNCiAgMS4gIFRoZSA2NjYgbWVjaGFuaXNtIGxlYXZlcyB0aGUgZGVjaXNp
b24gb2Ygd2hhdCBpcyBtZWFudCBieSAidW53YW50ZWQiIHRvIHRoZSBwcm92aWRlciwgd2hpY2gg
d2lsbCBpbmV2aXRhYmx5IGNhdXNlIGRhdGEgbG9zcyB0aHJvdWdoIHRoZSB1c2Ugb2YgaGV1cmlz
dGljcy4gQWRkaW5nIGEgaGVhZGVyIHRvIHRoZSA2MDMgcmVzcG9uc2UgaXMgYW4gZXh0ZW5zaWJs
ZSBtZWNoYW5pc20gdGhhdCBjb3VsZCBjYXB0dXJlIHRoZSBzaW5nbGUgc2VtYW50aWMgYml0IG9m
IDY2NiBhbmQgYW55IGZ1dHVyZSBzZW1hbnRpY3MgdGhhdCBvbmUgd2lzaGVzIHRvIGFkZCwgd2l0
aG91dCByZXF1aXJpbmcgdGhlIHByb3ZpZGVyIHRvIGd1ZXNzLiBUaGUgcHJvdmlkZXIgZ2V0cyBk
ZWZpbml0aXZlIGluZm9ybWF0aW9uIHRoYXQgaXQgY2FuIGFjdCBvbi4NCg0KVGhlIHByb2JsZW0g
aXMgdGhhdCB0aGUgc2VtYW50aWNzIG9mIDY2NiBhcmUgYmFja3dhcmRzIGZyb20gdGhlIHNlbWFu
dGljcyBvZiA2MDMuDQoNCjYwMyBtZWFucyAidGhlcmUgaXMgYW4gaXNzdWUgd2l0aCB0aGUgZGlz
cG9zaXRpb24gb2YgdGhlICpjYWxsZWQqIHBhcnR5IHRoYXQgcHJldmVudHMgY29tcGxldGluZyB0
aGUgY2FsbC4iDQoNCjY2NiBtZWFucyAidGhlcmUgaXMgYW4gaXNzdWUgd2l0aCB0aGUgZGlzcG9z
aXRpb24gb2YgdGhlICpjYWxsaW5nKiBwYXJ0eSB0aGF0IHByZXZlbnRzIGNvbXBsZXRpbmcgdGhl
IGNhbGwuIg0KDQpZb3UncmUgcHJvcG9zaW5nIGNvbmZsYXRpbmcgdGhlIHR3byBzZW1hbnRpY3Ms
IHdoaWNoIG5lY2Vzc2FyaWx5IGludHJvZHVjZXMgbW9yZSBhbWJpZ3VpdHksIG5vdCBsZXNzLg0K
DQpDYXJyaWVyIGRldGVybWluYXRpb24gb2YgaG93IHRvIGhhbmRsZSB0aGVzZSBjb2RlcyBpcywg
YXMgd2l0aCBhbnkgbnVpc2FuY2UgY29tbXVuaWNhdGlvbiBtaXRpZ2F0aW9uLCBnb2luZyB0byBu
ZWNlc3NhcmlseSBiZSBiYXNlZCBvbiBoZXVyaXN0aWNzIHRvIGF2b2lkIGFjY2lkZW50YWwgYmxh
Y2tsaXN0aW5nLCBpbnRlbnRpb25hbCBibG93YmFjaywgYW5kIHRoZSBpbmV2aXRhYmxlIGdhbWlu
ZyBvZiB0aGUgc3lzdGVtIGJ5IGJhZCBhY3RvcnMuIFlvdSBpbXBseSB0aGF0IHRoZSBhcHBsaWNh
dGlvbiBvZiBoZXVyaXN0aWNzIGlzIGFuIHVud2FudGVkIHNpZGUgZWZmZWN0IG9mIHRoZSBzeXN0
ZW0sIHdoZW4gaXQgaW4gZmFjdCB0aGUgcHJpbWFyeSBnb2FsLg0KDQpJbiB0ZXJtcyBvZiBiZWlu
ZyBhYmxlIHRvIHByb3ZpZGUgZ3JhZGF0aW9uIGJldHdlZW4gdHlwZXMgb2YgdW53YW50ZWQgY2Fs
bHMsIHRoZSBhcHBsaWNhdGlvbiBvZiBhIGhlYWRlciAtLSBhcyB5b3UgcHJvcG9zZSAtLSB0byBw
cm92aWRlIHN1Y2ggaW5kaWNhdGlvbiBzZWVtcyBsaWtlIGEgZmluZSBpZGVhLiBJIHdpbGwgcG9p
bnQgb3V0IG9uZSBjYXZlYXQgYW5kIG1ha2Ugb25lIG9ic2VydmF0aW9uLiBUaGUgY2F2ZWF0IGlz
IHRoYXQgaXQgd291bGQgYmUgaGFybWZ1bCB0byBhZGQgdGhpcyBoZWFkZXIgaW4gYSB3YXkgdGhh
dCByZXZlcnNlcyB0aGUgc2Vuc2Ugb2YgYSByZXNwb25zZSBjb2RlLCBzdWNoIGFzIG1ha2luZyA2
MDMgYmVhciBvbiB0aGUgY2FsbGluZyBwYXJ0eSByYXRoZXIgdGhhbiB0aGUgY2FsbGVkIHBhcnR5
OyBzbyBzdWNoIGFuIGluZGljYXRpb24gd291bGQgbmVlZCB0byBiZSBvbiBhIG5ldyByZXNwb25z
ZSBjb2RlLCBzdWNoIGFzIHRoZSBvbmUgY3VycmVudGx5IHByb3Bvc2VkIGluIGRyYWZ0LWlldGYt
c2lwY29yZS1zdGF0dXMtdW53YW50ZWQuIFRoZSBvYnNlcnZhdGlvbiBpcyB0aGF0IHRoaXMgbWVj
aGFuaXNtIGNhbiBiZSBhZGRlZCB0byB0aGlzIG5ldyBzdGF0dXMgYXQgYSBsYXRlciBkYXRlLCBp
biBhIG1vZHVsYXIgZmFzaGlvbiBhbmQgaW4gYSBiYWNrd2FyZHMgY29tcGF0aWJsZSB3YXkuIElu
IG90aGVyIHdvcmRzOiB5b3VyIHByb3Bvc2VkIGVuaGFuY2VtZW50IGlzICpuaWNlKiwgYnV0IGl0
IGRvZXMgbm90IHByZWNsdWRlIHB1Ymxpc2hpbmcgdGhlIG1lY2hhbmlzbSBjdXJyZW50bHkgZGVz
Y3JpYmVkLg0KDQoNCg0KICAxLiAgVGhlIDY2NiBtZWNoYW5pc20gbGltaXRzIHRoZSBpbXBsZW1l
bnRhdGlvbiBvZiB0aGUgbWVjaGFuaXNtIHRvIGEgMS1idXR0b24gY2hvaWNlIGFuZCByZXF1aXJl
cyBhZGRpdGlvbmFsIHN0YW5kYXJkaXphdGlvbiB3b3JrIHRvIHVzZSBhIGRpZmZlcmVudCBVSS4g
Q2xlYXJseSA2NjYgd2FzIGRlc2lnbmVkIGFyb3VuZCBzb21ldGhpbmcgYWtpbiB0byBhICJTUEFN
IiBidXR0b24gaW4gdGhlIFVJLiBCdXQgd2hhdCBpZiBJIHdhbnQgYSBmaWVsZCBpbiBteSBhZGRy
ZXNzIGJvb2sgdGhhdCBzYXlzLCAiUGVybWFuZW50bHkgYmxvY2sgdGhpcyBwYXJ0aWN1bGFyIGNh
bGxlciIgKHNheSwgbXkgZXgtYm95ZnJpZW5kIG9yIG15IGFubm95aW5nIG5laWdoYm9yKT8gSSBk
b24ndCB3YW50IHRvIGluZGljYXRlIHRoYXQgdGhlc2UgYXJlIHNwYW0gY2FsbHMgYmVjYXVzZSBJ
IGRvbid0IHdhbnQgbXkgcHJvdmlkZXIgYXBwbHlpbmcgaGV1cmlzdGljcyB0byB0aGVtLiBJIHdh
bnQgdG8gc2VuZCBiYWNrIGEgNjAzIHdpdGggYSBoZWFkZXIgdGhhdCBzYXlzLCAiQmxvY2sgdGhl
c2Ugd2hlbmV2ZXIgeW91IHNlZSB0aGVtLCBidXQgb25seSBmb3IgbWUuIiBJIGNhbiB0aGluayBv
ZiBhbGwgc29ydHMgb2Ygb3RoZXItdGhhbi1vbmUtYnV0dG9uIFVJcyB0aGF0IHNvbWVvbmUgbWln
aHQgd2FudCB0byBpbXBsZW1lbnQuIDY2NiBpcyB0aWVkIHRvIGEgcGFydGljdWxhciBVSS4gNjAz
IHdpdGggYSBoZWFkZXIgaXMgZXh0ZW5zaWJsZS4NCg0KVGhhdCBraW5kIG9mIHBlcnNpc3RlbnQs
IGhhcmQtc3RhdGUgdXNlciBhY2NvdW50IGNvbmZpZ3VyYXRpb24gKnJlYWxseSogaXNuJ3QgYSBy
ZWFzb25hYmxlIGtpbmQgb2YgdGhpbmcgdG8gZG8gd2l0aCBhIFNJUCBzdGF0dXMgY29kZSAobm90
IGxlYXN0IG9mIGFsbCBiZWNhdXNlIHlvdSB3b3VsZCBuZWVkIHNvbWUgbWVjaGFuaXNtIGZvciBy
ZXZpZXdpbmcgYW5kIG1hbmFnaW5nIHN1Y2ggYSBsaXN0OyBhbmQgd2hhdGV2ZXIgdGhhdCBtZWNo
YW5pc20gaXMgY291bGQganVzdCBhcyByZWFkaWx5IGJlIHVzZWQgZm9yIGFkZGluZyBlbnRyaWVz
KS4gSWYgeW91IGZlZWwgdGhlIG5lZWQgdG8gcHVyc3VlIHRoZSBzb21ld2hhdCByZWxhdGVkIHBy
b2JsZW0gc3BhY2Ugb2YgYSBuZXR3b3JrLWFzc2lzdGVkIGJsb2NrbGlzdCwgd2UgaGF2ZSBhIHZh
cmlldHkgb2YgdG9vbHMgd2UgY291bGQgYnJpbmcgdG8gYmVhciwgc3VjaCBhcyBYQ0FQLiBUaGF0
J3MgYSBzZXBhcmFibGUgcHJvYmxlbSwgdGhvdWdoLCBhbmQgSSB0aGluayB0aGF0IHRhbmdsaW5n
IGl0IHVwIHdpdGggc3BhbSBtaXRpZ2F0aW9uIGlzIGEgaHVnZSBtaXN0YWtlLg0KDQpJJ2xsIGFs
c28gcG9pbnQgb3V0IHRoYXQgZGV2aWNlcyBhcmUgcGVyZmVjdGx5IGNhcGFibGUgb2YgaGFuZGxp
bmcgdGhpcyBmZWF0dXJlIGxvY2FsbHkgd2l0aG91dCBhbnkgYXNzaXN0YW5jZSBmcm9tIHRoZSBu
ZXR3b3JrLCBzbyBJJ20gbm90IHN1cmUgaG93IG11Y2ggdmFsdWUgd291bGQgYmUgYWRkZWQgYnkg
ZGVmaW5pbmcgYSBuZXR3b3JrLWhvc3RlZCB2ZXJzaW9uIG9mIHRoZSBzZXJ2aWNlLiBUaGUgb3Zl
cmFyY2hpbmcgcG9pbnQsIHRob3VnaCwgaXMgdGhhdCBhIFNJUCByZXNwb25zZSBjb2RlIGlzIGFi
c29sdXRlbHkgdGhlIHdyb25nIGFwcHJvYWNoIGZvciBkb2luZyBzby4NCg0KDQoNCiAgMS4gIFRo
ZSA2NjYgbWVjaGFuaXNtIHdpbGwgYmUgdHJlYXRlZCBhcyBhIDYwMCAiQnVzeSIgZXJyb3IgYnkg
dW4tdXBncmFkZWQgY2FsbGVycyBhbmQvb3IgcHJvdmlkZXJzLiBUaGF0IG1pZ2h0IGltcGx5IHRv
IHNvbWUgaW1wbGVtZW50YXRpb25zIHRoYXQgdGhleSBzaG91bGQgdHJ5IHRvIHJlLWRpYWwgKGUu
Zy4sIHRoZSBwcm92aWRlciB1c2luZyB0aGUgYXV0by1yZWRpYWwgZmVhdHVyZSkgb3IgdG8gZW5n
YWdlIGluIG90aGVyIHBvb3IgYmVoYXZpb3IuIDYwMyB3aXRoIG5vIFJldHJ5LUFmdGVyIGhlYWRl
ciBhbHJlYWR5IGhhcyBhIHNlbWFudGljIG9mICJUaGUgY2FsbCB3YXMgcmVqZWN0ZWQgYW5kIEkn
bSBub3QgdGVsbGluZyB5b3Ugd2hlbiBhIGdvb2QgdGltZSB0byBjYWxsIGJhY2sgaXMiLCBzbyB0
aGVyZSBpcyBzb21lIGhvcGUgdGhhdCBhbiB1bi11cGdyYWRlZCBjYWxsZXIgaXMgbW9yZSBsaWtl
bHkgdG8gZG8gdGhlIHJpZ2h0IHRoaW5nLg0KDQoNCg0KVGhpcyBpcyByZWFsbHkgcmVhY2hpbmcs
IGFuZCBJIHRoaW5rIGlzIGJhc2VkIG9uIGEgbWlzcGVyY2VwdGlvbiBvZiBob3cgU0lQIGNsaWVu
dHMgYWN0dWFsbHkgd29yayB3aGVuIHRoZXkgcmVjZWl2ZSA2eHggcmVzcG9uc2VzLiBUYWtlbiB0
byBpdHMgbG9naWNhbCBjb25jbHVzaW9uLCBpZiB3ZSBhY2NlcHQgeW91ciBhc3NlcnRpb24gdGhl
biB3ZSBjYW4ndCBldmVyIGRlZmluZSBhIG5ldyA2eHgtY2xhc3MgU0lQIHJlc3BvbnNlIGNvZGUg
Zm9yIGZlYXIgdGhhdCBzdWNoIGNvZGVzICJtaWdodCBpbXBseSB0byBzb21lIGltcGxlbWVudGF0
aW9ucyB0aGF0IHRoZXkgc2hvdWxkIHRyeSB0byByZS1kaWFsIChlLmcuLCB0aGUgcHJvdmlkZXIg
dXNpbmcgdGhlIGF1dG8tcmVkaWFsIGZlYXR1cmUpIG9yIHRvIGVuZ2FnZSBpbiBvdGhlciBwb29y
IGJlaGF2aW9yLiINCg0KDQoNCi9hDQo=
--_000_CY1PR03MB23484A2E5BA8F065A090761CB23D0CY1PR03MB2348namp_
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjsN
Cgljb2xvcjpibGFjazt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgljb2xvcjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7
fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgljb2xvcjojOTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0K
cC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28tc3R5bGUt
bmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0
OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjsN
Cgljb2xvcjpibGFjazt9DQpzcGFuLkVtYWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpwZXJz
b25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3
aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5
Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4g
MTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rp
b24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0
IGwwDQoJe21zby1saXN0LWlkOjEyMDgwMzg3MzsNCgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6NzE2
MTg4NTAwO30NCkBsaXN0IGwxDQoJe21zby1saXN0LWlkOjkwNzExMjE0MDsNCgltc28tbGlzdC10
ZW1wbGF0ZS1pZHM6LTcxNDMyODE2NDt9DQpAbGlzdCBsMg0KCXttc28tbGlzdC1pZDoxNzc5MjU0
ODIxOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczoxNDM3ODcwOTk2O30NCkBsaXN0IGwyOmxldmVs
MSBsZm80DQoJe21zby1sZXZlbC1zdGFydC1hdDoyO30NCkBsaXN0IGwxOmxldmVsMSBsZm82DQoJ
e21zby1sZXZlbC1zdGFydC1hdDozO30NCm9sDQoJe21hcmdpbi1ib3R0b206MGluO30NCnVsDQoJ
e21hcmdpbi1ib3R0b206MGluO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+
PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4
dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxh
eW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGJnY29sb3I9IndoaXRlIiBs
YW5nPSJFTi1VUyIgbGluaz0iIzA1NjNDMSIgdmxpbms9IiM5NTRGNzIiPg0KPGRpdiBjbGFzcz0i
V29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjp3aW5kb3d0ZXh0Ij5GV0lXIChhbmQgY29uc2lkZXJpbmcgdGhhdCB3ZSBtYXkgZW5kIHVwIHdp
dGggYSDigJxyb3VnaCBjb25zZW5zdXPigJ0pLCBJIGFncmVlIHdpdGggQWRhbeKAmXMgYW5hbHlz
aXMgYmVsb3cuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOndpbmRvd3RleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjp3aW5kb3d0ZXh0
Ij5Tbywgb3ZlcmFsbCBJIGRvIG5vdCB0aGluayBhbnkgY2hhbmdlcyBhcmUgbmVlZGVkIGluIHRo
ZSBkcmFmdCBhbmQgaXQgY2FuIHByb2NlZWQgdG8gYmVjb21lIGEgUkZDLjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjp3aW5k
b3d0ZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6d2luZG93dGV4dCI+VGhhbmtzLDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjp3aW5k
b3d0ZXh0Ij5Ub2xnYTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjp3aW5kb3d0ZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAj
RTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOndpbmRvd3RleHQiPkZyb206PC9zcGFuPjwv
Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6d2luZG93dGV4dCI+IHNpcGNvcmUgW21haWx0bzpzaXBj
b3JlLWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPkFkYW0gUm9hY2g8YnI+
DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgTWFyY2ggMjEsIDIwMTcgMTI6NTkgUE08YnI+DQo8Yj5U
bzo8L2I+IFBldGUgUmVzbmljayAmbHQ7cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbSZndDs7IGll
dGZAaWV0Zi5vcmc8YnI+DQo8Yj5DYzo8L2I+IGJlbkBub3N0cnVtLmNvbTsgc2lwY29yZS1jaGFp
cnNAaWV0Zi5vcmc7IHNpcGNvcmVAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtc2lwY29yZS1zdGF0dXMt
dW53YW50ZWRAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtzaXBjb3JlXSBMYXN0
IENhbGw6ICZsdDtkcmFmdC1pZXRmLXNpcGNvcmUtc3RhdHVzLXVud2FudGVkLTA0LnR4dCZndDsg
KEEgU0lQIFJlc3BvbnNlIENvZGUgZm9yIFVud2FudGVkIENhbGxzKSB0byBQcm9wb3NlZCBTdGFu
ZGFyZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5PbiAzLzIxLzE3IDEwOjQ5LCBQZXRlIFJlc25pY2sgd3JvdGU6PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206
NS4wcHQiPg0KPG9sIHN0YXJ0PSIxIiB0eXBlPSIxIj4NCjxsaSBzdHlsZT0ibWFyZ2luLWxlZnQ6
MGluO21zby1saXN0OmwwIGxldmVsMSBsZm8yIj5UaGUgNjY2IG1lY2hhbmlzbSBsZWF2ZXMgdGhl
IGRlY2lzaW9uIG9mIHdoYXQgaXMgbWVhbnQgYnkgJnF1b3Q7dW53YW50ZWQmcXVvdDsgdG8gdGhl
IHByb3ZpZGVyLCB3aGljaCB3aWxsIGluZXZpdGFibHkgY2F1c2UgZGF0YSBsb3NzIHRocm91Z2gg
dGhlIHVzZSBvZiBoZXVyaXN0aWNzLiBBZGRpbmcgYSBoZWFkZXIgdG8gdGhlIDYwMyByZXNwb25z
ZSBpcyBhbiBleHRlbnNpYmxlDQogbWVjaGFuaXNtIHRoYXQgY291bGQgY2FwdHVyZSB0aGUgc2lu
Z2xlIHNlbWFudGljIGJpdCBvZiA2NjYgPGVtPmFuZCBhbnkgZnV0dXJlIHNlbWFudGljcyB0aGF0
IG9uZSB3aXNoZXMgdG8gYWRkPC9lbT4sIHdpdGhvdXQgcmVxdWlyaW5nIHRoZSBwcm92aWRlciB0
byBndWVzcy4gVGhlIHByb3ZpZGVyIGdldHMgZGVmaW5pdGl2ZSBpbmZvcm1hdGlvbiB0aGF0IGl0
IGNhbiBhY3Qgb24uPG86cD48L286cD48L2xpPjwvb2w+DQo8L2Jsb2NrcXVvdGU+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48YnI+DQpUaGUgcHJvYmxlbSBpcyB0aGF0IHRoZSBzZW1hbnRpY3Mgb2Yg
NjY2IGFyZSBiYWNrd2FyZHMgZnJvbSB0aGUgc2VtYW50aWNzIG9mIDYwMy48YnI+DQo8YnI+DQo2
MDMgbWVhbnMgJnF1b3Q7dGhlcmUgaXMgYW4gaXNzdWUgd2l0aCB0aGUgZGlzcG9zaXRpb24gb2Yg
dGhlICpjYWxsZWQqIHBhcnR5IHRoYXQgcHJldmVudHMgY29tcGxldGluZyB0aGUgY2FsbC4mcXVv
dDs8YnI+DQo8YnI+DQo2NjYgbWVhbnMgJnF1b3Q7dGhlcmUgaXMgYW4gaXNzdWUgd2l0aCB0aGUg
ZGlzcG9zaXRpb24gb2YgdGhlICpjYWxsaW5nKiBwYXJ0eSB0aGF0IHByZXZlbnRzIGNvbXBsZXRp
bmcgdGhlIGNhbGwuJnF1b3Q7PGJyPg0KPGJyPg0KWW91J3JlIHByb3Bvc2luZyBjb25mbGF0aW5n
IHRoZSB0d28gc2VtYW50aWNzLCB3aGljaCBuZWNlc3NhcmlseSBpbnRyb2R1Y2VzIG1vcmUgYW1i
aWd1aXR5LCBub3QgbGVzcy48YnI+DQo8YnI+DQpDYXJyaWVyIGRldGVybWluYXRpb24gb2YgaG93
IHRvIGhhbmRsZSB0aGVzZSBjb2RlcyBpcywgYXMgd2l0aCBhbnkgbnVpc2FuY2UgY29tbXVuaWNh
dGlvbiBtaXRpZ2F0aW9uLCBnb2luZyB0byBuZWNlc3NhcmlseSBiZSBiYXNlZCBvbiBoZXVyaXN0
aWNzIHRvIGF2b2lkIGFjY2lkZW50YWwgYmxhY2tsaXN0aW5nLCBpbnRlbnRpb25hbCBibG93YmFj
aywgYW5kIHRoZSBpbmV2aXRhYmxlIGdhbWluZyBvZiB0aGUgc3lzdGVtIGJ5IGJhZCBhY3RvcnMu
DQogWW91IGltcGx5IHRoYXQgdGhlIGFwcGxpY2F0aW9uIG9mIGhldXJpc3RpY3MgaXMgYW4gdW53
YW50ZWQgc2lkZSBlZmZlY3Qgb2YgdGhlIHN5c3RlbSwgd2hlbiBpdCBpbiBmYWN0IHRoZSBwcmlt
YXJ5IGdvYWwuPGJyPg0KPGJyPg0KSW4gdGVybXMgb2YgYmVpbmcgYWJsZSB0byBwcm92aWRlIGdy
YWRhdGlvbiBiZXR3ZWVuIHR5cGVzIG9mIHVud2FudGVkIGNhbGxzLCB0aGUgYXBwbGljYXRpb24g
b2YgYSBoZWFkZXIgLS0gYXMgeW91IHByb3Bvc2UgLS0gdG8gcHJvdmlkZSBzdWNoIGluZGljYXRp
b24gc2VlbXMgbGlrZSBhIGZpbmUgaWRlYS4gSSB3aWxsIHBvaW50IG91dCBvbmUgY2F2ZWF0IGFu
ZCBtYWtlIG9uZSBvYnNlcnZhdGlvbi4gVGhlIGNhdmVhdCBpcyB0aGF0IGl0IHdvdWxkDQogYmUg
aGFybWZ1bCB0byBhZGQgdGhpcyBoZWFkZXIgaW4gYSB3YXkgdGhhdCByZXZlcnNlcyB0aGUgc2Vu
c2Ugb2YgYSByZXNwb25zZSBjb2RlLCBzdWNoIGFzIG1ha2luZyA2MDMgYmVhciBvbiB0aGUgY2Fs
bGluZyBwYXJ0eSByYXRoZXIgdGhhbiB0aGUgY2FsbGVkIHBhcnR5OyBzbyBzdWNoIGFuIGluZGlj
YXRpb24gd291bGQgbmVlZCB0byBiZSBvbiBhIG5ldyByZXNwb25zZSBjb2RlLCBzdWNoIGFzIHRo
ZSBvbmUgY3VycmVudGx5IHByb3Bvc2VkDQogaW4gZHJhZnQtaWV0Zi1zaXBjb3JlLXN0YXR1cy11
bndhbnRlZC4gVGhlIG9ic2VydmF0aW9uIGlzIHRoYXQgdGhpcyBtZWNoYW5pc20gY2FuIGJlIGFk
ZGVkIHRvIHRoaXMgbmV3IHN0YXR1cyBhdCBhIGxhdGVyIGRhdGUsIGluIGEgbW9kdWxhciBmYXNo
aW9uIGFuZCBpbiBhIGJhY2t3YXJkcyBjb21wYXRpYmxlIHdheS4gSW4gb3RoZXIgd29yZHM6IHlv
dXIgcHJvcG9zZWQgZW5oYW5jZW1lbnQgaXMgKm5pY2UqLCBidXQgaXQgZG9lcyBub3QgcHJlY2x1
ZGUNCiBwdWJsaXNoaW5nIHRoZSBtZWNoYW5pc20gY3VycmVudGx5IGRlc2NyaWJlZC48YnI+DQo8
YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9w
OjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPG9sIHN0YXJ0PSIyIiB0eXBlPSIxIj4NCjxs
aSBzdHlsZT0ibWFyZ2luLWxlZnQ6MGluO21zby1saXN0OmwyIGxldmVsMSBsZm80Ij5UaGUgNjY2
IG1lY2hhbmlzbSBsaW1pdHMgdGhlIGltcGxlbWVudGF0aW9uIG9mIHRoZSBtZWNoYW5pc20gdG8g
YSAxLWJ1dHRvbiBjaG9pY2UgYW5kIHJlcXVpcmVzIGFkZGl0aW9uYWwgc3RhbmRhcmRpemF0aW9u
IHdvcmsgdG8gdXNlIGEgZGlmZmVyZW50IFVJLiBDbGVhcmx5IDY2NiB3YXMgZGVzaWduZWQgYXJv
dW5kIHNvbWV0aGluZyBha2luIHRvIGEgJnF1b3Q7U1BBTSZxdW90Ow0KIGJ1dHRvbiBpbiB0aGUg
VUkuIEJ1dCB3aGF0IGlmIEkgd2FudCBhIGZpZWxkIGluIG15IGFkZHJlc3MgYm9vayB0aGF0IHNh
eXMsICZxdW90O1Blcm1hbmVudGx5IGJsb2NrIHRoaXMgcGFydGljdWxhciBjYWxsZXImcXVvdDsg
KHNheSwgbXkgZXgtYm95ZnJpZW5kIG9yIG15IGFubm95aW5nIG5laWdoYm9yKT8gSSBkb24ndCB3
YW50IHRvIGluZGljYXRlIHRoYXQgdGhlc2UgYXJlIHNwYW0gY2FsbHMgYmVjYXVzZSBJIGRvbid0
IHdhbnQgbXkgcHJvdmlkZXIgYXBwbHlpbmcNCiBoZXVyaXN0aWNzIHRvIHRoZW0uIEkgd2FudCB0
byBzZW5kIGJhY2sgYSA2MDMgd2l0aCBhIGhlYWRlciB0aGF0IHNheXMsICZxdW90O0Jsb2NrIHRo
ZXNlIHdoZW5ldmVyIHlvdSBzZWUgdGhlbSwgYnV0IG9ubHkgZm9yIG1lLiZxdW90OyBJIGNhbiB0
aGluayBvZiBhbGwgc29ydHMgb2Ygb3RoZXItdGhhbi1vbmUtYnV0dG9uIFVJcyB0aGF0IHNvbWVv
bmUgbWlnaHQgd2FudCB0byBpbXBsZW1lbnQuIDY2NiBpcyB0aWVkIHRvIGEgcGFydGljdWxhciBV
SS4gNjAzIHdpdGgNCiBhIGhlYWRlciBpcyBleHRlbnNpYmxlLjxvOnA+PC9vOnA+PC9saT48L29s
Pg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KVGhhdCBraW5kIG9m
IHBlcnNpc3RlbnQsIGhhcmQtc3RhdGUgdXNlciBhY2NvdW50IGNvbmZpZ3VyYXRpb24gKnJlYWxs
eSogaXNuJ3QgYSByZWFzb25hYmxlIGtpbmQgb2YgdGhpbmcgdG8gZG8gd2l0aCBhIFNJUCBzdGF0
dXMgY29kZSAobm90IGxlYXN0IG9mIGFsbCBiZWNhdXNlIHlvdSB3b3VsZCBuZWVkIHNvbWUgbWVj
aGFuaXNtIGZvciByZXZpZXdpbmcgYW5kIG1hbmFnaW5nIHN1Y2ggYSBsaXN0OyBhbmQgd2hhdGV2
ZXIgdGhhdCBtZWNoYW5pc20NCiBpcyBjb3VsZCBqdXN0IGFzIHJlYWRpbHkgYmUgdXNlZCBmb3Ig
YWRkaW5nIGVudHJpZXMpLiBJZiB5b3UgZmVlbCB0aGUgbmVlZCB0byBwdXJzdWUgdGhlIHNvbWV3
aGF0IHJlbGF0ZWQgcHJvYmxlbSBzcGFjZSBvZiBhIG5ldHdvcmstYXNzaXN0ZWQgYmxvY2tsaXN0
LCB3ZSBoYXZlIGEgdmFyaWV0eSBvZiB0b29scyB3ZSBjb3VsZCBicmluZyB0byBiZWFyLCBzdWNo
IGFzIFhDQVAuIFRoYXQncyBhIHNlcGFyYWJsZSBwcm9ibGVtLCB0aG91Z2gsIGFuZA0KIEkgdGhp
bmsgdGhhdCB0YW5nbGluZyBpdCB1cCB3aXRoIHNwYW0gbWl0aWdhdGlvbiBpcyBhIGh1Z2UgbWlz
dGFrZS48YnI+DQo8YnI+DQpJJ2xsIGFsc28gcG9pbnQgb3V0IHRoYXQgZGV2aWNlcyBhcmUgcGVy
ZmVjdGx5IGNhcGFibGUgb2YgaGFuZGxpbmcgdGhpcyBmZWF0dXJlIGxvY2FsbHkgd2l0aG91dCBh
bnkgYXNzaXN0YW5jZSBmcm9tIHRoZSBuZXR3b3JrLCBzbyBJJ20gbm90IHN1cmUgaG93IG11Y2gg
dmFsdWUgd291bGQgYmUgYWRkZWQgYnkgZGVmaW5pbmcgYSBuZXR3b3JrLWhvc3RlZCB2ZXJzaW9u
IG9mIHRoZSBzZXJ2aWNlLiBUaGUgb3ZlcmFyY2hpbmcgcG9pbnQsIHRob3VnaCwNCiBpcyB0aGF0
IGEgU0lQIHJlc3BvbnNlIGNvZGUgaXMgYWJzb2x1dGVseSB0aGUgd3JvbmcgYXBwcm9hY2ggZm9y
IGRvaW5nIHNvLjxicj4NCjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUg
c3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8b2wgc3RhcnQ9
IjMiIHR5cGU9IjEiPg0KPGxpIHN0eWxlPSJtYXJnaW4tbGVmdDowaW47bXNvLWxpc3Q6bDEgbGV2
ZWwxIGxmbzYiPlRoZSA2NjYgbWVjaGFuaXNtIHdpbGwgYmUgdHJlYXRlZCBhcyBhIDYwMCAmcXVv
dDtCdXN5JnF1b3Q7IGVycm9yIGJ5IHVuLXVwZ3JhZGVkIGNhbGxlcnMgYW5kL29yIHByb3ZpZGVy
cy4gVGhhdCBtaWdodCBpbXBseSB0byBzb21lIGltcGxlbWVudGF0aW9ucyB0aGF0IHRoZXkgc2hv
dWxkIHRyeSB0byByZS1kaWFsIChlLmcuLCB0aGUgcHJvdmlkZXIgdXNpbmcgdGhlIGF1dG8tcmVk
aWFsDQogZmVhdHVyZSkgb3IgdG8gZW5nYWdlIGluIG90aGVyIHBvb3IgYmVoYXZpb3IuIDYwMyB3
aXRoIG5vIFJldHJ5LUFmdGVyIGhlYWRlciBhbHJlYWR5IGhhcyBhIHNlbWFudGljIG9mICZxdW90
O1RoZSBjYWxsIHdhcyByZWplY3RlZCBhbmQgSSdtIG5vdCB0ZWxsaW5nIHlvdSB3aGVuIGEgZ29v
ZCB0aW1lIHRvIGNhbGwgYmFjayBpcyZxdW90Oywgc28gdGhlcmUgaXMgc29tZSBob3BlIHRoYXQg
YW4gdW4tdXBncmFkZWQgY2FsbGVyIGlzIG1vcmUgbGlrZWx5IHRvIGRvIHRoZQ0KIHJpZ2h0IHRo
aW5nLjxvOnA+PC9vOnA+PC9saT48L29sPg0KPC9ibG9ja3F1b3RlPg0KPHA+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cD5UaGlzIGlzIHJlYWxseSByZWFjaGluZywgYW5kIEkgdGhpbmsgaXMgYmFz
ZWQgb24gYSBtaXNwZXJjZXB0aW9uIG9mIGhvdyBTSVAgY2xpZW50cyBhY3R1YWxseSB3b3JrIHdo
ZW4gdGhleSByZWNlaXZlIDZ4eCByZXNwb25zZXMuIFRha2VuIHRvIGl0cyBsb2dpY2FsIGNvbmNs
dXNpb24sIGlmIHdlIGFjY2VwdCB5b3VyIGFzc2VydGlvbiB0aGVuIHdlIGNhbid0IGV2ZXIgZGVm
aW5lIGEgbmV3IDZ4eC1jbGFzcyBTSVAgcmVzcG9uc2UgY29kZSBmb3INCiBmZWFyIHRoYXQgc3Vj
aCBjb2RlcyAmcXVvdDttaWdodCBpbXBseSB0byBzb21lIGltcGxlbWVudGF0aW9ucyB0aGF0IHRo
ZXkgc2hvdWxkIHRyeSB0byByZS1kaWFsIChlLmcuLCB0aGUgcHJvdmlkZXIgdXNpbmcgdGhlIGF1
dG8tcmVkaWFsIGZlYXR1cmUpIG9yIHRvIGVuZ2FnZSBpbiBvdGhlciBwb29yIGJlaGF2aW9yLiZx
dW90OzxvOnA+PC9vOnA+PC9wPg0KPHA+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cD4vYTxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=
--_000_CY1PR03MB23484A2E5BA8F065A090761CB23D0CY1PR03MB2348namp_--


From nobody Tue Mar 21 10:43:45 2017
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 CCABC129C48; Tue, 21 Mar 2017 10:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rhy6zX3Q2o8l; Tue, 21 Mar 2017 10:43:38 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC63F129BDB; Tue, 21 Mar 2017 10:43:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490118217; x=1521654217; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=IcBMkB34cKarcHBeOlLpKn4unYhqK6CwGmS9B9r7/Uo=; b=OlQYadoWXeeAismjqtqQcVwcOxegIhatD61/xM2fJSkASPM0hsjwRTUU P7+wq9ZPGNiWFKeNOpvvqIkw6x3D+X2PD/c+3YnGodeulLSdN9e383vbI rKB3h1UACoY6E9/RCzsekpMEcCaficwTkXaT4Yu6KXIwBevuumNrS9GiA M=;
X-IronPort-AV: E=Sophos;i="5.36,200,1486454400"; d="scan'208";a="271798514"
Received: from unknown (HELO ironmsg02-L.qualcomm.com) ([10.53.140.109]) by wolverine01.qualcomm.com with ESMTP; 21 Mar 2017 10:43:36 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8474"; a="889673326"
X-MGA-submission: =?us-ascii?q?MDELvyk0SZV+FWP22BiwMESYjkzI/vELT8D7rb?= =?us-ascii?q?eZlB9fMlcRBHhw9q53KnHjL0eWDVUPtfUO4Sx3K54qPDFLUbnp60y4lB?= =?us-ascii?q?IuwtIVv6i28up5GHJf0/em/FFhw2Va3Gq/0hX90edCV45diCLOc4oVHb?= =?us-ascii?q?Hk?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Mar 2017 10:43:36 -0700
Received: from [10.64.124.243] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 21 Mar 2017 10:43:30 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Alan Johnston <alan.b.johnston@gmail.com>
CC: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>, "sipcore@ietf.org" <sipcore@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-sipcore-status-unwanted@ietf.org" <draft-ietf-sipcore-status-unwanted@ietf.org>
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
Date: Tue, 21 Mar 2017 12:43:28 -0500
Message-ID: <5EA78FE0-9C80-4B7F-A7F0-F9096C94F078@qti.qualcomm.com>
In-Reply-To: <CAKhHsXHDoDnO_NBOpMsyKxfY9-oKqnjE9z9SgvXnpmOTJPfDpQ@mail.gmail.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com> <BY1PR09MB0631F94D0B74E498ECCF3A4DEA3D0@BY1PR09MB0631.namprd09.prod.outlook.com> <8443007A-60F0-4AB6-80EC-DD20368D61EA@qti.qualcomm.com> <CAKhHsXHDoDnO_NBOpMsyKxfY9-oKqnjE9z9SgvXnpmOTJPfDpQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01C.na.qualcomm.com (10.85.0.83) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jsq6NgK20S0f8N5pO70VYapS_zQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 17:43:40 -0000

On 21 Mar 2017, at 12:05, Alan Johnston wrote:

> If you are proposing using a SIP response code  603 and with a header 
> field
> Decline-Type: spam, the problem with this is that in SIP, failure 
> responses
> (non-2xx) are delivered hop-by-hop and not end-to-end.  This means 
> that
> although the first hop (proxy) will get the Decline-Type:spam header 
> field,
> any future hops will not.  Instead, they will just get the 603.
>
> A different response code such as 666 will be conveyed end-to-end, so 
> every
> proxy and the calling UA will get the semantics.

Adam walked me through the last few paragraphs of 3261 section 6. It's 
not clear in that text whether proxies will or won't preserve the 
headers, but if they don't, I expect that's a showstopper for my 
proposal. That's a bummer, because I do think the status code is going 
to cause future heartburn. However, if you SIP folks conclude that the 
header will not get through proxies (and I will take you all at your 
word if you so conclude), and this mechanism does need to survive 
proxies (which I suspect it does), then I think we're stuck with the 
status code.

If so, I will happily return to you all to your discussion of whether 
particular numbers do or do not belong in IETF specifications. :-) (For 
the record, I thought 451 set a poor precedent, but I'm a curmudgeon.)

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Tue Mar 21 10:47:15 2017
Return-Path: <acee@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 91B7A129BDB; Tue, 21 Mar 2017 10:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.298
X-Spam-Level: 
X-Spam-Status: No, score=-17.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s77PjzJ-lD5n; Tue, 21 Mar 2017 10:47:13 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0A1B128854; Tue, 21 Mar 2017 10:47:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2540; q=dns/txt; s=iport; t=1490118432; x=1491328032; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=CVX/iGnkPDTeZ/UsEYi9IlR5nlxwjcpW2wvOxrSs5ak=; b=lL4r5SJBEvG42nYb1sKpQAwX99R9y9j9uigGwER35QiE9XWi0yQ21YOr xJDriBCphx72F3W3yxVRB0gJaQKjsURKnOzcy2xc5934hZfiHz/jW35zw QNsTVKiHO/d9RPN43HeHB2Cqz1vG1L4pCCF3rMKHracgYaJ13sti2OFxO I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ATAQDEZdFY/4cNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1FhgQoHjWuRXpM1gg+CDiyFdgKDFD8YAQIBAQEBAQEBayiFFQE?= =?us-ascii?q?BAQEDbgsMBAIBCBUBJQsyJQIEAQ0FigQOrFeKSgEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAR2LPYo5BZAejDIBhnmLTIF7hSiKCpNeAR84gQRYFUGFDYFKdYcGK4EDgQ0?= =?us-ascii?q?BAQE?=
X-IronPort-AV: E=Sophos;i="5.36,200,1486425600"; d="scan'208";a="401183249"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Mar 2017 17:47:10 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v2LHlAet002529 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 21 Mar 2017 17:47:10 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 21 Mar 2017 13:47:09 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Tue, 21 Mar 2017 13:47:10 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "tom p." <daedulus@btconnect.com>, "ietf@ietf.org" <ietf@ietf.org>, "YANG Doctors" <yang-doctors@ietf.org>
CC: "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "draft-ietf-rtgwg-yang-key-chain@ietf.org" <draft-ietf-rtgwg-yang-key-chain@ietf.org>
Subject: Re: Last Call: <draft-ietf-rtgwg-yang-key-chain-15.txt> (Routing Key Chain YANG Data Model) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-rtgwg-yang-key-chain-15.txt> (Routing Key Chain YANG Data Model) to Proposed Standard
Thread-Index: AQHSomMGb4hAifYGPEi2aaI1piKkJqGfkYOA
Date: Tue, 21 Mar 2017 17:47:09 +0000
Message-ID: <D4F6DED9.A393B%acee@cisco.com>
References: <148976778864.13097.8837542947858587684.idtracker@ietfa.amsl.com> <011901d2a262$c59162e0$4001a8c0@gateway.2wire.net>
In-Reply-To: <011901d2a262$c59162e0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <00875A013CAE09438C552607340B61E0@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dLoihPBz-Eu3s7a5c--6aqFXqlE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 17:47:15 -0000

+yang-doctors

Hi Tom,=20


The draft validates with no errors/warnings with either 1.0 or 1.1 for the
version using the draft validator:

http://www.yangvalidator.com/draft-validator

But this raises an interesting point. Should the published version be 1.0
since the model doesn=B9t make usage of any 1.1 constructs?

Thanks,
Acee=20


On 3/21/17, 12:44 PM, "tom p." <daedulus@btconnect.com> wrote:

>Why does this I-D make no mention of YANG 1.1, which has been around for
>a while now (albeit not superseding YANG 1.0)?
>
>Has the YANG module been validated against YANG 1.1?
>
>Tom Petch
>
>
>----- Original Message -----
>From: "The IESG" <iesg-secretary@ietf.org>
>Sent: Friday, March 17, 2017 4:23 PM
>
>
>>
>> The IESG has received a request from the Routing Area Working Group WG
>> (rtgwg) to consider the following document:
>> - 'Routing Key Chain YANG Data Model'
>>   <draft-ietf-rtgwg-yang-key-chain-15.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 2017-04-07. 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 key chain YANG data model.  A key chain
>>    is a list of elements each containing a key string, send lifetime,
>>    accept lifetime, and algorithm (authentication or encryption).  By
>>    properly overlapping the send and accept lifetimes of multiple key
>>    chain elements, key strings and algorithms may be gracefully
>updated.
>>    By representing them in a YANG data model, key distribution can be
>>    automated.  Key chains are commonly used for routing protocol
>>    authentication and other applications.  In some applications, the
>>    protocols do not use the key chain element key directly, but rather
>a
>>    key derivation function is used to derive a short-lived key from
>the
>>    key chain element key (e.g., the Master Keys used in the TCP
>>    Authentication Option.
>>
>>
>>
>>
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/
>>
>> IESG discussion can be tracked via
>>
>https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>


From nobody Tue Mar 21 10:49:45 2017
Return-Path: <adam@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 2E463129542; Tue, 21 Mar 2017 10:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQhQisYXlxUx; Tue, 21 Mar 2017 10:49:37 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F094F128854; Tue, 21 Mar 2017 10:49:36 -0700 (PDT)
Received: from Orochi.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v2LHnWjh068329 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 21 Mar 2017 12:49:33 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Orochi.local
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: Pete Resnick <presnick@qti.qualcomm.com>, Alan Johnston <alan.b.johnston@gmail.com>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <E74825F1-B661-4A8C-9B96-CC970AEA0E56@qti.qualcomm.com> <BY1PR09MB0631F94D0B74E498ECCF3A4DEA3D0@BY1PR09MB0631.namprd09.prod.outlook.com> <8443007A-60F0-4AB6-80EC-DD20368D61EA@qti.qualcomm.com> <CAKhHsXHDoDnO_NBOpMsyKxfY9-oKqnjE9z9SgvXnpmOTJPfDpQ@mail.gmail.com> <5EA78FE0-9C80-4B7F-A7F0-F9096C94F078@qti.qualcomm.com>
Cc: "draft-ietf-sipcore-status-unwanted@ietf.org" <draft-ietf-sipcore-status-unwanted@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
From: Adam Roach <adam@nostrum.com>
Message-ID: <6b32dd4d-b5d8-c190-9d34-ecf54d1c3853@nostrum.com>
Date: Tue, 21 Mar 2017 12:49:26 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <5EA78FE0-9C80-4B7F-A7F0-F9096C94F078@qti.qualcomm.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0_Jc1mI23cvfPhdm_b1iw-isQgo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 17:49:38 -0000

On 3/21/17 12:43, Pete Resnick wrote:
> Adam walked me through the last few paragraphs of 3261 section 6.


To be clear (and this is an easy mistake to make, since the sections and 
their contained steps are huge), Pete is referring to the long-form 
version of step 6 in section 16.7 here. See RFC 3261, page 111.

/a


From nobody Tue Mar 21 12:52:05 2017
Return-Path: <worley@alum.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 B1A0F128B38 for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 12:51:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7nV4-XVKSh-V for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 12:51:57 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 476AB128E19 for <ietf@ietf.org>; Tue, 21 Mar 2017 12:51:56 -0700 (PDT)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-01v.sys.comcast.net with SMTP id qPnLcIZ7kO3QoqPoxchJSl; Tue, 21 Mar 2017 19:51:55 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-18v.sys.comcast.net with SMTP id qPovckuQDStKdqPovcxeBw; Tue, 21 Mar 2017 19:51:54 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v2LJpq5c005564; Tue, 21 Mar 2017 15:51:52 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v2LJpqde005556; Tue, 21 Mar 2017 15:51:52 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Adam Roach <adam@nostrum.com>
Cc: presnick@qti.qualcomm.com, alan.b.johnston@gmail.com, Henning.Schulzrinne@fcc.gov, sipcore@ietf.org, ietf@ietf.org, draft-ietf-sipcore-status-unwanted@ietf.org
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
In-Reply-To: <6b32dd4d-b5d8-c190-9d34-ecf54d1c3853@nostrum.com> (adam@nostrum.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 21 Mar 2017 15:51:52 -0400
Message-ID: <87wpbitnl3.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfHScBlLdI+tYRt5XHbAa4RKaEE048vzUGJMqPom0i1b0uVj2G0ueJ9K4Mu9xn9ehtGaGvuS4SdaBMhdgxtrVi5FJ/C8bhU4R02f9RxvPU7aXuZdgenrL YIjwS6Udt4SZjeI9qaK/BnIpJNn9n3B1vs3PWrdTHQKWORSNI8jJ2hYod91BA+wn++WcQL7vk3y1IWTeh9lAtIpPU3f25X1Lj+1TOoNKKgExRH1nroB+1OS+ ascF+Ih7Y3NZueei5ImMsldtu3wczd2L7mhwtgZ3fsfZ1AfbmQkJzEGYszZq/N9RKQjlSjEiVno4bbyqdCm732HnZEJ31xCU91aVuq4KahyYXsGCZWDeT+vC pP0lYJQ1L+lNRVhpU8lFSngE8WwVERNeNxFDlLEjD/qYIVlxcHA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f6WMNtDxga-gmgQcP1q10QPKmJY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 19:51:59 -0000

Adam Roach <adam@nostrum.com> writes:
> To be clear (and this is an easy mistake to make, since the sections and 
> their contained steps are huge), Pete is referring to the long-form 
> version of step 6 in section 16.7 here. See RFC 3261, page 111.

Ah, there's a tension between this paragraph:

         The stateful proxy MUST choose the "best" final response among
         those received and stored in the response context.

and this one:

         3-6xx responses are delivered hop-by-hop.  When issuing a 3-6xx
         response, the element is effectively acting as a UAS, issuing
         its own response, usually based on the responses received from
         downstream elements.  An element SHOULD preserve the To tag
         when simply forwarding a 3-6xx response to a request that did
         not contain a To tag.

But if many implementations take "choose the best final response" to
mean only re-sending the response code, we have a problem.

OTOH, it's quite possible to reserve a *set* of 6xx response codes to
carry the decline-type.  The only allocated 6xx responses are 600
(generic), 603, 604, and 606.

Dale


From nobody Tue Mar 21 15:10:20 2017
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD2EB127B57; Tue, 21 Mar 2017 15:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hv9vkV0f10gP; Tue, 21 Mar 2017 15:10:01 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53C6B12F28A; Tue, 21 Mar 2017 15:10:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id C202A7C63EA; Tue, 21 Mar 2017 23:09:58 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v4nPQI6N_4gu; Tue, 21 Mar 2017 23:09:58 +0100 (CET)
Received: from [IPv6:2001:470:de0a:1::5ea] (unknown [IPv6:2001:470:de0a:1::5ea]) by mork.alvestrand.no (Postfix) with ESMTPSA id D62527C56E3; Tue, 21 Mar 2017 23:09:57 +0100 (CET)
Subject: Re: Review of draft-ietf-rtcweb-overview-18
To: Jon Mitchell <jrmitche@puck.nether.net>, ops-dir@ietf.org
References: <148977468781.13113.11027871370786405378@ietfa.amsl.com>
Cc: draft-ietf-rtcweb-overview.all@ietf.org, rtcweb@ietf.org, ietf@ietf.org
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <8d6db7a5-7677-8561-26ac-78de4f53534e@alvestrand.no>
Date: Tue, 21 Mar 2017 23:09:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148977468781.13113.11027871370786405378@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zV6oMmvzF3FlwdrlRrIYQp5z7UU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Mar 2017 22:10:06 -0000

Den 17. mars 2017 19:18, skrev Jon Mitchell:
> Reviewer: Jon Mitchell
> Review result: Ready
> 
> I have reviewed this document as part of the Operational directorate's
> 
> ongoing effort to review all IETF documents being processed by the
> IESG.  These 
> comments were written with the intent of improving the operational
> aspects of the 
> IETF drafts. Comments that are not addressed in last call may be
> included in AD reviews 
> during the IESG review.  Document editors and WG chairs should treat
> these comments 
> just like any other last call comments. 
> 
> This document is an overall of the WebRTC protocols that are
> considered a "minimum" set to claim compliance with the standard the
> draft sets forth.  As far as I can tell, no new protocols or
> implementation details are contained in the draft and operational
> concerns largely are covered (or not) by the many referenced protocol
> specifications within it.  Therefore, I believe this draft is Ready,
> although there is some question in my mind of whether this is actually
> a standards track versus best current practice document as
> interoperability from the standpoint of this document seems to not
> require any new on the wire negotiation (outside of each individual's
> protocols negotiations).
> 
> 

Thanks for the review!

At one point I wondered if the correct designation for this document was
the rarely-used "Applicability Statement". The WG decided to not do
process experiments with this one, but did want it on the standards
track - ie "informational" was not appropriate.

AS documents are standards-track documents.


From nobody Tue Mar 21 17:20:40 2017
Return-Path: <burmaa@datacom.mn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40C80126D85 for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 17:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.084
X-Spam-Level: 
X-Spam-Status: No, score=-4.084 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=datacom.mn
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3g8iPzmhci55 for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 17:20:35 -0700 (PDT)
Received: from gmail.mxhero.com (engine-facing-node-4.mxhero.net [54.165.253.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E3D512940A for <ietf@ietf.org>; Tue, 21 Mar 2017 17:20:35 -0700 (PDT)
Received: from engine-facing-node-4.mxhero.net (localhost [127.0.0.1]) by gmail.mxhero.com (Postfix) with ESMTP id 447554EED8 for <ietf@ietf.org>; Wed, 22 Mar 2017 00:20:34 +0000 (UTC)
Received: from mail-pg0-f72.google.com (mail-pg0-f72.google.com [74.125.83.72]) by gmail.mxhero.com (Postfix) with ESMTPS for <ietf@ietf.org>; Wed, 22 Mar 2017 00:20:34 +0000 (UTC)
Received: by mail-pg0-f72.google.com with SMTP id 81so342148302pgh.3 for <ietf@ietf.org>; Tue, 21 Mar 2017 17:20:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=datacom.mn; s=google;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=O1S6IWfPY2ko1ahr37KP8TL75Xi+/KiDW+FfTNvePP0=; b=lP2LWnyT2BhNfC1ETKAixe1/Dg1BVlB3nIwfCA5AA5uB6nzYPYXfwsN8yji+EUfPnY YK3eyemGZHGyanoafX0Lc3/asroZYYr4c06y0tSlLUNLUqX6XItsnwQmDT1yriJSn4mj jg+T0ddgauSVn7aMQXjKV6eUxCmG8ugluJhOs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=O1S6IWfPY2ko1ahr37KP8TL75Xi+/KiDW+FfTNvePP0=; b=VFxAp0Vr/+HYy8+AFJiENhRM2wGfm6g3qBLDZHoNwOo6X9OWMZoss40JhkK8qPBc60 ixjVBS34jz+AxyrtW4E4pGhjHG8krYA4LJGzfPgwx6fZgtYO/w9bhvkLFNN/3coC8HQQ C5luzfKLyhQ7a32BMwoOEM6Q4mhabAschEsSW1vugKwTThmKgp8zLUfHHRJ72Tzwuv9r nY7QbmFGVyM5s7w+iWxIP3EzkjfRqAfSTf1+nVvmaeyjqtGyqZQDzLoFV479RQdYDct4 KvtZ8ZxwRpSxeYWcC+7KhY7igK9AxB3g/Rr4vxfmibYi0adx/fKadhMULv6XeXj/lQ7i Yt6w==
X-Gm-Message-State: AFeK/H2ATATCPe/FH37STHy4ujoWlgqG+t1D4ZDCEkTYCK4z05at99Sna8PQfIP32/pZT0rLkwJT0zsX8rqLCYpjMk8/E6VpElJ3mmofyg9TDE+KdJV+WaVilQBI8JdC8//Nq59Muv6oeYqJe93rDDShfH4=
X-Received: by 10.84.215.221 with SMTP id g29mr28515512plj.10.1490142033109; Tue, 21 Mar 2017 17:20:33 -0700 (PDT)
X-Received: by 10.84.215.221 with SMTP id g29mr28515494plj.10.1490142032940; Tue, 21 Mar 2017 17:20:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.180.206 with HTTP; Tue, 21 Mar 2017 17:20:32 -0700 (PDT)
In-Reply-To: <148976773241.13191.556904629338360291.idtracker@ietfa.amsl.com>
References: <148976773241.13191.556904629338360291.idtracker@ietfa.amsl.com>
From: Burmaa Baasansuren <burmaa@datacom.mn>
Date: Wed, 22 Mar 2017 09:20:32 +0900
Message-ID: <CAOYdyEiiqdtaHdwyNMaziWqXmFRhC_SrSSKncO4DRnY16dytTA@mail.gmail.com>
Subject: Fwd: Last Call: <draft-ietf-isis-mi-bis-01.txt> (IS-IS Multi-Instance) to Proposed Standard
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=f403045c66ca89e58f054b46ba04
X-mxHero-Original-Subject: Fwd: Last Call: <draft-ietf-isis-mi-bis-01.txt> (IS-IS Multi-Instance) to Proposed Standard
x-mxHero-Origin-Ip: 74.125.83.72
X-mxHero-Sender: burmaa@datacom.mn
X-mxHero-Recipient: ietf@ietf.org
X-mxHero-Output-Service: org.mxhero.plugin.smtpconnector.service.SMTPConnectorOutputService
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/svP5dQTXfP9DmISL2dDxku0PSc0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 00:20:39 -0000

--f403045c66ca89e58f054b46ba04
Content-Type: text/plain; charset=UTF-8

Can you unsuscribe all ietf telated email?

---------- Forwarded message ----------
From: *The IESG* <iesg-secretary@ietf.org>
Date: Saturday, 18 March 2017
Subject: Last Call: <draft-ietf-isis-mi-bis-01.txt> (IS-IS Multi-Instance)
to Proposed Standard
To: IETF-Announce <ietf-announce@ietf.org>
Cc: isis-chairs@ietf.org, draft-ietf-isis-mi-bis@ietf.org, Christian Hopps <
chopps@chopps.org>, isis-wg@ietf.org, akatlas@gmail.com



The IESG has received a request from the IS-IS for IP Internets WG (isis)
to consider the following document:
- 'IS-IS Multi-Instance'
  <draft-ietf-isis-mi-bis-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 <javascript:;> mailing lists by 2017-04-07. Exceptionally,
comments may be
sent to iesg@ietf.org <javascript:;> instead. In either case, please retain
the
beginning of the Subject line to allow automated sorting.

Abstract


   This draft describes a mechanism that allows a single router to share
   one or more circuits among multiple Intermediate System To
   Intermediate System (IS-IS) routing protocol instances.

   Multiple instances allow the isolation of resources associated with
   each instance.  Routers will form instance specific adjacencies.
   Each instance can support multiple topologies.  Each topology has a
   unique Link State Database (LSDB).  Each Protocol Data Unit (PDU)
   will contain a new Type Length Value (TLV) identifying the instance
   and the topology(ies) to which the PDU belongs.

   This draft updates RFC 6822 if approved.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-isis-mi-bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-isis-mi-bis/ballot/


No IPR declarations have been submitted directly on this I-D.







-- 

Warm regards,
B.Burmaa

--f403045c66ca89e58f054b46ba04
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
 <head></head>
 <body>
  Can you unsuscribe all ietf telated email?
  <span></span>
  <br>
  <br>---------- Forwarded message ----------
  <br>From: 
  <b>The IESG</b> &lt;
  <a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt;
  <br>Date: Saturday, 18 March 2017
  <br>Subject: Last Call: &lt;draft-ietf-isis-mi-bis-01.txt&gt; (IS-IS Multi-Instance) to Proposed Standard
  <br>To: IETF-Announce &lt;
  <a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>&gt;
  <br>Cc: 
  <a href="mailto:isis-chairs@ietf.org">isis-chairs@ietf.org</a>, 
  <a href="mailto:draft-ietf-isis-mi-bis@ietf.org">draft-ietf-isis-mi-bis@ietf.org</a>, Christian Hopps &lt;
  <a href="mailto:chopps@chopps.org">chopps@chopps.org</a>&gt;, 
  <a href="mailto:isis-wg@ietf.org">isis-wg@ietf.org</a>, 
  <a href="mailto:akatlas@gmail.com">akatlas@gmail.com</a>
  <br>
  <br>
  <br>
  <br> The IESG has received a request from the IS-IS for IP Internets WG (isis)
  <br> to consider the following document:
  <br> - 'IS-IS Multi-Instance'
  <br> &nbsp; &lt;draft-ietf-isis-mi-bis-01.
  <wbr>txt&gt; as Proposed Standard
  <br> 
  <br> The IESG plans to make a decision in the next few weeks, and solicits
  <br> final comments on this action. Please send substantive comments to the
  <br> 
  <a href="javascript:;" onclick="_e(event, 'cvml', 'ietf@ietf.org')">ietf@ietf.org</a>&nbsp;mailing lists by 2017-04-07. Exceptionally, comments may be
  <br> sent to 
  <a href="javascript:;" onclick="_e(event, 'cvml', 'iesg@ietf.org')">iesg@ietf.org</a> instead. In either case, please retain the
  <br> beginning of the Subject line to allow automated sorting.
  <br> 
  <br> Abstract
  <br> 
  <br> 
  <br> &nbsp; &nbsp;This draft describes a mechanism that allows a single router to share
  <br> &nbsp; &nbsp;one or more circuits among multiple Intermediate System To
  <br> &nbsp; &nbsp;Intermediate System (IS-IS) routing protocol instances.
  <br> 
  <br> &nbsp; &nbsp;Multiple instances allow the isolation of resources associated with
  <br> &nbsp; &nbsp;each instance.&nbsp; Routers will form instance specific adjacencies.
  <br> &nbsp; &nbsp;Each instance can support multiple topologies.&nbsp; Each topology has a
  <br> &nbsp; &nbsp;unique Link State Database (LSDB).&nbsp; Each Protocol Data Unit (PDU)
  <br> &nbsp; &nbsp;will contain a new Type Length Value (TLV) identifying the instance
  <br> &nbsp; &nbsp;and the topology(ies) to which the PDU belongs.
  <br> 
  <br> &nbsp; &nbsp;This draft updates RFC 6822 if approved.
  <br> 
  <br> 
  <br> 
  <br> 
  <br> 
  <br> The file can be obtained via
  <br> 
  <a href="https://datatracker.ietf.org/doc/draft-ietf-isis-mi-bis/" target="_blank">https://datatracker.ietf.org/<wbr>doc/draft-ietf-isis-mi-bis/</a>
  <br> 
  <br> IESG discussion can be tracked via
  <br> 
  <a href="https://datatracker.ietf.org/doc/draft-ietf-isis-mi-bis/ballot/" target="_blank">https://datatracker.ietf.org/<wbr>doc/draft-ietf-isis-mi-bis/<wbr>ballot/</a>
  <br> 
  <br> 
  <br> No IPR declarations have been submitted directly on this I-D.
  <br> 
  <br> 
  <br> 
  <br> 
  <br> 
  <br>
  <br>
  <br>-- 
  <br>
  <div dir="ltr">
   <div>
    <div dir="ltr">
     <div dir="ltr">
      <p><font color="#000000"><span style="font-size:9pt"><font face="Arial, sans-serif">Warm regards,<br></font></span><span style="font-family:Arial,sans-serif;font-size:9pt">B.Burmaa&nbsp;</span></font></p> 
      <p><br></p>
     </div>
    </div>
   </div>
  </div>
  <br> 
 </body>
</html>
--f403045c66ca89e58f054b46ba04--


From nobody Tue Mar 21 17:23:21 2017
Return-Path: <denis@ovsienko.info>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93FA1130133 for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 17:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.797
X-Spam-Level: 
X-Spam-Status: No, score=-4.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ovsienko.info
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67s6QRBO5RzP for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 17:23:18 -0700 (PDT)
Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com [135.84.80.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 278EF129412 for <ietf@ietf.org>; Tue, 21 Mar 2017 17:23:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1490142193;  s=zohomail; d=ovsienko.info; i=denis@ovsienko.info; h=Date:From:To:Cc:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; l=1280; bh=JaFimU7+RdtSDo7BQUmulrk/7MwUX1PEjFivG9JwEC4=; b=m89884NXuyPUi8si2VK4hYnD+0iqv/naaBYZvcc3noDZBbiGge8yjdnl6UQQ4Cy7 Bul7RUpvKTn5ByXVNsYLvWOMBEsHid0jSX1amtNhZBNPWVVQCN38puOWHRV3pH9A/9S EeBKX6DajDzOhIlJVWtIODNF0oNBZm0i9YyyvTF0=
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1490142193728685.4289529151474; Tue, 21 Mar 2017 17:23:13 -0700 (PDT)
Date: Wed, 22 Mar 2017 00:23:13 +0000
From: Denis Ovsienko <denis@ovsienko.info>
To: Paul Kyzivat <paul.kyzivat@comcast.net>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <15af365683e.dcf5ec8274777.6641471719326234265@ovsienko.info>
In-Reply-To: <d0768a84-410a-0acb-fd1a-b8f666eff18f@comcast.net>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <15aeb1be62a.11b35bf8267637.2121189919710903185@ovsienko.info> <d0768a84-410a-0acb-fd1a-b8f666eff18f@comcast.net>
Subject: Re: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rrZ-RiR_PAgqsBByjdl8xpTIHEA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 00:23:19 -0000

---- On Tue, 21 Mar 2017 02:38:33 +0000 Paul Kyzivat  wrote ---- 
>Denis, 
> 
>Do you have any expertise with SIP? I don't recall ever seeing your name 
>before. Your comments exhibit a profound misunderstanding of it. 

Pete, I am happy to admit I don't have any meaningful expertise with SIP and it is quite likely I misunderstand important things about it as an engineer.

The point I am making is one of an end user: the document is an ethical failure already, in its present edition it is not appropriate for the large, non-technical user base of SIP.

The Internet where software makes it more likely for people to go wrong is worse, not better. "The goal of the IETF is to make the Internet work better." So now is time to stop and think instead of rushing the document through.

>SIP response codes are almost never displayed to end users. For that 
>matter they aren't even typically exposed to *operators* of SIP-based 
>systems. Only when people are diagnosing signaling problems within the 
>network are they visible. So the basic premise of your objection is 
>ill-founded. 

This is similar to how HTTP response codes were originally intended; today's reality is that quite a fraction of Earth population can tell what HTTP 404 means.

-- 
    Denis Ovsienko



From nobody Tue Mar 21 19:04:44 2017
Return-Path: <gengxuesong@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA398129431; Tue, 21 Mar 2017 19:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9C_m8rpmaEmZ; Tue, 21 Mar 2017 19:04:39 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A877126BF7; Tue, 21 Mar 2017 19:04:38 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml709-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DDF00375; Wed, 22 Mar 2017 02:04:36 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 22 Mar 2017 02:04:34 +0000
Received: from DGGEMA403-HUB.china.huawei.com (10.3.20.44) by nkgeml411-hub.china.huawei.com (10.98.56.70) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 22 Mar 2017 10:04:32 +0800
Received: from DGGEMA501-MBS.china.huawei.com ([169.254.4.56]) by DGGEMA403-HUB.china.huawei.com ([10.3.20.44]) with mapi id 14.03.0301.000; Wed, 22 Mar 2017 10:04:30 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: Yoav Nir <ynir.ietf@gmail.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-ietf-aqm-codel.all@ietf.org" <draft-ietf-aqm-codel.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "aqm@ietf.org" <aqm@ietf.org>
Subject: RE: [aqm] Review of draft-ietf-aqm-codel-07
Thread-Topic: [aqm] Review of draft-ietf-aqm-codel-07
Thread-Index: AQHSohmrIModH2ljM06Ghh8sQcqdUqGgGhzw
Date: Wed, 22 Mar 2017 02:04:30 +0000
Message-ID: <F1C1D5B02EA3FA4A8AF54C86BA4F325CEB8479@DGGEMA501-MBS.china.huawei.com>
References: <149008338604.24977.6083947817909590331@ietfa.amsl.com>
In-Reply-To: <149008338604.24977.6083947817909590331@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.130.169.123]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.58D1DBB4.01E4, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.56, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: d1de04b9f72ef8ec43a766f971f4a0f3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E0Ooe7_zMHsjyra-oZ9QH50qCok>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 02:04:43 -0000

Hi,=20

I can not agree more on this.
It is well written, but I really think I can get the point of the draft fas=
ter if I can read the section 5 before section 3.


Best Regards,
Emma (Xuesong)

-----Original Message-----
From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Yoav Nir
Sent: Tuesday, March 21, 2017 4:03 PM
To: secdir@ietf.org
Cc: draft-ietf-aqm-codel.all@ietf.org; ietf@ietf.org; aqm@ietf.org
Subject: [aqm] Review of draft-ietf-aqm-codel-07

Reviewer: Yoav Nir
Review result: Has Nits

Hi,

I have reviewed this document as part of the security directorate's ongoing=
 effort to review all IETF documents being processed by the IESG.  These co=
mments were written primarily for the benefit of the security area director=
s.  Document editors and WG chairs should treat these comments just like an=
y other last call comments.

The document describes the CoDel (controlled delay) framework for reducing =
bufferbloat. It does a good job of describing the problem, outlining the so=
lution and providing both a description of the algorithm (including pseudo-=
code) and linking to real world implementations.=20

Two nits:

1. A lot of terms are used long before they are explained, such as Estimato=
r, Sojourn time, Interval (BTW: if this is a moving interval the spec shoul=
d probably say so). When reading sections 3 I concluded that the document w=
as aimed at peopel who already knew all these terms and didn't need definit=
ions, but then reading section 5 gave me a lot of a-ha moments about what I=
 had read previously.

2. The security considerations section says "There are no specific security=
 exposures associated with CoDel."  CoDel is about dropping packets, so imm=
ediately I have to think how I could subvert a router running CoDel to drop=
 other people's packets. Perhaps it is fine to say that there are no known =
attacks on CoDel and no steps necessary to mitigate such, but I think it's =
tempting fate and hackers to say that CoDel has no security exposures.

_______________________________________________
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm


From nobody Tue Mar 21 20:44:29 2017
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4200A131443; Tue, 21 Mar 2017 20:44:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Peter Yee <peter@akayla.com>
To: <gen-art@ietf.org>
Cc: sipcore@ietf.org, ietf@ietf.org, draft-ietf-sipcore-status-unwanted.all@ietf.org
Subject: Review of draft-ietf-sipcore-status-unwanted-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.00
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149015426220.3518.3546300688917567228@ietfa.amsl.com>
Date: Tue, 21 Mar 2017 20:44:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cLySixnP8mLyoFyjwjcaB7plSWI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 03:44:22 -0000

Reviewer: Peter Yee
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-sipcore-status-unwanted-04
Reviewer: Peter Yee
Review Date: 2017-03-21
IETF LC End Date: 2017-03-21
IESG Telechat date: Not scheduled for a telechat

Summary: This draft specifies a SIP response code for the callee to
indicate that the call is unwanted.  It goes to great lengths to
specify what may be done as a result of sending this response code,
all the while mandating nothing.

The document has a couple of nits, but nothing seriously wrong. 
[Ready with nits]

Major issues: None

Minor issues: None

Nits/editorial comments: 

Page 4, 1st full paragraph, 2nd sentence: I can't parse this sentence
as written.  It appears to be a list, but then has a clause (starting
at "based on") that doesn't fit neatly in the sequence.  Perhaps
inserting "and" before "based" would help.  Append "as" after "well".

Page 5, Section 6, 2nd paragraph, 1st sentence: change "extract" to
"exact".


From nobody Tue Mar 21 22:10:25 2017
Return-Path: <jri@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 AF796129461 for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 22:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VaBzlu5BCViz for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 22:10:18 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5C1812944E for <ietf@ietf.org>; Tue, 21 Mar 2017 22:10:15 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id z204so58448526vkd.1 for <ietf@ietf.org>; Tue, 21 Mar 2017 22:10:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5Gm2jlSTFBRw+QETQ1oGEA0bzyEcP/oREwyeO7z1t+8=; b=F6RYfmt29GLe7A+S6p/TrlVfpFhHPQXRBdVkmylwAhymusm9jgzEinFjv1+8rZCXTX lGakX67QZAWi+oCaaKnxZu2v/1lLzHHBS0D4JsL6Au8Vf9CYMy1poS9WaPCF8rwInnOu kl4KeEDOSjHDJX+IhCyZNOJ/EPo7iNKes2Ct02G3fONzFXUIvV8d3CYLiw3JfEuIPQrJ s4zROaP1myX+Mm3x1VcmxavW5IBtKbMg09g2oJHeDo1zE+Qzu3Qqh0zBD8BM6zaz4Ccu sBf07zI/pZOTez17jRWjHTGFHvEdzCfAk+NwFSvZpKAAwzWtZSI3BkqInb4jZviwAxj9 BGmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5Gm2jlSTFBRw+QETQ1oGEA0bzyEcP/oREwyeO7z1t+8=; b=ArH/g4XX19mycMy4uljIjIJwdSp1Wo1m8WOYgQ5l2Rynzl5gZiWn1FMEUcyFGbqhNx w3Em0vw7b51bG+N55TaXoWRLM9akh+Hq9zaQeSFHy6PTJeAU/xz6hbGIs2JxWdvhzdvZ wFpx5b84C64+cdIBNcqMbMVL8X1dNZH+G6MY3LgYJZ0GQgusytAo4suQsR/9QiY0gfLU 2o1lfHv6tIzfbEuGttlcJRZn8QbNdzsinnl6908filD7QFzYo820VIcqUCOAC68nOgpY VfLHTpahP1lhtyJO80O8rjtzFkRJH/J5B6fnnEGRioxXSUoP3pHkdD4UmYl70NBEkxgr GHUw==
X-Gm-Message-State: AFeK/H3kDyb6uETQA/5/8XBwzl8s416KAfa0KTO3dnxPTlD7dWwpchDzs8te/jmirmFMM87lCpglNXkNjJnosnXx
X-Received: by 10.176.74.155 with SMTP id s27mr14109789uae.143.1490159414417;  Tue, 21 Mar 2017 22:10:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.15.6 with HTTP; Tue, 21 Mar 2017 22:10:13 -0700 (PDT)
In-Reply-To: <F1C1D5B02EA3FA4A8AF54C86BA4F325CEB8479@DGGEMA501-MBS.china.huawei.com>
References: <149008338604.24977.6083947817909590331@ietfa.amsl.com> <F1C1D5B02EA3FA4A8AF54C86BA4F325CEB8479@DGGEMA501-MBS.china.huawei.com>
From: Jana Iyengar <jri@google.com>
Date: Tue, 21 Mar 2017 22:10:13 -0700
Message-ID: <CAGD1bZZQYU7opPhVt6o_=h5Q7rYMKe159m50V=9NGaQjFgYAxA@mail.gmail.com>
Subject: Re: [aqm] Review of draft-ietf-aqm-codel-07
To: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
Cc: Yoav Nir <ynir.ietf@gmail.com>, "secdir@ietf.org" <secdir@ietf.org>,  "draft-ietf-aqm-codel.all@ietf.org" <draft-ietf-aqm-codel.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "aqm@ietf.org" <aqm@ietf.org>
Content-Type: multipart/alternative; boundary=f403045ef6548e677b054b4ac607
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gkhYV-p3YkUQ9t0xACFa5t5mp1g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 05:10:20 -0000

--f403045ef6548e677b054b4ac607
Content-Type: text/plain; charset=UTF-8

Thanks Yoav, Emma. I can try to move Sec 5 before Sec 3, if that helps.
Yoav: What do you suggest we add for security considerations?

Thanks for the reviews!
- jana


On Tue, Mar 21, 2017 at 7:04 PM, Gengxuesong (Geng Xuesong) <
gengxuesong@huawei.com> wrote:

> Hi,
>
> I can not agree more on this.
> It is well written, but I really think I can get the point of the draft
> faster if I can read the section 5 before section 3.
>
>
> Best Regards,
> Emma (Xuesong)
>
> -----Original Message-----
> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Yoav Nir
> Sent: Tuesday, March 21, 2017 4:03 PM
> To: secdir@ietf.org
> Cc: draft-ietf-aqm-codel.all@ietf.org; ietf@ietf.org; aqm@ietf.org
> Subject: [aqm] Review of draft-ietf-aqm-codel-07
>
> Reviewer: Yoav Nir
> Review result: Has Nits
>
> Hi,
>
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the IESG.
> These comments were written primarily for the benefit of the security area
> directors.  Document editors and WG chairs should treat these comments just
> like any other last call comments.
>
> The document describes the CoDel (controlled delay) framework for reducing
> bufferbloat. It does a good job of describing the problem, outlining the
> solution and providing both a description of the algorithm (including
> pseudo-code) and linking to real world implementations.
>
> Two nits:
>
> 1. A lot of terms are used long before they are explained, such as
> Estimator, Sojourn time, Interval (BTW: if this is a moving interval the
> spec should probably say so). When reading sections 3 I concluded that the
> document was aimed at peopel who already knew all these terms and didn't
> need definitions, but then reading section 5 gave me a lot of a-ha moments
> about what I had read previously.
>
> 2. The security considerations section says "There are no specific
> security exposures associated with CoDel."  CoDel is about dropping
> packets, so immediately I have to think how I could subvert a router
> running CoDel to drop other people's packets. Perhaps it is fine to say
> that there are no known attacks on CoDel and no steps necessary to mitigate
> such, but I think it's tempting fate and hackers to say that CoDel has no
> security exposures.
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>

--f403045ef6548e677b054b4ac607
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Yoav, Emma. I can try to move Sec 5 before Sec 3, i=
f that helps.<div>Yoav: What do you suggest we add for security considerati=
ons?<br></div><div><br></div><div>Thanks for the reviews!</div><div>- jana<=
/div><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Tue, Mar 21, 2017 at 7:04 PM, Gengxuesong (Geng Xuesong) <span =
dir=3D"ltr">&lt;<a href=3D"mailto:gengxuesong@huawei.com" target=3D"_blank"=
>gengxuesong@huawei.com</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">Hi,<br>
<br>
I can not agree more on this.<br>
It is well written, but I really think I can get the point of the draft fas=
ter if I can read the section 5 before section 3.<br>
<br>
<br>
Best Regards,<br>
Emma (Xuesong)<br>
<div><div class=3D"h5"><br>
-----Original Message-----<br>
From: aqm [mailto:<a href=3D"mailto:aqm-bounces@ietf.org">aqm-bounces@ietf.=
org</a>] On Behalf Of Yoav Nir<br>
Sent: Tuesday, March 21, 2017 4:03 PM<br>
To: <a href=3D"mailto:secdir@ietf.org">secdir@ietf.org</a><br>
Cc: <a href=3D"mailto:draft-ietf-aqm-codel.all@ietf.org">draft-ietf-aqm-cod=
el.all@ietf.<wbr>org</a>; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a=
>; <a href=3D"mailto:aqm@ietf.org">aqm@ietf.org</a><br>
Subject: [aqm] Review of draft-ietf-aqm-codel-07<br>
<br>
Reviewer: Yoav Nir<br>
Review result: Has Nits<br>
<br>
Hi,<br>
<br>
I have reviewed this document as part of the security directorate&#39;s ong=
oing effort to review all IETF documents being processed by the IESG.=C2=A0=
 These comments were written primarily for the benefit of the security area=
 directors.=C2=A0 Document editors and WG chairs should treat these comment=
s just like any other last call comments.<br>
<br>
The document describes the CoDel (controlled delay) framework for reducing =
bufferbloat. It does a good job of describing the problem, outlining the so=
lution and providing both a description of the algorithm (including pseudo-=
code) and linking to real world implementations.<br>
<br>
Two nits:<br>
<br>
1. A lot of terms are used long before they are explained, such as Estimato=
r, Sojourn time, Interval (BTW: if this is a moving interval the spec shoul=
d probably say so). When reading sections 3 I concluded that the document w=
as aimed at peopel who already knew all these terms and didn&#39;t need def=
initions, but then reading section 5 gave me a lot of a-ha moments about wh=
at I had read previously.<br>
<br>
2. The security considerations section says &quot;There are no specific sec=
urity exposures associated with CoDel.&quot;=C2=A0 CoDel is about dropping =
packets, so immediately I have to think how I could subvert a router runnin=
g CoDel to drop other people&#39;s packets. Perhaps it is fine to say that =
there are no known attacks on CoDel and no steps necessary to mitigate such=
, but I think it&#39;s tempting fate and hackers to say that CoDel has no s=
ecurity exposures.<br>
<br>
</div></div>______________________________<wbr>_________________<br>
aqm mailing list<br>
<a href=3D"mailto:aqm@ietf.org">aqm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/aqm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/aqm</a><br>
</blockquote></div><br></div>

--f403045ef6548e677b054b4ac607--


From nobody Tue Mar 21 22:15:40 2017
Return-Path: <ynir.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 43E45126B7F; Tue, 21 Mar 2017 22:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PTrnNTS0L5OA; Tue, 21 Mar 2017 22:15:31 -0700 (PDT)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AB7B1242F5; Tue, 21 Mar 2017 22:15:31 -0700 (PDT)
Received: by mail-wm0-x229.google.com with SMTP id n11so26834026wma.0; Tue, 21 Mar 2017 22:15:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=lo9cWTZMulBLNJJsPrLhryDEhcoNvKm8b8lmD+hyHxg=; b=LcoMAD7nI9axHFd2bJmMgBoutPMxk+0BRW1SpQgMJ/tpA+JDd0fehwQ/O+mj4LVAhr imlbctRM8GZzP5Jsj4YOJx7YoFEGztLIbWqmL/AM7jtOjbckB4/xveSiyLKDUMjGy7IN eOQzO9SpYxvlQNI6FhKRZevyRMLtNuFm9TNjSMPQ0mEFzWFQoAZVtMsFEkaA1uPBDnB0 wWMRE42ls5pxrGNl5Jij3TAz9EzOs8ThkGogaLrHYU0rymaZ+Bk8IdbJOI7+6TEf5OQ8 SBQlCL0OHyAm4oiP48JENuNLY6r7DxXxX0P1Mn1gz+QsjiCIraerzgsLZ3auVQof5/27 6q0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=lo9cWTZMulBLNJJsPrLhryDEhcoNvKm8b8lmD+hyHxg=; b=snVewC/cZhygS8vUdjnjegbQojeiBdITGp5RTYJM4oO1GPWFchvI/FUSzvQdnfvDWf 5GdoN1I2zJbPtRlKMhZYRXy3YmbAQ11D2YhQxWqDp7v90Ll4VUKkuPTikrXdrZF/unc2 TzIZVIh3Ibqfv3beGehjB/2ey+J9Pfu56XEpPmEuS9yiTmFPv/zqEEJD8MM/V8fKxv67 FBdeiPL9RuamV2ws/AMC87OvyXefoHwCOA/LwqI1m3CjcIYs09aMKnoM/2uup1ZRphZy ClzHyEbg/tAF7mfqhLJFUlYLh17gLTWxd3pNs49gmJs/R2QwMbml1JG/RCDKHjn6e0r1 nHOw==
X-Gm-Message-State: AFeK/H04eV41kUhy8RGzHGGkSLOziWkPZxq4sowndOsu6m2N/vd+JQtxzXGUSGS6aE0XsA==
X-Received: by 10.28.55.138 with SMTP id e132mr5599740wma.6.1490159729938; Tue, 21 Mar 2017 22:15:29 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id u81sm328401wrb.67.2017.03.21.22.15.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Mar 2017 22:15:29 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <3C9CECA3-D84E-4471-B4AF-EA1C5061CC90@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A6D557CA-D55A-4A0A-8AE8-B5A59B241ECD"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [aqm] Review of draft-ietf-aqm-codel-07
Date: Wed, 22 Mar 2017 07:15:26 +0200
In-Reply-To: <CAGD1bZZQYU7opPhVt6o_=h5Q7rYMKe159m50V=9NGaQjFgYAxA@mail.gmail.com>
Cc: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, "secdir@ietf.org" <secdir@ietf.org>, "draft-ietf-aqm-codel.all@ietf.org" <draft-ietf-aqm-codel.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "aqm@ietf.org" <aqm@ietf.org>
To: Jana Iyengar <jri@google.com>
References: <149008338604.24977.6083947817909590331@ietfa.amsl.com> <F1C1D5B02EA3FA4A8AF54C86BA4F325CEB8479@DGGEMA501-MBS.china.huawei.com> <CAGD1bZZQYU7opPhVt6o_=h5Q7rYMKe159m50V=9NGaQjFgYAxA@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XMrY9GgGOGkKRJvPplsiQTKmJyE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 05:15:33 -0000

--Apple-Mail=_A6D557CA-D55A-4A0A-8AE8-B5A59B241ECD
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


> On 22 Mar 2017, at 7:10, Jana Iyengar <jri@google.com> wrote:
> 
> Thanks Yoav, Emma. I can try to move Sec 5 before Sec 3, if that helps.

Thanks. I think it will.

> Yoav: What do you suggest we add for security considerations?

How about:

OLD:
   There are no specific security exposures associated with CoDel

NEW:
   There are no known security exposures associated with CoDel at this time.

Yoav


--Apple-Mail=_A6D557CA-D55A-4A0A-8AE8-B5A59B241ECD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJY0ghvAAoJELhJCxUKWMyZ0qMIAMFaV/1VwjJx6+zZLL/Zr+Lq
1X1Mt70dc0cDK1/l/iHQvo0RFnLCD9sJUVoQzv0LBbvV5FNy6R96KwpoR4sRMjXD
+z7YF7+LBCqAdAo/z1091bJ6h+LDwxbn8aZf7pqnxC6NkWEE1IR4B8BJbOOFy8yA
2lKP45G0tet6pvIrFM5qP4usPxmSzi0dw0+py/9R9jBQN2bTdtLAO2AqOm2WroHU
UY7nVn9P/hZw5At5qH9dPMTACSE6gt+uuQVw9FLHw6SDwQb37M0+HPE6k1JLHPVI
/ZVA0ni+1m6feOJtlyKTyp2vKwvdbHNqjV9QNSBizWDxJhEaDYJl5AodVBS8e5w=
=+3oo
-----END PGP SIGNATURE-----

--Apple-Mail=_A6D557CA-D55A-4A0A-8AE8-B5A59B241ECD--


From nobody Tue Mar 21 22:20:51 2017
Return-Path: <jri@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 2913B12943C for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 22:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fP63MakGlr6l for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2017 22:20:47 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66964124281 for <ietf@ietf.org>; Tue, 21 Mar 2017 22:20:47 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id r69so5392879vke.2 for <ietf@ietf.org>; Tue, 21 Mar 2017 22:20:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FEYvf2mRafRqOtc+czZVd9CIIrv/29TN0hWnEjVyAtw=; b=e8QvGkl1NvLOY1pZEzz64fc4Xxz936JCdYtsTScb0a3yWWtkX0no3PzXg9tJztfFLJ 8A/+JKPjyx3t5Sc4VKFegwIydDbf9fbYag2KOK4W4ATPeKMDE4QENb29u7mGh6WDlawA TQANsNEIl9jgzV6Z6U//4aFyXnkuod478UF4KihY+Ajfad7qOrZRc2Z6JBSiBGghSnku Wn3bFlWrAHdPte3FtJ3KCOLGbSX+lhin+hRPEMSbCSu6ccLZQS4CoCEnWAuG7D1Ju/Wy yjj26hnr5LlPIQDPrDO7p5gbBv4mJFTu+oIHinqmoZP1zqrJSojzASchyxbnQHU4+7pE bKIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FEYvf2mRafRqOtc+czZVd9CIIrv/29TN0hWnEjVyAtw=; b=Pf2wJ7fn3aFTXPAIAImVYqCmW/A1la/CRBz77MfSsv4k7jXsKj0CvIleRTr88wCRFU C3mh8t6h1b2BUYPBGyQ7aOa5LKcfLSFQJBd5D6CrMTBnMc86isq/NFzvSKG/4bEVr3IY xB8MlOHASpUUaGqb7ZaDdBXLh/g6UAf97LYpOWZfWNmef/4umLv1qjprv7n9cj9EUTQF IdO9mA+QkUQNawFYWf0oVfnCyU2BzFs5HxCBHwcLeb6BFsMcyakgGWGXBt7uOcC2TqPP lYVn54OdoxMPHLzAFh+UYcs9IzAtx1Lmc/FCkXdcluuyHOtew/bNnWwgSFSAgo2BXXWw 0ELg==
X-Gm-Message-State: AFeK/H2c+4rNd0/bEsZIbIZy1iZ2PpTGK/HhwuedvgI2nkJ7f1/WAqLlxbSwxIaRbBLPkhZxbFqRFvD3tx7SDAw9
X-Received: by 10.176.16.5 with SMTP id f5mr13978324uab.13.1490160046244; Tue, 21 Mar 2017 22:20:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.15.6 with HTTP; Tue, 21 Mar 2017 22:20:45 -0700 (PDT)
In-Reply-To: <3C9CECA3-D84E-4471-B4AF-EA1C5061CC90@gmail.com>
References: <149008338604.24977.6083947817909590331@ietfa.amsl.com> <F1C1D5B02EA3FA4A8AF54C86BA4F325CEB8479@DGGEMA501-MBS.china.huawei.com> <CAGD1bZZQYU7opPhVt6o_=h5Q7rYMKe159m50V=9NGaQjFgYAxA@mail.gmail.com> <3C9CECA3-D84E-4471-B4AF-EA1C5061CC90@gmail.com>
From: Jana Iyengar <jri@google.com>
Date: Tue, 21 Mar 2017 22:20:45 -0700
Message-ID: <CAGD1bZZ18aQ68DEgXe=5nqp_yQngwMEqLAbXWdTiL6fyKNwOcw@mail.gmail.com>
Subject: Re: [aqm] Review of draft-ietf-aqm-codel-07
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, "secdir@ietf.org" <secdir@ietf.org>,  "draft-ietf-aqm-codel.all@ietf.org" <draft-ietf-aqm-codel.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "aqm@ietf.org" <aqm@ietf.org>
Content-Type: multipart/alternative; boundary=f403045e345e37540b054b4aec50
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-uIczvs1rFqp2TXcKpL6AqnLnJM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 05:20:49 -0000

--f403045e345e37540b054b4aec50
Content-Type: text/plain; charset=UTF-8

SGTM. Thanks!

On Tue, Mar 21, 2017 at 10:15 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:

>
> > On 22 Mar 2017, at 7:10, Jana Iyengar <jri@google.com> wrote:
> >
> > Thanks Yoav, Emma. I can try to move Sec 5 before Sec 3, if that helps.
>
> Thanks. I think it will.
>
> > Yoav: What do you suggest we add for security considerations?
>
> How about:
>
> OLD:
>    There are no specific security exposures associated with CoDel
>
> NEW:
>    There are no known security exposures associated with CoDel at this
> time.
>
> Yoav
>
>

--f403045e345e37540b054b4aec50
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">SGTM. Thanks!</div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Tue, Mar 21, 2017 at 10:15 PM, Yoav Nir <span dir=3D"=
ltr">&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf=
@gmail.com</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"><span cl=
ass=3D""><br>
&gt; On 22 Mar 2017, at 7:10, Jana Iyengar &lt;<a href=3D"mailto:jri@google=
.com">jri@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Thanks Yoav, Emma. I can try to move Sec 5 before Sec 3, if that helps=
.<br>
<br>
</span>Thanks. I think it will.<br>
<span class=3D""><br>
&gt; Yoav: What do you suggest we add for security considerations?<br>
<br>
</span>How about:<br>
<br>
OLD:<br>
<span class=3D"">=C2=A0 =C2=A0There are no specific security exposures asso=
ciated with CoDel<br>
<br>
</span>NEW:<br>
=C2=A0 =C2=A0There are no known security exposures associated with CoDel at=
 this time.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Yoav<br>
<br>
</font></span></blockquote></div><br></div>

--f403045e345e37540b054b4aec50--


From nobody Wed Mar 22 09:26:22 2017
Return-Path: <paul.kyzivat@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 68B42129A83 for <ietf@ietfa.amsl.com>; Wed, 22 Mar 2017 09:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VShfskDZNGCn for <ietf@ietfa.amsl.com>; Wed, 22 Mar 2017 09:26:18 -0700 (PDT)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C424129A37 for <ietf@ietf.org>; Wed, 22 Mar 2017 09:26:17 -0700 (PDT)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-02v.sys.comcast.net with SMTP id qj4ZcQqLWBHfPqj5UclW3e; Wed, 22 Mar 2017 16:26:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1490199976; bh=aYRxnsyEF9cRJLTtv2gUK9aOnob8SQWT9Tk+wh7RzdE=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=AVKIad1hZnMVWxglb8eymm/DzzMtoKP99JHu7Op1gsZaB7BwfpSH/yNBl+8UJJnnH al5Ku/F1nrGmyyM7sz5XqMIrHSiDr8FW8z2A7bjqwuFuVbyNZYpzJoQck+nOpOum4h uuO36hf6hDxvHNmeJKSLRHnueaiE0IzIBg0ClxwUFaKDjgPWlz1UtMID4SKHjoDzRM VwsDS4wHptOQ07bAUGO3a5MpMSPNM+TZl9Aidh0kWgyMaHDtQdNFf5/RiOxhWSltk2 0Yln1FfqnNvzWiy+99IiTOYNhxqjzyqqzyNDbYgn8egYZFss+moJRLYK+mOklJijhw ohcliN+dCQZjg==
Received: from [192.168.1.110] ([24.62.227.142]) by resomta-ch2-20v.sys.comcast.net with SMTP id qj5TcQ2mKNOhWqj5UcK0XL; Wed, 22 Mar 2017 16:26:16 +0000
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
To: Denis Ovsienko <denis@ovsienko.info>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <15aeb1be62a.11b35bf8267637.2121189919710903185@ovsienko.info> <d0768a84-410a-0acb-fd1a-b8f666eff18f@comcast.net> <15af365683e.dcf5ec8274777.6641471719326234265@ovsienko.info>
Cc: "ietf@ietf.org" <ietf@ietf.org>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Message-ID: <8ab19425-123f-4a2b-5c7e-7b39366e59e2@comcast.net>
Date: Wed, 22 Mar 2017 12:26:15 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <15af365683e.dcf5ec8274777.6641471719326234265@ovsienko.info>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfLqCV5cJU6K10aZzpFpK4Q01ErTMUjpitNC5XXfZgyREzNrm50oYIe6jBu6IGJiW+zzyyt1irPIlTopSUkw+aW18vztH0nVJyj81G6LSiKO6YOEvbZTz Cn8rorSSlYhNOYh7XTPHvAdGimOdVEnnQxwk+AtyC6WNY0AVjUS/dNAO4JJ/oWjessUbK2/JcfUNISvjmJ5vPdQobwE1u6Y3D0o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8H2lMihTD2AEdJMjfQjVvy1aE4Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 16:26:20 -0000

On 3/21/17 8:23 PM, Denis Ovsienko wrote:
> ---- On Tue, 21 Mar 2017 02:38:33 +0000 Paul Kyzivat  wrote ----
>> Denis,
>>
>> Do you have any expertise with SIP? I don't recall ever seeing your name
>> before. Your comments exhibit a profound misunderstanding of it.
>
> Pete, I am happy to admit I don't have any meaningful expertise with SIP and it is quite likely I misunderstand important things about it as an engineer.
>
> The point I am making is one of an end user: the document is an ethical failure already, in its present edition it is not appropriate for the large, non-technical user base of SIP.
>
> The Internet where software makes it more likely for people to go wrong is worse, not better. "The goal of the IETF is to make the Internet work better." So now is time to stop and think instead of rushing the document through.
>
>> SIP response codes are almost never displayed to end users. For that
>> matter they aren't even typically exposed to *operators* of SIP-based
>> systems. Only when people are diagnosing signaling problems within the
>> network are they visible. So the basic premise of your objection is
>> ill-founded.
>
> This is similar to how HTTP response codes were originally intended; today's reality is that quite a fraction of Earth population can tell what HTTP 404 means.

I don't believe I have *ever* seen a sip response code displayed on a 
user interface.

	Thanks,
	Paul


From nobody Wed Mar 22 11:37:30 2017
Return-Path: <fluffy@iii.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 45646129BF3 for <ietf@ietfa.amsl.com>; Wed, 22 Mar 2017 11:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.697
X-Spam-Level: 
X-Spam-Status: No, score=-4.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DT7S8pdf8jep for <ietf@ietfa.amsl.com>; Wed, 22 Mar 2017 11:37:22 -0700 (PDT)
Received: from smtp118.iad3a.emailsrvr.com (smtp118.iad3a.emailsrvr.com [173.203.187.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A95251294E1 for <ietf@ietf.org>; Wed, 22 Mar 2017 11:37:14 -0700 (PDT)
Received: from smtp23.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp23.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id C6C7E25BD3; Wed, 22 Mar 2017 14:37:09 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp23.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 7A98F25BEC;  Wed, 22 Mar 2017 14:37:09 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.61] (S01065475d0f7dcd1.cg.shawcable.net [70.75.17.123]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Wed, 22 Mar 2017 14:37:09 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <8ab19425-123f-4a2b-5c7e-7b39366e59e2@comcast.net>
Date: Wed, 22 Mar 2017 12:37:08 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <631C7A50-BE80-4C45-A1EC-A008797027AA@iii.ca>
References: <148893258669.17675.7013326933036466908.idtracker@ietfa.amsl.com> <15aeb1be62a.11b35bf8267637.2121189919710903185@ovsienko.info> <d0768a84-410a-0acb-fd1a-b8f666eff18f@comcast.net> <15af365683e.dcf5ec8274777.6641471719326234265@ovsienko.info> <8ab19425-123f-4a2b-5c7e-7b39366e59e2@comcast.net>
To: "ietf@ietf.org" <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M62paEtoXDPfws28_esnV2TSE-s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 18:37:25 -0000

FWIW ... I think the best thing would just be to allocate the next 6xx =
IANA code instead of using 666. The only reason 666 is funny is exactly =
the reason some people might not ind it funny. Just take the high road =
and make this discussions go away.=20




From nobody Wed Mar 22 11:37:46 2017
Return-Path: <Glenn.Deen@nbcuni.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5C21294E1; Wed, 22 Mar 2017 11:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZdKGfvslaCla; Wed, 22 Mar 2017 11:37:24 -0700 (PDT)
Received: from mx0a-00176a04.pphosted.com (mx0a-00176a04.pphosted.com [67.231.149.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4485D129BCB; Wed, 22 Mar 2017 11:37:22 -0700 (PDT)
Received: from pps.filterd (m0048276.ppops.net [127.0.0.1]) by m0048276.ppops.net-00176a04. (8.16.0.20/8.16.0.20) with SMTP id v2MIRqO3045204; Wed, 22 Mar 2017 14:37:20 -0400
Received: from usaoamgip001.mail.tfayd.com ([173.213.212.135]) by m0048276.ppops.net-00176a04. with ESMTP id 29ba17dpgp-1 (version=TLSv1.2 cipher=RC4-SHA bits=128 verify=NOT); Wed, 22 Mar 2017 14:37:19 -0400
Received: from unknown (HELO USUSHECWP007.mail.tfayd.com) ([10.40.78.204]) by usaoamgip001.mail.tfayd.com with ESMTP; 22 Mar 2017 14:37:17 -0400
Received: from USUSHEMWP012.mail.tfayd.com ([169.254.4.151]) by USUSHECWP007.mail.tfayd.com ([3.156.41.61]) with mapi id 14.03.0266.001; Wed, 22 Mar 2017 11:37:16 -0700
From: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
To: "98attendees@ietf.org" <98attendees@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: FW: Video Streaming Bar BoF @ IETF98
Thread-Topic: Video Streaming Bar BoF @ IETF98
Thread-Index: AQHSndU57AttaXTq/02muQPDHsLP+aGhOviA
Date: Wed, 22 Mar 2017 18:37:16 +0000
Message-ID: <D4F810F1.D1665%glenn.deen@nbcuni.com>
References: <D4EF03A1.D0EA4%glenn.deen@nbcuni.com>
In-Reply-To: <D4EF03A1.D0EA4%glenn.deen@nbcuni.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.3.150624
x-originating-ip: [10.23.94.151]
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
Content-Type: multipart/alternative; boundary="_000_D4F810F1D1665glenndeennbcunicom_"
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-22_16:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703220160
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zbcI3qLqi_3p80QgZ69jmcuOd7c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 18:37:26 -0000

--_000_D4F810F1D1665glenndeennbcunicom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpJIHdhbnQgdG8gaW52aXRlIGFueW9uZSB3aG8gaXMgaW50ZXJlc3RlZCBpbiBJbnRlcm5ldCBW
aWRlbyBTdHJlYW1pbmcgdG8gYSBCYXIgQm9GIG9uIEludGVybmV0IFZpZGVvIFN0cmVhbWluZyB0
byBiZSBoZWxkIGF0IElFVEY5OC4NCg0KVGltZTogICAgIE1vbmRheSBPY3QgMjd0aCAgYXQgNjoz
MC03OjMwcG0gQ0RUDQpXaGVyZTogIENvbHVtYnVzIFRhcCBhdCB0aGUgRmFpcm1vbnQgKHRoaXMg
aXMgdGhlIG92ZXJmbG93IGhvdGVsIGFuZCBpcyBjb25uZWN0ZWQgdG8gdGhlIHZlbnVlIHZpYSB0
aGUgdW5kZXJncm91bmQgbWFsbCkuDQoNClRoaXMgaXMgb3BlbiB0byBhbnlvbmUgaW50ZXJlc3Rl
ZCBzbyBwbGVhc2UgZmVlbCBmcmVlIHRvIHBhc3MgdGhpcyBpbnZpdGUgYWxvbmcuICBJJ20gdG9s
ZCB0aGF0IHRoZSBDb2x1bWJ1cyBUYXAgYWxzbyBoYXMgYSBmaW5lIHNlbGVjdGlvbiBvZiBiZWVy
IQ0KDQpUaGlzIGlzIGEgbm9uLWhvc3RlZCBldmVudCwgbWVhbmluZyBubyBmcmVlIGJlZXIsIGJ1
dCB0aGVyZSB3aWxsIGJlIGdyZWF0IGRpc2N1c3Npb24gb2YgSW50ZXJuZXQgdmlkZW8hDQoNCnJl
Z2FyZHMNCkdsZW5uIERlZW4NCg0KLS0tLS0tDQoNClRvcGljOiBWaWRlbyBTdHJlYW1pbmcgZVh0
ZW5zaW9ucyAoVi1TWCkNCg0KRGVzY3JpcHRpb246DQoNCkR1ZSB0byBpdHMgc2l6ZSBhbmQgc2Vu
c2l0aXZpdHkgdG8gbmV0d29yayBjb25kaXRpb25zLCB0aGUgdHJhbnNwb3J0IG9mIHZpZGVvIG92
ZXIgdGhlIEludGVybmV0IGhhcyBoaWdobGlnaHRlZCBhIHNpZ25pZmljYW50IHNjYWxhYmlsaXR5
IHByb2JsZW0gZm9yIHRoZSBJbnRlcm5ldC4gIE9uIHRoZSBiZWxpZWYgdGhhdCBhZGRyZXNzaW5n
IHRoaXMgc2NhbGFiaWxpdHkgcHJvYmxlbSByZXF1aXJlcyBiZXR0ZXIgaW50ZWdyYXRpb24gYmV0
d2VlbiBhcHBsaWNhdGlvbiB0cmFuc3BvcnQgYW5kIG5ldHdvcmtpbmcgdGVjaG5vbG9naWVzIGFu
ZCBsZXZlcmFnaW5nIElQdjYsIHRoaXMgQmFyIEJPRiB3aWxsIHNvbGljaXQgZXhwZXJpZW5jZXMg
b2YgdGhlIHNjYWxpbmcgcHJvYmxlbSBhcyBwZXJjZWl2ZWQgZnJvbSBkaWZmZXJlbnQgcGFydHMg
b2YgdGhlIGluZHVzdHJ5IChuZXR3b3JrLCBwcm9kdWNlciwgdmVuZG9ycykuDQoNClZpZGVvIGlz
IHdpdGhvdXQgcml2YWwgdGhlIHRvcCB1c2Ugb2YgSW50ZXJuZXQgYmFuZHdpZHRoLCBhbmQgaXRz
IGV2ZXIgZ3Jvd2luZyBkZW1hbmQgZm9yIG1vcmUgYmFuZHdpZHRoIGVhc2lseSBvdXQgcGFjZXMg
dGhlIG5ldyBjYXBhY2l0eSBiZWluZyBhZGRlZCBib3RoIGdsb2JhbGx5IGFuZCByZWdpb25hbGx5
IHdpdGggbm8gbGV0IHVwIGluIHNpZ2h0LiAgIFVzZXJzIGFyZSBmcnVzdHJhdGVkIGJ5IHF1YWxp
dHksIGJ1ZmZlcmluZywgYW5kIHN0dXR0ZXJpbmcgcHJvYmxlbXMuIFZpZGVvIHByb3ZpZGVycyBh
bmQgYWNjZXNzIG5ldHdvcmtzIGFyZSBpbnZlc3RpbmcgaGVhdmlseSB0byBrZWVwIHVwIHdpdGgg
ZGVtYW5kLiAgU2lnbmlmaWNhbnQgd29yayBoYXMgYmUgZG9uZSBhdCB0aGUgYXBwbGljYXRpb24g
bGF5ZXIgcHJvZHVjaW5nIG1vcmUgZWZmaWNpZW50IGNvZGVjcyBhbmQgaW5ub3ZhdGl2ZSBhZGFw
dGl2ZSBiaXRyYXRlIHRyYW5zcG9ydHMgbGlrZSBNUEVHLURBU0guICBUaGVzZSBhY2Nlc3MgaW52
ZXN0bWVudHMgYW5kIGFwcGxpY2F0aW9uIGxheWVyIHdvcmsgaGF2ZSBoZWxwZWQgYnV0IHRoZXkg
YWxvbmUgaGF2ZSBub3QgYmVlbiBlbm91Z2guDQoNCkEgdGFyZ2V0IG9mIGFueSBldmVudHVhbCB3
b3JrIGFuZCBwcm9kdWN0IGlzIHRvIGVuYWJsZSB2aWRlbyBhbmQgbmV0d29yayByb3V0aW5nIC8g
bWFuYWdlbWVudCB0byB3b3JrIG1vcmUgY29vcGVyYXRpdmVseSBhbmQgZWZmaWNpZW50bHkgdG8g
dHJhbnNwb3J0IHZpZGVvLiAgU3VjY2Vzc2Z1bCBhcHByb2FjaGVzIHdpbGwgbmVlZCB0byBkbyBz
byBpbiBhIGJhY2t3YXJkIGNvbXBhdGlibGUgd2F5cyB0byBwZXJtaXQgZXhpdGluZyBkZXZpY2Vz
IGFuZCBwbGF5ZXJzIHRvIHRha2UgYWR2YW50YWdlIG9mIHRoZSBpbXByb3ZlZCBuZXR3b3JrIGVm
ZmljaWVuY2llcy4NCg0KT25lIHByb3Bvc2VkIGFwcHJvYWNoIHRvIGRlYWxpbmcgd2l0aCBpc3N1
ZXMgd2FzIG91dGxpbmVkIGluIHRoZSBHbGFzcyB0byBHbGFzcyBJbnRlcm5ldCBFY29zeXN0ZW0g
Qm9GIHByb3Bvc2FsIOKAlCByZWxhdGVkIGRyYWZ0cyBhbmQgbWFpbGluZyBsaXN0IGluZm9ybWF0
aW9uIGlzIHByb3ZpZGVkIGJlbG93LiAgQSBkZW1vbnN0cmF0aW9uIG9mIEdHSUUgd2lsbCBiZSBw
cm92aWRlZCBkdXJpbmcgdGhlIEJvRiwgZm9yIGlsbHVzdHJhdGlvbiBwdXJwb3Nlcy4gIERpc2N1
c3Npb24gaXMgZXhwZWN0ZWQgYW5kIGVuY291cmFnZWQgdG8gcmFuZ2UgZnVydGhlciB0aGFuIHRo
ZSBzcGVjaWZpYyBHR0lFIHByb3Bvc2FsLg0KDQpUaGlzIHdpbGwgYmUgYW4gaW50ZXJhY3RpdmUg
ZGlzY3Vzc2lvbiBhbmQgd2UgZW5jb3VyYWdlIGFueW9uZSB3aXRoIGFuIGludGVyZXN0IGluIHRo
aXMgdG9waWMgdG8gY29tZSBhbmQgc2hhcmUgdGhlaXIgaWRlYXMuDQoNCg0KICAgIEFnZW5kYQ0K
SW50cm9kdWN0aW9uDQpDb250ZXh0IHNldHRpbmcgWzVtaW5dDQoNClJvdW5kdGFibGUgZGlzY3Vz
c2lvbiBvZiB0aGUgaXNzdWUocykgWzMwbWluXQ0KDQpEZW1vIG9mIEdHSUUgcHJvdG90eXBlIFsx
MG1pbl0NCg0KV2hlcmUgZnJvbSBoZXJlPyBbMTVtaW5dDQpQb3RlbnRpYWwgZm9yIElFVEYgd29y
ayDigJQgaXMgdGhlcmUgaW50ZXJlc3QgdG8gcHVyc3VlPw0KV29yayBmb3Igb3RoZXIgZ3JvdXBz
Pw0KDQoNCg0KICAgICAgICBNYWlsaW5nIExpc3Q6IOKAi2h0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vZ2dpZQ0KDQogICAgICAgIFJlbGV2YW50IGRyYWZ0czoNCiAgICAgICAg
ICAgIGRyYWZ0LWRlZW4tZGFpZ2xlLWdnaWUtMDIgOiAgR2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQg
RWNvc3lzdGVtIEludHJvZHVjdGlvbg0KICAgZHJhZnQtcm9zZS1kZWVuLWdnaWUtdXNlLWNhc2Vz
LTAwIDogR0dJRSBJbnRlcm5ldCBWaWRlbyBVc2UgQ2FzZXMNCiAgIGRyYWZ0LWRhaWdsZS1kZWVu
LWdnaWUtdXJpLXNuYXB0ci0wMCA6ICBHbGFzcyB0byBHbGFzcyBJbnRlcm5ldCBFY29zeXN0ZW0g
VVJJIGFuZCBTLU5BUFRSIFVzZQ0KICAgZHJhZnQtZGVlbi1uYWlrLWdnaWUtbWVuLW1wZWctZGFz
aC0wMCA6IFVzaW5nIE1lZGlhIEVuY29kaW5nIE5ldHdvcmtzIHRvIGFkZHJlc3MgTVBFRy1EQVNI
IHZpZGVvDQoNClRpbWU6ICAgICBNb25kYXkgT2N0IDI3dGggIGF0IDY6MzAtNzozMHBtIENEVA0K
V2hlcmU6ICBDb2x1bWJ1cyBUYXAgYXQgdGhlIEZhaXJtb250ICh0aGlzIGlzIHRoZSBvdmVyZmxv
dyBob3RlbCBhbmQgaXMgY29ubmVjdGVkIHRvIHRoZSB2ZW51ZSB2aWEgdGhlIHVuZGVyZ3JvdW5k
IG1hbGwpLg0KDQoNCg0K

--_000_D4F810F1D1665glenndeennbcunicom_
Content-Type: text/html; charset="utf-8"
Content-ID: <33869ECDCE02ED499379BCA1755EC467@NBCUNI.COM>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0i
d29yZC13cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQt
bGluZS1icmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQt
c2l6ZTogMTRweDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7Ij4NCjxkaXY+SSB3
YW50IHRvIGludml0ZSBhbnlvbmUgd2hvIGlzIGludGVyZXN0ZWQgaW4gSW50ZXJuZXQgVmlkZW8g
U3RyZWFtaW5nIHRvIGEgQmFyIEJvRiBvbiBJbnRlcm5ldCBWaWRlbyBTdHJlYW1pbmcgdG8gYmUg
aGVsZCBhdCBJRVRGOTguPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaW1lOiAmbmJz
cDsgJm5ic3A7IE1vbmRheSBPY3QgMjd0aCAmbmJzcDthdCA2OjMwLTc6MzBwbSBDRFQ8L2Rpdj4N
CjxkaXY+V2hlcmU6ICZuYnNwO0NvbHVtYnVzIFRhcCBhdCB0aGUgRmFpcm1vbnQgKHRoaXMgaXMg
dGhlIG92ZXJmbG93IGhvdGVsIGFuZCBpcyBjb25uZWN0ZWQgdG8gdGhlIHZlbnVlIHZpYSB0aGUg
dW5kZXJncm91bmQgbWFsbCkuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGlzIGlz
IG9wZW4gdG8gYW55b25lIGludGVyZXN0ZWQgc28gcGxlYXNlIGZlZWwgZnJlZSB0byBwYXNzIHRo
aXMgaW52aXRlIGFsb25nLiAmbmJzcDtJJ20gdG9sZCB0aGF0IHRoZSBDb2x1bWJ1cyBUYXAgYWxz
byBoYXMgYSBmaW5lIHNlbGVjdGlvbiBvZiBiZWVyISAmbmJzcDs8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9T
RUNUSU9OIj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJ3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7IC13ZWJr
aXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJyZWFrOiBhZnRlci13aGl0ZS1zcGFj
ZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAxNHB4OyBmb250LWZhbWlseTogQ2Fs
aWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5UaGlzIGlzIGEgbm9uLWhvc3RlZCBldmVudCwgbWVh
bmluZyBubyBmcmVlIGJlZXIsIGJ1dCB0aGVyZSB3aWxsIGJlIGdyZWF0IGRpc2N1c3Npb24gb2Yg
SW50ZXJuZXQgdmlkZW8hPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5yZWdhcmRzPC9k
aXY+DQo8ZGl2PkdsZW5uIERlZW48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pi0tLS0t
LTwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VG9waWM6IFZpZGVvIFN0cmVhbWluZyBl
WHRlbnNpb25zIChWLVNYKTwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+RGVzY3JpcHRp
b246ICZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+RHVlIHRvIGl0cyBzaXpl
IGFuZCBzZW5zaXRpdml0eSB0byBuZXR3b3JrIGNvbmRpdGlvbnMsIHRoZSB0cmFuc3BvcnQgb2Yg
dmlkZW8gb3ZlciB0aGUgSW50ZXJuZXQgaGFzIGhpZ2hsaWdodGVkIGEgc2lnbmlmaWNhbnQgc2Nh
bGFiaWxpdHkgcHJvYmxlbSBmb3IgdGhlIEludGVybmV0LiAmbmJzcDtPbiB0aGUgYmVsaWVmIHRo
YXQgYWRkcmVzc2luZyB0aGlzIHNjYWxhYmlsaXR5IHByb2JsZW0gcmVxdWlyZXMgYmV0dGVyIGlu
dGVncmF0aW9uIGJldHdlZW4NCiBhcHBsaWNhdGlvbiB0cmFuc3BvcnQgYW5kIG5ldHdvcmtpbmcg
dGVjaG5vbG9naWVzIGFuZCBsZXZlcmFnaW5nIElQdjYsIHRoaXMgQmFyIEJPRiB3aWxsIHNvbGlj
aXQgZXhwZXJpZW5jZXMgb2YgdGhlIHNjYWxpbmcgcHJvYmxlbSBhcyBwZXJjZWl2ZWQgZnJvbSBk
aWZmZXJlbnQgcGFydHMgb2YgdGhlIGluZHVzdHJ5IChuZXR3b3JrLCBwcm9kdWNlciwgdmVuZG9y
cykuICZuYnNwOyZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VmlkZW8gaXMg
d2l0aG91dCByaXZhbCB0aGUgdG9wIHVzZSBvZiBJbnRlcm5ldCBiYW5kd2lkdGgsIGFuZCBpdHMg
ZXZlciBncm93aW5nIGRlbWFuZCBmb3IgbW9yZSBiYW5kd2lkdGggZWFzaWx5IG91dCBwYWNlcyB0
aGUgbmV3IGNhcGFjaXR5IGJlaW5nIGFkZGVkIGJvdGggZ2xvYmFsbHkgYW5kIHJlZ2lvbmFsbHkg
d2l0aCBubyBsZXQgdXAgaW4gc2lnaHQuICZuYnNwOyBVc2VycyBhcmUgZnJ1c3RyYXRlZCBieSBx
dWFsaXR5LCBidWZmZXJpbmcsIGFuZA0KIHN0dXR0ZXJpbmcgcHJvYmxlbXMuIFZpZGVvIHByb3Zp
ZGVycyBhbmQgYWNjZXNzIG5ldHdvcmtzIGFyZSBpbnZlc3RpbmcgaGVhdmlseSB0byBrZWVwIHVw
IHdpdGggZGVtYW5kLiAmbmJzcDtTaWduaWZpY2FudCB3b3JrIGhhcyBiZSBkb25lIGF0IHRoZSBh
cHBsaWNhdGlvbiBsYXllciBwcm9kdWNpbmcgbW9yZSBlZmZpY2llbnQgY29kZWNzIGFuZCBpbm5v
dmF0aXZlIGFkYXB0aXZlIGJpdHJhdGUgdHJhbnNwb3J0cyBsaWtlIE1QRUctREFTSC4gJm5ic3A7
VGhlc2UNCiBhY2Nlc3MgaW52ZXN0bWVudHMgYW5kIGFwcGxpY2F0aW9uIGxheWVyIHdvcmsgaGF2
ZSBoZWxwZWQgYnV0IHRoZXkgYWxvbmUgaGF2ZSBub3QgYmVlbiBlbm91Z2guICZuYnNwOzwvZGl2
Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+QSB0YXJnZXQgb2YgYW55IGV2ZW50dWFsIHdvcmsg
YW5kIHByb2R1Y3QgaXMgdG8gZW5hYmxlIHZpZGVvIGFuZCBuZXR3b3JrIHJvdXRpbmcgLyBtYW5h
Z2VtZW50IHRvIHdvcmsgbW9yZSBjb29wZXJhdGl2ZWx5IGFuZCBlZmZpY2llbnRseSB0byB0cmFu
c3BvcnQgdmlkZW8uICZuYnNwO1N1Y2Nlc3NmdWwgYXBwcm9hY2hlcyB3aWxsIG5lZWQgdG8gZG8g
c28gaW4gYSBiYWNrd2FyZCBjb21wYXRpYmxlIHdheXMgdG8gcGVybWl0IGV4aXRpbmcgZGV2aWNl
cw0KIGFuZCBwbGF5ZXJzIHRvIHRha2UgYWR2YW50YWdlIG9mIHRoZSBpbXByb3ZlZCBuZXR3b3Jr
IGVmZmljaWVuY2llcy4gJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5PbmUg
cHJvcG9zZWQgYXBwcm9hY2ggdG8gZGVhbGluZyB3aXRoIGlzc3VlcyB3YXMgb3V0bGluZWQgaW4g
dGhlIEdsYXNzIHRvIEdsYXNzIEludGVybmV0IEVjb3N5c3RlbSBCb0YgcHJvcG9zYWwg4oCUIHJl
bGF0ZWQgZHJhZnRzIGFuZCBtYWlsaW5nIGxpc3QgaW5mb3JtYXRpb24gaXMgcHJvdmlkZWQgYmVs
b3cuICZuYnNwO0EgZGVtb25zdHJhdGlvbiBvZiBHR0lFIHdpbGwgYmUgcHJvdmlkZWQgZHVyaW5n
IHRoZSBCb0YsIGZvciBpbGx1c3RyYXRpb24NCiBwdXJwb3Nlcy4gJm5ic3A7RGlzY3Vzc2lvbiBp
cyBleHBlY3RlZCBhbmQgZW5jb3VyYWdlZCB0byByYW5nZSBmdXJ0aGVyIHRoYW4gdGhlIHNwZWNp
ZmljIEdHSUUgcHJvcG9zYWwuICZuYnNwOyAmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+
DQo8ZGl2PlRoaXMgd2lsbCBiZSBhbiBpbnRlcmFjdGl2ZSBkaXNjdXNzaW9uIGFuZCB3ZSBlbmNv
dXJhZ2UgYW55b25lIHdpdGggYW4gaW50ZXJlc3QgaW4gdGhpcyB0b3BpYyB0byBjb21lIGFuZCBz
aGFyZSB0aGVpciBpZGVhcy48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwv
ZGl2Pg0KPGRpdj4mbmJzcDsgJm5ic3A7IEFnZW5kYTwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0i
QXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5JbnRyb2R1Y3Rp
b248L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUt
c3BhY2U6cHJlIj48L3NwYW4+Q29udGV4dCBzZXR0aW5nIFs1bWluXTwvZGl2Pg0KPGRpdj48YnI+
DQo8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUt
c3BhY2U6cHJlIj48L3NwYW4+Um91bmR0YWJsZSBkaXNjdXNzaW9uIG9mIHRoZSBpc3N1ZShzKSBb
MzBtaW5dPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iQXBwbGUt
dGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5EZW1vIG9mIEdHSUUgcHJv
dG90eXBlIFsxMG1pbl08L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNz
PSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPldoZXJlIGZy
b20gaGVyZT8gWzE1bWluXTwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4i
IHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5Qb3RlbnRpYWwgZm9yIElFVEYgd29yayDi
gJQgaXMgdGhlcmUgaW50ZXJlc3QgdG8gcHVyc3VlPzwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0i
QXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5Xb3JrIGZvciBv
dGhlciBncm91cHM/PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3Bh
Y2U6cHJlIj48L3NwYW4+PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4mbmJzcDs8L2Rp
dj4NCjxkaXY+Jm5ic3A7ICZuYnNwOyZuYnNwOzwvZGl2Pg0KPGRpdj4mbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgTWFpbGluZyBMaXN0OiDigIs8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2dnaWUiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vZ2dpZTwvYT48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBSZWxldmFudCBkcmFmdHM6PC9kaXY+DQo8ZGl2PiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGRyYWZ0LWRlZW4tZGFpZ2xlLWdnaWUtMDIg
OiAmbmJzcDtHbGFzcyB0byBHbGFzcyBJbnRlcm5ldCBFY29zeXN0ZW0gSW50cm9kdWN0aW9uPC9k
aXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNl
OnByZSI+PC9zcGFuPiZuYnNwOyAmbmJzcDtkcmFmdC1yb3NlLWRlZW4tZ2dpZS11c2UtY2FzZXMt
MDAgOiBHR0lFIEludGVybmV0IFZpZGVvIFVzZSBDYXNlczxzcGFuIGNsYXNzPSJBcHBsZS10YWIt
c3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPjwvZGl2Pg0KPGRpdj48c3BhbiBj
bGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4mbmJz
cDsgJm5ic3A7ZHJhZnQtZGFpZ2xlLWRlZW4tZ2dpZS11cmktc25hcHRyLTAwIDogJm5ic3A7R2xh
c3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIFVSSSBhbmQgUy1OQVBUUiBVc2U8L2Rpdj4N
CjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJl
Ij48L3NwYW4+Jm5ic3A7ICZuYnNwO2RyYWZ0LWRlZW4tbmFpay1nZ2llLW1lbi1tcGVnLWRhc2gt
MDAgOiBVc2luZyBNZWRpYSBFbmNvZGluZyBOZXR3b3JrcyB0byBhZGRyZXNzIE1QRUctREFTSCB2
aWRlbyZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2PlRpbWU6ICZu
YnNwOyAmbmJzcDsgTW9uZGF5IE9jdCAyN3RoICZuYnNwO2F0IDY6MzAtNzozMHBtIENEVDwvZGl2
Pg0KPGRpdj5XaGVyZTogJm5ic3A7Q29sdW1idXMgVGFwIGF0IHRoZSBGYWlybW9udCAodGhpcyBp
cyB0aGUgb3ZlcmZsb3cgaG90ZWwgYW5kIGlzIGNvbm5lY3RlZCB0byB0aGUgdmVudWUgdmlhIHRo
ZSB1bmRlcmdyb3VuZCBtYWxsKS48L2Rpdj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxk
aXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvc3Bh
bj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_D4F810F1D1665glenndeennbcunicom_--


From nobody Wed Mar 22 11:50:23 2017
Return-Path: <Glenn.Deen@nbcuni.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AFD1129B7E; Wed, 22 Mar 2017 11:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B63-jP_m0fII; Wed, 22 Mar 2017 11:50:18 -0700 (PDT)
Received: from mx0a-00176a04.pphosted.com (mx0b-00176a04.pphosted.com [67.231.157.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 871661294C7; Wed, 22 Mar 2017 11:50:18 -0700 (PDT)
Received: from pps.filterd (m0048207.ppops.net [127.0.0.1]) by m0048207.ppops.net-00176a04. (8.16.0.20/8.16.0.20) with SMTP id v2MImXJX042075; Wed, 22 Mar 2017 14:50:15 -0400
Received: from usushmgip002.mail.tfayd.com ([216.178.109.236]) by m0048207.ppops.net-00176a04. with ESMTP id 29ba174xme-1 (version=TLSv1.2 cipher=RC4-SHA bits=128 verify=NOT); Wed, 22 Mar 2017 14:50:15 -0400
Received: from unknown (HELO USUSHECWP005.mail.tfayd.com) ([10.40.33.204]) by usushmgip002.mail.tfayd.com with ESMTP; 22 Mar 2017 11:50:14 -0700
Received: from USUSHEMWP012.mail.tfayd.com ([169.254.4.151]) by usushecwp005.mail.tfayd.com ([3.156.41.23]) with mapi id 14.03.0266.001; Wed, 22 Mar 2017 11:50:14 -0700
From: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
To: "98attendees@ietf.org" <98attendees@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Video Streaming Bar BoF @ IETF98
Thread-Topic: Video Streaming Bar BoF @ IETF98
Thread-Index: AQHSndU57AttaXTq/02muQPDHsLP+aGhOviAgAADpdw=
Date: Wed, 22 Mar 2017 18:50:13 +0000
Message-ID: <3E96BCDA-CEBA-42D5-9188-A91FD9004ED2@nbcuni.com>
References: <D4EF03A1.D0EA4%glenn.deen@nbcuni.com>, <D4F810F1.D1665%glenn.deen@nbcuni.com>
In-Reply-To: <D4F810F1.D1665%glenn.deen@nbcuni.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
Content-Type: multipart/alternative; boundary="_000_3E96BCDACEBA42D59188A91FD9004ED2nbcunicom_"
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-22_16:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703220161
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yxge2Wx9DqxofxrkzV68b06Us-o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 18:50:21 -0000

--_000_3E96BCDACEBA42D59188A91FD9004ED2nbcunicom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

T29wcyB2ZXJ5IHdyb25nIGRhdGUgKGNyZWRpdCB0byBQaGlsIGZvciBjYXRjaGluZyBpdCEpDQoN
CkNvcnJlY3QgRGF0ZSBpcyBNb25kYXkgTWFyY2ggMjcgQDY6MzAgQ0RUIQ0KDQpNeSBiYWQsDQpH
bGVubg0KDQpTZW50IGZyb20gbXkgaVBob25lDQoNCk9uIE1hciAyMiwgMjAxNywgYXQgNzozOCBQ
TSwgRGVlbiwgR2xlbm4gKE5CQ1VuaXZlcnNhbCkgPEdsZW5uLkRlZW5AbmJjdW5pLmNvbTxtYWls
dG86R2xlbm4uRGVlbkBuYmN1bmkuY29tPj4gd3JvdGU6DQoNCg0KSSB3YW50IHRvIGludml0ZSBh
bnlvbmUgd2hvIGlzIGludGVyZXN0ZWQgaW4gSW50ZXJuZXQgVmlkZW8gU3RyZWFtaW5nIHRvIGEg
QmFyIEJvRiBvbiBJbnRlcm5ldCBWaWRlbyBTdHJlYW1pbmcgdG8gYmUgaGVsZCBhdCBJRVRGOTgu
DQoNClRpbWU6ICAgICBNb25kYXkgT2N0IDI3dGggIGF0IDY6MzAtNzozMHBtIENEVA0KV2hlcmU6
ICBDb2x1bWJ1cyBUYXAgYXQgdGhlIEZhaXJtb250ICh0aGlzIGlzIHRoZSBvdmVyZmxvdyBob3Rl
bCBhbmQgaXMgY29ubmVjdGVkIHRvIHRoZSB2ZW51ZSB2aWEgdGhlIHVuZGVyZ3JvdW5kIG1hbGwp
Lg0KDQpUaGlzIGlzIG9wZW4gdG8gYW55b25lIGludGVyZXN0ZWQgc28gcGxlYXNlIGZlZWwgZnJl
ZSB0byBwYXNzIHRoaXMgaW52aXRlIGFsb25nLiAgSSdtIHRvbGQgdGhhdCB0aGUgQ29sdW1idXMg
VGFwIGFsc28gaGFzIGEgZmluZSBzZWxlY3Rpb24gb2YgYmVlciENCg0KVGhpcyBpcyBhIG5vbi1o
b3N0ZWQgZXZlbnQsIG1lYW5pbmcgbm8gZnJlZSBiZWVyLCBidXQgdGhlcmUgd2lsbCBiZSBncmVh
dCBkaXNjdXNzaW9uIG9mIEludGVybmV0IHZpZGVvIQ0KDQpyZWdhcmRzDQpHbGVubiBEZWVuDQoN
Ci0tLS0tLQ0KDQpUb3BpYzogVmlkZW8gU3RyZWFtaW5nIGVYdGVuc2lvbnMgKFYtU1gpDQoNCkRl
c2NyaXB0aW9uOg0KDQpEdWUgdG8gaXRzIHNpemUgYW5kIHNlbnNpdGl2aXR5IHRvIG5ldHdvcmsg
Y29uZGl0aW9ucywgdGhlIHRyYW5zcG9ydCBvZiB2aWRlbyBvdmVyIHRoZSBJbnRlcm5ldCBoYXMg
aGlnaGxpZ2h0ZWQgYSBzaWduaWZpY2FudCBzY2FsYWJpbGl0eSBwcm9ibGVtIGZvciB0aGUgSW50
ZXJuZXQuICBPbiB0aGUgYmVsaWVmIHRoYXQgYWRkcmVzc2luZyB0aGlzIHNjYWxhYmlsaXR5IHBy
b2JsZW0gcmVxdWlyZXMgYmV0dGVyIGludGVncmF0aW9uIGJldHdlZW4gYXBwbGljYXRpb24gdHJh
bnNwb3J0IGFuZCBuZXR3b3JraW5nIHRlY2hub2xvZ2llcyBhbmQgbGV2ZXJhZ2luZyBJUHY2LCB0
aGlzIEJhciBCT0Ygd2lsbCBzb2xpY2l0IGV4cGVyaWVuY2VzIG9mIHRoZSBzY2FsaW5nIHByb2Js
ZW0gYXMgcGVyY2VpdmVkIGZyb20gZGlmZmVyZW50IHBhcnRzIG9mIHRoZSBpbmR1c3RyeSAobmV0
d29yaywgcHJvZHVjZXIsIHZlbmRvcnMpLg0KDQpWaWRlbyBpcyB3aXRob3V0IHJpdmFsIHRoZSB0
b3AgdXNlIG9mIEludGVybmV0IGJhbmR3aWR0aCwgYW5kIGl0cyBldmVyIGdyb3dpbmcgZGVtYW5k
IGZvciBtb3JlIGJhbmR3aWR0aCBlYXNpbHkgb3V0IHBhY2VzIHRoZSBuZXcgY2FwYWNpdHkgYmVp
bmcgYWRkZWQgYm90aCBnbG9iYWxseSBhbmQgcmVnaW9uYWxseSB3aXRoIG5vIGxldCB1cCBpbiBz
aWdodC4gICBVc2VycyBhcmUgZnJ1c3RyYXRlZCBieSBxdWFsaXR5LCBidWZmZXJpbmcsIGFuZCBz
dHV0dGVyaW5nIHByb2JsZW1zLiBWaWRlbyBwcm92aWRlcnMgYW5kIGFjY2VzcyBuZXR3b3JrcyBh
cmUgaW52ZXN0aW5nIGhlYXZpbHkgdG8ga2VlcCB1cCB3aXRoIGRlbWFuZC4gIFNpZ25pZmljYW50
IHdvcmsgaGFzIGJlIGRvbmUgYXQgdGhlIGFwcGxpY2F0aW9uIGxheWVyIHByb2R1Y2luZyBtb3Jl
IGVmZmljaWVudCBjb2RlY3MgYW5kIGlubm92YXRpdmUgYWRhcHRpdmUgYml0cmF0ZSB0cmFuc3Bv
cnRzIGxpa2UgTVBFRy1EQVNILiAgVGhlc2UgYWNjZXNzIGludmVzdG1lbnRzIGFuZCBhcHBsaWNh
dGlvbiBsYXllciB3b3JrIGhhdmUgaGVscGVkIGJ1dCB0aGV5IGFsb25lIGhhdmUgbm90IGJlZW4g
ZW5vdWdoLg0KDQpBIHRhcmdldCBvZiBhbnkgZXZlbnR1YWwgd29yayBhbmQgcHJvZHVjdCBpcyB0
byBlbmFibGUgdmlkZW8gYW5kIG5ldHdvcmsgcm91dGluZyAvIG1hbmFnZW1lbnQgdG8gd29yayBt
b3JlIGNvb3BlcmF0aXZlbHkgYW5kIGVmZmljaWVudGx5IHRvIHRyYW5zcG9ydCB2aWRlby4gIFN1
Y2Nlc3NmdWwgYXBwcm9hY2hlcyB3aWxsIG5lZWQgdG8gZG8gc28gaW4gYSBiYWNrd2FyZCBjb21w
YXRpYmxlIHdheXMgdG8gcGVybWl0IGV4aXRpbmcgZGV2aWNlcyBhbmQgcGxheWVycyB0byB0YWtl
IGFkdmFudGFnZSBvZiB0aGUgaW1wcm92ZWQgbmV0d29yayBlZmZpY2llbmNpZXMuDQoNCk9uZSBw
cm9wb3NlZCBhcHByb2FjaCB0byBkZWFsaW5nIHdpdGggaXNzdWVzIHdhcyBvdXRsaW5lZCBpbiB0
aGUgR2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIEJvRiBwcm9wb3NhbCDigJQgcmVs
YXRlZCBkcmFmdHMgYW5kIG1haWxpbmcgbGlzdCBpbmZvcm1hdGlvbiBpcyBwcm92aWRlZCBiZWxv
dy4gIEEgZGVtb25zdHJhdGlvbiBvZiBHR0lFIHdpbGwgYmUgcHJvdmlkZWQgZHVyaW5nIHRoZSBC
b0YsIGZvciBpbGx1c3RyYXRpb24gcHVycG9zZXMuICBEaXNjdXNzaW9uIGlzIGV4cGVjdGVkIGFu
ZCBlbmNvdXJhZ2VkIHRvIHJhbmdlIGZ1cnRoZXIgdGhhbiB0aGUgc3BlY2lmaWMgR0dJRSBwcm9w
b3NhbC4NCg0KVGhpcyB3aWxsIGJlIGFuIGludGVyYWN0aXZlIGRpc2N1c3Npb24gYW5kIHdlIGVu
Y291cmFnZSBhbnlvbmUgd2l0aCBhbiBpbnRlcmVzdCBpbiB0aGlzIHRvcGljIHRvIGNvbWUgYW5k
IHNoYXJlIHRoZWlyIGlkZWFzLg0KDQoNCiAgICBBZ2VuZGENCkludHJvZHVjdGlvbg0KQ29udGV4
dCBzZXR0aW5nIFs1bWluXQ0KDQpSb3VuZHRhYmxlIGRpc2N1c3Npb24gb2YgdGhlIGlzc3VlKHMp
IFszMG1pbl0NCg0KRGVtbyBvZiBHR0lFIHByb3RvdHlwZSBbMTBtaW5dDQoNCldoZXJlIGZyb20g
aGVyZT8gWzE1bWluXQ0KUG90ZW50aWFsIGZvciBJRVRGIHdvcmsg4oCUIGlzIHRoZXJlIGludGVy
ZXN0IHRvIHB1cnN1ZT8NCldvcmsgZm9yIG90aGVyIGdyb3Vwcz8NCg0KDQoNCiAgICAgICAgTWFp
bGluZyBMaXN0OiDigItodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dnaWUN
Cg0KICAgICAgICBSZWxldmFudCBkcmFmdHM6DQogICAgICAgICAgICBkcmFmdC1kZWVuLWRhaWds
ZS1nZ2llLTAyIDogIEdsYXNzIHRvIEdsYXNzIEludGVybmV0IEVjb3N5c3RlbSBJbnRyb2R1Y3Rp
b24NCiAgIGRyYWZ0LXJvc2UtZGVlbi1nZ2llLXVzZS1jYXNlcy0wMCA6IEdHSUUgSW50ZXJuZXQg
VmlkZW8gVXNlIENhc2VzDQogICBkcmFmdC1kYWlnbGUtZGVlbi1nZ2llLXVyaS1zbmFwdHItMDAg
OiAgR2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIFVSSSBhbmQgUy1OQVBUUiBVc2UN
CiAgIGRyYWZ0LWRlZW4tbmFpay1nZ2llLW1lbi1tcGVnLWRhc2gtMDAgOiBVc2luZyBNZWRpYSBF
bmNvZGluZyBOZXR3b3JrcyB0byBhZGRyZXNzIE1QRUctREFTSCB2aWRlbw0KDQpUaW1lOiAgICAg
TW9uZGF5IE9jdCAyN3RoICBhdCA2OjMwLTc6MzBwbSBDRFQNCldoZXJlOiAgQ29sdW1idXMgVGFw
IGF0IHRoZSBGYWlybW9udCAodGhpcyBpcyB0aGUgb3ZlcmZsb3cgaG90ZWwgYW5kIGlzIGNvbm5l
Y3RlZCB0byB0aGUgdmVudWUgdmlhIHRoZSB1bmRlcmdyb3VuZCBtYWxsKS4NCg0KDQoNCg==

--_000_3E96BCDACEBA42D59188A91FD9004ED2nbcunicom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IGRpcj0iYXV0byI+DQo8
ZGl2Pk9vcHMgdmVyeSB3cm9uZyBkYXRlIChjcmVkaXQgdG8gUGhpbCBmb3IgY2F0Y2hpbmcgaXQh
KTwvZGl2Pg0KPGRpdiBpZD0iQXBwbGVNYWlsU2lnbmF0dXJlIj48YnI+DQo8L2Rpdj4NCjxkaXYg
aWQ9IkFwcGxlTWFpbFNpZ25hdHVyZSI+Q29ycmVjdCBEYXRlIGlzIE1vbmRheSBNYXJjaCAyNyBA
NjozMCBDRFQhPC9kaXY+DQo8ZGl2IGlkPSJBcHBsZU1haWxTaWduYXR1cmUiPjxicj4NCjwvZGl2
Pg0KPGRpdiBpZD0iQXBwbGVNYWlsU2lnbmF0dXJlIj5NeSBiYWQsPC9kaXY+DQo8ZGl2IGlkPSJB
cHBsZU1haWxTaWduYXR1cmUiPkdsZW5uJm5ic3A7PGJyPg0KPGJyPg0KU2VudCBmcm9tIG15IGlQ
aG9uZTwvZGl2Pg0KPGRpdj48YnI+DQpPbiBNYXIgMjIsIDIwMTcsIGF0IDc6MzggUE0sIERlZW4s
IEdsZW5uIChOQkNVbml2ZXJzYWwpICZsdDs8YSBocmVmPSJtYWlsdG86R2xlbm4uRGVlbkBuYmN1
bmkuY29tIj5HbGVubi5EZWVuQG5iY3VuaS5jb208L2E+Jmd0OyB3cm90ZTo8YnI+DQo8YnI+DQo8
L2Rpdj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPg0KPGRpdj4NCjxkaXY+PGJyPg0KPC9kaXY+
DQo8c3BhbiBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRpdj4NCjxkaXYgc3R5bGU9Indv
cmQtd3JhcDogYnJlYWstd29yZDsgLXdlYmtpdC1uYnNwLW1vZGU6IHNwYWNlOyAtd2Via2l0LWxp
bmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNlOyBjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LXNp
emU6IDE0cHg7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyI+DQo8ZGl2Pkkgd2Fu
dCB0byBpbnZpdGUgYW55b25lIHdobyBpcyBpbnRlcmVzdGVkIGluIEludGVybmV0IFZpZGVvIFN0
cmVhbWluZyB0byBhIEJhciBCb0Ygb24gSW50ZXJuZXQgVmlkZW8gU3RyZWFtaW5nIHRvIGJlIGhl
bGQgYXQgSUVURjk4LjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VGltZTogJm5ic3A7
ICZuYnNwOyBNb25kYXkgT2N0IDI3dGggJm5ic3A7YXQgNjozMC03OjMwcG0gQ0RUPC9kaXY+DQo8
ZGl2PldoZXJlOiAmbmJzcDtDb2x1bWJ1cyBUYXAgYXQgdGhlIEZhaXJtb250ICh0aGlzIGlzIHRo
ZSBvdmVyZmxvdyBob3RlbCBhbmQgaXMgY29ubmVjdGVkIHRvIHRoZSB2ZW51ZSB2aWEgdGhlIHVu
ZGVyZ3JvdW5kIG1hbGwpLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VGhpcyBpcyBv
cGVuIHRvIGFueW9uZSBpbnRlcmVzdGVkIHNvIHBsZWFzZSBmZWVsIGZyZWUgdG8gcGFzcyB0aGlz
IGludml0ZSBhbG9uZy4gJm5ic3A7SSdtIHRvbGQgdGhhdCB0aGUgQ29sdW1idXMgVGFwIGFsc28g
aGFzIGEgZmluZSBzZWxlY3Rpb24gb2YgYmVlciEgJm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VD
VElPTiI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0id29yZC13cmFwOiBicmVhay13b3JkOyAtd2Via2l0
LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7
IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtc2l6ZTogMTRweDsgZm9udC1mYW1pbHk6IENhbGli
cmksIHNhbnMtc2VyaWY7Ij4NCjxkaXY+VGhpcyBpcyBhIG5vbi1ob3N0ZWQgZXZlbnQsIG1lYW5p
bmcgbm8gZnJlZSBiZWVyLCBidXQgdGhlcmUgd2lsbCBiZSBncmVhdCBkaXNjdXNzaW9uIG9mIElu
dGVybmV0IHZpZGVvITwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+cmVnYXJkczwvZGl2
Pg0KPGRpdj5HbGVubiBEZWVuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4tLS0tLS08
L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PlRvcGljOiBWaWRlbyBTdHJlYW1pbmcgZVh0
ZW5zaW9ucyAoVi1TWCk8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkRlc2NyaXB0aW9u
OiAmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkR1ZSB0byBpdHMgc2l6ZSBh
bmQgc2Vuc2l0aXZpdHkgdG8gbmV0d29yayBjb25kaXRpb25zLCB0aGUgdHJhbnNwb3J0IG9mIHZp
ZGVvIG92ZXIgdGhlIEludGVybmV0IGhhcyBoaWdobGlnaHRlZCBhIHNpZ25pZmljYW50IHNjYWxh
YmlsaXR5IHByb2JsZW0gZm9yIHRoZSBJbnRlcm5ldC4gJm5ic3A7T24gdGhlIGJlbGllZiB0aGF0
IGFkZHJlc3NpbmcgdGhpcyBzY2FsYWJpbGl0eSBwcm9ibGVtIHJlcXVpcmVzIGJldHRlciBpbnRl
Z3JhdGlvbiBiZXR3ZWVuDQogYXBwbGljYXRpb24gdHJhbnNwb3J0IGFuZCBuZXR3b3JraW5nIHRl
Y2hub2xvZ2llcyBhbmQgbGV2ZXJhZ2luZyBJUHY2LCB0aGlzIEJhciBCT0Ygd2lsbCBzb2xpY2l0
IGV4cGVyaWVuY2VzIG9mIHRoZSBzY2FsaW5nIHByb2JsZW0gYXMgcGVyY2VpdmVkIGZyb20gZGlm
ZmVyZW50IHBhcnRzIG9mIHRoZSBpbmR1c3RyeSAobmV0d29yaywgcHJvZHVjZXIsIHZlbmRvcnMp
LiAmbmJzcDsmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PlZpZGVvIGlzIHdp
dGhvdXQgcml2YWwgdGhlIHRvcCB1c2Ugb2YgSW50ZXJuZXQgYmFuZHdpZHRoLCBhbmQgaXRzIGV2
ZXIgZ3Jvd2luZyBkZW1hbmQgZm9yIG1vcmUgYmFuZHdpZHRoIGVhc2lseSBvdXQgcGFjZXMgdGhl
IG5ldyBjYXBhY2l0eSBiZWluZyBhZGRlZCBib3RoIGdsb2JhbGx5IGFuZCByZWdpb25hbGx5IHdp
dGggbm8gbGV0IHVwIGluIHNpZ2h0LiAmbmJzcDsgVXNlcnMgYXJlIGZydXN0cmF0ZWQgYnkgcXVh
bGl0eSwgYnVmZmVyaW5nLCBhbmQNCiBzdHV0dGVyaW5nIHByb2JsZW1zLiBWaWRlbyBwcm92aWRl
cnMgYW5kIGFjY2VzcyBuZXR3b3JrcyBhcmUgaW52ZXN0aW5nIGhlYXZpbHkgdG8ga2VlcCB1cCB3
aXRoIGRlbWFuZC4gJm5ic3A7U2lnbmlmaWNhbnQgd29yayBoYXMgYmUgZG9uZSBhdCB0aGUgYXBw
bGljYXRpb24gbGF5ZXIgcHJvZHVjaW5nIG1vcmUgZWZmaWNpZW50IGNvZGVjcyBhbmQgaW5ub3Zh
dGl2ZSBhZGFwdGl2ZSBiaXRyYXRlIHRyYW5zcG9ydHMgbGlrZSBNUEVHLURBU0guICZuYnNwO1Ro
ZXNlDQogYWNjZXNzIGludmVzdG1lbnRzIGFuZCBhcHBsaWNhdGlvbiBsYXllciB3b3JrIGhhdmUg
aGVscGVkIGJ1dCB0aGV5IGFsb25lIGhhdmUgbm90IGJlZW4gZW5vdWdoLiAmbmJzcDs8L2Rpdj4N
CjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkEgdGFyZ2V0IG9mIGFueSBldmVudHVhbCB3b3JrIGFu
ZCBwcm9kdWN0IGlzIHRvIGVuYWJsZSB2aWRlbyBhbmQgbmV0d29yayByb3V0aW5nIC8gbWFuYWdl
bWVudCB0byB3b3JrIG1vcmUgY29vcGVyYXRpdmVseSBhbmQgZWZmaWNpZW50bHkgdG8gdHJhbnNw
b3J0IHZpZGVvLiAmbmJzcDtTdWNjZXNzZnVsIGFwcHJvYWNoZXMgd2lsbCBuZWVkIHRvIGRvIHNv
IGluIGEgYmFja3dhcmQgY29tcGF0aWJsZSB3YXlzIHRvIHBlcm1pdCBleGl0aW5nIGRldmljZXMN
CiBhbmQgcGxheWVycyB0byB0YWtlIGFkdmFudGFnZSBvZiB0aGUgaW1wcm92ZWQgbmV0d29yayBl
ZmZpY2llbmNpZXMuICZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+T25lIHBy
b3Bvc2VkIGFwcHJvYWNoIHRvIGRlYWxpbmcgd2l0aCBpc3N1ZXMgd2FzIG91dGxpbmVkIGluIHRo
ZSBHbGFzcyB0byBHbGFzcyBJbnRlcm5ldCBFY29zeXN0ZW0gQm9GIHByb3Bvc2FsIOKAlCByZWxh
dGVkIGRyYWZ0cyBhbmQgbWFpbGluZyBsaXN0IGluZm9ybWF0aW9uIGlzIHByb3ZpZGVkIGJlbG93
LiAmbmJzcDtBIGRlbW9uc3RyYXRpb24gb2YgR0dJRSB3aWxsIGJlIHByb3ZpZGVkIGR1cmluZyB0
aGUgQm9GLCBmb3IgaWxsdXN0cmF0aW9uDQogcHVycG9zZXMuICZuYnNwO0Rpc2N1c3Npb24gaXMg
ZXhwZWN0ZWQgYW5kIGVuY291cmFnZWQgdG8gcmFuZ2UgZnVydGhlciB0aGFuIHRoZSBzcGVjaWZp
YyBHR0lFIHByb3Bvc2FsLiAmbmJzcDsgJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0K
PGRpdj5UaGlzIHdpbGwgYmUgYW4gaW50ZXJhY3RpdmUgZGlzY3Vzc2lvbiBhbmQgd2UgZW5jb3Vy
YWdlIGFueW9uZSB3aXRoIGFuIGludGVyZXN0IGluIHRoaXMgdG9waWMgdG8gY29tZSBhbmQgc2hh
cmUgdGhlaXIgaWRlYXMuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+Jm5ic3A7ICZuYnNwOyBBZ2VuZGE8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFw
cGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+SW50cm9kdWN0aW9u
PC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNw
YWNlOnByZSI+PC9zcGFuPkNvbnRleHQgc2V0dGluZyBbNW1pbl08L2Rpdj4NCjxkaXY+PGJyPg0K
PC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNw
YWNlOnByZSI+PC9zcGFuPlJvdW5kdGFibGUgZGlzY3Vzc2lvbiBvZiB0aGUgaXNzdWUocykgWzMw
bWluXTwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRh
Yi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+RGVtbyBvZiBHR0lFIHByb3Rv
dHlwZSBbMTBtaW5dPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0i
QXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5XaGVyZSBmcm9t
IGhlcmU/IFsxNW1pbl08L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBz
dHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+UG90ZW50aWFsIGZvciBJRVRGIHdvcmsg4oCU
IGlzIHRoZXJlIGludGVyZXN0IHRvIHB1cnN1ZT88L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFw
cGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+V29yayBmb3Igb3Ro
ZXIgZ3JvdXBzPzxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNl
OnByZSI+PC9zcGFuPjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+Jm5ic3A7PC9kaXY+
DQo8ZGl2PiZuYnNwOyAmbmJzcDsmbmJzcDs8L2Rpdj4NCjxkaXY+Jm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7IE1haWxpbmcgTGlzdDog4oCLPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9nZ2llIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL2dnaWU8L2E+PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4mbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgUmVsZXZhbnQgZHJhZnRzOjwvZGl2Pg0KPGRpdj4mbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBkcmFmdC1kZWVuLWRhaWdsZS1nZ2llLTAyIDog
Jm5ic3A7R2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIEludHJvZHVjdGlvbjwvZGl2
Pg0KPGRpdj48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpw
cmUiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ZHJhZnQtcm9zZS1kZWVuLWdnaWUtdXNlLWNhc2VzLTAw
IDogR0dJRSBJbnRlcm5ldCBWaWRlbyBVc2UgQ2FzZXM8c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNw
YW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj48L2Rpdj4NCjxkaXY+PHNwYW4gY2xh
c3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+Jm5ic3A7
ICZuYnNwO2RyYWZ0LWRhaWdsZS1kZWVuLWdnaWUtdXJpLXNuYXB0ci0wMCA6ICZuYnNwO0dsYXNz
IHRvIEdsYXNzIEludGVybmV0IEVjb3N5c3RlbSBVUkkgYW5kIFMtTkFQVFIgVXNlPC9kaXY+DQo8
ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+
PC9zcGFuPiZuYnNwOyAmbmJzcDtkcmFmdC1kZWVuLW5haWstZ2dpZS1tZW4tbXBlZy1kYXNoLTAw
IDogVXNpbmcgTWVkaWEgRW5jb2RpbmcgTmV0d29ya3MgdG8gYWRkcmVzcyBNUEVHLURBU0ggdmlk
ZW8mbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj5UaW1lOiAmbmJz
cDsgJm5ic3A7IE1vbmRheSBPY3QgMjd0aCAmbmJzcDthdCA2OjMwLTc6MzBwbSBDRFQ8L2Rpdj4N
CjxkaXY+V2hlcmU6ICZuYnNwO0NvbHVtYnVzIFRhcCBhdCB0aGUgRmFpcm1vbnQgKHRoaXMgaXMg
dGhlIG92ZXJmbG93IGhvdGVsIGFuZCBpcyBjb25uZWN0ZWQgdG8gdGhlIHZlbnVlIHZpYSB0aGUg
dW5kZXJncm91bmQgbWFsbCkuPC9kaXY+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2
Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L3NwYW4+
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_3E96BCDACEBA42D59188A91FD9004ED2nbcunicom_--


From nobody Wed Mar 22 11:53:24 2017
Return-Path: <aaron.falk@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 127C0129BE6; Wed, 22 Mar 2017 11:53:17 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IlqmcJtMG2Q0; Wed, 22 Mar 2017 11:53:14 -0700 (PDT)
Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B104129644; Wed, 22 Mar 2017 11:53:14 -0700 (PDT)
Received: by mail-qk0-x244.google.com with SMTP id n141so27288470qke.3; Wed, 22 Mar 2017 11:53:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version; bh=4hQlC9/DlhcdVRGvBuqwA7UtTY7Ctj38dMF1fOXqyig=; b=TF/HiCsgPquEy61fnOm+pXh0QdCcg8hWAhL2Pgx3+ND0mpPmA+BMJVGst8nBpSeSIg DNTSMuIkW1hspdWojdYKR5WUKqaw2LJjgL53QOqLc83YiVdlwvDYhZkIn0zYAj58kYX4 CJ8V3YH2+VTAa4imhrlNWUhvqLdEZp+IQJJ1hzZGreb5cxE/rX+7WW91hjm7RJzdvFxy Ck8d0fBBt6AhMJ2TIbSXccYrSqNnmPDd8XVU0xB07SaqUoLOgHRKhThCaAmwr4lPFUET zg/nXz6OSrDDy5rG4MuFtufqGDtJxeMnmGmhzQhXWTNI6/Lg43Q2Q3TKWvJ3ahOCeSO9 fkbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version; bh=4hQlC9/DlhcdVRGvBuqwA7UtTY7Ctj38dMF1fOXqyig=; b=Nqod/e/0DrI9tJhqungF9wr5UhaemLre+v/i2PWTa0oHMtR7qlYfMX+1exThp7/z8E 2AsC4WVHOz7eb3v6DrR++nLBoAVhRRh6pJ2FrZPpvgSp5VOEZ/H0H8pMSwjgnNpeS/yQ InP9w3OdbjehN1SqRSy8FiTgoU3Ul0z0HRpc0rXU3kgphW9wESJaRkpWBdw2fmnXVAW/ jHZcKGemax6Ilxs1rwUl+CCZJXXnR5eHKVtX1BKGo6ceCxKIoZEHAiDiH8CWCv+YNPsc NpbvKvFBlBpfKTzExVh/H4M9mVoZ8n1OotYQU4jVRvvnyBujHYFr7yDxiaC2n+xQLIDg yXhA==
X-Gm-Message-State: AFeK/H1wDfvbcM8Wpyb2y+++0FIs4zLj5pHYFgDgaKlwC/87XN4l1mb69ePAwfDj9d4zJw==
X-Received: by 10.55.203.7 with SMTP id d7mr2146460qkj.245.1490208793404; Wed, 22 Mar 2017 11:53:13 -0700 (PDT)
Received: from [172.19.32.143] ([2001:4878:8000:60:396d:674b:26d8:1dac]) by smtp.gmail.com with ESMTPSA id h27sm1557560qtf.24.2017.03.22.11.53.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Mar 2017 11:53:12 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, 98attendees@ietf.org
Subject: Bad Attitude PechaKucha in Chicago -- Schedule & location
Date: Wed, 22 Mar 2017 14:53:12 -0400
Message-ID: <BC1446FD-BB05-408C-BDEE-86FD75D8E5EC@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_20BDE743-6DD9-46A5-A9FF-7CDAEF0A9B95_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8kVYyT1zykJNohi-CUWgFYBOYdU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 18:53:17 -0000

--=_MailMate_20BDE743-6DD9-46A5-A9FF-7CDAEF0A9B95_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

DATE: 		Thursday, March 30
TIME: 		21:30 - 23:00 (est)
LOCATION: 	Zurich G.
BAR: 		cash, 21:00 - 23:30 (est)
COUNT: 		10

=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94

A Pecha Kucha is a lightning-talk presentation format, originating in =

Japan, where a speaker presents 20 image-only slides that are each on =

the screen for 20 seconds and advance automatically.  With each talk =

lasting for 6:40, it has the feature of forcing presentations -- good or =

bad -- to be focused and brief.  This is an unofficial event. Topics are =

encouraged to be a IETF-related and satirical or controversial in some =

way, although not mean-spirited.  Anyone can participate in this social =

event.  Video from the Berlin and Seoul PKs can be found =

[here](http://snaggletooth.akam.ai).

Format Details:

* Presentation slots are open to all, assigned first come, first served.
* To reserve a presentation slot, send a name and title to =

aaron.falk@gmail.com and receive confirmation.
* Presenters must agree to adhere to the Pecha Kucha format (20 slides, =

primarily image-only, automatically advancing every 20 seconds).
* There are lots of online tutorials and suggestions for how to make a =

good Pecha Kucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

[[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pecha=
=2Ehtml)], =

[[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].
--=_MailMate_20BDE743-6DD9-46A5-A9FF-7CDAEF0A9B95_=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">DATE:         Thursday, March 30<br>
TIME:         21:30 - 23:00 (est)<br>
LOCATION:     Zurich G.<br>
BAR:         cash, 21:00 - 23:30 (est)<br>
COUNT:         10</p>

<p dir=3D"auto">=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94</p>=


<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin and Seoul PKs can be found <a href=3D"ht=
tp://snaggletooth.akam.ai" style=3D"color:#3983C4">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#3983C4">aaron.falk@gmail.com<=
/a> and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#3983C4">1</a>], [<a href=3D"http://blog.indezine.com/20=
12/05/10-tips-to-create-and-present-pecha.html" style=3D"color:#3983C4">2=
</a>], [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha=
-kucha/" style=3D"color:#3983C4">3</a>].</li>
</ul>
</div>
</div>
</body>
</html>

--=_MailMate_20BDE743-6DD9-46A5-A9FF-7CDAEF0A9B95_=--


From nobody Wed Mar 22 13:10:33 2017
Return-Path: <aaron.falk@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 EB541129979; Wed, 22 Mar 2017 13:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBxLbj1pcmEv; Wed, 22 Mar 2017 13:10:22 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A1391277BB; Wed, 22 Mar 2017 13:10:22 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id p22so25182581qka.3; Wed, 22 Mar 2017 13:10:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:in-reply-to:references:mime-version;  bh=hVl9+ANpFTeFIU8I/FkaIu7hajBPixufNgt7B/vVq7k=; b=A6TS09NjHxeQNmnPohHvuBB8bmeEaHLNFDYXFFZ/D4g6EOK6g5emN/A2a/1ONuSA68 dMU8171yOWbpkZjiOytDGz7aBggJN4cNg5dbFYSy7tLUMVXqZNPGKhcgK8VSgHtlqmoJ 72/3Gznpmiq6GrWiqYluCEWkYfYvcaQi6kX484X0SKzpJFFJNUY5nF2FWHBv5eRcc2d6 XcNsLZKByyhW9AGSBZywxu9J8sMLQx0qgoPmfxnnwWOqtdEhrKaTtZGbVHz7F4qkCN2B bjpZWv7KApNb5TnhBeyYeCMvUwXqJ+M2i2Kd+ya+8qBiOquVpRmNm3Ckv3SZanmhj6KA xPvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version; bh=hVl9+ANpFTeFIU8I/FkaIu7hajBPixufNgt7B/vVq7k=; b=DcjtLstHx13Jcbu4gdmezib8dyzp6KHlmEDJGIPdkkw2eUUro+iMPeJBAeVd+R3L+6 UlbEpH16UF0JsSWHUPPQKvAzzBTetJ+CkGiRL9Gfm0bb3DsCbjusjuAGY0SIP2X8X0cZ rBUFXIq7W1RX96Zn96NCcB5HH8lWCeOx6A7KjU+iCcw6Sg+nRoOojM2GIVCAwxf8TLGF vaM8a1HXj3ZWqXfJCWmmmrwicL2eTrIHmJ0k+wP64sBO/r2PYf/wvWAKryzSQqv4tps5 fhsdjR7bYzBe8PIiUsQhCG8lu6heEon2ic6qPXJvWgTkpr+sbVM9i97tiQDTBlDJKGNq Zp3Q==
X-Gm-Message-State: AFeK/H2n//jPmf+ZB/lYrozTeumYIF7dFGmyLxkOpi5KYiBHeqNOvhjCTNIddfA6t/OWnw==
X-Received: by 10.55.180.129 with SMTP id d123mr35398741qkf.158.1490213421035;  Wed, 22 Mar 2017 13:10:21 -0700 (PDT)
Received: from [172.19.33.255] ([2001:4878:8000:60:2c3e:6ce1:6f8:1b81]) by smtp.gmail.com with ESMTPSA id 1sm1691101qtb.40.2017.03.22.13.10.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Mar 2017 13:10:20 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, 98attendees@ietf.org
Subject: Re: Bad Attitude PechaKucha in Chicago -- Schedule & location
Date: Wed, 22 Mar 2017 16:10:19 -0400
Message-ID: <5400F783-D8F7-4B2B-8C5B-209A9EC66B15@gmail.com>
In-Reply-To: <BC1446FD-BB05-408C-BDEE-86FD75D8E5EC@gmail.com>
References: <BC1446FD-BB05-408C-BDEE-86FD75D8E5EC@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_20902089-FDA2-48CD-BDB3-95BF40FA1D9F_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MWRCyxZFB6cNF2TInu2xqDfXhPs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Mar 2017 20:10:25 -0000

--=_MailMate_20902089-FDA2-48CD-BDB3-95BF40FA1D9F_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

Sigh.  =E2=80=9Cest=E2=80=9D is intended to mean =E2=80=9Cestimated=E2=80=
=9D not =E2=80=9Ceastern =

standard time=E2=80=9D.

Email is hard.

=E2=80=94aaron

On 22 Mar 2017, at 14:53, Aaron Falk wrote:

> DATE: 		Thursday, March 30
> TIME: 		21:30 - 23:00 (est)
> LOCATION: 	Zurich G.
> BAR: 		cash, 21:00 - 23:30 (est)
> COUNT: 		10
>
> =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94
>
> A Pecha Kucha is a lightning-talk presentation format, originating in =

> Japan, where a speaker presents 20 image-only slides that are each on =

> the screen for 20 seconds and advance automatically.  With each talk =

> lasting for 6:40, it has the feature of forcing presentations -- good =

> or bad -- to be focused and brief.  This is an unofficial event. =

> Topics are encouraged to be a IETF-related and satirical or =

> controversial in some way, although not mean-spirited.  Anyone can =

> participate in this social event.  Video from the Berlin and Seoul PKs =

> can be found [here](http://snaggletooth.akam.ai).
>
> Format Details:
>
> * Presentation slots are open to all, assigned first come, first =

> served.
> * To reserve a presentation slot, send a name and title to =

> aaron.falk@gmail.com and receive confirmation.
> * Presenters must agree to adhere to the Pecha Kucha format (20 =

> slides, primarily image-only, automatically advancing every 20 =

> seconds).
> * There are lots of online tutorials and suggestions for how to make a =

> good Pecha Kucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

> [[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pec=
ha.html)], =

> [[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].

--=_MailMate_20902089-FDA2-48CD-BDB3-95BF40FA1D9F_=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Sigh.  =E2=80=9Cest=E2=80=9D is intended to mean =E2=80=9C=
estimated=E2=80=9D not =E2=80=9Ceastern standard time=E2=80=9D.</p>

<p dir=3D"auto">Email is hard.  </p>

<p dir=3D"auto">=E2=80=94aaron</p>

<p dir=3D"auto">On 22 Mar 2017, at 14:53, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">DATE:         Thursday, March 30<br>
TIME:         21:30 - 23:00 (est)<br>
LOCATION:     Zurich G.<br>
BAR:         cash, 21:00 - 23:30 (est)<br>
COUNT:         10</p>

<p dir=3D"auto">=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94</p>=


<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin and Seoul PKs can be found <a href=3D"ht=
tp://snaggletooth.akam.ai" style=3D"color:#777">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#777">aaron.falk@gmail.com</a>=
 and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#777">1</a>], [<a href=3D"http://blog.indezine.com/2012/=
05/10-tips-to-create-and-present-pecha.html" style=3D"color:#777">2</a>],=
 [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha=
/" style=3D"color:#777">3</a>].</li>
</ul>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_20902089-FDA2-48CD-BDB3-95BF40FA1D9F_=--


From nobody Thu Mar 23 12:20:37 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 635E7129C0B; Thu, 23 Mar 2017 12:20:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carlos Pignataro <cpignata@cisco.com>
To: <rtg-dir@ietf.org>
Cc: draft-ietf-trill-p2mp-bfd.all@ietf.org, ietf@ietf.org, trill@ietf.org
Subject: Review of draft-ietf-trill-p2mp-bfd-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149029682927.22415.11722241596169339182@ietfa.amsl.com>
Date: Thu, 23 Mar 2017 12:20:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vGwLwo7CvoWxjWF1DpHNgdJPkIU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Mar 2017 19:20:29 -0000

Reviewer: Carlos Pignataro
Review result: Has Nits

Hi,

This is a short yet well written document. Looks really good. Just a
couple of small questions/comments:

1. It's not clear exactly what from RFC 7175 is being updated by
Section 4. This is based on the last paragraph of the Intro, yet
Section 5 also seems relevant to that update.
2. In the IANA COnsiderations, it would be useful to explicitly list
that the "RBridge Channel Protocols" registry is part of the
"Transparent Interconnection of Lots of Links (TRILL) Parameters" 

Thanks,

Carlos Pignataro.


From nobody Thu Mar 23 12:24:18 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 992AC129BF3; Thu, 23 Mar 2017 12:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78CSRA3jQIoG; Thu, 23 Mar 2017 12:24:13 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD77B131635; Thu, 23 Mar 2017 12:24:02 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.5.9;
From: "Susan Hares" <shares@ndzh.com>
To: "'Carlos Pignataro'" <cpignata@cisco.com>, <rtg-dir@ietf.org>
Cc: <draft-ietf-trill-p2mp-bfd.all@ietf.org>, <ietf@ietf.org>, <trill@ietf.org>
References: <149029682927.22415.11722241596169339182@ietfa.amsl.com>
In-Reply-To: <149029682927.22415.11722241596169339182@ietfa.amsl.com>
Subject: RE: [RTG-DIR] Review of draft-ietf-trill-p2mp-bfd-04
Date: Thu, 23 Mar 2017 15:18:58 -0400
Message-ID: <00c301d2a40a$52aa0cb0$f7fe2610$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJSSExrVMsGcWq11VRSKhba87ASTqCjhABA
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DinA1PQB-OhDmkeJjOhi_3xKIcw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Mar 2017 19:24:15 -0000

Carlos:=20

Thank you for the quick review.=20

Sue=20

-----Original Message-----
From: rtg-dir [mailto:rtg-dir-bounces@ietf.org] On Behalf Of Carlos =
Pignataro
Sent: Thursday, March 23, 2017 3:20 PM
To: rtg-dir@ietf.org
Cc: draft-ietf-trill-p2mp-bfd.all@ietf.org; ietf@ietf.org; =
trill@ietf.org
Subject: [RTG-DIR] Review of draft-ietf-trill-p2mp-bfd-04

Reviewer: Carlos Pignataro
Review result: Has Nits

Hi,

This is a short yet well written document. Looks really good. Just a =
couple of small questions/comments:

1. It's not clear exactly what from RFC 7175 is being updated by Section =
4. This is based on the last paragraph of the Intro, yet Section 5 also =
seems relevant to that update.
2. In the IANA COnsiderations, it would be useful to explicitly list =
that the "RBridge Channel Protocols" registry is part of the =
"Transparent Interconnection of Lots of Links (TRILL) Parameters"=20

Thanks,

Carlos Pignataro.



From nobody Thu Mar 23 15:37:25 2017
Return-Path: <zhangmingui@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70D4612948D; Thu, 23 Mar 2017 15:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xjwB-BMBvTFh; Thu, 23 Mar 2017 15:37:22 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B4DB1292FD; Thu, 23 Mar 2017 15:37:21 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML714-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DJM22142; Thu, 23 Mar 2017 22:37:18 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 23 Mar 2017 22:37:17 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Fri, 24 Mar 2017 06:37:09 +0800
From: "Zhangmingui (Martin)" <zhangmingui@huawei.com>
To: Carlos Pignataro <cpignata@cisco.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "draft-ietf-trill-p2mp-bfd.all@ietf.org" <draft-ietf-trill-p2mp-bfd.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: RE: Review of draft-ietf-trill-p2mp-bfd-04
Thread-Topic: Review of draft-ietf-trill-p2mp-bfd-04
Thread-Index: AQHSpAqM/H6sHj72GE6hAlFdfMbv2aGjAqca
Date: Thu, 23 Mar 2017 22:37:09 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7A6418619@NKGEML515-MBX.china.huawei.com>
References: <149029682927.22415.11722241596169339182@ietfa.amsl.com>
In-Reply-To: <149029682927.22415.11722241596169339182@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.150.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.58D44E1F.00F6, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0afbde728a7e0f1dbe61aa7f651780fa
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yKdIWgd3mkl4mZGwBeUvap7CJKQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Mar 2017 22:37:24 -0000

Hi Carlos,

1. Yes. Section 5 rather than Seciton 4 is relevant. The last paragraph of =
the Intro will be updated to reflect this.

2. OK. The text will be updated.

Thanks,
Mingui
________________________________________
From: Carlos Pignataro [cpignata@cisco.com]
Sent: Friday, March 24, 2017 3:20
To: rtg-dir@ietf.org
Cc: draft-ietf-trill-p2mp-bfd.all@ietf.org; ietf@ietf.org; trill@ietf.org
Subject: Review of draft-ietf-trill-p2mp-bfd-04

Reviewer: Carlos Pignataro
Review result: Has Nits

Hi,

This is a short yet well written document. Looks really good. Just a
couple of small questions/comments:

1. It's not clear exactly what from RFC 7175 is being updated by
Section 4. This is based on the last paragraph of the Intro, yet
Section 5 also seems relevant to that update.
2. In the IANA COnsiderations, it would be useful to explicitly list
that the "RBridge Channel Protocols" registry is part of the
"Transparent Interconnection of Lots of Links (TRILL) Parameters"

Thanks,

Carlos Pignataro.=


From nobody Thu Mar 23 21:53:28 2017
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 B0E0C129411 for <ietf@ietfa.amsl.com>; Thu, 23 Mar 2017 21:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.397
X-Spam-Level: 
X-Spam-Status: No, score=-5.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DkMdcCVEiaAx for <ietf@ietfa.amsl.com>; Thu, 23 Mar 2017 21:53:24 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97723129407 for <ietf@ietf.org>; Thu, 23 Mar 2017 21:53:24 -0700 (PDT)
Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2O4pwIg077154 for <ietf@ietf.org>; Fri, 24 Mar 2017 00:53:24 -0400
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by mx0a-001b2d01.pphosted.com with ESMTP id 29cm3tnwar-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 24 Mar 2017 00:53:23 -0400
Received: from localhost by e38.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, 23 Mar 2017 22:53:23 -0600
Received: from b03cxnp07028.gho.boulder.ibm.com (9.17.130.15) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 23 Mar 2017 22:53:20 -0600
Received: from b03ledav006.gho.boulder.ibm.com (b03ledav006.gho.boulder.ibm.com [9.17.130.237]) by b03cxnp07028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v2O4rIBf17039662 for <ietf@ietf.org>; Thu, 23 Mar 2017 21:53:18 -0700
Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A121DC6042 for <ietf@ietf.org>; Thu, 23 Mar 2017 22:53:18 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav006.gho.boulder.ibm.com (Postfix) with ESMTPS id 87959C6037 for <ietf@ietf.org>; Thu, 23 Mar 2017 22:53:18 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v2O4rHHl009898 for <ietf@ietf.org>; Fri, 24 Mar 2017 00:53:17 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v2O4rH0Y009881 for ietf@ietf.org; Fri, 24 Mar 2017 00:53:17 -0400
From: narten@us.ibm.com
Date: Fri, 24 Mar 2017 00:53:17 -0400
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-TM-AS-GCONF: 00
x-cbid: 17032404-0028-0000-0000-00000746A59F
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006838; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000206; SDB=6.00838106; UDB=6.00412094; IPR=6.00615868;  BA=6.00005234; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014789; XFM=3.00000013; UTC=2017-03-24 04:53:21
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17032404-0029-0000-0000-0000348A74ED
Message-Id: <201703240453.v2O4rH0Y009881@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-24_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=52 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703240043
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H1_DWE_TiImjuoljOHWSD2Du-4Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 04:53:28 -0000

Total of 62 messages in the last 7 days.
 
script run at: Fri Mar 24 00:53:11 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.45% |    4 |  6.84% |    53891 | presnick@qti.qualcomm.com
  4.84% |    3 |  4.37% |    34384 | aaron.falk@gmail.com
  4.84% |    3 |  4.02% |    31655 | adam@nostrum.com
  3.23% |    2 |  5.25% |    41359 | glenn.deen@nbcuni.com
  3.23% |    2 |  5.21% |    40990 | bob.hinden@gmail.com
  4.84% |    3 |  3.09% |    24345 | worley@ariadne.com
  1.61% |    1 |  5.90% |    46463 | stewart.bryant@gmail.com
  4.84% |    3 |  2.64% |    20768 | jrmitche@puck.nether.net
  3.23% |    2 |  4.25% |    33463 | suresh.krishnan@ericsson.com
  1.61% |    1 |  5.33% |    42005 | henning.schulzrinne@fcc.gov
  3.23% |    2 |  2.95% |    23219 | jri@google.com
  3.23% |    2 |  2.87% |    22589 | paul.kyzivat@comcast.net
  3.23% |    2 |  2.61% |    20512 | denis@ovsienko.info
  3.23% |    2 |  2.54% |    19968 | christer.holmberg@ericsson.com
  1.61% |    1 |  3.97% |    31227 | tasveren@sonusnet.com
  3.23% |    2 |  2.14% |    16877 | mohta@necom830.hpcl.titech.ac.jp
  3.23% |    2 |  1.95% |    15383 | ynir.ietf@gmail.com
  1.61% |    1 |  3.34% |    26303 | ranjitkav0811@gmail.com
  1.61% |    1 |  2.52% |    19830 | alan.b.johnston@gmail.com
  1.61% |    1 |  2.37% |    18641 | robert@raszuk.net
  1.61% |    1 |  1.96% |    15397 | daedulus@btconnect.com
  1.61% |    1 |  1.82% |    14360 | ietfjournal@isoc.org
  1.61% |    1 |  1.74% |    13732 | burmaa@datacom.mn
  1.61% |    1 |  1.57% |    12328 | narten@us.ibm.com
  1.61% |    1 |  1.45% |    11453 | gregimirsky@gmail.com
  1.61% |    1 |  1.36% |    10726 | acee@cisco.com
  1.61% |    1 |  1.32% |    10356 | mahoney@nostrum.com
  1.61% |    1 |  1.31% |    10284 | fred.l.templin@boeing.com
  1.61% |    1 |  1.27% |     9985 | spencerdawkins.ietf@gmail.com
  1.61% |    1 |  1.20% |     9467 | pkyzivat@alum.mit.edu
  1.61% |    1 |  1.17% |     9237 | gengxuesong@huawei.com
  1.61% |    1 |  1.12% |     8826 | ben@nostrum.com
  1.61% |    1 |  1.02% |     8027 | zhangmingui@huawei.com
  1.61% |    1 |  1.01% |     7938 | housley@vigilsec.com
  1.61% |    1 |  0.99% |     7825 | harald@alvestrand.no
  1.61% |    1 |  0.91% |     7129 | ietf@rozanak.com
  1.61% |    1 |  0.87% |     6885 | fluffy@iii.ca
  1.61% |    1 |  0.87% |     6829 | shares@ndzh.com
  1.61% |    1 |  0.80% |     6294 | rsk@gsp.org
  1.61% |    1 |  0.77% |     6025 | peter@akayla.com
  1.61% |    1 |  0.67% |     5292 | cpignata@cisco.com
  1.61% |    1 |  0.65% |     5122 | ietf-secretariat@ietf.org
--------+------+--------+----------+------------------------
100.00% |   62 |100.00% |   787389 | Total


From nobody Thu Mar 23 23:06:47 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B7EC01296C3; Thu, 23 Mar 2017 23:06:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Chair <chair@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: IETF subpoena processes update and a request
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org,chair@ietf.org
Message-ID: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com>
Date: Thu, 23 Mar 2017 23:06:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kw8N_wPiEOyklA3OswNJjfhrOhc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 06:06:41 -0000

Occasionally the IETF is served with a subpoena, typically to assist
finding prior art, documents and list discussions, in an effort to 
resolve patent disputes. We encourage everyone to just use our 
publicly available resources instead of formal requests, but we 
do get a few subpoenas every year. The IETF charges a fee 
for the service. The IETF makes these civil subpoenas and 
the primary response public at [1].

The IAOC Legal Committee has identified two issues with the 
existing procedures [2]. First off, practices have evolved somewhat
since the procedures were last updated in 2007, and are out of 
date. For instance, the subpoenas are today handled by IETF Legal
Counsel, the Legal Committee Chair, the IAD and record custodians
such as the Secretariat and the RFC Publisher. Others, such as the
IETF Chair are not usually involved, despite what the existing 
procedures say.

Secondly, due to a recent request that we received, we now
realize that the existing procedures for the publication of 
subpoenas do not address situations where we might be 
ordered or requested by law enforcement authorities to not 
post the subpoena and response. These may include cases
where a subpoena identifies a person or a company. These
are criminal rather than civil cases. We do not think it is 
necessarily obvious what we should do here. For instance, 
it might not be the right thing from the privacy point to 
post details of requests that identify a person. There are
more cases, and some tradeoffs to consider.

Large Internet companies that hold user data have developed
policies to deal with some of these issues. The IETF’s situation
is of course somewhat different. For instance, most data that
the IETF has is publicly visible anyway. There’s some additional
data of course, and even for the public data our ability to vouch
for the authenticity of, e.g., an Internet-Draft from a given year
can be important. And of course, unlike the large Internet
companies, our legal department consists of much smaller
force, at least in terms of number of people :-)

The IAOC legal committee believes that we need two things.
First, we need an update of the procedures in general, which
is largely an internal organisational matter. Secondly, we need
to develop a policy to answer the cases where confidentiality
is either requested by law enforcement authorities or is 
otherwise the right thing. This is a policy question which we
believe is best answered through community opinion, and
obviously also careful legal review.

The plan is for the Legal committee to do two things this
spring. First develop and post the general update, which we
post to the community for information and feedback. Second,
develop an initial approach regarding an answer to the policy
question and post it to the community for discussion. Please
participate in that discussion — we’ll send details about where
and how when we post the initial proposal. Once the community
discussion comes to a conclusion, we will adopt the policy as
defined by the community and the legal situation. If anyone
has input on this topic, let us know. It is also fine to send
suggestions before the proposal is posted.

Jari Arkko, IETF Chair

[1] https://iaoc.ietf.org/subpoenas.html
[2] https://iaoc.ietf.org/subpoena-procedures.html


From nobody Thu Mar 23 23:24:21 2017
Return-Path: <angela.y@email.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDE84129BF7; Thu, 23 Mar 2017 23:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.672
X-Spam-Level: 
X-Spam-Status: No, score=-4.672 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKSFCqIkYqIt; Thu, 23 Mar 2017 23:24:18 -0700 (PDT)
Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 673D01316A7; Thu, 23 Mar 2017 23:24:17 -0700 (PDT)
Received: from [70.187.165.193] by 3capp-mailcom-lxa02.server.lan (via HTTP); Fri, 24 Mar 2017 07:24:15 +0100
MIME-Version: 1.0
Message-ID: <trinity-6c06211f-0c35-46b1-9f77-9b121d18c51f-1490336655557@3capp-mailcom-lxa02>
From: Angela <angela.y@email.com>
To: ietf@ietf.org, chair@ietf.org
Subject: Re: IETF subpoena processes update and a request
Content-Type: text/html; charset=UTF-8
Date: Fri, 24 Mar 2017 07:24:15 +0100
Importance: normal
Sensitivity: Normal
In-Reply-To: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com>
X-UI-Message-Type: mail
X-Priority: 3
X-Provags-ID: V03:K0:q+R5VYuk/Pl1kpyfUnctIru7Y11bGxsREziJPHAA9J1 1WM/bDx/oD1zOh4c5kEggk9f22K/qWmiqeXdZCz6zFSztHGvcg Y/fLMEXmES/1L7wLAYiF190l0Y8L1NiXXLFYgY4ArhFLY/ITfi +7ZFBPWfofwTmgrYlGs69wKQYx5f2H0uu1xAeaDZtcM2YjU9Bp kRCJLuUvH/xxDsbxudB49WSP7yXHBEYonJD3JMWPPerrXcthgk hb8PPNbiTH4URwYpgVf/aH8zD+LkBKX0KR+4I21wPtD8I0mYV8 6JU5NYfZddFfOej0t4Hn4MZKO8D
X-UI-Out-Filterresults: notjunk:1;V01:K0:ZIfUPCxdhHA=:+VSzV1U2oTOPIfCITvwJOd he+DqZ1bXn3VMlFsCiXa/a4ugp2u9HHbrzRmT5w1j/Be3IFnm+nWTMkgc8b2J+Lbwsmn8+OHs WWv285kdI8BzeIfb0elhDBC/vWEEHkwsGKpTEUc/LSaXkffocKJmfd3BOZ5h+C1hn1dYVXSw9 hz8vfRvU9Or3wzWRUHBZlCPdT2buxd4r+doF/ZczXjmOkKGRy7EbsYstxKsWrSmzGCkHKCSsn Z5nLo6frIgto41CJEbxtYwn0840aFzFACCAi4SvfAe/1n08Ap8nr8ILWWVAY82MjHstI72E2k rxr72mJgyTlhLxttCvvskw8OkWrMZ3rkZdH7+erptTSoTKMI3gY1jOXTxjBclRhWeU8aU+/96 Zut9te/G88Pv9Bzg8paSaa8LcAemr1Qag6TgHEl3SWDfgQM1a07hjhJOzGXODY1NBt3t7iznY eIAYkwy6kw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iU8v2yH68eh-epJ4V-cmknuPxi8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 06:24:20 -0000

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>I&#39;ve forwarded this to SBWASP, OC OWASP, &amp; LA OWASP &amp; my patent attorney as well :)
<div>&nbsp;
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Sent:</b>&nbsp;Thursday, March 23, 2017 at 11:06 PM<br/>
<b>From:</b>&nbsp;&quot;IETF Chair&quot; &lt;chair@ietf.org&gt;<br/>
<b>To:</b>&nbsp;&quot;IETF Announcement List&quot; &lt;ietf-announce@ietf.org&gt;<br/>
<b>Cc:</b>&nbsp;ietf@ietf.org<br/>
<b>Subject:</b>&nbsp;IETF subpoena processes update and a request</div>

<div name="quoted-content">Occasionally the IETF is served with a subpoena, typically to assist<br/>
finding prior art, documents and list discussions, in an effort to<br/>
resolve patent disputes. We encourage everyone to just use our<br/>
publicly available resources instead of formal requests, but we<br/>
do get a few subpoenas every year. The IETF charges a fee<br/>
for the service. The IETF makes these civil subpoenas and<br/>
the primary response public at [1].<br/>
<br/>
The IAOC Legal Committee has identified two issues with the<br/>
existing procedures [2]. First off, practices have evolved somewhat<br/>
since the procedures were last updated in 2007, and are out of<br/>
date. For instance, the subpoenas are today handled by IETF Legal<br/>
Counsel, the Legal Committee Chair, the IAD and record custodians<br/>
such as the Secretariat and the RFC Publisher. Others, such as the<br/>
IETF Chair are not usually involved, despite what the existing<br/>
procedures say.<br/>
<br/>
Secondly, due to a recent request that we received, we now<br/>
realize that the existing procedures for the publication of<br/>
subpoenas do not address situations where we might be<br/>
ordered or requested by law enforcement authorities to not<br/>
post the subpoena and response. These may include cases<br/>
where a subpoena identifies a person or a company. These<br/>
are criminal rather than civil cases. We do not think it is<br/>
necessarily obvious what we should do here. For instance,<br/>
it might not be the right thing from the privacy point to<br/>
post details of requests that identify a person. There are<br/>
more cases, and some tradeoffs to consider.<br/>
<br/>
Large Internet companies that hold user data have developed<br/>
policies to deal with some of these issues. The IETF&rsquo;s situation<br/>
is of course somewhat different. For instance, most data that<br/>
the IETF has is publicly visible anyway. There&rsquo;s some additional<br/>
data of course, and even for the public data our ability to vouch<br/>
for the authenticity of, e.g., an Internet-Draft from a given year<br/>
can be important. And of course, unlike the large Internet<br/>
companies, our legal department consists of much smaller<br/>
force, at least in terms of number of people :-)<br/>
<br/>
The IAOC legal committee believes that we need two things.<br/>
First, we need an update of the procedures in general, which<br/>
is largely an internal organisational matter. Secondly, we need<br/>
to develop a policy to answer the cases where confidentiality<br/>
is either requested by law enforcement authorities or is<br/>
otherwise the right thing. This is a policy question which we<br/>
believe is best answered through community opinion, and<br/>
obviously also careful legal review.<br/>
<br/>
The plan is for the Legal committee to do two things this<br/>
spring. First develop and post the general update, which we<br/>
post to the community for information and feedback. Second,<br/>
develop an initial approach regarding an answer to the policy<br/>
question and post it to the community for discussion. Please<br/>
participate in that discussion &mdash; we&rsquo;ll send details about where<br/>
and how when we post the initial proposal. Once the community<br/>
discussion comes to a conclusion, we will adopt the policy as<br/>
defined by the community and the legal situation. If anyone<br/>
has input on this topic, let us know. It is also fine to send<br/>
suggestions before the proposal is posted.<br/>
<br/>
Jari Arkko, IETF Chair<br/>
<br/>
[1] <a href="https://iaoc.ietf.org/subpoenas.html" target="_blank">https://iaoc.ietf.org/subpoenas.html</a><br/>
[2] <a href="https://iaoc.ietf.org/subpoena-procedures.html" target="_blank">https://iaoc.ietf.org/subpoena-procedures.html</a><br/>
&nbsp;</div>
</div>
</div>
</div></div></body></html>


From nobody Fri Mar 24 06:20:48 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 10BB41296CC; Fri, 24 Mar 2017 06:20:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Chair <chair@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: IETF-98 Highlights
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: chair@ietf.org,ietf@ietf.org
Message-ID: <149036163702.11846.7672875822645703367.idtracker@ietfa.amsl.com>
Date: Fri, 24 Mar 2017 06:20:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VQyAwy-wD7CT8wEs-DBzK81FHJ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 13:20:37 -0000

The Chicago IETF begins in a couple of days, and I wanted to point
people to a few highlights from my perspective. Of course, with over
hundred working groups, the IETF’s work program is quite diverse,
and different people are interested in different topics. But these topics
were particularly interesting, at least for me:

https://www.ietf.org/blog/2017/03/ietf-98-highlights/

See you soon in Chicago or over the net!

Jari Arkko, IETF Chair


From nobody Fri Mar 24 06:25:58 2017
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 A499E129676; Fri, 24 Mar 2017 06:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fsq3A9C7qcKL; Fri, 24 Mar 2017 06:25:56 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F50A12951A; Fri, 24 Mar 2017 06:25:56 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1crPE3-0004n2-4w; Fri, 24 Mar 2017 13:25:55 +0000
Date: Fri, 24 Mar 2017 08:25:55 -0500
Message-ID: <m2k27eg61o.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Chair <chair@ietf.org>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request
In-Reply-To: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M5tp1QZaQZGxsqHW5Wbh1z43N3o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 13:25:58 -0000

in what legal juristiction is the ietf?  in what juristiction is the
subpoena served?  how does an american (for example) gag order apply to
a nebulous entity such as the ietf?

can we move to iceland?

randy


From nobody Fri Mar 24 06:30:14 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F37901296E0; Fri, 24 Mar 2017 06:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5togToIghG4p; Fri, 24 Mar 2017 06:30:11 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A93FF12951A; Fri, 24 Mar 2017 06:30:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 997CE3D527FB; Fri, 24 Mar 2017 09:30:10 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfCiVROcTKJA; Fri, 24 Mar 2017 09:30:09 -0400 (EDT)
Received: from [10.252.203.183] (unknown [65.112.8.196]) by sobco.sobco.com (Postfix) with ESMTPSA id A07673D527EC; Fri, 24 Mar 2017 09:30:09 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IETF subpoena processes update and a request
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <m2k27eg61o.wl-randy@psg.com>
Date: Fri, 24 Mar 2017 09:30:08 -0400
Cc: IETF Chair <chair@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o5255UidL6Z5Afyph0yKiy42O8w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 13:30:13 -0000

all good questions - any suggested answers?

Scott

> On Mar 24, 2017, at 9:25 AM, Randy Bush <randy@psg.com> wrote:
> 
> in what legal juristiction is the ietf?  in what juristiction is the
> subpoena served?  how does an american (for example) gag order apply to
> a nebulous entity such as the ietf?
> 
> can we move to iceland?
> 
> randy
> 


From nobody Fri Mar 24 06:35:43 2017
Return-Path: <michael.cameron@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 47EC61296CC; Fri, 24 Mar 2017 06:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qYi7pFtRGOWt; Fri, 24 Mar 2017 06:35:40 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D2561204DA; Fri, 24 Mar 2017 06:35:40 -0700 (PDT)
X-AuditID: c6180641-c53ff70000000a06-5c-58d4da511120
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by  (Symantec Mail Security) with SMTP id 77.04.02566.15AD4D85; Fri, 24 Mar 2017 09:35:32 +0100 (CET)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0319.002; Fri, 24 Mar 2017 09:35:36 -0400
From: Michael Cameron <michael.cameron@ericsson.com>
To: Scott Bradner <sob@sobco.com>, Randy Bush <randy@psg.com>
CC: IETF Chair <chair@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: RE: IETF subpoena processes update and a request
Thread-Topic: IETF subpoena processes update and a request
Thread-Index: AQHSpGTmtNSGPJwUVE2WY6KD+TaHe6GkPpmAgAABLQD//738sA==
Date: Fri, 24 Mar 2017 13:35:35 +0000
Message-ID: <36BAA6A693139D4BBCB37CCCA660E08A18EC642F@eusaamb101.ericsson.se>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com> <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com>
In-Reply-To: <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyuXRPoG7IrSsRBtPvSVqcXTyHzeLZxvks Fs9aXzJZHO9UdmDxWLLkJ5PH1JmzGT1eHPjGHMAcxWWTkpqTWZZapG+XwJXRe2E6U8Ff9ooX W74yNjBuZ+ti5OSQEDCRmP1qF5DNxSEksJ5R4lHvX0YIZzmjxKT999m7GDk42ICqnj9jAWkQ EbCVuLuyiRXEZhZwkph+owFskLCApcTJl4fYIGqsJJ4/vsYIYTtJnD11kBnEZhFQlVizvYMV ZCSvgK/E/VMqEKsWMEpM3HeJCaSGE2j++gcbweYzCohJfD+1hglil7jErSfzmSCOFpBYsuc8 M4QtKvHy8T9WCFtJYtLSc1C36Ugs2P2JDcLWlli28DVYPa+AoMTJmU9YJjCKzkIydhaSlllI WmYhaVnAyLKKkaO0uCAnN93IcBMjMFKOSbA57mDc2+t5iFGAg1GJh/fD4SsRQqyJZcWVuYcY JTiYlUR498pejRDiTUmsrEotyo8vKs1JLT7EKM3BoiTO+678QoSQQHpiSWp2ampBahFMlomD U6qBUdSoaNn9FruJ7PHZ3bf0Jiesmu7SMm2G2tzT3+dMv/ts5YYMvf0aHHoPNf24jiybqRCr /npr3ESd+s932yfPtf411S9Na7vKPMdL2i2b5if5FExMdjrP9OLT4f+Ob9z8wyvYPzvueqkS anxpwVyp13oHHu9a8eG/+mrn3Ji1c4zNN3idCftn3K3EUpyRaKjFXFScCAAXhFh5kAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x3PymHWIp2whb9Mei5pcSqvpHC4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 13:35:42 -0000

Isn't the IETF part of the ISOC?

https://tools.ietf.org/html/rfc2134

The address, including street and number, of the initial registered office =
of the corporation is c/o C T Corporation System, 1030 15th Street, N.W., W=
ashington, D.C. 20005, and the name of its initial registered agent at such=
 address is C T Corporation System.

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Scott Bradner
Sent: Friday, March 24, 2017 8:30 AM
To: Randy Bush <randy@psg.com>
Cc: IETF Chair <chair@ietf.org>; IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request

all good questions - any suggested answers?

Scott

> On Mar 24, 2017, at 9:25 AM, Randy Bush <randy@psg.com> wrote:
>=20
> in what legal juristiction is the ietf?  in what juristiction is the=20
> subpoena served?  how does an american (for example) gag order apply=20
> to a nebulous entity such as the ietf?
>=20
> can we move to iceland?
>=20
> randy
>=20


From nobody Fri Mar 24 06:39:08 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E2CF129BF9; Fri, 24 Mar 2017 06:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TdRl7pscd6jR; Fri, 24 Mar 2017 06:39:02 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C32AE1296C8; Fri, 24 Mar 2017 06:38:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id C32A63D52B75; Fri, 24 Mar 2017 09:38:54 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U_tbIWpEL8Vu; Fri, 24 Mar 2017 09:38:53 -0400 (EDT)
Received: from [10.252.203.183] (unknown [65.112.8.196]) by sobco.sobco.com (Postfix) with ESMTPSA id 4E3923D52B67; Fri, 24 Mar 2017 09:38:53 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IETF subpoena processes update and a request
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <36BAA6A693139D4BBCB37CCCA660E08A18EC642F@eusaamb101.ericsson.se>
Date: Fri, 24 Mar 2017 09:38:52 -0400
Cc: Randy Bush <randy@psg.com>, IETF Chair <chair@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <61300916-3BE0-4818-BF29-A32E11A13AFB@sobco.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com> <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com> <36BAA6A693139D4BBCB37CCCA660E08A18EC642F@eusaamb101.ericsson.se>
To: Michael Cameron <michael.cameron@ericsson.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aaQW-1V5zNyQvgu9Odn7NPCkFG8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 13:39:04 -0000

from the IETF home page

The Internet Engineering Task Force (IETF) is an organized activity of =
the Internet Society (ISOC).

(see also RFC 2028)

i.e., the IETF is not a legal entity itself but the ISOC has been the =
legal contact point=20

Scott

> On Mar 24, 2017, at 9:35 AM, Michael Cameron =
<michael.cameron@ericsson.com> wrote:
>=20
> Isn't the IETF part of the ISOC?
>=20
> https://tools.ietf.org/html/rfc2134
>=20
> The address, including street and number, of the initial registered =
office of the corporation is c/o C T Corporation System, 1030 15th =
Street, N.W., Washington, D.C. 20005, and the name of its initial =
registered agent at such address is C T Corporation System.
>=20
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Scott Bradner
> Sent: Friday, March 24, 2017 8:30 AM
> To: Randy Bush <randy@psg.com>
> Cc: IETF Chair <chair@ietf.org>; IETF Rinse Repeat <ietf@ietf.org>
> Subject: Re: IETF subpoena processes update and a request
>=20
> all good questions - any suggested answers?
>=20
> Scott
>=20
>> On Mar 24, 2017, at 9:25 AM, Randy Bush <randy@psg.com> wrote:
>>=20
>> in what legal juristiction is the ietf?  in what juristiction is the=20=

>> subpoena served?  how does an american (for example) gag order apply=20=

>> to a nebulous entity such as the ietf?
>>=20
>> can we move to iceland?
>>=20
>> randy
>>=20
>=20


From nobody Fri Mar 24 06:41:23 2017
Return-Path: <michael.cameron@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 E916E1296C8; Fri, 24 Mar 2017 06:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8AUSPMLmx_i1; Fri, 24 Mar 2017 06:41:18 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC1EC129C39; Fri, 24 Mar 2017 06:41:17 -0700 (PDT)
X-AuditID: c6180641-c3fff70000000a06-18-58d4dba33b37
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by  (Symantec Mail Security) with SMTP id D7.34.02566.3ABD4D85; Fri, 24 Mar 2017 09:41:09 +0100 (CET)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0319.002; Fri, 24 Mar 2017 09:41:11 -0400
From: Michael Cameron <michael.cameron@ericsson.com>
To: Scott Bradner <sob@sobco.com>
CC: Randy Bush <randy@psg.com>, IETF Chair <chair@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: RE: IETF subpoena processes update and a request
Thread-Topic: IETF subpoena processes update and a request
Thread-Index: AQHSpGTmtNSGPJwUVE2WY6KD+TaHe6GkPpmA///AnoqAAABVwA==
Date: Fri, 24 Mar 2017 13:41:10 +0000
Message-ID: <36BAA6A693139D4BBCB37CCCA660E08A18EC648F@eusaamb101.ericsson.se>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com> <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com> <36BAA6A693139D4BBCB37CCCA660E08A18EC642F@eusaamb101.ericsson.se> <61300916-3BE0-4818-BF29-A32E11A13AFB@sobco.com>
In-Reply-To: <61300916-3BE0-4818-BF29-A32E11A13AFB@sobco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyuXRPlO7S21ciDObtN7I4u3gOm8WzjfNZ LJ61vmSyON6p7MDisWTJTyaPqTNnM3q8OPCNOYA5issmJTUnsyy1SN8ugStj1d6rjAVr+So+ r/jN1MB4lruLkYNDQsBEYtOTjC5GLg4hgfWMEvv6m9ggnOWMEs/O/WABKWIDKnr+DMjk5BAR UJQ4uu4/E4jNLJAgsebaabC4sIClxMmXh9ggaqwknj++xghhO0nsuPuaHcRmEVCV+LXwFyuI zSvgK9HedIcZYtd0JontX3vBGjgFbCWO79kC1sAoICbx/dQaqGXiEreezAezJQQEJJbsOc8M YYtKvHz8jxXCVpKYtPQcK0S9jsSC3Z/YIGxtiWULXzNDLBaUODnzCcsERtFZSMbOQtIyC0nL LCQtCxhZVjFylBYX5OSmGxluYgRGyjEJNscdjHt7PQ8xCnAwKvHwfjh8JUKINbGsuDL3EKME B7OSCO9e2asRQrwpiZVVqUX58UWlOanFhxilOViUxHnflV+IEBJITyxJzU5NLUgtgskycXBK NTBmNn+e8Lv1sWp+n/Otz0kzf+x1PXV465SbsYkv2yYuZ8vROJ8dojCpO2dvferky8oByeuW u/HaLhS0PewtfW36zr7CAwrvOMUTi7577GdeaDBn9fEdqptCbWydO16K+dlG2mzTeun26ilT T2yxAmfRz6rMA+uXeh+cU3XRiSup5m7evzMnL8spsRRnJBpqMRcVJwIA1cLElZACAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JdimeofLjZZNxUyJc2DppfFO5a4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 13:41:22 -0000

Confirmed that you serve the IETF with a subpoena by serving ISOC.

-----Original Message-----
From: Scott Bradner [mailto:sob@sobco.com]=20
Sent: Friday, March 24, 2017 8:39 AM
To: Michael Cameron <michael.cameron@ericsson.com>
Cc: Randy Bush <randy@psg.com>; IETF Chair <chair@ietf.org>; IETF Rinse Rep=
eat <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request

from the IETF home page

The Internet Engineering Task Force (IETF) is an organized activity of the =
Internet Society (ISOC).

(see also RFC 2028)

i.e., the IETF is not a legal entity itself but the ISOC has been the legal=
 contact point=20

Scott

> On Mar 24, 2017, at 9:35 AM, Michael Cameron <michael.cameron@ericsson.co=
m> wrote:
>=20
> Isn't the IETF part of the ISOC?
>=20
> https://tools.ietf.org/html/rfc2134
>=20
> The address, including street and number, of the initial registered offic=
e of the corporation is c/o C T Corporation System, 1030 15th Street, N.W.,=
 Washington, D.C. 20005, and the name of its initial registered agent at su=
ch address is C T Corporation System.
>=20
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Scott Bradner
> Sent: Friday, March 24, 2017 8:30 AM
> To: Randy Bush <randy@psg.com>
> Cc: IETF Chair <chair@ietf.org>; IETF Rinse Repeat <ietf@ietf.org>
> Subject: Re: IETF subpoena processes update and a request
>=20
> all good questions - any suggested answers?
>=20
> Scott
>=20
>> On Mar 24, 2017, at 9:25 AM, Randy Bush <randy@psg.com> wrote:
>>=20
>> in what legal juristiction is the ietf?  in what juristiction is the=20
>> subpoena served?  how does an american (for example) gag order apply=20
>> to a nebulous entity such as the ietf?
>>=20
>> can we move to iceland?
>>=20
>> randy
>>=20
>=20


From nobody Fri Mar 24 06:49:19 2017
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 384971296F6; Fri, 24 Mar 2017 06:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ik8idVr2WeYn; Fri, 24 Mar 2017 06:49:16 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CB0A12940F; Fri, 24 Mar 2017 06:49:16 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1crPab-0004zU-5i; Fri, 24 Mar 2017 13:49:13 +0000
Date: Fri, 24 Mar 2017 08:49:12 -0500
Message-ID: <m2h92ig4yv.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Scott Bradner <sob@sobco.com>
Cc: IETF Chair <chair@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request
In-Reply-To: <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com> <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tdYdH2raAscT6wyyfDRas4FlMV4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 13:49:18 -0000

>> in what legal juristiction is the ietf?  in what juristiction is the
>> subpoena served?  how does an american (for example) gag order apply to
>> a nebulous entity such as the ietf?
>
> all good questions - any suggested answers?

IANAL, IANAL, IANAL, IANAL, IANAL, IANAL, IANAL, IANAL, IANAL, IANAL

the ietf does not exist, but has a service address in the states.  the
latter could easily be changed, e.g. to genev=E9.

"is an organized activity of" seems vague and could be interpreted as
the ietf is, for legal purposes, subsumed by isoc.  this was likely not
an accident.

i assume the subpoena with the gag order was in the states, and the
server wore a brown shirt.

it would be cost effective not to have to get a us court decision
whether or not the subpoena/gag applied to the ietf.

>> can we move to iceland?

it is not an accident that cryptech's servers are in iceland and admin
in k=F8benhavn.

i would be asking george if he minded if the eff was consulted; though
they are likely already a bit overwhelmed with brown shirts.

randy


From nobody Fri Mar 24 06:55:27 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 658B3129B2B for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 06:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hYuCvi8E23eg for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 06:55:23 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DC8912971B for <ietf@ietf.org>; Fri, 24 Mar 2017 06:55:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 4B5503D53093 for <ietf@ietf.org>; Fri, 24 Mar 2017 09:55:22 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zOsSt6_GgePK for <ietf@ietf.org>; Fri, 24 Mar 2017 09:55:22 -0400 (EDT)
Received: from [10.252.203.183] (unknown [65.112.8.196]) by sobco.sobco.com (Postfix) with ESMTPSA id 15C163D53085 for <ietf@ietf.org>; Fri, 24 Mar 2017 09:55:22 -0400 (EDT)
From: Scott Bradner <sob@sobco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IETF subpoena processes update and a request
Date: Fri, 24 Mar 2017 09:55:21 -0400
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
In-Reply-To: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com>
Message-Id: <1F1EFD03-2C57-402D-B9B5-D5494C0146F6@sobco.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rroYe03wQdPEqZmno69JIhIJJVw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 13:55:26 -0000

I expect that the IAOC legal committee will post the initial approach =
and discussion request that Jari mentioned early next=20
week (well before the plenary :-) )

Scott


From nobody Fri Mar 24 09:27:34 2017
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 DD6B71297BD; Fri, 24 Mar 2017 09:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNMACwR0hujl; Fri, 24 Mar 2017 09:27:31 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5AD3120727; Fri, 24 Mar 2017 09:27:30 -0700 (PDT)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1crS3d-000DUI-J3; Fri, 24 Mar 2017 12:27:21 -0400
Date: Fri, 24 Mar 2017 12:27:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, Scott Bradner <sob@sobco.com>
cc: IETF Chair <chair@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request
Message-ID: <33DAE0FB5054D5E9B195CFCA@PSB>
In-Reply-To: <m2h92ig4yv.wl-randy@psg.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com> <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com> <m2h92ig4yv.wl-randy@psg.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZgDEXl4kEnXkOwvEWKUuh4nY7xM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 16:27:33 -0000

--On Friday, March 24, 2017 08:49 -0500 Randy Bush
<randy@psg.com> wrote:

>>> in what legal juristiction is the ietf?  in what
>>> juristiction is the subpoena served?  how does an american
>>> (for example) gag order apply to a nebulous entity such as
>>> the ietf?
>>=20
>> all good questions - any suggested answers?
>=20
> IANAL, IANAL, IANAL, IANAL, IANAL, IANAL, IANAL, IANAL, IANAL,
> IANAL
>=20
> the ietf does not exist, but has a service address in the
> states.  the latter could easily be changed, e.g. to =
genev=C3=A9.
>=20
> "is an organized activity of" seems vague and could be
> interpreted as the ietf is, for legal purposes, subsumed by
> isoc.  this was likely not an accident.
>=20
> i assume the subpoena with the gag order was in the states,
> and the server wore a brown shirt.
>...

Randy,

IANAL either, but it seems to me that Jari's note suggests a
more basic question that is almost independent of jurisdictional
issues.  Suppose the IETF (or whomever) receives a subpoena that
names individuals or companies in a way that might be
unfortunate, contain implicit accusations that might be
completely unfounded,  or even, in the opinion of those parties
if they knew, were libelous, and suppose it directs IETF to not
disclose the subpoena in any way.  Without offering anything
resembling a legal opinion, it probably makes a difference
whether the subpoena is associated with a law enforcement action
rather than the civil actions for which I think the policies
were designed.

Whether we are in a position to ignore or fight the subpoena or
not and independent of what we think about the alleged law
enforcement entities involved (including their choice of shirt
covers), it seems to me that a policy of posting subpoenas
raises several issues (with Jari's note explicitly identifying
the first).   "Lawyer" in parentheses identifies a question that
I think we need advice about if I'm not the only one who thinks
it is relevant but that would probably not be profitable to
debate on this list, at least before we have that advice.

I believe that many of the issues below would apply also to a
subpoena in a law enforcement action directed against an
individual or company (rather than, e.g., asking for
authenticated documents) even if it contained no demand for
confidentiality (again, IANAL).

(1) If the subpoena names an individual or company, is it
consistent with our privacy policies to disclose those names?

(2) If we think the answer is to avoid disclosing names by
posting the subpoena in redacted form (e.g., to eliminate
names), does the community want the IETF Trustees (or a
committee appointed by them and with membership and parties
consulted sometimes being less than transparent) to go into the
redaction business?  Does it make a difference if any
attorney-client confidentiality provisions apply only to ISOC or
the IAOC/IETF Trustees and not the community?  Would that
constitute a different sort of privacy or transparency problem
by encouraging members of the community to keep secrets from
each other?

(3) (Lawyer) If the subpoena's content, or even the fact that it
has been issued and served, implies things that the named person
or company would consider libelous if disclosed, does the IETF
become a party to the libel by making the subpoena public
(whether or not told to not do that)?

(4) (Lawyer)  I believe, but people with applicable professional
legal credentials and experience should confirm, that, if we
want to base the answers to any of these questions (including
whether the subpoena should be resisted if that is a
possibility) on knowing what sort of action is involved, based
on what laws, etc., we should get over it because a subpoena may
not disclose that information.=20

(5) (Lawyer) I understand that it is generally harder to serve
civil subpoenas across international boundaries than criminal
(or other law enforcement-initiated ones although there are
variations even within those categories.  If a criminal (or
other law enforcement) action is involved, how much protection
would "move to Iceland / Geneva/ somewhere else" provide.   Of
course, most, if not all, of those places have their own legal
systems and processes and moving there (if even if were
possible) might provide more protection from the processes of
the US but obviously less from those of the new host country.

(6) (Lawyer) Assuming the IETF (or IETF Trust) were to establish
some sort of locus/ HQ in Iceland / Geneva/ Lower Slobbovia and
claim that subpoenas need to be served there, would that provide
any significant protection, especially from subpoenas initiated
by law enforcement, or would they just treat whatever we would
say about where to serve the subpoenas and instead seek out ISOC
or AMS offices or particular named individuals in a convenient
country, serve them, and make the international issues their
problem.  I note in that regard that, while Finland may be a
good place to live, the ISOC Chair, AMS officers and HQ, and
incoming IETF Chair are all based in the US.

I have no reason to believe that those are all of the questions
that should be asked, but they are a start.

   john


From nobody Fri Mar 24 09:33:03 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3659C1294CF for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 09:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02p9JDcizeIE for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 09:33:00 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D24C120727 for <ietf@ietf.org>; Fri, 24 Mar 2017 09:33:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 1068F3D55BFE for <ietf@ietf.org>; Fri, 24 Mar 2017 12:32:59 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qP-ImoGDAhn for <ietf@ietf.org>; Fri, 24 Mar 2017 12:32:57 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 402D33D55BED for <ietf@ietf.org>; Fri, 24 Mar 2017 12:32:57 -0400 (EDT)
From: "Scott O. Bradner" <sob@sobco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IETF subpoena processes update and a request
Date: Fri, 24 Mar 2017 12:32:57 -0400
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com> <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com> <m2h92ig4yv.wl-randy@psg.com> <33DAE0FB5054D5E9B195CFCA@PSB>
To: IETF Rinse Repeat <ietf@ietf.org>
In-Reply-To: <33DAE0FB5054D5E9B195CFCA@PSB>
Message-Id: <D85AC54E-71CA-4700-9AC2-2923E5DB705C@sobco.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ex0_eW3WVIn2Azx11-CJIFM5GJM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 16:33:01 -0000

> On Mar 24, 2017, at 12:27 PM, John C Klensin <john-ietf@jck.com> wrote:
> 
> IANAL either, but it seems to me that Jari's note suggests a
> more basic question that is almost independent of jurisdictional
> issues.  Suppose the IETF (or whomever) receives a subpoena that
> names individuals or companies in a way that might be
> unfortunate, contain implicit accusations that might be
> completely unfounded,  or even, in the opinion of those parties
> if they knew, were libelous, and suppose it directs IETF to not
> disclose the subpoena in any way.  Without offering anything
> resembling a legal opinion, it probably makes a difference
> whether the subpoena is associated with a law enforcement action
> rather than the civil actions for which I think the policies
> were designed.

I know of no case of a civil subpoena that included a gag order

& yes, the procedures were deigned for civil cases (like patent prior art)

Scott


From nobody Fri Mar 24 09:47:21 2017
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 3DF63127078; Fri, 24 Mar 2017 09:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.022
X-Spam-Level: 
X-Spam-Status: No, score=-7.022 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kMtPatgOycRD; Fri, 24 Mar 2017 09:47:18 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53E68120727; Fri, 24 Mar 2017 09:47:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490374038; x=1521910038; h=from:to:subject:date:message-id:in-reply-to:references: mime-version:content-transfer-encoding; bh=sQlaUj4U1C2JXNxL4yzfeKQC6kwAshXZCkseapV4khQ=; b=WwY702xt879KmIb+AKPqjRBeaGpu/yJB49tYYtNZQGMZkyHUq9v32Mee 5JW625HDofB+3e6AIzt27LPxD6Cq6Y3IUHC3gEvM6tEjupmJJCeogGvfa 0Dlfwc+DCwPIAU0p65Rw9UAgpLTbqSJ+wcnnnjdbOaXAGvQlE+r/h1RHY s=;
X-IronPort-AV: E=Sophos;i="5.36,215,1486454400"; d="scan'208";a="367894461"
Received: from unknown (HELO ironmsg02-R.qualcomm.com) ([10.53.140.106]) by wolverine02.qualcomm.com with ESMTP; 24 Mar 2017 09:47:15 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8476"; a="925529008"
X-MGA-submission: =?us-ascii?q?MDHii+pdt/+FGnGuQYSPLAo9C7EPDlyXF4yO75?= =?us-ascii?q?qg/ImznO1NFQ2kOJZFS9VZN1JI0GRGb9+5eIzkVWWcVRAjuPtJTs9zfW?= =?us-ascii?q?L3TvbmqmtLlROV+dqjIgKFAkJ87UO+Ab6yEOtN3XGKtoHK3mPzuA5H0w?= =?us-ascii?q?XV?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 24 Mar 2017 09:47:15 -0700
Received: from [10.64.118.210] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 24 Mar 2017 09:47:14 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <ietf@ietf.org>, IETF Chair <chair@ietf.org>
Subject: Re: IETF subpoena processes update and a request
Date: Fri, 24 Mar 2017 11:47:13 -0500
Message-ID: <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com>
In-Reply-To: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WhGSe894XVQrUL8JeyrQxP8_-C8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 16:47:20 -0000

To deal with the second issue, it seems to me that we should address the 
first issue by making it crystal clear in the procedures that the 
subpoena must go to the entire IESG, not just the chair, and that 
whatever action is taken on the subpoena be approved by the IESG (with 
advice of counsel). If the entire IESG gets a copy of the subpoena, and  
our procedures make it clear to any court or other issuing authority 
that more than one person outside of their jurisdiction will be seeing 
the subpoena, perhaps that will mitigate the second issue.

If the current de-facto procedure has removed IETF leadership from the 
process, it is a problem that should be fixed not by changing the 
documented procedures, but by returning to them. It may be that most of 
the time IETF leadership ends up simply nodding at counsel, the IAOC, 
the IAD, etc., but they should absolutely be included.

Like others, I wonder about the prudence of naming ISOC (and certainly 
ISOC in the US) as the recipient for legal service. I'd like to hear 
from lawyers about other possibilities.

pr

On 24 Mar 2017, at 1:06, IETF Chair wrote:

> Occasionally the IETF is served with a subpoena, typically to assist
> finding prior art, documents and list discussions, in an effort to
> resolve patent disputes. We encourage everyone to just use our
> publicly available resources instead of formal requests, but we
> do get a few subpoenas every year. The IETF charges a fee
> for the service. The IETF makes these civil subpoenas and
> the primary response public at [1].
>
> The IAOC Legal Committee has identified two issues with the
> existing procedures [2]. First off, practices have evolved somewhat
> since the procedures were last updated in 2007, and are out of
> date. For instance, the subpoenas are today handled by IETF Legal
> Counsel, the Legal Committee Chair, the IAD and record custodians
> such as the Secretariat and the RFC Publisher. Others, such as the
> IETF Chair are not usually involved, despite what the existing
> procedures say.
>
> Secondly, due to a recent request that we received, we now
> realize that the existing procedures for the publication of
> subpoenas do not address situations where we might be
> ordered or requested by law enforcement authorities to not
> post the subpoena and response. These may include cases
> where a subpoena identifies a person or a company. These
> are criminal rather than civil cases. We do not think it is
> necessarily obvious what we should do here. For instance,
> it might not be the right thing from the privacy point to
> post details of requests that identify a person. There are
> more cases, and some tradeoffs to consider.
>
> Large Internet companies that hold user data have developed
> policies to deal with some of these issues. The IETF’s situation
> is of course somewhat different. For instance, most data that
> the IETF has is publicly visible anyway. There’s some additional
> data of course, and even for the public data our ability to vouch
> for the authenticity of, e.g., an Internet-Draft from a given year
> can be important. And of course, unlike the large Internet
> companies, our legal department consists of much smaller
> force, at least in terms of number of people :-)
>
> The IAOC legal committee believes that we need two things.
> First, we need an update of the procedures in general, which
> is largely an internal organisational matter. Secondly, we need
> to develop a policy to answer the cases where confidentiality
> is either requested by law enforcement authorities or is
> otherwise the right thing. This is a policy question which we
> believe is best answered through community opinion, and
> obviously also careful legal review.
>
> The plan is for the Legal committee to do two things this
> spring. First develop and post the general update, which we
> post to the community for information and feedback. Second,
> develop an initial approach regarding an answer to the policy
> question and post it to the community for discussion. Please
> participate in that discussion — we’ll send details about where
> and how when we post the initial proposal. Once the community
> discussion comes to a conclusion, we will adopt the policy as
> defined by the community and the legal situation. If anyone
> has input on this topic, let us know. It is also fine to send
> suggestions before the proposal is posted.
>
> Jari Arkko, IETF Chair
>
> [1] https://iaoc.ietf.org/subpoenas.html
> [2] https://iaoc.ietf.org/subpoena-procedures.html


From nobody Fri Mar 24 10:53:04 2017
Return-Path: <jari.arkko@piuha.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 EEC4712984B for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 10:53:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Es3_DYB1HG30 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 10:53:00 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7B17012984A for <ietf@ietf.org>; Fri, 24 Mar 2017 10:53:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E3C282CFD8; Fri, 24 Mar 2017 19:52:58 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ooy7rKhxgiPg; Fri, 24 Mar 2017 19:52:58 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id EDA602CC38; Fri, 24 Mar 2017 19:52:57 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: IETF subpoena processes update and a request
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <33DAE0FB5054D5E9B195CFCA@PSB>
Date: Fri, 24 Mar 2017 12:52:57 -0500
Cc: Scott Bradner <sob@sobco.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <BA6001D2-E97E-4211-B7F7-A27133C75A1D@piuha.net>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com> <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com> <m2h92ig4yv.wl-randy@psg.com> <33DAE0FB5054D5E9B195CFCA@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JJripxiL76U2ImXllNSxSsBeHz0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 17:53:03 -0000

Thanks John, this was useful.

Jari


From nobody Fri Mar 24 11:14:11 2017
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 C39FC12985B for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 11:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MplbqvwBi0ys for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 11:14:06 -0700 (PDT)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFA82129862 for <ietf@ietf.org>; Fri, 24 Mar 2017 11:14:04 -0700 (PDT)
Received: by mail-it0-x22c.google.com with SMTP id 190so9205664itm.0 for <ietf@ietf.org>; Fri, 24 Mar 2017 11:14:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=7QT2fx0NGhKYgxf4qw530Y7idwlaQ1ESvZwqsheEguc=; b=clQVQm8ymEDg1YgEilVe0rgO+VyhBJ82xv/lwtXsU4zrtKPoT+Ug6U7JpXzHNlI4Rr 9YSLCdRZEh2xsjQiahYeZPcKA8QvIxZl8NdHKfEBHn9sPrboEzr3HE80H8Xol16+tiwz NZ/baxJWmUrH8YyACJQ/UQuI3fWLvryWbgqDCeuD8pQadjGQWb7s6gK5qQC2yaUqHWZ6 yyiMMs0cABEgrH99We/VaGCogxhvlSZjGmadk4qdTASoEHe/OrvB5j4XjcDsG63PgRld CxgDpRlC4MYTBS031+Wqb2arHDFlqBMEK0J1bwqKvNBH2EP3U59b6po6rokuHH6wPS94 7XQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=7QT2fx0NGhKYgxf4qw530Y7idwlaQ1ESvZwqsheEguc=; b=PkDOfCOzB7bZDIR0SxiO7Ulkl9aArUNSDy3vUHYnorwjLQZhNV7q7qreGWS4iJSBcY sTVmD3LvOxgBsJ9I54Puj31SM3EY3C9/QUjPNl8UeeIEGe2VwHMZNkfNehJP/K641AO4 zGssTpSMC8LrLuXwpGDB4vos2eiS3hO5pb12SdZj61KEmTNqh8Dt/K4Ce1WajZ1qZRiP 5Qm1CW1KRmBtAN1Qvo/YzdzQDfLO4Zv6iq4zAbjl4OoeD0lCubiBONPIO6EFxGxfl7Vf MIsISwj3sc4p2oit/t238X/KmeOrIaIHHSb3Qwqe+hcXmAs/cr4RRX9toh1jEAiq6rVF n8zw==
X-Gm-Message-State: AFeK/H2rAwlO6UuuASJMwaaerB29Bsqln2c81/Pjp2qSkLKsUZftLCn2r/Tuu69TUop4fw==
X-Received: by 10.107.24.193 with SMTP id 184mr10383374ioy.11.1490379244038; Fri, 24 Mar 2017 11:14:04 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id i18sm1285977itb.28.2017.03.24.11.14.03 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Mar 2017 11:14:03 -0700 (PDT)
Subject: Re: IETF subpoena processes update and a request
To: ietf@ietf.org
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com> <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com> <m2h92ig4yv.wl-randy@psg.com> <33DAE0FB5054D5E9B195CFCA@PSB> <D85AC54E-71CA-4700-9AC2-2923E5DB705C@sobco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <bbb02cb7-dd1b-3dfe-5bd9-a75f59606407@gmail.com>
Date: Sat, 25 Mar 2017 07:14:14 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <D85AC54E-71CA-4700-9AC2-2923E5DB705C@sobco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vOc9Zm4z6ohMSUvqiHyqDBUTvMA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 18:14:10 -0000

On 25/03/2017 05:32, Scott O. Bradner wrote:
> 
>> On Mar 24, 2017, at 12:27 PM, John C Klensin <john-ietf@jck.com> wrote:
>>
>> IANAL either, but it seems to me that Jari's note suggests a
>> more basic question that is almost independent of jurisdictional
>> issues.  Suppose the IETF (or whomever) receives a subpoena that
>> names individuals or companies in a way that might be
>> unfortunate, contain implicit accusations that might be
>> completely unfounded,  or even, in the opinion of those parties
>> if they knew, were libelous, and suppose it directs IETF to not
>> disclose the subpoena in any way.  Without offering anything
>> resembling a legal opinion, it probably makes a difference
>> whether the subpoena is associated with a law enforcement action
>> rather than the civil actions for which I think the policies
>> were designed.
> 
> I know of no case of a civil subpoena that included a gag order

IANAL but there are those "superinjunctions" that sometimes allegedly
occur in English civil libel cases where even the existence of the
superinjunction is secret, under penalty of contempt of court. And
many countries do not have a generic right of free speech.

So, never say never :-(.

   Brian

> 
> & yes, the procedures were deigned for civil cases (like patent prior art)
> 
> Scott
> 
> 


From nobody Fri Mar 24 12:15:22 2017
Return-Path: <mcr+ietf@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 C479F127011 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tE-qfFs605Ri for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:15:19 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41DAE127A91 for <ietf@ietf.org>; Fri, 24 Mar 2017 12:15:19 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id A6B802009E; Fri, 24 Mar 2017 15:38:56 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 75BA2636E0; Fri, 24 Mar 2017 15:15:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: IETF subpoena processes update and a request
In-Reply-To: <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Fri, 24 Mar 2017 15:15:18 -0400
Message-ID: <25630.1490382918@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SuydxHzNUoj1jf7AiQUdUpsUsMc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 19:15:21 -0000

--=-=-=
Content-Type: text/plain


Pete Resnick <presnick@qti.qualcomm.com> wrote:
    > To deal with the second issue, it seems to me that we should address
    > the first issue by making it crystal clear in the procedures that the
    > subpoena must go to the entire IESG, not just the chair, and that
    > whatever action is taken on the subpoena be approved by the IESG (with
    > advice of counsel). If the entire IESG gets a copy of the subpoena, and
    > our procedures make it clear to any court or other issuing authority
    > that more than one person outside of their jurisdiction will be seeing
    > the subpoena, perhaps that will mitigate the second issue.

Is your goal here to dissuade them from placing gag orders on the subpeona,
or is it to make it clear that their subpoena should omit unnecessary
identifying information, as we will post it publically.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljVcEYACgkQgItw+93Q
3WXIzwf/RJEYCoTO1yW/UIky1RPsdf3kuq7UKmsyhRnFheNqO5M8FxZM9kKyYKbs
a2yB6H+tB1n9aAOBEkkZhDN1KEibKcQvQtByyzwykObXBQO6m3I+Thyj+VYX/Jsh
DQ2bW5+LE3+GdjWa6wF+ZwbEeK0rzktylXaBSQT+f0LqwbVdr8zolf4fBt8OtBh0
UrWsd2SMhrkZXD1cKMCbyw0sRgtW+j+jk/a95IyUOMoUtJnu5OjNHSGM7ZsGdW7/
NUY5gG0HT/y4vV4/GxsUcLeebvrNcvNM6G+nKY6YR7ebQ8gB90bP2XCuI1y7clfO
lgQeBZBHMIsMnOVl/vR4++BXoGAeYQ==
=79lM
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Mar 24 12:38:59 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DBC841294CC; Fri, 24 Mar 2017 12:38:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Chair <chair@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: IESG summary report
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: chair@ietf.org,iesg@ietf.org
Message-ID: <149038433780.11826.14935824626124453126.idtracker@ietfa.amsl.com>
Date: Fri, 24 Mar 2017 12:38:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3DQoKCGPGx5TCnFKJqd4fxplgWs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 19:38:58 -0000

Before each IETF, the IETF Chair and the IESG publish a brief report of
their activities. This is done to reduce reporting at the plenary.

Here is the report:

https://www.ietf.org/proceedings/98/slides/slides-98-ietf-sessc-iesg-summary-report-01.pdf

Comments, questions, suggestions, and feedback is always welcome!

Jari Arkko, IETF Chair


From nobody Fri Mar 24 12:39:52 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A70C71298AF; Fri, 24 Mar 2017 12:39:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carlos Pignataro <cpignata@cisco.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-mmusic-dtls-sdp.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
Subject: Review of draft-ietf-mmusic-dtls-sdp-22
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149038438654.11890.13127119697139266198@ietfa.amsl.com>
Date: Fri, 24 Mar 2017 12:39:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Lf4XWJ0g9j5m7Qn3EBRCH99TDrE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 19:39:47 -0000

Reviewer: Carlos Pignataro
Review result: Has Nits

This document is very comprehensive. Operational Considerations are
adequately covered.

In reviewing this document, I did find two adjacent issues that I
thought useful to comment on:

1. Clarity and Readability of Section 9

I appreciate the explicit OLD/NEW details and specifics on what is
changed on the updated RFCs. I wish more documents would do this!

However, the way in which this is done is very confusing and not
really optimizing clarity and readability. It is an operational issue
an implementor not understanding the spec :-)

The issue, in my view, is with the labels and markers. Subsections of
Section 9.2 do not follow the semantic structure of the document.
Instead they are included as follows:
"
Update to section 5:
--------------------
"
Which are then followed by OLD/NEW chunks. However, these chunks:
* include Section numbers and titles, 
* do not have extra indentation, and
* include only BEGIN marker but not END marker.

Like:

9.2.  Update to RFC 5763
Update to section 5:
--------------------
OLD TEXT:
5.  Establishing a Secure Channel

[... and then, two pages later ...]

NEW TEXT:
5.  Establishing a Secure Channel

I'd suggest:
a. Using Section 9.2.1, 9.2.2, etc. for each change.
b. Use more explicit chunk demarkators
c. Use beginning and ending markers.


2. The second issue, and likely this was discussed, relates to the use
of RFC 4572. A reference to RFC 4572 is Normative, and it is cited
within "NEW" text (not only "OLD" text). However RFC 4572 has been
Obsoleted by RFC 8122!

This is because draft-ietf-mmusic-4572-update published as RFC 8122,
which should be updated. 

But for example, why does NEW text here still points to RFC 4572?

--->8---
NEW TEXT:

5.  Establishing a Secure Channel

   The two endpoints in the exchange present their identities as part
of
   the DTLS handshake procedure using certificates. This document
uses
   certificates in the same style as described in
"Connection-Oriented
   Media Transport over the Transport Layer Security (TLS) Protocol
in
   the Session Description Protocol (SDP)" [RFC4572].
--->8---

And why RFC 4572 is Normatively referenced?

Thanks,

Carlos Pignataro.


From nobody Fri Mar 24 12:40:25 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CF041294EC for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NwFvi9tnak5f for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:40:20 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48AE6129882 for <ietf@ietf.org>; Fri, 24 Mar 2017 12:40:14 -0700 (PDT)
Received: (qmail 39384 invoked from network); 24 Mar 2017 19:40:13 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 24 Mar 2017 19:40:13 -0000
Date: 24 Mar 2017 19:39:51 -0000
Message-ID: <20170324193951.85037.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: presnick@qti.qualcomm.com
Subject: Re: IETF subpoena processes update and a request
In-Reply-To: <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VNbELmxLAGy1Y5i9S567SwQqOCA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 19:40:23 -0000

In article <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com> you write:
>Like others, I wonder about the prudence of naming ISOC (and certainly 
>ISOC in the US) as the recipient for legal service. I'd like to hear 
>from lawyers about other possibilities.

It's been like this for well over a decade. Remember that a major
reason to set up ISOC was to have an organizational home for the IETF.
For reasons I can explain if anyone cares, there is no way that ISOC
could move out of the US.

>To deal with the second issue, it seems to me that we should address the 
>first issue by making it crystal clear in the procedures that the 
>subpoena must go to the entire IESG, not just the chair, and that 
>whatever action is taken on the subpoena be approved by the IESG (with 
>advice of counsel).

Nearly all of the subpoenas that the IETF gets are stupendously boring
and routine, and I think this would be a poor addition to the IESG's
crowded schedule.  They typically ask for a certified copy of RFCs or
I-Ds, or for the date when various documents were published.  Read
them and snooze here:

https://iaoc.ietf.org/subpoenas.html

I know none of the details of the subpoena that led to this discussion
but I would be pretty surprised if weren't along the lines of asking
for documentation that a certain person was present at meeting
sessions, in the form of blue sheets or meeting recordings.  That
still doesn't sound like something the IESG needs to deal with.

As Klensin noted, just because someone is named does not mean that he
or she is a suspect in a case, and there's no compelling reason for
the IESG to know who it is.

R's,
John


From nobody Fri Mar 24 12:40:40 2017
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 9E86C1298C8 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.022
X-Spam-Level: 
X-Spam-Status: No, score=-7.022 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FEZ53KFAz4jD for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:40:30 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9636B1294EC for <ietf@ietf.org>; Fri, 24 Mar 2017 12:40:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490384424; x=1521920424; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=sob1tZulRfxlWPbr0VRL3DerEXx3TIiqK2UNmyfhAp4=; b=LxlJV8jIjlgTWPB2yO1jlSTpCJp/LE4fNTS6bfH9yIDTDjNnYL81QuE6 vogTSkapuKaGMwNAXpG2BYbaDJcsXRL7f8t/I8wo05XBHeYwN/6bzH/WJ n06rJnRe3oZp0oJ+5Eablg+3OeqTp8UzZSfnXK/0AC3+xWk3L7BMs/dCK 8=;
X-IronPort-AV: E=Sophos;i="5.36,216,1486454400"; d="scan'208";a="367920805"
Received: from unknown (HELO Ironmsg03-L.qualcomm.com) ([10.53.140.110]) by wolverine02.qualcomm.com with ESMTP; 24 Mar 2017 12:40:24 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8477"; a="1338163766"
X-MGA-submission: =?us-ascii?q?MDFSdffZ2UwJdoMwj2H8uRKDvV7Vr9E3EI8qxf?= =?us-ascii?q?cn4hqxEivcQbq933MubF4tnxjW4pa8cx8bKVSIbdrVfO3LRWNRh/2wqa?= =?us-ascii?q?amAyxhIx3laonA/uNyyhyk0GCRcQUbvNSH64GdEwPoDYFs6luukEy6sd?= =?us-ascii?q?mz?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 24 Mar 2017 12:40:23 -0700
Received: from [10.64.118.210] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 24 Mar 2017 12:40:23 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request
Date: Fri, 24 Mar 2017 14:40:21 -0500
Message-ID: <74917090-33FB-4D1A-BE11-6ECDF214B1E1@qti.qualcomm.com>
In-Reply-To: <25630.1490382918@obiwan.sandelman.ca>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com> <25630.1490382918@obiwan.sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01C.na.qualcomm.com (10.85.0.83) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zia96PLM2QSANIZ6XQwZ56nwhUc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 19:40:39 -0000

On 24 Mar 2017, at 14:15, Michael Richardson wrote:

> Pete Resnick <presnick@qti.qualcomm.com> wrote:
>     > To deal with the second issue, it seems to me that we should 
> address
>     > the first issue by making it crystal clear in the procedures 
> that the
>     > subpoena must go to the entire IESG, not just the chair, and 
> that
>     > whatever action is taken on the subpoena be approved by the IESG 
> (with
>     > advice of counsel). If the entire IESG gets a copy of the 
> subpoena, and
>     > our procedures make it clear to any court or other issuing 
> authority
>     > that more than one person outside of their jurisdiction will be 
> seeing
>     > the subpoena, perhaps that will mitigate the second issue.
>
> Is your goal here to dissuade them from placing gag orders on the 
> subpeona,
> or is it to make it clear that their subpoena should omit unnecessary
> identifying information, as we will post it publically.

Certainly I hope to dissuade gag orders, and certainly I want to make it 
clear that they should omit unnecessary identifying information, but 
note that I did not say that "we will post it publicly". We may, or we 
may not, post it publicly (cf. JCK's message), but either way I'd like 
it to be crystal clear that at least some persons over whom the issuer 
has no jurisdictional control (e.g., because the court is outside of the 
US and members of the IESG are US citizens, or vice versa) will be 
getting copies of the subpoena. So, gag orders will at best be advisory 
and it would be wise to omit unnecessary identifying information.

(My un-legally-educated guess here is that publicly posting something 
that is subject to a gag order, even by someone not normally subject to 
a particular jurisdiction, is a bit of a game of legal "chicken", since 
that person might want to enter that jurisdiction some day. But this is 
where I'd like like to leave it to our leadership to take advice of 
counsel and make their best judgment about what is right for the 
community. What I don't want is to have procedures that make it easy for 
any particular jurisdiction to dictate terms to us.)

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Fri Mar 24 12:45:38 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C24A129477 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level: 
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3WBhCqmulLL for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:45:34 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F4591270A3 for <ietf@ietf.org>; Fri, 24 Mar 2017 12:45:34 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id C7B021406B23; Fri, 24 Mar 2017 12:45:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=TGzUnja5NY+PTv SpQkLweuovWTI=; b=KJz0EU4grxIE+fP09LHjkiYuEiM/NoBIrgd0vtC2ghyAJs dBfMYEtJDcPTAuur3fR5EFuSaXrR6YFPvbKehTHcTvHdKPzi70TEaKR7wi6VjnUl wgG7r5zhwkggY96Oq+KixnZdzTiNo3/jTi/64kATh8KfTSKWYMpYv6+SWnqHw=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 5CD6D1406B05; Fri, 24 Mar 2017 12:45:33 -0700 (PDT)
Date: Fri, 24 Mar 2017 14:45:29 -0500
From: Nico Williams <nico@cryptonector.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: IETF subpoena processes update and a request
Message-ID: <20170324194528.GD7490@localhost>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com> <25630.1490382918@obiwan.sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <25630.1490382918@obiwan.sandelman.ca>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kxCn5UWtN0BQIGACvB10JyD1VfA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 19:45:36 -0000

On Fri, Mar 24, 2017 at 03:15:18PM -0400, Michael Richardson wrote:
> Pete Resnick <presnick@qti.qualcomm.com> wrote:
>     > To deal with the second issue, it seems to me that we should address
>     > the first issue by making it crystal clear in the procedures that the
>     > subpoena must go to the entire IESG, not just the chair, and that
>     > whatever action is taken on the subpoena be approved by the IESG (with
>     > advice of counsel). If the entire IESG gets a copy of the subpoena, and
>     > our procedures make it clear to any court or other issuing authority
>     > that more than one person outside of their jurisdiction will be seeing
>     > the subpoena, perhaps that will mitigate the second issue.
> 
> Is your goal here to dissuade them from placing gag orders on the subpeona,
> or is it to make it clear that their subpoena should omit unnecessary
> identifying information, as we will post it publically.

The latter is certainly not going to work out where the identifying
information is necessary to fulfilling the subpoena.  Intent to publish
might disuade civil parties from pressing subpoenas, but not law
enforcement agencies.

The former is unlikely to succeed as to LEAs.  I cannot imagine a
private organization by-law that could disuade a LEA from pressing a
subpoena on that party when that LEA has access to friendly courts (they
always do).

I agree that the IESG should get a copy as a matter of course, but as
the legal entity to which the subpoenas are and will be served to is
ISOC, the IESG and IETF may not get much say as to that.  It's hardly as
though ISOC might risk incurring criminal liability in order to abide by
our rules.  On the other hand, ISOC might be more inclined to fight a
gag order that requires it not inform even the IESG, than to fight a gag
order that allows it to inform the IESG.

In any case, I'm surprised to see nothing about a warrant canary yet in
this thread.  (Though even those might not work legally in some
jurisdictions.  ISOC is vulnerable to rubber hoses.)

Lastly, I agree that where it is clear that a subpoena relates to a
criminal investigation, as opposed to a civil matter, the subpoena
should not be published as-is, at least not without the approval of the
targets named in it or extraordinary action by ISOC/IESG where they
think the public's interest is much stronger than the targets'.  Any
redaction by the ISOC/IESG in such cases would presumably be at the
request of the targets, thus the targets might be the ones proposing
redactions (which, ISOC/IESG might reject).  I suppose the relevant
distinguishing characteristic is: who pressed the subpoena, an LEA or a
non-LEA.

Nico
-- 


From nobody Fri Mar 24 14:22:27 2017
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 46B99129504 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 14:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iFxC4MMHEESX for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 14:22:23 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A91EB127F0E for <ietf@ietf.org>; Fri, 24 Mar 2017 14:22:23 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id w124so21581852itb.1 for <ietf@ietf.org>; Fri, 24 Mar 2017 14:22:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=pBAydH7KwIhJxgKe48fuN1mL8/kmcMe+b8o3VzR92Ig=; b=KMsY9+GtaOh053UxW6mT7a9uPDVQYI46TRd94qHKuqTUpGhg78js6JgO7oSr2PP9Xf wmqyv83j9S6eTfwozITyKU8bWIwwuzUOIDmJJWj3x2u9S/lgLIlyeZzFNrEw2SVrceWw 2hV63fQMFDyAZQ+Ld6G+UaIei5LISHY9VHOTPyl3/TGTcjkEZ7IwjZsjH3T6lXmdKpnu xjDDU6YblikElScJH++JzXvNmHuBg/z6dAm8oaOmPIKVg6oKEUJIqi/izJlgu5lD2lxA KTxE88RvbkFm1SBbd3Ye9bB67LNSALyFWxZCbavU37sC7SvOVc6K8L5AlfsGdI69EwI0 XvWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=pBAydH7KwIhJxgKe48fuN1mL8/kmcMe+b8o3VzR92Ig=; b=huFspJLYDDEa0WS8+cpFATpUU1iaGh04TGh/sZdNnT1zwdei16Af7FP2RptQmjPsAR VwBQ/uD2IXadDTlIUO0JS1SckhEg39REC8vLxAa/fT85+vQ1ypbXlzv4KZYaSKUe3Dzr WsVOUPyR0NME9v2lbZKTP3Q2FjGxMr92qeW+uAW/AZBHsQpz5JKtm+pAb/zqzLEgnk7c OB9+pfSZSQRHkA8gLiDkXTmRzyqHriIZEsHzqvkeZaAXfcEtjad2udd2vk120LE8bls0 lSGcLNqVTYqH2aZbEecFPf0o5IZgAMoAZiccLY43uQLZAm9X+0K0/1u7YmSbEw7JAry4 JizQ==
X-Gm-Message-State: AFeK/H2xAh03YUUy9u06vmkuH9lYCE+IBfpHmLmr8rsR/20yCdraeurWKio2Ja8LRqjujw==
X-Received: by 10.36.216.4 with SMTP id b4mr5342693itg.100.1490390542810; Fri, 24 Mar 2017 14:22:22 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id d42sm1762506ioj.61.2017.03.24.14.22.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Mar 2017 14:22:22 -0700 (PDT)
Subject: Re: IETF subpoena processes update and a request
To: John Levine <johnl@taugh.com>, ietf@ietf.org
References: <20170324193951.85037.qmail@ary.lan>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5306327a-25aa-2bae-e0db-7a818455849e@gmail.com>
Date: Sat, 25 Mar 2017 10:22:33 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170324193951.85037.qmail@ary.lan>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JfIDdLyx8moHTQMZiki-wodHHy4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 21:22:25 -0000

On 25/03/2017 08:39, John Levine wrote:
...
> Nearly all of the subpoenas that the IETF gets are stupendously boring
> and routine, and I think this would be a poor addition to the IESG's
> crowded schedule.  

+1. This would be a pointless and annoying addition to the IESG's already
high workload. I am quite certain that IASA will bring them in if a
case arises that they need to be involved in. But indeed, ISOC was
partly created, and IASA was 100% created, to save the IETF leadership
from as much legal, financial and admin stuff as possible.

Setting subpoena policy is a fine topic for community discussion. Beyond
that, the engineers of the IETF should not be involved unless absolutely
unavoidable.

   Brian


From nobody Fri Mar 24 14:32:05 2017
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 AFAA6129882 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 14:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.022
X-Spam-Level: 
X-Spam-Status: No, score=-7.022 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5JLSFPZKf32 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 14:32:01 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44A231294FD for <ietf@ietf.org>; Fri, 24 Mar 2017 14:32:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490391121; x=1521927121; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=AZIuliR4rqoWPBdL0PWXjpJmxAkuKMUKcJmWclQ76VQ=; b=N7JoBRpW/64UXplBjrX5wI2vQow61J9QckDk6yTYD6o1XJhC25vVgm3L Mc1y4EVW9M25oxdzAp1BYuBhr0EYINrrqfPPCPHA8obELp6kTZQIMtWkV OFU3vQ5S/1hRB+dogKmYO6VQ83N+7HGZzQt8LS41IrpiNlM1v87u9afzO M=;
X-IronPort-AV: E=Sophos;i="5.36,216,1486454400"; d="scan'208";a="367943406"
Received: from unknown (HELO ironmsg02-R.qualcomm.com) ([10.53.140.106]) by wolverine02.qualcomm.com with ESMTP; 24 Mar 2017 14:32:00 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8477"; a="925685149"
X-MGA-submission: =?us-ascii?q?MDEGBoKIt3Oul1v/a3QxvpgPe4imlPiuEYGZSD?= =?us-ascii?q?wCwMyyX3Boa7yTm2Uxlr5KLVmB9tBjVgTS/2OK+KBlOwVuBnTDKsClqK?= =?us-ascii?q?phB5gT+CzW8dogytbJB7JCUTbvFRdUrd9ZTlpbnW6gzNliwmlw05KRAw?= =?us-ascii?q?Xz?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 24 Mar 2017 14:31:59 -0700
Received: from [10.64.118.210] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 24 Mar 2017 14:31:57 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: John Levine <johnl@taugh.com>
CC: <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request
Date: Fri, 24 Mar 2017 16:31:56 -0500
Message-ID: <5DAE09F6-D7DE-47B4-ABA6-BC9A92DDEE4E@qti.qualcomm.com>
In-Reply-To: <20170324193951.85037.qmail@ary.lan>
References: <20170324193951.85037.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01C.na.qualcomm.com (10.85.0.83) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p7Phm7C36820OW5EV1tv_-MOrMY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 21:32:04 -0000

On 24 Mar 2017, at 14:39, John Levine wrote:

> In article <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com> you 
> write:
>> Like others, I wonder about the prudence of naming ISOC (and 
>> certainly
>> ISOC in the US) as the recipient for legal service. I'd like to hear
>> from lawyers about other possibilities.
>
> It's been like this for well over a decade. Remember that a major
> reason to set up ISOC was to have an organizational home for the IETF.

I will say, as someone who was on the IAB when BCP 101 was written, that 
I favored a tight financial coupling and a more minimal organizational 
coupling. There are times when being somewhat separate is a good thing.

> For reasons I can explain if anyone cares, there is no way that ISOC
> could move out of the US.

As luck would have it, I never suggested that.

> Nearly all of the subpoenas that the IETF gets are stupendously boring
> and routine, and I think this would be a poor addition to the IESG's
> crowded schedule.

And hence my earlier comment that I expect that "most of the time IETF 
leadership ends up simply nodding at counsel, the IAOC, the IAD, etc.". 
I am someone that has believed for quite some time that the IAB and IETF 
chairs themselves really do not need to be members of the IAOC, as I 
think it's a waste of resources, and BCP 101 should be updated to allow 
for at least delegates. And I equally expect that most members of the 
IESG will summarily ignore most subpoenas that fly by. But having them 
made available is not a burden, and even having a pro-forma agenda item 
on the IESG's agenda where Amy can say, "Any questions or discussions of 
the subpoenas? [5 second pause] Next on the agenda..." is really not a 
significant burden. Most of the time, the agenda item will be 
exceedingly boring...until it's not. I can certainly imagine the kind of 
case where the cursory read of a subpoena causes an AD to say, "Whoa! 
Someone needs to go to court to get that quashed!"

> ...there's no compelling reason for
> the IESG to know who it is.

Whenever someone says, "there's no need for you to know this 
information", when not preceded by a long explanation of an additional 
harm one is incurring by simply knowing the piece of information, 
particularly when "you" is the leadership of an organization, it sends 
up a giant red flag for me. The leadership should have available every 
piece of information available to them, and they can choose whether or 
not they need to examine it or act on it. But to withhold information 
without compelling reason is deeply problematic. Unless you spend your 
time in a SCIF, the burden is to show why someone should not have 
information available to them, not the other way around.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Fri Mar 24 14:47:32 2017
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 BA1921299B2 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 14:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9PxKCO1B5nU for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 14:47:28 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1C3C129504 for <ietf@ietf.org>; Fri, 24 Mar 2017 14:47:28 -0700 (PDT)
Received: from [192.168.0.158] (50-232-11-130-static.hfc.comcastbusiness.net [50.232.11.130]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2OLnUq6003321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 24 Mar 2017 14:49:30 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490392171; bh=m1iq87DSCq5SNUquA+NdFRsr/ANhHtPbkIAtACTOkZU=; h=Subject:To:References:Cc:From:Reply-To:Date:In-Reply-To:From; b=G3Wp+a6LWJZ611kSTl2/Aybx9yJ7HKBbMIMmYAJfke4tNuWyNbQt2Zq+jcFcpHHqU e896MBueWgP8O5/PW+F6btsFdoeWu614zv6N7x4ISIeRHs7qvDjFeopYq7yQU5r8lN wmIH21vmvXjOFtC/GScj+UCwc0uZe84g5aauFsIM=
Subject: IAOC membership (was: Re: IETF subpoena processes update and a request)
To: Pete Resnick <presnick@qti.qualcomm.com>, John Levine <johnl@taugh.com>
References: <20170324193951.85037.qmail@ary.lan> <5DAE09F6-D7DE-47B4-ABA6-BC9A92DDEE4E@qti.qualcomm.com>
Cc: ietf@ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <784a4e97-50f0-40ff-31e5-ccc4dbcbef85@dcrocker.net>
Date: Fri, 24 Mar 2017 16:47:25 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <5DAE09F6-D7DE-47B4-ABA6-BC9A92DDEE4E@qti.qualcomm.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Oxg-3QEXSF9oMXYiFWpRnj8-zAg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 21:47:32 -0000

On 3/24/2017 4:31 PM, Pete Resnick wrote:
> I am someone that has believed for quite some time that the IAB and IETF
> chairs themselves really do not need to be members of the IAOC, as I
> think it's a waste of resources,


The primary argument in favor of their ex-oficio membership is breadth 
of view -- they have a degree of involvement in IETF-related activity 
that no one else does, thus permitting a currency in assessment that 
others cannot reliably provide.

 From my time on the IAOC, I have to admit to seeing some legitimacy in 
this view.  Not enough to think they need to be voting members -- I'd 
like to see the voting membership expanded, per the IASA 2.0 discussions 
now underway.  But enough to justify their ex-oficio participation.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Fri Mar 24 15:25:23 2017
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 D22EC128990; Fri, 24 Mar 2017 15:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pEu5LsM6V2yS; Fri, 24 Mar 2017 15:25:20 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 858C812894E; Fri, 24 Mar 2017 15:25:20 -0700 (PDT)
Received: from [128.9.184.140] ([128.9.184.140]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v2OMP84m023632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 24 Mar 2017 15:25:08 -0700 (PDT)
Subject: Re: IETF subpoena processes update and a request
To: John C Klensin <john-ietf@jck.com>, Randy Bush <randy@psg.com>, Scott Bradner <sob@sobco.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <m2k27eg61o.wl-randy@psg.com> <7B9DC018-C522-492C-824D-6643E32A146D@sobco.com> <m2h92ig4yv.wl-randy@psg.com> <33DAE0FB5054D5E9B195CFCA@PSB>
Cc: IETF Chair <chair@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <a5e9202a-1c2e-e7c5-989d-745c7fbeaefb@isi.edu>
Date: Fri, 24 Mar 2017 15:25:08 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <33DAE0FB5054D5E9B195CFCA@PSB>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: v2OMP84m023632
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ThLV_ds6qUkEbEX7AMVdEo4VEkI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 22:25:22 -0000

On 3/24/2017 9:27 AM, John C Klensin wrote:
> Suppose the IETF (or whomever) receives a subpoena that
> names individuals or companies in a way that might be
> unfortunate, contain implicit accusations that might be
> completely unfounded,  or even, in the opinion of those parties
> if they knew, were libelous, and suppose it directs IETF to not
> disclose the subpoena in any way.  Without offering anything
> resembling a legal opinion, it probably makes a difference
> whether the subpoena is associated with a law enforcement action
> rather than the civil actions for which I think the policies
> were designed.
This seems like it also raises the EU's "right to be forgotten"
principle, which would affect whether the ISOC can archive even notices
that were originally public.

Sort of running a boat, blimp, or satellite in "international waters",
it seems like these are complications to operating *anywhere*.

Joe


From nobody Fri Mar 24 16:05:45 2017
Return-Path: <gorry@erg.abdn.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 7FFB912762F; Fri, 24 Mar 2017 16:05:31 -0700 (PDT)
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=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, RP_MATCHES_RCVD=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gaew8qrTwwoA; Fri, 24 Mar 2017 16:05:27 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 57715120326; Fri, 24 Mar 2017 16:05:27 -0700 (PDT)
Received: from Gs-MacBook-Pro.local (unknown [216.80.70.251]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 214791B017C3; Sat, 25 Mar 2017 01:02:41 +0000 (GMT)
Message-ID: <58D518EA.5000508@erg.abdn.ac.uk>
Date: Fri, 24 Mar 2017 13:02:34 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
CC: "tsv-area@ietf.org" <tsv-area@ietf.org>,  "6man-chairs@ietf.org" <6man-chairs@ietf.org>, IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>,  "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <804AA9E4-A643-47A3-9FCC-DA1C450E7FB1@gmail.com>
In-Reply-To: <804AA9E4-A643-47A3-9FCC-DA1C450E7FB1@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/59oFa8eDsHRMad57PddmkKOIIgQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 23:05:32 -0000

On 17/03/2017, 21:56, Bob Hinden wrote:
> Gorry,
>
> Thanks for the detailed review.
>
> Several of the reviews have suggested significant changes to this document.  The working group was trying to make a few changes to bring it into alignment with some changes to rfc2460bis (based on updating documents).  It was not attempting a major rewrite when advancing it to Internet Standard.  The alternative that the working group discussed was to file errata on RFC1981 and leave it to a future document update.
>
> I don’t think many of these changes can be done and still advance it to Internet Standard. If we can’t advance the current document, then the w.g. may want to just do the errata and withdraw the advancement request.  Of course, if people want to work on a revision of IPv6 Path MTU Discovery, it would be welcomed, but it won’t be able to advanced to Internet Standard.
>
> Comments below.
>
> Thanks,
> Bob
Thanks Bob,

I note  the question of status, but in this case, there's a lot happened 
in the Internet since this PS was first published, and much of this was 
in the transport area. Please see replies to comments below. I'm happy 
to discuss or refine text, if this helps.

Gorry
>> On Feb 14, 2017, at 9:23 AM, Gorry Fairhurst<gorry@erg.abdn.ac.uk>  wrote:
>>
>>
>> I have some late transport comments on this ID. The update seems to retain a lot of thinking that is really historical and I'd really encourage people to look again to making the document uptodate.
>>
>> Detailed comments follow.
>>
>> Best wishes,
>>
>> Gorry
>>
>> ----
>> The following text strikes me as a little odd in an update:
>> " Moreover, TCP implementations that follow the "slow-
>>    start" congestion-avoidance algorithm [CONG] typically calculate and
>>    cache several other values derived from the PMTU.  It may be simpler
>>    to receive asynchronous notification when the PMTU changes, so that
>>    these variables may be updated.”
>> - A modern TCP caches at least some path information in the TCB, why start with this clause at all:
>> "Moreover, TCP implementations that follow the "slow start" congestion-avoidance algorithm [CONG] typically calculate and”
>> and simply replace this with something like:
>> "TCP implementations”?
>> ——
> To clarify, you are suggesting to replace it with:
>
>     TCP implementations typically cache several other values derived
>     from the PMTU.  It may be simpler to receive asynchronous notification when
>     the PMTU changes, so that these variables may be updated.
> I think that is editorial, and OK to change.  The paragraph will read:
>
>     The TCP layer must track the PMTU for the path(s) in use by a
>     connection; it should not send segments that would result in packets
>     larger than the PMTU.  A simple implementation could ask the IP layer
>     for this value each time it created a new segment, but this could be
>     inefficient.  TCP implementation typically cache several other values
>     derived from the PMTU.  It may be simpler to receive asynchronous
>     notification when the PMTU changes, so that these variables may be
>     updated.
Thanks. Seems better, although I would suggest to revise this in this way:

    A packetization layer layer (e.g., TCP) must track the PMTU
    for the path(s) in use by a
    connection; it should not send segments that would result in packets
    larger than the PMTU, except to probe during PMTU discovery.
    A simple implementation could ask the IP layer
    for this value each time it created a new segment, but this could be
    inefficient.  An implementation typically caches other values
    derived from the PMTU.  It may be simpler to receive asynchronous
    notification when the PMTU changes, so that these variables may be
    also updated.

- This would fix typos, and also make the text relevant to transport protocols,
rather than only TCP. Which is I beleive the correct interpretation.

>> The following text also seems to not reflect a modern TCP stack:
>> " It is sufficient
>>    to treat this as any other dropped segment, and wait until the
>>    retransmission timer expires to cause retransmission of the segment.”
>> (and following 3 paras).
>> Could this be replaced by text that does not exclude modern retransmission methods:
>> " It is sufficient
>>    to treat this in the same way as any other dropped segment, and
>>    will be recovered by normal retransmission methods.”
> Yes, resulting in:
>
>     When a Packet Too Big message is received, it implies that a packet
>     was dropped by the node that sent the ICMP message.  It is sufficient
>     to treat this in the same way as any other dropped segment, and will
>     be recovered by normal retransmission methods.  If the Path MTU
>     Discovery process requires several steps to find the PMTU of the full
>     path, this could delay the connection by many round-trip times.
Good. Seems much better.
>
>> —
>> There is a block of text that describes retransmission triggered by ICMPv6.
>> Has this code been implemented in modern releases of TCP?:
>> "   Alternatively, the retransmission could be done in immediate response
>>    to a notification that the Path MTU has changed, but only for the
>>    specific connection specified by the Packet Too Big message.”
>> - It seems to expose a number of attack vectors that really should not be exposed!!
> Are you suggesting remove this text?  Following this text, there are two notes.
>
I'd personally remove this and the notes (you decide) - more because it 
says think that it opens a can of worms about transport details that are 
largely beyond the scope of the document (such as whether to trust 
ICMPv6 as indications of actual loss, and how this interacts with 
re-packaging to a different segment size, congetsuon control, etc).

If the WG thinks retaining some text is good, I'd say (as a cautious 
transport person) that we should call out a warning to people doing 
transmissions...

OLD:
      If the new estimated PMTU is
       still wrong, the process repeats, and there is an exponential
       growth in the number of superfluous segments sent.
NEW:
      If the new estimated PMTU is
       still wrong, the process repeats, and there is an exponential
       growth in the number of superfluous segments sent.
       Retransmissions can increase network load in
       response to congestion, worsening that congestion.  Any
       packetization layer that uses retransmission is responsible for
      congestion control of its retransmissions.

If you wish, cite RFC8085 and RFC4821 to let people figure this out? 
(these 2 sentences come directly from RFC8085).
>> ---
>> The discussion of NFS may still be a reasonable historic example, but to be current it should really refer also to NFSv4/TCP as utlising the MTU discovery provided by TCP, since UDP-based NFS is no longer a key application.
>> —
> I was planning to update the reference to NFS to RFC7530.   I could add text that says something like:
The protocol changed though - so it's not just a replacement reference.

I think text should note that RFC7530 says NFS must be able to run over 
a congestion-controlled transport, such as TCP.
>     It is recommended that NFS running over TCP utilize the MTU discovery
>     provided by TCP.
>
> Other suggestions?
Maybe, you could say something like:
"RFC191 used NFS as an example of a UDP-based application that benefits 
from PMTU discovery. Since then RFC7530, states the supported transport 
layer between NFS
and IP must be an IETF standardized transport protocol that is specified 
to avoid
network congestion; such transports include TCP and the Stream Control 
Transmission Protocol (SCTP). In this case, the transport is itself 
responsible for determining and using an effective Path MTU, including 
implementing PMTU discovery when this is needed."

RFC8085 may well be a good place to point to say what is 
needed/desirable for PMTU for UDP applications, if you wish to say 
something about UDP.
>> There is no mention that paths including tunnels can eat ICMPv6 PTB messages on the tunnel segment, blackholing them, which prevents reaching the destination.
> As noted above, I think adding discussion about tunnels is out of scope of this effort.
I agree that new mechanisms are out of scope, I was hoping that a simple 
note on tunnels would be in the security considerations.

RFC8085 or draft-ietf-intarea-tunnels could be pointed to describe the 
implications of tunnels.
>> ---
>> I think the security consideration is naive!
> Suggestions?
"   In the first attack, the false message indicates a PMTU much smaller
    than reality.  This should not entirely stop data flow, since the
    victim node should never set its PMTU estimate below the IPv6 minimum
    link MTU.  It will, however, result in suboptimal performance."

So... In the case of the first attack, I still question whether this 
choice of words misrepresents the attack.
What if, the false message advertises ~1280 bytes, and the path uses a 
tunnel encapsulation transporting IPv6, then the PTB message can be 
basis for a straight DoS attack that does stop data flow?

I would recommend revising the security considerations (at least to 
something like):
"  In the first attack, the false message indicates a PMTU much smaller
    than reality.  In response, the
    victim node should never set its PMTU estimate below the IPv6 minimum
    link MTU. A sender that falsely reduces to this MTU would observe 
suboptimal performance."

- Although this skirts the problem.
>> This statement in particular seems to open DOS vulnerability:
>> "
>>   When a node receives a Packet Too Big message, it MUST reduce its
>>    estimate of the PMTU for the relevant path, based on the value of the
>>    MTU field in the message."
>> - Introdueces a significant vulnerability.  A rogue PTB message that reduces the PMTU to a minimum, can result in a path too small to carry an encapsulated packet. (Recently noted by Fernando Gont).
> Suggestions?
See below - and above.
>> Moreover, other layers view ICMP messages with suspicion and have long noted the need to check ICMP payload and match only packets that relate to actual 5-tuples in use (effectively reducing vulnerability to off-path attacks). For example, the Guidelines for UDP, rfc5405bis, state:
>>
>> " Applications SHOULD appropriately validate the payload of ICMP
>>    messages to ensure these are received in response to transmitted
>>    traffic (i.e., a reported error condition that corresponds to a UDP
>>    datagram actually sent by the application). …“
>> - clearly handling this in IP-layer tunnels can be troublesome, but that's a problem that should be described, not obscured.
> I could add something like the following as a new second paragraph in Section 4 Protocol Requirements:
>
>    Protocols SHOULD appropriately validate the payload of ICMPv6 PTB
>    messages to ensure these are received in response to transmitted
>    traffic (i.e., a reported error condition that corresponds to a UDP
>    datagram actually sent by the application).
>
> or similar.

That certainly is a nod in what I think is really the correct direction.
Probably /UDP/ should be /IPv6 packet/ given the context of this ID.
>
>> ——
>>
>> I’d finally  like to add my concerns about the understatement of the value of PLPMTUD, which seems to not reflect the recommendations to use this method:
>> “  It defines a method for Packetization Layer Path
>>    MTU Discovery (PLPMTUD) designed for use over paths where delivery of
>>    ICMP messages to a host is not assured.”
>> This  seems under-stating the value and recommendations to deploy PLMTUD, compared with current transport-area recommendations, for instance, the UDP Guidelines provide much more on this important design consideration:
>
> The w.g. spent a lot of time on this paragraph.  The intent was to point to it, but not into detail of how it worked, nor make it a new requirement.  There was some discussion that adding more detail about the relationship between PTMUD and PLPMTUD in the ongoing update to IPv6 Node Requirements would be helpful.

I appreciate people have spent time trying to get the IPv6 
specifications progressed to standards status. This is a good effort, 
but I think just adding a nod in the introduction is rather feeble for 
soemthing now recommended. I think at least the security considerations 
should motivate the benefits of this approach (see next).
>> "   Packetization Layer Path MTU Discovery (PLPMTUD) [RFC4821] does not
>>    rely upon network support for ICMP messages and is therefore
>>    considered more robust than standard PMTUD.  It is not susceptible to
>>    "black holing" of ICMP message.  To operate, PLPMTUD requires changes
>>    to the way the transport is used, both to transmit probe packets, and
>>    to account for the loss or success of these probes.  This updates not
>>    only the PMTU algorithm, it also impacts loss recovery, congestion
>>    control, etc.  These updated mechanisms can be implemented within a
>>    connection-oriented transport (e.g., TCP, SCTP, DCCP), but are not a
>>    part of UDP, but this type of feedback is not typically present for
>>    unidirectional applications."
>>
>> ----
>>
>> The examples used in the definition of  "upper layer" and "link" also makes this document appear as historic, rather than a new RFC!
> As noted above, I think there would be support for a rewrite if some folks wanted to take that on.
Could the WG consider to also add the first two sentences to the 
security considerations?

Gorry

P.S. A few more out-dated statements abiut TCP, based on the way 
specific stacks work when the original was written:

- The phrase below needs to be removed also, since not all TCP stacks 
behave in this way anymore:
", which is always a multiple of the segment size"

- There was very specific detailis relating to 4.2BSD TCP 
implementations, which would have been better not being here.



From nobody Fri Mar 24 16:13:02 2017
Return-Path: <mcr+ietf@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 34EAE1292AE for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 16:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u3tYmJQ_rjfO for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 16:12:58 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F28F128CD5 for <ietf@ietf.org>; Fri, 24 Mar 2017 16:12:58 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 94D23E19D; Fri, 24 Mar 2017 19:36:36 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C7FB5636E0; Fri, 24 Mar 2017 19:12:57 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Pete Resnick <presnick@qti.qualcomm.com>
cc: ietf@ietf.org
Subject: Re: IETF subpoena processes update and a request
In-Reply-To: <74917090-33FB-4D1A-BE11-6ECDF214B1E1@qti.qualcomm.com>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com> <25630.1490382918@obiwan.sandelman.ca> <74917090-33FB-4D1A-BE11-6ECDF214B1E1@qti.qualcomm.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Fri, 24 Mar 2017 19:12:57 -0400
Message-ID: <14654.1490397177@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f9Wu3BV3Hc0jql0uuIc-lNkTgt8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Mar 2017 23:13:00 -0000

--=-=-=
Content-Type: text/plain


Pete Resnick <presnick@qti.qualcomm.com> wrote:
    > Certainly I hope to dissuade gag orders, and certainly I want to make
    > it clear that they should omit unnecessary identifying information, but
    > note that I did not say that "we will post it publicly". We may, or we
    > may not, post it publicly (cf. JCK's message), but either way I'd like
    > it to be crystal clear that at least some persons over whom the issuer
    > has no jurisdictional control (e.g., because the court is outside of
    > the US and members of the IESG are US citizens, or vice versa) will be
    > getting copies of the subpoena. So, gag orders will at best be advisory
    > and it would be wise to omit unnecessary identifying information.

Well... we will distribute it outside of the court's jurisdiction, using
unencrypted email (where it might be subject to access to information
process...), and then discuss it at an IETF telechat where anyone may dial
in.  This is what I meant... we aren't going to try to keep it very secret.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljVp/kACgkQgItw+93Q
3WXXPQgAo8aj/+PwckBKW6pHtqBsdVtZfnF52UVa5Ey1KspEWRJJG0gSqeu85VfC
8TqDdp6ccHcFm2OxlJwdNP2Two1bul0KpdmSRXBYs5jINURQDpyIoX+BcyBizdMp
gqo+/E8x3vblu1C32xsFcOpMvbesv0iWka4yzLmXRKcoy1+WJ2GPikm1dp6d4fQq
2TFlXwiZMpEEYDveAqOXJsu5OC+3OZJV6dXJ2eTEcWhD20SMW6X8enA8TkqTT3cx
D4lQcLJjS0gXxhvdItjb4aBs1fgfE9S+eSO4un/26Oa7d9bEZfZlidUaJ8GT0LKs
T8wPe3VUjE0opGTkAA1SVeQk1MCcyg==
=hrs2
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Mar 24 17:50:12 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07BAA1293E1 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 17:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=J5E1nHPp; dkim=pass (1536-bit key) header.d=taugh.com header.b=DV0ryk7+
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vl1QAauxZ50T for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 17:50:08 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F16CC126D73 for <ietf@ietf.org>; Fri, 24 Mar 2017 17:50:07 -0700 (PDT)
Received: (qmail 40658 invoked from network); 25 Mar 2017 00:50: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:references:mime-version:content-type:user-agent; s=9ed0.58d5bebc.k1703; bh=ySbYqfojilZEr1+yQgEV8iclrPHulLJOsLtEUtyhufc=; b=J5E1nHPpwoNSAogOBqVSQAZq+eGrz6CAvwYacYHuiQTQafYwvE+BTvBInRp31M6G/R5RUtfl+9q1ZH/b1y3lJbo4XY0AF+uSGL8B5k3ZrGwK5LETZsNwhvb56RjaOfpgJgABd7lc0aOGiRqy6QTV4K0dOQWIoWrS+ExA1zksTryPJTpxnpODuOOpoNeCsPZo5JjoD8sMiqR8OiEbp5WJTsilxf/3Lr4qTldtO5xL5J19bwhRB0+9X/JMMliMLSjf
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=9ed0.58d5bebc.k1703; bh=ySbYqfojilZEr1+yQgEV8iclrPHulLJOsLtEUtyhufc=; b=DV0ryk7+b2ULMr3R/+DJbFlAhFsMhPbgD4a1uaaw8HD37Wgvj2bSajoRQJsb1xyp3rFZMnYrZDSVf5KY9UpdCR92B6vLZGBYTokw9huXhi/uLzH7t050d7WqQDI5ktues9azr8M3DIBB4Tq78LzreqiyWoD9lmkDJaQKeryBPdJpBHkr3VqSuTuqi4e4gKjfUBzFdi+9UtoEvLG+OmrGGpfAGCv+Uw5SFe1SLgSVWfbwnoqZN4Rm3lNSPUrccO2R
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 25 Mar 2017 00:50:04 -0000
Date: 24 Mar 2017 20:50:04 -0400
Message-ID: <alpine.OSX.2.20.1703241826550.72979@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Pete Resnick" <presnick@qti.qualcomm.com>
Cc: "IETF general list" <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request
In-Reply-To: <5DAE09F6-D7DE-47B4-ABA6-BC9A92DDEE4E@qti.qualcomm.com>
References: <20170324193951.85037.qmail@ary.lan> <5DAE09F6-D7DE-47B4-ABA6-BC9A92DDEE4E@qti.qualcomm.com>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Vfx5AuLCi4tQ2vKJp-vfnqR0NqI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Mar 2017 00:50:10 -0000

>> Nearly all of the subpoenas that the IETF gets are stupendously boring
>> and routine, and I think this would be a poor addition to the IESG's
>> crowded schedule.
>
> And hence my earlier comment that I expect that "most of the time IETF 
> leadership ends up simply nodding at counsel, the IAOC, the IAD, etc.". ...

You've been on the IESG and I haven't, but I'm still scratching my head 
about why this process needs to change to give the IESG even a little more 
work after it's been working OK for over a decade.

>> ...there's no compelling reason for the IESG to know who it is.
>
> Whenever someone says, "there's no need for you to know this information", 
> when not preceded by a long explanation of an additional harm one is 
> incurring by simply knowing the piece of information, particularly when "you" 
> is the leadership of an organization, it sends up a giant red flag for me.

See Klensin's previous message.  The chance of reputation damage to 
someone named in a subpoena is significant, and the IESG has no legal 
expertise.

Here's a scenario: ISOC gets a subpoena from the L.A. county attorney, in 
connection with an investigation of abuse of a minor, send them what you 
have that shows whether Bob and Pete were in the foo session on March 25, 
2015.  Fine says the IESG, send them the blue sheets and the recording. 
The backstory is that Bob is in a messy divorce with accusations going 
back and forth, and he told the cops that he couldn't have done it because 
he was in Texas at the IETF, in fact he was in a session where Pete was 
presenting and they had a long argument at the mike which Pete will surely 
recall, but of course that's not in the subpoena.  So the cops sent the 
subpoena to see if the story holds up.

An IESG member, who was selected for his expertise in crypto algorithms, 
not criminal law, mentions in the bar late some evening, wow, there's 
something going on in L.A. about Bob and Pete and child abuse, and word 
gets around, with bad effects on Pete's career.  The timing makes it clear 
that the leak was from the IETF, the guilty party doesn't confess (he 
doesn't remember talking about it) so ISOC is hauled in front of a judge 
who asks why we show criminal subpoenas to a bunch of nerds with no legal 
experience rather than having our lawyer handle it like everyone else 
does.

Maybe that wouldn't happen, but the more people who know about something, 
the more likely it is to leak with bad results.

R's,
John


From nobody Fri Mar 24 18:18:52 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F38C81297E6 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 18:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzIBuVj1cLOs for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 18:18:49 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F9AE129515 for <ietf@ietf.org>; Fri, 24 Mar 2017 18:18:49 -0700 (PDT)
Received: (qmail 48591 invoked from network); 25 Mar 2017 01:18:47 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 25 Mar 2017 01:18:47 -0000
Date: 25 Mar 2017 01:18:25 -0000
Message-ID: <20170325011825.85855.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: RTBF, was IETF subpoena processes update and a request
In-Reply-To: <a5e9202a-1c2e-e7c5-989d-745c7fbeaefb@isi.edu>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-obYV5BjzFJNweDXiLBmR9aWNZQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Mar 2017 01:18:51 -0000

In article <a5e9202a-1c2e-e7c5-989d-745c7fbeaefb@isi.edu> you write:
>This seems like it also raises the EU's "right to be forgotten"
>principle, which would affect whether the ISOC can archive even notices
>that were originally public.

Only if ISOC were subject to EU law.  Since ISOC has no physical
presence in the EU and the IETF has no office anywhere, I don't see
why EU law would apply.

R's,
John


From nobody Fri Mar 24 19:04:04 2017
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 09675129991 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 19:04:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZMRG-fSPkjUp for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 19:04:00 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2D8A128BE1 for <ietf@ietf.org>; Fri, 24 Mar 2017 19:04:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490407440; x=1521943440; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=lIn08QB5G8fscl7MSDVl//yVeyIgGE9Zr2jsHoafkjk=; b=YW1fw926PDlfoogfWbNHUQ6s1au1I1qp49+elO27iyR2OENfowMRjhWD gbatHHWrs/CD0oD1eVnO5OQzkIuJeSanuhsRRPCQqx4KJnN7rKodZJyAr pMhv7+FC6NJh/uh8KIsWKxvvSPJNd8Xnr5HLgJDK9D8wRqA349ma70vL5 c=;
X-IronPort-AV: E=Sophos;i="5.36,217,1486454400"; d="scan'208";a="367991192"
Received: from unknown (HELO Ironmsg03-L.qualcomm.com) ([10.53.140.110]) by wolverine02.qualcomm.com with ESMTP; 24 Mar 2017 19:04:00 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8477"; a="1338361535"
X-MGA-submission: =?us-ascii?q?MDESG7z+27rrJkrpWTv4fszhOHmPV7AeF842UP?= =?us-ascii?q?GgcbVmqYoxXAuw0JMRDZaJ4So4M/zGW7wgoQ2bOzyFZiJVJXKI7YUwSH?= =?us-ascii?q?sswHoWe4sxaM3vvXkZJvIyXgCtGHQrlrfA6VTe1usI5jakiiwnwR+Svb?= =?us-ascii?q?Uq?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 24 Mar 2017 19:03:59 -0700
Received: from [10.64.118.210] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 24 Mar 2017 19:03:58 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: John R Levine <johnl@taugh.com>
CC: IETF general list <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request
Date: Fri, 24 Mar 2017 21:04:06 -0500
Message-ID: <0341FB9B-E672-400C-916E-3C6AC0685307@qti.qualcomm.com>
In-Reply-To: <alpine.OSX.2.20.1703241826550.72979@ary.qy>
References: <20170324193951.85037.qmail@ary.lan> <5DAE09F6-D7DE-47B4-ABA6-BC9A92DDEE4E@qti.qualcomm.com> <alpine.OSX.2.20.1703241826550.72979@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TDI01tDOO82zUudQAMP7gX-ZcU4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Mar 2017 02:04:03 -0000

On 24 Mar 2017, at 19:50, John R Levine wrote:

> You've been on the IESG and I haven't, but I'm still scratching my 
> head about why this process needs to change to give the IESG even a 
> little more work after it's been working OK for over a decade.

First of all, this whole discussion started because of something that is 
not working (or at least wasn't anticipated and there are concerns 
about): Dealing with gag orders and the like. My contention was (is) 
that in addressing that, it would help to be absolutely clear in our 
procedure documents that IETF leadership, who will inevitably consist of 
people from different nations under different laws, will have full 
access to any subpoena, in the way that the officers of any organization 
would have access to any legal documents.

Second, I would be perfectly OK (and would not at all be surprised) if 
the IESG were to say to legal counsel, for example, "While you should 
supply the IESG with all subpoenas through our normal procedure, any 
subpoena that simply asks for certified blue sheets you should simply 
satisfy such a subpoena, since blue sheets are public information 
anyway." The addition of any "process" is only to ensure that subpoenas 
are visible to leadership, not because any particular kind of subpoena 
needs review.

>> Whenever someone says, "there's no need for you to know this 
>> information", when not preceded by a long explanation of an 
>> additional harm one is incurring by simply knowing the piece of 
>> information, particularly when "you" is the leadership of an 
>> organization, it sends up a giant red flag for me.
>
> See Klensin's previous message.  The chance of reputation damage to 
> someone named in a subpoena is significant, and the IESG has no legal 
> expertise.

The IESG has legal expertise in the form of a legal advisor, the same 
way the Board of Directors of any corporation does, and the same way I 
do with my personal attorney. And it would behoove any and all of us to 
follow that legal advice and make ourselves aware of what should and 
should not be publicized. And an AD who goes blabbing about the contents 
of any legal document without talking to counsel is not suited to be an 
AD.

> ...judge who asks why we show criminal subpoenas to a bunch of nerds 
> with no legal experience rather than having our lawyer handle it like
> everyone else does.

That's insulting of the intelligence and integrity of the IESG, and I 
think it's the height of hubris on your part. Any judge who asks why 
criminal subpoenas are shown to a "bunch of idiots" on the Board of 
Directors of a corporation who have "no legal experience" should be told 
to piss off; they are the people responsible for the corporation, and 
they can look at any legal document served on the company, and they have 
the eventual responsibility for any information that goes out the door.  
I can tell you that the day my attorney supplies my documents in 
response to a subpoena without asking me, or without having prior 
instructions on particular documents that they can supply, and says 
anything close to, "You don't need to know what's in the subpoena", is 
the day my attorney gets fired.

And please, do consider the case where the subpoena is from an authority 
in <<insert country that you're not impressed with>> and the subpoena is 
for all of the server logs in order to discover whether John, a citizen 
of said country, has been reading messages from a particular WG that 
said the authorities in this country deem to be talking about tools of 
sedition like encryption. I'd like to think that our leadership might 
weigh in on such a request.

Again, I am fine if the IESG wants to delegate the authority to answer 
certain (or even most) subpoenas. But I want our procedures to be clear 
that they can look at them and everyone to be on notice about what that 
implies. What I absolutely do not want is a contractor or advisor who is 
not answerable to the community having the power to withhold information 
from our chosen leadership.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Fri Mar 24 20:09:43 2017
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 A73101293F2 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 20:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qRxY5wzT8txI for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 20:09:40 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C257128AB0 for <ietf@ietf.org>; Fri, 24 Mar 2017 20:09:40 -0700 (PDT)
Received: from [192.168.1.28] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2P39NOw003925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 24 Mar 2017 20:09:25 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: RTBF, was IETF subpoena processes update and a request
From: Joe Touch <touch@isi.edu>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <20170325011825.85855.qmail@ary.lan>
Date: Fri, 24 Mar 2017 20:09:23 -0700
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1DB553AB-CFE3-4537-BEDF-2E4FDAF24895@isi.edu>
References: <20170325011825.85855.qmail@ary.lan>
To: John Levine <johnl@taugh.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MHZwtWbO5JMcILHavGP_nZctkRU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Mar 2017 03:09:42 -0000

> On Mar 24, 2017, at 6:18 PM, John Levine <johnl@taugh.com> wrote:
>=20
> In article <a5e9202a-1c2e-e7c5-989d-745c7fbeaefb@isi.edu> you write:
>> This seems like it also raises the EU's "right to be forgotten"
>> principle, which would affect whether the ISOC can archive even notices
>> that were originally public.
>=20
> Only if ISOC were subject to EU law.  Since ISOC has no physical
> presence in the EU and the IETF has no office anywhere, I don't see
> why EU law would apply.

I was wondering more if it would matter if the subpoena were issued by the E=
U or referred to a party who were an EU citizen.=20

Joe=


From nobody Sat Mar 25 10:23:07 2017
Return-Path: <jari.arkko@piuha.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 F26AE1294B2 for <ietf@ietfa.amsl.com>; Sat, 25 Mar 2017 10:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12vabaqWBv72 for <ietf@ietfa.amsl.com>; Sat, 25 Mar 2017 10:23:03 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8EEF0126CD8 for <ietf@ietf.org>; Sat, 25 Mar 2017 10:23:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B03672CC5E; Sat, 25 Mar 2017 19:23:02 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RfI1WTawHz4e; Sat, 25 Mar 2017 19:23:02 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id AD7AF2CC38; Sat, 25 Mar 2017 19:23:01 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: IETF subpoena processes update and a request
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_9A537065-307F-4AB0-850F-559554F0898B"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <0341FB9B-E672-400C-916E-3C6AC0685307@qti.qualcomm.com>
Date: Sat, 25 Mar 2017 12:23:00 -0500
Cc: IETF general list <ietf@ietf.org>
Message-Id: <303E2204-762B-43A5-9469-1E063948344C@piuha.net>
References: <20170324193951.85037.qmail@ary.lan> <5DAE09F6-D7DE-47B4-ABA6-BC9A92DDEE4E@qti.qualcomm.com> <alpine.OSX.2.20.1703241826550.72979@ary.qy> <0341FB9B-E672-400C-916E-3C6AC0685307@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n2-7Rw8Cj2BzuD5Rtu0WdJHP_2Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Mar 2017 17:23:06 -0000

--Apple-Mail=_9A537065-307F-4AB0-850F-559554F0898B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

John, Pete,

I think you=92re diving deep into the details of one particular aspect
of this problem. That=92s fine, but I wanted to point out that the =
overall
issues are broader. Even on the aspect of creating pushback for
authorities generating unnecessary subpoenas, there are multiple
approaches, document distribution within the leadership is just one
way.

And then there are other issues, worrying about the privacy
of the people mentioned in any subpoena, re-examining if we
could tune what information we retain at the IETF, rewriting the
algorithm on what our staff should do automatically and when
they need to alert the leadership, looking at what other organisations
have done in these kinds of situations, and so on.

FWIW, I think we at the legal committee and leadership want to be on
listening and learning mode about this issue for a while before
jumping into specific ways to address the issues. Keep those thoughts
coming!

Jari


--Apple-Mail=_9A537065-307F-4AB0-850F-559554F0898B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJY1qd0AAoJEM80gCTQU46q7KkP/i23lOK5daBVKpJ/Zk8Wutb+
hui4bzc4ANfvdor/3G9ltFD6MRvhj5ai5kiVhnzpxAlm2vis6pEbMv0HVzcIKt3f
qab15CssdpLg21iVoXukjoX66S7PcqgtzauDPNYcDRNUcTeKlFjenfABfwRB1rdP
S1x9XBsevqhq4NmAWHmioEYiEoimhP/STt4ld2pYoAv+CbYwHCDjsN0BTKkjV0p5
69S1I/wkGZ1cF4pAnBzmAzSKiWqRCWq6bOM12V2ZfNfDUS3f8jbh+rM0aSfnAU/n
IzB3C1vlOmh4gFoIJgHUtrgvFgI1HkfGsof+VWerwPfCVnWvckxQIDDYN35sJ2cn
f97mqBCOcJYTEXGMyckYlTQRcay7dqIU6i9eXlU3OpTuvk2yKHvM3tcblDYTY0SA
W/2NsRBi9JrgnKHTKvusCzu4bTjAzZRkWuSXD7AqvXthRWRNFQ6CFMlnax5Rg+g9
yn+KXHVlis2SR+C/+qt5HQTo/NLvvO5y7e6e9vwg/HYGaQUPIvJsB/lJYYzLCiZF
vXJly2tqWL7O4tIN5dEIGDinuG/kDNFExVTwz/lvlMEQNqhh9e+k9xGysgF8yopQ
t0z7gCjUP/86DA3iptJE3mnMBP8nhrYZc59ft5BiLaRaajdj+j4PeqZMYQNBmZTp
5nodtm7ZFuoilR2QeueQ
=oFeX
-----END PGP SIGNATURE-----

--Apple-Mail=_9A537065-307F-4AB0-850F-559554F0898B--


From nobody Sat Mar 25 12:02:39 2017
Return-Path: <jari.arkko@piuha.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 947E61294A6 for <ietf@ietfa.amsl.com>; Sat, 25 Mar 2017 12:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SrUTV1i_0wh for <ietf@ietfa.amsl.com>; Sat, 25 Mar 2017 12:02:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8AB128959 for <ietf@ietf.org>; Sat, 25 Mar 2017 12:02:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7EF092CC5E for <ietf@ietf.org>; Sat, 25 Mar 2017 21:02:33 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wYXuY8GuCSL2 for <ietf@ietf.org>; Sat, 25 Mar 2017 21:02:33 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id D15522CC38 for <ietf@ietf.org>; Sat, 25 Mar 2017 21:02:32 +0200 (EET) (envelope-from jari.arkko@piuha.net)
From: Jari Arkko <jari.arkko@piuha.net>
X-Pgp-Agent: GPGMail
Content-Type: multipart/signed; boundary="Apple-Mail=_94168C72-47F6-48EF-ABE0-FB828B04292F"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: note takers and jabber scribes for the plenary
Date: Sat, 25 Mar 2017 14:02:31 -0500
Message-Id: <9DB0B4E9-B4AD-4FA3-8901-4CBE0A29CFFC@piuha.net>
To: IETF general list <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oL1XqThUb8rPlbZzNB0rj8ijNV8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Mar 2017 19:02:38 -0000

--Apple-Mail=_94168C72-47F6-48EF-ABE0-FB828B04292F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Folks,

We need one or preferably two volunteers to take notes during the =
plenary on Wednesday. And a Jabber scribe. If you have the ability to =
help us, it would be appreciated!

Jari


--Apple-Mail=_94168C72-47F6-48EF-ABE0-FB828B04292F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJY1r7IAAoJEM80gCTQU46qPwMP/A9zTs0/S4+YQ0e/Qq8Q2CeM
YyUsrKl27Py897v+j3e4hEMmTOA39s63uLJQXE+LfW7DWuct/1NgSPB0GXauwubm
H+fSZkb8mIzGEeaAzt7U4JicblumiFF7kXZZ94ElLi+N+NR7S+SqOtowcSnZc7US
Ku7hFPBDLlFo8NhkIMKLiflxAYO02zw9kfhlxtIGC0XaEcPK/jPXq420YMDbzon+
fcE7ZeqPVmJ9Zh6FThs7nbOpTyz6Aw+keYW7Gf/kL+QgeMI1NORP3QPnuGjTd6kN
1m+88itQetIkgPAc3nFDim4soj88WyxRRligH55se7liImUI9xEePhgKgQRS266p
GDUQFxYb0epyxQUuyng7CVhV9L4sLK54YS3d0Tow3Z7NKmzMsV4TAURLNKp8oCIM
X995VkIELcPNKVyXEqKG30xdiZ4wuMznzgHwsEYAC+KAEAu5/bwbO9jKpdWOS3lE
fIlKSMwao2u7fkBujkA/Ksm3PKkj5XTj1mFRBkTwyVrpMsS1Qx7nL56I29q9h4zN
IKm8Cis0FwYKXyWh15QK/6PLaFlk/VqzNEJbp/iRM2sBZ+t9WK5e3LwDdv7IaiPU
vcKXeoWlTHhNh2KmtwD3LvOGuk/Jc/3tM7jw/l8ka2+Sy2stqsnDEjub+OlnoeoQ
CfVSItKtR/lxVUblnJGU
=VdEu
-----END PGP SIGNATURE-----

--Apple-Mail=_94168C72-47F6-48EF-ABE0-FB828B04292F--


From nobody Sat Mar 25 13:42:34 2017
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 A152A126BFD for <ietf@ietfa.amsl.com>; Sat, 25 Mar 2017 13:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dDAJ6NWRHm3y for <ietf@ietfa.amsl.com>; Sat, 25 Mar 2017 13:42:31 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7103124D68 for <ietf@ietf.org>; Sat, 25 Mar 2017 13:42:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490474550; x=1522010550; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=J3BTFsPkv9lo9aaTYEatZzTXbgxYpavQhy0maqC05YQ=; b=oAnR4V40oxy+ygK6SR3Q/GzrGPVvKIMMLS7pbrtu82QMI6aC7Te7H1fr nBngn5HmpOJRBxkeN8O0lj5T2FlXagb4QEAdvVTrLr5MTUslL+owTjoko nAMJBxjGcYj5+1GkkZ5gvrzlRtMIGU9EegKXsIBkgEU4iFy2xn1NX/x/V I=;
X-IronPort-AV: E=Sophos;i="5.36,222,1486454400"; d="scan'208";a="368126817"
Received: from unknown (HELO ironmsg02-R.qualcomm.com) ([10.53.140.106]) by wolverine02.qualcomm.com with ESMTP; 25 Mar 2017 13:42:30 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8478"; a="926167304"
X-MGA-submission: =?us-ascii?q?MDExOCV+LPe5LE8uVpNXP4IWt2VBiYgZPQAvGQ?= =?us-ascii?q?7j0WC7TTH/NdZy8fZ2trrS/B5V/71FgnZqQh6tjBwm7h9G85usqnt0xi?= =?us-ascii?q?cWtYT0PJs6Z9G6CdQuq6S7KGRCF7b6CtRrzSLGFyB1JukVPxWOBdFQOF?= =?us-ascii?q?CN?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 25 Mar 2017 13:42:30 -0700
Received: from [10.64.105.168] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sat, 25 Mar 2017 13:42:29 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Jari Arkko <jari.arkko@piuha.net>
CC: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request
Date: Sat, 25 Mar 2017 15:42:28 -0500
Message-ID: <BB078B16-C911-4505-9BB0-C0BEE2C6F5C4@qti.qualcomm.com>
In-Reply-To: <303E2204-762B-43A5-9469-1E063948344C@piuha.net>
References: <20170324193951.85037.qmail@ary.lan> <5DAE09F6-D7DE-47B4-ABA6-BC9A92DDEE4E@qti.qualcomm.com> <alpine.OSX.2.20.1703241826550.72979@ary.qy> <0341FB9B-E672-400C-916E-3C6AC0685307@qti.qualcomm.com> <303E2204-762B-43A5-9469-1E063948344C@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lTcr6pjdtgKrbLtwWybqNg7rOMA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Mar 2017 20:42:33 -0000

Thanks Jari. I was absolutely contributing to missing the forest for the 
trees. Sorry for that. My apparent vehemence notwithstanding, it's not 
the particular mechanism I care about; it's that we end up with a 
structure where the IETF maintains control over its own affairs, and 
decides for itself what is (or is not) important to it. You are exactly 
right that we need to figure out what's important first, and figure out 
mechanism to make that happen second.

Discussions of what lawyers should or should not do will be taken to the 
pub.

pr

On 25 Mar 2017, at 12:23, Jari Arkko wrote:

> John, Pete,
>
> I think you’re diving deep into the details of one particular aspect
> of this problem. That’s fine, but I wanted to point out that the 
> overall
> issues are broader. Even on the aspect of creating pushback for
> authorities generating unnecessary subpoenas, there are multiple
> approaches, document distribution within the leadership is just one
> way.
>
> And then there are other issues, worrying about the privacy
> of the people mentioned in any subpoena, re-examining if we
> could tune what information we retain at the IETF, rewriting the
> algorithm on what our staff should do automatically and when
> they need to alert the leadership, looking at what other organisations
> have done in these kinds of situations, and so on.
>
> FWIW, I think we at the legal committee and leadership want to be on
> listening and learning mode about this issue for a while before
> jumping into specific ways to address the issues. Keep those thoughts
> coming!
>
> Jari


-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Sat Mar 25 20:02:22 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BF79A1294CF; Sat, 25 Mar 2017 20:02:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Fernando Gont <fgont@si6networks.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-aqm-codel.all@ietf.org, ietf@ietf.org, aqm@ietf.org, fgont@si6networks.com
Subject: Review of draft-ietf-aqm-codel-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149049732959.11830.18161576308900341179@ietfa.amsl.com>
Date: Sat, 25 Mar 2017 20:02:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DsZJapBUr5pvyVzRL-ZMM3ijiFI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Mar 2017 03:02:10 -0000

Reviewer: Fernando Gont
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-aqm-codel-07
Reviewer: Fernando Gont
Review Date: 2017-03-25
IETF LC End Date: 2017-03-27
IESG Telechat date: 2017-04-13

Summary:
The document is well written. However, there seem to be too many
details that are left out in other associated documents. Whereas such
details (including figures) are needed to understand this document,
they should be included here. Either provide full explanations or
summarize the outcome without details (there's text that somehow
relies on the reading finding such figures elsewhere).


Major issues:
* Section 5.1, page 16:
>    A more detailed explanation with many pictures can be found in
>    http://www.ietf.org/proceedings/84/slides/slides-84-tsvarea-4.pdf
.

Unless I'm missing something, if this document is specifying CoDel,
then all such details should be here.


Minor issues:
* General:
The document would benefit from a terminology section. For example,
only well into the I-D one finds definitions of terms such as "sojourn
times" or "target setpoint". Not sure if those terms are supposed to
be trivial/obvious to most people reading this document, but their
non-definition left me trying to figure out what the terms were about
before I was ale to better understand what you were describing.



Page 3, Section 1:
>    o  simple and efficient implementation (can easily span the
spectrum
>       from low-end, linux-based access points and home routers up
to
>       high-end commercial router silicon)
 
There seems to be an unnecesary implicit "judgement" here, associating
linux-based with low-end, and commercial with high end. I suggest you
modify the text.


Page 10:
>            count_ = (delta > 1 && now - drop_next_ < 16*interval_)?

For clarity, I'd use additional parenthesis here.


Nits/editorial comments: 
* Page 17:
>  The power vs. f curve for any AIMD TCP is monotone decreasing. 

Please expand the acronym.


* Page 17:
>    simulation that this result holds for Reno, Cubic, and
>    Westwood[TSV84].

Missing space.

Thanks!
Fernando






From nobody Sun Mar 26 02:12:00 2017
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 00681124B0A for <ietf@ietfa.amsl.com>; Sun, 26 Mar 2017 02:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mlazjdpcyCRS for <ietf@ietfa.amsl.com>; Sun, 26 Mar 2017 02:11:56 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6D6F12420B for <ietf@ietf.org>; Sun, 26 Mar 2017 02:11:56 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cs4DH-0004zq-7U; Sun, 26 Mar 2017 05:11:51 -0400
Date: Sun, 26 Mar 2017 05:11:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, Jari Arkko <jari.arkko@piuha.net>
cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
Subject: Re: IETF subpoena processes update and a request
Message-ID: <9E387DF69E6A5D294E99F6DF@[192.168.7.38]>
In-Reply-To: <BB078B16-C911-4505-9BB0-C0BEE2C6F5C4@qti.qualcomm.com>
References: <20170324193951.85037.qmail@ary.lan> <5DAE09F6-D7DE-47B4-ABA6-BC9A92DDEE4E@qti.qualcomm.com> <alpine.OSX.2.20.1703241826550.72979@ary.qy> <0341FB9B-E672-400C-916E-3C6AC0685307@qti.qualcomm.com> <303E2204-762B-43A5-9469-1E063948344C@piuha.net> <BB078B16-C911-4505-9BB0-C0BEE2C6F5C4@qti.qualcomm.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-SA-Exim-Connect-IP: ::1
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S-1MuW4eWN9vLeWmBuzUZmt3Z48>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Mar 2017 09:11:58 -0000

--On Saturday, 25 March, 2017 15:42 -0500 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

> Thanks Jari. I was absolutely contributing to missing the
> forest for the trees. Sorry for that. My apparent vehemence
> notwithstanding, it's not the particular mechanism I care
> about; it's that we end up with a structure where the IETF
> maintains control over its own affairs, and decides for itself
> what is (or is not) important to it. You are exactly right
> that we need to figure out what's important first, and figure
> out mechanism to make that happen second.

Pete,
One quick observation.  While this certainly won't be applicable
to all situations, responding to a judge who has said, or
authorized someone to say "do X" by "well, our rules or bylaws
don't allow us to do X so we are either going to just interpret
your order as 'do Y' or we will do nothing until you tell us to
do Y" is not likely to have an attractive outcome.   Of course,
"unattractive" doesn't necessarily mean "undesirable" -- that
depends on what one is trying to accomplish.  It seems to me
that some of what you have suggested is quite analogous to civil
disobedience -- entirely justified and appropriate if one feels
strongly enough about an issue to make that type of public
statement, but something that one should do only if one is
willing to accept the possibility of hostile attacks and/or jail
time.  As you know, those are not just metaphors.

    john




From nobody Sun Mar 26 07:57:39 2017
Return-Path: <iab-chair@iab.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 EC6E7129447; Sun, 26 Mar 2017 07:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gN4kCK76DMXV; Sun, 26 Mar 2017 07:57:30 -0700 (PDT)
Received: from iab.org (dhcp-8725.meeting.ietf.org [31.133.135.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 8AA23129451; Sun, 26 Mar 2017 07:57:30 -0700 (PDT)
Date: Sun, 26 Mar 2017 10:57:28 -0400
From: IAB Chair <iab-chair@iab.org>
To: ietf-announce@ietf.org, ietf@ietf.org
Subject: IAB report to the community before IETF 98
Message-ID: <20170326145728.GA30502@iab.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k5jgS6S_szLHKrV6msUF9BvOkx4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Mar 2017 14:57:33 -0000

Dear colleagues,

This is the usual IAB report to the community about our activities
since the previous meeting (in this case, since IETF 97 in Seoul).
As ever, we hope that this form allows you to prepare topics you might
want to discuss during the open mic. But of course, if you have views
you want to make known by email, we're easy to reach: send mail to
architecture-discuss@iab.org to reach our public discussion list, and
iab@iab.org to reach just the IAB.

The IAB has a few chartered roles. We confirm the appointments to the
IESG and perform standards process oversight and handle appeals. We
also perform architectural oversight (including appointing the IRTF
Chair), we manage the RFC series and the IETF's relationship with
IANA, and we handle liaisons and appointments both to ISOC and to
other organizations. We try to ensure that anything we do is part of
one of these areas of responsibility, and we try to make sure these
are all covered.

Here's what we've been doing since IETF 97.  You can find mention of
each of these on the IAB pages at https://www.iab.org (where there's
more background, too):

    • RFC Format Changes. You've been hearing for some time about
      these. In December, the requirements were published as RFCs
      7990-7998. There remains work to be done in this area, as the
      project shifts to building and testing the tools required, but
      for now, the IAB returns more immediate oversight to the RFC
      Series Oversight Committee. (RFC Series)

    • Appointment to the ISOC Board of Trustees.  The IAB made its
      appointment to the ISOC BoT.  We thank the community for the
      feedback on candidates.  ISOC announces its BoT itself, so look
      for that announcement in the near future. (Liaisons and appointments)

    • Reappointment of Independent Submission Editor.  The IAB
      reappointed Nevil Brownlee as the Independent Submission Editor
      (ISE).  We appreciate Nevil's willingness to serve for another
      year.  (RFC Series)

    • Appointment to IETF Administrative Oversight Committee (IAOC).
      The IAB alternates with the IESG in making 2-year appointments
      to the IAOC.  The IAB appointed Kaveh Ranjbar.  We thank the
      community for the comments on candidates. (Liaisons and appointments)

    • Public comment responses.  The IAB tries to respond to requests
      for comment when it believes that the request impinges on the
      architecture or functioning of the Internet and and that a
      response may be of general use to the community.  Since Seoul
      we commented on a request from ICANN for comment on display of
      RDDS output, a request from ICANN for comment on Identifier
      Technology Health Indicators, and to a request from the United
      States NTIA on Fostering the Advancement of the Internet of
      Things.  The IAB also made a statement on OCSP Stapling.
      (Architectural oversight)

    • Process documents.  Thanks to the IANA Stewardship Transition
      last year, the IAB has some new appointments to make.  We have
      encoded our procedures for making two such appointments in RFCs
      8090 ("Appointment Procedures for the IETF Representatives to
      the Community Coordination Group") and RFC 8128 ("IETF
      Appointment Procedures for the ICANN Root Zone Evolution Review
      Committee"). (Liaisons and appointments)

    • Confirmation of the IESG.  This year, this task was more
      exciting than usual because of people moving around on the
      IESG. (IESG confirmation)
    
        DOCUMENTS

You can always find the documents the IAB has adopted and is working
on at https://datatracker.ietf.org/stream/iab.  

There is one document about the RFC series:

draft-iab-rfc-preservation-04
    Digital Preservation Considerations for the RFC Series (at RFC
    Editor)

There are in process some workshop reports:

draft-iab-carisreport-02
    Coordinating Attack Response at Internet Scale (CARIS) Workshop
    Report (at the RFC Editor)
draft-iab-iotsi-workshop-01
    Report from the Internet of Things (IoT) Semantic Interoperability
    (IOTSI) Workshop 2016
draft-iab-iotsu-workshop-01
    Report from the Internet of Things (IoT) Software Update (IoTSU)
    Workshop 2016 (in community review, nearly done)
draft-nrooney-marnew-report-02
    IAB Workshop on Managing Radio Networks in an Encrypted World
    (MaRNEW) Report (expired but adopted; the new version of the file
    has not been uploaded since Seoul)

The other documents are related to the IAB's architectural functions:

draft-iab-privsec-confidentiality-mitigations-08
    Confidentiality in the Face of Pervasive Surveillance
draft-iab-protocol-transitions-08
    Out With the Old and In With the New: Planning for Protocol
    Transitions (in community review, nearly done)
draft-iab-web-pki-problems-05
    Improving the Public Key Infrastructure (PKI) for the World Wide
    Web

    PROGRAMS

The IAB organizes its work, for the most part, into programs.  There
are basically two classes: management programs and architectural
programs.  The former are how we handle the oversight of various
things, and the latter are where we do architectural work.  The former
are expected to last as long as the IAB continues to have that
oversight function; the latter last until the IAB has come to a
conclusion on the relevant group of topics, and we expect them to wind
down afterwards.  Programs are listed at
https://www.iab.org/activities/programs/.  As a general rule, each
architectural program has a public mailing list, as well as a
member-specific list.  For subscription instructions, see
https://www.iab.org/iab-mailing-lists/..

We review programs periodically.  In the period since Seoul, we
reviewed the IANA Evolution Program.  The program did a lot of work in
the period prior to the IANA stewardship transition; but with that
event over the IAB determined that we could expect a period of
quiet. Accordingly, the membership of the program has been scaled
back, and the work plan for the program has reverted to the usual
oversight function that was its normal business prior to the
transition work.

The IAB also reviewed the Names and Identifiers Program (INIP).  The
IAB observed that the program had not achieved most of its goals over
its time, and also noted that there did not seem to be the energy and
evidence of progress that might indicate the results would change.
It's worth noting that our discussion of this situation set out a new
presumption for the management of programs.  People have sometimes
made an analogy between programs and IETF working groups, but they
serve different purposes.  Unlike working groups, which have a
procedural function on top of the other functions, IAB programs are
inexpensive to set up and close down.  Therefore, the IAB decided to
close INIP, even though the issues that inspired the program remain
unresolved and even though the IAB continues to think there is a
problem that needs some architectural input.  It appears there are
some other programs that would benefit from similar treatment, and the
IAB will be reviewing those in the near future.

The IAB also reviewed the RFC Series Oversight Committee (RSOC).  This
is an unusual program in that it is formally created by an RFC, but
internally we operate it like any other oversight program.  This
program is functioning well.  The two major work items are any needed
assistance in digesting the format changes, and the RSE RFP and
selection process (which will happen this year).  There was some
discussion of replacing Adam Roach on the RSOC were he to be appointed
as an Area Director, but the IAB decided against it.  There is also a
potentially important thing to draw to community attention: there is a
new guideline for the display of DOIs, and RSOC is unhappy with it.
If the guideline is to be enforced, RSOC plans to recommend
discontinuing the use of DOIs.  More discussion is in the IAB meeting
minutes from 2017-01-11.

We added a new program before IETF 97: the Plenary Planning Program,
to ensure that the IAB component of the IETF plenary is improved.  The
program is fairly new, and this is only the second meeting where its
influence is being felt, so it would be a good time to get feedback
about whether things are getting better.

    OPEN COMMUNICATIONS

For some years, the IAB has had a wiki that it uses for its internal
communications.  Because of the role of the IAB, especially in respect
of appointments and outward-facing activities, that wiki has always
been private to the IAB.  Some materials ought to be handled
privately.

Nevertheless, there are lots of things the IAB discusses that do not
need to be private.  Yet the availability of the private wiki
naturally meant that materials tended to end up there even if they did
not need to be private.

To solve this, the IAB has created a separate, public wiki.  It is at
https://www.iab.org/wiki/index.php/Main_Page.  There have been some
teething problems due to accounts not working as expected (and due to
old habits dying hard), but we're working to put any work that does
not need to be private in the public wiki.  

    RENEWAL

IAB terms begin and end with the first IETF meeting of the year, so
this report is the final one from this IAB.  The new IAB will begin in
Chicago, at IETF 98:

Alissa Cooper, IETF Chair, Cisco
Brian Trammell, ETH
Erik Nordmark, Independent
Gabriel Montenegro, Microsoft
Jari Arkko, Ericsson
Jeff Tantsura, Futurewei
Joe Hildebrand, Mozilla
Lee Howard, Independent
Mark Nottingham, Akamai Technologies
Martin Thomson, Mozilla
Robert Sparks, Oracle
Suzanne Woolf, Independent
Ted Hardie, Google

We thank outgoing members Ralph Droms, Russ Housley, Andrew Sullivan,
and Dave Thaler for their service.  At IETF 98, the IAB will also
select its new chair and will announce who it is during the course of
the meeting.

Respectfully submitted,

Andrew Sullivan
For the IAB

-- 
IAB Chair (Andrew Sullivan)
iab-chair@iab.org


From nobody Sun Mar 26 12:07:27 2017
Return-Path: <Lucas.Pardue@bbc.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 DCDD4126E01; Sun, 26 Mar 2017 12:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOjvZcPCjE_y; Sun, 26 Mar 2017 12:07:17 -0700 (PDT)
Received: from mailout0.cwwtf.bbc.co.uk (mailout0.cwwtf.bbc.co.uk [132.185.160.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E2E71294B0; Sun, 26 Mar 2017 12:07:16 -0700 (PDT)
Received: from BGB01XI1010.national.core.bbc.co.uk (bgb01xi1010.national.core.bbc.co.uk [10.161.14.14]) by mailout0.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id v2QJ7FIF027075; Sun, 26 Mar 2017 20:07:15 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1010.national.core.bbc.co.uk ([10.161.14.14]) with mapi id 14.03.0319.002; Sun, 26 Mar 2017 20:07:14 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>, "98attendees@ietf.org" <98attendees@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Video Streaming Bar BoF @ IETF98
Thread-Topic: Video Streaming Bar BoF @ IETF98
Thread-Index: AQHSndU57AttaXTq/02muQPDHsLP+aGhOviAgAZNx78=
Date: Sun, 26 Mar 2017 19:07:13 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A37707D6A@bgb01xud1012>
References: <D4EF03A1.D0EA4%glenn.deen@nbcuni.com>, <D4F810F1.D1665%glenn.deen@nbcuni.com>
In-Reply-To: <D4F810F1.D1665%glenn.deen@nbcuni.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.211]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-11.0.0.4179-8.100.1062-22968.001
x-tm-as-result: No--35.863200-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_7CF7F94CB496BF4FAB1676F375F9666A37707D6Abgb01xud1012_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LwyQsS87wrnmVt4rx1A1mzEZdR8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Mar 2017 19:07:20 -0000

--_000_7CF7F94CB496BF4FAB1676F375F9666A37707D6Abgb01xud1012_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgR2xlbm4sIGFsbCwNCg0KVGhhbmsgeW91IGZvciBhcnJhbmdpbmcgdGhpcy4NCg0KQXQgdGhl
IEJCQyB3ZSBhcmUgdmVyeSBpbnRlcmVzdGluZyBpbiBzb2x2aW5nIHNvbWUgb2YgdGhlIGNoYWxs
ZW5nZXMgZm9yIHN0cmVhbWluZyBhdCBzY2FsZS4gU29tZSBvZiBvdXIgcmVjZW50IHJlc2VhcmNo
IGhhcyBmb2N1c2VkIG9uIHRoZSB0cmFuc3BvcnQgb2YgTVBFRy1EQVNIIG92ZXIgbXVsdGljYXN0
LCBpbiBwYXJ0aWN1bGFyIGFkZHJlc3Npbmcgc29tZSBvZiB0aGUgaXNzdWVzIGFyb3VuZCBjbGll
bnRzJyBhYmlsaXR5IHRvIGRpc2NvdmVyIHN1Y2ggc2VydmljZXMgYW5kIHJldXNlIG9mIGV4aXN0
aW5nIHRlY2hub2xvZ2llcy4NCg0KVG8gdGhpcyBlbmQsIHdlIGhhdmUgcHVibGlzaGVkIGFuIEkt
RCB0aGF0IGRlc2NyaWJlcyBhIGdlbmVyaWMgYnVsayB0cmFuc3BvcnQgdXNpbmcgSFRUUCBvdmVy
IG11bHRpY2FzdCBRVUlDIChkcmFmdC1wYXJkdWUtcXVpYy1odHRwLW1jYXN0PGh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1wYXJkdWUtcXVpYy1odHRwLW1jYXN0LTAwPikuIFdlIGFs
c28gaGF2ZSBhIHByb3RvdHlwZSBvZiB0aGlzLCBzcGVjaWFsaXNlZCBmb3IgYSBsaXZlIE1QRUct
REFTSCBzdHJlYW0sIHdoaWNoIHdlIGhhdmUgZGVtb25zdHJhdGVkIHdpdGggQXV0b21hdGljIE11
bHRpY2FzdCBUdW5uZWxsaW5nIChBTVQpIGF0IHRoZSBIYWNrYXRob24uDQoNCldlJ2xsIGJlIGF0
IHRoZSBCYXIgYm9GIGFuZCBob3BlIHRvIG1lZXQgbGlrZSBtaW5kZWQgc291bHMuDQoNClJlZ2Fy
ZHMNCkx1Y2FzIFBhcmR1ZQ0KQkJDIFImRA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCkZyb206IDk4YXR0ZW5kZWVzIFs5OGF0dGVuZGVlcy1ib3VuY2VzQGlldGYub3JnXSBvbiBi
ZWhhbGYgb2YgRGVlbiwgR2xlbm4gKE5CQ1VuaXZlcnNhbCkgW0dsZW5uLkRlZW5AbmJjdW5pLmNv
bV0NClNlbnQ6IDIyIE1hcmNoIDIwMTcgMTg6MzcNClRvOiA5OGF0dGVuZGVlc0BpZXRmLm9yZzsg
aWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogWzk4YXR0ZW5kZWVzXSBGVzogVmlkZW8gU3RyZWFtaW5n
IEJhciBCb0YgQCBJRVRGOTgNCg0KDQpJIHdhbnQgdG8gaW52aXRlIGFueW9uZSB3aG8gaXMgaW50
ZXJlc3RlZCBpbiBJbnRlcm5ldCBWaWRlbyBTdHJlYW1pbmcgdG8gYSBCYXIgQm9GIG9uIEludGVy
bmV0IFZpZGVvIFN0cmVhbWluZyB0byBiZSBoZWxkIGF0IElFVEY5OC4NCg0KVGltZTogICAgIE1v
bmRheSBPY3QgMjd0aCAgYXQgNjozMC03OjMwcG0gQ0RUDQpXaGVyZTogIENvbHVtYnVzIFRhcCBh
dCB0aGUgRmFpcm1vbnQgKHRoaXMgaXMgdGhlIG92ZXJmbG93IGhvdGVsIGFuZCBpcyBjb25uZWN0
ZWQgdG8gdGhlIHZlbnVlIHZpYSB0aGUgdW5kZXJncm91bmQgbWFsbCkuDQoNClRoaXMgaXMgb3Bl
biB0byBhbnlvbmUgaW50ZXJlc3RlZCBzbyBwbGVhc2UgZmVlbCBmcmVlIHRvIHBhc3MgdGhpcyBp
bnZpdGUgYWxvbmcuICBJJ20gdG9sZCB0aGF0IHRoZSBDb2x1bWJ1cyBUYXAgYWxzbyBoYXMgYSBm
aW5lIHNlbGVjdGlvbiBvZiBiZWVyIQ0KDQpUaGlzIGlzIGEgbm9uLWhvc3RlZCBldmVudCwgbWVh
bmluZyBubyBmcmVlIGJlZXIsIGJ1dCB0aGVyZSB3aWxsIGJlIGdyZWF0IGRpc2N1c3Npb24gb2Yg
SW50ZXJuZXQgdmlkZW8hDQoNCnJlZ2FyZHMNCkdsZW5uIERlZW4NCg0KLS0tLS0tDQoNClRvcGlj
OiBWaWRlbyBTdHJlYW1pbmcgZVh0ZW5zaW9ucyAoVi1TWCkNCg0KRGVzY3JpcHRpb246DQoNCkR1
ZSB0byBpdHMgc2l6ZSBhbmQgc2Vuc2l0aXZpdHkgdG8gbmV0d29yayBjb25kaXRpb25zLCB0aGUg
dHJhbnNwb3J0IG9mIHZpZGVvIG92ZXIgdGhlIEludGVybmV0IGhhcyBoaWdobGlnaHRlZCBhIHNp
Z25pZmljYW50IHNjYWxhYmlsaXR5IHByb2JsZW0gZm9yIHRoZSBJbnRlcm5ldC4gIE9uIHRoZSBi
ZWxpZWYgdGhhdCBhZGRyZXNzaW5nIHRoaXMgc2NhbGFiaWxpdHkgcHJvYmxlbSByZXF1aXJlcyBi
ZXR0ZXIgaW50ZWdyYXRpb24gYmV0d2VlbiBhcHBsaWNhdGlvbiB0cmFuc3BvcnQgYW5kIG5ldHdv
cmtpbmcgdGVjaG5vbG9naWVzIGFuZCBsZXZlcmFnaW5nIElQdjYsIHRoaXMgQmFyIEJPRiB3aWxs
IHNvbGljaXQgZXhwZXJpZW5jZXMgb2YgdGhlIHNjYWxpbmcgcHJvYmxlbSBhcyBwZXJjZWl2ZWQg
ZnJvbSBkaWZmZXJlbnQgcGFydHMgb2YgdGhlIGluZHVzdHJ5IChuZXR3b3JrLCBwcm9kdWNlciwg
dmVuZG9ycykuDQoNClZpZGVvIGlzIHdpdGhvdXQgcml2YWwgdGhlIHRvcCB1c2Ugb2YgSW50ZXJu
ZXQgYmFuZHdpZHRoLCBhbmQgaXRzIGV2ZXIgZ3Jvd2luZyBkZW1hbmQgZm9yIG1vcmUgYmFuZHdp
ZHRoIGVhc2lseSBvdXQgcGFjZXMgdGhlIG5ldyBjYXBhY2l0eSBiZWluZyBhZGRlZCBib3RoIGds
b2JhbGx5IGFuZCByZWdpb25hbGx5IHdpdGggbm8gbGV0IHVwIGluIHNpZ2h0LiAgIFVzZXJzIGFy
ZSBmcnVzdHJhdGVkIGJ5IHF1YWxpdHksIGJ1ZmZlcmluZywgYW5kIHN0dXR0ZXJpbmcgcHJvYmxl
bXMuIFZpZGVvIHByb3ZpZGVycyBhbmQgYWNjZXNzIG5ldHdvcmtzIGFyZSBpbnZlc3RpbmcgaGVh
dmlseSB0byBrZWVwIHVwIHdpdGggZGVtYW5kLiAgU2lnbmlmaWNhbnQgd29yayBoYXMgYmUgZG9u
ZSBhdCB0aGUgYXBwbGljYXRpb24gbGF5ZXIgcHJvZHVjaW5nIG1vcmUgZWZmaWNpZW50IGNvZGVj
cyBhbmQgaW5ub3ZhdGl2ZSBhZGFwdGl2ZSBiaXRyYXRlIHRyYW5zcG9ydHMgbGlrZSBNUEVHLURB
U0guICBUaGVzZSBhY2Nlc3MgaW52ZXN0bWVudHMgYW5kIGFwcGxpY2F0aW9uIGxheWVyIHdvcmsg
aGF2ZSBoZWxwZWQgYnV0IHRoZXkgYWxvbmUgaGF2ZSBub3QgYmVlbiBlbm91Z2guDQoNCkEgdGFy
Z2V0IG9mIGFueSBldmVudHVhbCB3b3JrIGFuZCBwcm9kdWN0IGlzIHRvIGVuYWJsZSB2aWRlbyBh
bmQgbmV0d29yayByb3V0aW5nIC8gbWFuYWdlbWVudCB0byB3b3JrIG1vcmUgY29vcGVyYXRpdmVs
eSBhbmQgZWZmaWNpZW50bHkgdG8gdHJhbnNwb3J0IHZpZGVvLiAgU3VjY2Vzc2Z1bCBhcHByb2Fj
aGVzIHdpbGwgbmVlZCB0byBkbyBzbyBpbiBhIGJhY2t3YXJkIGNvbXBhdGlibGUgd2F5cyB0byBw
ZXJtaXQgZXhpdGluZyBkZXZpY2VzIGFuZCBwbGF5ZXJzIHRvIHRha2UgYWR2YW50YWdlIG9mIHRo
ZSBpbXByb3ZlZCBuZXR3b3JrIGVmZmljaWVuY2llcy4NCg0KT25lIHByb3Bvc2VkIGFwcHJvYWNo
IHRvIGRlYWxpbmcgd2l0aCBpc3N1ZXMgd2FzIG91dGxpbmVkIGluIHRoZSBHbGFzcyB0byBHbGFz
cyBJbnRlcm5ldCBFY29zeXN0ZW0gQm9GIHByb3Bvc2FsIOKAlCByZWxhdGVkIGRyYWZ0cyBhbmQg
bWFpbGluZyBsaXN0IGluZm9ybWF0aW9uIGlzIHByb3ZpZGVkIGJlbG93LiAgQSBkZW1vbnN0cmF0
aW9uIG9mIEdHSUUgd2lsbCBiZSBwcm92aWRlZCBkdXJpbmcgdGhlIEJvRiwgZm9yIGlsbHVzdHJh
dGlvbiBwdXJwb3Nlcy4gIERpc2N1c3Npb24gaXMgZXhwZWN0ZWQgYW5kIGVuY291cmFnZWQgdG8g
cmFuZ2UgZnVydGhlciB0aGFuIHRoZSBzcGVjaWZpYyBHR0lFIHByb3Bvc2FsLg0KDQpUaGlzIHdp
bGwgYmUgYW4gaW50ZXJhY3RpdmUgZGlzY3Vzc2lvbiBhbmQgd2UgZW5jb3VyYWdlIGFueW9uZSB3
aXRoIGFuIGludGVyZXN0IGluIHRoaXMgdG9waWMgdG8gY29tZSBhbmQgc2hhcmUgdGhlaXIgaWRl
YXMuDQoNCg0KICAgIEFnZW5kYQ0KSW50cm9kdWN0aW9uDQpDb250ZXh0IHNldHRpbmcgWzVtaW5d
DQoNClJvdW5kdGFibGUgZGlzY3Vzc2lvbiBvZiB0aGUgaXNzdWUocykgWzMwbWluXQ0KDQpEZW1v
IG9mIEdHSUUgcHJvdG90eXBlIFsxMG1pbl0NCg0KV2hlcmUgZnJvbSBoZXJlPyBbMTVtaW5dDQpQ
b3RlbnRpYWwgZm9yIElFVEYgd29yayDigJQgaXMgdGhlcmUgaW50ZXJlc3QgdG8gcHVyc3VlPw0K
V29yayBmb3Igb3RoZXIgZ3JvdXBzPw0KDQoNCg0KICAgICAgICBNYWlsaW5nIExpc3Q6IOKAi2h0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZ2dpZQ0KDQogICAgICAgIFJlbGV2
YW50IGRyYWZ0czoNCiAgICAgICAgICAgIGRyYWZ0LWRlZW4tZGFpZ2xlLWdnaWUtMDIgOiAgR2xh
c3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIEludHJvZHVjdGlvbg0KICAgZHJhZnQtcm9z
ZS1kZWVuLWdnaWUtdXNlLWNhc2VzLTAwIDogR0dJRSBJbnRlcm5ldCBWaWRlbyBVc2UgQ2FzZXMN
CiAgIGRyYWZ0LWRhaWdsZS1kZWVuLWdnaWUtdXJpLXNuYXB0ci0wMCA6ICBHbGFzcyB0byBHbGFz
cyBJbnRlcm5ldCBFY29zeXN0ZW0gVVJJIGFuZCBTLU5BUFRSIFVzZQ0KICAgZHJhZnQtZGVlbi1u
YWlrLWdnaWUtbWVuLW1wZWctZGFzaC0wMCA6IFVzaW5nIE1lZGlhIEVuY29kaW5nIE5ldHdvcmtz
IHRvIGFkZHJlc3MgTVBFRy1EQVNIIHZpZGVvDQoNClRpbWU6ICAgICBNb25kYXkgT2N0IDI3dGgg
IGF0IDY6MzAtNzozMHBtIENEVA0KV2hlcmU6ICBDb2x1bWJ1cyBUYXAgYXQgdGhlIEZhaXJtb250
ICh0aGlzIGlzIHRoZSBvdmVyZmxvdyBob3RlbCBhbmQgaXMgY29ubmVjdGVkIHRvIHRoZSB2ZW51
ZSB2aWEgdGhlIHVuZGVyZ3JvdW5kIG1hbGwpLg0KDQoNCg0K

--_000_7CF7F94CB496BF4FAB1676F375F9666A37707D6Abgb01xud1012_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgZGlyPSJsdHIiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUi
IGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8c3R5bGUgdHlwZT0idGV4dC9j
c3MiIGlkPSJvd2FQYXJhU3R5bGUiPjwvc3R5bGU+PHN0eWxlIHR5cGU9InRleHQvY3NzIj4KOnJv
b3QgLmJiY2NvbV9zcG9uc29yOm5vdChib2R5KSwKOnJvb3QgLmJiY2NvbV9jb21wYW5pb24KeyBk
aXNwbGF5OiBub25lICFpbXBvcnRhbnQ7IH08L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgc3R5bGU9
IndvcmQtd3JhcDpicmVhay13b3JkOyBjb2xvcjpyZ2IoMCwwLDApOyBmb250LXNpemU6MTRweDsg
Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmIiBmcHN0eWxlPSIxIiBvY3NpPSIwIj4NCjxk
aXYgc3R5bGU9ImRpcmVjdGlvbjogbHRyO2ZvbnQtZmFtaWx5OiBUYWhvbWE7Y29sb3I6ICMwMDAw
MDA7Zm9udC1zaXplOiAxMHB0OyI+SGkgR2xlbm4sIGFsbCwNCjxkaXY+PGJyPg0KPC9kaXY+DQo8
ZGl2PlRoYW5rIHlvdSBmb3IgYXJyYW5naW5nIHRoaXMuJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4N
CjwvZGl2Pg0KPGRpdj5BdCB0aGUgQkJDIHdlIGFyZSB2ZXJ5IGludGVyZXN0aW5nIGluIHNvbHZp
bmcgc29tZSBvZiB0aGUgY2hhbGxlbmdlcyBmb3Igc3RyZWFtaW5nIGF0IHNjYWxlLiBTb21lIG9m
IG91ciByZWNlbnQgcmVzZWFyY2ggaGFzIGZvY3VzZWQgb24gdGhlIHRyYW5zcG9ydCBvZiBNUEVH
LURBU0ggb3ZlciBtdWx0aWNhc3QsIGluIHBhcnRpY3VsYXIgYWRkcmVzc2luZyBzb21lIG9mIHRo
ZSBpc3N1ZXMgYXJvdW5kIGNsaWVudHMnIGFiaWxpdHkgdG8gZGlzY292ZXINCiBzdWNoIHNlcnZp
Y2VzIGFuZCByZXVzZSBvZiBleGlzdGluZyB0ZWNobm9sb2dpZXMuJm5ic3A7PC9kaXY+DQo8ZGl2
Pjxicj4NCjwvZGl2Pg0KPGRpdj5UbyB0aGlzIGVuZCwgd2UgaGF2ZSBwdWJsaXNoZWQgYW4gSS1E
IHRoYXQgZGVzY3JpYmVzIGEgZ2VuZXJpYyBidWxrIHRyYW5zcG9ydCB1c2luZyBIVFRQIG92ZXIg
bXVsdGljYXN0IFFVSUMgKDxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1wYXJkdWUtcXVpYy1odHRwLW1jYXN0LTAwIj5kcmFmdC1wYXJkdWUtcXVpYy1odHRwLW1jYXN0
PC9hPikuIFdlIGFsc28gaGF2ZSBhIHByb3RvdHlwZSBvZiB0aGlzLCBzcGVjaWFsaXNlZA0KIGZv
ciBhIGxpdmUgTVBFRy1EQVNIIHN0cmVhbSwgd2hpY2ggd2UgaGF2ZSBkZW1vbnN0cmF0ZWQgd2l0
aCBBdXRvbWF0aWMgTXVsdGljYXN0IFR1bm5lbGxpbmcgKEFNVCkgYXQgdGhlIEhhY2thdGhvbi48
L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PldlJ2xsIGJlIGF0IHRoZSBCYXIgYm9GIGFu
ZCBob3BlIHRvIG1lZXQgbGlrZSBtaW5kZWQgc291bHMuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2
Pg0KPGRpdj5SZWdhcmRzPC9kaXY+DQo8ZGl2Pkx1Y2FzIFBhcmR1ZTwvZGl2Pg0KPGRpdj5CQkMg
UiZhbXA7RDxicj4NCjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OiBUaW1lcyBOZXcgUm9tYW47IGNv
bG9yOiAjMDAwMDAwOyBmb250LXNpemU6IDE2cHgiPg0KPGhyIHRhYmluZGV4PSItMSI+DQo8ZGl2
IGlkPSJkaXZScEY1MjQ4OCIgc3R5bGU9ImRpcmVjdGlvbjogbHRyOyI+PGZvbnQgZmFjZT0iVGFo
b21hIiBzaXplPSIyIiBjb2xvcj0iIzAwMDAwMCI+PGI+RnJvbTo8L2I+IDk4YXR0ZW5kZWVzIFs5
OGF0dGVuZGVlcy1ib3VuY2VzQGlldGYub3JnXSBvbiBiZWhhbGYgb2YgRGVlbiwgR2xlbm4gKE5C
Q1VuaXZlcnNhbCkgW0dsZW5uLkRlZW5AbmJjdW5pLmNvbV08YnI+DQo8Yj5TZW50OjwvYj4gMjIg
TWFyY2ggMjAxNyAxODozNzxicj4NCjxiPlRvOjwvYj4gOThhdHRlbmRlZXNAaWV0Zi5vcmc7IGll
dGZAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gWzk4YXR0ZW5kZWVzXSBGVzogVmlkZW8g
U3RyZWFtaW5nIEJhciBCb0YgQCBJRVRGOTg8YnI+DQo8L2ZvbnQ+PGJyPg0KPC9kaXY+DQo8ZGl2
PjwvZGl2Pg0KPGRpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xLX1NSQ19CT0RZ
X1NFQ1RJT04iPg0KPGRpdj4NCjxkaXYgc3R5bGU9IndvcmQtd3JhcDpicmVhay13b3JkOyBjb2xv
cjpyZ2IoMCwwLDApOyBmb250LXNpemU6MTRweDsgZm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNl
cmlmIj4NCjxkaXY+SSB3YW50IHRvIGludml0ZSBhbnlvbmUgd2hvIGlzIGludGVyZXN0ZWQgaW4g
SW50ZXJuZXQgVmlkZW8gU3RyZWFtaW5nIHRvIGEgQmFyIEJvRiBvbiBJbnRlcm5ldCBWaWRlbyBT
dHJlYW1pbmcgdG8gYmUgaGVsZCBhdCBJRVRGOTguPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0K
PGRpdj5UaW1lOiAmbmJzcDsgJm5ic3A7IE1vbmRheSBPY3QgMjd0aCAmbmJzcDthdCA2OjMwLTc6
MzBwbSBDRFQ8L2Rpdj4NCjxkaXY+V2hlcmU6ICZuYnNwO0NvbHVtYnVzIFRhcCBhdCB0aGUgRmFp
cm1vbnQgKHRoaXMgaXMgdGhlIG92ZXJmbG93IGhvdGVsIGFuZCBpcyBjb25uZWN0ZWQgdG8gdGhl
IHZlbnVlIHZpYSB0aGUgdW5kZXJncm91bmQgbWFsbCkuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2
Pg0KPGRpdj5UaGlzIGlzIG9wZW4gdG8gYW55b25lIGludGVyZXN0ZWQgc28gcGxlYXNlIGZlZWwg
ZnJlZSB0byBwYXNzIHRoaXMgaW52aXRlIGFsb25nLiAmbmJzcDtJJ20gdG9sZCB0aGF0IHRoZSBD
b2x1bWJ1cyBUYXAgYWxzbyBoYXMgYSBmaW5lIHNlbGVjdGlvbiBvZiBiZWVyISAmbmJzcDs8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9
Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJ3b3JkLXdyYXA6YnJl
YWstd29yZDsgY29sb3I6cmdiKDAsMCwwKTsgZm9udC1zaXplOjE0cHg7IGZvbnQtZmFtaWx5OkNh
bGlicmksc2Fucy1zZXJpZiI+DQo8ZGl2PlRoaXMgaXMgYSBub24taG9zdGVkIGV2ZW50LCBtZWFu
aW5nIG5vIGZyZWUgYmVlciwgYnV0IHRoZXJlIHdpbGwgYmUgZ3JlYXQgZGlzY3Vzc2lvbiBvZiBJ
bnRlcm5ldCB2aWRlbyE8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PnJlZ2FyZHM8L2Rp
dj4NCjxkaXY+R2xlbm4gRGVlbjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+LS0tLS0t
PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5Ub3BpYzogVmlkZW8gU3RyZWFtaW5nIGVY
dGVuc2lvbnMgKFYtU1gpPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5EZXNjcmlwdGlv
bjogJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5EdWUgdG8gaXRzIHNpemUg
YW5kIHNlbnNpdGl2aXR5IHRvIG5ldHdvcmsgY29uZGl0aW9ucywgdGhlIHRyYW5zcG9ydCBvZiB2
aWRlbyBvdmVyIHRoZSBJbnRlcm5ldCBoYXMgaGlnaGxpZ2h0ZWQgYSBzaWduaWZpY2FudCBzY2Fs
YWJpbGl0eSBwcm9ibGVtIGZvciB0aGUgSW50ZXJuZXQuICZuYnNwO09uIHRoZSBiZWxpZWYgdGhh
dCBhZGRyZXNzaW5nIHRoaXMgc2NhbGFiaWxpdHkgcHJvYmxlbSByZXF1aXJlcyBiZXR0ZXIgaW50
ZWdyYXRpb24gYmV0d2Vlbg0KIGFwcGxpY2F0aW9uIHRyYW5zcG9ydCBhbmQgbmV0d29ya2luZyB0
ZWNobm9sb2dpZXMgYW5kIGxldmVyYWdpbmcgSVB2NiwgdGhpcyBCYXIgQk9GIHdpbGwgc29saWNp
dCBleHBlcmllbmNlcyBvZiB0aGUgc2NhbGluZyBwcm9ibGVtIGFzIHBlcmNlaXZlZCBmcm9tIGRp
ZmZlcmVudCBwYXJ0cyBvZiB0aGUgaW5kdXN0cnkgKG5ldHdvcmssIHByb2R1Y2VyLCB2ZW5kb3Jz
KS4gJm5ic3A7Jm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5WaWRlbyBpcyB3
aXRob3V0IHJpdmFsIHRoZSB0b3AgdXNlIG9mIEludGVybmV0IGJhbmR3aWR0aCwgYW5kIGl0cyBl
dmVyIGdyb3dpbmcgZGVtYW5kIGZvciBtb3JlIGJhbmR3aWR0aCBlYXNpbHkgb3V0IHBhY2VzIHRo
ZSBuZXcgY2FwYWNpdHkgYmVpbmcgYWRkZWQgYm90aCBnbG9iYWxseSBhbmQgcmVnaW9uYWxseSB3
aXRoIG5vIGxldCB1cCBpbiBzaWdodC4gJm5ic3A7IFVzZXJzIGFyZSBmcnVzdHJhdGVkIGJ5IHF1
YWxpdHksIGJ1ZmZlcmluZywgYW5kDQogc3R1dHRlcmluZyBwcm9ibGVtcy4gVmlkZW8gcHJvdmlk
ZXJzIGFuZCBhY2Nlc3MgbmV0d29ya3MgYXJlIGludmVzdGluZyBoZWF2aWx5IHRvIGtlZXAgdXAg
d2l0aCBkZW1hbmQuICZuYnNwO1NpZ25pZmljYW50IHdvcmsgaGFzIGJlIGRvbmUgYXQgdGhlIGFw
cGxpY2F0aW9uIGxheWVyIHByb2R1Y2luZyBtb3JlIGVmZmljaWVudCBjb2RlY3MgYW5kIGlubm92
YXRpdmUgYWRhcHRpdmUgYml0cmF0ZSB0cmFuc3BvcnRzIGxpa2UgTVBFRy1EQVNILiAmbmJzcDtU
aGVzZQ0KIGFjY2VzcyBpbnZlc3RtZW50cyBhbmQgYXBwbGljYXRpb24gbGF5ZXIgd29yayBoYXZl
IGhlbHBlZCBidXQgdGhleSBhbG9uZSBoYXZlIG5vdCBiZWVuIGVub3VnaC4gJm5ic3A7PC9kaXY+
DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5BIHRhcmdldCBvZiBhbnkgZXZlbnR1YWwgd29yayBh
bmQgcHJvZHVjdCBpcyB0byBlbmFibGUgdmlkZW8gYW5kIG5ldHdvcmsgcm91dGluZyAvIG1hbmFn
ZW1lbnQgdG8gd29yayBtb3JlIGNvb3BlcmF0aXZlbHkgYW5kIGVmZmljaWVudGx5IHRvIHRyYW5z
cG9ydCB2aWRlby4gJm5ic3A7U3VjY2Vzc2Z1bCBhcHByb2FjaGVzIHdpbGwgbmVlZCB0byBkbyBz
byBpbiBhIGJhY2t3YXJkIGNvbXBhdGlibGUgd2F5cyB0byBwZXJtaXQgZXhpdGluZyBkZXZpY2Vz
DQogYW5kIHBsYXllcnMgdG8gdGFrZSBhZHZhbnRhZ2Ugb2YgdGhlIGltcHJvdmVkIG5ldHdvcmsg
ZWZmaWNpZW5jaWVzLiAmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pk9uZSBw
cm9wb3NlZCBhcHByb2FjaCB0byBkZWFsaW5nIHdpdGggaXNzdWVzIHdhcyBvdXRsaW5lZCBpbiB0
aGUgR2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIEJvRiBwcm9wb3NhbCDigJQgcmVs
YXRlZCBkcmFmdHMgYW5kIG1haWxpbmcgbGlzdCBpbmZvcm1hdGlvbiBpcyBwcm92aWRlZCBiZWxv
dy4gJm5ic3A7QSBkZW1vbnN0cmF0aW9uIG9mIEdHSUUgd2lsbCBiZSBwcm92aWRlZCBkdXJpbmcg
dGhlIEJvRiwgZm9yIGlsbHVzdHJhdGlvbg0KIHB1cnBvc2VzLiAmbmJzcDtEaXNjdXNzaW9uIGlz
IGV4cGVjdGVkIGFuZCBlbmNvdXJhZ2VkIHRvIHJhbmdlIGZ1cnRoZXIgdGhhbiB0aGUgc3BlY2lm
aWMgR0dJRSBwcm9wb3NhbC4gJm5ic3A7ICZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4N
CjxkaXY+VGhpcyB3aWxsIGJlIGFuIGludGVyYWN0aXZlIGRpc2N1c3Npb24gYW5kIHdlIGVuY291
cmFnZSBhbnlvbmUgd2l0aCBhbiBpbnRlcmVzdCBpbiB0aGlzIHRvcGljIHRvIGNvbWUgYW5kIHNo
YXJlIHRoZWlyIGlkZWFzLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9k
aXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDsgQWdlbmRhPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJB
cHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPkludHJvZHVjdGlv
bjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1z
cGFjZTpwcmUiPjwvc3Bhbj5Db250ZXh0IHNldHRpbmcgWzVtaW5dPC9kaXY+DQo8ZGl2Pjxicj4N
CjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1z
cGFjZTpwcmUiPjwvc3Bhbj5Sb3VuZHRhYmxlIGRpc2N1c3Npb24gb2YgdGhlIGlzc3VlKHMpIFsz
MG1pbl08L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10
YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPkRlbW8gb2YgR0dJRSBwcm90
b3R5cGUgWzEwbWluXTwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9
IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+V2hlcmUgZnJv
bSBoZXJlPyBbMTVtaW5dPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIg
c3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPlBvdGVudGlhbCBmb3IgSUVURiB3b3JrIOKA
lCBpcyB0aGVyZSBpbnRlcmVzdCB0byBwdXJzdWU/PC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJB
cHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPldvcmsgZm9yIG90
aGVyIGdyb3Vwcz88c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFj
ZTpwcmUiPjwvc3Bhbj48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PiZuYnNwOzwvZGl2
Pg0KPGRpdj4mbmJzcDsgJm5ic3A7Jm5ic3A7PC9kaXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyBNYWlsaW5nIExpc3Q6IOKAizxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vZ2dpZSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vZ2dpZTwvYT48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8
ZGl2PiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBSZWxldmFudCBkcmFmdHM6PC9kaXY+DQo8
ZGl2PiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGRyYWZ0LWRlZW4t
ZGFpZ2xlLWdnaWUtMDIgOiAmbmJzcDtHbGFzcyB0byBHbGFzcyBJbnRlcm5ldCBFY29zeXN0ZW0g
SW50cm9kdWN0aW9uPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5
bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPiZuYnNwOyAmbmJzcDtkcmFmdC1yb3NlLWRlZW4t
Z2dpZS11c2UtY2FzZXMtMDAgOiBHR0lFIEludGVybmV0IFZpZGVvIFVzZSBDYXNlczxzcGFuIGNs
YXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPjwvZGl2
Pg0KPGRpdj48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpw
cmUiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ZHJhZnQtZGFpZ2xlLWRlZW4tZ2dpZS11cmktc25hcHRy
LTAwIDogJm5ic3A7R2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIFVSSSBhbmQgUy1O
QVBUUiBVc2U8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0i
d2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+Jm5ic3A7ICZuYnNwO2RyYWZ0LWRlZW4tbmFpay1nZ2ll
LW1lbi1tcGVnLWRhc2gtMDAgOiBVc2luZyBNZWRpYSBFbmNvZGluZyBOZXR3b3JrcyB0byBhZGRy
ZXNzIE1QRUctREFTSCB2aWRlbyZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+
DQo8ZGl2PlRpbWU6ICZuYnNwOyAmbmJzcDsgTW9uZGF5IE9jdCAyN3RoICZuYnNwO2F0IDY6MzAt
NzozMHBtIENEVDwvZGl2Pg0KPGRpdj5XaGVyZTogJm5ic3A7Q29sdW1idXMgVGFwIGF0IHRoZSBG
YWlybW9udCAodGhpcyBpcyB0aGUgb3ZlcmZsb3cgaG90ZWwgYW5kIGlzIGNvbm5lY3RlZCB0byB0
aGUgdmVudWUgdmlhIHRoZSB1bmRlcmdyb3VuZCBtYWxsKS48L2Rpdj4NCjwvZGl2Pg0KPGRpdj48
YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvc3Bhbj48L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4N
CjwvaHRtbD4NCg==

--_000_7CF7F94CB496BF4FAB1676F375F9666A37707D6Abgb01xud1012_--


From nobody Sun Mar 26 14:23:05 2017
Return-Path: <bob.hinden@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 18840127871; Sun, 26 Mar 2017 14:23:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJvoAqKwZy7z; Sun, 26 Mar 2017 14:23:00 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60D3E126BF0; Sun, 26 Mar 2017 14:23:00 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id u1so30186156wra.2; Sun, 26 Mar 2017 14:23:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=NLt274xY80wnDd8Lx3qrFJnF65/i8bPr1S8zWExwSVY=; b=Hp61IQgzzkepINfuBAkrwRlOqXMuwkUXyFVc5juv10ABPtoSL+LFKT8tiVMMAptJBC 8GdoFUJmsPfX0+1k+L72aN2t+YpaUsnLh3dT8YppdwsPrqpLObf5ayj/lAqFeJuPpctc MFAjLSMk3vVgohx84Cw2fcFK0hfRQqGVXjNlvfElEOpoPAKoofCdgaaEjwnuU5E+kGGD CL5eN9xnfSVb/7jZ1nlIDzRlGDumw8yIqGPbtC9lTr5JD4SXN0705p26yV+PhfCR4lts HYRNyws2+/kOIVqjN/7rFzwLlkibkijboGLTsDDLpEOfN34dRxZ1B2tUNb2VrhNVTF8S c+Ag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=NLt274xY80wnDd8Lx3qrFJnF65/i8bPr1S8zWExwSVY=; b=cXLdc4yTtxgl8nfh7CHdpArBZp9FMurLS4ExTQgJKP+tYWlaTMe7BAEnqcGJZnSwJ2 pFQE0tioIDLhEoRQ6NlKvUzRtSTLyHb2kNx8Pj4CUGBW6pYCg4G6umUxweuDYSXR3+se NAOIxtWg01T0D83/Sso7TvZ8fZtFMNM8SasXam7De/vccvYnXqy8I9uri1XotlMMS56y wcJ3LSK5h6D77mmcmBEJ/E19nv/MpBiOBskrBZogxoPvypKqlS793DtxU1s8IQTrGF0X 1o1UUo4k8qIXUWWVC/uf/LowSAxGJK1NBgWGtOpDTpfyv2njAYzFWmEIFTo0StUcjADv MRsQ==
X-Gm-Message-State: AFeK/H01xpv6CYhJeDqVEaba9gh0UiON/hiED9MCpBfPGbmo97hRQI0hJ+cULht650CM9Q==
X-Received: by 10.28.11.130 with SMTP id 124mr6916926wml.3.1490563378478; Sun, 26 Mar 2017 14:22:58 -0700 (PDT)
Received: from dhcp-9201.meeting.ietf.org (dhcp-9201.meeting.ietf.org. [31.133.146.1]) by smtp.gmail.com with ESMTPSA id l21sm12180619wrl.59.2017.03.26.14.22.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Mar 2017 14:22:56 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <4BC1763E-9D76-4EAA-B0B4-35620421736B@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BA125144-D743-4BD9-923D-DD79D54571BC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Sun, 26 Mar 2017 16:22:51 -0500
In-Reply-To: <58D518EA.5000508@erg.abdn.ac.uk>
Cc: Bob Hinden <bob.hinden@gmail.com>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
To: gorry@erg.abdn.ac.uk
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <804AA9E4-A643-47A3-9FCC-DA1C450E7FB1@gmail.com> <58D518EA.5000508@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8m4F0eX8qnHKBvMDWotdse6a09Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Mar 2017 21:23:03 -0000

--Apple-Mail=_BA125144-D743-4BD9-923D-DD79D54571BC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Gorry,

> On Mar 24, 2017, at 8:02 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk> =
wrote:
>=20
> On 17/03/2017, 21:56, Bob Hinden wrote:
>> Gorry,
>>=20
>> Thanks for the detailed review.
>>=20
>> Several of the reviews have suggested significant changes to this =
document.  The working group was trying to make a few changes to bring =
it into alignment with some changes to rfc2460bis (based on updating =
documents).  It was not attempting a major rewrite when advancing it to =
Internet Standard.  The alternative that the working group discussed was =
to file errata on RFC1981 and leave it to a future document update.
>>=20
>> I don=E2=80=99t think many of these changes can be done and still =
advance it to Internet Standard. If we can=E2=80=99t advance the current =
document, then the w.g. may want to just do the errata and withdraw the =
advancement request.  Of course, if people want to work on a revision of =
IPv6 Path MTU Discovery, it would be welcomed, but it won=E2=80=99t be =
able to advanced to Internet Standard.
>>=20
>> Comments below.
>>=20
>> Thanks,
>> Bob
> Thanks Bob,
>=20
> I note  the question of status, but in this case, there's a lot =
happened in the Internet since this PS was first published, and much of =
this was in the transport area. Please see replies to comments below. =
I'm happy to discuss or refine text, if this helps.

Comments below.  Let=E2=80=99s get together and go over the document =
while we are in Chicago.  I want to make sure the changes are made =
correctly and in context.

Thanks,
Bob

>=20
> Gorry
>>> On Feb 14, 2017, at 9:23 AM, Gorry Fairhurst<gorry@erg.abdn.ac.uk>  =
wrote:
>>>=20
>>>=20
>>> I have some late transport comments on this ID. The update seems to =
retain a lot of thinking that is really historical and I'd really =
encourage people to look again to making the document uptodate.
>>>=20
>>> Detailed comments follow.
>>>=20
>>> Best wishes,
>>>=20
>>> Gorry
>>>=20
>>> ----
>>> The following text strikes me as a little odd in an update:
>>> " Moreover, TCP implementations that follow the "slow-
>>>   start" congestion-avoidance algorithm [CONG] typically calculate =
and
>>>   cache several other values derived from the PMTU.  It may be =
simpler
>>>   to receive asynchronous notification when the PMTU changes, so =
that
>>>   these variables may be updated.=E2=80=9D
>>> - A modern TCP caches at least some path information in the TCB, why =
start with this clause at all:
>>> "Moreover, TCP implementations that follow the "slow start" =
congestion-avoidance algorithm [CONG] typically calculate and=E2=80=9D
>>> and simply replace this with something like:
>>> "TCP implementations=E2=80=9D?
>>> =E2=80=94=E2=80=94
>> To clarify, you are suggesting to replace it with:
>>=20
>>    TCP implementations typically cache several other values derived
>>    from the PMTU.  It may be simpler to receive asynchronous =
notification when
>>    the PMTU changes, so that these variables may be updated.
>> I think that is editorial, and OK to change.  The paragraph will =
read:
>>=20
>>    The TCP layer must track the PMTU for the path(s) in use by a
>>    connection; it should not send segments that would result in =
packets
>>    larger than the PMTU.  A simple implementation could ask the IP =
layer
>>    for this value each time it created a new segment, but this could =
be
>>    inefficient.  TCP implementation typically cache several other =
values
>>    derived from the PMTU.  It may be simpler to receive asynchronous
>>    notification when the PMTU changes, so that these variables may be
>>    updated.
> Thanks. Seems better, although I would suggest to revise this in this =
way:
>=20
>   A packetization layer layer (e.g., TCP) must track the PMTU
>   for the path(s) in use by a
>   connection; it should not send segments that would result in packets
>   larger than the PMTU, except to probe during PMTU discovery.
>   A simple implementation could ask the IP layer
>   for this value each time it created a new segment, but this could be
>   inefficient.  An implementation typically caches other values
>   derived from the PMTU.  It may be simpler to receive asynchronous
>   notification when the PMTU changes, so that these variables may be
>   also updated.
>=20
> - This would fix typos, and also make the text relevant to transport =
protocols,
> rather than only TCP. Which is I beleive the correct interpretation.

I think that=E2=80=99s good.  I will require some other changes to the =
Section that is titled "TCP layer action=E2=80=9D, let=E2=80=99s discuss =
this later.

>=20
>>> The following text also seems to not reflect a modern TCP stack:
>>> " It is sufficient
>>>   to treat this as any other dropped segment, and wait until the
>>>   retransmission timer expires to cause retransmission of the =
segment.=E2=80=9D
>>> (and following 3 paras).
>>> Could this be replaced by text that does not exclude modern =
retransmission methods:
>>> " It is sufficient
>>>   to treat this in the same way as any other dropped segment, and
>>>   will be recovered by normal retransmission methods.=E2=80=9D
>> Yes, resulting in:
>>=20
>>    When a Packet Too Big message is received, it implies that a =
packet
>>    was dropped by the node that sent the ICMP message.  It is =
sufficient
>>    to treat this in the same way as any other dropped segment, and =
will
>>    be recovered by normal retransmission methods.  If the Path MTU
>>    Discovery process requires several steps to find the PMTU of the =
full
>>    path, this could delay the connection by many round-trip times.
> Good. Seems much better.

Good.

>>=20
>>> =E2=80=94
>>> There is a block of text that describes retransmission triggered by =
ICMPv6.
>>> Has this code been implemented in modern releases of TCP?:
>>> "   Alternatively, the retransmission could be done in immediate =
response
>>>   to a notification that the Path MTU has changed, but only for the
>>>   specific connection specified by the Packet Too Big message.=E2=80=9D=

>>> - It seems to expose a number of attack vectors that really should =
not be exposed!!
>> Are you suggesting remove this text?  Following this text, there are =
two notes.
>>=20
> I'd personally remove this and the notes (you decide) - more because =
it says think that it opens a can of worms about transport details that =
are largely beyond the scope of the document (such as whether to trust =
ICMPv6 as indications of actual loss, and how this interacts with =
re-packaging to a different segment size, congetsuon control, etc).
>=20
> If the WG thinks retaining some text is good, I'd say (as a cautious =
transport person) that we should call out a warning to people doing =
transmissions...
>=20
> OLD:
>     If the new estimated PMTU is
>      still wrong, the process repeats, and there is an exponential
>      growth in the number of superfluous segments sent.
> NEW:
>     If the new estimated PMTU is
>      still wrong, the process repeats, and there is an exponential
>      growth in the number of superfluous segments sent.
>      Retransmissions can increase network load in
>      response to congestion, worsening that congestion.  Any
>      packetization layer that uses retransmission is responsible for
>     congestion control of its retransmissions.
>=20
> If you wish, cite RFC8085 and RFC4821 to let people figure this out? =
(these 2 sentences come directly from RFC8085).

Ok, I think that works.

>>> ---
>>> The discussion of NFS may still be a reasonable historic example, =
but to be current it should really refer also to NFSv4/TCP as utlising =
the MTU discovery provided by TCP, since UDP-based NFS is no longer a =
key application.
>>> =E2=80=94
>> I was planning to update the reference to NFS to RFC7530.   I could =
add text that says something like:
> The protocol changed though - so it's not just a replacement =
reference.
>=20
> I think text should note that RFC7530 says NFS must be able to run =
over a congestion-controlled transport, such as TCP.
>>    It is recommended that NFS running over TCP utilize the MTU =
discovery
>>    provided by TCP.
>>=20
>> Other suggestions?
> Maybe, you could say something like:
> "RFC191 used NFS as an example of a UDP-based application that =
benefits from PMTU discovery. Since then RFC7530, states the supported =
transport layer between NFS
> and IP must be an IETF standardized transport protocol that is =
specified to avoid
> network congestion; such transports include TCP and the Stream Control =
Transmission Protocol (SCTP). In this case, the transport is itself =
responsible for determining and using an effective Path MTU, including =
implementing PMTU discovery when this is needed.=E2=80=9D


>=20
> RFC8085 may well be a good place to point to say what is =
needed/desirable for PMTU for UDP applications, if you wish to say =
something about UDP.

Thanks, I think that works.  Not sure if the other paragraphs on NFS =
should remain.


>>> There is no mention that paths including tunnels can eat ICMPv6 PTB =
messages on the tunnel segment, blackholing them, which prevents =
reaching the destination.
>> As noted above, I think adding discussion about tunnels is out of =
scope of this effort.
> I agree that new mechanisms are out of scope, I was hoping that a =
simple note on tunnels would be in the security considerations.
>=20
> RFC8085 or draft-ietf-intarea-tunnels could be pointed to describe the =
implications of tunnels.
>>> ---
>>> I think the security consideration is naive!
>> Suggestions?
> "   In the first attack, the false message indicates a PMTU much =
smaller
>   than reality.  This should not entirely stop data flow, since the
>   victim node should never set its PMTU estimate below the IPv6 =
minimum
>   link MTU.  It will, however, result in suboptimal performance."
>=20
> So... In the case of the first attack, I still question whether this =
choice of words misrepresents the attack.
> What if, the false message advertises ~1280 bytes, and the path uses a =
tunnel encapsulation transporting IPv6, then the PTB message can be =
basis for a straight DoS attack that does stop data flow?
>=20
> I would recommend revising the security considerations (at least to =
something like):
> "  In the first attack, the false message indicates a PMTU much =
smaller
>   than reality.  In response, the
>   victim node should never set its PMTU estimate below the IPv6 =
minimum
>   link MTU. A sender that falsely reduces to this MTU would observe =
suboptimal performance."
>=20
> - Although this skirts the problem.

OK, I agree this is better.

>>> This statement in particular seems to open DOS vulnerability:
>>> "
>>>  When a node receives a Packet Too Big message, it MUST reduce its
>>>   estimate of the PMTU for the relevant path, based on the value of =
the
>>>   MTU field in the message."
>>> - Introdueces a significant vulnerability.  A rogue PTB message that =
reduces the PMTU to a minimum, can result in a path too small to carry =
an encapsulated packet. (Recently noted by Fernando Gont).
>> Suggestions?
> See below - and above.
>>> Moreover, other layers view ICMP messages with suspicion and have =
long noted the need to check ICMP payload and match only packets that =
relate to actual 5-tuples in use (effectively reducing vulnerability to =
off-path attacks). For example, the Guidelines for UDP, rfc5405bis, =
state:
>>>=20
>>> " Applications SHOULD appropriately validate the payload of ICMP
>>>   messages to ensure these are received in response to transmitted
>>>   traffic (i.e., a reported error condition that corresponds to a =
UDP
>>>   datagram actually sent by the application). =E2=80=A6=E2=80=9C
>>> - clearly handling this in IP-layer tunnels can be troublesome, but =
that's a problem that should be described, not obscured.
>> I could add something like the following as a new second paragraph in =
Section 4 Protocol Requirements:
>>=20
>>   Protocols SHOULD appropriately validate the payload of ICMPv6 PTB
>>   messages to ensure these are received in response to transmitted
>>   traffic (i.e., a reported error condition that corresponds to a UDP
>>   datagram actually sent by the application).
>>=20
>> or similar.
>=20
> That certainly is a nod in what I think is really the correct =
direction.
> Probably /UDP/ should be /IPv6 packet/ given the context of this ID.

Good, I think that makes sense.

>>=20
>>> =E2=80=94=E2=80=94
>>>=20
>>> I=E2=80=99d finally  like to add my concerns about the =
understatement of the value of PLPMTUD, which seems to not reflect the =
recommendations to use this method:
>>> =E2=80=9C  It defines a method for Packetization Layer Path
>>>   MTU Discovery (PLPMTUD) designed for use over paths where delivery =
of
>>>   ICMP messages to a host is not assured.=E2=80=9D
>>> This  seems under-stating the value and recommendations to deploy =
PLMTUD, compared with current transport-area recommendations, for =
instance, the UDP Guidelines provide much more on this important design =
consideration:
>>=20
>> The w.g. spent a lot of time on this paragraph.  The intent was to =
point to it, but not into detail of how it worked, nor make it a new =
requirement.  There was some discussion that adding more detail about =
the relationship between PTMUD and PLPMTUD in the ongoing update to IPv6 =
Node Requirements would be helpful.
>=20
> I appreciate people have spent time trying to get the IPv6 =
specifications progressed to standards status. This is a good effort, =
but I think just adding a nod in the introduction is rather feeble for =
soemthing now recommended. I think at least the security considerations =
should motivate the benefits of this approach (see next).
>>> "   Packetization Layer Path MTU Discovery (PLPMTUD) [RFC4821] does =
not
>>>   rely upon network support for ICMP messages and is therefore
>>>   considered more robust than standard PMTUD.  It is not susceptible =
to
>>>   "black holing" of ICMP message.  To operate, PLPMTUD requires =
changes
>>>   to the way the transport is used, both to transmit probe packets, =
and
>>>   to account for the loss or success of these probes.  This updates =
not
>>>   only the PMTU algorithm, it also impacts loss recovery, congestion
>>>   control, etc.  These updated mechanisms can be implemented within =
a
>>>   connection-oriented transport (e.g., TCP, SCTP, DCCP), but are not =
a
>>>   part of UDP, but this type of feedback is not typically present =
for
>>>   unidirectional applications."
>>>=20
>>> ----
>>>=20
>>> The examples used in the definition of  "upper layer" and "link" =
also makes this document appear as historic, rather than a new RFC!
>> As noted above, I think there would be support for a rewrite if some =
folks wanted to take that on.
> Could the WG consider to also add the first two sentences to the =
security considerations?

Sorry, which two sentences?

>=20
> Gorry
>=20
> P.S. A few more out-dated statements abiut TCP, based on the way =
specific stacks work when the original was written:
>=20
> - The phrase below needs to be removed also, since not all TCP stacks =
behave in this way anymore:
> ", which is always a multiple of the segment size"
>=20
> - There was very specific detailis relating to 4.2BSD TCP =
implementations, which would have been better not being here.
>=20
>=20

OK, I can remove both.





--Apple-Mail=_BA125144-D743-4BD9-923D-DD79D54571BC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJY2DEsAAoJEK7rdBF357uokT0H/2VCVMjQgoGMDl42peaiitp6
ZcL7MwA59BVUaHTv/fwR7FdHgSKZ5JwyQI/j2/fbriJSwxjb+FnPQO8194kkSSd4
mnrIpQnTxHfOczDRTwVuT1YLD5hNWj4R3sm8Ot+6qr7qm05DjjY4D32sj5LOq0eo
QRfwAW1N6kZZEEwCrDtQe4fClj5V7287V7o6GnMvSKLM6XoKS6l+BRwxUmX7v6fk
VFKpC7bqt1n4deud+dJKBuwP5lCBK3Ymij+tgn0NUh7kHD7c0uMBLsTngW9QsaFQ
uLshSCMuj5jkS8ebdbJxtj5+xqEXQ/1wNwkjGrJPIr0/cYCEOJj+ioXXbucgkqU=
=/Knx
-----END PGP SIGNATURE-----

--Apple-Mail=_BA125144-D743-4BD9-923D-DD79D54571BC--


From nobody Sun Mar 26 17:54:41 2017
Return-Path: <gorry@erg.abdn.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 27D8C129441; Sun, 26 Mar 2017 17:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZNXDcE2cMEL; Sun, 26 Mar 2017 17:54:35 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 2BBF3128E19; Sun, 26 Mar 2017 17:54:35 -0700 (PDT)
Received: from Gs-MacBook-Pro.local (unknown [216.80.70.251]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 980F01B0173B; Mon, 27 Mar 2017 03:51:48 +0100 (BST)
Message-ID: <58D862B2.5050607@erg.abdn.ac.uk>
Date: Sun, 26 Mar 2017 19:54:10 -0500
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
CC: "tsv-area@ietf.org" <tsv-area@ietf.org>,  "6man-chairs@ietf.org" <6man-chairs@ietf.org>, IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>,  "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <804AA9E4-A643-47A3-9FCC-DA1C450E7FB1@gmail.com> <58D518EA.5000508@erg.abdn.ac.uk> <4BC1763E-9D76-4EAA-B0B4-35620421736B@gmail.com>
In-Reply-To: <4BC1763E-9D76-4EAA-B0B4-35620421736B@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8eyvba8zQKCQiXeJesJBgB6pE5U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 00:54:38 -0000

Thanks for those coments, which I cut, because I think they can now be turned to text. You asked a question about one comment, see below:

GF:
Could the WG consider to also add the first two sentences to the security considerations?
Bob:
Sorry, which two sentences?

These were the two sentences, the rest of the para explained what PMTUD was, and probably could be left to the reader:

   "Packetization Layer Path MTU Discovery (PLPMTUD) [RFC4821] does not
   rely upon network support for ICMP messages and is therefore
   considered more robust than standard PMTUD.  It is not susceptible to
   "black holing" of ICMP message."

Gorry


From nobody Sun Mar 26 19:35:25 2017
Return-Path: <bob.hinden@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 4450E127735; Sun, 26 Mar 2017 19:35:17 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iOTXrPFYo7U3; Sun, 26 Mar 2017 19:35:15 -0700 (PDT)
Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DA331200A0; Sun, 26 Mar 2017 19:35:15 -0700 (PDT)
Received: by mail-wr0-x22e.google.com with SMTP id w11so23492324wrc.3; Sun, 26 Mar 2017 19:35:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Y14bXAoeZfUpvBy1Oe5b9AIwA4Yncv4zGU5sf9A9PfE=; b=XP4L7+9sC7lFhY/HDpg9PaPp1ujQMlt9veSfSxjzTMAeKc/OeIFtQkuj9laEAGers6 27rbwe+qpLtr4/5F0EMwPpmEAiuBUnPnwNjgjvrM5T+Sit46l/iAOuhmGS2Vz2uUFnTE gNEONUEyYzbbY7Ln+C1QskB9eQ3BGDpLSsnIzPJ+idFRBx3U9sECY4fprGsD9JTisTJk pyZGPRqP05pF8r4iOyKAONdcDbMQ1R3hAmYyIByT0vb5JHjmkenEXEnp6IRee5QmT9np Ll2CXzRKqvKRlkm+OVAx7W9lx2LCyz82OKEhGAl/uYWtUHo3WiBxn8JfaIscf+pVXKeK ltVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Y14bXAoeZfUpvBy1Oe5b9AIwA4Yncv4zGU5sf9A9PfE=; b=A9BoI5lD+uHVyq3D0+5427zGd3gpIl4zSHGvcCrSxy36xPDYXPKoNhdb6SGHEAW+df ELZ9ZfhLOa3FApxQMDi/RLnWBJeuCMfOv8KwnWyuDIgRO9TcU12QV02JoHDKos5tR8CX wIjUFrMWZbv7fNtuumc3GO4ReDJiixk+rdYdel6LDLuRONKCNwhuUsYTZQQRrBokHNBM no3NFe2KvtPWjsVb3+jSTWQURv4YVooOk0SBixG9YlZdYCcVUC0LovYfamKD3DEQfoqT 61SN3HEoblu+kl/gwOZTAGrhB0HNnej5YEJ6hSgRU0MngLeFk9Vb/UiI1IfSSRTDHZOY t/hg==
X-Gm-Message-State: AFeK/H1FaWewkcSpWla76f8/6+oGyuoeQm2xSxpxPgGqF8NMmqPQNolcUUcsb6ttj1ytNg==
X-Received: by 10.223.162.130 with SMTP id s2mr19298484wra.149.1490582113932;  Sun, 26 Mar 2017 19:35:13 -0700 (PDT)
Received: from dhcp-9201.meeting.ietf.org (dhcp-9201.meeting.ietf.org. [31.133.146.1]) by smtp.gmail.com with ESMTPSA id u145sm12442868wmu.1.2017.03.26.19.35.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Mar 2017 19:35:12 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <18CAF7CE-FDC1-46AD-9857-D4475564F4FA@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4C8AF37D-719F-4B29-B836-FC94BA0F810E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Sun, 26 Mar 2017 21:35:08 -0500
In-Reply-To: <58D862B2.5050607@erg.abdn.ac.uk>
Cc: Bob Hinden <bob.hinden@gmail.com>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
To: gorry@erg.abdn.ac.uk
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <804AA9E4-A643-47A3-9FCC-DA1C450E7FB1@gmail.com> <58D518EA.5000508@erg.abdn.ac.uk> <4BC1763E-9D76-4EAA-B0B4-35620421736B@gmail.com> <58D862B2.5050607@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gibhGwvLxLB3ed9IeBb9IjIcRRY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 02:35:17 -0000

--Apple-Mail=_4C8AF37D-719F-4B29-B836-FC94BA0F810E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Gorry,

> On Mar 26, 2017, at 7:54 PM, Gorry Fairhurst <gorry@erg.abdn.ac.uk> =
wrote:
>=20
> Thanks for those coments, which I cut, because I think they can now be =
turned to text. You asked a question about one comment, see below:
>=20
> GF:
> Could the WG consider to also add the first two sentences to the =
security considerations?
> Bob:
> Sorry, which two sentences?
>=20
> These were the two sentences, the rest of the para explained what =
PMTUD was, and probably could be left to the reader:
>=20
>  "Packetization Layer Path MTU Discovery (PLPMTUD) [RFC4821] does not
>  rely upon network support for ICMP messages and is therefore
>  considered more robust than standard PMTUD.  It is not susceptible to
>  "black holing" of ICMP message.=E2=80=9D

OK, I can add that.

Thanks,
Bob

>=20
> Gorry
>=20


--Apple-Mail=_4C8AF37D-719F-4B29-B836-FC94BA0F810E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJY2HpcAAoJEK7rdBF357uoSVoH/iVdpGHz8JGR3UhiN/C3zWJK
lulo/fQRKO3ITqwFnXa4zGNQbmkkNoVLaZ2M9nKHkqrpspoWwwMAGPvgTOKZt4sM
1WnUQadwbNW6Kyhr1YzxNXdQ/Ih5ifB81oagqLDNpbMK6mlPMq3GFcfCClr+Jofi
YF4pUhPifVB58EufDHqdKMHtjVSqorAZCl9ePBcFyv4X37eyUrwTylPcH5qmVz3U
aSeA8s96c8RVc6ZmgiyphGpsw3W6X93BIYwASUpH6uvzqk5cHSPIYw/9281KvCA1
3UrsE873C+qFJjmuMsnvl6sSb0DO7B2LNWR44XwtF6eoTf+Ocp8NFgaZ7H7v5D0=
=G4Fz
-----END PGP SIGNATURE-----

--Apple-Mail=_4C8AF37D-719F-4B29-B836-FC94BA0F810E--


From nobody Mon Mar 27 08:17:45 2017
Return-Path: <iesg@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B0398129784; Mon, 27 Mar 2017 08:17:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IESG <iesg@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org,housley@vigilsec.com
Subject: www.ietf.org revamp project update
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org,chair@ietf.org,housley@vigilsec.com
Message-ID: <149062785971.30517.4261336260907603476.idtracker@ietfa.amsl.com>
Date: Mon, 27 Mar 2017 08:17:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RDBSyO79U28qSNb8ejXfH82X1Lc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 15:17:43 -0000

I wanted to provide a brief update on the www.ietf.org website revamp
project.

The project has moved forward. We're not quite done yet, and know
things that we still need to work on. But, we have started to collect 
more feedback on the designs. A preview will be available at IETF 98.

Also, Russ Housley recently took over from Joe Hildebrand as the 
project manager. Thank you! I also want to thank Joe for the work
he did to get the project to this point. 

Our current website has had a number of issues. For instance, every
time I write a blog article, several people complain that they can't read
it well on their mobile devices. The project will fix this, but also try to
otherwise improve the experience and usefulness of the website for both
participants and those who otherwise seek information about the IETF.
The website also needs to act as the ‘front door’ to the IETF, make it
easy to get involved, and help everyone understand what the IETF does.
The complete scope of the work is available at [1].

As part of the project, a Community Review Committee was established
to provide ongoing guidance. A preview was shown around IETF 93,
and an update last summer [2]. Since then, the revamped design has
been implemented on a development server provided by the selected
vendor (Torchbox, https://www.torchbox.com) using an open source
content management system (Wagtail, https://www.wagtail.io).

At IETF 98, we will be demonstrating the new web site at a table near IETF
meeting registration. Hours will be posted on a sign by the table. If you 
are here, we hope you will stop by to take a look and talk to us to help us
understand what would make the revamped site better for your work. The
critical aspect of the design is that your typical uses of the website are 
easily accessible, and we've found that the design team alone doesn't 
always know how you use the website. So feedback is appreciated, and 
will be acted upon. We've already gotten clear feedback from IESG 
members, and will be making modifications based on that.

For those not attending IETF 98, we’ll be arranging other opportunities,
including online, to review and provide feedback shortly after the
meeting.

Jari Arkko, IETF Chair

[1] https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf
[2] https://www.ietf.org/blog/2016/06/www-ietf-org-revamp-update/


From nobody Mon Mar 27 09:34:47 2017
Return-Path: <Glenn.Deen@nbcuni.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30600127B57; Mon, 27 Mar 2017 09:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nXeo_9hmSvSz; Mon, 27 Mar 2017 09:34:40 -0700 (PDT)
Received: from mx0a-00176a04.pphosted.com (mx0a-00176a04.pphosted.com [67.231.149.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 800DE128C81; Mon, 27 Mar 2017 09:34:38 -0700 (PDT)
Received: from pps.filterd (m0048276.ppops.net [127.0.0.1]) by m0048276.ppops.net-00176a04. (8.16.0.20/8.16.0.20) with SMTP id v2RGS18N032264; Mon, 27 Mar 2017 12:34:36 -0400
Received: from usushmgip002.mail.tfayd.com ([216.178.109.236]) by m0048276.ppops.net-00176a04. with ESMTP id 29dhfqwfc1-1 (version=TLSv1.2 cipher=RC4-SHA bits=128 verify=NOT); Mon, 27 Mar 2017 12:34:36 -0400
Received: from unknown (HELO USUSHECWP008.mail.tfayd.com) ([10.40.33.204]) by usushmgip002.mail.tfayd.com with ESMTP; 27 Mar 2017 09:34:35 -0700
Received: from USUSHEMWP012.mail.tfayd.com ([169.254.4.151]) by USUSHECWP008.mail.tfayd.com ([3.156.41.62]) with mapi id 14.03.0266.001; Mon, 27 Mar 2017 09:34:35 -0700
From: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
To: "ietf@ietf.org" <ietf@ietf.org>, "ggie@ietf.org" <ggie@ietf.org>, "98attendees@ietf.org" <98attendees@ietf.org>
Subject: New Room: Video Streaming Bar BoF
Thread-Topic: New Room: Video Streaming Bar BoF
Thread-Index: AQHSpxgEE1B5mX6gNU6RkMi6lqTn3g==
Date: Mon, 27 Mar 2017 16:34:34 +0000
Message-ID: <D4FE8D2B.D1AD9%glenn.deen@nbcuni.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.3.150624
x-originating-ip: [10.53.64.210]
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
Content-Type: multipart/alternative; boundary="_000_D4FE8D2BD1AD9glenndeennbcunicom_"
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-27_15:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703270138
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JL4XFlW5jCaBjoGWRWCJFUd2zhk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 16:34:42 -0000

--_000_D4FE8D2BD1AD9glenndeennbcunicom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgQWxsLA0KDQpUaGUgVmlkZW8gU3RyZWFtaW5nIEJhciBCb0YgaGFzIGJlZW4gbW92ZWQgdG8g
dGhlIFN0LiBHYWxsZW4gcm9vbSBhdCB0aGUgU3dpc3NvdGVsDQoNCk5ldyBMb2NhdGlvbjogIFN0
LiBHYWxsZW4gMS8y4oCTIHRoaXMgaXMgb24gdGhlIDJuZCBmbG9vciBvZiB0aGUgU3dpc3NvdGVs
Lg0KVGltZTogICAgIE1vbmRheSBPY3QgMjd0aCAgYXQgNjozMC03OjMwcG0gQ0RUDQoNCi1nbGVu
biBkZWVuDQogICAgICAgICAgICAgLS0tLS0tLS0tDQpUb3BpYzogVmlkZW8gU3RyZWFtaW5nIGVY
dGVuc2lvbnMgKFYtU1gpDQoNCkRlc2NyaXB0aW9uOg0KDQpEdWUgdG8gaXRzIHNpemUgYW5kIHNl
bnNpdGl2aXR5IHRvIG5ldHdvcmsgY29uZGl0aW9ucywgdGhlIHRyYW5zcG9ydCBvZiB2aWRlbyBv
dmVyIHRoZSBJbnRlcm5ldCBoYXMgaGlnaGxpZ2h0ZWQgYSBzaWduaWZpY2FudCBzY2FsYWJpbGl0
eSBwcm9ibGVtIGZvciB0aGUgSW50ZXJuZXQuICBPbiB0aGUgYmVsaWVmIHRoYXQgYWRkcmVzc2lu
ZyB0aGlzIHNjYWxhYmlsaXR5IHByb2JsZW0gcmVxdWlyZXMgYmV0dGVyIGludGVncmF0aW9uIGJl
dHdlZW4gYXBwbGljYXRpb24gdHJhbnNwb3J0IGFuZCBuZXR3b3JraW5nIHRlY2hub2xvZ2llcyBh
bmQgbGV2ZXJhZ2luZyBJUHY2LCB0aGlzIEJhciBCT0Ygd2lsbCBzb2xpY2l0IGV4cGVyaWVuY2Vz
IG9mIHRoZSBzY2FsaW5nIHByb2JsZW0gYXMgcGVyY2VpdmVkIGZyb20gZGlmZmVyZW50IHBhcnRz
IG9mIHRoZSBpbmR1c3RyeSAobmV0d29yaywgcHJvZHVjZXIsIHZlbmRvcnMpLg0KDQpWaWRlbyBp
cyB3aXRob3V0IHJpdmFsIHRoZSB0b3AgdXNlIG9mIEludGVybmV0IGJhbmR3aWR0aCwgYW5kIGl0
cyBldmVyIGdyb3dpbmcgZGVtYW5kIGZvciBtb3JlIGJhbmR3aWR0aCBlYXNpbHkgb3V0IHBhY2Vz
IHRoZSBuZXcgY2FwYWNpdHkgYmVpbmcgYWRkZWQgYm90aCBnbG9iYWxseSBhbmQgcmVnaW9uYWxs
eSB3aXRoIG5vIGxldCB1cCBpbiBzaWdodC4gICBVc2VycyBhcmUgZnJ1c3RyYXRlZCBieSBxdWFs
aXR5LCBidWZmZXJpbmcsIGFuZCBzdHV0dGVyaW5nIHByb2JsZW1zLiBWaWRlbyBwcm92aWRlcnMg
YW5kIGFjY2VzcyBuZXR3b3JrcyBhcmUgaW52ZXN0aW5nIGhlYXZpbHkgdG8ga2VlcCB1cCB3aXRo
IGRlbWFuZC4gIFNpZ25pZmljYW50IHdvcmsgaGFzIGJlIGRvbmUgYXQgdGhlIGFwcGxpY2F0aW9u
IGxheWVyIHByb2R1Y2luZyBtb3JlIGVmZmljaWVudCBjb2RlY3MgYW5kIGlubm92YXRpdmUgYWRh
cHRpdmUgYml0cmF0ZSB0cmFuc3BvcnRzIGxpa2UgTVBFRy1EQVNILiAgVGhlc2UgYWNjZXNzIGlu
dmVzdG1lbnRzIGFuZCBhcHBsaWNhdGlvbiBsYXllciB3b3JrIGhhdmUgaGVscGVkIGJ1dCB0aGV5
IGFsb25lIGhhdmUgbm90IGJlZW4gZW5vdWdoLg0KDQpBIHRhcmdldCBvZiBhbnkgZXZlbnR1YWwg
d29yayBhbmQgcHJvZHVjdCBpcyB0byBlbmFibGUgdmlkZW8gYW5kIG5ldHdvcmsgcm91dGluZyAv
IG1hbmFnZW1lbnQgdG8gd29yayBtb3JlIGNvb3BlcmF0aXZlbHkgYW5kIGVmZmljaWVudGx5IHRv
IHRyYW5zcG9ydCB2aWRlby4gIFN1Y2Nlc3NmdWwgYXBwcm9hY2hlcyB3aWxsIG5lZWQgdG8gZG8g
c28gaW4gYSBiYWNrd2FyZCBjb21wYXRpYmxlIHdheXMgdG8gcGVybWl0IGV4aXRpbmcgZGV2aWNl
cyBhbmQgcGxheWVycyB0byB0YWtlIGFkdmFudGFnZSBvZiB0aGUgaW1wcm92ZWQgbmV0d29yayBl
ZmZpY2llbmNpZXMuDQoNCk9uZSBwcm9wb3NlZCBhcHByb2FjaCB0byBkZWFsaW5nIHdpdGggaXNz
dWVzIHdhcyBvdXRsaW5lZCBpbiB0aGUgR2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVt
IEJvRiBwcm9wb3NhbCDigJQgcmVsYXRlZCBkcmFmdHMgYW5kIG1haWxpbmcgbGlzdCBpbmZvcm1h
dGlvbiBpcyBwcm92aWRlZCBiZWxvdy4gIEEgZGVtb25zdHJhdGlvbiBvZiBHR0lFIHdpbGwgYmUg
cHJvdmlkZWQgZHVyaW5nIHRoZSBCb0YsIGZvciBpbGx1c3RyYXRpb24gcHVycG9zZXMuICBEaXNj
dXNzaW9uIGlzIGV4cGVjdGVkIGFuZCBlbmNvdXJhZ2VkIHRvIHJhbmdlIGZ1cnRoZXIgdGhhbiB0
aGUgc3BlY2lmaWMgR0dJRSBwcm9wb3NhbC4NCg0KVGhpcyB3aWxsIGJlIGFuIGludGVyYWN0aXZl
IGRpc2N1c3Npb24gYW5kIHdlIGVuY291cmFnZSBhbnlvbmUgd2l0aCBhbiBpbnRlcmVzdCBpbiB0
aGlzIHRvcGljIHRvIGNvbWUgYW5kIHNoYXJlIHRoZWlyIGlkZWFzLg0KDQoNCiAgICBBZ2VuZGEN
CkludHJvZHVjdGlvbg0KQ29udGV4dCBzZXR0aW5nIFs1bWluXQ0KDQpSb3VuZHRhYmxlIGRpc2N1
c3Npb24gb2YgdGhlIGlzc3VlKHMpIFszMG1pbl0NCg0KRGVtbyBvZiBHR0lFIHByb3RvdHlwZSBb
MTBtaW5dDQoNCldoZXJlIGZyb20gaGVyZT8gWzE1bWluXQ0KUG90ZW50aWFsIGZvciBJRVRGIHdv
cmsg4oCUIGlzIHRoZXJlIGludGVyZXN0IHRvIHB1cnN1ZT8NCldvcmsgZm9yIG90aGVyIGdyb3Vw
cz8NCg0KDQoNCiAgICAgICAgTWFpbGluZyBMaXN0OiDigItodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2dnaWUNCg0KICAgICAgICBSZWxldmFudCBkcmFmdHM6DQogICAgICAg
ICAgICBkcmFmdC1kZWVuLWRhaWdsZS1nZ2llLTAyIDogIEdsYXNzIHRvIEdsYXNzIEludGVybmV0
IEVjb3N5c3RlbSBJbnRyb2R1Y3Rpb24NCiAgIGRyYWZ0LXJvc2UtZGVlbi1nZ2llLXVzZS1jYXNl
cy0wMCA6IEdHSUUgSW50ZXJuZXQgVmlkZW8gVXNlIENhc2VzDQogICBkcmFmdC1kYWlnbGUtZGVl
bi1nZ2llLXVyaS1zbmFwdHItMDAgOiAgR2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVt
IFVSSSBhbmQgUy1OQVBUUiBVc2UNCiAgIGRyYWZ0LWRlZW4tbmFpay1nZ2llLW1lbi1tcGVnLWRh
c2gtMDAgOiBVc2luZyBNZWRpYSBFbmNvZGluZyBOZXR3b3JrcyB0byBhZGRyZXNzIE1QRUctREFT
SCB2aWRlbw0KDQpUaW1lOiAgICAgTW9uZGF5IE9jdCAyN3RoICBhdCA2OjMwLTc6MzBwbSBDRFQN
Cg==

--_000_D4FE8D2BD1AD9glenndeennbcunicom_
Content-Type: text/html; charset="utf-8"
Content-ID: <FD573BDA1EBA074FB7BB9AE31A556BD3@NBCUNI.COM>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGJsb2NrcXVvdGUgdHlw
ZT0iY2l0ZSI+DQo8ZGl2PkhpIEFsbCw8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PlRo
ZSBWaWRlbyBTdHJlYW1pbmcgQmFyIEJvRiBoYXMgYmVlbiBtb3ZlZCB0byB0aGUgU3QuIEdhbGxl
biByb29tIGF0IHRoZSBTd2lzc290ZWw8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pk5l
dyBMb2NhdGlvbjogJm5ic3A7PHNwYW4gc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQt
ZmFtaWx5OiBDb25zb2xhczsgZm9udC1zaXplOiAxNHB4OyI+U3QuIEdhbGxlbiAxLzI8L3NwYW4+
PGZvbnQgZmFjZT0iQ29uc29sYXMiPuKAkzwvZm9udD48c3BhbiBzdHlsZT0iY29sb3I6IHJnYigw
LCAwLCAwKTsgZm9udC1mYW1pbHk6IENvbnNvbGFzOyBmb250LXNpemU6IDE0cHg7Ij4mbmJzcDt0
aGlzIGlzIG9uIHRoZSAybmQgZmxvb3Igb2YgdGhlIFN3aXNzb3RlbC48L3NwYW4+PC9kaXY+DQo8
L2Jsb2NrcXVvdGU+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBzdHlsZT0iY29sb3I6IHJnYigw
LCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmk7IGZvbnQtc2l6ZTogMTRweDsiPg0KPHNwYW4g
aWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXYgc3R5bGU9IndvcmQtd3JhcDogYnJlYWst
d29yZDsgLXdlYmtpdC1uYnNwLW1vZGU6IHNwYWNlOyAtd2Via2l0LWxpbmUtYnJlYWs6IGFmdGVy
LXdoaXRlLXNwYWNlOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KVGltZTog
Jm5ic3A7ICZuYnNwOyBNb25kYXkgT2N0IDI3dGggJm5ic3A7YXQgNjozMC03OjMwcG0gQ0RUPC9k
aXY+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4tZ2xlbm4gZGVlbjwvZGl2Pg0K
PC9ibG9ja3F1b3RlPg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1p
bHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7LS0tLS0tLS0tPC9kaXY+DQo8Ymxv
Y2txdW90ZSB0eXBlPSJjaXRlIiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1p
bHk6IENhbGlicmk7IGZvbnQtc2l6ZTogMTRweDsiPg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9T
RUNUSU9OIj4NCjxkaXYgc3R5bGU9IndvcmQtd3JhcDogYnJlYWstd29yZDsgLXdlYmtpdC1uYnNw
LW1vZGU6IHNwYWNlOyAtd2Via2l0LWxpbmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNlOyBmb250
LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5Ub3BpYzogVmlkZW8gU3RyZWFt
aW5nIGVYdGVuc2lvbnMgKFYtU1gpPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5EZXNj
cmlwdGlvbjogJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5EdWUgdG8gaXRz
IHNpemUgYW5kIHNlbnNpdGl2aXR5IHRvIG5ldHdvcmsgY29uZGl0aW9ucywgdGhlIHRyYW5zcG9y
dCBvZiB2aWRlbyBvdmVyIHRoZSBJbnRlcm5ldCBoYXMgaGlnaGxpZ2h0ZWQgYSBzaWduaWZpY2Fu
dCBzY2FsYWJpbGl0eSBwcm9ibGVtIGZvciB0aGUgSW50ZXJuZXQuICZuYnNwO09uIHRoZSBiZWxp
ZWYgdGhhdCBhZGRyZXNzaW5nIHRoaXMgc2NhbGFiaWxpdHkgcHJvYmxlbSByZXF1aXJlcyBiZXR0
ZXIgaW50ZWdyYXRpb24gYmV0d2Vlbg0KIGFwcGxpY2F0aW9uIHRyYW5zcG9ydCBhbmQgbmV0d29y
a2luZyB0ZWNobm9sb2dpZXMgYW5kIGxldmVyYWdpbmcgSVB2NiwgdGhpcyBCYXIgQk9GIHdpbGwg
c29saWNpdCBleHBlcmllbmNlcyBvZiB0aGUgc2NhbGluZyBwcm9ibGVtIGFzIHBlcmNlaXZlZCBm
cm9tIGRpZmZlcmVudCBwYXJ0cyBvZiB0aGUgaW5kdXN0cnkgKG5ldHdvcmssIHByb2R1Y2VyLCB2
ZW5kb3JzKS4gJm5ic3A7Jm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5WaWRl
byBpcyB3aXRob3V0IHJpdmFsIHRoZSB0b3AgdXNlIG9mIEludGVybmV0IGJhbmR3aWR0aCwgYW5k
IGl0cyBldmVyIGdyb3dpbmcgZGVtYW5kIGZvciBtb3JlIGJhbmR3aWR0aCBlYXNpbHkgb3V0IHBh
Y2VzIHRoZSBuZXcgY2FwYWNpdHkgYmVpbmcgYWRkZWQgYm90aCBnbG9iYWxseSBhbmQgcmVnaW9u
YWxseSB3aXRoIG5vIGxldCB1cCBpbiBzaWdodC4gJm5ic3A7IFVzZXJzIGFyZSBmcnVzdHJhdGVk
IGJ5IHF1YWxpdHksIGJ1ZmZlcmluZywgYW5kDQogc3R1dHRlcmluZyBwcm9ibGVtcy4gVmlkZW8g
cHJvdmlkZXJzIGFuZCBhY2Nlc3MgbmV0d29ya3MgYXJlIGludmVzdGluZyBoZWF2aWx5IHRvIGtl
ZXAgdXAgd2l0aCBkZW1hbmQuICZuYnNwO1NpZ25pZmljYW50IHdvcmsgaGFzIGJlIGRvbmUgYXQg
dGhlIGFwcGxpY2F0aW9uIGxheWVyIHByb2R1Y2luZyBtb3JlIGVmZmljaWVudCBjb2RlY3MgYW5k
IGlubm92YXRpdmUgYWRhcHRpdmUgYml0cmF0ZSB0cmFuc3BvcnRzIGxpa2UgTVBFRy1EQVNILiAm
bmJzcDtUaGVzZQ0KIGFjY2VzcyBpbnZlc3RtZW50cyBhbmQgYXBwbGljYXRpb24gbGF5ZXIgd29y
ayBoYXZlIGhlbHBlZCBidXQgdGhleSBhbG9uZSBoYXZlIG5vdCBiZWVuIGVub3VnaC4gJm5ic3A7
PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5BIHRhcmdldCBvZiBhbnkgZXZlbnR1YWwg
d29yayBhbmQgcHJvZHVjdCBpcyB0byBlbmFibGUgdmlkZW8gYW5kIG5ldHdvcmsgcm91dGluZyAv
IG1hbmFnZW1lbnQgdG8gd29yayBtb3JlIGNvb3BlcmF0aXZlbHkgYW5kIGVmZmljaWVudGx5IHRv
IHRyYW5zcG9ydCB2aWRlby4gJm5ic3A7U3VjY2Vzc2Z1bCBhcHByb2FjaGVzIHdpbGwgbmVlZCB0
byBkbyBzbyBpbiBhIGJhY2t3YXJkIGNvbXBhdGlibGUgd2F5cyB0byBwZXJtaXQgZXhpdGluZyBk
ZXZpY2VzDQogYW5kIHBsYXllcnMgdG8gdGFrZSBhZHZhbnRhZ2Ugb2YgdGhlIGltcHJvdmVkIG5l
dHdvcmsgZWZmaWNpZW5jaWVzLiAmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2
Pk9uZSBwcm9wb3NlZCBhcHByb2FjaCB0byBkZWFsaW5nIHdpdGggaXNzdWVzIHdhcyBvdXRsaW5l
ZCBpbiB0aGUgR2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIEJvRiBwcm9wb3NhbCDi
gJQgcmVsYXRlZCBkcmFmdHMgYW5kIG1haWxpbmcgbGlzdCBpbmZvcm1hdGlvbiBpcyBwcm92aWRl
ZCBiZWxvdy4gJm5ic3A7QSBkZW1vbnN0cmF0aW9uIG9mIEdHSUUgd2lsbCBiZSBwcm92aWRlZCBk
dXJpbmcgdGhlIEJvRiwgZm9yIGlsbHVzdHJhdGlvbg0KIHB1cnBvc2VzLiAmbmJzcDtEaXNjdXNz
aW9uIGlzIGV4cGVjdGVkIGFuZCBlbmNvdXJhZ2VkIHRvIHJhbmdlIGZ1cnRoZXIgdGhhbiB0aGUg
c3BlY2lmaWMgR0dJRSBwcm9wb3NhbC4gJm5ic3A7ICZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8
L2Rpdj4NCjxkaXY+VGhpcyB3aWxsIGJlIGFuIGludGVyYWN0aXZlIGRpc2N1c3Npb24gYW5kIHdl
IGVuY291cmFnZSBhbnlvbmUgd2l0aCBhbiBpbnRlcmVzdCBpbiB0aGlzIHRvcGljIHRvIGNvbWUg
YW5kIHNoYXJlIHRoZWlyIGlkZWFzLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJy
Pg0KPC9kaXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDsgQWdlbmRhPC9kaXY+DQo8ZGl2PjxzcGFuIGNs
YXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOiBwcmU7Ij48L3NwYW4+SW50
cm9kdWN0aW9uPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9
IndoaXRlLXNwYWNlOiBwcmU7Ij48L3NwYW4+Q29udGV4dCBzZXR0aW5nIFs1bWluXTwvZGl2Pg0K
PGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHls
ZT0id2hpdGUtc3BhY2U6IHByZTsiPjwvc3Bhbj5Sb3VuZHRhYmxlIGRpc2N1c3Npb24gb2YgdGhl
IGlzc3VlKHMpIFszMG1pbl08L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNs
YXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOiBwcmU7Ij48L3NwYW4+RGVt
byBvZiBHR0lFIHByb3RvdHlwZSBbMTBtaW5dPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRp
dj48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTogcHJlOyI+
PC9zcGFuPldoZXJlIGZyb20gaGVyZT8gWzE1bWluXTwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0i
QXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTogcHJlOyI+PC9zcGFuPlBvdGVudGlh
bCBmb3IgSUVURiB3b3JrIOKAlCBpcyB0aGVyZSBpbnRlcmVzdCB0byBwdXJzdWU/PC9kaXY+DQo8
ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOiBwcmU7
Ij48L3NwYW4+V29yayBmb3Igb3RoZXIgZ3JvdXBzPzxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3Bh
biIgc3R5bGU9IndoaXRlLXNwYWNlOiBwcmU7Ij48L3NwYW4+PC9kaXY+DQo8ZGl2Pjxicj4NCjwv
ZGl2Pg0KPGRpdj4mbmJzcDs8L2Rpdj4NCjxkaXY+Jm5ic3A7ICZuYnNwOyZuYnNwOzwvZGl2Pg0K
PGRpdj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgTWFpbGluZyBMaXN0OiDigIs8YSBocmVm
PSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dnaWUiPmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZ2dpZTwvYT48L2Rpdj4NCjxkaXY+PGJyPg0KPC9k
aXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBSZWxldmFudCBkcmFmdHM6PC9k
aXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGRyYWZ0
LWRlZW4tZGFpZ2xlLWdnaWUtMDIgOiAmbmJzcDtHbGFzcyB0byBHbGFzcyBJbnRlcm5ldCBFY29z
eXN0ZW0gSW50cm9kdWN0aW9uPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3Bh
biIgc3R5bGU9IndoaXRlLXNwYWNlOiBwcmU7Ij48L3NwYW4+Jm5ic3A7ICZuYnNwO2RyYWZ0LXJv
c2UtZGVlbi1nZ2llLXVzZS1jYXNlcy0wMCA6IEdHSUUgSW50ZXJuZXQgVmlkZW8gVXNlIENhc2Vz
PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6IHByZTsiPjwv
c3Bhbj48L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hp
dGUtc3BhY2U6IHByZTsiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ZHJhZnQtZGFpZ2xlLWRlZW4tZ2dp
ZS11cmktc25hcHRyLTAwIDogJm5ic3A7R2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVt
IFVSSSBhbmQgUy1OQVBUUiBVc2U8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1z
cGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6IHByZTsiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ZHJhZnQt
ZGVlbi1uYWlrLWdnaWUtbWVuLW1wZWctZGFzaC0wMCA6IFVzaW5nIE1lZGlhIEVuY29kaW5nIE5l
dHdvcmtzIHRvIGFkZHJlc3MgTVBFRy1EQVNIIHZpZGVvJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4N
CjwvZGl2Pg0KPGRpdj5UaW1lOiAmbmJzcDsgJm5ic3A7IE1vbmRheSBPY3QgMjd0aCAmbmJzcDth
dCA2OjMwLTc6MzBwbSBDRFQ8L2Rpdj4NCjwvZGl2Pg0KPC9zcGFuPjwvYmxvY2txdW90ZT4NCjwv
Ym9keT4NCjwvaHRtbD4NCg==

--_000_D4FE8D2BD1AD9glenndeennbcunicom_--


From nobody Mon Mar 27 10:49:53 2017
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1FF129544; Mon, 27 Mar 2017 10:49:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jouni.nospam@gmail.com>
To: <ops-dir@ietf.org>
Cc: dnsop@ietf.org, ietf@ietf.org, draft-ietf-dnsop-nsec-aggressiveuse.all@ietf.org
Subject: Review of draft-ietf-dnsop-nsec-aggressiveuse-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149063698126.30570.4959246116267967756@ietfa.amsl.com>
Date: Mon, 27 Mar 2017 10:49:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YeZW1S-psDfiK4E0QPRRa0yeomU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 17:49:41 -0000

Reviewer: Jouni Korhonen
Review result: Has Nits

I think would be ready if it passed IDnits. I found the document good
read and found no sinkholes in it. Pointing up two implementations was
also great.

The Proto Write-up seems not be up to date with what IDnits says e.g.,
when it comes to downrefs, which is what the IDnits complain about.

A couple of editorials:

Lines 118-119 says: "This takes this.." I would reword to something
like:
   "This document takes using NXDOMAIN information for more effective
caching further."

Lines 396 and 397 uses "is NOT" and "IS making". I would use lower
case here. No reason to use capitalized and still non-RFC2119
language.

Line 407 is would be great to indicate since which version of Unbound
support has been in place.


From nobody Mon Mar 27 11:12:07 2017
Return-Path: <Glenn.Deen@nbcuni.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F0DB129490; Mon, 27 Mar 2017 11:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FEE3lStlbvhj; Mon, 27 Mar 2017 11:11:53 -0700 (PDT)
Received: from mx0a-00176a04.pphosted.com (mx0a-00176a04.pphosted.com [67.231.149.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB4C612943C; Mon, 27 Mar 2017 11:11:53 -0700 (PDT)
Received: from pps.filterd (m0047965.ppops.net [127.0.0.1]) by m0047965.ppops.net-00176a04. (8.16.0.20/8.16.0.20) with SMTP id v2RI8Bqf042459; Mon, 27 Mar 2017 14:11:51 -0400
Received: from usaoamgip001.mail.tfayd.com ([173.213.212.135]) by m0047965.ppops.net-00176a04. with ESMTP id 29dn6swn4h-1 (version=TLSv1.2 cipher=RC4-SHA bits=128 verify=NOT); Mon, 27 Mar 2017 14:11:50 -0400
Received: from unknown (HELO USUSHECWP006.mail.tfayd.com) ([10.40.78.204]) by usaoamgip001.mail.tfayd.com with ESMTP; 27 Mar 2017 14:11:48 -0400
Received: from USUSHEMWP012.mail.tfayd.com ([169.254.4.151]) by usushecwp006.mail.tfayd.com ([3.156.41.24]) with mapi id 14.03.0266.001; Mon, 27 Mar 2017 11:10:55 -0700
From: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
To: "ietf@ietf.org" <ietf@ietf.org>, "ggie@ietf.org" <ggie@ietf.org>, "98attendees@ietf.org" <98attendees@ietf.org>
Subject: New Room: Video Streaming Bar BoF (now in March)
Thread-Topic: New Room: Video Streaming Bar BoF (now in March)
Thread-Index: AQHSpyV5WgoT2w7GGEaiOfZiF7ZsZw==
Date: Mon, 27 Mar 2017 18:10:54 +0000
Message-ID: <D4FEA341.D1AE2%glenn.deen@nbcuni.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.3.150624
x-originating-ip: [10.53.64.210]
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
Content-Type: multipart/alternative; boundary="_000_D4FEA341D1AE2glenndeennbcunicom_"
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-27_16:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703270152
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Jhxwz1DjrKgIOp05EZYcTz7xgGc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 18:11:56 -0000

--_000_D4FEA341D1AE2glenndeennbcunicom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhlIFZpZGVvIFN0cmVhbWluZyBCYXIgQm9GIGhhcyBiZWVuIG1vdmVkIHRvIHRoZSBTdC4gR2Fs
bGVuIHJvb20gYXQgdGhlIFN3aXNzb3RlbA0KDQpOZXcgTG9jYXRpb246ICBTdC4gR2FsbGVuIDEv
MuKAkyB0aGlzIGlzIG9uIHRoZSAybmQgZmxvb3Igb2YgdGhlIFN3aXNzb3RlbC4NClRpbWU6ICAg
ICBNb25kYXkgTUFSQ0ggMjd0aCAgYXQgNjozMC03OjMwcG0gQ0RUDQoNCi1nbGVubiBkZWVuDQoN
CkZyb206IEdHSUUgPGdnaWUtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86Z2dpZS1ib3VuY2VzQGll
dGYub3JnPj4gb24gYmVoYWxmIG9mIEdsZW5uIERlZW4gPGdsZW5uLmRlZW5AbmJjdW5pLmNvbTxt
YWlsdG86Z2xlbm4uZGVlbkBuYmN1bmkuY29tPj4NCkRhdGU6IE1vbmRheSwgTWFyY2ggMjcsIDIw
MTcgYXQgOTozNCBBTQ0KVG86ICJpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPiIg
PGlldGZAaWV0Zi5vcmc8bWFpbHRvOmlldGZAaWV0Zi5vcmc+PiwgImdnaWVAaWV0Zi5vcmc8bWFp
bHRvOmdnaWVAaWV0Zi5vcmc+IiA8Z2dpZUBpZXRmLm9yZzxtYWlsdG86Z2dpZUBpZXRmLm9yZz4+
LCAiOThhdHRlbmRlZXNAaWV0Zi5vcmc8bWFpbHRvOjk4YXR0ZW5kZWVzQGlldGYub3JnPiIgPDk4
YXR0ZW5kZWVzQGlldGYub3JnPG1haWx0bzo5OGF0dGVuZGVlc0BpZXRmLm9yZz4+DQpTdWJqZWN0
OiBbR0dJRV0gTmV3IFJvb206IFZpZGVvIFN0cmVhbWluZyBCYXIgQm9GDQoNCkhpIEFsbCwNCg0K
VGhlIFZpZGVvIFN0cmVhbWluZyBCYXIgQm9GIGhhcyBiZWVuIG1vdmVkIHRvIHRoZSBTdC4gR2Fs
bGVuIHJvb20gYXQgdGhlIFN3aXNzb3RlbA0KDQpOZXcgTG9jYXRpb246ICBTdC4gR2FsbGVuIDEv
MuKAkyB0aGlzIGlzIG9uIHRoZSAybmQgZmxvb3Igb2YgdGhlIFN3aXNzb3RlbC4NClRpbWU6ICAg
ICBNb25kYXkgTWFyY2ggMjd0aCAgYXQgNjozMC03OjMwcG0gQ0RUDQoNCi1nbGVubiBkZWVuDQog
ICAgICAgICAgICAgLS0tLS0tLS0tDQpUb3BpYzogVmlkZW8gU3RyZWFtaW5nIGVYdGVuc2lvbnMg
KFYtU1gpDQoNCkRlc2NyaXB0aW9uOg0KDQpEdWUgdG8gaXRzIHNpemUgYW5kIHNlbnNpdGl2aXR5
IHRvIG5ldHdvcmsgY29uZGl0aW9ucywgdGhlIHRyYW5zcG9ydCBvZiB2aWRlbyBvdmVyIHRoZSBJ
bnRlcm5ldCBoYXMgaGlnaGxpZ2h0ZWQgYSBzaWduaWZpY2FudCBzY2FsYWJpbGl0eSBwcm9ibGVt
IGZvciB0aGUgSW50ZXJuZXQuICBPbiB0aGUgYmVsaWVmIHRoYXQgYWRkcmVzc2luZyB0aGlzIHNj
YWxhYmlsaXR5IHByb2JsZW0gcmVxdWlyZXMgYmV0dGVyIGludGVncmF0aW9uIGJldHdlZW4gYXBw
bGljYXRpb24gdHJhbnNwb3J0IGFuZCBuZXR3b3JraW5nIHRlY2hub2xvZ2llcyBhbmQgbGV2ZXJh
Z2luZyBJUHY2LCB0aGlzIEJhciBCT0Ygd2lsbCBzb2xpY2l0IGV4cGVyaWVuY2VzIG9mIHRoZSBz
Y2FsaW5nIHByb2JsZW0gYXMgcGVyY2VpdmVkIGZyb20gZGlmZmVyZW50IHBhcnRzIG9mIHRoZSBp
bmR1c3RyeSAobmV0d29yaywgcHJvZHVjZXIsIHZlbmRvcnMpLg0KDQpWaWRlbyBpcyB3aXRob3V0
IHJpdmFsIHRoZSB0b3AgdXNlIG9mIEludGVybmV0IGJhbmR3aWR0aCwgYW5kIGl0cyBldmVyIGdy
b3dpbmcgZGVtYW5kIGZvciBtb3JlIGJhbmR3aWR0aCBlYXNpbHkgb3V0IHBhY2VzIHRoZSBuZXcg
Y2FwYWNpdHkgYmVpbmcgYWRkZWQgYm90aCBnbG9iYWxseSBhbmQgcmVnaW9uYWxseSB3aXRoIG5v
IGxldCB1cCBpbiBzaWdodC4gICBVc2VycyBhcmUgZnJ1c3RyYXRlZCBieSBxdWFsaXR5LCBidWZm
ZXJpbmcsIGFuZCBzdHV0dGVyaW5nIHByb2JsZW1zLiBWaWRlbyBwcm92aWRlcnMgYW5kIGFjY2Vz
cyBuZXR3b3JrcyBhcmUgaW52ZXN0aW5nIGhlYXZpbHkgdG8ga2VlcCB1cCB3aXRoIGRlbWFuZC4g
IFNpZ25pZmljYW50IHdvcmsgaGFzIGJlIGRvbmUgYXQgdGhlIGFwcGxpY2F0aW9uIGxheWVyIHBy
b2R1Y2luZyBtb3JlIGVmZmljaWVudCBjb2RlY3MgYW5kIGlubm92YXRpdmUgYWRhcHRpdmUgYml0
cmF0ZSB0cmFuc3BvcnRzIGxpa2UgTVBFRy1EQVNILiAgVGhlc2UgYWNjZXNzIGludmVzdG1lbnRz
IGFuZCBhcHBsaWNhdGlvbiBsYXllciB3b3JrIGhhdmUgaGVscGVkIGJ1dCB0aGV5IGFsb25lIGhh
dmUgbm90IGJlZW4gZW5vdWdoLg0KDQpBIHRhcmdldCBvZiBhbnkgZXZlbnR1YWwgd29yayBhbmQg
cHJvZHVjdCBpcyB0byBlbmFibGUgdmlkZW8gYW5kIG5ldHdvcmsgcm91dGluZyAvIG1hbmFnZW1l
bnQgdG8gd29yayBtb3JlIGNvb3BlcmF0aXZlbHkgYW5kIGVmZmljaWVudGx5IHRvIHRyYW5zcG9y
dCB2aWRlby4gIFN1Y2Nlc3NmdWwgYXBwcm9hY2hlcyB3aWxsIG5lZWQgdG8gZG8gc28gaW4gYSBi
YWNrd2FyZCBjb21wYXRpYmxlIHdheXMgdG8gcGVybWl0IGV4aXRpbmcgZGV2aWNlcyBhbmQgcGxh
eWVycyB0byB0YWtlIGFkdmFudGFnZSBvZiB0aGUgaW1wcm92ZWQgbmV0d29yayBlZmZpY2llbmNp
ZXMuDQoNCk9uZSBwcm9wb3NlZCBhcHByb2FjaCB0byBkZWFsaW5nIHdpdGggaXNzdWVzIHdhcyBv
dXRsaW5lZCBpbiB0aGUgR2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIEJvRiBwcm9w
b3NhbCDigJQgcmVsYXRlZCBkcmFmdHMgYW5kIG1haWxpbmcgbGlzdCBpbmZvcm1hdGlvbiBpcyBw
cm92aWRlZCBiZWxvdy4gIEEgZGVtb25zdHJhdGlvbiBvZiBHR0lFIHdpbGwgYmUgcHJvdmlkZWQg
ZHVyaW5nIHRoZSBCb0YsIGZvciBpbGx1c3RyYXRpb24gcHVycG9zZXMuICBEaXNjdXNzaW9uIGlz
IGV4cGVjdGVkIGFuZCBlbmNvdXJhZ2VkIHRvIHJhbmdlIGZ1cnRoZXIgdGhhbiB0aGUgc3BlY2lm
aWMgR0dJRSBwcm9wb3NhbC4NCg0KVGhpcyB3aWxsIGJlIGFuIGludGVyYWN0aXZlIGRpc2N1c3Np
b24gYW5kIHdlIGVuY291cmFnZSBhbnlvbmUgd2l0aCBhbiBpbnRlcmVzdCBpbiB0aGlzIHRvcGlj
IHRvIGNvbWUgYW5kIHNoYXJlIHRoZWlyIGlkZWFzLg0KDQoNCiAgICBBZ2VuZGENCkludHJvZHVj
dGlvbg0KQ29udGV4dCBzZXR0aW5nIFs1bWluXQ0KDQpSb3VuZHRhYmxlIGRpc2N1c3Npb24gb2Yg
dGhlIGlzc3VlKHMpIFszMG1pbl0NCg0KRGVtbyBvZiBHR0lFIHByb3RvdHlwZSBbMTBtaW5dDQoN
CldoZXJlIGZyb20gaGVyZT8gWzE1bWluXQ0KUG90ZW50aWFsIGZvciBJRVRGIHdvcmsg4oCUIGlz
IHRoZXJlIGludGVyZXN0IHRvIHB1cnN1ZT8NCldvcmsgZm9yIG90aGVyIGdyb3Vwcz8NCg0KDQoN
CiAgICAgICAgTWFpbGluZyBMaXN0OiDigItodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2dnaWUNCg0KICAgICAgICBSZWxldmFudCBkcmFmdHM6DQogICAgICAgICAgICBkcmFm
dC1kZWVuLWRhaWdsZS1nZ2llLTAyIDogIEdsYXNzIHRvIEdsYXNzIEludGVybmV0IEVjb3N5c3Rl
bSBJbnRyb2R1Y3Rpb24NCiAgIGRyYWZ0LXJvc2UtZGVlbi1nZ2llLXVzZS1jYXNlcy0wMCA6IEdH
SUUgSW50ZXJuZXQgVmlkZW8gVXNlIENhc2VzDQogICBkcmFmdC1kYWlnbGUtZGVlbi1nZ2llLXVy
aS1zbmFwdHItMDAgOiAgR2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIFVSSSBhbmQg
Uy1OQVBUUiBVc2UNCiAgIGRyYWZ0LWRlZW4tbmFpay1nZ2llLW1lbi1tcGVnLWRhc2gtMDAgOiBV
c2luZyBNZWRpYSBFbmNvZGluZyBOZXR3b3JrcyB0byBhZGRyZXNzIE1QRUctREFTSCB2aWRlbw0K
DQpUaW1lOiAgICAgTW9uZGF5IE9jdCAyN3RoICBhdCA2OjMwLTc6MzBwbSBDRFQNCg==

--_000_D4FEA341D1AE2glenndeennbcunicom_
Content-Type: text/html; charset="utf-8"
Content-ID: <10686EF3E4773D41B987F5BF134533C5@NBCUNI.COM>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj48c3BhbiBpZD0i
T0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRpdiBzdHlsZT0id29yZC13cmFwOiBicmVhay13b3Jk
OyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0ZXItd2hp
dGUtc3BhY2U7Ij4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPg0KPGRpdj5UaGUgVmlkZW8gU3Ry
ZWFtaW5nIEJhciBCb0YgaGFzIGJlZW4gbW92ZWQgdG8gdGhlIFN0LiBHYWxsZW4gcm9vbSBhdCB0
aGUgU3dpc3NvdGVsPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5OZXcgTG9jYXRpb246
ICZuYnNwOzxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogQ29uc29sYXM7Ij5TdC4gR2FsbGVuIDEv
Mjwvc3Bhbj48Zm9udCBmYWNlPSJDb25zb2xhcyI+4oCTPC9mb250PjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTogQ29uc29sYXM7Ij4mbmJzcDt0aGlzIGlzIG9uIHRoZSAybmQgZmxvb3Igb2YgdGhl
IFN3aXNzb3RlbC48L3NwYW4+PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8YmxvY2txdW90ZSB0eXBl
PSJjaXRlIiBzdHlsZT0iZm9udC1mYW1pbHk6IENhbGlicmk7Ij48c3BhbiBpZD0iT0xLX1NSQ19C
T0RZX1NFQ1RJT04iPg0KPGRpdiBzdHlsZT0id29yZC13cmFwOiBicmVhay13b3JkOyAtd2Via2l0
LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7
IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyI+DQpUaW1lOiAmbmJzcDsgJm5ic3A7
IE1vbmRheSBNQVJDSCAyN3RoICZuYnNwO2F0IDY6MzAtNzozMHBtIENEVDwvZGl2Pg0KPC9zcGFu
Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+LWdsZW5uIGRlZW48L2Rpdj4NCjwvYmxvY2txdW90
ZT4NCjwvZGl2Pg0KPC9zcGFuPjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJP
TEtfU1JDX0JPRFlfU0VDVElPTiI+DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpOyBm
b250LXNpemU6MTFwdDsgdGV4dC1hbGlnbjpsZWZ0OyBjb2xvcjpibGFjazsgQk9SREVSLUJPVFRP
TTogbWVkaXVtIG5vbmU7IEJPUkRFUi1MRUZUOiBtZWRpdW0gbm9uZTsgUEFERElORy1CT1RUT006
IDBpbjsgUEFERElORy1MRUZUOiAwaW47IFBBRERJTkctUklHSFQ6IDBpbjsgQk9SREVSLVRPUDog
I2I1YzRkZiAxcHQgc29saWQ7IEJPUkRFUi1SSUdIVDogbWVkaXVtIG5vbmU7IFBBRERJTkctVE9Q
OiAzcHQiPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkZyb206IDwvc3Bhbj5HR0lF
ICZsdDs8YSBocmVmPSJtYWlsdG86Z2dpZS1ib3VuY2VzQGlldGYub3JnIj5nZ2llLWJvdW5jZXNA
aWV0Zi5vcmc8L2E+Jmd0OyBvbiBiZWhhbGYgb2YgR2xlbm4gRGVlbiAmbHQ7PGEgaHJlZj0ibWFp
bHRvOmdsZW5uLmRlZW5AbmJjdW5pLmNvbSI+Z2xlbm4uZGVlbkBuYmN1bmkuY29tPC9hPiZndDs8
YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+RGF0ZTogPC9zcGFuPk1vbmRheSwg
TWFyY2ggMjcsIDIwMTcgYXQgOTozNCBBTTxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpi
b2xkIj5UbzogPC9zcGFuPiZxdW90OzxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIj5pZXRm
QGlldGYub3JnPC9hPiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciPmll
dGZAaWV0Zi5vcmc8L2E+Jmd0OywgJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOmdnaWVAaWV0Zi5vcmci
PmdnaWVAaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86Z2dpZUBpZXRmLm9y
ZyI+Z2dpZUBpZXRmLm9yZzwvYT4mZ3Q7LCAmcXVvdDs8YSBocmVmPSJtYWlsdG86OThhdHRlbmRl
ZXNAaWV0Zi5vcmciPjk4YXR0ZW5kZWVzQGlldGYub3JnPC9hPiZxdW90Ow0KICZsdDs8YSBocmVm
PSJtYWlsdG86OThhdHRlbmRlZXNAaWV0Zi5vcmciPjk4YXR0ZW5kZWVzQGlldGYub3JnPC9hPiZn
dDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDogPC9zcGFuPltH
R0lFXSBOZXcgUm9vbTogVmlkZW8gU3RyZWFtaW5nIEJhciBCb0Y8YnI+DQo8L2Rpdj4NCjxkaXY+
PGJyPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0id29yZC13cmFwOiBicmVhay13b3JkOyAt
d2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0ZXItd2hpdGUt
c3BhY2U7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtc2l6ZTogMTRweDsgZm9udC1mYW1pbHk6
IENhbGlicmksIHNhbnMtc2VyaWY7Ij4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPg0KPGRpdj5I
aSBBbGwsPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGUgVmlkZW8gU3RyZWFtaW5n
IEJhciBCb0YgaGFzIGJlZW4gbW92ZWQgdG8gdGhlIFN0LiBHYWxsZW4gcm9vbSBhdCB0aGUgU3dp
c3NvdGVsPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5OZXcgTG9jYXRpb246ICZuYnNw
OzxzcGFuIHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ29uc29sYXM7
IGZvbnQtc2l6ZTogMTRweDsiPlN0LiBHYWxsZW4gMS8yPC9zcGFuPjxmb250IGZhY2U9IkNvbnNv
bGFzIj7igJM8L2ZvbnQ+PHNwYW4gc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFt
aWx5OiBDb25zb2xhczsgZm9udC1zaXplOiAxNHB4OyI+Jm5ic3A7dGhpcyBpcyBvbiB0aGUgMm5k
IGZsb29yIG9mIHRoZSBTd2lzc290ZWwuPC9zcGFuPjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGJs
b2NrcXVvdGUgdHlwZT0iY2l0ZSIgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFt
aWx5OiBDYWxpYnJpOyBmb250LXNpemU6IDE0cHg7Ij4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlf
U0VDVElPTiI+DQo8ZGl2IHN0eWxlPSJ3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJz
cC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJyZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgZm9u
dC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7Ij4NClRpbWU6ICZuYnNwOyAmbmJzcDsgTW9u
ZGF5IE1hcmNoIDI3dGggJm5ic3A7YXQgNjozMC03OjMwcG0gQ0RUPC9kaXY+DQo8L3NwYW4+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4tZ2xlbm4gZGVlbjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0K
PGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNh
bnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7LS0tLS0tLS0tPC9kaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJj
aXRlIiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmk7IGZv
bnQtc2l6ZTogMTRweDsiPg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXYg
c3R5bGU9IndvcmQtd3JhcDogYnJlYWstd29yZDsgLXdlYmtpdC1uYnNwLW1vZGU6IHNwYWNlOyAt
d2Via2l0LWxpbmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNlOyBmb250LWZhbWlseTogQ2FsaWJy
aSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5Ub3BpYzogVmlkZW8gU3RyZWFtaW5nIGVYdGVuc2lvbnMg
KFYtU1gpPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5EZXNjcmlwdGlvbjogJm5ic3A7
PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5EdWUgdG8gaXRzIHNpemUgYW5kIHNlbnNp
dGl2aXR5IHRvIG5ldHdvcmsgY29uZGl0aW9ucywgdGhlIHRyYW5zcG9ydCBvZiB2aWRlbyBvdmVy
IHRoZSBJbnRlcm5ldCBoYXMgaGlnaGxpZ2h0ZWQgYSBzaWduaWZpY2FudCBzY2FsYWJpbGl0eSBw
cm9ibGVtIGZvciB0aGUgSW50ZXJuZXQuICZuYnNwO09uIHRoZSBiZWxpZWYgdGhhdCBhZGRyZXNz
aW5nIHRoaXMgc2NhbGFiaWxpdHkgcHJvYmxlbSByZXF1aXJlcyBiZXR0ZXIgaW50ZWdyYXRpb24g
YmV0d2Vlbg0KIGFwcGxpY2F0aW9uIHRyYW5zcG9ydCBhbmQgbmV0d29ya2luZyB0ZWNobm9sb2dp
ZXMgYW5kIGxldmVyYWdpbmcgSVB2NiwgdGhpcyBCYXIgQk9GIHdpbGwgc29saWNpdCBleHBlcmll
bmNlcyBvZiB0aGUgc2NhbGluZyBwcm9ibGVtIGFzIHBlcmNlaXZlZCBmcm9tIGRpZmZlcmVudCBw
YXJ0cyBvZiB0aGUgaW5kdXN0cnkgKG5ldHdvcmssIHByb2R1Y2VyLCB2ZW5kb3JzKS4gJm5ic3A7
Jm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5WaWRlbyBpcyB3aXRob3V0IHJp
dmFsIHRoZSB0b3AgdXNlIG9mIEludGVybmV0IGJhbmR3aWR0aCwgYW5kIGl0cyBldmVyIGdyb3dp
bmcgZGVtYW5kIGZvciBtb3JlIGJhbmR3aWR0aCBlYXNpbHkgb3V0IHBhY2VzIHRoZSBuZXcgY2Fw
YWNpdHkgYmVpbmcgYWRkZWQgYm90aCBnbG9iYWxseSBhbmQgcmVnaW9uYWxseSB3aXRoIG5vIGxl
dCB1cCBpbiBzaWdodC4gJm5ic3A7IFVzZXJzIGFyZSBmcnVzdHJhdGVkIGJ5IHF1YWxpdHksIGJ1
ZmZlcmluZywgYW5kDQogc3R1dHRlcmluZyBwcm9ibGVtcy4gVmlkZW8gcHJvdmlkZXJzIGFuZCBh
Y2Nlc3MgbmV0d29ya3MgYXJlIGludmVzdGluZyBoZWF2aWx5IHRvIGtlZXAgdXAgd2l0aCBkZW1h
bmQuICZuYnNwO1NpZ25pZmljYW50IHdvcmsgaGFzIGJlIGRvbmUgYXQgdGhlIGFwcGxpY2F0aW9u
IGxheWVyIHByb2R1Y2luZyBtb3JlIGVmZmljaWVudCBjb2RlY3MgYW5kIGlubm92YXRpdmUgYWRh
cHRpdmUgYml0cmF0ZSB0cmFuc3BvcnRzIGxpa2UgTVBFRy1EQVNILiAmbmJzcDtUaGVzZQ0KIGFj
Y2VzcyBpbnZlc3RtZW50cyBhbmQgYXBwbGljYXRpb24gbGF5ZXIgd29yayBoYXZlIGhlbHBlZCBi
dXQgdGhleSBhbG9uZSBoYXZlIG5vdCBiZWVuIGVub3VnaC4gJm5ic3A7PC9kaXY+DQo8ZGl2Pjxi
cj4NCjwvZGl2Pg0KPGRpdj5BIHRhcmdldCBvZiBhbnkgZXZlbnR1YWwgd29yayBhbmQgcHJvZHVj
dCBpcyB0byBlbmFibGUgdmlkZW8gYW5kIG5ldHdvcmsgcm91dGluZyAvIG1hbmFnZW1lbnQgdG8g
d29yayBtb3JlIGNvb3BlcmF0aXZlbHkgYW5kIGVmZmljaWVudGx5IHRvIHRyYW5zcG9ydCB2aWRl
by4gJm5ic3A7U3VjY2Vzc2Z1bCBhcHByb2FjaGVzIHdpbGwgbmVlZCB0byBkbyBzbyBpbiBhIGJh
Y2t3YXJkIGNvbXBhdGlibGUgd2F5cyB0byBwZXJtaXQgZXhpdGluZyBkZXZpY2VzDQogYW5kIHBs
YXllcnMgdG8gdGFrZSBhZHZhbnRhZ2Ugb2YgdGhlIGltcHJvdmVkIG5ldHdvcmsgZWZmaWNpZW5j
aWVzLiAmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pk9uZSBwcm9wb3NlZCBh
cHByb2FjaCB0byBkZWFsaW5nIHdpdGggaXNzdWVzIHdhcyBvdXRsaW5lZCBpbiB0aGUgR2xhc3Mg
dG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIEJvRiBwcm9wb3NhbCDigJQgcmVsYXRlZCBkcmFm
dHMgYW5kIG1haWxpbmcgbGlzdCBpbmZvcm1hdGlvbiBpcyBwcm92aWRlZCBiZWxvdy4gJm5ic3A7
QSBkZW1vbnN0cmF0aW9uIG9mIEdHSUUgd2lsbCBiZSBwcm92aWRlZCBkdXJpbmcgdGhlIEJvRiwg
Zm9yIGlsbHVzdHJhdGlvbg0KIHB1cnBvc2VzLiAmbmJzcDtEaXNjdXNzaW9uIGlzIGV4cGVjdGVk
IGFuZCBlbmNvdXJhZ2VkIHRvIHJhbmdlIGZ1cnRoZXIgdGhhbiB0aGUgc3BlY2lmaWMgR0dJRSBw
cm9wb3NhbC4gJm5ic3A7ICZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VGhp
cyB3aWxsIGJlIGFuIGludGVyYWN0aXZlIGRpc2N1c3Npb24gYW5kIHdlIGVuY291cmFnZSBhbnlv
bmUgd2l0aCBhbiBpbnRlcmVzdCBpbiB0aGlzIHRvcGljIHRvIGNvbWUgYW5kIHNoYXJlIHRoZWly
IGlkZWFzLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2
PiZuYnNwOyAmbmJzcDsgQWdlbmRhPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWIt
c3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOiBwcmU7Ij48L3NwYW4+SW50cm9kdWN0aW9uPC9kaXY+
DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOiBw
cmU7Ij48L3NwYW4+Q29udGV4dCBzZXR0aW5nIFs1bWluXTwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6
IHByZTsiPjwvc3Bhbj5Sb3VuZHRhYmxlIGRpc2N1c3Npb24gb2YgdGhlIGlzc3VlKHMpIFszMG1p
bl08L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWIt
c3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOiBwcmU7Ij48L3NwYW4+RGVtbyBvZiBHR0lFIHByb3Rv
dHlwZSBbMTBtaW5dPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0i
QXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTogcHJlOyI+PC9zcGFuPldoZXJlIGZy
b20gaGVyZT8gWzE1bWluXTwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4i
IHN0eWxlPSJ3aGl0ZS1zcGFjZTogcHJlOyI+PC9zcGFuPlBvdGVudGlhbCBmb3IgSUVURiB3b3Jr
IOKAlCBpcyB0aGVyZSBpbnRlcmVzdCB0byBwdXJzdWU/PC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNz
PSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOiBwcmU7Ij48L3NwYW4+V29yayBm
b3Igb3RoZXIgZ3JvdXBzPzxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRl
LXNwYWNlOiBwcmU7Ij48L3NwYW4+PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4mbmJz
cDs8L2Rpdj4NCjxkaXY+Jm5ic3A7ICZuYnNwOyZuYnNwOzwvZGl2Pg0KPGRpdj4mbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgTWFpbGluZyBMaXN0OiDigIs8YSBocmVmPSJodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dnaWUiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vZ2dpZTwvYT48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBSZWxldmFudCBkcmFmdHM6PC9kaXY+DQo8ZGl2PiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGRyYWZ0LWRlZW4tZGFpZ2xlLWdn
aWUtMDIgOiAmbmJzcDtHbGFzcyB0byBHbGFzcyBJbnRlcm5ldCBFY29zeXN0ZW0gSW50cm9kdWN0
aW9uPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRl
LXNwYWNlOiBwcmU7Ij48L3NwYW4+Jm5ic3A7ICZuYnNwO2RyYWZ0LXJvc2UtZGVlbi1nZ2llLXVz
ZS1jYXNlcy0wMCA6IEdHSUUgSW50ZXJuZXQgVmlkZW8gVXNlIENhc2VzPHNwYW4gY2xhc3M9IkFw
cGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6IHByZTsiPjwvc3Bhbj48L2Rpdj4NCjxk
aXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6IHByZTsi
Pjwvc3Bhbj4mbmJzcDsgJm5ic3A7ZHJhZnQtZGFpZ2xlLWRlZW4tZ2dpZS11cmktc25hcHRyLTAw
IDogJm5ic3A7R2xhc3MgdG8gR2xhc3MgSW50ZXJuZXQgRWNvc3lzdGVtIFVSSSBhbmQgUy1OQVBU
UiBVc2U8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hp
dGUtc3BhY2U6IHByZTsiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ZHJhZnQtZGVlbi1uYWlrLWdnaWUt
bWVuLW1wZWctZGFzaC0wMCA6IFVzaW5nIE1lZGlhIEVuY29kaW5nIE5ldHdvcmtzIHRvIGFkZHJl
c3MgTVBFRy1EQVNIIHZpZGVvJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5U
aW1lOiAmbmJzcDsgJm5ic3A7IE1vbmRheSBPY3QgMjd0aCAmbmJzcDthdCA2OjMwLTc6MzBwbSBD
RFQ8L2Rpdj4NCjwvZGl2Pg0KPC9zcGFuPjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8
L3NwYW4+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_D4FEA341D1AE2glenndeennbcunicom_--


From nobody Mon Mar 27 12:34:59 2017
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 E546E12958B for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 12:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0T9pwUfyUkUD for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 12:34:50 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1EFB128CB9 for <ietf@ietf.org>; Mon, 27 Mar 2017 12:34:50 -0700 (PDT)
Received: from [128.9.184.151] ([128.9.184.151]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2RJY9wa001776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 27 Mar 2017 12:34:10 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: Phillip Hallam-Baker <phill@hallambaker.com>, Tony Finch <dot@dotat.at>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <9F0F8841-BC1D-4C27-83EF-8F93F33FB021@puck.nether.net> <CAMm+Lwh5JMn+JxPB3Q3RKpeibckVSB2Fqm_RajcnU28OAx=jOw@mail.gmail.com> <1483474918.1346083.836313393.2699EBD5@webmail.messagingengine.com> <CAMm+LwjJDyCv2mBG8ob-njDj-4m5tr7jP6XAiEn1ME5NCYcpiQ@mail.gmail.com> <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu>
Date: Mon, 27 Mar 2017 12:34:10 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zELnSdBnaubzJIexLAOD5RBOo10>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 19:34:58 -0000

Hi, all,

I've submitted the time frame discussion intended to resolve this issue,
which also recently arouse on another mailing list. Further discussion
on this draft will occur on the ART mailing list (art@ietf.org).

Joe

-----------

A new version of I-D, draft-touch-time-01.txt
has been successfully submitted by Joe Touch and posted to the
IETF repository.

Name:		draft-touch-time
Revision:	01
Title:		Resolving Multiple Time Scales in the Internet
Document date:	2017-03-27
Group:		Individual Submission
Pages:		17
URL:            https://www.ietf.org/internet-drafts/draft-touch-time-01.txt
Status:         https://datatracker.ietf.org/doc/draft-touch-time/
Htmlized:       https://tools.ietf.org/html/draft-touch-time-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-touch-time-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-touch-time-01

Abstract:
   Internet systems use a variety of time scales, which can complicate
   time comparisons and calculations. This document explains these
   various ways of indicating time and explains how they can be used
   together safely. This document is intended as a companion to
   Internet time as discussed in RFC 3339.


From nobody Mon Mar 27 13:24:19 2017
Return-Path: <nomcom-chair-2016@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ECA56129626; Mon, 27 Mar 2017 13:24:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2016 <nomcom-chair-2016@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: Report out from the NomCom 2016-2017
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
Date: Mon, 27 Mar 2017 13:24:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vy_Ec2L2Hte29VhTxyeah-tkGrc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 20:24:18 -0000

All -

Please find below some high level outcomes and observations from this years 
NomCom. Issues of particular interest to the community include both the
issues related to recruiting and supporting nominees and the corner cases we 
encountered that which may require updates to our current guiding documents. 
The list closes with a few action steps that everyone can take to help improve 
next years process.

We will be happy to take questions and community feedback either in Plenary
or via email: nomcom-2016@ietf.org

Details on this years membership and the outcomes of our selection processes
can be found here: https://datatracker.ietf.org/nomcom/2016/

I want to thank everyone who participated this cycle. The inputs, the
willingness to serve, and the willingness to support nominee participation all
contributed to our results. Special thanks to Peter Yee for stepping up as
the in-coming NomCom Chair.

Lucy Lynch
NomCom Chair 2016-2017

NomCom 2016-2017

The Three Stages of the NomCom Process

- Recruit and Select NomCom Members  (March -> July)
  -- Calls for Volunteers
  -- Direct email/Registration tick box volunteers
  -- Random Selection Process
  --- 10 voting members drawn from a pool of 128 volunteers
- Recruit Nominees and Gather Data (July -> November)
  -- Position Descriptions
  -- Call for Nominations
  --- Out of 97 nominations 39 were accepted.
  -- Questionnaires
  -- Community Feedback
  -- Interviews with IAB/IESG/IAOC Chairs
  -- Interviews with exiting IAB/IESG Members
  -- Nominee Interviews (38 on-site in Seoul, 1 by phone)
- Select for Open Positions (November -> March)
  -- NomCom review of all inputs
  -- First order sorting
  -- Discussion of top ranked nominees
  -- Straw Polls/Condorcet ranking/etc.
  -- Up/Down E-Vote to confirm top choices
  -- Submit for approval (IAB/ISOC/IESG)
  -- Announce slates when approved.
  -- Feedback provided to nominees who accepted a nomination on request.

Bonus Round Nominee Process (2016-2017) 

- Recruit/Select/Submit/Announce for short term ART AD vacancy
  -- mandated 6 week time-line start to finish
  -- appointment must run a full year
  -- had to complete before IETF 98
  -- There were 14 nominations and 4 people accepted
  -- Interviews were conducted via WebEX
  -- Selection and Approval process was successful

Areas of Weakness:

- Some Areas have very small leadership pools
  -- OPS/INT/TSV
  --- persistent issue over several NomCom cycles
- Employer support for participation
  -- we are losing good candidates due to lack of support
  -- the value to the IETF and the nominee may be well understood
  -- the value proposition for the employer needs work/promotion
- Clear and distinct position descriptions
  -- The IAOC and IAB material may be too generic for the *randomly selected*
     NomCom members who don't track these bodies closely.
  -- The Operations and Management distinction not always reflected
     in community nominations so may need additional flagging.

IETF Internal Data and Tools:

- Validating status for NomCom volunteers
  -- existing data has some gaps
  -- but this is improving with each round of registrations
- Validating primary email addresses in the data-tracker
  -- some folk don't see their nomination due to stale email in profiles
- Tools and AMS folk provide great support to the NomCom 
  -- The tools depend on good data to function
  -- Tools team was quick to fix issues and small requests
  -- There is a wish list for future features
  -- Still a lot of hand crafted tasks outside the existing tool set

NomCom Lessons Learned (Re-learned):

- We needed a Questionnaire for the IETF Chair position
  -- we used the IESG form but had additional questions
- All of the questionnaires are long but... hard to cut down.
- There is a strong bias toward Two Term appointments
  -- one and three term appointment options engender a lot of discussion
- Nominations and feedback both come from a small sub-set of the community
  -- less then 100 individuals overall
- A "living" NomCom Chairs Best Practices document would be useful

RFC Updates Needed:

- The composition of the IESG has changed (and may again)
  -- document the 3 AD pattern
  -- document the 2 AD (not alike) pattern
- We need to document the process for filling an IESG to IESG move
  --- current text addresses IAB to IESG
  --- additional patterns may also occur

and...

The Elephant in the Room:

- Remote Participation
  -- The NomCom has a 3 of 5 meeting requirement for both
     the Chair and the membership
  -- We had one nominee who has been primarily remote
  -- Visa and meeting location issues  

Three things every IETFer can do

- Check your status to volunteer for the NomCom
  -- https://www.ietf.org/registration/nomcom.py
  -- and work with AMS to update your records as needed
  -- if you qualify, check the NomCom Volunteer box when your register
- Check your profile in the data-tracker
  -- https://datatracker.ietf.org/accounts/profile/
  -- are your Primary and Active email details correct?
- Provide feedback on the Nominees!
  -- consider providing area and issue feedback as well


From nobody Mon Mar 27 14:17:37 2017
Return-Path: <mcr+ietf@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 924B3129690; Mon, 27 Mar 2017 14:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ngfzQJ7n9fm9; Mon, 27 Mar 2017 14:17:28 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7646312968D; Mon, 27 Mar 2017 14:17:07 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 75224200A3; Mon, 27 Mar 2017 17:40:55 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9208D636E0; Mon, 27 Mar 2017 17:17:06 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
CC: tools-discuss@ietf.org
Subject: Re: Report out from the NomCom 2016-2017
In-Reply-To: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
References: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 27 Mar 2017 17:17:06 -0400
Message-ID: <10254.1490649426@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dWdaQhRoG_7MqUpCi096ewL5Vzw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 21:17:30 -0000

--=-=-=
Content-Type: text/plain


NomCom Chair 2016 <nomcom-chair-2016@ietf.org> wrote:
    > - Check your status to volunteer for the NomCom --
    > https://www.ietf.org/registration/nomcom.py -- and work with AMS to
    > update your records as needed -- if you qualify, check the NomCom
    > Volunteer box when your register

Maybe these two steps could be combined, and one's nomcom eligility placed
on your registration receipt...



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljZgU8ACgkQgItw+93Q
3WVY0Af+NOibX9h5NrNckkZViuWM+zd677fa2JBHc/xaoouFBmkUedjO1FE7jekI
D0zWdd6k0xVvcl05cIdw+rtje85TNPSsCVEMEnvZ41UYiOlD4V2IGiS3oL431KDC
9/ks3N9cmGkIbf3WakO2zziXH0kHZKGafDS9QEBv+97PZsu2ry6ccVKM0nnSiUsm
bzj80qZBauOhPDAoGmstMVgVpwoASZH3GHXY+mPc1QPCMrY4H+nP79edHt6NQCbW
mM+oJVOtb4k2+Hf0ujCJ37Y3HbD2h/KF3kEDS/QLAhsbs6gOTIk+3JflFc9yzkar
v0tY+FxT6bKcGCaPqnqfiS/AmejlPg==
=Ldb7
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar 27 14:28:07 2017
Return-Path: <ggm@algebras.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 4036E129683 for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 14:28:01 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MnyHFZtfhW3O for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 14:27:59 -0700 (PDT)
Received: from mail-vk0-x242.google.com (mail-vk0-x242.google.com [IPv6:2607:f8b0:400c:c05::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28CEC1296A8 for <ietf@ietf.org>; Mon, 27 Mar 2017 14:27:38 -0700 (PDT)
Received: by mail-vk0-x242.google.com with SMTP id j137so10237954vke.0 for <ietf@ietf.org>; Mon, 27 Mar 2017 14:27:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=p8nvW8fCz2n/bTo9Cr/rmWXQQpeCTC8FCtdH5UgVv8s=; b=Jyt7CxckOnQ2AZN6RXO6/+GugZodk22I/8LRaEDwFfIGZLZ5jxskjEYE63T3m4S8My AkCm8Njsu38pAJJu7gR4KHKv2D+7/L7Rdtx+YThA6JXLp4W5wKcc7bXeUfw1aHg0zU0a 6Vam2Mr3xRT14Ahc0hw61GUG1/nT4f8rCfyt7gCF7cJO0JzkdXL40/UFWx80FoZZvclL kuLf/ZMfl9AmZCVHmrXLuZwemAIdHHXNui4nXxXBSeVTpQvg03cQEA4PXH+6dkcnVSGc C4/QnEzP9rccmNaOThMdbtEcAtFKqZLn0a61h6y500RuRvYjTfrnLuN+pbCRNEmQkBMx G+kA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=p8nvW8fCz2n/bTo9Cr/rmWXQQpeCTC8FCtdH5UgVv8s=; b=ASnjRma9qGLHNWuyoLSzITr+2IuDVghz09cteF/btMdCN0ycVTkt3f4ivVrVOzrzBT XsSHl+M809cBAuJX2/7iT/qovt1f4s4arCvRTRvuIGQlWlBr4WkD63KjjmRwrCH51iiY Rp0nMvhVKiAQECsH8rxRhq4S1/4EoGKfx+fdk2/A0uNXDaHy6AfiB/uI2Or1rrtDoAXY W++Dl6qjTKYshnTB3BqiD0IfSNlOEN4lX37fSHMz2PjhJx7GwYvsQx7nzfYnruZgp7bx NsqLgqjFRiTga6w5Te+/p7deoiq5Y2CNPZAMtSR6bG9btTWSOtaNcAHEYKSaZFfHd1ZQ vRlg==
X-Gm-Message-State: AFeK/H2agXxTLLKrhysqrzKjLSjM13HQddqNAuvZ7iAr3OWBf7+DOd+FSQIcb5ezD7gLdxGh+9EFVVPHU4Ugnw==
X-Received: by 10.176.7.71 with SMTP id h65mr10042028uah.46.1490650056964; Mon, 27 Mar 2017 14:27:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.84.20 with HTTP; Mon, 27 Mar 2017 14:27:36 -0700 (PDT)
X-Originating-IP: [2001:67c:370:128:7d2b:3ede:b43f:2f90]
In-Reply-To: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
References: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
From: George Michaelson <ggm@algebras.org>
Date: Mon, 27 Mar 2017 16:27:36 -0500
Message-ID: <CAKr6gn3LxBMkhgEJx__W1U26XBJg7ZYQS2NnaA=BsrzP+qeL0w@mail.gmail.com>
Subject: Re: Report out from the NomCom 2016-2017
To: IETF Discussion Mailing List <ietf@ietf.org>
Cc: IETF Announcement List <ietf-announce@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OCwvY52KqULsSq7hW1yisoA4Fpk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 21:28:01 -0000

I'd like to thank Lucy and all the nomcom team I interacted with, for
a positive, affirming and above-all human(e) process.

I found the entire conversation very profitable. I understand
expectations better, and I was able to "escape the room" with my
dignity and a sense of purpose intact.

Considering the modern focus on 3h and 3day whiteboard tests of
terror, what we did, is have a conversation of equals.

which, I like.

so, thanks.

-George

On Mon, Mar 27, 2017 at 3:24 PM, NomCom Chair 2016
<nomcom-chair-2016@ietf.org> wrote:
> All -
>
> Please find below some high level outcomes and observations from this years
> NomCom. Issues of particular interest to the community include both the
> issues related to recruiting and supporting nominees and the corner cases we
> encountered that which may require updates to our current guiding documents.
> The list closes with a few action steps that everyone can take to help improve
> next years process.
>
> We will be happy to take questions and community feedback either in Plenary
> or via email: nomcom-2016@ietf.org
>
> Details on this years membership and the outcomes of our selection processes
> can be found here: https://datatracker.ietf.org/nomcom/2016/
>
> I want to thank everyone who participated this cycle. The inputs, the
> willingness to serve, and the willingness to support nominee participation all
> contributed to our results. Special thanks to Peter Yee for stepping up as
> the in-coming NomCom Chair.
>
> Lucy Lynch
> NomCom Chair 2016-2017
>
> NomCom 2016-2017
>
> The Three Stages of the NomCom Process
>
> - Recruit and Select NomCom Members  (March -> July)
>   -- Calls for Volunteers
>   -- Direct email/Registration tick box volunteers
>   -- Random Selection Process
>   --- 10 voting members drawn from a pool of 128 volunteers
> - Recruit Nominees and Gather Data (July -> November)
>   -- Position Descriptions
>   -- Call for Nominations
>   --- Out of 97 nominations 39 were accepted.
>   -- Questionnaires
>   -- Community Feedback
>   -- Interviews with IAB/IESG/IAOC Chairs
>   -- Interviews with exiting IAB/IESG Members
>   -- Nominee Interviews (38 on-site in Seoul, 1 by phone)
> - Select for Open Positions (November -> March)
>   -- NomCom review of all inputs
>   -- First order sorting
>   -- Discussion of top ranked nominees
>   -- Straw Polls/Condorcet ranking/etc.
>   -- Up/Down E-Vote to confirm top choices
>   -- Submit for approval (IAB/ISOC/IESG)
>   -- Announce slates when approved.
>   -- Feedback provided to nominees who accepted a nomination on request.
>
> Bonus Round Nominee Process (2016-2017)
>
> - Recruit/Select/Submit/Announce for short term ART AD vacancy
>   -- mandated 6 week time-line start to finish
>   -- appointment must run a full year
>   -- had to complete before IETF 98
>   -- There were 14 nominations and 4 people accepted
>   -- Interviews were conducted via WebEX
>   -- Selection and Approval process was successful
>
> Areas of Weakness:
>
> - Some Areas have very small leadership pools
>   -- OPS/INT/TSV
>   --- persistent issue over several NomCom cycles
> - Employer support for participation
>   -- we are losing good candidates due to lack of support
>   -- the value to the IETF and the nominee may be well understood
>   -- the value proposition for the employer needs work/promotion
> - Clear and distinct position descriptions
>   -- The IAOC and IAB material may be too generic for the *randomly selected*
>      NomCom members who don't track these bodies closely.
>   -- The Operations and Management distinction not always reflected
>      in community nominations so may need additional flagging.
>
> IETF Internal Data and Tools:
>
> - Validating status for NomCom volunteers
>   -- existing data has some gaps
>   -- but this is improving with each round of registrations
> - Validating primary email addresses in the data-tracker
>   -- some folk don't see their nomination due to stale email in profiles
> - Tools and AMS folk provide great support to the NomCom
>   -- The tools depend on good data to function
>   -- Tools team was quick to fix issues and small requests
>   -- There is a wish list for future features
>   -- Still a lot of hand crafted tasks outside the existing tool set
>
> NomCom Lessons Learned (Re-learned):
>
> - We needed a Questionnaire for the IETF Chair position
>   -- we used the IESG form but had additional questions
> - All of the questionnaires are long but... hard to cut down.
> - There is a strong bias toward Two Term appointments
>   -- one and three term appointment options engender a lot of discussion
> - Nominations and feedback both come from a small sub-set of the community
>   -- less then 100 individuals overall
> - A "living" NomCom Chairs Best Practices document would be useful
>
> RFC Updates Needed:
>
> - The composition of the IESG has changed (and may again)
>   -- document the 3 AD pattern
>   -- document the 2 AD (not alike) pattern
> - We need to document the process for filling an IESG to IESG move
>   --- current text addresses IAB to IESG
>   --- additional patterns may also occur
>
> and...
>
> The Elephant in the Room:
>
> - Remote Participation
>   -- The NomCom has a 3 of 5 meeting requirement for both
>      the Chair and the membership
>   -- We had one nominee who has been primarily remote
>   -- Visa and meeting location issues
>
> Three things every IETFer can do
>
> - Check your status to volunteer for the NomCom
>   -- https://www.ietf.org/registration/nomcom.py
>   -- and work with AMS to update your records as needed
>   -- if you qualify, check the NomCom Volunteer box when your register
> - Check your profile in the data-tracker
>   -- https://datatracker.ietf.org/accounts/profile/
>   -- are your Primary and Active email details correct?
> - Provide feedback on the Nominees!
>   -- consider providing area and issue feedback as well
>


From nobody Mon Mar 27 15:43:10 2017
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 18544126E3A for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 15:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level: 
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VoQuFUlv9qPp for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 15:43:06 -0700 (PDT)
Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86378126BFD for <ietf@ietf.org>; Mon, 27 Mar 2017 15:43:06 -0700 (PDT)
Received: by mail-it0-x235.google.com with SMTP id y18so93204769itc.0 for <ietf@ietf.org>; Mon, 27 Mar 2017 15:43:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=pLjDPtJDlTHWFqoMWewIWzR2fqJvSMc8xJsy3+Iq2Lg=; b=TYkIcajBBEXXBAC6hhFu2tWptLPM4WAI8EaOh0AuwnC1jw5MmWiUkQ5fCHGeWxoPXc 2juiyjhAkQr6XsOaV+gVEBcXxD7A231dDBownRPZP8Zir/a6Aa/Xgr4VAvEuemZw6VZ5 3RQCG8qooEGpIt5+1mJGYrT8CnIv61u4YIlC69r8iGyrTh0q+qLtl0bTTu21DXxMHaHG 7J+2bw1R9ZgPq6upsGEnApXoQieE5l2gpdN5bXDN3UtelXu2fblESjOufX9YXQFqfa3M dJ4DtAUv+FyiLd5Okra4HCjWOU15R75CGys2aG+qNSFWAa9fQ0u/CqvEdAUYA2Lr9C30 2+1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=pLjDPtJDlTHWFqoMWewIWzR2fqJvSMc8xJsy3+Iq2Lg=; b=NMDRwqd84sCgRlD/rLqarUSkcdG2T9JSUsaPluCif2IEUOs2xHkbqwIUGQYVQzvBFO gt91+dh3bTMy2l2GLF/0/kL6Vm59J6MPUvt8hhO8cQUwlgb22muWnm819nL964CNY0Qd coPc0dL22F7H7pLMNR1OzIZhTFYdQ8o59gFkt0gc8bfmsgAj0rqISw8mqfVF5W9reGnD PpoIhnXbobIPjQjrvwEqLIk3gp8py9ggWqv5uszWv3kbkJ5S/pwP2G/ZAQa7Y9gL8ps9 VOa9HymYxOQYjR+1QgyMa5h7iaQpyEbMsOEz0zt0KW2h2jeJXwXg/MFWu1x8K99cwrP1 BdWw==
X-Gm-Message-State: AFeK/H0MjWKT3EnD69Hiw83p0jxLCVozNcsxObCG85Z481tvn1lKwW0osg9jvwsjZoA5nr+2Mt0mlMNurD5G/A==
X-Received: by 10.107.46.136 with SMTP id u8mr22771230iou.85.1490654585846; Mon, 27 Mar 2017 15:43:05 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.35.200 with HTTP; Mon, 27 Mar 2017 15:43:05 -0700 (PDT)
In-Reply-To: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
References: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 27 Mar 2017 17:43:05 -0500
X-Google-Sender-Auth: UB4UpAyV8KnH-cVYEkylN8sdqZU
Message-ID: <CAC4RtVCh=X7M6GzicYtp7cr3FTjzY-=Fczp1eSf5uetQY6zYHw@mail.gmail.com>
Subject: Re: Report out from the NomCom 2016-2017
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GONQFTl1ivt_43fPbYB7TRh5Kdg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 22:43:08 -0000

>   -- Announce slates when approved.
>   -- Feedback provided to nominees who accepted a nomination on request.

I've thanked the NomCom for this last item, and I want to repeat that
thanks publicly: I'm *so* glad that this NomCom has agreed to provide
feedback, I've found their feedback to be excellent and valuable to
me, and I very much hope that future NomComs continue this new
practice.

Barry


From nobody Mon Mar 27 15:45:33 2017
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 920AD126E3A for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 15:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1J6pjdnkONyh for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 15:45:30 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E20EC129577 for <ietf@ietf.org>; Mon, 27 Mar 2017 15:45:29 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id w43so65298694wrb.0 for <ietf@ietf.org>; Mon, 27 Mar 2017 15:45:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PnxbRN3eug+BdNJpCXmv3KIJJsnJ7kIcVVPs0Qnm3zg=; b=GiuwO+fGmGS+nmG+9/LcoGK+eRl4wINyRhnUqYkJvdgNmkK2miAI3r/uv3GZQbobXT UX6tEOXtET7FN5Frp7h3IxtaF5Fv5y3Z+3dg6DDm2r4MxD1insLT2mW19J832dsaaPF/ mzKKXOey8TpxalU8kGPibTEfakzStwiZeTyKEzKdS8aavaXuFHapqh2t7CQK6pSD0s0O 5ke75cpFnPwbG4mYtxyrsQ8YIT09x4ooo94TsVMfj4Qqdxa418qAkvONeNe6FRxtV7qV vu0z0wGomel6ky+nCKrmOmNj8ESEmPw/GnHqyE2ZunNL9ixyQEmZWYDsvpdKjJ9YemGr rvsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PnxbRN3eug+BdNJpCXmv3KIJJsnJ7kIcVVPs0Qnm3zg=; b=fKobL5N2AWmcofExNUFr4gHFZbUScwOsmwL/bUjhEgMVbvCn1zhDQ64qr6vYF+KMnv vL7My9DzXZ1VHB6EdA1sKInB7WzaO4s7s4xth3wLLlXdjQF4nyCwLdehbhUYyda/3jB9 jPvu3J2eYI5o9r5PkFPgTnDYT4Y2XbBSfaSrCovtNqb6iuhgEXwqFfdG9zuwvsC99dqV hrBDsngNDkWt2+RJs6PtQ6MyZGeUqapFkFa4liKz8Lb4OaKg8NdBlM4i4pfQN6cqzpWf Tk4lF7Xar88fpzQzY3If2Nqw0DY+GQ76FpfUWjopcZ7PlrSoT0e66uqhQGyQPkbIoqaJ 1ENQ==
X-Gm-Message-State: AFeK/H1u9Qq5hlvfVy7XMYXTzox1JAj2SKE1gyNAWJru2vE34OyFpnu2FQuD5Zw18ucWvFJUNp7SaErgBXl9Ag==
X-Received: by 10.28.180.195 with SMTP id d186mr11751612wmf.112.1490654728226;  Mon, 27 Mar 2017 15:45:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.145.69 with HTTP; Mon, 27 Mar 2017 15:45:27 -0700 (PDT)
In-Reply-To: <CAC4RtVCh=X7M6GzicYtp7cr3FTjzY-=Fczp1eSf5uetQY6zYHw@mail.gmail.com>
References: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com> <CAC4RtVCh=X7M6GzicYtp7cr3FTjzY-=Fczp1eSf5uetQY6zYHw@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Mon, 27 Mar 2017 18:45:27 -0400
Message-ID: <CAG4d1rfc4Rm3Avr-fkykqb0T3cd8VVp8Hv6sa0xgp=6nOLYpWQ@mail.gmail.com>
Subject: Re: Report out from the NomCom 2016-2017
To: Barry Leiba <barryleiba@computer.org>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a114b61d68f1224054bbe19e4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qhdt59UJCR1P7Q4dH7k8Ofshojw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 22:45:32 -0000

--001a114b61d68f1224054bbe19e4
Content-Type: text/plain; charset=UTF-8

On Mon, Mar 27, 2017 at 6:43 PM, Barry Leiba <barryleiba@computer.org>
wrote:

> >   -- Announce slates when approved.
> >   -- Feedback provided to nominees who accepted a nomination on request.
>
> I've thanked the NomCom for this last item, and I want to repeat that
> thanks publicly: I'm *so* glad that this NomCom has agreed to provide
> feedback, I've found their feedback to be excellent and valuable to
> me, and I very much hope that future NomComs continue this new
> practice.


I strongly agree.  It is extremely helpful to have feedback.

Regards,
Alia

--001a114b61d68f1224054bbe19e4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Mar 27, 2017 at 6:43 PM, Barry Leiba <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:barryleiba@computer.org" target=3D"_blank">barryleiba@computer.org</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"><span class=3D"">&gt;=
=C2=A0 =C2=A0-- Announce slates when approved.<br>
&gt;=C2=A0 =C2=A0-- Feedback provided to nominees who accepted a nomination=
 on request.<br>
<br>
</span>I&#39;ve thanked the NomCom for this last item, and I want to repeat=
 that<br>
thanks publicly: I&#39;m *so* glad that this NomCom has agreed to provide<b=
r>
feedback, I&#39;ve found their feedback to be excellent and valuable to<br>
me, and I very much hope that future NomComs continue this new<br>
practice.</blockquote><div><br></div><div>I strongly agree.=C2=A0 It is ext=
remely helpful to have feedback.</div><div><br></div><div>Regards,</div><di=
v>Alia=C2=A0</div></div><br></div></div>

--001a114b61d68f1224054bbe19e4--


From nobody Mon Mar 27 15:48:20 2017
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 E45291296B1 for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 15:48:18 -0700 (PDT)
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=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ATy23KMLvMKb for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 15:48:17 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFFF01296A4 for <ietf@ietf.org>; Mon, 27 Mar 2017 15:48:16 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v2RMmBqh014689; Mon, 27 Mar 2017 23:48:11 +0100
Received: from 950129200 (dhcp-8535.meeting.ietf.org [31.133.133.53]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v2RMm9HY014671 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Mar 2017 23:48:10 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Barry Leiba'" <barryleiba@computer.org>, "'IETF discussion list'" <ietf@ietf.org>
References: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com> <CAC4RtVCh=X7M6GzicYtp7cr3FTjzY-=Fczp1eSf5uetQY6zYHw@mail.gmail.com>
In-Reply-To: <CAC4RtVCh=X7M6GzicYtp7cr3FTjzY-=Fczp1eSf5uetQY6zYHw@mail.gmail.com>
Subject: RE: Report out from the NomCom 2016-2017
Date: Mon, 27 Mar 2017 23:48:09 +0100
Message-ID: <002a01d2a74c$3624f330$a26ed990$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG4AZj8JFA8DvNOcql1Tf+uKxwIcgEoEo8ModVTb8A=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-22970.003
X-TM-AS-Result: No--13.056-10.0-31-10
X-imss-scan-details: No--13.056-10.0-31-10
X-TMASE-MatchedRID: HXSqh3WYKftlx7C8em/tVu0/o+/4D7DzXZfXqSXUXvkQI6JYceCSYGCA /WPi4f08CiU/ecaS1Y1W3VcAc19KwQmWooBi7asXGrp19tJczoWdtHUoZpvlecWkDW4kV3WaIRx QCWPfi6l8beWYRZDCBtGd1EGjtJPEcqDNL2RTzARb/n0V6kg0kRLXa2P1m93z4VxV5lFS0Fk5d9 n04fLNZk2pWHi7CF1CRpvSv/4NlMkRTDsU3WmrQriMC5wdwKqdfS0Ip2eEHnxlgn288nW9IN5/H gWYxplM5MIx11wv+CM7AFczfjr/7NNZrheW7/xSg+TCLVR0mfy1cRW8EC796KjHKZ5NBOEJh+EJ IQHqC8g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QJQ59lP_Sv3GgfxKRrErT-HeENk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 22:48:19 -0000

Echo what Barry said.
IMHO, giving feedback was a very brave thing to do.=20
Previous NomComs have shied away from this for fear of confidentiality =
and the additional thought and hard work needed to keep community =
feedback anonymous.=20
Also NomComs have been worried about opening discussions about their =
decisions.
I think this year's NomCom handled this very well, and I hope they leave =
a sound trail of breadcrumbs for future NomComs to follow.

Adrian

> >   -- Feedback provided to nominees who accepted a nomination on =
request.
>=20
> I've thanked the NomCom for this last item, and I want to repeat that
> thanks publicly: I'm *so* glad that this NomCom has agreed to provide
> feedback, I've found their feedback to be excellent and valuable to
> me, and I very much hope that future NomComs continue this new
> practice.


From nobody Mon Mar 27 16:01:25 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E2D01296B9 for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 16:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=Pr+Ng+Y8; dkim=pass (1024-bit key) header.d=yitter.info header.b=l+uXfcYL
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h_OJ-t8zhrN5 for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 16:01:22 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16EB61296B3 for <ietf@ietf.org>; Mon, 27 Mar 2017 16:01:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 70361BB82E for <ietf@ietf.org>; Mon, 27 Mar 2017 23:00:51 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1490655651; bh=SfqchmMTHBAg3IvJbyqEyh8stvaXNjDql0NJ0eaj9SI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Pr+Ng+Y85LeQOmAFJ/ranFQ/fniD3hH9YbOKcURkoP5P2RpS22hrpP3Yi8rcyhaVu 31GA+uA9MkCsjG/mS8f8OM0mkrEPItliA0LBnA8bL6ZNi/tUAZHJdRB1zBFBMCIM1g kYRKQy0gUGVqpPe29Kpkn8yPQrFUdHTgSmmywBmk=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0J0ql5zH0N7 for <ietf@ietf.org>; Mon, 27 Mar 2017 23:00:50 +0000 (UTC)
Date: Mon, 27 Mar 2017 19:00:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1490655650; bh=SfqchmMTHBAg3IvJbyqEyh8stvaXNjDql0NJ0eaj9SI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=l+uXfcYL6DlqJWFJFnaRH2uWrgbuTLwL8IQHSoB6MgsgxVZwlf7ZL9f7781E/CJ8e /7FdKao3Oo0bg0V9ad7AtDQw6/nrwsOJsVR31bnvVLEzZ61C0rdNxOGM4j9+hKjG3e JTt7OnQfPSxN78k58hZ3kSlMTBhGI5grmiwS4g3s=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Employer support (was Re: Report out from the NomCom 2016-2017)
Message-ID: <20170327230048.GB36874@mx4.yitter.info>
References: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q_3SEk6iL8e7_3vnqkWJLpJp1pQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Mar 2017 23:01:24 -0000

Dear colleagues,

I've now had more than one person ask me about this, and since the
NomCom report raises the issue of employer support I think
transparency requires that I say something.

While I never planned to stand for IAB chair again this year, I did
submit my candidacy for reappointment to the IAB.  Unfortunately, due
to some uncertaintly in my personal circumstances before the NomCom
rendered its decision, I had to withdraw my name from consideration at
the last minute.  To be clear, my current employer did not withdraw
support for my activities in the IETF.  I apologise to those who spent
their time sending comments assuming my commitment to stand, when it
turned out I could not follow through on that commitment.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Mar 27 22:17:55 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CEEDA128D44; Mon, 27 Mar 2017 22:17:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Chair <chair@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org,odonoghue@isoc.org
Subject: Education and Mentoring Directorate
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org,chair@ietf.org,odonoghue@isoc.org
Message-ID: <149067827375.30562.13563276433564594725.idtracker@ietfa.amsl.com>
Date: Mon, 27 Mar 2017 22:17:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/knrYRJ3uPwnvgr9tknVXenRdLlE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 05:17:54 -0000

The goals of the IETF Education and Mentoring Directorate are to enhance
the productivity of IETF work, expand diversity and inclusiveness of the
IETF, and enable the IETF to facilitate technical development and
innovation in the Internet.

In support of this goal, this directorate will structure and guide the
educational activities and associated materials to be more accessible,
relevant, reusable, and broadly understandable. The directorate shall
also help the mentoring activities to focus on the establishment of
relationships that enable productive participation in the IETF. Next,
this directorate will serve as a coordination function for IETF related
outreach activities, directed at participants, ensuring that related
activities are sufficiently coordinated and have the necessary
education and mentoring program support. Finally, the directorate
will work on improved metrics and measurements for assessing the
effectiveness of directorate activities. 

This directorate serves the General (GEN) area in IETF. The
participants include the project leaders of the defined education,
mentoring, and outreach coordination projects, the IESG and tools
liaisons to educational activities, the IETF chair, IETF executive
director, and additional members selected as needed. 

The initial projects identified by the directorate are: 

- Tutorials
- Online educational materials (content and organization) 
- Ongoing document maintenance (Tao, “About the IETF”, etc) 
- Newcomer’s Outreach (meet and greet, social dinner, emails) 
- WG Chairs Forum
- Mentoring 
- IETF Hubs 
- Assessment metrics and measurement

Success of these activities depends on support from the community.
Specific examples of volunteers currently needed: 

- Website reviewers 
- IETF Overview Document editors
- WG Chair Forum coordinator
- Configuring tutorials for better online access
- Online educational materials (content and organization) 

Please send email to Karen and the IETF Chair to volunteer! 

Jari Arkko
Karen O'Donoghue


From nobody Mon Mar 27 22:55:26 2017
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 21B981292D0 for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 22:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2c9d0LF-k6d for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 22:55:22 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E928128AB0 for <ietf@ietf.org>; Mon, 27 Mar 2017 22:55:22 -0700 (PDT)
Received: from [77.72.226.187] (unknown [IPv6:2a01:3f0:1:0:783a:9e0b:e930:e8dd]) by mail.frobbit.se (Postfix) with ESMTPSA id DB5E5202D4 for <ietf@ietf.org>; Tue, 28 Mar 2017 07:55:18 +0200 (CEST)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: ietf@ietf.org
Subject: Re: IAB Selects Ted Hardie as new IAB Chair
Date: Tue, 28 Mar 2017 07:55:18 +0200
Message-ID: <6DF45F8B-58F1-4039-81E7-FF524A2512BA@frobbit.se>
In-Reply-To: <149062321788.30595.1561953763547820100.idtracker@ietfa.amsl.com>
References: <149062321788.30595.1561953763547820100.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_138C2E69-E732-480D-A8A5-2873AD3DA338_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6080)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c-b9C24tJObHlH4kJXHJ9ix_XNY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 05:55:24 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_138C2E69-E732-480D-A8A5-2873AD3DA338_=
Content-Type: text/plain

On 27 Mar 2017, at 16:00, IAB Executive Administrative Manager wrote:

> The IAB has selected Ted Hardie as the new IAB Chair.
>
> The IAB would like to thank Andrew Sullivan for his service in the role over the past two years.

What an excellent swap!

Andrew, thanks for everything!

Ted, welcome!!!

   Patrik

--=_MailMate_138C2E69-E732-480D-A8A5-2873AD3DA338_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAljZ+sYACgkQrMabGguI181ZywCfRgrJN9BO7LyeEqdjEVLPmOW7
Ma4AnA2CY6YpL6YWzZ83YKSbTdP7mFnz
=640u
-----END PGP SIGNATURE-----

--=_MailMate_138C2E69-E732-480D-A8A5-2873AD3DA338_=--


From nobody Mon Mar 27 23:38:02 2017
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 36869129669 for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 23:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pj4gpBF2Popc for <ietf@ietfa.amsl.com>; Mon, 27 Mar 2017 23:37:58 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4328129442 for <ietf@ietf.org>; Mon, 27 Mar 2017 23:37:58 -0700 (PDT)
Received: from [77.72.226.187] (unknown [IPv6:2a01:3f0:1:0:783a:9e0b:e930:e8dd]) by mail.frobbit.se (Postfix) with ESMTPSA id 4080421903; Tue, 28 Mar 2017 08:37:56 +0200 (CEST)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Joe Touch" <touch@isi.edu>
Cc: "Phillip Hallam-Baker" <phill@hallambaker.com>, "Tony Finch" <dot@dotat.at>, "IETF Discussion Mailing List" <ietf@ietf.org>, "Jared Mauch" <jared@puck.nether.net>
Subject: Re: Predictable Internet Time
Date: Tue, 28 Mar 2017 08:37:56 +0200
Message-ID: <4079C051-C0C1-4220-8F0A-39F1FF0EDEF3@frobbit.se>
In-Reply-To: <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <9F0F8841-BC1D-4C27-83EF-8F93F33FB021@puck.nether.net> <CAMm+Lwh5JMn+JxPB3Q3RKpeibckVSB2Fqm_RajcnU28OAx=jOw@mail.gmail.com> <1483474918.1346083.836313393.2699EBD5@webmail.messagingengine.com> <CAMm+LwjJDyCv2mBG8ob-njDj-4m5tr7jP6XAiEn1ME5NCYcpiQ@mail.gmail.com> <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu> <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_EB3E301D-A68B-401B-BA06-4CF416A51DE7_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6080)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iTKCLBGhIwXJxXRSSxSRdqmhrfo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 06:38:01 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_EB3E301D-A68B-401B-BA06-4CF416A51DE7_=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Joe,

I have read your I-D and like it! Let me start there :-)

What I think is not clear enough is the problem with POSIX, and it should=
 be more clear in some place, maybe section 6.1, that POSIX definition wh=
ich is in use in quite a number of systems do not handle leap second very=
 well. Too many do believe the time_t definitions include the number of s=
econds since epoch when in reality it does not (as you note in the defini=
tions).

One could even question whether it is Continuous as two seconds will have=
 the same number since epoch around the addition of a leap second (the la=
st second of the day with leap second and the first the day after the add=
ition of leap second). I claim it is not as if you look at also fractions=
 of seconds it will go backward like:

:
(N-1).0
(N-1).1
:
(N-1).9
N.0
N.1
:
N.9
N.0
N.1
:
N.9
(N+1).0
(N+1).1
:

There are some people that have suggested a change, for example <http://w=
ww.cl.cam.ac.uk/~mgk25/time/c/> but I have not seen any movement. Maybe y=
ou know more than me on this?

   Patrik

On 27 Mar 2017, at 21:34, Joe Touch wrote:

> Hi, all,
>
> I've submitted the time frame discussion intended to resolve this issue=
, which also recently arouse on another mailing list. Further discussion =
on this draft will occur on the ART mailing list (art@ietf.org).
>
> Joe
>
> -----------
>
> A new version of I-D, draft-touch-time-01.txt
> has been successfully submitted by Joe Touch and posted to the IETF rep=
ository.
>
> Name:		draft-touch-time
> Revision:	01
> Title:		Resolving Multiple Time Scales in the Internet
> Document date:	2017-03-27
> Group:		Individual Submission
> Pages:		17
> URL:            https://www.ietf.org/internet-drafts/draft-touch-time-0=
1.txt Status:         https://datatracker.ietf.org/doc/draft-touch-time/
> Htmlized:       https://tools.ietf.org/html/draft-touch-time-01 Htmlize=
d:       https://datatracker.ietf.org/doc/html/draft-touch-time-01 Diff: =
          https://www.ietf.org/rfcdiff?url2=3Ddraft-touch-time-01
>
> Abstract:
>    Internet systems use a variety of time scales, which can complicate =
  time comparisons and calculations. This document explains these   vario=
us ways of indicating time and explains how they can be used   together s=
afely. This document is intended as a companion to   Internet time as dis=
cussed in RFC 3339.

--=_MailMate_EB3E301D-A68B-401B-BA06-4CF416A51DE7_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAljaBMQACgkQrMabGguI183f+QCeI+0V6J4C93i2zxROIRzloIQR
L9QAn0eCLd+LwHAwK7qZsSx5Zb8E2XG6
=5Kxs
-----END PGP SIGNATURE-----

--=_MailMate_EB3E301D-A68B-401B-BA06-4CF416A51DE7_=--


From nobody Tue Mar 28 00:35:25 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E6335129413; Tue, 28 Mar 2017 00:35:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?b?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>
To: <ops-dir@ietf.org>
Cc: draft-ietf-pals-status-reduction.all@ietf.org, ietf@ietf.org, pals@ietf.org
Subject: Review of draft-ietf-pals-status-reduction-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149068651891.30599.6466255675652833743@ietfa.amsl.com>
Date: Tue, 28 Mar 2017 00:35:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HdzoEkqicw6DXX84DO2c5wcmEJA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 07:35:19 -0000

Reviewer: Jürgen Schönwälder
Review result: Has Nits

Disclaimer: I have not much clue about MPLS LSP PWs and hence I am
reading this from a perspective of a clueless outsider.

Section 1.2 is not really about terminology but instead it basically
expands acronyms. The section does not define any terms or does it
make it clear where terms are defined. A reader who does not know
T-PE
will not be pointed to a document that defines 'Terminating Provider
Edge Node of MS-PW'. I usally find terminology sections more useful
if
they say where definitions of terms get be found.

Section 3: s/the the/the/

Section 4: What is the 'Version' field in the message format?

Section 4: There is an 8-bit field marked U C Flags and I _assume_
the
U and C bits are the 'first' two bits and the 'remaining bits are the
flags managed by IANA. Perhaps make this clearer, e.g.:

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Last Received Seq Number     | Message Type  |U|C|   Flags   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Or alternatively simply name the entire 8-bit flags field like you do
in the text where you refer to Message Flags and then explain in the
text under the 'Message Flags' that the first two bits have a fixed
meaning.

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Last Received Seq Number     | Message Type  | Message Flags |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

This option carries less information but then you use 'Message Flags'
in several places and you also request an IANA registry for Message
Flags where the U and C bit are allocated. Looking at the IANA text,
it says 'bit position' 0 and 1. Not sure this is clear enough, you
seem to number bits in the order 0, 1, 2, ...

It turns out we have several slightly different labels further down
in
the document for this flags field throughout the document - this
makes
searching in the text difficult, please use a single consistent name
for this message field.

Section 8.2 says values 1 and 2 are defined in this document but then
it seems value 3 is also allocated, no?

Subsections of section 8 switches several times between decimal and
hexadecimal numbers. Perhaps things get clearer if a single number
system (e.g., hexadecimal) is used when talking about a specific
registry. Numbers like 134,217,728 look somewhat confusing, 0x8000000
seems simpler.



From nobody Tue Mar 28 05:53:32 2017
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 8EEE31243FE; Tue, 28 Mar 2017 05:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dp2nmqGIThZU; Tue, 28 Mar 2017 05:53:28 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FA471299A0; Tue, 28 Mar 2017 05:53:25 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id f193so38920429oib.2; Tue, 28 Mar 2017 05:53:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ds0RYZguf7M16ib70UuFhjID9HG/SaRtGyyAAcNJQFU=; b=Ewz8HbPsc/x6sincn9/onaN/i1aJ8x8LEhe9A22ambk8Gzz4byCz+XJ2LoWmemuNp9 hPOejO8cEK8JMWXVEDY/37zDkZiHDv3R9aCTLG8N86HqZ7XxTIekIs8ZwgNNvG8YuTco 3VoYcAQ4sEH4Cfe0+bvcWbpRAkiRq0iAdvCRXc8l52EzOZef3kz2HP6JoLL63ByKx0S3 DDTupUJHYyzNj4fWrEZ0MM76Z8qvCIpuItKTEp/mkqHM3xUyROjAXv5ROuN58Bte/t+0 ahGX84BLIHxvmhKKM/kTc6hR5RF6tOpUPpxR8QmG5VaFR2pnGoNehv57UREaZjd7EHpc GPhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ds0RYZguf7M16ib70UuFhjID9HG/SaRtGyyAAcNJQFU=; b=MI6iXmnrUW9RbQHjuXPqlMNGcYDBzmpGjXI5neM4cgTp/g9ZPcKbjfaExLVtVKEKHc NUXfngoDlX2duTHVtxKFoMMa4bE/2nm6GTfH4twzHOxPl9JA4oWhjGhqKk0zG8ZlwbpY +phyygFKdB6VfTqoWCyPwNy5bGMPVdUN3rzD2fgch8UbQlskbXUUcAFlnr6ElCWemYsp GBdedukOc2NzMBtwS8MsxOmbS6XAo2w9muGZvC+gdnKiGH8zd7srbC958SfJjNXtb0ug zrzZs9kiox5hbItSW2XwYrfdjT45NjiAh9wF0f4JTV3wzKqGS9wae6KV/mIXi/bV207A WeFQ==
X-Gm-Message-State: AFeK/H0T1dmHt5/ipZozrJZXWtMw96hgOfJcbyQ9Z5qSnMI0xUWkO6RnQTVohjcnZluwJykJJWWAb6298Po97w==
X-Received: by 10.202.207.85 with SMTP id f82mr14836753oig.159.1490705604741;  Tue, 28 Mar 2017 05:53:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.231.201 with HTTP; Tue, 28 Mar 2017 05:53:04 -0700 (PDT)
In-Reply-To: <149068651891.30599.6466255675652833743@ietfa.amsl.com>
References: <149068651891.30599.6466255675652833743@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 28 Mar 2017 07:53:04 -0500
Message-ID: <CAA=duU2snsfsVQUX+P_NGii+t4Qvzpqjz6ms0PWnT4v+EjoOYA@mail.gmail.com>
Subject: Re: Review of draft-ietf-pals-status-reduction-04
To: =?UTF-8?B?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>
Cc: ops-dir@ietf.org, draft-ietf-pals-status-reduction.all@ietf.org,  IETF Discussion <ietf@ietf.org>, "pals@ietf.org" <pals@ietf.org>
Content-Type: multipart/alternative; boundary=001a113df38c091317054bc9f209
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EKpLCDDKZwQG_MyGOBmxfEMMrq0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 12:53:31 -0000

--001a113df38c091317054bc9f209
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

J=C3=BCrgen,

On behalf of the PALS WG, thanks for the review!

Cheers,
Andy


On Tue, Mar 28, 2017 at 2:35 AM, J=C3=BCrgen Sch=C3=B6nw=C3=A4lder <
j.schoenwaelder@jacobs-university.de> wrote:

> Reviewer: J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
> Review result: Has Nits
>
> Disclaimer: I have not much clue about MPLS LSP PWs and hence I am
> reading this from a perspective of a clueless outsider.
>
> Section 1.2 is not really about terminology but instead it basically
> expands acronyms. The section does not define any terms or does it
> make it clear where terms are defined. A reader who does not know
> T-PE
> will not be pointed to a document that defines 'Terminating Provider
> Edge Node of MS-PW'. I usally find terminology sections more useful
> if
> they say where definitions of terms get be found.
>
> Section 3: s/the the/the/
>
> Section 4: What is the 'Version' field in the message format?
>
> Section 4: There is an 8-bit field marked U C Flags and I _assume_
> the
> U and C bits are the 'first' two bits and the 'remaining bits are the
> flags managed by IANA. Perhaps make this clearer, e.g.:
>
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |  Last Received Seq Number     | Message Type  |U|C|   Flags   |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Or alternatively simply name the entire 8-bit flags field like you do
> in the text where you refer to Message Flags and then explain in the
> text under the 'Message Flags' that the first two bits have a fixed
> meaning.
>
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |  Last Received Seq Number     | Message Type  | Message Flags |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> This option carries less information but then you use 'Message Flags'
> in several places and you also request an IANA registry for Message
> Flags where the U and C bit are allocated. Looking at the IANA text,
> it says 'bit position' 0 and 1. Not sure this is clear enough, you
> seem to number bits in the order 0, 1, 2, ...
>
> It turns out we have several slightly different labels further down
> in
> the document for this flags field throughout the document - this
> makes
> searching in the text difficult, please use a single consistent name
> for this message field.
>
> Section 8.2 says values 1 and 2 are defined in this document but then
> it seems value 3 is also allocated, no?
>
> Subsections of section 8 switches several times between decimal and
> hexadecimal numbers. Perhaps things get clearer if a single number
> system (e.g., hexadecimal) is used when talking about a specific
> registry. Numbers like 134,217,728 look somewhat confusing, 0x8000000
> seems simpler.
>
>
>

--001a113df38c091317054bc9f209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-size:12.800000190734863px">J=C3=BCrgen=
,</span><br><div><span style=3D"font-size:12.800000190734863px"><br></span>=
</div><div><span style=3D"font-size:12.800000190734863px">On behalf of the =
PALS WG, thanks for the review!</span></div><div><span style=3D"font-size:1=
2.800000190734863px"><br></span></div><div><span style=3D"font-size:12.8000=
00190734863px">Cheers,</span></div><div><span style=3D"font-size:12.8000001=
90734863px">Andy</span></div><div><span style=3D"font-size:12.8000001907348=
63px"><br></span></div></div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Tue, Mar 28, 2017 at 2:35 AM, J=C3=BCrgen Sch=C3=B6nw=C3=A4l=
der <span dir=3D"ltr">&lt;<a href=3D"mailto:j.schoenwaelder@jacobs-universi=
ty.de" target=3D"_blank">j.schoenwaelder@jacobs-university.de</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">Reviewer: J=C3=BCrgen Sch=C3=B6n=
w=C3=A4lder<br>
Review result: Has Nits<br>
<br>
Disclaimer: I have not much clue about MPLS LSP PWs and hence I am<br>
reading this from a perspective of a clueless outsider.<br>
<br>
Section 1.2 is not really about terminology but instead it basically<br>
expands acronyms. The section does not define any terms or does it<br>
make it clear where terms are defined. A reader who does not know<br>
T-PE<br>
will not be pointed to a document that defines &#39;Terminating Provider<br=
>
Edge Node of MS-PW&#39;. I usally find terminology sections more useful<br>
if<br>
they say where definitions of terms get be found.<br>
<br>
Section 3: s/the the/the/<br>
<br>
Section 4: What is the &#39;Version&#39; field in the message format?<br>
<br>
Section 4: There is an 8-bit field marked U C Flags and I _assume_<br>
the<br>
U and C bits are the &#39;first&#39; two bits and the &#39;remaining bits a=
re the<br>
flags managed by IANA. Perhaps make this clearer, e.g.:<br>
<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-<wbr>+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-<wbr>+-+-+<br>
=C2=A0 =C2=A0|=C2=A0 Last Received Seq Number=C2=A0 =C2=A0 =C2=A0| Message =
Type=C2=A0 |U|C|=C2=A0 =C2=A0Flags=C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-<wbr>+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-<wbr>+-+-+<br>
<br>
Or alternatively simply name the entire 8-bit flags field like you do<br>
in the text where you refer to Message Flags and then explain in the<br>
text under the &#39;Message Flags&#39; that the first two bits have a fixed=
<br>
meaning.<br>
<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-<wbr>+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-<wbr>+-+-+<br>
=C2=A0 =C2=A0|=C2=A0 Last Received Seq Number=C2=A0 =C2=A0 =C2=A0| Message =
Type=C2=A0 | Message Flags |<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-<wbr>+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-<wbr>+-+-+<br>
<br>
This option carries less information but then you use &#39;Message Flags&#3=
9;<br>
in several places and you also request an IANA registry for Message<br>
Flags where the U and C bit are allocated. Looking at the IANA text,<br>
it says &#39;bit position&#39; 0 and 1. Not sure this is clear enough, you<=
br>
seem to number bits in the order 0, 1, 2, ...<br>
<br>
It turns out we have several slightly different labels further down<br>
in<br>
the document for this flags field throughout the document - this<br>
makes<br>
searching in the text difficult, please use a single consistent name<br>
for this message field.<br>
<br>
Section 8.2 says values 1 and 2 are defined in this document but then<br>
it seems value 3 is also allocated, no?<br>
<br>
Subsections of section 8 switches several times between decimal and<br>
hexadecimal numbers. Perhaps things get clearer if a single number<br>
system (e.g., hexadecimal) is used when talking about a specific<br>
registry. Numbers like 134,217,728 look somewhat confusing, 0x8000000<br>
seems simpler.<br>
<br>
<br>
</blockquote></div><br></div>

--001a113df38c091317054bc9f209--


From nobody Tue Mar 28 09:01:25 2017
Return-Path: <christer.holmberg@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 1342C127871; Tue, 28 Mar 2017 09:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxvDPyQfZzPk; Tue, 28 Mar 2017 09:01:16 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3A9C1294CE; Tue, 28 Mar 2017 09:01:10 -0700 (PDT)
X-AuditID: c1b4fb3a-4d72198000003958-dd-58da88c4b64f
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by  (Symantec Mail Security) with SMTP id 9F.C2.14680.4C88AD85; Tue, 28 Mar 2017 18:01:08 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.242]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0339.000; Tue, 28 Mar 2017 18:00:52 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "cpignata@cisco.com" <cpignata@cisco.com>
CC: "draft-ietf-mmusic-dtls-sdp.all@ietf.org" <draft-ietf-mmusic-dtls-sdp.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: Review of draft-ietf-mmusic-dtls-sdp-22
Thread-Topic: Re: Review of draft-ietf-mmusic-dtls-sdp-22
Thread-Index: AdKn2P/3kP9b7RTPScO/+C/SvNdcJg==
Date: Tue, 28 Mar 2017 16:00:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4CB3298B@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7hO6RjlsRBhP7zC0+vdvBYrHj7g42 i2cb57NYTF3+mMWBxWPK742sHkuW/GQKYIrisklJzcksSy3St0vgypi79CljwUrJiimHtzA3 MHaIdDFyckgImEhMvdHA3sXIxSEksJ5R4uXiH4wQzhJGiXdHJ7B2MXJwsAlYSHT/0wZpEBHQ lTjbfpEZpIZZYCGjxPeznxhBEsJAkz4sXsoIUWQp8WfKZhYIW0+id88KJhCbRUBVYtfph2wg Nq+Ar8T6/mawOKOAmMT3U2vAbGYBcYlbT+YzQVwnILFkz3lmCFtU4uXjf6wQtpJE45InrBD1 OhILdn9ig7C1JZYtfM0MMV9Q4uTMJywTGIVnIRk7C0nLLCQts5C0LGBkWcUoWpxaXJybbmSk l1qUmVxcnJ+nl5dasokRGA0Ht/y22sF48LnjIUYBDkYlHt4HUjcjhFgTy4orcw8xSnAwK4nw fuMGCvGmJFZWpRblxxeV5qQWH2KU5mBREud12HchQkggPbEkNTs1tSC1CCbLxMEp1cC4oful z/7zn+odlosF1Ww1uM4SIlHnm7Hwb9yNxIVFuZn+Hzt+PdzmEddvxCxVzHfiloLsMYNk/7s5 rtlX9TObOne/cpQJLCtYcC8tWWRaZmPE54KkzUuX7ngpf7TKObShx8835OwmJSGXtkkH333e v8RmS/NkhswNu//PrPYW0J9tZxZn/VmJpTgj0VCLuag4EQA7DDyhggIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-Zo2-IrR9EsMYTEgDhVi497m0BU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 16:01:18 -0000

Hi Carlos,

Thanks for your review! Please see inline.

>Reviewer: Carlos Pignataro
>Review result: Has Nits
>
>This document is very comprehensive. Operational Considerations are
>adequately covered.
>
>In reviewing this document, I did find two adjacent issues that I
>thought useful to comment on:
>
>1. Clarity and Readability of Section 9
>
>I appreciate the explicit OLD/NEW details and specifics on what is
>changed on the updated RFCs. I wish more documents would do this!
>
>However, the way in which this is done is very confusing and not
>really optimizing clarity and readability. It is an operational issue
>an implementor not understanding the spec :-)
>
>The issue, in my view, is with the labels and markers. Subsections of
>Section 9.2 do not follow the semantic structure of the document.
>Instead they are included as follows:
>"
>Update to section 5:
>--------------------
>"
>Which are then followed by OLD/NEW chunks. However, these chunks:
>* include Section numbers and titles,=20
>* do not have extra indentation, and
>* include only BEGIN marker but not END marker.
>
>Like:
>
>9.2.  Update to RFC 5763
>Update to section 5:
>--------------------
>OLD TEXT:
>5.  Establishing a Secure Channel
>
>[... and then, two pages later ...]
>
>NEW TEXT:
>5.  Establishing a Secure Channel
>
>I'd suggest:
>a. Using Section 9.2.1, 9.2.2, etc. for each change.

I can put each section change in a separate section.

9.2.1 Update to section 5
9.2.2 Update to section 6.6
...

Or, do you want to have the old and new text in different sections too? Per=
sonally I would like to keep the old and new text in the same section.

>b. Use more explicit chunk demarkators

It was been suggested to use "|".=20

>c. Use beginning and ending markers.

[BEGIN]
Blah blah blah...
[END]

----------

>2. The second issue, and likely this was discussed, relates to the use
>of RFC 4572. A reference to RFC 4572 is Normative, and it is cited
>within "NEW" text (not only "OLD" text). However RFC 4572 has been
>Obsoleted by RFC 8122!
>
>This is because draft-ietf-mmusic-4572-update published as RFC 8122,
>which should be updated.=20

Correct. I will do that in the next version.

>But for example, why does NEW text here still points to RFC 4572?

The reason is probably that, initially draft-4572-update did not obsolete R=
FC 4572 - it simply updated it. But, later it was agreed that draft-4572-up=
date will obsolete RFC 4572, but that was not reflected in draft-dtls-sdp.

So, you are correct, the new text shall point to RFC 8122. I will fix that =
in the next version.

---------

>--->8---
>NEW TEXT:
>
>5.  Establishing a Secure Channel
>
>   The two endpoints in the exchange present their identities as part
>   of the DTLS handshake procedure using certificates. This document
>   uses certificates in the same style as described in "Connection-Oriente=
d
>   Media Transport over the Transport Layer Security (TLS) Protocol
>   in the Session Description Protocol (SDP)" [RFC4572].
> --->8---
>
> And why RFC 4572 is Normatively referenced?

I will make the reference Informative.

Thanks!

Regards,

Christer


From nobody Tue Mar 28 09:34:42 2017
Return-Path: <sandy@tislabs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2637120724; Tue, 28 Mar 2017 09:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VP3qpkn_TIXJ; Tue, 28 Mar 2017 09:34:38 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 679E2126DFB; Tue, 28 Mar 2017 09:34:35 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id C36FB28B0041; Tue, 28 Mar 2017 12:34:33 -0400 (EDT)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id 2AE6A1F8036; Tue, 28 Mar 2017 12:34:33 -0400 (EDT)
From: Sandra Murphy <sandy@tislabs.com>
X-Pgp-Agent: GPGMail
Content-Type: multipart/signed; boundary="Apple-Mail=_FC2E29DD-1191-43F4-99A0-C3D82E427BCC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: secdir review of draft-ietf-dnsop-nsec-aggressiveuse
Date: Tue, 28 Mar 2017 12:34:32 -0400
Message-Id: <F8D0F7F4-414B-44A4-B6D0-428D506D97C7@tislabs.com>
Cc: Sandra Murphy <sandy@tislabs.com>
To: secdir@ietf.org, draft-ietf-dnsop-nsec-aggressiveuse@ietf.org, dnsops-chairs@ietf.org, The IETF <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WAC70Y0PsmYFWX4FwsLZBqWR2G8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 16:34:41 -0000

--Apple-Mail=_FC2E29DD-1191-43F4-99A0-C3D82E427BCC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

This document suggests that resolvers should use NSEC/NSEC3 proof of =
non-existence for a domain name in a received query to generate a =
negative reply, rather than relying on the current spec of an exact =
match to the domain name.  Generating positive replies from wildcard =
answers is also suggested.

The motivation is improvements in latency for queriers and improvements =
in bandwidth and CPU load on recursive resolvers and validation servers.

I have no serious objections about the draft.

I am curious about my thought that an attacker might find this of =
benefit, as they can learn of non-existence in just one query, rather =
than every name in a NSEC denied range. I know zone walking is a concern =
to some, but I do not know if ease of determining non-existence is also =
a concern.

Section 7 explicitly spells out the changes to RFC4035 are explicitly =
spelled
out as to what is removed and what replaces it.  Section 5 is not so =
clearly
delineated.

The last paragraph of 5., nothing in 5.1 or 5.2, and the last paragraph =
of 5.3
use SHOUD/MUST/MAY kinds of language.  For the paragraphs that don=E2=80=99=
t - should
they?  For the paragraphs that do, is this additional behavior or a
replacement for existing spec (i.e. like the section 7 update to =
RFC4035).
If a replacement, a replacement of what?  If not, where do the new =
paragraphs
fit?

The following is a sequential set of comments, not in importance order.

page 3

  This document updates RFC 4035 to allow recursive resolvers to use
  NSEC/NSEC3 resource records to synthesize negative answers from the
  information they have in the cache.

re: recursive resolvers - is the technique not applicable to stub =
resolvers?
(I do see references to stub resolver caches in a web search, but you =
can=E2=80=99t
trust the web.)

 [RFC8020], and [I-D.vixie-dnsext-resimprove] proposes first steps to
  using NXDOMAIN information for more effective caching.  This takes
  this technique further.

Unless rfc8020 and the vixie draft are the same thing (don=E2=80=99t =
think so),
should be =E2=80=9Cpropose=E2=80=9D.


Too many uses of =E2=80=9Cthis=E2=80=9D in that last sentence - I =
presume you mean
  This draft takes those previous techniques further.


page 4

  If a validating resolver receives a query for cat.example.com, it
  contacts its resolver (which may be itself)

Maybe

  If a validating resolver receives a query for cat.example.com, it
  contacts its recursive resolver (which may be itself)

About:

  and also has
  privacy implications (e.g: typos leak out further than necessary).

Does it also make certain explorations easier, where someone can find =
out a range
that does not exist by doing just one query rather than query every name =
in the
range?  Or is that sort of exploration already prevented by other =
techniques?

  If a query is received for leek.example.org, it contacts its resolver
  (which may be itself)

I suggest =E2=80=9Cthe resolver contacts its <recursive> resolver=E2=80=9D=
 - the query is not
doing the contacting.


page 6

section 5.1 and 5.2 say =E2=80=9Cresolver can immediately return=E2=80=9D =
- is this meant
to specify new behavior, should they have SHOULD/MAY/MUST kinds of =
words?

page 7

  Section 5 of [RFC2308] states that the maximum number of negative
  cache TTL value is 3 hours (10800).

I don=E2=80=99t find a maximum in RFC2308.  I do find:
                   Values of one to three hours have been found to work =
well
  and would make sensible a default.
Did I miss something?


=E2=80=9Cthe maximum number of negative cache TTL value is=E2=80=9D - a =
bit twisty.  Did you
mean something like:

 Section 5 of [RFC2308] states that the maximum negative cache TTL value =
is=E2=80=9D

otherwise, I=E2=80=99d think =E2=80=9Cnumber of =E2=80=A6 values=E2=80=9D,=
 but even so I don=E2=80=99t think there are
multiple values here. Are there?

page 9

<truly nitty>

The text says

  Thanks to Mark Andrews for providing the helpful notes for
  implementors provided in Appendix B.

  The authors would like to specifically thank
  =E2=80=A6
  Mark Andrews also provided the
  helpful notes for implementors (https://www.ietf.org/mail-
  archive/web/dnsop/current/msg18332.html) which we made into
  Appendix B.

Perhaps you intended to thank him twice?  No problem, just wondering.

=E2=80=94Sandy







--Apple-Mail=_FC2E29DD-1191-43F4-99A0-C3D82E427BCC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJY2pCZAAoJEHplpQeet0IZo3gP/3t/CE2rDgrsON3Amp1fM9w8
0nbnNufy6WSlNKLDy7RSnM9Ej4sThhW15mJxQ5KJSypv3lkxuZ8/4eGrOGwUQswi
c/IsSjaRUQhuvJ6UTK7KT/s2RH6rfaBLWFCPrx6H7Xmm3UZhWcNOV1WPR+omCP5f
n7qSCmNIGKFWEXSM1Db5Ty6SUbE/sk6M4mVQHs6q0eNxPp8xFfneN9OoVDIyPcUO
S4Ql4UE/fV+uiRHIdhgfjf8GX9uQ0JkTZnBoZpAJM7/ByLqs3Z/TPZhKNwemv0D/
/LD5SyilX2M7twpcbIUx/dOKss3oli0DtfRaGCdfb6MmTt01m+2VmAWgbHEJKHTO
UbCJ/nLkFpbvMWLVzkW6X38Y3qNlKLtPxmQT9eVku5dqo+xQLTCQoWopI+bx4DRA
fgB/+NKX/uQjMrXa19ZXWjQjLKY5Mj/HD4dYCD4Tuvgp24DRf7dJf1q+lpDHQRo3
AxqXE9qKvJ6bHnurxsGZG6O5x5TQ4xEYwLpXe+WNSvz78fRWVbdmlh3s5+mFl97f
vozqqSxwtvRQZIZeYM24kXDGiw5jQlT2rFLH4SNXDDbu43kNveYKbsw4WXQqfVVJ
d4H6f48r2G91OdEd2MHTc0EjU1uDesGHEMUhIjxStlE7BZmFcadKTU48bxe9yrFU
QF/fKyHRoAMMSynlqs4K
=6ryT
-----END PGP SIGNATURE-----

--Apple-Mail=_FC2E29DD-1191-43F4-99A0-C3D82E427BCC--


From nobody Tue Mar 28 10:39:26 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36567129687 for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 10:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level: 
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OMUq2enoKV6p for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 10:39:23 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E4921293FC for <ietf@ietf.org>; Tue, 28 Mar 2017 10:39:23 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id C26CF1406B1A; Tue, 28 Mar 2017 10:39:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=fHW5IjlEurhM3q 5xu5QLqEKATQc=; b=WrFzkv0i3jWSSKI72DDldR+mT4HFiEHs0/WLEU/cNhU9zq itcKXPq2a0HC+yxKrrtvZDL3IvsXUc/hytJu1nyx8e7/bzKusyaXCBiAYXpC4Wib pLe/VVzzwWYHdzR+UB3T3/Rq7MpLQeHsnhoj9dfygX8jHBv3IAaAuyEBZI/f8=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 86C0A1406B0A; Tue, 28 Mar 2017 10:39:20 -0700 (PDT)
Date: Tue, 28 Mar 2017 12:39:18 -0500
From: Nico Williams <nico@cryptonector.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: ietf@ietf.org
Subject: Re: Predictable Internet Time
Message-ID: <20170328173916.GE7490@localhost>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <504e2cea0d1668c31486b05fec0a967a4446aefe@webmail.weijax.net> <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <alpine.DEB.2.11.1701031348430.7102@grey.csi.cam.ac.uk> <f94415b6-d9f7-0a03-cf5b-ce39c109aa71@isi.edu> <f9429571-b9d5-75d4-9b46-b877a189a7bf@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f9429571-b9d5-75d4-9b46-b877a189a7bf@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2NmVJ46_QE9TxG-FPtmzI2oA7ag>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 17:39:25 -0000

On Tue, Jan 03, 2017 at 06:35:03PM +0000, Stewart Bryant wrote:
> Yes, the system should use a leap-second-free constant-duration-seconds time
> for everything. It is only humans that need the variable jumpy version of
> time presented to them, and that is a UI issue.

I don't think that's quite right.

Unix time is canonically a count of seconds since an epoch and admits no
leap seconds.  A conversion of Unix time to adjusted (i.e., with leap
seconds added) time since the same epoch would be nice, as well as:

 - conversion from either to broken down time
    - with seconds count up to 60 when converting from seconds-with-leaps
 - formatting of dates from either as well as from broken down time
    - but when converting from seconds-with-leaps the formatted string
      can show seconds-in-minute values of 60
    - whereas when converting from Unix seconds the formatted string can
      never show seconds-in-minute values of 60
 - parsing to broken down time and to seconds-since-epoch types
    - ignoring leap seconds when converting to Unix time
    - correctly accounting for all leap seconds prior to that time when
      converting to seconds-with-leaps-since-epoch

It's all about data typing.  In POSIX C API terms, we need new functions
to deal with seconds-with-leaps-since-epoch, and obviously a lot of
prayer because there's no way in C to distinguish one integer type from
the other (well, the new type could be wrapped in a struct..).

We will have to deal with multiple kinds of time as long as different
applications/users need different definitions of time.  Astronomers may
need corrected time, while bankers may want to ignore leap seconds --
all on the same systems (same OSes, same code libraries).

Functionally this is about data typing -- preferably strong data typing.

Smearing is a third time representation that also needs conversion to
the other types (more opportunity for bugs!); it leaves a bad taste.  It
may work for some apps though, but all nodes had better smear in exactly
the same way -- within your tolerances -- if your app depends on time
for synchronization.

Nico
-- 


From nobody Tue Mar 28 10:48:54 2017
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 50CDB126B72 for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 10:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xOP6HWbvDvZh for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 10:48:50 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5E9C1293F8 for <ietf@ietf.org>; Tue, 28 Mar 2017 10:48:47 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v2SHlUOv012884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Mar 2017 10:47:30 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <9F0F8841-BC1D-4C27-83EF-8F93F33FB021@puck.nether.net> <CAMm+Lwh5JMn+JxPB3Q3RKpeibckVSB2Fqm_RajcnU28OAx=jOw@mail.gmail.com> <1483474918.1346083.836313393.2699EBD5@webmail.messagingengine.com> <CAMm+LwjJDyCv2mBG8ob-njDj-4m5tr7jP6XAiEn1ME5NCYcpiQ@mail.gmail.com> <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu> <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu> <4079C051-C0C1-4220-8F0A-39F1FF0EDEF3@frobbit.se>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Tony Finch <dot@dotat.at>, IETF Discussion Mailing List <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu>
Date: Tue, 28 Mar 2017 10:47:30 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <4079C051-C0C1-4220-8F0A-39F1FF0EDEF3@frobbit.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Xx0Y2APriXEACFv4AZODg9xfr9U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 17:48:52 -0000

Hi, Patrik,


On 3/27/2017 11:37 PM, Patrik Fältström wrote:
> Joe,
>
> I have read your I-D and like it! Let me start there :-)
>
> What I think is not clear enough is the problem with POSIX, and it should be more clear in some place, maybe section 6.1, that POSIX definition which is in use in quite a number of systems do not handle leap second very well. Too many do believe the time_t definitions include the number of seconds since epoch when in reality it does not (as you note in the definitions).

I can make that more clear, but AFAICT POSIX time is *defined* as
seconds since the Unix epoch *not counting* leap seconds at all.

> One could even question whether it is Continuous as two seconds will have the same number since epoch around the addition of a leap second 
It is Continuous by definition.

When UTC adds a leap second, nothing different happens to POSIX time.

...
> There are some people that have suggested a change, for example <http://www.cl.cam.ac.uk/~mgk25/time/c/> but I have not seen any movement. Maybe you know more than me on this?
AFAICT, that's just attempting to redefine the <time.c> interface as
returning UTC rather than POSIX time.

Which works *IF* your machine has access to updated leap-second
information, e.g., via NTP.

Joe

> On 27 Mar 2017, at 21:34, Joe Touch wrote:
>
>> Hi, all,
>>
>> I've submitted the time frame discussion intended to resolve this issue, which also recently arouse on another mailing list. Further discussion on this draft will occur on the ART mailing list (art@ietf.org).
>>
>> Joe
>>
>> -----------
>>
>> A new version of I-D, draft-touch-time-01.txt
>> has been successfully submitted by Joe Touch and posted to the IETF repository.
>>
>> Name:		draft-touch-time
>> Revision:	01
>> Title:		Resolving Multiple Time Scales in the Internet
>> Document date:	2017-03-27
>> Group:		Individual Submission
>> Pages:		17
>> URL:            https://www.ietf.org/internet-drafts/draft-touch-time-01.txt Status:         https://datatracker.ietf.org/doc/draft-touch-time/
>> Htmlized:       https://tools.ietf.org/html/draft-touch-time-01 Htmlized:       https://datatracker.ietf.org/doc/html/draft-touch-time-01 Diff:           https://www.ietf.org/rfcdiff?url2=draft-touch-time-01
>>
>> Abstract:
>>    Internet systems use a variety of time scales, which can complicate   time comparisons and calculations. This document explains these   various ways of indicating time and explains how they can be used   together safely. This document is intended as a companion to   Internet time as discussed in RFC 3339.


From nobody Tue Mar 28 12:10:01 2017
Return-Path: <michael.breuer@ilsf.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1BF129490 for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 12:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vTMb03l7-rhG for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 12:09:51 -0700 (PDT)
Received: from vwp3261.webpack.hosteurope.de (vwp3261.webpack.hosteurope.de [IPv6:2a01:488:42:1000:57e6:2d0c::]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A796E129495 for <ietf@ietf.org>; Tue, 28 Mar 2017 12:09:51 -0700 (PDT)
Received: from t2001067c0370012830f8cda7ec9a9039.v6.meeting.ietf.org ([2001:67c:370:128:30f8:cda7:ec9a:9039] helo=boell.ac.ilsf.de); authenticated by vwp3261.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1cswV1-0001YU-Vp; Tue, 28 Mar 2017 21:09:48 +0200
Subject: Re: Predictable Internet Time
To: Joe Touch <touch@isi.edu>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <9F0F8841-BC1D-4C27-83EF-8F93F33FB021@puck.nether.net> <CAMm+Lwh5JMn+JxPB3Q3RKpeibckVSB2Fqm_RajcnU28OAx=jOw@mail.gmail.com> <1483474918.1346083.836313393.2699EBD5@webmail.messagingengine.com> <CAMm+LwjJDyCv2mBG8ob-njDj-4m5tr7jP6XAiEn1ME5NCYcpiQ@mail.gmail.com> <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu> <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu> <4079C051-C0C1-4220-8F0A-39F1FF0EDEF3@frobbit.se> <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
From: Michael Breuer <michael.breuer@ilsf.de>
Openpgp: id=93EDD6E843159956FCA31698DB0B3B15EB351B72
X-Enigmail-Draft-Status: N1010
Message-ID: <0538a417-ec02-e6c6-ff50-5b34b73a6f64@ilsf.de>
Date: Tue, 28 Mar 2017 21:09:44 +0200
User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-bounce-key: webpack.hosteurope.de; michael.breuer@ilsf.de; 1490728191; 8dd56bba; 
X-HE-SMSGID: 1cswV1-0001YU-Vp
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M8zpuHnSI1c4qYU_QRiqhYWh-xg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 19:10:00 -0000

Hej Joe

On 03/28/17 19:47, Joe Touch wrote:
> Hi, Patrik,
> 
> 
> On 3/27/2017 11:37 PM, Patrik Fältström wrote:
>> Joe,
>> 
>> I have read your I-D and like it! Let me start there :-)
>> 
>> What I think is not clear enough is the problem with POSIX, and it
>> should be more clear in some place, maybe section 6.1, that POSIX
>> definition which is in use in quite a number of systems do not
>> handle leap second very well. Too many do believe the time_t
>> definitions include the number of seconds since epoch when in
>> reality it does not (as you note in the definitions).
> 
> I can make that more clear, but AFAICT POSIX time is *defined* as 
> seconds since the Unix epoch *not counting* leap seconds at all.
> 
>> One could even question whether it is Continuous as two seconds
>> will have the same number since epoch around the addition of a leap
>> second
> It is Continuous by definition.
> 
> When UTC adds a leap second, nothing different happens to POSIX
> time.
> 

That's a quite complex topic to find precise wording. If the last
statement would be right, wouldn't this be a contradiction to your
earlier statement, POSIX time be defined *not counting* leap seconds?
AFAIK POSIX time is continuous and not counting leap seconds. So when
UTC adds a leap second, something quite different happens to POSIX time.
It will change the leap-second-offset between UTC and Unix time.

To my opinion, any time system utilising leap seconds isn't continuos at
all. There are continuous time systems like TAI or GPS system time (or
any other satellite navigation system time) and POSIX time, which (by
design) shift away from UTC over time.

Michael

> ...
>> There are some people that have suggested a change, for example
>> <http://www.cl.cam.ac.uk/~mgk25/time/c/> but I have not seen any
>> movement. Maybe you know more than me on this?
> AFAICT, that's just attempting to redefine the <time.c> interface as 
> returning UTC rather than POSIX time.
> 
> Which works *IF* your machine has access to updated leap-second 
> information, e.g., via NTP.
> 
> Joe
> 
>> On 27 Mar 2017, at 21:34, Joe Touch wrote:
>> 
>>> Hi, all,
>>> 
>>> I've submitted the time frame discussion intended to resolve this
>>> issue, which also recently arouse on another mailing list.
>>> Further discussion on this draft will occur on the ART mailing
>>> list (art@ietf.org).
>>> 
>>> Joe
>>> 
>>> -----------
>>> 
>>> A new version of I-D, draft-touch-time-01.txt has been
>>> successfully submitted by Joe Touch and posted to the IETF
>>> repository.
>>> 
>>> Name:		draft-touch-time Revision:	01 Title:		Resolving Multiple
>>> Time Scales in the Internet Document date:	2017-03-27 Group:
>>> Individual Submission Pages:		17 URL:
>>> https://www.ietf.org/internet-drafts/draft-touch-time-01.txt
>>> Status:
>>> https://datatracker.ietf.org/doc/draft-touch-time/ Htmlized:
>>> https://tools.ietf.org/html/draft-touch-time-01 Htmlized:
>>> https://datatracker.ietf.org/doc/html/draft-touch-time-01 Diff:
>>> https://www.ietf.org/rfcdiff?url2=draft-touch-time-01
>>> 
>>> Abstract: Internet systems use a variety of time scales, which
>>> can complicate   time comparisons and calculations. This document
>>> explains these   various ways of indicating time and explains how
>>> they can be used   together safely. This document is intended as
>>> a companion to   Internet time as discussed in RFC 3339.
> 
> 


From nobody Tue Mar 28 12:17:02 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DACD21297ED for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 12:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level: 
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNJnFe7-vxOu for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 12:16:59 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A82F129686 for <ietf@ietf.org>; Tue, 28 Mar 2017 12:16:59 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id 952BA1406B20; Tue, 28 Mar 2017 12:16:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=BFrujY9Kk3yxCv+4nIifUeBNhE4=; b=X3inlM0bLTF 6DQzQ5apjkphi7rCw3Sj8YwWUetMdpG57R30aXpoelxVoBzS4XFIf46bsoD5Mqe+ HBHj+6PtjDcJRPhP4WjoSAF7l4gfVg90ZJ+S+SOG31yeH404LAQHE0bxQSGinByL 6S0WigmC2dJH6apSm8KPacL0nGKS5fV4=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 49D9E1406B1F; Tue, 28 Mar 2017 12:16:58 -0700 (PDT)
Date: Tue, 28 Mar 2017 14:16:55 -0500
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Predictable Internet Time
Message-ID: <20170328191654.GH7490@localhost>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JipZ14ngeLmfXZmqiqGn5bGgDZ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 19:17:01 -0000

On Sat, Dec 31, 2016 at 04:32:20PM -0500, Phillip Hallam-Baker wrote:
> Well the astronomers are at it again. They are messing about with time
> which is a terrible idea. Specifically they are adding another leap sec=
ond.
>=20
> [...]
>=20
> So to remove the confusion entirely, while preventing the need for a
> discontinuous adjustment of the drift between UTC and TAI, I propose th=
e
> Predictable Internet Time (PIT) as follows.

We have two kinds of time today: UTC on the one hand (has leaps) and
TAI (and POSIX) on the other (has no leaps).  Converting between the two
requires a leap second history.

Leap seconds are not that predictable.  Significant seismic events
(e.g., the 2004 earthquake and tsunami) can measurably alter the speed
of Earth's rotation on its axis.

You propose a new kind of time that lies between UTC and TAI.
Conversions between this new type and TAI would still need adjustment as
leap second rates change, while conversions to UTC would still need a
leap second history _and_ said adjustments.

I imagine many would code-inject PIT at run-time as being POSIX time.

> Nor is changing the definition of UTC to effect simultaneous change a
> feasible solution because to do so would be to demand the astronomers
> accept a diminution in their own prestige.

Or a new time "data type" just for them, but leaving UTC =3D TAI + 36
after a certain date because UTC has been used widely for non-astronomy-
related purposes.

> With a suitable definition, PIT could create a condition in which it wo=
uld
> only take a decision by one major government to force a change on the
> astronomers. The commercial advantages of PIT over UTC are obvious - fe=
wer
> things are going to break for no good reason. That is an argument that
> every politician is willing to listen to.

Do we have this much influence?  If we do, why not just... lobby for
fixing UTC and creating an TAC (tempt astronomique coordin=E9) to serve,
for astronomers, the function that UTC serves today.

> While a variance of a second or three between New York and London might=
 be
> inconvenient, [...]

For some apps that could be terrible.  Now developers will have to think
about 200% more time conversions.  Not exactly thrilling.

Nico
--=20


From nobody Tue Mar 28 12:19:22 2017
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 80EC612955E for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 12:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id clOa-YFfARkS for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 12:19:19 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3D7D129486 for <ietf@ietf.org>; Tue, 28 Mar 2017 12:19:18 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v2SJIbD6014358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Mar 2017 12:18:38 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: Michael Breuer <michael.breuer@ilsf.de>, =?UTF-8?Q?Patrik_F=c3=a4ltstr?= =?UTF-8?B?w7Zt?= <paf@frobbit.se>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <9F0F8841-BC1D-4C27-83EF-8F93F33FB021@puck.nether.net> <CAMm+Lwh5JMn+JxPB3Q3RKpeibckVSB2Fqm_RajcnU28OAx=jOw@mail.gmail.com> <1483474918.1346083.836313393.2699EBD5@webmail.messagingengine.com> <CAMm+LwjJDyCv2mBG8ob-njDj-4m5tr7jP6XAiEn1ME5NCYcpiQ@mail.gmail.com> <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu> <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu> <4079C051-C0C1-4220-8F0A-39F1FF0EDEF3@frobbit.se> <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu> <0538a417-ec02-e6c6-ff50-5b34b73a6f64@ilsf.de>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <9567b902-396f-f9a6-4853-b1f25844bb17@isi.edu>
Date: Tue, 28 Mar 2017 12:18:37 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <0538a417-ec02-e6c6-ff50-5b34b73a6f64@ilsf.de>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kn8KRxbFwh06ZsZI0gqe_O78M3E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 19:19:21 -0000

On 3/28/2017 12:09 PM, Michael Breuer wrote:
> ...
>> When UTC adds a leap second, nothing different happens to POSIX
>> time.
>>
> That's a quite complex topic to find precise wording. If the last
> statement would be right, wouldn't this be a contradiction to your
> earlier statement, POSIX time be defined *not counting* leap seconds?

POSIX ignores leap seconds - whether added (typical) or removed (if that
ever happens).

> AFAIK POSIX time is continuous and not counting leap seconds. So when
> UTC adds a leap second, something quite different happens to POSIX time.
POSIX doesn't know or care - it just keeps ticking.

> It will change the leap-second-offset between UTC and Unix time.

That happens because of something UTC did, not something POSIX did.

> To my opinion, any time system utilising leap seconds isn't continuos at
> all. There are continuous time systems like TAI or GPS system time (or
> any other satellite navigation system time) 
GPS reports TAI+19s, but at least one other satellite system jumps with
leaps (GLONASS).

> and POSIX time, which (by
> design) shift away from UTC over time.
TAI does too.

TAI and POSIX also drift away from each other in unpredictable ways
because TAI uses SI seconds and POSIX has no precise definition (it
appears to assume a second derived from a mean solar day, but it isn't
precisly spec'd).

Joe


From nobody Tue Mar 28 13:24:12 2017
Return-Path: <dot@dotat.at>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5996129A16 for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 13:24:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYNoodnmlPPn for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 13:24:08 -0700 (PDT)
Received: from ppsw-43.csi.cam.ac.uk (ppsw-43.csi.cam.ac.uk [131.111.8.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8639A12955E for <ietf@ietf.org>; Tue, 28 Mar 2017 13:24:08 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:49572) by ppsw-43.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.139]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1csxer-0003K8-ox (Exim 4.89) (return-path <dot@dotat.at>); Tue, 28 Mar 2017 21:24:01 +0100
Date: Tue, 28 Mar 2017 21:24:01 +0100
From: Tony Finch <dot@dotat.at>
To: Joe Touch <touch@isi.edu>
cc: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>,  Phillip Hallam-Baker <phill@hallambaker.com>,  IETF Discussion Mailing List <ietf@ietf.org>,  Jared Mauch <jared@puck.nether.net>
Subject: Re: Predictable Internet Time
In-Reply-To: <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu>
Message-ID: <alpine.DEB.2.11.1703282114160.2180@grey.csi.cam.ac.uk>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <9F0F8841-BC1D-4C27-83EF-8F93F33FB021@puck.nether.net> <CAMm+Lwh5JMn+JxPB3Q3RKpeibckVSB2Fqm_RajcnU28OAx=jOw@mail.gmail.com> <1483474918.1346083.836313393.2699EBD5@webmail.messagingengine.com> <CAMm+LwjJDyCv2mBG8ob-njDj-4m5tr7jP6XAiEn1ME5NCYcpiQ@mail.gmail.com> <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu> <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu> <4079C051-C0C1-4220-8F0A-39F1FF0EDEF3@frobbit.se> <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NXMxoeHrevNO_oqjD7iehUFi1dg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 20:24:11 -0000

Joe Touch <touch@isi.edu> wrote:
>
> When UTC adds a leap second, nothing different happens to POSIX time.

Clearly not. Either it jumps backwards at the start of the leap second, or
at the end of the leap second, or it stops for a second, or it runs slow
for some  period of time in a controlled manner (e.g. leap smear) or an
uncontrolled manner (NTP swinging around in a wild effort to resync).

The POSIX formula that specifies the translation from UTC to time_t
implies that it jumps back at the end of the leap second.
http://pubs.opengroup.org/onlinepubs/9699919799.2016edition/basedefs/V1_chap04.html#tag_04_16

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
South German Bight, Humber, Thames: Southwesterly 4 or 5, increasing 6 at
times. Slight or moderate. Occasional rain, fog patches. Moderate or good,
occasionally very poor.


From nobody Tue Mar 28 13:28:54 2017
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 B63B412704A for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 13:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zlBZLQJ0HxHn for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 13:28:51 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21D4B1275AB for <ietf@ietf.org>; Tue, 28 Mar 2017 13:28:51 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2SKS3xB014000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Mar 2017 13:28:03 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: Tony Finch <dot@dotat.at>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <9F0F8841-BC1D-4C27-83EF-8F93F33FB021@puck.nether.net> <CAMm+Lwh5JMn+JxPB3Q3RKpeibckVSB2Fqm_RajcnU28OAx=jOw@mail.gmail.com> <1483474918.1346083.836313393.2699EBD5@webmail.messagingengine.com> <CAMm+LwjJDyCv2mBG8ob-njDj-4m5tr7jP6XAiEn1ME5NCYcpiQ@mail.gmail.com> <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu> <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu> <4079C051-C0C1-4220-8F0A-39F1FF0EDEF3@frobbit.se> <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu> <alpine.DEB.2.11.1703282114160.2180@grey.csi.cam.ac.uk>
Cc: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <b3618f1c-5eb5-0875-7c5d-4a0bb70eb25d@isi.edu>
Date: Tue, 28 Mar 2017 13:28:03 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.11.1703282114160.2180@grey.csi.cam.ac.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G49ix5_T4uYVrlHGWahOPYZKcGs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 20:28:53 -0000

On 3/28/2017 1:24 PM, Tony Finch wrote:
> Joe Touch <touch@isi.edu> wrote:
>> When UTC adds a leap second, nothing different happens to POSIX time.
> Clearly not. Either it jumps backwards at the start of the leap second, or
> at the end of the leap second, or it stops for a second, or it runs slow
> for some  period of time in a controlled manner (e.g. leap smear) or an
> uncontrolled manner (NTP swinging around in a wild effort to resync).

POSIX time just keeps ticking.

It is only in relation to UTC that you would notice anything. And it
isn't POSIX that is jumping - it is UTC.

> The POSIX formula that specifies the translation from UTC to time_t
> implies that it jumps back at the end of the leap second.
> http://pubs.opengroup.org/onlinepubs/9699919799.2016edition/basedefs/V1_chap04.html#tag_04_16
That equation is clearly introduced as "A value that approximates..."

Leap seconds and the difference between 86400 seconds/day and SI
definitions are where the approximation errs.

Joe


From nobody Tue Mar 28 14:37:18 2017
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 00C7E129631 for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 14:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ECAouLWGxks for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 14:37:15 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43FAE129634 for <ietf@ietf.org>; Tue, 28 Mar 2017 14:37:14 -0700 (PDT)
Received: from [128.9.184.151] ([128.9.184.151]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v2SLatXJ027483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Mar 2017 14:36:55 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: Nico Williams <nico@cryptonector.com>, Stewart Bryant <stewart.bryant@gmail.com>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <504e2cea0d1668c31486b05fec0a967a4446aefe@webmail.weijax.net> <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <alpine.DEB.2.11.1701031348430.7102@grey.csi.cam.ac.uk> <f94415b6-d9f7-0a03-cf5b-ce39c109aa71@isi.edu> <f9429571-b9d5-75d4-9b46-b877a189a7bf@gmail.com> <20170328173916.GE7490@localhost>
Cc: ietf@ietf.org
From: Joe Touch <touch@isi.edu>
Message-ID: <5837a781-16b7-7366-e9b9-2934aa13b4c0@isi.edu>
Date: Tue, 28 Mar 2017 14:36:54 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170328173916.GE7490@localhost>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: v2SLatXJ027483
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9gUD34axMmtl1sHyfNrIys7B3IM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Mar 2017 21:37:17 -0000

Hi, all,

Please take this discussion to ART (art@ietf.org)

Joe


On 3/28/2017 10:39 AM, Nico Williams wrote:
> On Tue, Jan 03, 2017 at 06:35:03PM +0000, Stewart Bryant wrote:
>> Yes, the system should use a leap-second-free constant-duration-seconds time
>> for everything. It is only humans that need the variable jumpy version of
>> time presented to them, and that is a UI issue.
> I don't think that's quite right.
>
> Unix time is canonically a count of seconds since an epoch and admits no
> leap seconds.  A conversion of Unix time to adjusted (i.e., with leap
> seconds added) time since the same epoch would be nice, as well as:
>
>  - conversion from either to broken down time
>     - with seconds count up to 60 when converting from seconds-with-leaps
>  - formatting of dates from either as well as from broken down time
>     - but when converting from seconds-with-leaps the formatted string
>       can show seconds-in-minute values of 60
>     - whereas when converting from Unix seconds the formatted string can
>       never show seconds-in-minute values of 60
>  - parsing to broken down time and to seconds-since-epoch types
>     - ignoring leap seconds when converting to Unix time
>     - correctly accounting for all leap seconds prior to that time when
>       converting to seconds-with-leaps-since-epoch
>
> It's all about data typing.  In POSIX C API terms, we need new functions
> to deal with seconds-with-leaps-since-epoch, and obviously a lot of
> prayer because there's no way in C to distinguish one integer type from
> the other (well, the new type could be wrapped in a struct..).
>
> We will have to deal with multiple kinds of time as long as different
> applications/users need different definitions of time.  Astronomers may
> need corrected time, while bankers may want to ignore leap seconds --
> all on the same systems (same OSes, same code libraries).
>
> Functionally this is about data typing -- preferably strong data typing.
>
> Smearing is a third time representation that also needs conversion to
> the other types (more opportunity for bugs!); it leaves a bad taste.  It
> may work for some apps though, but all nodes had better smear in exactly
> the same way -- within your tolerances -- if your app depends on time
> for synchronization.
>
> Nico


From nobody Tue Mar 28 22:52:25 2017
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 E2F80127241 for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 22:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UKYNP0LXSZ-e for <ietf@ietfa.amsl.com>; Tue, 28 Mar 2017 22:52:19 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F172129666 for <ietf@ietf.org>; Tue, 28 Mar 2017 22:52:19 -0700 (PDT)
Received: from [77.72.226.187] (unknown [IPv6:2a01:3f0:1:0:40c0:f25d:2a01:265]) by mail.frobbit.se (Postfix) with ESMTPSA id 106A821903; Wed, 29 Mar 2017 07:52:16 +0200 (CEST)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Joe Touch" <touch@isi.edu>
Cc: "Phillip Hallam-Baker" <phill@hallambaker.com>, "Tony Finch" <dot@dotat.at>, "IETF Discussion Mailing List" <ietf@ietf.org>, "Jared Mauch" <jared@puck.nether.net>
Subject: Re: Predictable Internet Time
Date: Wed, 29 Mar 2017 07:52:15 +0200
Message-ID: <A4FF8930-F644-496A-8AEE-F3A8504039E8@frobbit.se>
In-Reply-To: <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <9F0F8841-BC1D-4C27-83EF-8F93F33FB021@puck.nether.net> <CAMm+Lwh5JMn+JxPB3Q3RKpeibckVSB2Fqm_RajcnU28OAx=jOw@mail.gmail.com> <1483474918.1346083.836313393.2699EBD5@webmail.messagingengine.com> <CAMm+LwjJDyCv2mBG8ob-njDj-4m5tr7jP6XAiEn1ME5NCYcpiQ@mail.gmail.com> <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu> <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu> <4079C051-C0C1-4220-8F0A-39F1FF0EDEF3@frobbit.se> <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_06216BC6-9D1F-4127-BB5B-A375C618C7E9_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6080)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nNTuiD1di9rjlH_tejcpdcsvxK4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 05:52:22 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_06216BC6-9D1F-4127-BB5B-A375C618C7E9_=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 28 Mar 2017, at 19:47, Joe Touch wrote:

> On 3/27/2017 11:37 PM, Patrik F=C3=A4ltstr=C3=B6m wrote:
>> Joe,
>>
>> I have read your I-D and like it! Let me start there :-)
>>
>> What I think is not clear enough is the problem with POSIX, and it sho=
uld be more clear in some place, maybe section 6.1, that POSIX definition=
 which is in use in quite a number of systems do not handle leap second v=
ery well. Too many do believe the time_t definitions include the number o=
f seconds since epoch when in reality it does not (as you note in the def=
initions).
>
> I can make that more clear, but AFAICT POSIX time is *defined* as secon=
ds since the Unix epoch *not counting* leap seconds at all.

Well, one of the problems is that the specification of POSIX time is a bi=
t unclear.

>> One could even question whether it is Continuous as two seconds will h=
ave the same number since epoch around the addition of a leap second
>
> > It is Continuous by definition.
>
> When UTC adds a leap second, nothing different happens to POSIX time.

No, that is not correct if you look at the day when the leap second is ad=
ded.

POSIX is number of (days * 86400) plus seconds inside the current day. Th=
is implies if there is a day with a leap second there will be 86401 secon=
ds which also will be the first second the following day.

>> There are some people that have suggested a change, for example <http:=
//www.cl.cam.ac.uk/~mgk25/time/c/> but I have not seen any movement. Mayb=
e you know more than me on this?
>
> AFAICT, that's just attempting to redefine the <time.c> interface as re=
turning UTC rather than POSIX time.

The UNIX time_t struct do deliver UTC, including leap seconds, but the nu=
mber of seconds from epoch is wrong regarding leap seconds. Includes one =
leap second within the day of the leap second being added and without lea=
p seconds otherwise.

> Which works *IF* your machine has access to updated leap-second informa=
tion, e.g., via NTP.

Correct, if one have access to leap seconds, one could adjust the number =
of seconds and that could happen already today as POSIX definition is a b=
it unclear on this. But people have not implemented it. So instead for ex=
ample Google smear the leap second over the day so that there is not bump=
 in the road, and they run NTP servers that do give back this smeared tim=
e that differs from UTC.

All just because a. unclear information from POSIX and b. bad implementat=
ions in *ux.

   paf

--=_MailMate_06216BC6-9D1F-4127-BB5B-A375C618C7E9_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAljbS5AACgkQrMabGguI182HFQCfSaqANdkKY3ElK/A6bm200Lwo
KY0AoJlirvqOc43TEY99VDAwSy4JXbwo
=EZCt
-----END PGP SIGNATURE-----

--=_MailMate_06216BC6-9D1F-4127-BB5B-A375C618C7E9_=--


From nobody Wed Mar 29 04:51:16 2017
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 A24381296BC for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 04:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bs59mf6g73aP for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 04:51:13 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 238901294F4 for <ietf@ietf.org>; Wed, 29 Mar 2017 04:51:13 -0700 (PDT)
Received: from [192.168.0.158] (50-232-11-130-static.hfc.comcastbusiness.net [50.232.11.130]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2TBrH03032478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Wed, 29 Mar 2017 04:53:17 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490788398; bh=kOa0I7oB/lGztKL4hgqu34K4OX1bnnx70MKKEiJCzQo=; h=To:From:Subject:Reply-To:Date:From; b=dgRg8/FcW4ltuv3zCBGVc+rsQ7SsVCl5QFXrh5f/rHYZX/Jh06w10YIEHLb6caFqQ NEPecQIJdKwVnNQcGP9fsTS7cP+V5hYANB/MN7KjOydY8WpeExYbt6tl5jgMIZs7aW q4HILcbGP7k7oVnF1NgNggFwHst0fmyzq30nB/Mc=
To: IETF general list <ietf@ietf.org>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Getting the latest version of an RFC specification
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net>
Date: Wed, 29 Mar 2017 06:51:04 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iFY_SIUPBvSZhOMgSSJwdrP9j6w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 11:51:15 -0000

G'day.

The RFC labeling model is to assign a unique serial number to a static 
document.  A new version of a spec gets a new serial number. This basic 
model has the benefit of both simplicity and predictability.

To this we've added an overlay model, using Obsoletes/ObsoletedBy. This 
makes it dramatically easier to see that something has been obsoleted 
and to find its replacement.

However the seeing and the finding are an essentially manual process. 
One must go to the online older document, then notice the Obsoleted By 
tag and then click to follow it.

Sometimes it would be helpful for the requester to be able to say 'give 
me the latest' more easily.

So I'm wondering whether the IETF should consider adding a citation 
feature for this.

Something like:

      https://tools.ietf.org/html/rfc822/latest

would display the contents of:

      https://tools.ietf.org/html/rfc5322

by having the fetching system automatically traversing the Obsoleted By 
links in RFC 822 and then RFC 2822.

Some sort of display banner would flag this, to help the user see that 
they are getting a different version than they cited.


Thoughts?

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Mar 29 05:19:53 2017
Return-Path: <ynir.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 8E18A129463 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 05:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rux6_dZx_3YU for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 05:19:48 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DABC1294CF for <ietf@ietf.org>; Wed, 29 Mar 2017 05:19:45 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id e75so90286881itd.1 for <ietf@ietf.org>; Wed, 29 Mar 2017 05:19:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=c44dE/pAfsVuft5vuBK8ionfC3QxC+DpdBhV+gIgsXc=; b=nv/lGjNY7aeYcDqt/w/fXwVmEYDnp7SJ7xkYOCb3IKh3URMoXqVRVq7VUPq+RWyy0w bC/VWbB/rPNuyti69L9BQioB+Ke67XBCp9RDE8MtKqZ95wwFoUOmTtpe4c72oea1rXeF ZQ3f3cUsi40zmnCN5CDIBTsAJVEACUjnLtsM5Xl6zV9fHN4BxLyVh91obvpJFbpQm6Np dgZ55FS4t3yVJM4bobczDJWezvonQKQq0r5cZttfUiXrQ5mayhHmSsbTrRG+ax9gLf3N 1uToJsRZLiLj+UoUNlLk6ct65XFhHdJKOCrpVYMe8EtiK0bGH1u/RMHdpy+4awdjrg7b cMtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=c44dE/pAfsVuft5vuBK8ionfC3QxC+DpdBhV+gIgsXc=; b=YOOQAaRfggCWAn9Xu09Ksia1opq6Lw8pgHPe0HBUxuGQLPFHOiiS2AWEamLW7xvpb5 Zz1LEOvzDyxyitumTUGQxoF5qH59LZsUIEAPnF4bNNi0SOzgroPD1sLoeZLoZ8bP/Qqd ErIZNZSLn9Y648q5FPWFFpgcquCnXeSnd2KsJPjDHJpNiCF8Th8yfWIWY5MkZnEVMr6q vgVbxtu7uZccQrVZHvw31UFhQhZsDxjcECRNNrA0O1t08loTqnyjh2EJT0+5D61tLviz UhU/RtWs+/0CUcBJ/WgO0kHM+gc8rSQTODiP30hjKq5DdQ6NVvjcLqGgGgE/bOypSxC8 JT9A==
X-Gm-Message-State: AFeK/H1HvBAiZzl0YVm7lsoqe626DIghFAJG5eqT+LIzYZsOUnKmrDxg84zspDMOFpSfMw==
X-Received: by 10.36.138.129 with SMTP id v123mr434762itd.108.1490789984713; Wed, 29 Mar 2017 05:19:44 -0700 (PDT)
Received: from ?IPv6:2001:67c:1233::7964:d574:44d2:79d8? ([2001:67c:1233:0:7964:d574:44d2:79d8]) by smtp.gmail.com with ESMTPSA id g204sm3218099ita.31.2017.03.29.05.19.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 05:19:43 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <38BC1BB4-0996-4138-BEE0-58CD4F2B867B@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_86FDDE1E-2C7D-4CD0-B9AE-481446B35EC3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Getting the latest version of an RFC specification
Date: Wed, 29 Mar 2017 07:19:41 -0500
In-Reply-To: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net>
Cc: IETF general list <ietf@ietf.org>
To: dcrocker@bbiw.net
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kXZs5UtyDMweYv3JFVHNzd2YioU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 12:19:52 -0000

--Apple-Mail=_86FDDE1E-2C7D-4CD0-B9AE-481446B35EC3
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_F4A20A0A-9F87-44EB-A4B8-39870BE99A2A"


--Apple-Mail=_F4A20A0A-9F87-44EB-A4B8-39870BE99A2A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi, Dave

This is definitely doable, although I=E2=80=99d prefer that /latest =
redirect to the latest rather than display it.

I question how useful it is.  The obsoletes/obsoletedBy relationship is =
semantically overloaded. Consider the header of RFC 4306:

   Obsoleted by: 5996
   Updated by: 5282
   Request for Comments: 4306
   Obsoletes: 2407, 2408, 2409

RFC 5996 defines IKEv2, same as RFC 4306, but the three RFCs that 4306 =
obsoletes define the protocol IKEv1, a different protocol.

So what should https://tools.ietf.org/html/rfc2407/latest =
<https://tools.ietf.org/html/rfc2407/latest> return?  2407, because that =
is the latest RFC defining IKEv1, or 5996 (actually, 7296) because =
it=E2=80=99s the latest IKE?

The 822 =E2=80=94> 2822 =E2=80=94> 5322 path is one we should follow. =
I=E2=80=99m not sure the same applies to different versions of a =
protocol.

Yoav

> On 29 Mar 2017, at 6:51, Dave Crocker <dhc@dcrocker.net> wrote:
>=20
> G'day.
>=20
> The RFC labeling model is to assign a unique serial number to a static =
document.  A new version of a spec gets a new serial number. This basic =
model has the benefit of both simplicity and predictability.
>=20
> To this we've added an overlay model, using Obsoletes/ObsoletedBy. =
This makes it dramatically easier to see that something has been =
obsoleted and to find its replacement.
>=20
> However the seeing and the finding are an essentially manual process. =
One must go to the online older document, then notice the Obsoleted By =
tag and then click to follow it.
>=20
> Sometimes it would be helpful for the requester to be able to say =
'give me the latest' more easily.
>=20
> So I'm wondering whether the IETF should consider adding a citation =
feature for this.
>=20
> Something like:
>=20
>     https://tools.ietf.org/html/rfc822/latest
>=20
> would display the contents of:
>=20
>     https://tools.ietf.org/html/rfc5322
>=20
> by having the fetching system automatically traversing the Obsoleted =
By links in RFC 822 and then RFC 2822.
>=20
> Some sort of display banner would flag this, to help the user see that =
they are getting a different version than they cited.
>=20
>=20
> Thoughts?
>=20
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>=20


--Apple-Mail=_F4A20A0A-9F87-44EB-A4B8-39870BE99A2A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi, Dave<div class=3D""><br class=3D""></div><div =
class=3D"">This is definitely doable, although I=E2=80=99d prefer that =
/latest redirect to the latest rather than display it.</div><div =
class=3D""><br class=3D""></div><div class=3D"">I question how useful it =
is. &nbsp;The obsoletes/obsoletedBy relationship is semantically =
overloaded. Consider the header of RFC 4306:</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">&nbsp; &nbsp;Obsoleted =
by: 5996&nbsp;</div><div class=3D"">&nbsp; &nbsp;Updated by: =
5282</div><div class=3D"">&nbsp; &nbsp;Request for Comments: =
4306</div><div class=3D"">&nbsp; &nbsp;Obsoletes: 2407, 2408, =
2409&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">RFC =
5996 defines IKEv2, same as RFC 4306, but the three RFCs that 4306 =
obsoletes define the protocol IKEv1, a different protocol.</div><div =
class=3D""><br class=3D""></div><div class=3D"">So what should <a =
href=3D"https://tools.ietf.org/html/rfc2407/latest" =
class=3D"">https://tools.ietf.org/html/rfc2407/latest</a>&nbsp;return? =
&nbsp;2407, because that is the latest RFC defining IKEv1, or 5996 =
(actually, 7296) because it=E2=80=99s the latest IKE?</div><div =
class=3D""><br class=3D""></div><div class=3D"">The 822 =E2=80=94&gt; =
2822 =E2=80=94&gt; 5322 path is one we should follow. I=E2=80=99m not =
sure the same applies to different versions of a protocol.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Yoav</div><div =
class=3D""><br class=3D""></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 29 Mar 2017, at 6:51, Dave Crocker &lt;<a =
href=3D"mailto:dhc@dcrocker.net" class=3D"">dhc@dcrocker.net</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">G'day.<br class=3D""><br class=3D"">The RFC labeling model is =
to assign a unique serial number to a static document. &nbsp;A new =
version of a spec gets a new serial number. This basic model has the =
benefit of both simplicity and predictability.<br class=3D""><br =
class=3D"">To this we've added an overlay model, using =
Obsoletes/ObsoletedBy. This makes it dramatically easier to see that =
something has been obsoleted and to find its replacement.<br =
class=3D""><br class=3D"">However the seeing and the finding are an =
essentially manual process. One must go to the online older document, =
then notice the Obsoleted By tag and then click to follow it.<br =
class=3D""><br class=3D"">Sometimes it would be helpful for the =
requester to be able to say 'give me the latest' more easily.<br =
class=3D""><br class=3D"">So I'm wondering whether the IETF should =
consider adding a citation feature for this.<br class=3D""><br =
class=3D"">Something like:<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/rfc822/latest" =
class=3D"">https://tools.ietf.org/html/rfc822/latest</a><br class=3D""><br=
 class=3D"">would display the contents of:<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"https://tools.ietf.org/html/rfc5322" =
class=3D"">https://tools.ietf.org/html/rfc5322</a><br class=3D""><br =
class=3D"">by having the fetching system automatically traversing the =
Obsoleted By links in RFC 822 and then RFC 2822.<br class=3D""><br =
class=3D"">Some sort of display banner would flag this, to help the user =
see that they are getting a different version than they cited.<br =
class=3D""><br class=3D""><br class=3D"">Thoughts?<br class=3D""><br =
class=3D"">d/<br class=3D"">-- <br class=3D"">Dave Crocker<br =
class=3D"">Brandenburg InternetWorking<br class=3D""><a =
href=3D"http://bbiw.net" class=3D"">bbiw.net</a><br class=3D""><br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_F4A20A0A-9F87-44EB-A4B8-39870BE99A2A--

--Apple-Mail=_86FDDE1E-2C7D-4CD0-B9AE-481446B35EC3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJY26ZeAAoJELhJCxUKWMyZRuEIAIZUZWoH3yxuCncCwOsIxWZ0
5m9tVU12kJR8Orc+tCwyXktO4XqhzcAE+JTfY6b4CHJ6hx+7azEr7Ov+wOSK7PzF
Y4qAKMlU78YV7VG7pANG5pFHu4ee1SrYRpd+SDdzxQLowlTlhpwpUSi0gcn+nwpm
KHRIH6gRTh5Mxge897DlzO9tUNtth2NZApecAwtxNdn+ACQZbTAQ4yJ4hgzQO0Nc
1Tl7P1rv6ecugtgjLaj9N1ZsriupeDP4nVnmlzmdyUiYdx3RwULxfzDWJMyf6vGU
WVS1Y3QXXUkpFUpRCAj0zKA/U+V1umAF55+2iQom6HqTXwFq/pmtM06fzBCmnAc=
=eRsY
-----END PGP SIGNATURE-----

--Apple-Mail=_86FDDE1E-2C7D-4CD0-B9AE-481446B35EC3--


From nobody Wed Mar 29 05:34:46 2017
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 DE74D1296C7 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 05:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6-5kbgZ1N_3 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 05:34:41 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B496E1294D8 for <ietf@ietf.org>; Wed, 29 Mar 2017 05:34:40 -0700 (PDT)
Received: from [192.168.0.158] (50-232-11-130-static.hfc.comcastbusiness.net [50.232.11.130]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2TCaiEV001901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Mar 2017 05:36:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490791005; bh=Pj/PSwihpiuMb4GEXFiMvJKBzGce0kTreccgQH1VIs0=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=ZNnseCUKs67jDUd7uLW89t9NEwCpiTIuQM9wmwhonCYbSPy6SEo7oo7WoueguAOH3 yVI3ATxWCwdOHBMVxnAfB/EBz5XZ1SCO++JRGSl6r3pGlS2puLTbi14VlgJVNzP4lu LHEYaahA7+Tbn5pVtwhfc8jfCAQzEgyrfWs2rUJ8=
Subject: Re: Getting the latest version of an RFC specification
To: Yoav Nir <ynir.ietf@gmail.com>
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net> <38BC1BB4-0996-4138-BEE0-58CD4F2B867B@gmail.com>
Cc: IETF general list <ietf@ietf.org>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <de157331-d3ff-483c-b69b-116f4d1cde0b@dcrocker.net>
Date: Wed, 29 Mar 2017 07:34:31 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <38BC1BB4-0996-4138-BEE0-58CD4F2B867B@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-vzTd_U4bZ-PZ5deJ3Kzvly3xAI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 12:34:45 -0000

On 3/29/2017 7:19 AM, Yoav Nir wrote:
> I question how useful it is.  The obsoletes/obsoletedBy relationship is
> semantically overloaded. Consider the header of RFC 4306:

Yoav,

Thanks for the thoughtful (and quick) response.  Yes, the total model 
and application of its details are more complicated.  But I found myself 
relying on a very simple distinction:

If someone wants to do research and explore old stuff, they can still do 
that.  The can still merrily wander the link sequences.

However "Obsoleted By" means "don't use the old stuff".

So if one merely wants to get (or wants to cite) the most recent version 
of what they /should/ use, then the feature I'm suggesting will support 
that.  More easily and reliably than can happen now.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Mar 29 06:12:19 2017
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 0B841126DD9 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 06:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z8i9qBXqlX9t for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 06:12:14 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF9DF1294D8 for <ietf@ietf.org>; Wed, 29 Mar 2017 06:12:13 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ctDOV-000Hcz-A5; Wed, 29 Mar 2017 09:12:11 -0400
Date: Wed, 29 Mar 2017 09:12:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, Yoav Nir <ynir.ietf@gmail.com>
cc: IETF general list <ietf@ietf.org>
Subject: Re: Getting the latest version of an RFC specification
Message-ID: <28769B239D7982B8A4E8E932@JCK-EEE10>
In-Reply-To: <de157331-d3ff-483c-b69b-116f4d1cde0b@dcrocker.net>
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net> <38BC1BB4-0996-4138-BEE0-58CD4F2B867B@gmail.com> <de157331-d3ff-483c-b69b-116f4d1cde0b@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
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/csUlTstOx0_zh_iLWMdBquWEl-g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 13:12:17 -0000

Dave,

--On Wednesday, 29 March, 2017 07:34 -0500 Dave Crocker
<dhc@dcrocker.net> wrote:

> On 3/29/2017 7:19 AM, Yoav Nir wrote:
>> I question how useful it is.  The obsoletes/obsoletedBy
>> relationship is semantically overloaded. Consider the header
>> of RFC 4306:
> 
> Yoav,
> 
> Thanks for the thoughtful (and quick) response.  Yes, the
> total model and application of its details are more
> complicated.  But I found myself relying on a very simple
> distinction:
> 
> If someone wants to do research and explore old stuff, they
> can still do that.  The can still merrily wander the link
> sequences.
> 
> However "Obsoleted By" means "don't use the old stuff".

Sadly, while it should, it doesn't.  The community has allowed
several situations to occur in which a document is obsoleted,
some of its sections are not replaced with newer material, and
those sections continue to be referenced, occasionally
normatively, from other documents.  An even more common case
occurs when 

 * RFC X is published
 * RFY Y is published sometime later, normatively
	referencing RFC X
 * RFC Z is published, obsoleting RFC X.   

It is now unclear whether, until RFC Y is replaced, whatever it
specifies should be used in conjunction with the relevant parts
of RFC X or with the implementer's guess as to what the
specification of RFC Ybis, referencing RFC Z and modified
consistently, would be.  Sometime that is easy and obvious,
sometimes, especially when Z changes protocol behavior or data
structures from X rather than just being a clarification, it is
not.

To make things a bit more complicated, replacement of a document
is not always one-one.   We consolidate documents in
updates/replacements, sometimes we split them, and more complex
relationships, while not common, have happened.  In some of the
forking cases, we have part of RFC A replaced by RFC C and
another part replaced by RFC D and, because the historical
metadata  doesn't make it convenient, list only C as doing the
obsoleting so a simple link based  on the metadata would be
misleading.

One can sensibly argue that we shouldn't let those kinds of
entanglements happen.  But it is what we do.  In the extreme
case, the normative reference from Y to to X should imply that
the request to publish Z should go into normative reference hold
in the RFC Editor queue until Ybis is ready for publication.
But we don't do that.   More realistically, I think the real
question is "what do I need to use to properly implement this
specification today?".  Explorations of that question are what
lead us to summary roadmap documents or associated Applicability
Statements.  They are also what led to to the "ISD" proposal and
similar ideas, where the _standard_ (even, that WG concluded, at
the Proposed level) would be a summary document independent of
RFC numbers with appropriate links and, as necessary,
explanation.

In the past, I've argued that, if a document is published with
"Obsoletes XYZ", it needs to contain a section that sorts all of
those issues out.  I've gotten zero traction.

I fear that, unless there were a case by case analysis of each
document with an "obsoletes" tag, there are enough non-obvious
cases around to create significant risk that you idea would
cause more harm than the added convenience it would provide.
On the other hand, if the incoming IESG were convinced that this
is enough of a problem, it wouldn't be hard to dig the ISD and
other NEWTRK proposals up and update and re-post them.

best,
     john



From nobody Wed Mar 29 06:28:42 2017
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 8099F1294F6 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 06:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GFZ1M2GBTonn for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 06:28:39 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CA4E129510 for <ietf@ietf.org>; Wed, 29 Mar 2017 06:28:38 -0700 (PDT)
Received: from [192.168.0.158] (50-232-11-130-static.hfc.comcastbusiness.net [50.232.11.130]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2TDUglS005258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Mar 2017 06:30:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490794243; bh=1cjyMr1JH8Wq8HnIpUJRbzP8vS64rIyArVVtFV98Iqk=; h=Subject:To:References:Cc:From:Reply-To:Date:In-Reply-To:From; b=InbgLiu+CnVdt8LC76DhpExM10GEoNJM6x/0aCqo5QryMkHtKAmdS+pBp44aDEd9J 6BJFZc7nN9WO02TJj6G0h5fwRYCu5ngHViXTV/jGGFLrdmXnWZwZNUgFdoP9TN841o GhFYiL3kyDrjzXJJC0dWaGTDMFTrmyYSeccpyb7w=
Subject: Re: Getting the latest version of an RFC specification
To: John C Klensin <john-ietf@jck.com>
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net> <38BC1BB4-0996-4138-BEE0-58CD4F2B867B@gmail.com> <de157331-d3ff-483c-b69b-116f4d1cde0b@dcrocker.net> <28769B239D7982B8A4E8E932@JCK-EEE10>
Cc: IETF general list <ietf@ietf.org>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <717845a7-aab9-9b8c-13b1-bacd576f5656@dcrocker.net>
Date: Wed, 29 Mar 2017 08:28:36 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <28769B239D7982B8A4E8E932@JCK-EEE10>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kYhPPzO0Le5GCzLhU1blRDNu9bs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 13:28:40 -0000

On 3/29/2017 8:12 AM, John C Klensin wrote:
>> However "Obsoleted By" means "don't use the old stuff".
> Sadly, while it should, it doesn't.  The community has allowed
> several situations to occur in which a document is obsoleted,


I fear you are overinterpreting the use of what I'm suggesting or are 
conflating tasks.

Anyone who wants to be, or must be, diligent and thorough still can be.

My suggestion is for the folk who want simple, simplistic, basic access 
to 'the most current' spec.  The concerns you raise do not invalidate 
the suggested mechanism's accomplishment of that goal.

Rather, your concerns highlight the bounded scope of that goal, which 
I'll claim was already there -- but it's ok to emphasize it.  One can 
imagine an IETF Surgeon General's warning sign on the banner when the 
'latest' version is displayed, cautioning against excessive inhaling of 
the contents.

So, yes, the concerns you raise are all entirely valid... for someone 
who must dot all the specification i's and cross all the implementation 
ts, but that's not the target audience for the mechanism I'm suggesting.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Mar 29 06:54:55 2017
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 94FF4129514 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 06:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MzSVIwmuImjj for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 06:54:51 -0700 (PDT)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 348DD120726 for <ietf@ietf.org>; Wed, 29 Mar 2017 06:54:48 -0700 (PDT)
Received: by mail-qt0-x234.google.com with SMTP id x35so12943336qtc.2 for <ietf@ietf.org>; Wed, 29 Mar 2017 06:54:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/gz8iBJlsxBBg1oiPd3DvjM3zCahMvqRbOTwg9a/x2A=; b=heowW2laUnCAQCRx+Qxkiev39vt1JlVpFrFmPPSclX2AgqL2r5TGS3taUuU/JZasma /MWBiGXwzuE8nCX1bEXmt1fuvXL7yj5EiI6oBEahwXShNsMY50DX7IT3rLywW6Dctr10 8WAHUhO9Fj3Uv9jN97yMkp6e9S3gkK8wS2O+6G3aVYqTevGJnGO7tA1SdFF/tsQIpcq3 a/cpDTICAI6+HHRJ7Jv/rHRDvEL78Fd0Zl3kxrp1sub5RpjXDKW+EkJY6GV99ZF6zkX3 KUvPOY2ESNNyD/q8E82ahljSkuqPDs52SEUCide2YHCX7352521vFDBYsSAS6AqVWk1s 8E7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/gz8iBJlsxBBg1oiPd3DvjM3zCahMvqRbOTwg9a/x2A=; b=jaPXp8lWWNbwd+18Hdq2mBrPVqMj9MPYrtB1Sd/zq8KzNnh0lxr4vJd1BlQZ/Uy440 Pof2ESnPhgEc+n+0mhXr0Ja2oo0rNaTbRtZqsibiegh7Evdf+73jpGqnjOye5ZZckz/9 rf7O3IaaQVAR5lsHvJtB2mz4CICufrgMR87WpzLUynPEGrarBCFTXvMtL9OOJylMOtjo 66BPClF11woF3EYT279Igybfes/hTI1+D6Z6+BdVYgmxYQnyXN8FXulM10Ep+R1wssU9 qaQ3ZyJ6IjMUnbEnlQpXf3vUVpjNS3r9i3eG5miH9rJloWI4f4T5ubB/5+F2zcV0dNlk FS9g==
X-Gm-Message-State: AFeK/H1xYu4f6IyaOtcmlw7US3OnFqmcjTT+ApjNyj21KeG1XudrCXiD/hyp6XsUCK9i1zORaMhcJm3FtYAjyiG6
X-Received: by 10.237.53.177 with SMTP id c46mr779368qte.124.1490795687001; Wed, 29 Mar 2017 06:54:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.177.11 with HTTP; Wed, 29 Mar 2017 06:54:06 -0700 (PDT)
In-Reply-To: <148700405095.24965.11757083307121031800.idtracker@ietfa.amsl.com>
References: <148700405095.24965.11757083307121031800.idtracker@ietfa.amsl.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 29 Mar 2017 08:54:06 -0500
Message-ID: <CAHw9_iJhaaeTzrtMxmkPAJ1-8PQUM034Sm9CNQMheTASvbzbsg@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-07.txt> (Effect of Pervasive Encryption) to Informational RFC
To: "ietf@ietf.org Disgust" <ietf@ietf.org>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, draft-mm-wg-effect-encrypt@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RmAHC0-Znultwbg3b4j7S1jRfVA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 13:54:54 -0000

Hi,

I'd like to let you know that I've placed this
draft-mm-wg-effect-encrypt on the next telechat (as a returning item).

The document has had a number of changes. I think that the changes
make the document much more readable and complete, but are largely
editorial, and that the document does not need another last call.

Please take a look at the document and provide feedback on the changes
(preferably by April 7th).

Please also let me know if you disagree, and feel that the changes are
significant enough that it really does require a new IETF LC.

Warren.


On Mon, Feb 13, 2017 at 10:40 AM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Effect of Pervasive Encryption'
>   <draft-mm-wg-effect-encrypt-07.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 2017-03-13. 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
>
>
>    Increased use of encryption impacts operations for security and
>    network management causing a shift in how these functions are
>    performed.  In some cases, new methods to both monitor and protect
>    data will evolve.  In other cases, the ability to monitor and
>    troubleshoot could be eliminated.  This draft includes a collection
>    of current security and network management functions that may be
>    impacted by the shift to increased use of encryption.  This draft
>    does not attempt to solve these problems, but rather document the
>    current state to assist in the development of alternate options to
>    achieve the intended purpose of the documented practices.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-mm-wg-effect-encrypt/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-mm-wg-effect-encrypt/ballot/
>
> No IPR declarations have been submitted directly on this I-D.
>
> I-D nits notes that there is one use of a 2119 MUST (which can be
> lowercased I guess) and the reference to [SACM] in 5.7 has no
> matching entry in section 12, but we can fix those later.
>
> This is an AD-sponsored last call. The relevant AD (Stephen
> Farrell) will be escaping the IESG in March, so there may not be
> time to get this document approved by the IESG before then,
> e.g., if there is substantive discussion during/after IETF LC.
> Warren Kumari, (one of the incoming ADs) has agreed to pick
> this up should that be necessary. But better to get it over the
> line if we do turn out to have IETF consensus for it now.
>
>
>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Wed Mar 29 06:57:05 2017
Return-Path: <ynir.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 57E801294C5 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 06:57:03 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nQ5ihdarYoOW for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 06:57:01 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8129D120726 for <ietf@ietf.org>; Wed, 29 Mar 2017 06:57:01 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id y18so152817344itc.0 for <ietf@ietf.org>; Wed, 29 Mar 2017 06:57:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=9Udth2GeU0z8oqFOsk8LIxyaZuleHVqemAQPK7cRmh0=; b=GtZQWnsawBsKkWNueBsGt4i+c1BPsvOuLujQcy4ZrfsGh7bplSRUHuA3LBikZKmWYG To6yZLgFuQywNMa6zlL2H5RElgbLY2m3b5bNaPO/kYQMidSdy2WHJf+Kxb918aBa31pa 4T7CNPGVZ5+XzTHlD9r6tj9TzKsLnlbTmbiRDKv1G0EAmejNSGBDxGZwVOaPKCE79cZT RDTgRyczasijtMUpBk7PWt7/u2vQg3qrxniB8/U6B0vtQlQKViEorKwdh26QfDpqVGMj 4kUvJhMgnZyHX9IcTHPyEE3jTtRdkavRemlRxIfCWs1s+q0VADqsK+Z7OX092M0ac3eB MBtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=9Udth2GeU0z8oqFOsk8LIxyaZuleHVqemAQPK7cRmh0=; b=UB3h3YanOhGXu0LzMlAcjWpbmORQ+51LPBQUBvr/Mei0LqeCShb1IH6FLy1FDzIoJF 9i19/kp/8IW763JLNj1ft3/Fv9WukfKKWv9T8NLw9OrbkOwkZKisST4k13LhJO3au5UO f3AQQ9BSkRsqOrKFQBaiBI0MZMUuvwE+AvqIUNQ9QXC8OZhrurAnc+QY6hUPb4hhtR87 IoD+eCxEkuuJW0ISySeWAIvQUyIGQoxfbk8zo9H9H6/ROSjTEzDfpuvY7rDRj//PH0FE 7ctugYE4j0I4EDwucCKx0km1lT07V2WBziz06rknzdVPBbZXNxt8kecSEFprCMnuafeg i+eQ==
X-Gm-Message-State: AFeK/H3kUuOdJ6qDgszWY8+phQO7kdjF0A2M/1rvxD/PSDMlwzXKD2HfFdNKh6izYTGdBQ==
X-Received: by 10.36.184.71 with SMTP id m68mr1376234ite.8.1490795814845; Wed, 29 Mar 2017 06:56:54 -0700 (PDT)
Received: from t2001067c03700128509a7ded3cb9d2c7.v6.meeting.ietf.org (t2001067c03700128509a7ded3cb9d2c7.v6.meeting.ietf.org. [2001:67c:370:128:509a:7ded:3cb9:d2c7]) by smtp.gmail.com with ESMTPSA id x26sm279481ita.1.2017.03.29.06.56.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 06:56:54 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <BF7A45FE-A989-4E06-8883-088959139614@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8E17F0C4-4A43-48B3-B110-4B3F61806420"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Getting the latest version of an RFC specification
Date: Wed, 29 Mar 2017 08:56:52 -0500
In-Reply-To: <de157331-d3ff-483c-b69b-116f4d1cde0b@dcrocker.net>
Cc: IETF general list <ietf@ietf.org>
To: dcrocker@bbiw.net
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net> <38BC1BB4-0996-4138-BEE0-58CD4F2B867B@gmail.com> <de157331-d3ff-483c-b69b-116f4d1cde0b@dcrocker.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p9_BKVBI52aZ_eaZR4x8-C9MPys>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 13:57:03 -0000

--Apple-Mail=_8E17F0C4-4A43-48B3-B110-4B3F61806420
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 29 Mar 2017, at 7:34, Dave Crocker <dhc@dcrocker.net> wrote:
>=20
> On 3/29/2017 7:19 AM, Yoav Nir wrote:
>> I question how useful it is.  The obsoletes/obsoletedBy relationship =
is
>> semantically overloaded. Consider the header of RFC 4306:
>=20
> Yoav,
>=20
> Thanks for the thoughtful (and quick) response.  Yes, the total model =
and application of its details are more complicated.  But I found myself =
relying on a very simple distinction:
>=20
> If someone wants to do research and explore old stuff, they can still =
do that.  The can still merrily wander the link sequences.
>=20
> However "Obsoleted By" means "don't use the old stuff".
>=20
> So if one merely wants to get (or wants to cite) the most recent =
version of what they /should/ use, then the feature I'm suggesting will =
support that.  More easily and reliably than can happen now.
>=20

Right. It is a useful thing (and may be a task for next IETF=E2=80=99s =
code sprint).  People should just know that they might get surprising =
results.

Yoav



--Apple-Mail=_8E17F0C4-4A43-48B3-B110-4B3F61806420
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJY270lAAoJELhJCxUKWMyZZGAIAKdvocTKd+HboWYsAadtXQAL
VlPVZx1NKXQuvfAV9LuB9RmSlW9rfCRNAPHscjt6p1tNMtgAEVPopZdQc0XnSxhc
xMbbODlF/HbpRt9+bhKWEiOA/xO3nyU5r29PGDNamxvmhInuxYeeUDzGpD5unQfM
44CuWwRYzCs0gSG8Rw0KofVTxoHXiKIZigoIqmWLQThHi/lXsSaPUdNtlTXGn4w6
/dDORjYQPhsU2ngocdig1MjTRw42XX3yjo1XZB/baDk+UHYnTMCj0DIpK5ZU2IxM
mufLKJK3lqAtZqwcHk9SU1zBIowF8+TWPTN7R3G88Rlm5IRpv2rZrpNod7V10Qc=
=WHgD
-----END PGP SIGNATURE-----

--Apple-Mail=_8E17F0C4-4A43-48B3-B110-4B3F61806420--


From nobody Wed Mar 29 07:06:44 2017
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E87124D37; Wed, 29 Mar 2017 07:06:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: recentattendees@ietf.org, ietf@ietf.org
Subject: IETF 99 Registration, Hotel Reservations, Social Ticket Sales Open!
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: IETF Agenda <agenda@ietf.org>
Message-ID: <149079640320.26806.6658983960693843354.idtracker@ietfa.amsl.com>
Date: Wed, 29 Mar 2017 07:06:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/J21ulDmuxYXT7CUcnkkWtsG8U1Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 14:06:43 -0000

IETF 99
Prague, Czech Republic
July 16-21, 2017
Host: Comcast/NBCUniversal and CZ.NIC

IETF 99 Information: https://ietf.org/meeting/99/index.html
Register online at: https://ietf.org/meeting/register.html

1.  Registration
2.  Value Added Tax (VAT)
3.  Visas & Letters of Invitation
4.  Accommodations
5.  Social Event!

1. Registration:

Registration fees do not include the VAT of 21%. The VAT will be added to the fee and paid over to the tax authorities.

	A. Early-Bird Registration: USD 700.00, if paid in full prior to 23:59 UTC 2017-07-07
	B. After Early-Bird cutoff: USD 875.00
	C. Full-time Student Registrations: USD 150.00 (with proper ID)
	D. One Day Pass Registration: USD 375.00
	E. Registration Cancellation   
	Cutoff for registration cancellation is Monday, 10 July 2017 at UTC 23:59. 
	Cancellations are subject to a 10% (ten percent) cancellation fee if requested by 
	that date and time.
	F. Online Registration and Payment ends Friday, 14 July, 2017, 17:00 local Prague time
	G. On-site Registration begins on Sunday, 16 July 2017 at 10:00 local Prague time.

2. Value Added Tax (VAT)

	You may be entitled to recoup some or all of the VAT.
	In addition to a receipt from the IETF, all IETF 99
	attendees will receive a VAT compliant invoice from BC&A
	(VMC), our tax agent. For this meeting the Czech VAT of
	21% has been added to the Registration Fee. More
	information is available at:
	https://www.ietf.org/meeting/99/vat.html

3. Visas & Letters of Invitation:

	Letters of invitation are available through the registration
	system. Once you register for IETF 99 you may request a local
	letter of invitation through a link in your confirmation email or
	the self-service portal. 

4.  Accommodations:
	
	1. Hilton Prague (Headquarters Hotel, block of 600 rooms)
	Room Rate:  $148 (single) $164 (double) USD. Includes in-room high-speed
	Internet and breakfast.
	VAT of 15% (taxes subject to change) is excluded from
	the above prices.
	Reservation Cutoff Date: 19 June 2017
	Cancel with No Penalty: 7 Days prior to arrival
	Distance to Meeting Venue: N/A
	More detail at: http://www.ietf.org/meeting/99/hotel.html
	Reservations: http://eventsathilton.com/show/58ca77f5e6f1441222ee7b5e
	
	2. Hilton Prague Old Town (Overflow hotel, block of 140)
	Room Rate: $148 (single) $163 (double) USD. Includes in-room high-speed
	Internet and breakfast.
	VAT of 15% (taxes subject to change) is excluded from
	the above prices.
	Reservations Cutoff Date: 27 June 2017
	Cancel with No Penalty: Up to 72 hours prior to check-in/arrival
	Distance to Meeting Venue: 11 minute walk
	Reservations: http://eventsathilton.com/show/58ca6c33e6f1441222ee7b58

5. Social Event
	Date: Tuesday, 18 July 2017
	Time: 18:30 - 22:00
	Cost: $20 USD per ticket, limit two per attendee. Children 10 and under are free. 
	Hosted by: CZ.NIC, Comcast, and NBC Universal
	Location: Kafka museum at Hergetova Cihelna
	
	Join us on Tuesday, July 18 from 18:30 to 22:00 for a
	tour of the Kafka museum at Hergetova Cihelna. A boat
	ride to the event will start the evening off before you
	experience an interactive tour of different eras of
	Prague's history and meet iconic Czech personas that
	changed the country. The event will have Czech and other
	cuisines, beer, wine and non-alcoholic beverages.

	More information here: https://www.ietf99.cz/#socialevent
	Link to purchase Social Tickets: https://www.ietf.org/registration/ietf99/eventticket.py


From nobody Wed Mar 29 07:44:51 2017
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 2C298126DD9 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 07:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OwXF5fdcRsME for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 07:44:45 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EA88129526 for <ietf@ietf.org>; Wed, 29 Mar 2017 07:44:40 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2TEhpek016872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Mar 2017 07:43:52 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <9F0F8841-BC1D-4C27-83EF-8F93F33FB021@puck.nether.net> <CAMm+Lwh5JMn+JxPB3Q3RKpeibckVSB2Fqm_RajcnU28OAx=jOw@mail.gmail.com> <1483474918.1346083.836313393.2699EBD5@webmail.messagingengine.com> <CAMm+LwjJDyCv2mBG8ob-njDj-4m5tr7jP6XAiEn1ME5NCYcpiQ@mail.gmail.com> <263de3ca-e2a2-c99f-1a9d-18e352c900ce@isi.edu> <869e1c74-2e6e-f4cd-4830-50985bab6be8@isi.edu> <4079C051-C0C1-4220-8F0A-39F1FF0EDEF3@frobbit.se> <240f1201-937b-24d1-d066-4f35a6788cb8@isi.edu> <A4FF8930-F644-496A-8AEE-F3A8504039E8@frobbit.se>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Tony Finch <dot@dotat.at>, IETF Discussion Mailing List <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <75c5729b-c892-376e-a7e4-aa16ca808eaf@isi.edu>
Date: Wed, 29 Mar 2017 07:43:50 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <A4FF8930-F644-496A-8AEE-F3A8504039E8@frobbit.se>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yut4BPH7rHvGjcE6_B-0QYkjS64>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 14:44:49 -0000

Hi, Patrik,


On 3/28/2017 10:52 PM, Patrik Fältström wrote:
> On 28 Mar 2017, at 19:47, Joe Touch wrote:
>
>> On 3/27/2017 11:37 PM, Patrik Fältström wrote:
>>> Joe,
>>>
>>> I have read your I-D and like it! Let me start there :-)
>>>
>>> What I think is not clear enough is the problem with POSIX, and it should be more clear in some place, maybe section 6.1, that POSIX definition which is in use in quite a number of systems do not handle leap second very well. Too many do believe the time_t definitions include the number of seconds since epoch when in reality it does not (as you note in the definitions).
>> I can make that more clear, but AFAICT POSIX time is *defined* as seconds since the Unix epoch *not counting* leap seconds at all.
> Well, one of the problems is that the specification of POSIX time is a bit unclear.
>
>>> One could even question whether it is Continuous as two seconds will have the same number since epoch around the addition of a leap second
>>> It is Continuous by definition.
>> When UTC adds a leap second, nothing different happens to POSIX time.
> No, that is not correct if you look at the day when the leap second is added.
>
> POSIX is number of (days * 86400) plus seconds inside the current day.

POSIX asserts that a "day" = 86400 * "seconds" but defines neither day
nor second.

It definitely says it does not include leap seconds, so there cannot be
"plus seconds inside the current day" - doing that assumes that POSIX
days are correlated to UTC days, but that's never stated.

>  This implies if there is a day with a leap second there will be 86401 seconds which also will be the first second the following day.

A UTC day with a leap second clearly has to use a different definition
of either 'second' or 'day' than POSIX, which requires that every day
has exactly 86400 seconds.

>
>>> There are some people that have suggested a change, for example <http://www.cl.cam.ac.uk/~mgk25/time/c/> but I have not seen any movement. Maybe you know more than me on this?
>> AFAICT, that's just attempting to redefine the <time.c> interface as returning UTC rather than POSIX time.
> The UNIX time_t struct do deliver UTC, including leap seconds, but the number of seconds from epoch is wrong regarding leap seconds. Includes one leap second within the day of the leap second being added and without leap seconds otherwise.
time_t in POSIX is supposed to return a signed integer of the number of
seconds since the Unix epoch.

any more complicated structure is an attempt by a system to convert its
internal time to UTC, which requires knowing about leap seconds as well
as knowing the relation of the local internal "second" vs the SI version.

>> Which works *IF* your machine has access to updated leap-second information, e.g., via NTP.
> Correct, if one have access to leap seconds, one could adjust the number of seconds and that could happen already today as POSIX definition is a bit unclear on this. 

IMO, it's very clear that leap adjustments are not part of POSIX time.

> But people have not implemented it. So instead for example Google smear the leap second over the day so that there is not bump in the road, and they run NTP servers that do give back this smeared time that differs from UTC.
They're not using POSIX time then; they're using an internal
approximation of UTC to provide time to NTP.

Joe


From nobody Wed Mar 29 08:41:14 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4E93126DC2 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:41:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level: 
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mkPzwVpQeqLb for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:41:11 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D4FB129789 for <ietf@ietf.org>; Wed, 29 Mar 2017 08:41:09 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id 970A51406B1F; Wed, 29 Mar 2017 08:41:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=UJz0jc/zNhxeZ0 b1HJnybiXbPuY=; b=GZlz8ThT5XmJ1Yrr97dfszqLXqL/s7mmVQRDZGMMJfg25j AFcM4Dvv8kdF0KgkQpSowzE2dhF5MO/Cku5sb6j9DhBhYglfTxr9IhGuQUgwx/tO GpGESs8GAOhT5h46wsRXC/mI2bJmct9MO46o8ZPmqaYg6I0B0hhPKvT0G/Dd0=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 80B741406B0A; Wed, 29 Mar 2017 08:41:06 -0700 (PDT)
Date: Wed, 29 Mar 2017 10:41:03 -0500
From: Nico Williams <nico@cryptonector.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Cyrus Daboo <cyrus@daboo.name>, Ted Lemon <mellon@fugue.com>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Predictable Internet Time
Message-ID: <20170329154102.GP7490@localhost>
References: <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <alpine.DEB.2.11.1701031348430.7102@grey.csi.cam.ac.uk> <0bbfcd7c-11a7-0e7f-56f7-eee959b7a947@gmail.com> <CAMm+Lwi0sQyRE_2dMCkwTk7xTiK2JbHhHSPYMkdG2FeBw_6CNA@mail.gmail.com> <7BDE58D23ADF3BC046F8942D@caldav.corp.apple.com> <b27515e2-a36a-7bf2-0ca4-1fae31a9dc21@gmail.com> <04DD5DFCB528DCD404C81F78@caldav.corp.apple.com> <A193D619-7B59-4EFB-A773-B6F6E4FD5884@fugue.com> <C93A4EFBD3E91F4F714DF948@caldav.corp.apple.com> <29873ae2-22a2-d59b-38a6-b06763eeaec3@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <29873ae2-22a2-d59b-38a6-b06763eeaec3@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/To-qe3CCYZ9IyhKmI_DinizUNGI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 15:41:13 -0000

On Wed, Jan 04, 2017 at 09:21:29AM +0000, Stewart Bryant wrote:
> On 03/01/2017 19:54, Cyrus Daboo wrote:
> >>This is true, but any specific local time will always occur at a
> >>specific universal time, so this isn't actually a problem.
> >
> >No! That is not true because a future local time is not guaranteed to
> >be at a specific universal time because local government can change
> >their time zone (or more likely) their daylight savings time
> >transition at any time between now and said future time. i.e., you
> >cannot "pre-cache" all the local time -> UTC mappings for a future
> >recurring event and then just use the UTC values, because the time
> >zone definition may change.
> 
> So an application sensitive to that needs to specify its timing in
> terms of local time, but that should not force the fundamental time
> distribution system to operate in that mode.

Sure it does!  If you want to interchange calendaring events (which...
people _do_) then those events must refer to local time, and they must
be stored in local time form.  Otherwise the same issues Cyrus mentions
crop up.

This is hardly problematic.  It just means that

a) every system needs to be able to convert to/from local time (but that
   was _already_ the case even when you believed that local time was
   only for interaction with a user) from using any and all timezones
   (which was not already the case for you, but it's fine anyways),

b) (a) implies that tzdist is needed and TZ data has to be kept up to
   date.

> Maybe we need two time distribution systems, one that accurately does
> the ranging and flywheel management and distributes precision time for
> technical purposes, and a separate one that manages the offsets and
> jumps relative to the underlying precision continuous time
> distribution system.

Yes, of course.

Nico
-- 


From nobody Wed Mar 29 08:46:01 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF0A126557 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level: 
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DnvYqSAyKcFt for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:45:42 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF5FA1292C5 for <ietf@ietf.org>; Wed, 29 Mar 2017 08:45:42 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id 5738E1406B21; Wed, 29 Mar 2017 08:45:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=d97V1mW3Mta629 qPVopkdbSCL3Y=; b=bUm9IfF/b9BvKVw9lZbhVxWqdO4W+Hxj3mEvBdVmR0a6pW rx5ubfmIBnPzCgsijbqyFa4Q9llOTOQzcoJdAPVjg1C5iJPWpWKpwYKzMPUIFWyw mGVShYIskCdYhifab6Hm4XPdEqBfWKzt6KMvK0BOFnQzVpXeCgstqwmApHqgw=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 53A0F1406B20; Wed, 29 Mar 2017 08:45:40 -0700 (PDT)
Date: Wed, 29 Mar 2017 10:45:37 -0500
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Cyrus Daboo <cyrus@daboo.name>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Predictable Internet Time
Message-ID: <20170329154536.GQ7490@localhost>
References: <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <alpine.DEB.2.11.1701031348430.7102@grey.csi.cam.ac.uk> <0bbfcd7c-11a7-0e7f-56f7-eee959b7a947@gmail.com> <CAMm+Lwi0sQyRE_2dMCkwTk7xTiK2JbHhHSPYMkdG2FeBw_6CNA@mail.gmail.com> <7BDE58D23ADF3BC046F8942D@caldav.corp.apple.com> <b27515e2-a36a-7bf2-0ca4-1fae31a9dc21@gmail.com> <04DD5DFCB528DCD404C81F78@caldav.corp.apple.com> <A193D619-7B59-4EFB-A773-B6F6E4FD5884@fugue.com> <C93A4EFBD3E91F4F714DF948@caldav.corp.apple.com> <CAMm+LwgWSp7R=vZfWNXTsk4DjCDAWo4PVNnYsGPrewZp2Ng0hw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+LwgWSp7R=vZfWNXTsk4DjCDAWo4PVNnYsGPrewZp2Ng0hw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OpwSshaqvVWdyJaiduTQsVN5ck0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 15:45:47 -0000

On Tue, Jan 03, 2017 at 03:06:57PM -0500, Phillip Hallam-Baker wrote:
> +1

Indeed.

> Case in point, the time displayed on my Honda Oddy does not correct for
> daylight savings correctly because some pimple brain decided to vary the
> date of the switchover and there is no way to update the firmware without
> spending stupid amounts of money to do so.
> 
> This is the sort of thing I would like to be able to avoid in IoT. The
> problem being that to do so requires vendors to think about problems as
> something other than an excuse to sell a 'pro' version or updates.

Trouble is, this is one more protocol for IoTs to speak.  One more
source of those vulnerabilities that make IoTs IoSs.

> Not being able to predict with accuracy when a future time expressed in
> civil time will occur is a problem.

It's easy to predict that actual changes will be withing +/- 1 hour
though.  For events scheduled far into the future this is mostly a
non-issue.

I'm not interested in more complaining about politicians making our life
hell.  Fact is they get to and they do and they have and they will keep
doing it.  So we should arrange our affairs as to minimize the pain and
just move on.

Nico
-- 


From nobody Wed Mar 29 08:54:21 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9DD126D74 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level: 
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QiLfieYZBtTK for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:54:18 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60C55126557 for <ietf@ietf.org>; Wed, 29 Mar 2017 08:54:18 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id F3BA21406B1F; Wed, 29 Mar 2017 08:54:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=TSIArRKo0Xav/I 13ssPJu6czShk=; b=DW9eNwGLY07ZKS2WaUcCigCbNKnh4WdK5v8OWODI+1bnxn D9kdS8BfREjWJFBdgzhvCMnyYLkvM61J4cMn58Vhircob9EYd6Hkc54sFwDHDfKM +NMtyxcGOIw+HdY2GlxGgARNhK6Qc+eWjyriWw9MraTclJHsVa+iRqV2V13HE=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 986921406B1A; Wed, 29 Mar 2017 08:54:17 -0700 (PDT)
Date: Wed, 29 Mar 2017 10:54:15 -0500
From: Nico Williams <nico@cryptonector.com>
To: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Predictable Internet Time
Message-ID: <20170329155414.GR7490@localhost>
References: <CAMm+Lwg+aD1DQ_=sr=3_7J2Eq+E16EScycyv7k=fdjrRvqdRVg@mail.gmail.com> <m1cOYZ6-0000FAC@stereo.hq.phicoh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m1cOYZ6-0000FAC@stereo.hq.phicoh.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9u5Q3dYECdNJBHqJVTKMxHVTDQY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 15:54:19 -0000

On Wed, Jan 04, 2017 at 12:32:23AM +0100, Philip Homburg wrote:
> Unfortunately, there doesn't seem to be an IETF equivalent for operating
> systems, so it will be completely random whether anything will happen in
> this area or not.

There's no reason that the IETF could not a) define an abstract time API
that includes time "types" ({UTC, TAI, local, smeared, whatever} x
{various possible representations}), conversions between them, and
behaviors, then b) define bindings of this API for various programming
languages.  The Open Group, to give one example, could take our advice
on this matter -- or not; they'd not be obligated, natch.

The IETF has done this for other networking technologies (sockets
extensions for IPv6, GSS-API, ...).

Because our protocols must deal with time, this is very much in our
bailiwick.  It also fits in other SDOs, but as none have published such
a spec, we might lead.

Any RFC on smeared time surely would at least define a subset of this
abstract API for conversions to/from UTC.  We might as well go all the
way.

Nico
-- 


From nobody Wed Mar 29 08:56:57 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE1E5126B6D for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level: 
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XTlQQCOLa8d0 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:56:53 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D561712953C for <ietf@ietf.org>; Wed, 29 Mar 2017 08:56:53 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id 5E69E1406B1A; Wed, 29 Mar 2017 08:56:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=t0Mmq3zonHgtdK oVD/ZTPYwn0Xg=; b=ya6EdFFACUIL18ZxJ7siHDEYx/eoKrjRnR/CrkYw84PyVb jrR+wV0TTaZjaPyhn84DgVCMHOZhAgE8OddirHhpxb1ZORLZ6kH4JZSNuR1oy+Dn xoTjxcwobhNsNyR4YHToovMz7I9jekCjoWeL+G0RZIopz+cJFRknQF4Zk8HGE=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 132ED1406B0A; Wed, 29 Mar 2017 08:56:53 -0700 (PDT)
Date: Wed, 29 Mar 2017 10:56:50 -0500
From: Nico Williams <nico@cryptonector.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: Predictable Internet Time
Message-ID: <20170329155649.GS7490@localhost>
References: <m1cOYZ6-0000FAC@stereo.hq.phicoh.net> <bf1a0b49-6f76-1ec8-0a70-bfff9be40c16@alvestrand.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <bf1a0b49-6f76-1ec8-0a70-bfff9be40c16@alvestrand.no>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y2kVwcopRcsJ8AHcrF29zYZUg4s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 15:56:56 -0000

On Wed, Jan 04, 2017 at 09:49:35AM +0100, Harald Alvestrand wrote:
> FWIW, the W3C has switched to defining time inside a Web page in two
> segments:
> - Page load time, which is UTC-derived (POSIX time extended to
> milliseconds), and can jump when the system clock is reset
> - Events related to the page load time, which has floating-point
> representation, and is guaranteed to be monotonic.

But aren't these relative times (intervals)?  As long as they are short
enough, distinctions between UTC, TAI, local, and smeared time will make
little difference most of the time.  (Naturally, using local time might
cause a page load time to appear to be negative, or over an hour, around
daylight savings switch overs, or if one is moving across timezones,
thus "most of the time".)


From nobody Wed Mar 29 09:30:30 2017
Return-Path: <fujiwara@jprs.co.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 2BBF3129549; Wed, 29 Mar 2017 09:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-rZlri0i5ei; Wed, 29 Mar 2017 09:30:20 -0700 (PDT)
Received: from off-send01.osa.jprs.co.jp (off-send01.osa.jprs.co.jp [IPv6:2001:218:3001:17::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D72EF1243F3; Wed, 29 Mar 2017 09:30:15 -0700 (PDT)
Received: from off-sendsmg01.osa.jprs.co.jp (off-sendsmg01.osa.jprs.co.jp [172.23.8.61]) by off-send01.osa.jprs.co.jp (8.14.4/8.14.4) with ESMTP id v2TGUCxX015312; Thu, 30 Mar 2017 01:30:12 +0900
Received: from off-sendsmg01.osa.jprs.co.jp (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 816AF180064; Thu, 30 Mar 2017 01:30:10 +0900 (JST)
Received: from localhost (off-cpu05.osa.jprs.co.jp [172.23.4.15]) by off-sendsmg01.osa.jprs.co.jp (Postfix) with ESMTP id 6C5F0180062; Thu, 30 Mar 2017 01:30:10 +0900 (JST)
Date: Thu, 30 Mar 2017 01:30:10 +0900 (JST)
Message-Id: <20170330.013010.111206076393335798.fujiwara@jprs.co.jp>
To: jouni.nospam@gmail.com
Cc: ops-dir@ietf.org, dnsop@ietf.org, ietf@ietf.org, draft-ietf-dnsop-nsec-aggressiveuse.all@ietf.org
Subject: Re: [DNSOP] Review of draft-ietf-dnsop-nsec-aggressiveuse-08
From: fujiwara@jprs.co.jp
In-Reply-To: <149063698126.30570.4959246116267967756@ietfa.amsl.com>
References: <149063698126.30570.4959246116267967756@ietfa.amsl.com>
X-Mailer: Mew version 6.5 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1690-8.1.0.1062-22972.007
X-TM-AS-Result: No--1.579-5.0-31-10
X-imss-scan-details: No--1.579-5.0-31-10
X-TMASE-MatchedRID: I5Fk1qs03HZCXIGdsOwlUu5i6weAmSDKZggZX8gYmrWObf10apLcSYu3 renu5Y0wMEy6Wuy7Ct700AgBAXs4SDJz3NGP4sGiDPhWwJzVhb60NJ9wxH7tk4KwF4K/wIz96dX KvERZ4p2t2gtuWr1Lmu47aD4Eo6Bix3+VDjLVh5QdxBAG5/hkW8nlJe2gk8vI/RM/+SKR6qcP65 UmIJNL5L4hC3jqtx/XHHX4BkBfkXmMkVxV9HfBrk1rhQ5+QlI0+KgiyLtJrSCY5NBG7YIbV66Vr pWAb3te4vM1YF6AJbZcLc3sLtjOt1ZFWWuOwo7wMM4ioayl4t151TqU12Mb2uloYgzjonrsro1U RZJFbJtjOpwWsqMi2XW10lvR22DEn+w6tI06i1IYPdI6KnbaYyT72kg3esYp8wkfUH0RC3ZL1Xd OlixYVfoyHrcxti9vnX+P461qsDhKemLhqA7Wjm4DIJPw+zue1PeR9HWWCpTMJ5bhTjeL1cOC91 ofseCc
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fbAKaKdjcBMGNfd-4ZRenSZ4_2c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 16:30:23 -0000

Thanks for the review

> From: Jouni Korhonen <jouni.nospam@gmail.com>
> Reviewer: Jouni Korhonen
> Review result: Has Nits
> 
> I think would be ready if it passed IDnits. I found the document good
> read and found no sinkholes in it. Pointing up two implementations was
> also great.
> 
> The Proto Write-up seems not be up to date with what IDnits says e.g.,
> when it comes to downrefs, which is what the IDnits complain about.
> 
> A couple of editorials:
> 
> Lines 118-119 says: "This takes this.." I would reword to something
> like:
>    "This document takes using NXDOMAIN information for more effective
> caching further."
> 
> Lines 396 and 397 uses "is NOT" and "IS making". I would use lower
> case here. No reason to use capitalized and still non-RFC2119
> language.

I will update the parts.

> Line 407 is would be great to indicate since which version of Unbound
> support has been in place.

It is my edit mistake. Unbound does not implement "Aggressive use of
DNSSEC-validated Cache" now.

  See: https://mailarchive.ietf.org/arch/msg/dnsop/Iv1mxko-ZtUBkNWPZnnnwT9LR-A

# I implemented NSEC only version using Unbound three years ago as a patch.

--
Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>


From nobody Wed Mar 29 11:35:17 2017
Return-Path: <willi.uebelherr@riseup.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 1CDF3120046 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 11:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OORMmlE6SZk5 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 11:35:01 -0700 (PDT)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A26B51293E4 for <ietf@ietf.org>; Wed, 29 Mar 2017 11:34:47 -0700 (PDT)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id D58861A2266; Wed, 29 Mar 2017 18:34:46 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1490812487; bh=735FpxV/D9y1LxFnfEGgiGydGzPepPLOO517nijKx5c=; h=From:Subject:References:To:Cc:Date:In-Reply-To:From; b=E8NCN5miBYKatAeSzuX8ho42x3plRBI82qgR9NqAL3sr6Isb9rPIMgEzV07PlhxGk giAmF7dDp5QVoKjfDJT/Ak5KGbnpWAfQ2Il/EvEp2tGngChzeDJLT82cpcMq9DxU6k I94e2iIblTCgx46j2QW67OSQ2j0BUHcSEOMn8Y8Q=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id DC88B1C0633
From: willi uebelherr <willi.uebelherr@riseup.net>
Subject: Robert Steele: Details on NSA Backdoor in INTEL Chips
References: <80744451.124562.0@wordpress.com>
To: ISOC Internet Policy <internetpolicy@elists.isoc.org>
Cc: IETF discussion <ietf@ietf.org>, IRTF discuss <irtf-discuss@irtf.org>, IRTF gaia <gaia@irtf.org>, IGF gov <governance@lists.igcaucus.org>, IGF dc <dc@intgovforum.org>, Best Bits <bestbits@lists.bestbits.net>, IUF list <iuf@lists.riseup.net>
Message-ID: <0f651625-8559-6c3d-060b-7e54230b3755@riseup.net>
Date: Wed, 29 Mar 2017 15:34:36 -0300
MIME-Version: 1.0
In-Reply-To: <80744451.124562.0@wordpress.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-xgoIX9Lf2oLOHK22U9suTsLSPk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 18:35:13 -0000

Robert Steele: Details on NSA Backdoor in INTEL Chips
http://phibetaiota.net/2017/03/robert-steele-details-on-nsa-backdoor-in-intel-chips/

DuckDuckGo search: NSA backdoor INTEL
https://duckduckgo.com/?q=NSA+backdoor+INTEL&t=ha&ia=web

Expert Says NSA Have Backdoors Built Into Intel And AMD Processors
http://www.eteknix.com/expert-says-nsa-have-backdoors-built-into-intel-and-amd-processors/

Intel ME dumpintel and comments
http://boards.4chan.org/pol/thread/117886401/intel-me


Dear friends,

many of us speak and write about encryption, about surveillance, about 
external control. Intel and Samsung, maybe also AMD, IBM/Motorola and 
others, have it installed. The underlayer between OS and hardware. 
Totally controlled from outside and independent of BIOS and OS.

Intel implemented it in the i3, i5, i7. Personal PC environment. And 
servers and workstation? I am sure, it is the same.

The decryption of the encryption makes too much effort. With ME it is 
easy and allways working. This is the reality, not the future.

Our possible answer: Free technology.

many greetings, willi



-------- Forwarded Message --------
Subject: [New post] Robert Steele: Details on NSA Backdoor in INTEL Chips
Date: Wed, 29 Mar 2017 11:58:39 +0000
From: Public Intelligence Blog <donotreply@wordpress.com>
To: willi.uebelherr@gmail.com

Post       : Robert Steele: Details on NSA Backdoor in INTEL Chips
URL        : 
http://phibetaiota.net/2017/03/robert-steele-details-on-nsa-backdoor-in-intel-chips/
Posted     : March 29, 2017 at 8:00 am
Author     : Editor
Categories : Corruption, Government

I have consulted with my senior NSA colleagues and they validate this 
information.

http://phibetaiota.net/wp-content/uploads/2017/03/Intel-Inside.jpg


_______________________________________________
Discussion mailing list
Discussion@lists.fsfe.org
https://lists.fsfe.org/mailman/listinfo/discussion


From nobody Wed Mar 29 14:01:47 2017
Return-Path: <tobias.gondrom@gondrom.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 DA40A12997E; Wed, 29 Mar 2017 14:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=tobias.gondrom@gondrom.org header.d=gondrom.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6cmXTTSFBTfz; Wed, 29 Mar 2017 14:01:42 -0700 (PDT)
Received: from gondrom.org (www.gondrom.org [5.35.241.16]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D602B1298CC; Wed, 29 Mar 2017 14:01:41 -0700 (PDT)
Received: from seraph (dhcp-8443.meeting.ietf.org [31.133.132.67]) by gondrom.org (Postfix) with ESMTPSA id B19D9649A9; Wed, 29 Mar 2017 23:01:37 +0200 (CEST)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=DaSVBv82k25qQToL7/5VllHjv2YwlXSBrgiUaaUTXUIf5TZGNbNj7hS7hUU9O6mo6feijvdOJckoWFoTZ9RnerjQpK+O5Wl5GMwy14r+xEK/4lttsvX6h5TyMu2KCfofHW9SDsrzgMTzeF0pdYwHMcuTuZYI0TRTOI4Wey74/Kw=; h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language;
From: "Tobias Gondrom" <tobias.gondrom@gondrom.org>
To: "'IETF discussion list'" <ietf@ietf.org>, "'IETF Announcement List'" <ietf-announce@ietf.org>
Subject: IETF Trust report updates
Date: Wed, 29 Mar 2017 16:01:35 -0500
Message-ID: <040a01d2a8cf$a8ab7030$fa025090$@gondrom.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_040B_01D2A8A5.BFD6C7C0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdKozhjzS+/p5us5TmufKDSKMjtL2w==
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pxyJUPb64nHRiAsSiULFoQ2SQPI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 21:01:47 -0000

This is a multipart message in MIME format.

------=_NextPart_000_040B_01D2A8A5.BFD6C7C0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Dear IETF community,=20

=20

It is my great pleasure to announce the new IETF Trust chair Kaveh =
Ranjbar.=20

He has newly joined the IAOC and Trust and has been elected as new IETF =
Trust chair during the Trust meeting yesterday.=20

=20

Aligned with the new update oriented format for the plenary, this =
meeting, there will be no IETF Trust report during the plenary.=20

Over the last four months since our last IETF meeting, there have been =
less actions for the Trust, so we like to provide our report information =
this time via the presentation slides and answer any questions you may =
have.=20

You can find the Trust slides as part of the material for the =
Administrative Plenary today.=20

https://www.ietf.org/proceedings/98/slides/slides-98-ietf-sessc-trust-rep=
ort-00.pdf=20

=20

Over the last years, it has been a great honor and pleasure to work with =
all of you and together for our Internet community.=20

And I will be looking forward to working one more year for you as IAOC =
member and Trustee of the IETF Trust.=20

=20

Best regards and see you around, Tobias =F0=9F=98=8A=20

(outgoing IETF Trust Chair)

=20

=20


------=_NextPart_000_040B_01D2A8A5.BFD6C7C0
Content-Type: text/html;
	charset="UTF-8"
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=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal>Dear IETF community, <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>It is my =
great pleasure to announce the new IETF Trust chair Kaveh Ranjbar. =
<o:p></o:p></p><p class=3DMsoNormal>He has newly joined the IAOC and =
Trust and has been elected as new IETF Trust chair during the Trust =
meeting yesterday. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Aligned with =
the new update oriented format for the plenary, this meeting, there will =
be no IETF Trust report during the plenary. <o:p></o:p></p><p =
class=3DMsoNormal>Over the last four months since our last IETF meeting, =
there have been less actions for the Trust, so we like to provide our =
report information this time via the presentation slides and answer any =
questions you may have. <o:p></o:p></p><p class=3DMsoNormal>You can find =
the Trust slides as part of the material for the Administrative Plenary =
today. <o:p></o:p></p><p class=3DMsoNormal><a =
href=3D"https://www.ietf.org/proceedings/98/slides/slides-98-ietf-sessc-t=
rust-report-00.pdf">https://www.ietf.org/proceedings/98/slides/slides-98-=
ietf-sessc-trust-report-00.pdf</a> <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Over the =
last years, it has been a great honor and pleasure to work with all of =
you and together for our Internet community. <o:p></o:p></p><p =
class=3DMsoNormal>And I will be looking forward to working one more year =
for you as IAOC member and Trustee of the IETF Trust. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Best regards =
and see you around, Tobias <span style=3D'font-family:"Segoe UI =
Emoji",sans-serif'>&#128522;</span> <o:p></o:p></p><p =
class=3DMsoNormal>(outgoing IETF Trust Chair)<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_040B_01D2A8A5.BFD6C7C0--


From nobody Wed Mar 29 14:19:42 2017
Return-Path: <phluid61@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 CEF061274D2 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.15
X-Spam-Level: 
X-Spam-Status: No, score=-2.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97y7veeafrPb for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:19:37 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFC4C128CB9 for <ietf@ietf.org>; Wed, 29 Mar 2017 14:19:35 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id l7so7469105ioe.3 for <ietf@ietf.org>; Wed, 29 Mar 2017 14:19:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=/gG/5ErXB0t6ngar1uXWKlvVJBXbFHbeXgTerao1HmY=; b=IIle4e3mUIUTxT9P2+k0tHM7A780sR33+Ydp/Fz70Z7o39urULJYh5JooULMiTvGTt UTIHomNpTKWj/mwXmzz2U7794GxpfN4oHpTp4wx4lyociQas8LPojC570qbl8APrbAGs fy2MKyVBTScrPRQlH5oEFHW7z+v5L3H0g0Po9eVVyRIrK+etPHlZClvXcymVYUcCO34Z ONSZHjZypf0LB6LptIfjBOkmVwQsyXLcUO/+dn+tJACkwxWktjgZKst1s0jKUFJ+7K3H fB9P2VRos9sKsnBM0ldKB7VloRN6HASenUrXp0ku4GOY6p6ISVIPRT7lhfL2D6XN3+W1 AmLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=/gG/5ErXB0t6ngar1uXWKlvVJBXbFHbeXgTerao1HmY=; b=jQCSmirRrHrSkbFdODzbsCdLOhB6lO6R/TinQql9cfMh45yjKJ2ejqrKqKwWvzzJOy Met+cmRrTM6hoc2ajuIsj5Bf8LSER4usV0JuvqEfZY26dwrTShp5ODFCjssdZv6T3xJ+ Vi1WwSr1QQPTieRhyKeCIyKhR2HGEgD7RGFcZvFLvn7AnbSwK/mm/emY3t8Ll+0E4hgA 9mqB/6//aay1k7cbWa50wwojG5UcN5NrgEG9qTZ8I3EjITfgKjpsgmAbaNZKHn0bqqu3 ItzHKYIe0q4RtDGrLaScki7IOkTrVaBXTLrUvzzwgPXGrU6iBgThxMzUZPgMb3taw9rw CDHw==
X-Gm-Message-State: AFeK/H0tzFIyAzioDEwxL2Wn3ChLsmCHV+GQYdJH6DY66a5kYHDKkAlhhAvKwGrBcarqBv4WSKJSQG0KCBNDLQ==
X-Received: by 10.107.11.35 with SMTP id v35mr3071937ioi.86.1490822375402; Wed, 29 Mar 2017 14:19:35 -0700 (PDT)
MIME-Version: 1.0
Sender: phluid61@gmail.com
Received: by 10.107.154.7 with HTTP; Wed, 29 Mar 2017 14:19:34 -0700 (PDT)
Received: by 10.107.154.7 with HTTP; Wed, 29 Mar 2017 14:19:34 -0700 (PDT)
In-Reply-To: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net>
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net>
From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Thu, 30 Mar 2017 07:19:34 +1000
X-Google-Sender-Auth: JQjlxCy5OuhvpKMgyHxE-P8OYk0
Message-ID: <CACweHND9_9x7ZBc0_95keKbkQt8bz6YLJBP06qE=y=-S=GNDRg@mail.gmail.com>
Subject: Re: Getting the latest version of an RFC specification
To: Dave Crocker <dcrocker@bbiw.net>
Cc: IETF general list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113df9b81bf507054be5220c
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yu6bziDYgP9RARC9VOIpmGu4xeM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 21:19:41 -0000

--001a113df9b81bf507054be5220c
Content-Type: text/plain; charset=UTF-8

On 29 Mar 2017 21:52, "Dave Crocker" <dhc@dcrocker.net> wrote:

G'day.

The RFC labeling model is to assign a unique serial number to a static
document.  A new version of a spec gets a new serial number. This basic
model has the benefit of both simplicity and predictability.

To this we've added an overlay model, using Obsoletes/ObsoletedBy. This
makes it dramatically easier to see that something has been obsoleted and
to find its replacement.

However the seeing and the finding are an essentially manual process. One
must go to the online older document, then notice the Obsoleted By tag and
then click to follow it.

Sometimes it would be helpful for the requester to be able to say 'give me
the latest' more easily.

So I'm wondering whether the IETF should consider adding a citation feature
for this.

Something like:

     https://tools.ietf.org/html/rfc822/latest

would display the contents of:

     https://tools.ietf.org/html/rfc5322

by having the fetching system automatically traversing the Obsoleted By
links in RFC 822 and then RFC 2822.

Some sort of display banner would flag this, to help the user see that they
are getting a different version than they cited.


Thoughts?

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


It sounds good, for the most part, as a quick and dirty tool (though a 30x
redirect would probably be better than displaying the ultimate RFC
in-place.)

Out of malign curiosity, what would you expect from:
https://tools.ietf.org/html/rfc1738/latest
<https://tools.ietf.org/html/rfc822/latest> ?

Cheers

--001a113df9b81bf507054be5220c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On 29 Mar 2017 21:52, &quot;Dave Crocker&quot; &lt;<a href=3D"mailto:=
dhc@dcrocker.net">dhc@dcrocker.net</a>&gt; wrote:<br type=3D"attribution"><=
blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">G&#39;day.<br>
<br>
The RFC labeling model is to assign a unique serial number to a static docu=
ment.=C2=A0 A new version of a spec gets a new serial number. This basic mo=
del has the benefit of both simplicity and predictability.<br>
<br>
To this we&#39;ve added an overlay model, using Obsoletes/ObsoletedBy. This=
 makes it dramatically easier to see that something has been obsoleted and =
to find its replacement.<br>
<br>
However the seeing and the finding are an essentially manual process. One m=
ust go to the online older document, then notice the Obsoleted By tag and t=
hen click to follow it.<br>
<br>
Sometimes it would be helpful for the requester to be able to say &#39;give=
 me the latest&#39; more easily.<br>
<br>
So I&#39;m wondering whether the IETF should consider adding a citation fea=
ture for this.<br>
<br>
Something like:<br>
<br>
=C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/rfc822/latest" r=
el=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/r<wbr>fc822=
/latest</a><br>
<br>
would display the contents of:<br>
<br>
=C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/rfc5322" rel=3D"=
noreferrer" target=3D"_blank">https://tools.ietf.org/html/r<wbr>fc5322</a><=
br>
<br>
by having the fetching system automatically traversing the Obsoleted By lin=
ks in RFC 822 and then RFC 2822.<br>
<br>
Some sort of display banner would flag this, to help the user see that they=
 are getting a different version than they cited.<br>
<br>
<br>
Thoughts?<font color=3D"#888888"><br>
<br>
d/<br>
-- <br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" rel=3D"noreferrer" target=3D"_blank">bbiw.net</=
a><br>
<br>
</font></blockquote></div><br></div></div><div class=3D"gmail_extra" dir=3D=
"auto">It sounds good, for the most part, as a quick and dirty tool (though=
 a 30x redirect would probably be better than displaying the ultimate RFC i=
n-place.)</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div class=
=3D"gmail_extra" dir=3D"auto">Out of malign curiosity, what would you expec=
t from:=C2=A0<a href=3D"https://tools.ietf.org/html/rfc822/latest" style=3D=
"font-family:sans-serif">https://tools.ietf.org/html/rfc1738/latest</a>=C2=
=A0?</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"g=
mail_extra" dir=3D"auto">Cheers</div></div>

--001a113df9b81bf507054be5220c--


From nobody Wed Mar 29 14:25:57 2017
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 EB718129486 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvbxB6qcenmk for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:25:54 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B833B12945D for <ietf@ietf.org>; Wed, 29 Mar 2017 14:25:54 -0700 (PDT)
Received: from [31.133.143.184] (dhcp-8fb8.meeting.ietf.org [31.133.143.184]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2TLRs7T026709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Mar 2017 14:27:58 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490822880; bh=2alVNcq49Rj3501XhE1+nASZODW+m+dKIzchmlW5ck0=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=ja9IATTIjzvBQp/h4pZ0VnWpy3Iw48DGHx0sHEcLhOiY4EIKhcrhR4zq3japGN7MA Ep9IsS5VEw+D+rbqGD1XASDVWoO2x8Zy7O2T6gzGFgMs0im2B2RmiD3NRKhEhxPCxy vFd7G2IyZqjagwGRgXhUC7mVV8c/GAPx7us7/9uU=
Subject: Re: Getting the latest version of an RFC specification
To: Matthew Kerwin <matthew@kerwin.net.au>
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net> <CACweHND9_9x7ZBc0_95keKbkQt8bz6YLJBP06qE=y=-S=GNDRg@mail.gmail.com>
Cc: IETF general list <ietf@ietf.org>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <c7a4c153-1202-4490-92ea-f119e6702489@dcrocker.net>
Date: Wed, 29 Mar 2017 16:25:43 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CACweHND9_9x7ZBc0_95keKbkQt8bz6YLJBP06qE=y=-S=GNDRg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QOhVByIxKJYq_tACGdXtqUA8kfc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 21:25:56 -0000

On 3/29/2017 4:19 PM, Matthew Kerwin wrote:
> Out of malign curiosity, what would you expect
> from: https://tools.ietf.org/html/rfc1738/latest
> <https://tools.ietf.org/html/rfc822/latest> ?


cool!  bifurcated obsolescence.  show both 'latest' documents at the 
same time?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Mar 29 14:35:35 2017
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26D8212948C for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yO1149xaji7L for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:35:31 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF729129440 for <ietf@ietf.org>; Wed, 29 Mar 2017 14:35:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id A733B7C6503 for <ietf@ietf.org>; Wed, 29 Mar 2017 23:35:29 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i_l0xIEyk4KX for <ietf@ietf.org>; Wed, 29 Mar 2017 23:35:29 +0200 (CEST)
Received: from [IPv6:2001:67c:370:128:5dc2:e048:33d5:8fed] (t2001067c037001285dc2e04833d58fed.v6.meeting.ietf.org [IPv6:2001:67c:370:128:5dc2:e048:33d5:8fed]) by mork.alvestrand.no (Postfix) with ESMTPSA id 9B2DF7C6502 for <ietf@ietf.org>; Wed, 29 Mar 2017 23:35:28 +0200 (CEST)
Subject: Re: Predictable Internet Time
To: ietf@ietf.org
References: <m1cOYZ6-0000FAC@stereo.hq.phicoh.net> <bf1a0b49-6f76-1ec8-0a70-bfff9be40c16@alvestrand.no> <20170329155649.GS7490@localhost>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <c71146d8-f17c-59ea-f093-a3b02f6a1946@alvestrand.no>
Date: Wed, 29 Mar 2017 23:35:25 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <20170329155649.GS7490@localhost>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FlH-9F9XtZ_881zYwIYLnP7WHkc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 21:35:34 -0000

On 03/29/2017 05:56 PM, Nico Williams wrote:
> On Wed, Jan 04, 2017 at 09:49:35AM +0100, Harald Alvestrand wrote:
>> FWIW, the W3C has switched to defining time inside a Web page in two
>> segments:
>> - Page load time, which is UTC-derived (POSIX time extended to
>> milliseconds), and can jump when the system clock is reset
>> - Events related to the page load time, which has floating-point
>> representation, and is guaranteed to be monotonic.
> But aren't these relative times (intervals)?  As long as they are short
> enough, distinctions between UTC, TAI, local, and smeared time will make
> little difference most of the time.  (Naturally, using local time might
> cause a page load time to appear to be negative, or over an hour, around
> daylight savings switch overs, or if one is moving across timezones,
> thus "most of the time".)
>
The first is an absolute time. The second is relative.


-- 
Surveillance is pervasive. Go Dark.


From nobody Wed Mar 29 14:40:38 2017
Return-Path: <ynir.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 A9B99127071 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:40:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYzVMEcA9XRp for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:40:34 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75C951250B8 for <ietf@ietf.org>; Wed, 29 Mar 2017 14:40:34 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id e75so102064096itd.1 for <ietf@ietf.org>; Wed, 29 Mar 2017 14:40:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=yjmOPmXGf48sI7DI7TVV+jMKmyYCOG4YLlmEVkT02iI=; b=N8KeVEhBrhM7icwkH4bSFgF8pIuo9y5jFVoPGXqkg+69R0F1lrOAO5YwO44h5y22zB 9d2WiYP9v2WGMML42GGBBOG+hCf/55zziF67ZQrhXf8hawKSWOWnKg6fxdjnINZUjbcK 6ExR+yGHLN9N53cQL1qSSf4Qse5BayD/WhLvo++EOfFm/fbaZ+tNv4K2yJoX9mIk8S4w EoxXgP9jAdK5xrs5BVIIjLX/7MubVby60aDoHmwPG1EXpvL8PenxuqVwAchQq5Oq6Ivy 0DYlz5MGjkBmKUnbOobASjhAy7gRCDYVSkW3PfnG6ZBEZNVPyG02jmtYqDZLNndhXlt5 /McA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=yjmOPmXGf48sI7DI7TVV+jMKmyYCOG4YLlmEVkT02iI=; b=Mbuz3tC0awW1XMe9IOhNPCFERiaJ4EC802ANLYuJGBDR2n9LHDhSZgLlH8A16mOqA8 d6Hjo0+f1J+M8UCOVODwcPbzlzzGz5d+tElqPHjE6VoYJFgUTwbr1bhBmariQp6jlLEa i7GonXk8h1Z3vBrVMVy3ZmRoo9aWGVYD4UD4dC70Ysgrkg0+L2ohFJDOyr+ThPE6Wpk2 yXuHoUUlJgyEpxfQq2yzgTUbu7JEJW1k33kAlgTzghtr9Sn5ntFYE58CQUDZDCW95nrh +CPD8ZSnbKsfcwlgBOag8zNQNKMrY9WuyTJitCcvMtz8tPyjCi+QOmrr0lXoLIqGO4qe 8r6Q==
X-Gm-Message-State: AFeK/H0tcQUtjZE3VVwcqazWVoSseC6JbCsb3HKr7Jw7FJi+hcFRfdV4UyFMMQoZiVfdMQ==
X-Received: by 10.36.144.132 with SMTP id x126mr603434itd.35.1490823633898; Wed, 29 Mar 2017 14:40:33 -0700 (PDT)
Received: from t2001067c03700128f5d7507edd3635c6.v6.meeting.ietf.org (t2001067c03700128f5d7507edd3635c6.v6.meeting.ietf.org. [2001:67c:370:128:f5d7:507e:dd36:35c6]) by smtp.gmail.com with ESMTPSA id 86sm284878iom.58.2017.03.29.14.40.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 14:40:33 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <C48761FC-E4C1-4951-ABF0-162B298135DA@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F8DEBBD4-3D26-4F19-885F-F23541C422F3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Getting the latest version of an RFC specification
Date: Wed, 29 Mar 2017 16:40:31 -0500
In-Reply-To: <CACweHND9_9x7ZBc0_95keKbkQt8bz6YLJBP06qE=y=-S=GNDRg@mail.gmail.com>
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF general list <ietf@ietf.org>
To: Matthew Kerwin <matthew@kerwin.net.au>
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net> <CACweHND9_9x7ZBc0_95keKbkQt8bz6YLJBP06qE=y=-S=GNDRg@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zhY7W9IqEbQt3u5c2t4TBKeK0YU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 21:40:37 -0000

--Apple-Mail=_F8DEBBD4-3D26-4F19-885F-F23541C422F3
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_7145AD1E-E351-4573-882B-188352F74A2B"


--Apple-Mail=_7145AD1E-E351-4573-882B-188352F74A2B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 29 Mar 2017, at 16:19, Matthew Kerwin <matthew@kerwin.net.au> =
wrote:
>=20
>=20
> On 29 Mar 2017 21:52, "Dave Crocker" <dhc@dcrocker.net =
<mailto:dhc@dcrocker.net>> wrote:
> G'day.
>=20
> The RFC labeling model is to assign a unique serial number to a static =
document.  A new version of a spec gets a new serial number. This basic =
model has the benefit of both simplicity and predictability.
>=20
> To this we've added an overlay model, using Obsoletes/ObsoletedBy. =
This makes it dramatically easier to see that something has been =
obsoleted and to find its replacement.
>=20
> However the seeing and the finding are an essentially manual process. =
One must go to the online older document, then notice the Obsoleted By =
tag and then click to follow it.
>=20
> Sometimes it would be helpful for the requester to be able to say =
'give me the latest' more easily.
>=20
> So I'm wondering whether the IETF should consider adding a citation =
feature for this.
>=20
> Something like:
>=20
>      https://tools.ietf.org/html/rfc822/latest =
<https://tools.ietf.org/html/rfc822/latest>
>=20
> would display the contents of:
>=20
>      https://tools.ietf.org/html/rfc5322 =
<https://tools.ietf.org/html/rfc5322>
>=20
> by having the fetching system automatically traversing the Obsoleted =
By links in RFC 822 and then RFC 2822.
>=20
> Some sort of display banner would flag this, to help the user see that =
they are getting a different version than they cited.
>=20
>=20
> Thoughts?
>=20
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net <http://bbiw.net/>
>=20
>=20
> It sounds good, for the most part, as a quick and dirty tool (though a =
30x redirect would probably be better than displaying the ultimate RFC =
in-place.)
>=20
> Out of malign curiosity, what would you expect from: =
https://tools.ietf.org/html/rfc1738/latest =
<https://tools.ietf.org/html/rfc822/latest> ?

That one is terribly wrong. Generic URL is obsoleted by the telnet URL =
and the Gopher URL?  And then, after being =E2=80=9Cobsoleted", it is =
still updated by three separate RFCs, the latest of which 12 years =
later?

But there are examples that are properly tagged.  =
https://tools.ietf.org/html/rfc2616 =
<https://tools.ietf.org/html/rfc2616> is obsoleted by a series of six =
RFCs.

Yoav


--Apple-Mail=_7145AD1E-E351-4573-882B-188352F74A2B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 29 Mar 2017, at 16:19, Matthew Kerwin &lt;<a =
href=3D"mailto:matthew@kerwin.net.au" =
class=3D"">matthew@kerwin.net.au</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"auto" =
class=3D""><div class=3D""><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On 29 Mar 2017 21:52, "Dave Crocker" &lt;<a =
href=3D"mailto:dhc@dcrocker.net" class=3D"">dhc@dcrocker.net</a>&gt; =
wrote:<br type=3D"attribution" class=3D""><blockquote class=3D"quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">G'day.<br class=3D"">
<br class=3D"">
The RFC labeling model is to assign a unique serial number to a static =
document.&nbsp; A new version of a spec gets a new serial number. This =
basic model has the benefit of both simplicity and predictability.<br =
class=3D"">
<br class=3D"">
To this we've added an overlay model, using Obsoletes/ObsoletedBy. This =
makes it dramatically easier to see that something has been obsoleted =
and to find its replacement.<br class=3D"">
<br class=3D"">
However the seeing and the finding are an essentially manual process. =
One must go to the online older document, then notice the Obsoleted By =
tag and then click to follow it.<br class=3D"">
<br class=3D"">
Sometimes it would be helpful for the requester to be able to say 'give =
me the latest' more easily.<br class=3D"">
<br class=3D"">
So I'm wondering whether the IETF should consider adding a citation =
feature for this.<br class=3D"">
<br class=3D"">
Something like:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp;<a href=3D"https://tools.ietf.org/html/rfc822/latest" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/r<wbr =
class=3D"">fc822/latest</a><br class=3D"">
<br class=3D"">
would display the contents of:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp;<a href=3D"https://tools.ietf.org/html/rfc5322" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/r<wbr class=3D"">fc5322</a><br =
class=3D"">
<br class=3D"">
by having the fetching system automatically traversing the Obsoleted By =
links in RFC 822 and then RFC 2822.<br class=3D"">
<br class=3D"">
Some sort of display banner would flag this, to help the user see that =
they are getting a different version than they cited.<br class=3D"">
<br class=3D"">
<br class=3D"">
Thoughts?<font color=3D"#888888" class=3D""><br class=3D"">
<br class=3D"">
d/<br class=3D"">
-- <br class=3D"">
Dave Crocker<br class=3D"">
Brandenburg InternetWorking<br class=3D"">
<a href=3D"http://bbiw.net/" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">bbiw.net</a><br class=3D"">
<br class=3D"">
</font></blockquote></div><br class=3D""></div></div><div =
class=3D"gmail_extra" dir=3D"auto">It sounds good, for the most part, as =
a quick and dirty tool (though a 30x redirect would probably be better =
than displaying the ultimate RFC in-place.)</div><div =
class=3D"gmail_extra" dir=3D"auto"><br class=3D""></div><div =
class=3D"gmail_extra" dir=3D"auto">Out of malign curiosity, what would =
you expect from:&nbsp;<a =
href=3D"https://tools.ietf.org/html/rfc822/latest" =
style=3D"font-family:sans-serif" =
class=3D"">https://tools.ietf.org/html/rfc1738/latest</a>&nbsp;?</div></di=
v></div></blockquote><div><br class=3D""></div></div>That one is =
terribly wrong. Generic URL is obsoleted by the telnet URL and the =
Gopher URL? &nbsp;And then, after being =E2=80=9Cobsoleted", it is still =
updated by three separate RFCs, the latest of which 12 years later?<div =
class=3D""><br class=3D""></div><div class=3D"">But there are examples =
that are properly tagged. &nbsp;<a =
href=3D"https://tools.ietf.org/html/rfc2616" =
class=3D"">https://tools.ietf.org/html/rfc2616</a>&nbsp;is obsoleted by =
a series of six RFCs.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Yoav</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_7145AD1E-E351-4573-882B-188352F74A2B--

--Apple-Mail=_F8DEBBD4-3D26-4F19-885F-F23541C422F3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJY3CnPAAoJELhJCxUKWMyZuzUH+gNjpoFKAjageAXwDFaWVLwZ
fMp2eqRGoeCEsslisO3Tc5vd0n+xZjB/L4mX6yrFJQ6Mx/Ef3iRXMMGnizdyVP2r
LCYFsV6n0xhtNbbbzy/mFghx8i8F6j+vLhVUDrlv0lbueEgY6pRKlb+MgGGnBuVM
YpLvSXUsxHu2rADHMcVuRFh8hc4gjuDpmAx6JkrO/I59blXeusN+87FYtM9Ldmkv
Q5rXNEjsCara7E8n2e+6Jk4hSdFOgWFnBjNUAEUue3Amq3tuOCYAOdUv66o1ng+D
yTwNtn2LLPd6fU3YJTg3r8rd4m40AVfLj1aInxMPulUuhaEOwXWmYbU4xvvQBMk=
=WQDK
-----END PGP SIGNATURE-----

--Apple-Mail=_F8DEBBD4-3D26-4F19-885F-F23541C422F3--


From nobody Wed Mar 29 14:44:22 2017
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 21A591250B8 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6YbJ-wOCNFIi for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 14:44:18 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE2D3127775 for <ietf@ietf.org>; Wed, 29 Mar 2017 14:44:18 -0700 (PDT)
Received: from [31.133.143.184] (dhcp-8fb8.meeting.ietf.org [31.133.143.184]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2TLkLTl027055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Mar 2017 14:46:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490823983; bh=h9HLEPDt2mZI9AsXojsVFo3waddEX5KfBr80V0gpGf0=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=pbfkvHbvcVjCp2mXLKCdXosHa7/EoBRmpR4phui6Se8oFhz/xszC3Lh1lMEQp5zJY wluToWi5fcZ2haboVkv4Cbun8Ga9TbiRQjRDwGDXUQHk5k4v25JrdrS31256YsG5JV Z0Sq7SbWNkNXXobBTGbueORHB/z/dWxR9yGo2nnc=
Subject: Re: Getting the latest version of an RFC specification
To: Yoav Nir <ynir.ietf@gmail.com>, Matthew Kerwin <matthew@kerwin.net.au>
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net> <CACweHND9_9x7ZBc0_95keKbkQt8bz6YLJBP06qE=y=-S=GNDRg@mail.gmail.com> <C48761FC-E4C1-4951-ABF0-162B298135DA@gmail.com>
Cc: IETF general list <ietf@ietf.org>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <9437d845-ff46-3c02-f842-1ed1fae7f54b@dcrocker.net>
Date: Wed, 29 Mar 2017 16:44:08 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <C48761FC-E4C1-4951-ABF0-162B298135DA@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/d0ywIIyXb2tpA8dJTRSiGEB0vuc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 21:44:20 -0000

On 3/29/2017 4:40 PM, Yoav Nir wrote:
> But there are examples that are properly tagged.
>  https://tools.ietf.org/html/rfc2616 is obsoleted by a series of six RFCs.

So to attempt a more serious suggestion -- remembering that the whole 
idea here was KISS:  If the Obsoleted-By field contains multiple 
pointers, then present this fact to the user and request that the select 
one.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Mar 29 15:04:13 2017
Return-Path: <ynir.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 4E146126C2F for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 15:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6I1NykbamPTM for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 15:04:10 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6641126DDF for <ietf@ietf.org>; Wed, 29 Mar 2017 15:04:08 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id f84so8026882ioj.0 for <ietf@ietf.org>; Wed, 29 Mar 2017 15:04:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=4kN+sfeyUEb//g06D5wyTdHfGNSySOQkziCbOzN1hbY=; b=FJXwfPUKyuMCjMM8pZFtduxhpLcy3f2Ycs6bW1kjUTdouEDdg5pw+W1n2Ct79CeXTZ 38C24hVz1YavNyuOG8JL8PP89uaACmKzgmC8Wz1OngTtvtzMgoV8kir9oM2823n6fEcE +SApx8BdkSiqUfoa3MCj2CQwkM3Ko6qy+itF4YjqgpPnti/sRWFlRBqiW3xCKf7pYVgK R/OlEluXRsBbggOi+0FhOdpwftpahpQ+/EFCVup9+pEWzEecGb+9t+/Joma81lbBjwFS /KYDkloANwnW2DsEIVGxeQUg3ZyKfeprWBEB5+HHxER5+x/QdPg51cxZu4hzolPvWJmL oW6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=4kN+sfeyUEb//g06D5wyTdHfGNSySOQkziCbOzN1hbY=; b=Zk1bhKMwJBL6kTt89GBbCcSDNa/wEvhWicu4ZR62EMcADiPiduci8NQ4nwfKyqc/Fc fNkl2MoIOMuAW5YCL75dozin2x/GntvCtsx3leX4LG5/jtW55/Vc+WaSXLcgzHwKiTSr +h4cYKyatmtQmWrBK1GkHJL7N6FuG8gsm9ZGKebL4NvJhMHAvdSYJ3dIL9GOxbmKw6CM yDIlcKmKQkG2GtX9imU6M+MWzeZHW09Yh0HLvmanWtZ9LNsMxO9eY0CRTNKJKtnxsEVL 6fpOAFM3J/7W4+FH2Ja/97x+Ncns60eZe+hRsNOLXhXksE9iBFTP6KNna/nzzpuQnv/J hdtg==
X-Gm-Message-State: AFeK/H2kQAhKquC/fzUuWBhX31cg1ziG4TDgl152H5J7+zwvzjXWBHf5GwUSxptE2eFnPg==
X-Received: by 10.107.132.155 with SMTP id o27mr3141315ioi.138.1490825048048;  Wed, 29 Mar 2017 15:04:08 -0700 (PDT)
Received: from t2001067c03700128f5d7507edd3635c6.v6.meeting.ietf.org (t2001067c03700128f5d7507edd3635c6.v6.meeting.ietf.org. [2001:67c:370:128:f5d7:507e:dd36:35c6]) by smtp.gmail.com with ESMTPSA id 33sm317545ios.54.2017.03.29.15.04.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 15:04:07 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <2FF66A0A-EC38-4915-A987-3F81424D29AF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E62268DD-ED66-4538-A518-1B0A1F75F6C7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Getting the latest version of an RFC specification
Date: Wed, 29 Mar 2017 17:04:06 -0500
In-Reply-To: <9437d845-ff46-3c02-f842-1ed1fae7f54b@dcrocker.net>
Cc: Matthew Kerwin <matthew@kerwin.net.au>, IETF general list <ietf@ietf.org>
To: dcrocker@bbiw.net
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net> <CACweHND9_9x7ZBc0_95keKbkQt8bz6YLJBP06qE=y=-S=GNDRg@mail.gmail.com> <C48761FC-E4C1-4951-ABF0-162B298135DA@gmail.com> <9437d845-ff46-3c02-f842-1ed1fae7f54b@dcrocker.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y_dJn4yo-ufA-2RLK5vCxsU5hlc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Mar 2017 22:04:12 -0000

--Apple-Mail=_E62268DD-ED66-4538-A518-1B0A1F75F6C7
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_105A900E-7EA2-45CF-A905-6F24B5216FA1"


--Apple-Mail=_105A900E-7EA2-45CF-A905-6F24B5216FA1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Yeah, like instead of redirecting to the next stop, present a page with =
a list of the obsoleting RFCs (name + title) and a link to each, like:

RFC 2616 is obsoleted by the following RFCs:
   o RFC 7230 <https://tools.ietf.org/html/rfc7230/latest> - Hypertext =
Transfer Protocol (HTTP/1.1): Message Syntax and Routing
   o RFC 7231 <https://tools.ietf.org/html/rfc7231/latest> - Hypertext =
Transfer Protocol (HTTP/1.1): Semantics and Content

and so on=E2=80=A6.

> On 29 Mar 2017, at 16:44, Dave Crocker <dhc@dcrocker.net> wrote:
>=20
> On 3/29/2017 4:40 PM, Yoav Nir wrote:
>> But there are examples that are properly tagged.
>> https://tools.ietf.org/html/rfc2616 is obsoleted by a series of six =
RFCs.
>=20
> So to attempt a more serious suggestion -- remembering that the whole =
idea here was KISS:  If the Obsoleted-By field contains multiple =
pointers, then present this fact to the user and request that the select =
one.
>=20
> d/
>=20
>=20
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


--Apple-Mail=_105A900E-7EA2-45CF-A905-6F24B5216FA1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Yeah, like instead of redirecting to the next stop, present a =
page with a list of the obsoleting RFCs (name + title) and a link to =
each, like:<div class=3D""><br class=3D""></div><div class=3D"">RFC 2616 =
is obsoleted by the following RFCs:</div><div class=3D"">&nbsp; =
&nbsp;o&nbsp;<a href=3D"https://tools.ietf.org/html/rfc7230/latest" =
class=3D"">RFC 7230</a>&nbsp;-&nbsp;<span style=3D"font-size: 1em; =
font-weight: bold;" class=3D"">Hypertext Transfer Protocol (HTTP/1.1): =
Message Syntax and Routing</span></div><div class=3D""><span =
style=3D"font-size: 1em;" class=3D"">&nbsp; &nbsp;o&nbsp;</span><a =
href=3D"https://tools.ietf.org/html/rfc7231/latest" class=3D"">RFC =
7231</a><span style=3D"font-size: 1em;" =
class=3D"">&nbsp;-&nbsp;</span><span style=3D"font-size: 1em; =
font-weight: bold;" class=3D"">Hypertext Transfer Protocol (HTTP/1.1): =
Semantics and Content</span></div><div class=3D""><br =
class=3D""></div><div class=3D"">and so on=E2=80=A6.</div><div =
class=3D""><span style=3D"font-size: 1em; font-weight: bold;" =
class=3D"">&nbsp; &nbsp;</span></div><div class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 29 Mar 2017, at 16:44, Dave =
Crocker &lt;<a href=3D"mailto:dhc@dcrocker.net" =
class=3D"">dhc@dcrocker.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
3/29/2017 4:40 PM, Yoav Nir wrote:<br class=3D""><blockquote type=3D"cite"=
 class=3D"">But there are examples that are properly tagged.<br =
class=3D""> <a href=3D"https://tools.ietf.org/html/rfc2616" =
class=3D"">https://tools.ietf.org/html/rfc2616</a> is obsoleted by a =
series of six RFCs.<br class=3D""></blockquote><br class=3D"">So to =
attempt a more serious suggestion -- remembering that the whole idea =
here was KISS: &nbsp;If the Obsoleted-By field contains multiple =
pointers, then present this fact to the user and request that the select =
one.<br class=3D""><br class=3D"">d/<br class=3D""><br class=3D""><br =
class=3D"">-- <br class=3D"">Dave Crocker<br class=3D"">Brandenburg =
InternetWorking<br class=3D""><a href=3D"http://bbiw.net" =
class=3D"">bbiw.net</a><br class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_105A900E-7EA2-45CF-A905-6F24B5216FA1--

--Apple-Mail=_E62268DD-ED66-4538-A518-1B0A1F75F6C7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJY3C9WAAoJELhJCxUKWMyZMi0IAMouVoU2K+1wWczK7sDaiwbu
d9saIeZbOeLKsBIaiLMmCJoV2n8QNyjjElwNc7L2dtpQsFXmuh9kknw4WMvYRrlU
JrvdhORwrFKoU8ptG8JEiHwbm73Xxs1yiamYXPMF6OkWW/BJ0WIE/ilaMU/erfQL
Z8tkzCM1TVXe7NNgwKdc20wgGk6E4UthoPOVIotpjedKbhNgCMrbcLNblagXARq+
vVXSkgkq43ocR51nYRBjwx/j9d61QkWCFicYN8lKRTHYqMLUAtb4025INTHe9l0Y
5JB89WS4QGKvFI7YIAHVKyD05P7DGJn2CavTJy4wzRpEYuf97LjA5HBUj1H5kw8=
=kUqT
-----END PGP SIGNATURE-----

--Apple-Mail=_E62268DD-ED66-4538-A518-1B0A1F75F6C7--


From nobody Wed Mar 29 19:59:12 2017
Return-Path: <John_Leddy@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 00BAF12949A; Wed, 29 Mar 2017 19:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42BRkpntnVIw; Wed, 29 Mar 2017 19:59:09 -0700 (PDT)
Received: from vaadcmhout02.cable.comcast.com (vaadcmhout02.cable.comcast.com [96.114.28.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DCCE12947F; Wed, 29 Mar 2017 19:59:07 -0700 (PDT)
X-AuditID: 60721c4c-b47ff7000000bcc0-e6-58dc7476d420
Received: from VAADCEX43.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id 2C.52.48320.6747CD85; Wed, 29 Mar 2017 22:59:04 -0400 (EDT)
Received: from VAADCEX41.cable.comcast.com (147.191.103.218) by VAADCEX43.cable.comcast.com (147.191.103.220) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 29 Mar 2017 22:59:01 -0400
Received: from VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268]) by VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268%19]) with mapi id 15.00.1263.000; Wed, 29 Mar 2017 22:59:01 -0400
From: "Leddy, John" <John_Leddy@comcast.com>
To: "suresh.krishnan@ericsson.com" <suresh.krishnan@ericsson.com>
CC: "ietf@ietf.org" <ietf@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSqOd8Ap6Hay13uEWcjbPxwh2xd6GssVmA
Date: Thu, 30 Mar 2017 02:59:01 +0000
Message-ID: <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com>
In-Reply-To: <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.114.156.8]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B45636A149C009428985D2AD8AB2D28B@cable.comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrIIsWRmVeSWpSXmKPExsWSUOxpoVtRcifC4OVyPotXb6+xWTzbOJ/F 4uXZ90wWM+b8ZHdg8fj19Sqbx5IlP5kCmKK4bFJSczLLUov07RK4MrZ0drAUdKhUzLl9j72B cYJyFyMnh4SAicTsnn/sXYxcHEIC25kkGrovMYEkhAQOMUp8WKwIYZ9klFjVlQRiswnoSMyY do0VxBYRcJS4/7KJBaSZWWAuo0Tzuu0sIAlhAQ+JSZuusUAUeUqs23gYyOYAso0kdp+RAwmz CKhKLDj5AmwOr4CLxJymvYwQu4okFsyfyQxicwrYSvSvPQkWZxQQk/h+ag3YbcwC4hK3nsxn gnhAQGLJnvPMELaoxMvH/8BmigroSczc+ZcRIq4jcfb6EyjbQGLr0n0sELaCxPb928BOYxbQ lFi/Sx9ivIPE//2bWCFsRYkp3Q/ZIc4UlDg58wlUq6TEwRU3WCYwSs9CctEshEmzkEyahWTS LCSTFjCyrmKUK0tMTEnOzcgvLTEw0ktOTMpJ1UvOz01OLC4B0ZsYQRFfJOOzg/HTNI9DjAIc jEo8vCH+dyKEWBPLiitzgfHEwawkwqv16XaEEG9KYmVValF+fFFpTmrxIUZpDhYlcV6vm7ci hATSE0tSs1NTC1KLYLJMHJxSDYzWNf7fZ2jvnRl255jak+cHbOu/62tICjEplbPbHO78+fyw SrToie9xe3OeSj/MNeWRyxZWa+1e+f5E/Kc78jUSbpF914J0X3yR4f7HUPRwzaKguv7NPPl+ unb74h+cvvX816RPdlfqLPlOGiunsT5arRo0fU/ykvzvQg8khQ8JMd+eHMPD91iJpTgj0VCL uag4EQAIKSfr9AIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z3so1Wz_PASAE7sePfTt49I63dw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 02:59:11 -0000

PiBPbiBNYXIgMTQsIDIwMTcsIGF0IDk6NDcgUE0sIFN1cmVzaCBLcmlzaG5hbiA8c3VyZXNoLmty
aXNobmFuQGVyaWNzc29uLmNvbT4gd3JvdGU6DQogICAgPiANCiAgICA+IE5FVzoNCiAgICA+IA0K
ICAgID4gV2l0aCBvbmUgZXhjZXB0aW9uLCBleHRlbnNpb24gaGVhZGVycyBhcmUgbm90IGV4YW1p
bmVkLCBwcm9jZXNzZWQsDQogICAgPiBpbnNlcnRlZCwgb3IgZGVsZXRlZCBieSBhbnkgbm9kZSBh
bG9uZyBhIHBhY2tldCdzIGRlbGl2ZXJ5IHBhdGgsDQogICAgPiB1bnRpbCB0aGUgcGFja2V0IHJl
YWNoZXMgdGhlIG5vZGUgKG9yIGVhY2ggb2YgdGhlIHNldCBvZiBub2RlcywgaW4NCiAgICA+IHRo
ZSBjYXNlIG9mIG11bHRpY2FzdCkgaWRlbnRpZmllZCBpbiB0aGUgRGVzdGluYXRpb24gQWRkcmVz
cyBmaWVsZCBvZg0KICAgID4gdGhlIElQdjYgaGVhZGVyLi4uDQogICAgPiANCiAgICA+IFBsZWFz
ZSBmZWVsIGZyZWUgdG8gY29tbWVudCBlaXRoZXIgcHJpdmF0ZWx5IG9yIG9uIGxpc3QgaWYgeW91
IGhhdmUgYW55IGNvbmNlcm5zIHdpdGggdGhpcyByZXNvbHV0aW9uIGdvaW5nIGZvcndhcmQuDQoN
Cg0KU3VyZXNoLA0KDQpJIHN0aWxsIGhhdmUgY29uY2VybnMgdGhhdCB3ZSBhcmUgZWxpbWluYXRp
bmcgYSB0b29sIHRoYXQgbWF5IHByb3ZlIHZlcnkgaGVscGZ1bCBpbiBtaWdyYXRpb25zIHdpdGhv
dXQgdW5kZXJzdGFuZGluZyBpdHMgdmFsdWUuDQoNClRoZSBJbnRlcm5ldCB0cmFuc2l0aW9uIG9m
IElQVjQgLT4gRHVhbCBTdGFjayBWNC9WNiAtPiBJUFY2IE9ubHk7IGhhcyBiZWVuIGxvbmcsIG9w
ZXJhdGlvbmFsbHkgY29tcGxleCBhbmQgZnVsbCBvZiB1bmV4cGVjdGVkIGNoYWxsZW5nZXMuDQpX
ZSBhcmUgb25seSBub3cgc3RhcnRpbmcgdG8gbWFrZSB0aGUgdHJhbnNpdGlvbiBmcm9tIER1YWwg
U3RhY2sgdG8gSVBWNiBPbmx5LCB0aGVyZSBhcmUgc3RpbGwgbWFueSB1bmtub3ducyBvbiBob3cg
dG8gY29tcGxldGUgdGhpcyBtaWdyYXRpb24uDQoNCkFzIHdlIGNvbnRlbXBsYXRlIGZpbmlzaGlu
ZyB0aGlzIG1ham9yIE5ldHdvcmsgc2hpZnQg4oCTIFdlIGZpbmQgb3Vyc2VsdmVzIGluIHRoZSBl
YXJseSBzdGFnZXMgb2YgYW5vdGhlci4NCg0KVGhlIHRyYW5zaXRpb24gZnJvbSBQaHlzaWNhbCB0
byBWaXJ0dWFsIEluZnJhc3RydWN0dXJlLiAgQWdhaW4sIHRoZSBtaWdyYXRpb24gd2lsbCBiZSBs
b25nLCBvcGVyYXRpb25hbGx5IGNvbXBsZXggYW5kIGZ1bGwgb2YgdW5leHBlY3RlZCBjaGFsbGVu
Z2VzLg0KDQpJbiB0aGUgb2xkIHdvcmxkIHdpdGggU2VydmVycyBydW5uaW5nIEFwcGxpY2F0aW9u
cyBpbiBQaHlzaWNhbCBsb2NhdGlvbnMgZGVzaWduZWQgZm9yIHZlcnkgcHJlZGljdGFibGUgbG9h
ZHM7IHVzaW5nIGFuIGVuY2FwL2RlY2FwIHR1bm5lbCB0byBlbXVsYXRlIGEgcGh5c2ljYWwgY2ly
Y3VpdCBiZXR3ZWVuIGxvY2F0aW9ucyBoYXMgbWFueSBhdHRyYWN0aXZlIHByb3BlcnRpZXMg4oCT
IGJ1dCB0aGF0IGlzIGNvbXBhcmVkIHRvIGFjdHVhbGx5IG9yZGVyaW5nIGFuZCBwcm92aXNpb25p
bmcgcmVhbCBjaXJjdWl0cyBiZXR3ZWVuIGxvY2F0aW9ucy4NCg0KSW4gdGhlIG5ldyB3b3JsZCBv
ZiBkeW5hbWljIHJlc291cmNlcyBzcHVuIHVwIG9uIGRlbWFuZCBpbiBkaXN0cmlidXRlZCBlbnZp
cm9ubWVudHMgYWNyb3NzIG11bHRpcGxlIHByb3ZpZGVycywgQXBwbGljYXRpb25zIGhhdmluZyB0
aGUgSW50ZWxsaWdlbmNlIGFuZCBTdGF0ZSB0byBicmluZyB1cCB0aGVpciBvd24gcmVxdWlyZWQg
Y29ubmVjdGl2aXR5IGlzIHZlcnkgbmF0dXJhbC4gIFRoaXMgaXMgd2hlcmUgd2UgYXJlIHB1dHRp
bmcgdGhlIG1ham9yaXR5IG9mIG91ciBlZmZvcnRzLiAgU1J2NiBlbmFibGVzIHZlcnkgYXR0cmFj
dGl2ZSBzb2x1dGlvbnMgYnkgQXBwbGljYXRpb25zIGJ1aWxkaW5nIHRoZWlyIG93biBoZWFkZXJz
Lg0KDQpUaGUgY2hhbGxlbmdlcyBjb21lIGFzIHdlIHRyeSB0byBtaWdyYXRlIGFuZCByZXF1aXJl
IHRoZXNlIHR3byBpbmZyYXN0cnVjdHVyZXMgdG8gSW50ZXJvcGVyYXRlIGZvciBhIGxvbmcgdGlt
ZS4NCkJ1cmRlbmluZyB0aGUgbmV3IFZpcnR1YWwgd29ybGQgd2l0aCBPbGQsIFN0YXRpYyBjaXJj
dWl0IHBhcmFkaWdtcyBpcyBub3Qgb3B0aW1hbC4NClN1cHBsZW1lbnRpbmcgdGhlIGxlZ2FjeSBp
bmZyYXN0cnVjdHVyZSB3aXRoIGFuIGFzc2lzdCBmdW5jdGlvbiBzZWVtcyBhIHJlYXNvbmFibGUg
c29sdXRpb24uICAoRXh0IEhkciBpbnNlcnRpb24vZGVsZXRpb24gb3IgZW5jYXAvZGVjYXAgdHVu
bmVscykNCg0KVGhlIHByZWZlcnJlZCBhc3Npc3QgbWVjaGFuaXNtIHNlZW1zIHRvIGJlIHRoZSBv
bmUgdGhhdCBhbGxvd3MgdGhlIE5ldyBXb3JsZCB0byBvcGVyYXRlIGluIGl0cyBmaW5hbCBwcmVm
ZXJyZWQgc3RhdGUsIHNlbmRpbmcgYW5kIHJlY2VpdmluZyBwYWNrZXRzIHdpdGggdGhlaXIgb3du
IGhlYWRlcnMuIChTUnY2KQ0KQnV0IHdoYXQgZG9lcyBhbiBBcHBsaWNhdGlvbiBpbiB0aGUgbmV3
IHdvcmxkIGR1ZSB3aGVuIGl0IGlzIGF0dGVtcHRpbmcgdG8gY29tbXVuaWNhdGUgd2l0aCBhbiBB
cHBsaWNhdGlvbiBpbiB0aGUgT2xkIFdvcmxkPw0KU2hvdWxkbuKAmXQgaXQgYnVpbGQgYW4gU1J2
NiBoZWFkZXI/ICBUaGF0IHdvdWxkIG1lYW4gdGhhdCB0aGUgYXNzaXN0IGZ1bmN0aW9uIHdvdWxk
IG5lZWQgdG8gYmUgdGhlIGxhc3QgU0lEIGluIHRoZSBTZWdtZW50IExpc3QgYW5kIGJlIGNhcGFi
bGUgb2YgcmVtb3ZpbmcgdGhlIFNSSC4NCldvdWxkbuKAmXQgaXQgbWFrZSBzZW5zZSBmb3IgdGhl
IGFzc2lzdCBmdW5jdGlvbiB0byBkbyB0aGUgc2FtZSB0aGluZyBpbiB0aGUgcmV2ZXJzZSBkaXJl
Y3Rpb247IGFuIE9sZCBXb3JsZCBTZXJ2ZXIgdGFsa2luZyB0byBhIE5ldyBWaXJ0dWFsIFdvcmxk
IEFwcGxpY2F0aW9uPyAgSW5zZXJ0IGFuIFNSSC4NCg0KSWYgdGhpcyBpbnNlcnQvZGVsZXRlIG9m
IGFuIFNSSCBpcyBwcmVtYXR1cmVseSBwcm9oaWJpdGVkOyAgV2hhdCBpcyBhIHJlY29tbWVuZGVk
IHNvbHV0aW9uIHRvIHRoZSBSZWFsIFdvcmxkIHByb2JsZW0gYWJvdmUuICBOb3QgdXNlIGNhc2Us
IHdlIGFyZSBpbXBsZW1lbnRpbmcuDQoNCkFnYWluOyBJ4oCZbSB3b3JyaWVkIHdlIGFyZSBlbGlt
aW5hdGluZyBhIHRvb2wgdGhhdCBtYXkgcHJvdmUgdmVyeSBoZWxwZnVsLCBwcmVjbHVkZSBpdHMg
dXNlIGluIGZ1dHVyZSBJRVRGIHdvcmsgYW5kIHNodXRkb3duIGEgcGF0aCBmb3IgSW5ub3ZhdGlv
biBpbiBOZXR3b3JraW5nLA0KDQpUaGFuayB5b3UgZm9yIGFza2luZyBhbmQgbGlzdGVuaW5nIHRv
IG15IGNvbmNlcm5zLA0KDQpKb2huIExlZGR5DQpDb21jYXN0DQoNCiAgICANCiAgICANCiAgICAN
CiAgICANCg0K


From nobody Wed Mar 29 22:10:02 2017
Return-Path: <tjc@ecs.soton.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 96E2612948D; Wed, 29 Mar 2017 22:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HE6cHp0XWT_U; Wed, 29 Mar 2017 22:09:59 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C80B51292F5; Wed, 29 Mar 2017 22:09:57 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2U59nwo023964; Thu, 30 Mar 2017 06:09:50 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v2U59nwo023964
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1490850590; bh=qQ+wkM8a2jK8gfpMQAXbEtr66rw=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=MjGgNcC42x5gMcsziZJ5m9T2bwHRJD2POensI5FrdX6wiLXEiOg3GoLj10l/BY/oK OI8Dt2Avyr/hFVkZGeM0Oe8o/0ud7dOfw7Q7zty4sHSOsSFRdPoXp8qzYeW7dzqRc7 f3btmxrVo3ADlTKtL8Yp9BCy9WN817d2cqoSUJu0=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y2Y69n1151000425fR ret-id none; Thu, 30 Mar 2017 06:09:50 +0100
Received: from dhcp-953e.meeting.ietf.org (dhcp-953e.meeting.ietf.org [31.133.149.62]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2U59cLd020815 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Mar 2017 06:09:39 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com>
Date: Thu, 30 Mar 2017 06:09:37 +0100
Cc: "suresh.krishnan@ericsson.com" <suresh.krishnan@ericsson.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>,  "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|eed7c9a1e88b01b870b0ed916a75b22ey2Y69n03tjc|ecs.soton.ac.uk|DF41D301-8760-41E9-9ED4-2D28F394C070@ecs.soton.ac.uk>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <DF41D301-8760-41E9-9ED4-2D28F394C070@ecs.soton.ac.uk>
To: "Leddy, John" <John_Leddy@comcast.com>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y2Y69n115100042500; tid=y2Y69n1151000425fR; client=relay,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v2U59nwo023964
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gqZaa6Po0WkgJhcSGHEyKOAQVTY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 05:10:02 -0000

Hi,

> On 30 Mar 2017, at 03:59, Leddy, John <John_Leddy@comcast.com> wrote:
>=20
>> On Mar 14, 2017, at 9:47 PM, Suresh Krishnan =
<suresh.krishnan@ericsson.com> wrote:
>>=20
>> NEW:
>>=20
>> With one exception, extension headers are not examined, processed,
>> inserted, or deleted by any node along a packet's delivery path,
>> until the packet reaches the node (or each of the set of nodes, in
>> the case of multicast) identified in the Destination Address field of
>> the IPv6 header...
>>=20
>> Please feel free to comment either privately or on list if you have =
any concerns with this resolution going forward.
>=20
>=20
> Suresh,
>=20
> I still have concerns that we are eliminating a tool that may prove =
very helpful in migrations without understanding its value.
>=20
> The Internet transition of IPV4 -> Dual Stack V4/V6 -> IPV6 Only; has =
been long, operationally complex and full of unexpected challenges.
> We are only now starting to make the transition from Dual Stack to =
IPV6 Only, there are still many unknowns on how to complete this =
migration.
>=20
> As we contemplate finishing this major Network shift =E2=80=93 We find =
ourselves in the early stages of another.
>=20
> The transition from Physical to Virtual Infrastructure.  Again, the =
migration will be long, operationally complex and full of unexpected =
challenges.
>=20
> In the old world with Servers running Applications in Physical =
locations designed for very predictable loads; using an encap/decap =
tunnel to emulate a physical circuit between locations has many =
attractive properties =E2=80=93 but that is compared to actually =
ordering and provisioning real circuits between locations.
>=20
> In the new world of dynamic resources spun up on demand in distributed =
environments across multiple providers, Applications having the =
Intelligence and State to bring up their own required connectivity is =
very natural.  This is where we are putting the majority of our efforts. =
 SRv6 enables very attractive solutions by Applications building their =
own headers.
>=20
> The challenges come as we try to migrate and require these two =
infrastructures to Interoperate for a long time.
> Burdening the new Virtual world with Old, Static circuit paradigms is =
not optimal.
> Supplementing the legacy infrastructure with an assist function seems =
a reasonable solution.  (Ext Hdr insertion/deletion or encap/decap =
tunnels)
>=20
> The preferred assist mechanism seems to be the one that allows the New =
World to operate in its final preferred state, sending and receiving =
packets with their own headers. (SRv6)
> But what does an Application in the new world due when it is =
attempting to communicate with an Application in the Old World?
> Shouldn=E2=80=99t it build an SRv6 header?  That would mean that the =
assist function would need to be the last SID in the Segment List and be =
capable of removing the SRH.
> Wouldn=E2=80=99t it make sense for the assist function to do the same =
thing in the reverse direction; an Old World Server talking to a New =
Virtual World Application?  Insert an SRH.
>=20
> If this insert/delete of an SRH is prematurely prohibited;  What is a =
recommended solution to the Real World problem above.  Not use case, we =
are implementing.
>=20
> Again; I=E2=80=99m worried we are eliminating a tool that may prove =
very helpful, preclude its use in future IETF work and shutdown a path =
for Innovation in Networking,
>=20
> Thank you for asking and listening to my concerns,

Understood, but why do you require direct insertion rather than using =
encap as per 2460bis?

Tim

>=20
> John Leddy
> Comcast
>=20
>=20
>=20
>=20
>=20
>=20


From nobody Wed Mar 29 22:39:17 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 468DB128BB6 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 22:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.396
X-Spam-Level: 
X-Spam-Status: No, score=-5.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6d-C_mszfoMB for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 22:39:14 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1978C12922E for <ietf@ietf.org>; Wed, 29 Mar 2017 22:39:13 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.64.210]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LlGoc-1cJaHQ0yhi-00b10I; Thu, 30 Mar 2017 07:39:02 +0200
Subject: Re: Getting the latest version of an RFC specification
To: dcrocker@bbiw.net, IETF general list <ietf@ietf.org>
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <14811bee-fd75-8f09-a29d-06cf1e23eb69@gmx.de>
Date: Thu, 30 Mar 2017 07:38:57 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:olhdS7UvfdPuBFXQQ4GRiJN2Ld3GO92/KPb0CZmwf2V0qqjh5X0 FRH7fQMMNFuxRQ9GTnTF/v3nCzSEczVN5yQyOFyTp2T+p+C9JDYxSnwPLgRVTTPCp3OD4lW /QOX02DzVXESJxrb6+aktmQxnTnQz3TiFtobxd7ghBECGgS2yDY5z6cAA4fa53oIF+ze0n7 eYzlTl7XgTCM5LVYG58lw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:F4x3YotKJis=:XiJefLtNafz9/FztH8H3oG Gvv2sNh97A/jOx2b95iJ21Tka2gzPy28MofwLvT2pNcyiJkk1LQCLckZeWkYZqLNlv88qk+fV 2QscomLzJ6sfv4TpQEiWZu7nv5/+YfRJJUoPr/8D7LGko+bqs8zTvLY1B1Mc+83Dvjng+TgtZ zuMMBhuKwAXFfoOalDK+sErZ4HIqvrL4BzjVwz5zlhYK6xifuLK2rYvZ+zMZvACG4mD/uYs1T c9M5nfXdBwc4I3S5PDU5wkumC+LlwS5i+zRGGtlpS/fMiSYAjHvnTkFxulZoYRuFTwOPb8fiy cTcwJDa0giHed7ap2X4urCftr6A3DcymN5M15CMG+fdtbP2WrsNtva083B88uWiNZNmi65ziD Ith6VT0raD7xTFsCKEr0ZFS3zM4ln2Y4gXETD5/whvdM7b7tEPmF6cAsmYaDn3v19RBw0l5Q5 m4BWkU3Af3nqOgVPZ+kvTAompHPjDzF7HpA4QdwHBljIXaOZPnWWr0iME7YmlxSO0HXlbS6CX GCBYrTFDnKCmRdwyStGjxQv24KqMag7Kb6miuDVRxapHVXChUpmf98/fGFahqh6UEzJlIxfmc GxNY0h+/AWfmxWoNkbPrMxvSfKC4VZGGR/z7hFREaSHWXsYq/7dbp1aJ/RZgY5IGVud2nWgaQ CQ/TXlgBEMbT7T5XrSFp7V2IhidRGauNPy0iTsTJW5JdkTbg9+Mj36xpDpP0gITbzHwVIXtDh 1kqnelVNlBS09e/H/263rbsf32wsZzKtPzxxEevQ5hH0RPTQSSTUGIqdRr0bJ8h+R9P7sTdNo Ogu8ZRm
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zgV00Wsmdgzf0mEQ6qWZPl5HkzM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 05:39:16 -0000

On 2017-03-29 13:51, Dave Crocker wrote:
> G'day.
>
> The RFC labeling model is to assign a unique serial number to a static
> document.  A new version of a spec gets a new serial number. This basic
> model has the benefit of both simplicity and predictability.
>
> To this we've added an overlay model, using Obsoletes/ObsoletedBy. This
> makes it dramatically easier to see that something has been obsoleted
> and to find its replacement.
>
> However the seeing and the finding are an essentially manual process.
> One must go to the online older document, then notice the Obsoleted By
> tag and then click to follow it.
>
> Sometimes it would be helpful for the requester to be able to say 'give
> me the latest' more easily.
>
> So I'm wondering whether the IETF should consider adding a citation
> feature for this.
>
> Something like:
>
>      https://tools.ietf.org/html/rfc822/latest
>
> would display the contents of:
>
>      https://tools.ietf.org/html/rfc5322
>
> by having the fetching system automatically traversing the Obsoleted By
> links in RFC 822 and then RFC 2822.
>
> Some sort of display banner would flag this, to help the user see that
> they are getting a different version than they cited.
> ...

FWIW, a related (ans so far unanswered) question is how to present the 
updated/obsoleted information in the new HTML variant of the RFC format.

tools.ietf.org generates as static header block such as:

> [Docs] [txt|pdf] [draft-ietf-http-v...] [Diff1] [Diff2] [Errata]
>
> Obsoleted by: 7230, 7231, 7232, 7233, 7234, 7235          DRAFT STANDARD
> Updated by: 2817, 5785, 6266, 6585                          Errata Exist

-- <https://tools.ietf.org/html/rfc2616>

rfc2629.xslt inserts similar information dynamically (querying 
tools.org), example:

	<https://greenbytes.de/tech/webdav/rfc2616.html#rfc.status>

(details in 
<https://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#rfc-editor.meta-data>).

Best regards, Julian


From nobody Thu Mar 30 02:31:03 2017
Return-Path: <mark@townsley.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 585D912922E for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 02:30:57 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=townsley-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMCaxf85T4cO for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 02:30:55 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 706961286AB for <ietf@ietf.org>; Thu, 30 Mar 2017 02:30:53 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id l7so15295715ioe.3 for <ietf@ietf.org>; Thu, 30 Mar 2017 02:30:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=townsley-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=y6q0pnLA8HspTv5iDBhyIDQ6gMaxLzqIUvQvqlhjkY4=; b=eVsQpV8h/9CQSfb/rEhUv5OJNeq44kmU0n0K15MciNol7TPhjqGR3CNovWaQvs/cG+ YvO8YF1iv3VC8KMTznF9r3FAEJZU5q3M0ZKj5CfoS6p3QMTF7oxgC7qT5oxTUGJ310dL HVaiQVpsmN0Egs3e5IE+iSPaYGU5VfYEWqp/KTRCqgmgbKO44WqZPX2BOyq+1QjL6Fk7 zmq7he71i2JNgeJspk2w9z5RJVe/nQdp7WVYrw0vM8c3oJnd6MnJtZZ1R5zK68YO/Xre ZPbGEtOid61ppzlBaNEn9Ojn3Y80a5QlUo9iC0hk034OA+EfLMXByzLpsYQleC3T3DMG JZVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=y6q0pnLA8HspTv5iDBhyIDQ6gMaxLzqIUvQvqlhjkY4=; b=DjkrVRRx2N4AyGIN1L3zf5tq3CFRtcigHI2slNDsgoJPK8DLShLoXf8COmNnHyByxm Ue084bbaQL2MOj9f7BlXLtX1gamZh/gs8RBIprL4bgngfAUYyTV507b4/Vv6VA4KWGBU pIeQekEOAmURjd1fhP4ls/SoL6nkZktC5hvNFfz481Qvoa+aROOwwqX//NOTI3BcgDMt iv0KUqYwXyHCF41e0hWPWB2VM7qaKZROrlz6aJqgpPVCm5uNJB/g3n0EqrZsnGnsHqBP bH4zN8R0vAIEXOBv3EdGjH1Ji6E/2hwySfkLJSLkkShKIfIa4jpuZJLDNigFUqpSqJGV dBFA==
X-Gm-Message-State: AFeK/H1KcbkbsfFadiujXrtBih4u6NJGlT4+giiKa62l4m2p7dlDqRwz1XUTaUa/+p+ZHg==
X-Received: by 10.107.35.129 with SMTP id j123mr5887389ioj.195.1490866252738;  Thu, 30 Mar 2017 02:30:52 -0700 (PDT)
Received: from [10.71.6.171] (chsptrs33.c.subnet.rcn.com. [207.229.161.32]) by smtp.gmail.com with ESMTPSA id w133sm4768960itf.2.2017.03.30.02.30.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 02:30:51 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
From: Mark Townsley <mark@townsley.net>
X-Mailer: iPad Mail (14D27)
In-Reply-To: <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com>
Date: Thu, 30 Mar 2017 04:30:51 -0500
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>,  "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E03B93AF-82B9-453E-8596-8978FA490D17@townsley.net>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com>
To: "Leddy, John" <John_Leddy@comcast.com>, "suresh.krishnan@ericsson.com" <suresh.krishnan@ericsson.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KXnV1oPl8x0ulAcZgsFbQiB_YpA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 09:30:57 -0000

I think this is hitting on a very important point about protocol transition h=
ere, something that I think all of us should step back and consider from a v=
ery humble vantage point.

The transition from IPv4 to IPv6 has been hard, certainly much harder than I=
 think the contributors to RFC2460 originally expected. We've had to go back=
 after the fact to define and perfect things like NAT64 to sit at the bounda=
ry of IPv6-only networks, allowing communication between IPv6-only and IPv4-=
only endpoints by inserting and deleting IPv6 and IPv4 headers.=20

The whole idea of an extension header is to extend the capabilities of IPv6.=
 Extended functions naturally come with transition, and transition happens p=
rogressively. Inserting and deleting an extension header is analogous to a N=
AT64 function - not something we necessarily want, but something we have rea=
lized we need, to handle transition within the reality that wide spread flag=
 days are impossible.

If I take IPv6 SR as an example of an extended IPv6 function, some endpoints=
 will support IPv6 SR sooner than others. Some network domains will operate w=
ith IPv6 SR everywhere sooner than others. The ability to classify traffic a=
nd insert an SR header upon entry into an SR domain is important to transiti=
on, and is completely analogous to what, say, T-Mobile does with NAT64 and 4=
64xlat. =20

Suresh, I think this may be a tussle point (to refer to Dave Clark's present=
ation earlier this evening). 2460bis should not try to over-specify here. In=
stead, allow for a bit of flex while we truly get our heads around how to de=
ploy and operate systems which use IPv6 extension headers.

- Mark




On Mar 29, 2017, at 9:59 PM, Leddy, John <John_Leddy@comcast.com> wrote:

>> On Mar 14, 2017, at 9:47 PM, Suresh Krishnan <suresh.krishnan@ericsson.co=
m> wrote:
>>=20
>> NEW:
>>=20
>> With one exception, extension headers are not examined, processed,
>> inserted, or deleted by any node along a packet's delivery path,
>> until the packet reaches the node (or each of the set of nodes, in
>> the case of multicast) identified in the Destination Address field of
>> the IPv6 header...
>>=20
>> Please feel free to comment either privately or on list if you have any c=
oncerns with this resolution going forward.
>=20
>=20
> Suresh,
>=20
> I still have concerns that we are eliminating a tool that may prove very h=
elpful in migrations without understanding its value.
>=20
> The Internet transition of IPV4 -> Dual Stack V4/V6 -> IPV6 Only; has been=
 long, operationally complex and full of unexpected challenges.
> We are only now starting to make the transition from Dual Stack to IPV6 On=
ly, there are still many unknowns on how to complete this migration.
>=20
> As we contemplate finishing this major Network shift =E2=80=93 We find our=
selves in the early stages of another.
>=20
> The transition from Physical to Virtual Infrastructure.  Again, the migrat=
ion will be long, operationally complex and full of unexpected challenges.
>=20
> In the old world with Servers running Applications in Physical locations d=
esigned for very predictable loads; using an encap/decap tunnel to emulate a=
 physical circuit between locations has many attractive properties =E2=80=93=
 but that is compared to actually ordering and provisioning real circuits be=
tween locations.
>=20
> In the new world of dynamic resources spun up on demand in distributed env=
ironments across multiple providers, Applications having the Intelligence an=
d State to bring up their own required connectivity is very natural.  This i=
s where we are putting the majority of our efforts.  SRv6 enables very attra=
ctive solutions by Applications building their own headers.
>=20
> The challenges come as we try to migrate and require these two infrastruct=
ures to Interoperate for a long time.
> Burdening the new Virtual world with Old, Static circuit paradigms is not o=
ptimal.
> Supplementing the legacy infrastructure with an assist function seems a re=
asonable solution.  (Ext Hdr insertion/deletion or encap/decap tunnels)
>=20
> The preferred assist mechanism seems to be the one that allows the New Wor=
ld to operate in its final preferred state, sending and receiving packets wi=
th their own headers. (SRv6)
> But what does an Application in the new world due when it is attempting to=
 communicate with an Application in the Old World?
> Shouldn=E2=80=99t it build an SRv6 header?  That would mean that the assis=
t function would need to be the last SID in the Segment List and be capable o=
f removing the SRH.
> Wouldn=E2=80=99t it make sense for the assist function to do the same thin=
g in the reverse direction; an Old World Server talking to a New Virtual Wor=
ld Application?  Insert an SRH.
>=20
> If this insert/delete of an SRH is prematurely prohibited;  What is a reco=
mmended solution to the Real World problem above.  Not use case, we are impl=
ementing.
>=20
> Again; I=E2=80=99m worried we are eliminating a tool that may prove very h=
elpful, preclude its use in future IETF work and shutdown a path for Innovat=
ion in Networking,
>=20
> Thank you for asking and listening to my concerns,
>=20
> John Leddy
> Comcast
>=20
>=20
>=20
>=20
>=20
>=20


From nobody Thu Mar 30 02:38:32 2017
Return-Path: <mark@townsley.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 5BAB5129471 for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 02:38:25 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=townsley-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id orSrndx2wR2e for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 02:38:23 -0700 (PDT)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FD24126BF6 for <ietf@ietf.org>; Thu, 30 Mar 2017 02:38:23 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id 190so71296156itm.0 for <ietf@ietf.org>; Thu, 30 Mar 2017 02:38:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=townsley-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HWf2QcWbZBuKsyIZCdueo1BZBZrhnTZNlN9iVvH5tcE=; b=VSbwJfSPObPV13wyBnSbHv8f9hExdks3xjgxH3x8NGaoHZXazWLE9AB0mTuOcbrccW gARn8WJughBnSMY+O5Udpf8bzt/NTLLji8ffVM4Ssoca5xh7BOZGyzGlFL1v1dMWjv4a Dm56TsenTc9OmkFnIyzpF/KahpT5WF0kYismnUNsZ/C7mU2PBKfC0D9GnNH/b8726z14 TkqBzECTySTKDyyq3rloPd8xv59mM2/g4ATBvTgxJVMuYrUmeJPkKpATd0eSmgCvy2AF WTd8mPO+IBDKjeP9pL3s6p00UOaQlkXDHoY+VcNgtMIGBPzVhlJ3RGpwF8rsHPfBXQ/f VYjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HWf2QcWbZBuKsyIZCdueo1BZBZrhnTZNlN9iVvH5tcE=; b=CDoi5hHiwTs+DJTmEEAQSe8SLsfNk9V5g3R2/jO1CtS9hqC4ayPDiD3eKPPSZuiZ7O sk6/S11Qb4kKKNVnDSJX+9CosLZhm3ofcVC5LPlL6hSUOf+J7sFdsnXX1NRNswMMUrzn fzg6bFE7OIHzbj0wgSisFZz9rUsfzshEWZj4erjp2SjYYrWMEsy4lNqmZmh+ubS6OixQ jMPa5uQPiVjcutrh3nlCTPUNYRDdgLqfXaH3s64zGhxDWpsGUzUXWQysLa54hXhLI+Eh lioW2OyDMGf7DRdz3fpU9FokEw4s2fyWtNqWAy+TNvHo1LNwkh7ukXjsTE33+9a2pMUd LJPA==
X-Gm-Message-State: AFeK/H0qgIrVAZdRynceDx629odFuLTEUPKrCCLaiy7/gMR6n+6jAppBUNYA4JcQW12fDQ==
X-Received: by 10.36.65.147 with SMTP id b19mr3335183itd.111.1490866702882; Thu, 30 Mar 2017 02:38:22 -0700 (PDT)
Received: from [10.71.6.171] (chsptrs33.c.subnet.rcn.com. [207.229.161.32]) by smtp.gmail.com with ESMTPSA id k68sm1100321iod.13.2017.03.30.02.38.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 02:38:21 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
From: Mark Townsley <mark@townsley.net>
X-Mailer: iPad Mail (14D27)
In-Reply-To: <EMEW3|eed7c9a1e88b01b870b0ed916a75b22ey2Y69n03tjc|ecs.soton.ac.uk|DF41D301-8760-41E9-9ED4-2D28F394C070@ecs.soton.ac.uk>
Date: Thu, 30 Mar 2017 04:38:20 -0500
Cc: "Leddy, John" <John_Leddy@comcast.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>,  "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A112F912-A7FC-4682-A043-4430DD578306@townsley.net>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <DF41D301-8760-41E9-9ED4-2D28F394C070@ecs.soton.ac.uk> <EMEW3|eed7c9a1e88b01b870b0ed916a75b22ey2Y69n03tjc|ecs.soton.ac.uk|DF41D301-8760-41E9-9ED4-2D28F394C070@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UfexdkSgjWOiFJsJ4JlMaTtD6eQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 09:38:25 -0000

> On Mar 30, 2017, at 12:09 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>=20
> Understood, but why do you require direct insertion rather than using enca=
p as per 2460bis?

The same reason we have MAP-T and 464xlat.=20

- Mark

>=20
> Tim
>=20
>>=20
>> John Leddy
>> Comcast
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20


From nobody Thu Mar 30 04:07:01 2017
Return-Path: <John_Leddy@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 2840F129471; Thu, 30 Mar 2017 04:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hzis7LmUkRBH; Thu, 30 Mar 2017 04:06:57 -0700 (PDT)
Received: from vaadcmhout02.cable.comcast.com (vaadcmhout02.cable.comcast.com [96.114.28.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B961127A97; Thu, 30 Mar 2017 04:06:57 -0700 (PDT)
X-AuditID: 60721c4c-b2dff7000000bcc0-91-58dce6ce975d
Received: from VAADCEX43.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id 10.E3.48320.EC6ECD85; Thu, 30 Mar 2017 07:06:56 -0400 (EDT)
Received: from VAADCEX41.cable.comcast.com (147.191.103.218) by VAADCEX43.cable.comcast.com (147.191.103.220) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 30 Mar 2017 07:06:53 -0400
Received: from VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268]) by VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268%19]) with mapi id 15.00.1263.000; Thu, 30 Mar 2017 07:06:53 -0400
From: "Leddy, John" <John_Leddy@comcast.com>
To: Mark Townsley <mark@townsley.net>
CC: Tim Chown <tjc@ecs.soton.ac.uk>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSqOd8Ap6Hay13uEWcjbPxwh2xd6GssVmAgABnjYCAAEsUAP//1bD/
Date: Thu, 30 Mar 2017 11:06:53 +0000
Message-ID: <619B8C8A-066E-4C5B-A462-DF109E39DA71@cable.comcast.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <DF41D301-8760-41E9-9ED4-2D28F394C070@ecs.soton.ac.uk> <EMEW3|eed7c9a1e88b01b870b0ed916a75b22ey2Y69n03tjc|ecs.soton.ac.uk|DF41D301-8760-41E9-9ED4-2D28F394C070@ecs.soton.ac.uk>, <A112F912-A7FC-4682-A043-4430DD578306@townsley.net>
In-Reply-To: <A112F912-A7FC-4682-A043-4430DD578306@townsley.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrAIsWRmVeSWpSXmKPExsWSUOxpoXvh2Z0Ig+VTVCxevb3GZvFs43wW i5dn3zNZTDvwgMni0J7nbA6sHn/XuXosWfKTyeP+tIlMAcxRXDYpqTmZZalF+nYJXBkXPsxg K3jBVrH1bGED4yLWLkZODgkBE4nrf+azdDFycQgJbGeSuNFxjRXCOcQo0fbvLhuEc5JRYt/T D8wgLWwCOhIzpl0DaxcRUJVYe+UhM0gRs8A+Rol3H0+CJYQFPCQmbbrGAlHkKbFu42EgmwPI dpPo/hEOYrIA9e66aQJi8gq4SBzaUQKxaiqzxIKGOYwgnZwCDhLzGnaA2YwCYhLfT61hArGZ BcQlbj2ZzwTxgYDEkj3nmSFsUYmXj/9BfWYgsXXpPhaIeh2JBbs/sUHY2hLLFr4Gq+cVEJQ4 OfMJC0S9pMTBFTdYJjCKz0KyYhaS9llI2mchaV/AyLKKUa4sMTElOTcjv7TEwEgvOTEpJ1Uv OT83ObG4BERvYgTFY5GMzw7GT9M8DjEKcDAq8fBu3XsnQog1say4MhcY3BzMSiK83E+AQrwp iZVVqUX58UWlOanFhxilOViUxHm9bt6KEBJITyxJzU5NLUgtgskycXBKNTBOFp9le+rutAUO /6/ulkw7M6PdS7Ou1krwXrjJicV/psScWrT/XCljsGwA49ZulV3ea3cxyZ4O/3AyyWpf6POp 0f5t57Y9qeZPyNrDwLRcRsFUuelm5akNih7PTWL6fJY0q3Fw5b189eTT0SlZQgyLRC/2L1Hp meYuOf07O2tRiNPODyEpD08osRRnJBpqMRcVJwIAPuhLg8MCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oW1KNDHEmuooGZnJ4ar3PWEB16I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 11:07:00 -0000

The issue is the encap/decap pair - like an old circuit model.

Do we add the encap/decap function into a Domain doing native SRv6 and the =
complexity of choosing which to use - into all the vm's?  Or do we extend t=
he new SRv6 domain to the legacy infrastructure.   If we do this, there is =
no tunnel.  There is no encap/decap pair - you need to proxy for the legacy=
 gear/services.

John

> On Mar 30, 2017, at 4:38 AM, Mark Townsley <mark@townsley.net> wrote:
>=20
>=20
>=20
>> On Mar 30, 2017, at 12:09 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>>=20
>> Understood, but why do you require direct insertion rather than using en=
cap as per 2460bis?
>=20
> The same reason we have MAP-T and 464xlat.=20
>=20
> - Mark
>=20
>>=20
>> Tim
>>=20
>>>=20
>>> John Leddy
>>> Comcast
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>=20
>=20


From nobody Thu Mar 30 05:44:32 2017
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 3CF91129698; Thu, 30 Mar 2017 05:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHoSKLBbuYdl; Thu, 30 Mar 2017 05:44:25 -0700 (PDT)
Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D04FD129677; Thu, 30 Mar 2017 05:44:24 -0700 (PDT)
Received: by mail-it0-x242.google.com with SMTP id 190so12866333itm.3; Thu, 30 Mar 2017 05:44:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=MTlfsjXmfKNHquRWOk/cej1jwTINVowrSssjAKLOtLM=; b=K96Cagm7TlTGUG6U85N/4fj1p8ZgOIfW1WGLULiExVD9y1qUXTckCJectO9Z7VI38G qlouwL81kfweOpBpAKlSvjkdvooYV5ZV3vIleEbIx3A5Tmnhe6ci5FOyYZdIKCK5AoNm u1IxrAUSbSQT+YhiMu2woxcxNpeHak/7x6W267F+02G7Wt60YSXgYXwPb8MQmh0hBzBV fe2Q441t2mOJRs9sbvXhYR3YntG/k+3TFJW72eYLJudUJQT6Y5fQLxWwSCCz3fhgV6xw DJxwKEzPeZbWCzTCFPqvRYAYztJK3NXSBXwQdhwGRgih2iSnRtYk2irYCZu+GEFQKGmE 2s6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=MTlfsjXmfKNHquRWOk/cej1jwTINVowrSssjAKLOtLM=; b=teXV8AGUNeWBK91gtYHWWoPbD6L6hyqM0PlSFvz+q+AaW8a+awRvhESb7mbHwNLat3 gHOD8gq1pQAThGfZ8nYF6VE9Mv7oNck0Zy5xCkRlBzoKsxFwwTyZbSe8wltiXwzolgu1 B35LRjh2aGkpRhwGCPz4C2g9JPH2sdRYhu1zEY6q68+A6c61uzapXBEYI27Rd35xgZTr MP1/io2b3F49Molz+njIMj/jcOb26QZfT+pxc3eCHs7j7pU8QbIgjSVcMqKTuCkabUDu KU5TldradGvt+6ZN8uSP/xVrNEQKS1YpFtWDxIdSM5NoUa6r2rCaUZdR7zjaciveGOgZ yPvg==
X-Gm-Message-State: AFeK/H2x+QIL2wyrM+LP0MH27jExMwuRAF2ZYEgZjihz4bZTCWQ3F7oxR9wbNCFEND2mrQ==
X-Received: by 10.36.0.198 with SMTP id 189mr3892889ita.82.1490877864156; Thu, 30 Mar 2017 05:44:24 -0700 (PDT)
Received: from [31.133.147.88] (dhcp-9358.meeting.ietf.org. [31.133.147.88]) by smtp.gmail.com with ESMTPSA id m77sm1292122ita.16.2017.03.30.05.44.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 05:44:23 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: "Leddy, John" <John_Leddy@comcast.com>, "suresh.krishnan@ericsson.com" <suresh.krishnan@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com>
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man <ipv6@ietf.org>, IETF discussion list <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com>
Date: Fri, 31 Mar 2017 01:44:30 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W3rpKuBxQ8hdodE4yQeI_H2sRwk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 12:44:26 -0000

On 30/03/2017 15:59, Leddy, John wrote:

=2E..
> If this insert/delete of an SRH is prematurely prohibited;  What is a r=
ecommended solution to the Real World problem above.  Not use case, we ar=
e implementing.
>=20
> Again; I=E2=80=99m worried we are eliminating a tool that may prove ver=
y helpful, preclude its use in future IETF work and shutdown a path for I=
nnovation in Networking,

I've tried to say this before but I'm not sure people are getting it:=20

RFC2460bis, if approved as is, draws a line in the sand *for interoperabi=
lity across the whole Internet*. There are reasons for this - PMTUD in an=
y form, any future replacement for the unsuccessful IPsec/AH, and all the=
 problems of deploying extension headers that are understood by some node=
s and not by others.=20

There is no reason why a subsequent standards-track document cannot allow=
 header insertion (and removal) within finite domains where the above iss=
ues do not apply. In fact, an improved version of draft-voyer-6man-extens=
ion-header-insertion-00 could become exactly that.

There doesn't need to be a tussle here.=20

   Brian Carpenter


From nobody Thu Mar 30 06:12:11 2017
Return-Path: <jefftant.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 24F071294C4; Thu, 30 Mar 2017 06:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h9oxSGcyYfnZ; Thu, 30 Mar 2017 06:12:01 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D1B41294E5; Thu, 30 Mar 2017 06:12:00 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id y18so1843938itc.1; Thu, 30 Mar 2017 06:12:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=9WQ7aB6vOJr1y7R0P5/9V9w9T05gr0aI9C9EMyRo9eg=; b=i8Rg94o9+SiFlNew/sVHkegPsLfsVdLovEHVgK9YMhdYFOUupl/si3AnFGu39jBZKw ds4Ysv50MqCC+UmdwxKFlrKcOKPk8S2P2SUyKRcgyOKEAwXuH7qosbqeBIMUswpsG+F2 lohw59sD+cPCTz8IO6W86VtygilJAYZXsn1kWUO9FvdRj5qVpesgWzPFv6wc9mpyopcn 376t04XJBbI3919TznT4A/iOaOCAX4bnbACEXnaIMP6P4zYj/llYjT8edRxKxYXKecMX 2yw7ke1ST552YUjvLKd60PPmKpqi1/P9iFFYHh0SU0LvoHxDK5VbPEnkvZvMkFf7U/gQ /tsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=9WQ7aB6vOJr1y7R0P5/9V9w9T05gr0aI9C9EMyRo9eg=; b=Obzl268B24W21d6hQ2jKmH7V4Gu+yjSdS1Xo59lf1sBhiApwbboTtlMWXjpb06qaM4 wZXD/bGdarsunG/gWoeN4SyI1PT3gCwN+p+P/F9TgrdBjRkin3a5iIxaHhzTYLRN75Gn mkZtSUiqsSh3PttrKYJ3Wu/OdmsiS08PVv9HWbx+ZgrTcbHfWQvaDCJ3AEqrOvRlVzR8 1ErCluQQkftv5Te+qvbphLZiIi7/eOXhoEtkOrq4Eyg4mvpLTEFbo8XkLVgJuariKgM4 3WgJUY1VrqJYIx/l9lbG9rvqrcREdNwJxIz0zOJgO2xLoQxXkt16V/ZbCDCVbD2eUKM2 k9wg==
X-Gm-Message-State: AFeK/H2eHo2nQlEfYYWrq7jVtMSyq+8kU13Owei/voOsUrGOVTAZyopyjHh5ZzJAQvS8LA==
X-Received: by 10.36.43.78 with SMTP id h75mr311776ita.25.1490879519903; Thu, 30 Mar 2017 06:11:59 -0700 (PDT)
Received: from [31.133.143.171] (t2001067c037001284d2da5a9acf593c2.v6.meeting.ietf.org. [2001:67c:370:128:4d2d:a5a9:acf5:93c2]) by smtp.gmail.com with ESMTPSA id v185sm1328437itf.11.2017.03.30.06.11.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 06:11:58 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Thu, 30 Mar 2017 08:11:57 -0500
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Leddy, John" <John_Leddy@comcast.com>, "suresh.krishnan@ericsson.com" <suresh.krishnan@ericsson.com>
CC: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man <ipv6@ietf.org>, IETF discussion list <ietf@ietf.org>
Message-ID: <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com>
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com>
In-Reply-To: <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t9XFBPgLyECyqvZjW_6X2jKxkig>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 13:12:08 -0000

Brian,

if I understand you correctly:=20

If properly worded (improved) draft-voyer explicitly states =E2=80=93 the intenti=
on is to change the 2460(bis) behavior and to allow header insertion within =
a controlled domain, and given there=E2=80=99s a valid justification of why encap =
wouldn=E2=80=99t=E2=80=99 meet the need, you wouldn=E2=80=99t oppose?=20

Thanks!=20

Cheers,
Jeff

On 3/30/17, 07:44, "ietf on behalf of Brian E Carpenter" <ietf-bounces@ietf=
.org on behalf of brian.e.carpenter@gmail.com> wrote:

    On 30/03/2017 15:59, Leddy, John wrote:
   =20
    ...
    > If this insert/delete of an SRH is prematurely prohibited;  What is a=
 recommended solution to the Real World problem above.  Not use case, we are=
 implementing.
    >=20
    > Again; I=E2=80=99m worried we are eliminating a tool that may prove very he=
lpful, preclude its use in future IETF work and shutdown a path for Innovati=
on in Networking,
   =20
    I've tried to say this before but I'm not sure people are getting it:=20
   =20
    RFC2460bis, if approved as is, draws a line in the sand *for interopera=
bility across the whole Internet*. There are reasons for this - PMTUD in any=
 form, any future replacement for the unsuccessful IPsec/AH, and all the pro=
blems of deploying extension headers that are understood by some nodes and n=
ot by others.=20
   =20
    There is no reason why a subsequent standards-track document cannot all=
ow header insertion (and removal) within finite domains where the above issu=
es do not apply. In fact, an improved version of draft-voyer-6man-extension-=
header-insertion-00 could become exactly that.
   =20
    There doesn't need to be a tussle here.=20
   =20
       Brian Carpenter
   =20
   =20



From nobody Thu Mar 30 06:30:26 2017
Return-Path: <suresh.krishnan@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 447FA1296B1; Thu, 30 Mar 2017 06:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GhYUEPyE4r1d; Thu, 30 Mar 2017 06:30:23 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DC62129698; Thu, 30 Mar 2017 06:30:23 -0700 (PDT)
X-AuditID: c618062d-d73ff700000009d8-9b-58dd1a1258ab
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by  (Symantec Mail Security) with SMTP id DA.DC.02520.21A1DD85; Thu, 30 Mar 2017 16:45:41 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0319.002; Thu, 30 Mar 2017 09:30:18 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "Leddy, John" <John_Leddy@comcast.com>
CC: "ietf@ietf.org" <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv86cghjjmGk6P6rsvHH5Q4qGssVmAgAEK0QA=
Date: Thu, 30 Mar 2017 13:30:17 +0000
Message-ID: <CC4FF04D-0712-4304-BD5F-3D9F57E533A3@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com>
In-Reply-To: <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_65BB2E3A-3775-4603-8BAC-3263668990BE"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHIsWRmVeSWpSXmKPExsUyuXRPiK6o1N0Ig7Xf9Cxevb3GZvFs43wW i5dn3zNZLF2wnMmBxeN6Zwuzx5IlP5kCmKK4bFJSczLLUov07RK4Mm5Of8lWMMev4uHZucwN jLvduhg5OSQETCS2dDxk72Lk4hAS2MAoMXfqWyYIZzmjxLbG2+wgVWxAVRt2fmYCsUUEtCT2 nN0M1sEsMJVR4vLSe8wgCWEBD4lJm66xQBR5SqzbeBjKtpLoXbCPFcRmEVCVuPl2AxuIzStg L7H13TRmiG1rGSXa3twFa+AUcJV4dPsaWAOjgJjE91NrwDYzC4hL3HoynwnibhGJhxdPs0HY ohIvH/9jhbCVJD7+ng913RRGiWtbd7BCbBOUODnzCcsERpFZSGbNQlY3C0kdRJG2xLKFr5kh bE2J/d3LoeKmEq+PfmSEsK0lZvw6yAZhK0pM6X7IvoCRYxUjR2lxQU5uupHBJkZgzB2TYNPd wXh/uuchRgEORiUe3gd7b0cIsSaWFVfmHmJUAWp9tGH1BUYplrz8vFQlEd61bHcjhHhTEiur Uovy44tKc1KLDzFKc7AoifNOOH8hQkggPbEkNTs1tSC1CCbLxMEp1cC4XWTm5bLp6l0ygndY GKa06kU+vrPL8KWJOEfkpGWzGNzsN59WWXrUJ7NIeY7aptBcl5DdF5n+1vc9WeK+1I3V8G3B 6rVN60Qv7Dr89xy/8THhzHl7tnxLvHZJ8G2kas7Wb28T2TmKr/jNN0zc77K3Xzjkym07q24v LYdbQjLKNyP65K//ba9TYinOSDTUYi4qTgQAAk/ap8ECAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aDXG7t3BUlVP64ASgyZnfE84c7E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 13:30:25 -0000

--Apple-Mail=_65BB2E3A-3775-4603-8BAC-3263668990BE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi John,
  Thanks for chiming in. I recognize that you might have use cases that =
might be better off with header insertion but I think they should be =
handled as and when they come up for consideration (e.g. in the SRv6 =
discussions). Holding up this document is not going to help in any way =
in reinterpreting what RFC2460 intended. My suggestion for proponents of =
safe header insertion to write up how it is expected to work and have =
the discussion then.

Thanks
Suresh

> On Mar 29, 2017, at 9:59 PM, Leddy, John <John_Leddy@comcast.com> =
wrote:
>=20
>> On Mar 14, 2017, at 9:47 PM, Suresh Krishnan =
<suresh.krishnan@ericsson.com> wrote:
>>=20
>> NEW:
>>=20
>> With one exception, extension headers are not examined, processed,
>> inserted, or deleted by any node along a packet's delivery path,
>> until the packet reaches the node (or each of the set of nodes, in
>> the case of multicast) identified in the Destination Address field of
>> the IPv6 header...
>>=20
>> Please feel free to comment either privately or on list if you have =
any concerns with this resolution going forward.
>=20
>=20
> Suresh,
>=20
> I still have concerns that we are eliminating a tool that may prove =
very helpful in migrations without understanding its value.
>=20
> The Internet transition of IPV4 -> Dual Stack V4/V6 -> IPV6 Only; has =
been long, operationally complex and full of unexpected challenges.
> We are only now starting to make the transition from Dual Stack to =
IPV6 Only, there are still many unknowns on how to complete this =
migration.
>=20
> As we contemplate finishing this major Network shift =E2=80=93 We find =
ourselves in the early stages of another.
>=20
> The transition from Physical to Virtual Infrastructure.  Again, the =
migration will be long, operationally complex and full of unexpected =
challenges.
>=20
> In the old world with Servers running Applications in Physical =
locations designed for very predictable loads; using an encap/decap =
tunnel to emulate a physical circuit between locations has many =
attractive properties =E2=80=93 but that is compared to actually =
ordering and provisioning real circuits between locations.
>=20
> In the new world of dynamic resources spun up on demand in distributed =
environments across multiple providers, Applications having the =
Intelligence and State to bring up their own required connectivity is =
very natural.  This is where we are putting the majority of our efforts. =
 SRv6 enables very attractive solutions by Applications building their =
own headers.
>=20
> The challenges come as we try to migrate and require these two =
infrastructures to Interoperate for a long time.
> Burdening the new Virtual world with Old, Static circuit paradigms is =
not optimal.
> Supplementing the legacy infrastructure with an assist function seems =
a reasonable solution.  (Ext Hdr insertion/deletion or encap/decap =
tunnels)
>=20
> The preferred assist mechanism seems to be the one that allows the New =
World to operate in its final preferred state, sending and receiving =
packets with their own headers. (SRv6)
> But what does an Application in the new world due when it is =
attempting to communicate with an Application in the Old World?
> Shouldn=E2=80=99t it build an SRv6 header?  That would mean that the =
assist function would need to be the last SID in the Segment List and be =
capable of removing the SRH.
> Wouldn=E2=80=99t it make sense for the assist function to do the same =
thing in the reverse direction; an Old World Server talking to a New =
Virtual World Application?  Insert an SRH.
>=20
> If this insert/delete of an SRH is prematurely prohibited;  What is a =
recommended solution to the Real World problem above.  Not use case, we =
are implementing.
>=20
> Again; I=E2=80=99m worried we are eliminating a tool that may prove =
very helpful, preclude its use in future IETF work and shutdown a path =
for Innovation in Networking,
>=20
> Thank you for asking and listening to my concerns,
>=20
> John Leddy
> Comcast
>=20
>=20
>=20
>=20
>=20
>=20


--Apple-Mail=_65BB2E3A-3775-4603-8BAC-3263668990BE
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzMwMTMzMDE3WjAjBgkqhkiG9w0B
CQQxFgQU/6WTQS7gR+AeGjbiM4QXlieHqhswXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQAZTCsgY/E5rQHjHIFsM61QmBBMEem+rpdAhd19YgNpUGVwzIzMFSpPnghMuXz/
PNSWSrxzwEvXTaLoqSgHRYmZBhXqhcveEa2+dtq3h/TOkYWwpMPvaQzeGM2iwxU73cqf/KRp57R1
BEKilYhhJ75uixq6tXyWIxo09jFaS75Z06/y9q5azqLWZZppvyrNVvS3codDyNKAcXcVjjDnyRhg
13PBw73zJulkgyoiIo+PBkEhqOJofzVvizhx+w+rSOZ8tYCXsQpeConquTpuWZDroo7tBsf4v8Jx
QE7wumpw6HbpQS0tReQpYu19JhuzlqxEmhepC3tmbm1+ETtyW0BsAAAAAAAA

--Apple-Mail=_65BB2E3A-3775-4603-8BAC-3263668990BE--


From nobody Thu Mar 30 07:53:16 2017
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 700F3129517; Thu, 30 Mar 2017 07:53:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: <secdir@ietf.org>
Cc: draft-ietf-pals-status-reduction.all@ietf.org, ietf@ietf.org, pals@ietf.org
Subject: Secdir last call review of draft-ietf-pals-status-reduction-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149088558240.15511.14051374750329617951@ietfa.amsl.com>
Date: Thu, 30 Mar 2017 07:53:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O5W-CaYkgEXeND97Aru0L8lsfSs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 14:53:03 -0000

Reviewer: Yaron Sheffer
Review result: Ready

This document proposes a way to aggregate status messages of multiple
pseudowires carried on the same MPLS-network LSP.

The Security Considerations simply refer to an earlier RFC, and this
makes sense in this case.

However from a broader perspective, I think the community should
consider another look at its security assumptions. After what we've
seen in recent years, maybe it's not a good idea to refer back to a
2006 document that contains this sentence: "To prevent unwanted packet
insertion, it is also important to prevent unauthorized physical
access to the PSN," We have all learned the hard way that this advice
is not practical - bad actors WILL get physical access to your
network.


From nobody Thu Mar 30 08:11:21 2017
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 E832B129631; Thu, 30 Mar 2017 08:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9rsu8kvE3TnC; Thu, 30 Mar 2017 08:11:12 -0700 (PDT)
Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAE06129474; Thu, 30 Mar 2017 08:11:12 -0700 (PDT)
Received: by mail-io0-x242.google.com with SMTP id f84so3166361ioj.0; Thu, 30 Mar 2017 08:11:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=rsRGoBg1Q9hS4Ronww7dPjKGRkcX3T1dDyU0G4abGRs=; b=fqbAqxUX7pHx+nt3W0QV9mc6X+OpXram+Pu/Ht2NcYdbonzTEWSI0DSmPeFWvwwCIO ebIjrHYHw+LYQTCCBwdX7KDgtVRHqLRGjwaWhUlzIdrWKyL1sAOXTZp/QxU+hvJW5Ftd lnkIXNpGtN19qsLDWyLhLG+pCtA4XNDnMx8YgcSS5UGmHHMGjK+9VUwFoaXV+1O5SlAu /C5t2WdkmfSd/1m6yq8iPr7aMBTgfX2VqSyUUH+2IGbV8ZSC8T4SqRVGPuKFps5uRxlB svs4KpThR+paJRD/asNsVvl5dS36yhAuYlCO8Wq4hhZz5oubD6re1Afw8WI20NfFaJGh o4Bw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=rsRGoBg1Q9hS4Ronww7dPjKGRkcX3T1dDyU0G4abGRs=; b=f8ps8D9b3MyDm2yJIfGVFBym/McPO9/3oYAgjplwMStNsnRp4v/MDO9dorPS2dx32l z9EM8rKzHVSSixpw+vYoL6b7RxKnUgWX6CAymSvxXR6RWdfsF+GOM3Q2is/SKnjBcklF lSremBxoT/YI39KyYHnrxVeFsNcm5f7DB5TFWe3MLfQ49Zn7HlkFaX+bLBjXSPEzCcIf NBPAr6VlsvZqjpHky/VJBFQNYqso07wOPdrNUi9+zDJ5Koxez5ysL3wXi9X48iw88xQ4 ferUoIKeSrApGPfuypWrDeWvfXkVuE5i0cH1X2gyTb8NiwM/GrcYjT5XW8NE+YIgZZqX 5R7g==
X-Gm-Message-State: AFeK/H0nC6Vkm1celwrSRknfW5A0zHejXYh8DjWIJ7WuTdYfiL/o9ZZVf/J2HyC5h7uxNg==
X-Received: by 10.107.22.194 with SMTP id 185mr963301iow.122.1490886672188; Thu, 30 Mar 2017 08:11:12 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:28cc:dc4c:9703:6781? (t2001067c0370012828ccdc4c97036781.v6.meeting.ietf.org. [2001:67c:370:128:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 89sm1474063ioj.17.2017.03.30.08.11.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 08:11:11 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Jeff Tantsura <jefftant.ietf@gmail.com>, "Leddy, John" <John_Leddy@comcast.com>, "suresh.krishnan@ericsson.com" <suresh.krishnan@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com>
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man <ipv6@ietf.org>, IETF discussion list <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com>
Date: Fri, 31 Mar 2017 04:11:19 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VogsyBWD2ErvIIbs7JRk368E9i0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 15:11:15 -0000

On 31/03/2017 02:11, Jeff Tantsura wrote:
> Brian,
>=20
> if I understand you correctly:=20
>=20
> If properly worded (improved) draft-voyer explicitly states =E2=80=93 t=
he intention is to change the 2460(bis) behavior and to allow header inse=
rtion within a controlled domain, and given there=E2=80=99s a valid justi=
fication of why encap wouldn=E2=80=99t=E2=80=99 meet the need, you wouldn=
=E2=80=99t oppose?=20

No, I wouldn't. I might even help; hence my suggested tweak to 2460bis. N=
ote that the tricky bit (in reality and in the text) is a crisp definitio=
n of what the domain boundary is and what happens when packets with inser=
ted headers accidentally escape. We did hit that difficulty when trying (=
and failing) to define local-use rules for stateful use of the flow label=
=2E But we were trying to do that in a generic document (in effect, an ex=
tension of RFC2460) and failed for essentially the same reasons that led =
Suresh to his decision on 2460bis.

https://tools.ietf.org/html/draft-ietf-6man-flow-3697bis-01 shows some re=
mnants of that attempt.

    Brian


>=20
> Thanks!=20
>=20
> Cheers,
> Jeff
>=20
> On 3/30/17, 07:44, "ietf on behalf of Brian E Carpenter" <ietf-bounces@=
ietf.org on behalf of brian.e.carpenter@gmail.com> wrote:
>=20
>     On 30/03/2017 15:59, Leddy, John wrote:
>    =20
>     ...
>     > If this insert/delete of an SRH is prematurely prohibited;  What =
is a recommended solution to the Real World problem above.  Not use case,=
 we are implementing.
>     >=20
>     > Again; I=E2=80=99m worried we are eliminating a tool that may pro=
ve very helpful, preclude its use in future IETF work and shutdown a path=
 for Innovation in Networking,
>    =20
>     I've tried to say this before but I'm not sure people are getting i=
t:=20
>    =20
>     RFC2460bis, if approved as is, draws a line in the sand *for intero=
perability across the whole Internet*. There are reasons for this - PMTUD=
 in any form, any future replacement for the unsuccessful IPsec/AH, and a=
ll the problems of deploying extension headers that are understood by som=
e nodes and not by others.=20
>    =20
>     There is no reason why a subsequent standards-track document cannot=
 allow header insertion (and removal) within finite domains where the abo=
ve issues do not apply. In fact, an improved version of draft-voyer-6man-=
extension-header-insertion-00 could become exactly that.
>    =20
>     There doesn't need to be a tussle here.=20
>    =20
>        Brian Carpenter
>    =20
>    =20
>=20
>=20
>=20


From nobody Thu Mar 30 08:31:17 2017
Return-Path: <rraszuk@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 2687E129512; Thu, 30 Mar 2017 08:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z-wSdaCu5cGS; Thu, 30 Mar 2017 08:31:06 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CD5C129533; Thu, 30 Mar 2017 08:31:04 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id y18so78460637itc.1; Thu, 30 Mar 2017 08:31:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=b5zLQECnWrxvR4MOa5o3fJnL2vxvJEobnElGydwPSqs=; b=ZwLiwNin+0sYnmDZm0o1bE0x3tRdCCZQgfTRVn0lOVvon+k8Te1gNEMvQP6NY01HLu nuvjZS3Os0Wyc1WkQthgnWWF02uS12DoTFGmh1kedIHTbWqajvn82vuj94t9ToOTnqom tbf/mQO47R34XZiGud+6dShTN9TkJY09KJNhxiYvj7IlIhNAihP7VEMe+OgnQsjZEhgx htKUq3Q68RFxKpVnwhoca0CQvaSd8vuEeR/iIDH3Z661irF94H50/xhM7rI20ieE8Lpl Uw2diNLwziP+Bg+FZ3duV22+UlijtHtGcy3umpHoiwpHJlGLkMO7t3YBm8fxr9gXZWOh FQxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=b5zLQECnWrxvR4MOa5o3fJnL2vxvJEobnElGydwPSqs=; b=BDa1jU9ZXmrHmhufcHAcSpO/VkxlvN5QxvZNhyJP33Ug0KZsPIibG6xHXAP4QgDt7D IRqy3GUpzwRWaDUl6hGKn+zvDy6xs1Bnk0RiR2RHxjZBmAwH5vz8Qiine2BDCplT97AF 1W2y4pexSE+Xy+7TV5mdPhGp9TDxQ1gHMaj8vgsemrPj7u0/H2WzivfnjUHhGQrRQcsk 4Ue2t6651cuY7vKVXb08vbO1rONqLHC5xO9LC2ergmRej52mgDgoKZiYuz7AU9aPTYk2 JZ4rDtTYeZ7klL0xjaZhIxcxgfJN7ML/s1lio9WfPcigIA9evNepXZmirjXAVckqxoDv EtYQ==
X-Gm-Message-State: AFeK/H2p/wFG4/g5jd8Dc37K5XGFdup5+zksyRRLGSCwAU6kiDoBmJBjMThtzvd0rdOx83svTpeNnwd3pd8+fA==
X-Received: by 10.36.65.203 with SMTP id b72mr5036732itd.24.1490887863519; Thu, 30 Mar 2017 08:31:03 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 08:31:02 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 08:31:02 -0700 (PDT)
In-Reply-To: <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 30 Mar 2017 10:31:02 -0500
X-Google-Sender-Auth: W1jS1pmtbL_4D912WoIZdG-CEFw
Message-ID: <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, IETF Discussion <ietf@ietf.org>,  "suresh.krishnan@ericsson.com" <suresh.krishnan@ericsson.com>, 6man <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>,  Jeff Tantsura <jefftant.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a1143f4348163aa054bf461e5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lUTPlUgQlyPvipnvmt2MhyPsjsg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 15:31:09 -0000

--001a1143f4348163aa054bf461e5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Brian,

Could you elaborate a bit on the definition of "accidentally escaping
packets" ?

The fundamental issue with original Suresh suggestion I see is that his
proposed text kills ability to have 2460bis as normative reference in any
other draft describing or defining extension headers. And effectively stops
any work which needs to be based on 2460bis till 2460bis is updated.

Kind regards
R.






On Mar 30, 2017 10:11, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

On 31/03/2017 02:11, Jeff Tantsura wrote:
> Brian,
>
> if I understand you correctly:
>
> If properly worded (improved) draft-voyer explicitly states =E2=80=93 the
intention is to change the 2460(bis) behavior and to allow header insertion
within a controlled domain, and given there=E2=80=99s a valid justification=
 of why
encap wouldn=E2=80=99t=E2=80=99 meet the need, you wouldn=E2=80=99t oppose?

No, I wouldn't. I might even help; hence my suggested tweak to 2460bis.
Note that the tricky bit (in reality and in the text) is a crisp definition
of what the domain boundary is and what happens when packets with inserted
headers accidentally escape. We did hit that difficulty when trying (and
failing) to define local-use rules for stateful use of the flow label. But
we were trying to do that in a generic document (in effect, an extension of
RFC2460) and failed for essentially the same reasons that led Suresh to his
decision on 2460bis.

https://tools.ietf.org/html/draft-ietf-6man-flow-3697bis-01 shows some
remnants of that attempt.

    Brian


>
> Thanks!
>
> Cheers,
> Jeff
>
> On 3/30/17, 07:44, "ietf on behalf of Brian E Carpenter" <
ietf-bounces@ietf.org on behalf of brian.e.carpenter@gmail.com> wrote:
>
>     On 30/03/2017 15:59, Leddy, John wrote:
>
>     ...
>     > If this insert/delete of an SRH is prematurely prohibited;  What is
a recommended solution to the Real World problem above.  Not use case, we
are implementing.
>     >
>     > Again; I=E2=80=99m worried we are eliminating a tool that may prove=
 very
helpful, preclude its use in future IETF work and shutdown a path for
Innovation in Networking,
>
>     I've tried to say this before but I'm not sure people are getting it:
>
>     RFC2460bis, if approved as is, draws a line in the sand *for
interoperability across the whole Internet*. There are reasons for this -
PMTUD in any form, any future replacement for the unsuccessful IPsec/AH,
and all the problems of deploying extension headers that are understood by
some nodes and not by others.
>
>     There is no reason why a subsequent standards-track document cannot
allow header insertion (and removal) within finite domains where the above
issues do not apply. In fact, an improved version of
draft-voyer-6man-extension-header-insertion-00 could become exactly that.
>
>     There doesn't need to be a tussle here.
>
>        Brian Carpenter
>
>
>
>
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--001a1143f4348163aa054bf461e5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Brian,<div dir=3D"auto"><br></div><div dir=3D"auto">Co=
uld you elaborate a bit on the definition of &quot;accidentally escaping pa=
ckets&quot; ?</div><div dir=3D"auto"><br></div><div dir=3D"auto">The fundam=
ental issue with original Suresh suggestion I see is that his proposed text=
 kills ability to have 2460bis as normative reference in any other draft de=
scribing or defining extension headers. And effectively stops any work whic=
h needs to be based on 2460bis till 2460bis is updated.</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Kind regards</div><div dir=3D"auto">R.</div=
><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto">=
<br></div><div dir=3D"auto"><br></div><br><div class=3D"gmail_extra" dir=3D=
"auto"><br><div class=3D"gmail_quote">On Mar 30, 2017 10:11, &quot;Brian E =
Carpenter&quot; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.=
carpenter@gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote clas=
s=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><div class=3D"quoted-text">On 31/03/2017 02:11, Jeff Tantsura wrot=
e:<br>
&gt; Brian,<br>
&gt;<br>
&gt; if I understand you correctly:<br>
&gt;<br>
&gt; If properly worded (improved) draft-voyer explicitly states =E2=80=93 =
the intention is to change the 2460(bis) behavior and to allow header inser=
tion within a controlled domain, and given there=E2=80=99s a valid justific=
ation of why encap wouldn=E2=80=99t=E2=80=99 meet the need, you wouldn=E2=
=80=99t oppose?<br>
<br>
</div>No, I wouldn&#39;t. I might even help; hence my suggested tweak to 24=
60bis. Note that the tricky bit (in reality and in the text) is a crisp def=
inition of what the domain boundary is and what happens when packets with i=
nserted headers accidentally escape. We did hit that difficulty when trying=
 (and failing) to define local-use rules for stateful use of the flow label=
. But we were trying to do that in a generic document (in effect, an extens=
ion of RFC2460) and failed for essentially the same reasons that led Suresh=
 to his decision on 2460bis.<br>
<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-6man-flow-3697bis-01" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-ie=
tf-6man-flow-3697bis-<wbr>01</a> shows some remnants of that attempt.<br>
<font color=3D"#888888"><br>
=C2=A0 =C2=A0 Brian<br>
</font><div class=3D"quoted-text"><br>
<br>
&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; Cheers,<br>
&gt; Jeff<br>
&gt;<br>
&gt; On 3/30/17, 07:44, &quot;ietf on behalf of Brian E Carpenter&quot; &lt=
;<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> on beha=
lf of <a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmai=
l.com</a>&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0On 30/03/2017 15:59, Leddy, John wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0...<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; If this insert/delete of an SRH is prematurely=
 prohibited;=C2=A0 What is a recommended solution to the Real World problem=
 above.=C2=A0 Not use case, we are implementing.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Again; I=E2=80=99m worried we are eliminating =
a tool that may prove very helpful, preclude its use in future IETF work an=
d shutdown a path for Innovation in Networking,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0I&#39;ve tried to say this before but I&#39;m not s=
ure people are getting it:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0RFC2460bis, if approved as is, draws a line in the =
sand *for interoperability across the whole Internet*. There are reasons fo=
r this - PMTUD in any form, any future replacement for the unsuccessful IPs=
ec/AH, and all the problems of deploying extension headers that are underst=
ood by some nodes and not by others.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0There is no reason why a subsequent standards-track=
 document cannot allow header insertion (and removal) within finite domains=
 where the above issues do not apply. In fact, an improved version of draft=
-voyer-6man-extension-<wbr>header-insertion-00 could become exactly that.<b=
r>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0There doesn&#39;t need to be a tussle here.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 Brian Carpenter<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
</div><div class=3D"elided-text">------------------------------<wbr>-------=
-----------------------<wbr>--------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr=
>listinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
</div></blockquote></div><br></div></div>

--001a1143f4348163aa054bf461e5--


From nobody Thu Mar 30 08:47:46 2017
Return-Path: <suresh.krishnan@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 DFD3F1296CF; Thu, 30 Mar 2017 08:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xjJ1IpA8KSDv; Thu, 30 Mar 2017 08:47:35 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3CB512996E; Thu, 30 Mar 2017 08:47:34 -0700 (PDT)
X-AuditID: c618062d-d73ff700000009d8-65-58dd3a3b4622
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by  (Symantec Mail Security) with SMTP id 87.32.02520.B3A3DD85; Thu, 30 Mar 2017 19:02:54 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0339.000; Thu, 30 Mar 2017 11:47:28 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Robert Raszuk <robert@raszuk.net>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Leddy, John" <John_Leddy@comcast.com>, IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv86cghjjmGk6P6rsvHH5Q4qGssVmAgAD+BwCAAAesgIAAIVmAgAAFgwCAAASPgA==
Date: Thu, 30 Mar 2017 15:47:22 +0000
Message-ID: <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com>
In-Reply-To: <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_0B3335B8-A35C-497C-A6BC-E72F064D784D"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMIsWRmVeSWpSXmKPExsUyuXSPt66d1d0Ig+WHpC3aLu5jsnj19hqb xbON81ksXp59D+R2/GSyWLpgOZNF08ImZgd2j+udLcweO2fdZfdYsuQnk8fujQuYAliiuGxS UnMyy1KL9O0SuDK6r65lLlhhXLH/0gfGBsanBl2MnBwSAiYS9x4tZOpi5OIQEtjAKPHg020W CGc5o8THD23sIFVsQFUbdn5mArFFBFQlOk88YgYpYhaYzSSx+vQDNpCEsICHxKRN11ggijwl 1m08DGWHSZx4+owVxGYBaj637jeQzcHBK2AvseSYKMSyXmaJVQ9Pg83hFAiUWN+3kRHEZhQQ k/h+ag3YYmYBcYlbT+YzQZwtIvHwIkS9hICoxMvH/1ghbCWJj7/ns0PUT2GUaHnrCmLzCghK nJz5hGUCo8gsJKNmISmbhaQMIq4tsWzha+ZZQKcyC+hITF7ICBE2lXh99COUbS0x49dBNghb UWJK90P2BYwcqxg5SosLcnLTjQw2MQKj85gEm+4OxvvTPQ8xCnAwKvHwPth7O0KINbGsuDL3 EKMKUOujDasvMEqx5OXnpSqJ8Fqo3Y0Q4k1JrKxKLcqPLyrNSS0+xCjNwaIkzjvh/IUIIYH0 xJLU7NTUgtQimCwTB6dUA2OwloWH55wlXy+/CnSYYHzzztaMKdZ3Xt2ZHvnqxPqS5YEa7y90 i0suTY7f8mLeZJadUb8XvtyWZ5buMufT9Ic+au+lTt9O+rnpq6uBYHljbdSrOTfersh7XLf7 UK+Kn9B73vlH0n+/qVDIqf3uNT13igZX1cRNItPK3ipFHvpTt7/fcPs3+2ltSizFGYmGWsxF xYkAKHy0DdYCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3s8t0nzGwEU8hrBWUWU9u1ZmNLQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 15:47:39 -0000

--Apple-Mail=_0B3335B8-A35C-497C-A6BC-E72F064D784D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Robert,

> On Mar 30, 2017, at 10:31 AM, Robert Raszuk <robert@raszuk.net> wrote:
>=20
> Hi Brian,
>=20
> Could you elaborate a bit on the definition of "accidentally escaping =
packets" ?
>=20
> The fundamental issue with original Suresh suggestion I see is that =
his proposed text kills ability to have 2460bis as normative reference =
in any other draft describing or defining extension headers. And =
effectively stops any work which needs to be based on 2460bis till =
2460bis is updated.

This is not true. The *new draft* will update RFC2460bis. We do not need =
a new (RFC2460bis)bis to do this. I can understand that this would be =
bad, but that is not the intent.

Thanks
Suresh=

--Apple-Mail=_0B3335B8-A35C-497C-A6BC-E72F064D784D
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzMwMTU0NzIyWjAjBgkqhkiG9w0B
CQQxFgQUcN3EfN3JyKPngQtde2ontD6hFRcwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQBUAaE2yv1TI1LeVe6uKL9ota71E7H36U6X8PMC68rl1GYv2XRwliaxa9DqGIJx
vHG1RcCx+Vbam3W7CPs7PwvCk6X0EBy+ooVGUa87CqL0wobjVhsz6dGOY11Mx5671yahl84yz7wc
22YJXRbODpQEt9Q9FR97OLbiBMf7tx7+SKyoeRG18/U1thA3JKLSEYIDEkQhEU25GumcvAGDncFO
1wKOujDbZxAltgduYeYDBfMVuqgbHcQQxjkSKsv5yT//6d7z3FopFTE/tkE9NfkMCV6b+t8Rw//j
pDy763NIkdwpijR5bhjSLlzIy6lQoSZJ1CdC30ISn93B7JX/z87dAAAAAAAA

--Apple-Mail=_0B3335B8-A35C-497C-A6BC-E72F064D784D--


From nobody Thu Mar 30 08:58:53 2017
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 B57AF128990; Thu, 30 Mar 2017 08:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RH1uoj45dYgp; Thu, 30 Mar 2017 08:58:49 -0700 (PDT)
Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8540B126C3D; Thu, 30 Mar 2017 08:58:49 -0700 (PDT)
Received: by mail-io0-x241.google.com with SMTP id f84so3303497ioj.0; Thu, 30 Mar 2017 08:58:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=tCZ/F9hXmSCQ2Jyo/Dj81IAlMYc45elag7ntOcbZKc0=; b=hmsh1LhmQBQ1J/3Gmth307ahbqBmgJ7o5mC1zceA0B1zfEn+s27w63iTiYyFXIbzuh YK4rjBKWLnXEdWgCAcyY98zDImxbRN9Hhu80HgXEkwiuMUYjtb+0UH/Z7QMAqiLas7eJ idN/YReYNl84b2ax9VA/QRIH3SjX/h5qoLgYXk2hgNPYMbtvrwtv0qSGFxZg4eyjJ5/G V8+l0J3nmSvw/tsN7b4aEk6fkuEEh0TRrN0oO1TsEU4TheNlv9/9ovmV3kelqH9G5Vn+ IQbT6dzy9oBMXVLyQAorLkpztcUuNJGTtTcSDLk37If4KHIKLbo9JxGTQmuC2S5MSGjE PAUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=tCZ/F9hXmSCQ2Jyo/Dj81IAlMYc45elag7ntOcbZKc0=; b=JFtLb9ZXXs3WusZWspYxpJAfE2kxjIL0kx38t9oFd5JLyCLiMhjxvePZTfV7wePT2u 2Ao6blK7o87LKTYNV5T+5DbXKBb+y078LAQblLL8/YVvd7iMI+5ehPA11BmgkV5FA96F H75DFP6XIHuUsQ+fmMThlSwmoJqzVfdoWCnye8TG+cUjUL2fZoo4djNuHpcb01osABiO K+oNMhwQ4BhWdt+7tEReiwe62we/NB/l8511dAndu37f1c7MuBMGDb50u1XalBWX2n68 NxtoRQxdEGc/5lx/YYHgDUvrVvKXiYmzavm7nXvgAeldLd4TLe2B1FkyHdNpmfPyDovT iYjg==
X-Gm-Message-State: AFeK/H2/6lzfhXJGyq+7t4T7yPeCrNn9lcgjFavKDnm5xnSl37zJ/cjDpMnwDWOICeFibA==
X-Received: by 10.107.132.74 with SMTP id g71mr1208158iod.174.1490889528785; Thu, 30 Mar 2017 08:58:48 -0700 (PDT)
Received: from [31.133.134.152] (dhcp-8698.meeting.ietf.org. [31.133.134.152]) by smtp.gmail.com with ESMTPSA id 78sm1543546ity.7.2017.03.30.08.58.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 08:58:47 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Robert Raszuk <robert@raszuk.net>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, IETF Discussion <ietf@ietf.org>, "suresh.krishnan@ericsson.com" <suresh.krishnan@ericsson.com>, 6man <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <517fb98e-49ab-6a00-fdbb-9c9b7c6edbd5@gmail.com>
Date: Fri, 31 Mar 2017 04:58:52 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WovvkH839mLASHm3R6c_kN9PVc0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 15:58:52 -0000

Hi Robert,

On 31/03/2017 04:31, Robert Raszuk wrote:
> Hi Brian,
>=20
> Could you elaborate a bit on the definition of "accidentally escaping
> packets" ?

There was concern that configuration errors are always possible, so a
a host might send packets with stateful flow labels to an external
destination (first error) and the border router might fail to block
them (second error). I think your case is a bit different.

(I have a meeting this afternoon with some people who want to
define a local use of flow labels compatibly with RFC6437. These
arguments span many years.)
=20
> The fundamental issue with original Suresh suggestion I see is that his=

> proposed text kills ability to have 2460bis as normative reference in a=
ny
> other draft describing or defining extension headers. And effectively s=
tops
> any work which needs to be based on 2460bis till 2460bis is updated.

No, that's a misunderstanding of how RFC spaghetti is constructed. What w=
e'd
do is produce (I'm making this up) draft-ietf-6man-extension-header-inser=
tion
which includes an Updates: 2460bis header. If approved, it becomes a Prop=
osed
Standard that updates an Internet Standard. And it says, quite explicitly=
,
something like:

"Within a network domain defined as in Section N, there is an additional
exception to the following rule in Section 4 of [RFC2460bis]:
<blockquote>
   With one exception, extension headers are not examined, processed,
   inserted, or deleted by any node along a packet's delivery path,
   until the packet reaches the node (or each of the set of nodes, in
   the case of multicast) identified in the Destination Address field of
   the IPv6 header.
</blockquote>
The exception is that..."

That's what I meant about 2460bis being a line in the *sand* in
another message. Not carved in stone.

    Brian

>=20
> Kind regards
> R.
>=20
>=20
>=20
>=20
>=20
>=20
> On Mar 30, 2017 10:11, "Brian E Carpenter" <brian.e.carpenter@gmail.com=
>
> wrote:
>=20
> On 31/03/2017 02:11, Jeff Tantsura wrote:
>> Brian,
>>
>> if I understand you correctly:
>>
>> If properly worded (improved) draft-voyer explicitly states =E2=80=93 =
the
> intention is to change the 2460(bis) behavior and to allow header inser=
tion
> within a controlled domain, and given there=E2=80=99s a valid justifica=
tion of why
> encap wouldn=E2=80=99t=E2=80=99 meet the need, you wouldn=E2=80=99t opp=
ose?
>=20
> No, I wouldn't. I might even help; hence my suggested tweak to 2460bis.=

> Note that the tricky bit (in reality and in the text) is a crisp defini=
tion
> of what the domain boundary is and what happens when packets with inser=
ted
> headers accidentally escape. We did hit that difficulty when trying (an=
d
> failing) to define local-use rules for stateful use of the flow label. =
But
> we were trying to do that in a generic document (in effect, an extensio=
n of
> RFC2460) and failed for essentially the same reasons that led Suresh to=
 his
> decision on 2460bis.
>=20
> https://tools.ietf.org/html/draft-ietf-6man-flow-3697bis-01 shows some
> remnants of that attempt.
>=20
>     Brian
>=20
>=20
>>
>> Thanks!
>>
>> Cheers,
>> Jeff
>>
>> On 3/30/17, 07:44, "ietf on behalf of Brian E Carpenter" <
> ietf-bounces@ietf.org on behalf of brian.e.carpenter@gmail.com> wrote:
>>
>>     On 30/03/2017 15:59, Leddy, John wrote:
>>
>>     ...
>>     > If this insert/delete of an SRH is prematurely prohibited;  What=
 is
> a recommended solution to the Real World problem above.  Not use case, =
we
> are implementing.
>>     >
>>     > Again; I=E2=80=99m worried we are eliminating a tool that may pr=
ove very
> helpful, preclude its use in future IETF work and shutdown a path for
> Innovation in Networking,
>>
>>     I've tried to say this before but I'm not sure people are getting =
it:
>>
>>     RFC2460bis, if approved as is, draws a line in the sand *for
> interoperability across the whole Internet*. There are reasons for this=
 -
> PMTUD in any form, any future replacement for the unsuccessful IPsec/AH=
,
> and all the problems of deploying extension headers that are understood=
 by
> some nodes and not by others.
>>
>>     There is no reason why a subsequent standards-track document canno=
t
> allow header insertion (and removal) within finite domains where the ab=
ove
> issues do not apply. In fact, an improved version of
> draft-voyer-6man-extension-header-insertion-00 could become exactly tha=
t.
>>
>>     There doesn't need to be a tussle here.
>>
>>        Brian Carpenter
>>
>>
>>
>>
>>
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


From nobody Thu Mar 30 09:13:58 2017
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 B61F9129631; Thu, 30 Mar 2017 09:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szimti7CGMRy; Thu, 30 Mar 2017 09:13:54 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C829612997E; Thu, 30 Mar 2017 09:13:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5288; q=dns/txt; s=iport; t=1490890432; x=1492100032; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=rJB4pQa5I/S7VqwMNoWxZOViQg5tF/Mp+EXm5eOD+lc=; b=avY70Sh7Df6t3ZfbNUyW6a65ZIGjHx0cL+eT/7yZcbgGkJ0mEomeQcLU TCe/cWRp5FKUC884stiGS2pUEHpFP0G2tlW1N7YBKs8Pi/pZM5OnkEHJG phibfTa22MGZ5PnNXglmooaE3Y+SAqxv2CCzASGsV4JDPc+6H7MqZxVge Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BaAgBoLt1Y/4cNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1aBbAeDW4oRkTMflVCCDoYiAhqDHD8YAQIBAQEBAQEBayiFFQE?= =?us-ascii?q?BAQECASMEDUUFCwIBCBgCAiYCAgIwFRABAQQOBYoDCK4KgWw6ilUBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEdgQuFQ4IFCIFZgQmHWi6CMQEEiSKMdoZSAZJPgXyFKoo?= =?us-ascii?q?RiFmLEwEfOIEFWxVSAYRHHYFjdYgHgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.36,247,1486425600"; d="scan'208";a="405245993"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Mar 2017 16:13:36 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v2UGDa6k022073 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 30 Mar 2017 16:13:36 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 30 Mar 2017 12:13:35 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Thu, 30 Mar 2017 12:13:35 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
CC: "draft-ietf-mmusic-dtls-sdp.all@ietf.org" <draft-ietf-mmusic-dtls-sdp.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: Review of draft-ietf-mmusic-dtls-sdp-22
Thread-Topic: Review of draft-ietf-mmusic-dtls-sdp-22
Thread-Index: AdKn2P/3kP9b7RTPScO/+C/SvNdcJgBuRuYA
Date: Thu, 30 Mar 2017 16:13:35 +0000
Message-ID: <8F8DC522-9FF6-4414-9E02-95211155A87C@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B4CB3298B@ESESSMB109.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4CB3298B@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.169.56]
Content-Type: text/plain; charset="utf-8"
Content-ID: <92CD995A2BABA04794D28942B85EE1CC@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W9fnZXM2La2zEOXHvpsnbUWCqPM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 16:13:57 -0000

SGksIENocmlzdGVyLA0KDQo+IE9uIE1hciAyOCwgMjAxNywgYXQgMTI6MDAgUE0sIENocmlzdGVy
IEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+IHdyb3RlOg0KPiANCj4g
SGkgQ2FybG9zLA0KPiANCj4gVGhhbmtzIGZvciB5b3VyIHJldmlldyEgUGxlYXNlIHNlZSBpbmxp
bmUuDQoNCkFueXRpbWUg4oCUIHRoYW5rcyBmb3IgdGhlIGZvbGxvdy11cCENCg0KPiANCj4+IFJl
dmlld2VyOiBDYXJsb3MgUGlnbmF0YXJvDQo+PiBSZXZpZXcgcmVzdWx0OiBIYXMgTml0cw0KPj4g
DQo+PiBUaGlzIGRvY3VtZW50IGlzIHZlcnkgY29tcHJlaGVuc2l2ZS4gT3BlcmF0aW9uYWwgQ29u
c2lkZXJhdGlvbnMgYXJlDQo+PiBhZGVxdWF0ZWx5IGNvdmVyZWQuDQo+PiANCj4+IEluIHJldmll
d2luZyB0aGlzIGRvY3VtZW50LCBJIGRpZCBmaW5kIHR3byBhZGphY2VudCBpc3N1ZXMgdGhhdCBJ
DQo+PiB0aG91Z2h0IHVzZWZ1bCB0byBjb21tZW50IG9uOg0KPj4gDQo+PiAxLiBDbGFyaXR5IGFu
ZCBSZWFkYWJpbGl0eSBvZiBTZWN0aW9uIDkNCj4+IA0KPj4gSSBhcHByZWNpYXRlIHRoZSBleHBs
aWNpdCBPTEQvTkVXIGRldGFpbHMgYW5kIHNwZWNpZmljcyBvbiB3aGF0IGlzDQo+PiBjaGFuZ2Vk
IG9uIHRoZSB1cGRhdGVkIFJGQ3MuIEkgd2lzaCBtb3JlIGRvY3VtZW50cyB3b3VsZCBkbyB0aGlz
IQ0KPj4gDQo+PiBIb3dldmVyLCB0aGUgd2F5IGluIHdoaWNoIHRoaXMgaXMgZG9uZSBpcyB2ZXJ5
IGNvbmZ1c2luZyBhbmQgbm90DQo+PiByZWFsbHkgb3B0aW1pemluZyBjbGFyaXR5IGFuZCByZWFk
YWJpbGl0eS4gSXQgaXMgYW4gb3BlcmF0aW9uYWwgaXNzdWUNCj4+IGFuIGltcGxlbWVudG9yIG5v
dCB1bmRlcnN0YW5kaW5nIHRoZSBzcGVjIDotKQ0KPj4gDQo+PiBUaGUgaXNzdWUsIGluIG15IHZp
ZXcsIGlzIHdpdGggdGhlIGxhYmVscyBhbmQgbWFya2Vycy4gU3Vic2VjdGlvbnMgb2YNCj4+IFNl
Y3Rpb24gOS4yIGRvIG5vdCBmb2xsb3cgdGhlIHNlbWFudGljIHN0cnVjdHVyZSBvZiB0aGUgZG9j
dW1lbnQuDQo+PiBJbnN0ZWFkIHRoZXkgYXJlIGluY2x1ZGVkIGFzIGZvbGxvd3M6DQo+PiAiDQo+
PiBVcGRhdGUgdG8gc2VjdGlvbiA1Og0KPj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4+ICINCj4+
IFdoaWNoIGFyZSB0aGVuIGZvbGxvd2VkIGJ5IE9MRC9ORVcgY2h1bmtzLiBIb3dldmVyLCB0aGVz
ZSBjaHVua3M6DQo+PiAqIGluY2x1ZGUgU2VjdGlvbiBudW1iZXJzIGFuZCB0aXRsZXMsIA0KPj4g
KiBkbyBub3QgaGF2ZSBleHRyYSBpbmRlbnRhdGlvbiwgYW5kDQo+PiAqIGluY2x1ZGUgb25seSBC
RUdJTiBtYXJrZXIgYnV0IG5vdCBFTkQgbWFya2VyLg0KPj4gDQo+PiBMaWtlOg0KPj4gDQo+PiA5
LjIuICBVcGRhdGUgdG8gUkZDIDU3NjMNCj4+IFVwZGF0ZSB0byBzZWN0aW9uIDU6DQo+PiAtLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KPj4gT0xEIFRFWFQ6DQo+PiA1LiAgRXN0YWJsaXNoaW5nIGEgU2Vj
dXJlIENoYW5uZWwNCj4+IA0KPj4gWy4uLiBhbmQgdGhlbiwgdHdvIHBhZ2VzIGxhdGVyIC4uLl0N
Cj4+IA0KPj4gTkVXIFRFWFQ6DQo+PiA1LiAgRXN0YWJsaXNoaW5nIGEgU2VjdXJlIENoYW5uZWwN
Cj4+IA0KPj4gSSdkIHN1Z2dlc3Q6DQo+PiBhLiBVc2luZyBTZWN0aW9uIDkuMi4xLCA5LjIuMiwg
ZXRjLiBmb3IgZWFjaCBjaGFuZ2UuDQo+IA0KPiBJIGNhbiBwdXQgZWFjaCBzZWN0aW9uIGNoYW5n
ZSBpbiBhIHNlcGFyYXRlIHNlY3Rpb24uDQo+IA0KPiA5LjIuMSBVcGRhdGUgdG8gc2VjdGlvbiA1
DQo+IDkuMi4yIFVwZGF0ZSB0byBzZWN0aW9uIDYuNg0KPiAuLi4NCj4gDQo+IE9yLCBkbyB5b3Ug
d2FudCB0byBoYXZlIHRoZSBvbGQgYW5kIG5ldyB0ZXh0IGluIGRpZmZlcmVudCBzZWN0aW9ucyB0
b28/IFBlcnNvbmFsbHkgSSB3b3VsZCBsaWtlIHRvIGtlZXAgdGhlIG9sZCBhbmQgbmV3IHRleHQg
aW4gdGhlIHNhbWUgc2VjdGlvbi4NCg0KSSBhZ3JlZS4gSGF2aW5nIGEgc2VjdGlvbiBmb3IgZWFj
aCBjaGFuZ2UgY2h1bmsgKE9MRC9ORVcpIHNlZW1zIG1vc3QgY2xlYW4gYW5kIGNsZWFyLg0KDQo+
IA0KPj4gYi4gVXNlIG1vcmUgZXhwbGljaXQgY2h1bmsgZGVtYXJrYXRvcnMNCj4gDQo+IEl0IHdh
cyBiZWVuIHN1Z2dlc3RlZCB0byB1c2UgInwiLiANCj4gDQo+PiBjLiBVc2UgYmVnaW5uaW5nIGFu
ZCBlbmRpbmcgbWFya2Vycy4NCj4gDQo+IFtCRUdJTl0NCj4gQmxhaCBibGFoIGJsYWguLi4NCj4g
W0VORF0NCj4gDQo+IC0tLS0tLS0tLS0NCg0KVGhhbmsgeW91IOKAlCBhbnkgZm9ybWF0IHRoYXQg
eW91IGZlZWwgd2lsbCBhZGQgY2xhcml0eS4gUmlnaHQgbm93IGl0IHdhcyBhIGJpdCBjaGFsbGVu
Z2luZyB0byBwYXJzZS4NCg0KPiANCj4+IDIuIFRoZSBzZWNvbmQgaXNzdWUsIGFuZCBsaWtlbHkg
dGhpcyB3YXMgZGlzY3Vzc2VkLCByZWxhdGVzIHRvIHRoZSB1c2UNCj4+IG9mIFJGQyA0NTcyLiBB
IHJlZmVyZW5jZSB0byBSRkMgNDU3MiBpcyBOb3JtYXRpdmUsIGFuZCBpdCBpcyBjaXRlZA0KPj4g
d2l0aGluICJORVciIHRleHQgKG5vdCBvbmx5ICJPTEQiIHRleHQpLiBIb3dldmVyIFJGQyA0NTcy
IGhhcyBiZWVuDQo+PiBPYnNvbGV0ZWQgYnkgUkZDIDgxMjIhDQo+PiANCj4+IFRoaXMgaXMgYmVj
YXVzZSBkcmFmdC1pZXRmLW1tdXNpYy00NTcyLXVwZGF0ZSBwdWJsaXNoZWQgYXMgUkZDIDgxMjIs
DQo+PiB3aGljaCBzaG91bGQgYmUgdXBkYXRlZC4gDQo+IA0KPiBDb3JyZWN0LiBJIHdpbGwgZG8g
dGhhdCBpbiB0aGUgbmV4dCB2ZXJzaW9uLg0KDQpBY2suIFRoYW5rcy4NCg0KPiANCj4+IEJ1dCBm
b3IgZXhhbXBsZSwgd2h5IGRvZXMgTkVXIHRleHQgaGVyZSBzdGlsbCBwb2ludHMgdG8gUkZDIDQ1
NzI/DQo+IA0KPiBUaGUgcmVhc29uIGlzIHByb2JhYmx5IHRoYXQsIGluaXRpYWxseSBkcmFmdC00
NTcyLXVwZGF0ZSBkaWQgbm90IG9ic29sZXRlIFJGQyA0NTcyIC0gaXQgc2ltcGx5IHVwZGF0ZWQg
aXQuIEJ1dCwgbGF0ZXIgaXQgd2FzIGFncmVlZCB0aGF0IGRyYWZ0LTQ1NzItdXBkYXRlIHdpbGwg
b2Jzb2xldGUgUkZDIDQ1NzIsIGJ1dCB0aGF0IHdhcyBub3QgcmVmbGVjdGVkIGluIGRyYWZ0LWR0
bHMtc2RwLg0KPiANCj4gU28sIHlvdSBhcmUgY29ycmVjdCwgdGhlIG5ldyB0ZXh0IHNoYWxsIHBv
aW50IHRvIFJGQyA4MTIyLiBJIHdpbGwgZml4IHRoYXQgaW4gdGhlIG5leHQgdmVyc2lvbi4NCj4g
DQoNClBlcmZlY3QuDQoNCj4gLS0tLS0tLS0tDQo+IA0KPj4gLS0tPjgtLS0NCj4+IE5FVyBURVhU
Og0KPj4gDQo+PiA1LiAgRXN0YWJsaXNoaW5nIGEgU2VjdXJlIENoYW5uZWwNCj4+IA0KPj4gIFRo
ZSB0d28gZW5kcG9pbnRzIGluIHRoZSBleGNoYW5nZSBwcmVzZW50IHRoZWlyIGlkZW50aXRpZXMg
YXMgcGFydA0KPj4gIG9mIHRoZSBEVExTIGhhbmRzaGFrZSBwcm9jZWR1cmUgdXNpbmcgY2VydGlm
aWNhdGVzLiBUaGlzIGRvY3VtZW50DQo+PiAgdXNlcyBjZXJ0aWZpY2F0ZXMgaW4gdGhlIHNhbWUg
c3R5bGUgYXMgZGVzY3JpYmVkIGluICJDb25uZWN0aW9uLU9yaWVudGVkDQo+PiAgTWVkaWEgVHJh
bnNwb3J0IG92ZXIgdGhlIFRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKSBQcm90b2NvbA0K
Pj4gIGluIHRoZSBTZXNzaW9uIERlc2NyaXB0aW9uIFByb3RvY29sIChTRFApIiBbUkZDNDU3Ml0u
DQo+PiAtLS0+OC0tLQ0KPj4gDQo+PiBBbmQgd2h5IFJGQyA0NTcyIGlzIE5vcm1hdGl2ZWx5IHJl
ZmVyZW5jZWQ/DQo+IA0KPiBJIHdpbGwgbWFrZSB0aGUgcmVmZXJlbmNlIEluZm9ybWF0aXZlLg0K
PiANCg0KTG9va3MgZ29vZCDigJQgdGhhbmtzIGFnYWluLA0KDQrigJQgQ2FybG9zLg0KDQo+IFRo
YW5rcyENCj4gDQo+IFJlZ2FyZHMsDQo+IA0KPiBDaHJpc3Rlcg0KPiANCg0K


From nobody Thu Mar 30 09:52:53 2017
Return-Path: <rraszuk@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 36D19129865; Thu, 30 Mar 2017 09:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FxviwNm4HTfj; Thu, 30 Mar 2017 09:52:43 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 889F212953C; Thu, 30 Mar 2017 09:52:43 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id z13so23235781iof.2; Thu, 30 Mar 2017 09:52:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=SDNfM87Oz/fWUEPB3/KHz/tM0fzfo2VKteaqPdtHQtw=; b=MuKc4X7vnlJ02VSnTOE0cIqD3CjrpWUMP3k6tE3xrAPW3rIYR2+94aSOvnEzmjRIut 10y/OYxVzXVzHQa62mAbYORUAvx7HjIa3KKFy5nwlNC6bTqWErw2FzOOj5zwqoeNoYYb mcfP2uauUDlW8ZZ8XtB1d808wsreGltcgsq/qqcPHb60d+3iz4WJGm/4+WR7CpgusKf1 c0YUdgxd1avVsfkRAFw29G3nSQGUmVuypRb4fBYHsIhof8NYcxioHidTmLVFJS7itlDt I560cNQ2WAVfH6ijmU1DEHnS15VFbrh+sVXDODDnCEEKwL7EJWXdTI7uPbhdgVhQ07u0 R2wA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=SDNfM87Oz/fWUEPB3/KHz/tM0fzfo2VKteaqPdtHQtw=; b=GWOOS+O2gZpSeJ45PZeimi7DYE2whrVuj8c/+3MFU0kh0RiUzG3oBsKe551E3odnOo xmLODQzbKY9ucHq2gPOsIPgwp8BBBmd0UBlIK1wlY/2fVXpLjYRC7EiPxDhC9gqMpzcT H5YpXaB5RXUKt8RnoOMHx/jNnbAQqRgsYnScNyj56LANuPdji2YeOHcjQYzmrnDSq94g 3bKCjT2zfbWx5lS++HYyWXN9ss33rzZPCW9VIu4G9Hrcl0FvLN9w/nAkunGN78Tm4IoZ x3m4gWKr1AlvZTvdLrrb441LRCLyWMk5YIMMrZ8YHBQPiz6c30WgD+H1orKpcOQCbuQX tQLw==
X-Gm-Message-State: AFeK/H2Wt4ZRe2yDcgRCzwkzWtmq4YIn2c8W8YHV07OMhl4bUCH7BLwtX4PMbHMCmfn01dG/CkcUapWYMgoKng==
X-Received: by 10.107.7.29 with SMTP id 29mr1561996ioh.57.1490892762916; Thu, 30 Mar 2017 09:52:42 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 09:52:41 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 09:52:41 -0700 (PDT)
In-Reply-To: <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 30 Mar 2017 11:52:41 -0500
X-Google-Sender-Auth: 6kW8W3GoZxQDkE9QPwdfLi0ch9Q
Message-ID: <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Jeff Tantsura <jefftant.ietf@gmail.com>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ea6f0883455054bf5851d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8nLebXswvTgajaaM7-_5F-0k06I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 16:52:46 -0000

--001a113ea6f0883455054bf5851d
Content-Type: text/plain; charset=UTF-8

Ok so till a new document updates 2460bis any further work on EHs is frozen
as it would reference 2460bis with new text. That was my main point.

And what current EH implementations are supposed to do in the mean time ?
Would IANA allocate codepoints for EH work before 2460bis is formally
updated which in the current IETF speed is easy 2+years ?

Note that without the proposed clarification none of the above obstacles
exist.

Thx
R.

On Mar 30, 2017 10:47, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
wrote:

> Hi Robert,
>
> > On Mar 30, 2017, at 10:31 AM, Robert Raszuk <robert@raszuk.net> wrote:
> >
> > Hi Brian,
> >
> > Could you elaborate a bit on the definition of "accidentally escaping
> packets" ?
> >
> > The fundamental issue with original Suresh suggestion I see is that his
> proposed text kills ability to have 2460bis as normative reference in any
> other draft describing or defining extension headers. And effectively stops
> any work which needs to be based on 2460bis till 2460bis is updated.
>
> This is not true. The *new draft* will update RFC2460bis. We do not need a
> new (RFC2460bis)bis to do this. I can understand that this would be bad,
> but that is not the intent.
>
> Thanks
> Suresh

--001a113ea6f0883455054bf5851d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Ok so till a new document updates 2460bis any further wor=
k on EHs is frozen as it would reference 2460bis with new text. That was my=
 main point.<div dir=3D"auto"><br></div><div dir=3D"auto">And what current =
EH implementations are supposed to do in the mean time ? Would IANA allocat=
e codepoints for EH work before 2460bis is formally updated which in the cu=
rrent IETF speed is easy 2+years ?</div><div dir=3D"auto"><br></div><div di=
r=3D"auto">Note that without the proposed clarification none of the above o=
bstacles exist.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thx</div=
><div dir=3D"auto">R.</div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mar 30, 2017 10:47, &quot;Suresh Krishnan&quot; &lt;<a =
href=3D"mailto:suresh.krishnan@ericsson.com">suresh.krishnan@ericsson.com</=
a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Rob=
ert,<br>
<br>
&gt; On Mar 30, 2017, at 10:31 AM, Robert Raszuk &lt;<a href=3D"mailto:robe=
rt@raszuk.net">robert@raszuk.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Brian,<br>
&gt;<br>
&gt; Could you elaborate a bit on the definition of &quot;accidentally esca=
ping packets&quot; ?<br>
&gt;<br>
&gt; The fundamental issue with original Suresh suggestion I see is that hi=
s proposed text kills ability to have 2460bis as normative reference in any=
 other draft describing or defining extension headers. And effectively stop=
s any work which needs to be based on 2460bis till 2460bis is updated.<br>
<br>
This is not true. The *new draft* will update RFC2460bis. We do not need a =
new (RFC2460bis)bis to do this. I can understand that this would be bad, bu=
t that is not the intent.<br>
<br>
Thanks<br>
Suresh</blockquote></div></div>

--001a113ea6f0883455054bf5851d--


From nobody Thu Mar 30 09:54:43 2017
Return-Path: <mackermann@bcbsm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A4F4129810 for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 09:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level: 
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=bcbsm.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OqoorEGeAk2b for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 09:54:40 -0700 (PDT)
Received: from mx.z120.zixworks.com (bcbsm.zixworks.com [199.30.235.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2118F12953C for <ietf@ietf.org>; Thu, 30 Mar 2017 09:54:40 -0700 (PDT)
Received: from 127.0.0.1 (ZixVPM [127.0.0.1]) by Outbound.z120.zixworks.com (Proprietary) with SMTP id A8A591C190F for <ietf@ietf.org>; Thu, 30 Mar 2017 11:54:39 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [12.107.172.81]) by mx.z120.zixworks.com (Proprietary) with SMTP id C362F1C114F; Thu, 30 Mar 2017 11:54:38 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 24CD4FE04E; Thu, 30 Mar 2017 12:54:50 -0400 (EDT)
Received: from imsva2.bcbsm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C9955FE048; Thu, 30 Mar 2017 12:54:49 -0400 (EDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (unknown [216.32.180.51]) by imsva2.bcbsm.com (Postfix) with ESMTPS; Thu, 30 Mar 2017 12:54:49 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bcbsm.onmicrosoft.com;  s=selector1-bcbsm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=wduUvwCRouLEdi2To1rQHd9se6Pe3Pccbt6FA6zfKIs=; b=WDVM2FQ36KGRK9U3BZDLNimg2cnhXx/iOF6gXPWXrsogX17Zzugj4YN32bLMrx/Tv0053MzdRqB4xMr4albtxvPd+9oeC9bctscrN2vLCAvqB8sfdF4flHeXs0nAuJrOK9sgiX9PUWtJxhjl9kG4rmHxJEd3D3YSHmZyn1B0e2g=
Received: from CY4PR14MB1368.namprd14.prod.outlook.com (10.172.158.148) by CY4PR14MB1368.namprd14.prod.outlook.com (10.172.158.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1005.10; Thu, 30 Mar 2017 16:54:36 +0000
Received: from CY4PR14MB1368.namprd14.prod.outlook.com ([10.172.158.148]) by CY4PR14MB1368.namprd14.prod.outlook.com ([10.172.158.148]) with mapi id 15.01.1005.010; Thu, 30 Mar 2017 16:54:36 +0000
From: "Ackermann, Michael" <MAckermann@bcbsm.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, "Leddy, John" <John_Leddy@comcast.com>
CC: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv71giYAPcbUKK9ywM4gSjvqGssVmAgADHxICAADaS8A==
Date: Thu, 30 Mar 2017 16:54:36 +0000
Message-ID: <CY4PR14MB1368118932BAB02AE83C781FD7340@CY4PR14MB1368.namprd14.prod.outlook.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <CC4FF04D-0712-4304-BD5F-3D9F57E533A3@ericsson.com>
In-Reply-To: <CC4FF04D-0712-4304-BD5F-3D9F57E533A3@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ericsson.com; dkim=none (message not signed) header.d=none;ericsson.com; dmarc=none action=none header.from=bcbsm.com;
x-originating-ip: [31.133.151.189]
x-microsoft-exchange-diagnostics: 1; CY4PR14MB1368; 7:cYl4U0U39j1L20c4wZjlF9xEd1w9mDO+YkWpz0dSaLYonHS4V2LCWesLtQqkIfl0jzd0S71MOCanc5TcLEzt//rClWMu8vtXFhRKC2jGD+GROd/ahtHk5vl7POOzsk8pm+2U68TS2uiRqkTpJBM3t4gT6AWYaPAFO2PO2wFGBUEpgUspQ11rmaX0MWJ5DHjZ85A4z7+S2v3dCF6OTAk4krsbJhShYk8xkhqzWOo8kyaR9WgnclzRswOW2Nd+a51e2zyxeCBqtfJZTOi+hZ0PuKmh90Wl2WSsoFbyzd+UkzU+P63FyhUdjrprLNVZxMvFctUvzBZ/CDubF0NlPXdQ6Q==; 20:VP2GvtT57gNf6YV+bLxTWZPQISXqhjGhG/r82KBeGS+h8obw9GA4Gw6aaNKlsLmZYeoRNUVWTaqKA3liT4f3l8SsGuSm/JIomRgkKfvNxBh6RBuNBCNWsHmeEGMfs+V5efTQVlv5PjXWSQBmo+ecA7sHgliS17Sg0V4FcO3kRLc=
x-ms-office365-filtering-correlation-id: f385ea2c-1b58-4261-e8dd-08d4778d72d7
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:CY4PR14MB1368; 
x-microsoft-antispam-prvs: <CY4PR14MB13689F1887FE7C728BBCF9DED7340@CY4PR14MB1368.namprd14.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(158342451672863)(278428928389397)(62221491112393); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(201703131423075)(201702281528075)(201703061421075)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148); SRVR:CY4PR14MB1368; BCL:0; PCL:0; RULEID:; SRVR:CY4PR14MB1368; 
x-forefront-prvs: 02622CEF0A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39830400002)(39400400002)(39450400003)(39410400002)(24454002)(377454003)(13464003)(85664002)(55016002)(53936002)(99286003)(76176999)(50986999)(54356999)(54906002)(229853002)(38730400002)(9686003)(66066001)(3280700002)(6436002)(77096006)(102836003)(4326008)(6116002)(345774005)(6246003)(2906002)(6506006)(3846002)(7736002)(8676002)(3660700001)(81166006)(7696004)(2900100001)(8936002)(53546009)(86362001)(5660300001)(33656002)(80792005)(93886004)(25786009)(122556002)(2950100002)(189998001)(74316002)(305945005); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR14MB1368; H:CY4PR14MB1368.namprd14.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: bcbsm.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2017 16:54:36.4256 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6f56d3fa-5682-4261-b169-bc0d615da17c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR14MB1368
X-TM-AS-GCONF: 00
X-VPM-HOST: vmvpm01.z120.zixworks.com
X-VPM-GROUP-ID: 19321b46-2b69-48ec-8db7-7383451d49d2
X-VPM-MSG-ID: 419e3e74-0327-4029-8b75-f7581af17f4c
X-VPM-ENC-REGIME: Plaintext
X-VPM-IS-HYBRID: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qf1SC_4--L59vBhqprBMaTEtLeA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 16:54:42 -0000

VGhpcyBpcyBzb21ldGhpbmcgSSB0cmllZCB0byBzYXkgYXQgdGhlIG1pYyB0b2RheSwgYnV0
IEkgd2FzIHRvbyBsYXRlLiANCklmIHdlIHB1dCBwb3RlbnRpYWxseSB2YWx1YWJsZSB1c2Ug
Y2FzZXMgaW50byB0aGUgYnVja2V0IG9mICJFeGNlcHRpb25zIiwgIHRoaXMgYmVjb21lcyB5
ZXQgYW5vdGhlciBleGN1c2UgdG8gZGVsYXkgb3IgYXZvaWQgYWRvcHRpb24gb2YgSVB2NiBi
eSB0aGUgdmVyeSBsYXJnZSBwZXJjZW50YWdlIG9mIEVudGVycHJpc2VzIHdobyBoYXZlIHll
dCB0byBkbyBzbyAoYW5kIGhhdmUgbm8gc2VyaW91cyBwbGFucykgdG9kYXkuIA0KDQpJIGFt
IGhvcGVmdWwgdGhhdCB3b3JrIGluIHRoZSBJRVRGIHdpbGwgcHJvdmlkZSBmZWF0dXJlcyBh
bmQgaGVuY2UgbW90aXZhdGlvbiBmb3IgdXMgc2FkbHkgZGVsaW5xdWVudCBFbnRlcnByaXNl
cyB0byBiZWdpbiBhY3R1YWxseSB1c2luZyBJUHY2LiAgICBJIGFtIGNvbmNlcm5lZCB0aGF0
IHBlcmNlcHRpb24gb2Ygc29sdXRpb25zIGJlaW5nICJFeGNlcHRpb25zIiBvciBub24gc3Rh
bmRhcmQsIHdpbGwgY2F1c2UgY29uc3Rlcm5hdGlvbiAod2FycmFudGVkIG9yIG5vdCkgYW5k
IGF2b2lkYW5jZS4gDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlw
djYgW21haWx0bzppcHY2LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBTdXJlc2gg
S3Jpc2huYW4NClNlbnQ6IFRodXJzZGF5LCBNYXJjaCAzMCwgMjAxNyA5OjMwIEFNDQpUbzog
TGVkZHksIEpvaG4gPEpvaG5fTGVkZHlAY29tY2FzdC5jb20+DQpDYzogZHJhZnQtaWV0Zi02
bWFuLXJmYzI0NjBiaXMuYWxsQGlldGYub3JnOyA2bWFuIFdHIDxpcHY2QGlldGYub3JnPjsg
aWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IElFVEYgTGFzdCBDYWxsIGNvbmNsdXNpb24g
Zm9yIGRyYWZ0LWlldGYtNm1hbi1yZmMyNDYwYmlzLTA4DQoNCkhpIEpvaG4sDQogIFRoYW5r
cyBmb3IgY2hpbWluZyBpbi4gSSByZWNvZ25pemUgdGhhdCB5b3UgbWlnaHQgaGF2ZSB1c2Ug
Y2FzZXMgdGhhdCBtaWdodCBiZSBiZXR0ZXIgb2ZmIHdpdGggaGVhZGVyIGluc2VydGlvbiBi
dXQgSSB0aGluayB0aGV5IHNob3VsZCBiZSBoYW5kbGVkIGFzIGFuZCB3aGVuIHRoZXkgY29t
ZSB1cCBmb3IgY29uc2lkZXJhdGlvbiAoZS5nLiBpbiB0aGUgU1J2NiBkaXNjdXNzaW9ucyku
IEhvbGRpbmcgdXAgdGhpcyBkb2N1bWVudCBpcyBub3QgZ29pbmcgdG8gaGVscCBpbiBhbnkg
d2F5IGluIHJlaW50ZXJwcmV0aW5nIHdoYXQgUkZDMjQ2MCBpbnRlbmRlZC4gTXkgc3VnZ2Vz
dGlvbiBmb3IgcHJvcG9uZW50cyBvZiBzYWZlIGhlYWRlciBpbnNlcnRpb24gdG8gd3JpdGUg
dXAgaG93IGl0IGlzIGV4cGVjdGVkIHRvIHdvcmsgYW5kIGhhdmUgdGhlIGRpc2N1c3Npb24g
dGhlbi4NCg0KVGhhbmtzDQpTdXJlc2gNCg0KPiBPbiBNYXIgMjksIDIwMTcsIGF0IDk6NTkg
UE0sIExlZGR5LCBKb2huIDxKb2huX0xlZGR5QGNvbWNhc3QuY29tPiB3cm90ZToNCj4gDQo+
PiBPbiBNYXIgMTQsIDIwMTcsIGF0IDk6NDcgUE0sIFN1cmVzaCBLcmlzaG5hbiA8c3VyZXNo
LmtyaXNobmFuQGVyaWNzc29uLmNvbT4gd3JvdGU6DQo+PiANCj4+IE5FVzoNCj4+IA0KPj4g
V2l0aCBvbmUgZXhjZXB0aW9uLCBleHRlbnNpb24gaGVhZGVycyBhcmUgbm90IGV4YW1pbmVk
LCBwcm9jZXNzZWQsIA0KPj4gaW5zZXJ0ZWQsIG9yIGRlbGV0ZWQgYnkgYW55IG5vZGUgYWxv
bmcgYSBwYWNrZXQncyBkZWxpdmVyeSBwYXRoLCANCj4+IHVudGlsIHRoZSBwYWNrZXQgcmVh
Y2hlcyB0aGUgbm9kZSAob3IgZWFjaCBvZiB0aGUgc2V0IG9mIG5vZGVzLCBpbiANCj4+IHRo
ZSBjYXNlIG9mIG11bHRpY2FzdCkgaWRlbnRpZmllZCBpbiB0aGUgRGVzdGluYXRpb24gQWRk
cmVzcyBmaWVsZCBvZiANCj4+IHRoZSBJUHY2IGhlYWRlci4uLg0KPj4gDQo+PiBQbGVhc2Ug
ZmVlbCBmcmVlIHRvIGNvbW1lbnQgZWl0aGVyIHByaXZhdGVseSBvciBvbiBsaXN0IGlmIHlv
dSBoYXZlIGFueSBjb25jZXJucyB3aXRoIHRoaXMgcmVzb2x1dGlvbiBnb2luZyBmb3J3YXJk
Lg0KPiANCj4gDQo+IFN1cmVzaCwNCj4gDQo+IEkgc3RpbGwgaGF2ZSBjb25jZXJucyB0aGF0
IHdlIGFyZSBlbGltaW5hdGluZyBhIHRvb2wgdGhhdCBtYXkgcHJvdmUgdmVyeSBoZWxwZnVs
IGluIG1pZ3JhdGlvbnMgd2l0aG91dCB1bmRlcnN0YW5kaW5nIGl0cyB2YWx1ZS4NCj4gDQo+
IFRoZSBJbnRlcm5ldCB0cmFuc2l0aW9uIG9mIElQVjQgLT4gRHVhbCBTdGFjayBWNC9WNiAt
PiBJUFY2IE9ubHk7IGhhcyBiZWVuIGxvbmcsIG9wZXJhdGlvbmFsbHkgY29tcGxleCBhbmQg
ZnVsbCBvZiB1bmV4cGVjdGVkIGNoYWxsZW5nZXMuDQo+IFdlIGFyZSBvbmx5IG5vdyBzdGFy
dGluZyB0byBtYWtlIHRoZSB0cmFuc2l0aW9uIGZyb20gRHVhbCBTdGFjayB0byBJUFY2IE9u
bHksIHRoZXJlIGFyZSBzdGlsbCBtYW55IHVua25vd25zIG9uIGhvdyB0byBjb21wbGV0ZSB0
aGlzIG1pZ3JhdGlvbi4NCj4gDQo+IEFzIHdlIGNvbnRlbXBsYXRlIGZpbmlzaGluZyB0aGlz
IG1ham9yIE5ldHdvcmsgc2hpZnQg4oCTIFdlIGZpbmQgb3Vyc2VsdmVzIGluIHRoZSBlYXJs
eSBzdGFnZXMgb2YgYW5vdGhlci4NCj4gDQo+IFRoZSB0cmFuc2l0aW9uIGZyb20gUGh5c2lj
YWwgdG8gVmlydHVhbCBJbmZyYXN0cnVjdHVyZS4gIEFnYWluLCB0aGUgbWlncmF0aW9uIHdp
bGwgYmUgbG9uZywgb3BlcmF0aW9uYWxseSBjb21wbGV4IGFuZCBmdWxsIG9mIHVuZXhwZWN0
ZWQgY2hhbGxlbmdlcy4NCj4gDQo+IEluIHRoZSBvbGQgd29ybGQgd2l0aCBTZXJ2ZXJzIHJ1
bm5pbmcgQXBwbGljYXRpb25zIGluIFBoeXNpY2FsIGxvY2F0aW9ucyBkZXNpZ25lZCBmb3Ig
dmVyeSBwcmVkaWN0YWJsZSBsb2FkczsgdXNpbmcgYW4gZW5jYXAvZGVjYXAgdHVubmVsIHRv
IGVtdWxhdGUgYSBwaHlzaWNhbCBjaXJjdWl0IGJldHdlZW4gbG9jYXRpb25zIGhhcyBtYW55
IGF0dHJhY3RpdmUgcHJvcGVydGllcyDigJMgYnV0IHRoYXQgaXMgY29tcGFyZWQgdG8gYWN0
dWFsbHkgb3JkZXJpbmcgYW5kIHByb3Zpc2lvbmluZyByZWFsIGNpcmN1aXRzIGJldHdlZW4g
bG9jYXRpb25zLg0KPiANCj4gSW4gdGhlIG5ldyB3b3JsZCBvZiBkeW5hbWljIHJlc291cmNl
cyBzcHVuIHVwIG9uIGRlbWFuZCBpbiBkaXN0cmlidXRlZCBlbnZpcm9ubWVudHMgYWNyb3Nz
IG11bHRpcGxlIHByb3ZpZGVycywgQXBwbGljYXRpb25zIGhhdmluZyB0aGUgSW50ZWxsaWdl
bmNlIGFuZCBTdGF0ZSB0byBicmluZyB1cCB0aGVpciBvd24gcmVxdWlyZWQgY29ubmVjdGl2
aXR5IGlzIHZlcnkgbmF0dXJhbC4gIFRoaXMgaXMgd2hlcmUgd2UgYXJlIHB1dHRpbmcgdGhl
IG1ham9yaXR5IG9mIG91ciBlZmZvcnRzLiAgU1J2NiBlbmFibGVzIHZlcnkgYXR0cmFjdGl2
ZSBzb2x1dGlvbnMgYnkgQXBwbGljYXRpb25zIGJ1aWxkaW5nIHRoZWlyIG93biBoZWFkZXJz
Lg0KPiANCj4gVGhlIGNoYWxsZW5nZXMgY29tZSBhcyB3ZSB0cnkgdG8gbWlncmF0ZSBhbmQg
cmVxdWlyZSB0aGVzZSB0d28gaW5mcmFzdHJ1Y3R1cmVzIHRvIEludGVyb3BlcmF0ZSBmb3Ig
YSBsb25nIHRpbWUuDQo+IEJ1cmRlbmluZyB0aGUgbmV3IFZpcnR1YWwgd29ybGQgd2l0aCBP
bGQsIFN0YXRpYyBjaXJjdWl0IHBhcmFkaWdtcyBpcyBub3Qgb3B0aW1hbC4NCj4gU3VwcGxl
bWVudGluZyB0aGUgbGVnYWN5IGluZnJhc3RydWN0dXJlIHdpdGggYW4gYXNzaXN0IGZ1bmN0
aW9uIHNlZW1zIA0KPiBhIHJlYXNvbmFibGUgc29sdXRpb24uICAoRXh0IEhkciBpbnNlcnRp
b24vZGVsZXRpb24gb3IgZW5jYXAvZGVjYXAgDQo+IHR1bm5lbHMpDQo+IA0KPiBUaGUgcHJl
ZmVycmVkIGFzc2lzdCBtZWNoYW5pc20gc2VlbXMgdG8gYmUgdGhlIG9uZSB0aGF0IGFsbG93
cyB0aGUgTmV3IA0KPiBXb3JsZCB0byBvcGVyYXRlIGluIGl0cyBmaW5hbCBwcmVmZXJyZWQg
c3RhdGUsIHNlbmRpbmcgYW5kIHJlY2VpdmluZyBwYWNrZXRzIHdpdGggdGhlaXIgb3duIGhl
YWRlcnMuIChTUnY2KSBCdXQgd2hhdCBkb2VzIGFuIEFwcGxpY2F0aW9uIGluIHRoZSBuZXcg
d29ybGQgZHVlIHdoZW4gaXQgaXMgYXR0ZW1wdGluZyB0byBjb21tdW5pY2F0ZSB3aXRoIGFu
IEFwcGxpY2F0aW9uIGluIHRoZSBPbGQgV29ybGQ/DQo+IFNob3VsZG7igJl0IGl0IGJ1aWxk
IGFuIFNSdjYgaGVhZGVyPyAgVGhhdCB3b3VsZCBtZWFuIHRoYXQgdGhlIGFzc2lzdCBmdW5j
dGlvbiB3b3VsZCBuZWVkIHRvIGJlIHRoZSBsYXN0IFNJRCBpbiB0aGUgU2VnbWVudCBMaXN0
IGFuZCBiZSBjYXBhYmxlIG9mIHJlbW92aW5nIHRoZSBTUkguDQo+IFdvdWxkbuKAmXQgaXQg
bWFrZSBzZW5zZSBmb3IgdGhlIGFzc2lzdCBmdW5jdGlvbiB0byBkbyB0aGUgc2FtZSB0aGlu
ZyBpbiB0aGUgcmV2ZXJzZSBkaXJlY3Rpb247IGFuIE9sZCBXb3JsZCBTZXJ2ZXIgdGFsa2lu
ZyB0byBhIE5ldyBWaXJ0dWFsIFdvcmxkIEFwcGxpY2F0aW9uPyAgSW5zZXJ0IGFuIFNSSC4N
Cj4gDQo+IElmIHRoaXMgaW5zZXJ0L2RlbGV0ZSBvZiBhbiBTUkggaXMgcHJlbWF0dXJlbHkg
cHJvaGliaXRlZDsgIFdoYXQgaXMgYSByZWNvbW1lbmRlZCBzb2x1dGlvbiB0byB0aGUgUmVh
bCBXb3JsZCBwcm9ibGVtIGFib3ZlLiAgTm90IHVzZSBjYXNlLCB3ZSBhcmUgaW1wbGVtZW50
aW5nLg0KPiANCj4gQWdhaW47IEnigJltIHdvcnJpZWQgd2UgYXJlIGVsaW1pbmF0aW5nIGEg
dG9vbCB0aGF0IG1heSBwcm92ZSB2ZXJ5IA0KPiBoZWxwZnVsLCBwcmVjbHVkZSBpdHMgdXNl
IGluIGZ1dHVyZSBJRVRGIHdvcmsgYW5kIHNodXRkb3duIGEgcGF0aCBmb3IgDQo+IElubm92
YXRpb24gaW4gTmV0d29ya2luZywNCj4gDQo+IFRoYW5rIHlvdSBmb3IgYXNraW5nIGFuZCBs
aXN0ZW5pbmcgdG8gbXkgY29uY2VybnMsDQo+IA0KPiBKb2huIExlZGR5DQo+IENvbWNhc3QN
Cj4gDQo+IA0KPiANCj4gDQo+IA0KPiANCg0KCgpUaGUgaW5mb3JtYXRpb24gY29udGFpbmVk
IGluIHRoaXMgY29tbXVuaWNhdGlvbiBpcyBoaWdobHkgY29uZmlkZW50aWFsIGFuZCBpcyBp
bnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwocykgdG8gd2hv
bSB0aGlzIGNvbW11bmljYXRpb24gaXMgZGlyZWN0ZWQuIElmIHlvdSBhcmUgbm90IHRoZSBp
bnRlbmRlZCByZWNpcGllbnQsIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgYW55IHZp
ZXdpbmcsIGNvcHlpbmcsIGRpc2Nsb3N1cmUgb3IgZGlzdHJpYnV0aW9uIG9mIHRoaXMgaW5m
b3JtYXRpb24gaXMgcHJvaGliaXRlZC4gUGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyLCBieSBl
bGVjdHJvbmljIG1haWwgb3IgdGVsZXBob25lLCBvZiBhbnkgdW5pbnRlbmRlZCByZWNlaXB0
IGFuZCBkZWxldGUgdGhlIG9yaWdpbmFsIG1lc3NhZ2Ugd2l0aG91dCBtYWtpbmcgYW55IGNv
cGllcy4KIAogQmx1ZSBDcm9zcyBCbHVlIFNoaWVsZCBvZiBNaWNoaWdhbiBhbmQgQmx1ZSBD
YXJlIE5ldHdvcmsgb2YgTWljaGlnYW4gYXJlIG5vbnByb2ZpdCBjb3Jwb3JhdGlvbnMgYW5k
IGluZGVwZW5kZW50IGxpY2Vuc2VlcyBvZiB0aGUgQmx1ZSBDcm9zcyBhbmQgQmx1ZSBTaGll
bGQgQXNzb2NpYXRpb24uCg==


From nobody Thu Mar 30 10:00:52 2017
Return-Path: <rraszuk@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 3E646129810; Thu, 30 Mar 2017 10:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BYGvG9Cki_7n; Thu, 30 Mar 2017 10:00:47 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B88A1294DB; Thu, 30 Mar 2017 10:00:47 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id l7so23309256ioe.3; Thu, 30 Mar 2017 10:00:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=+GCyDs4QmlqzkR7cYHmpyHMA9NwFGnNG2muBQrNG408=; b=oOKowJoY8/eeA8uxAhEl6v+BHov1Ja6tuy6f8poxV6q9wQRX2xeHVvUnqpF0H7kkdi dDDlqCjsTxR4jXUU6GJdA+vTA1V3cgqmy1mCEEar93N38UWZJcTZ+KPkyUgmlV2qGt4+ nGavyAseKjL6wLhSBdLo70d0TZWDdj+zDqKvSwNP0WYKIIaRoU4wZaT1PiX9oJE+wZ8p j158PIy1ElE8QXwlugQt4u+z/aUy1cPR4lIGOJyDXrzxLoSM3LZR/7S/vbpps8xV97MX /c7DanSbQ8MIqBy7YRWzUQZ1jc6czITerzpwn87yIPDBICiqnBdwCDBUOVCsFUGj/0Uq 4mQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=+GCyDs4QmlqzkR7cYHmpyHMA9NwFGnNG2muBQrNG408=; b=MxVQw16VuZ0SfEZN4M5uG+2uwC9ATLOCX1nwzmt69hhjipcGrUpakvKAj4ZkZpKxF7 A1FNnwTshyd+E9ENNs2vdvD3LNN7yEdpQGnAIsHqh896Q5HZhsfHe7SEdWurKKCwHeiU Dn4FPtT/1muermKY1rrd4HwzuqFkmEhYcaWTjGpc1yMMBvpc1M/3qolBQT+4NJx1D0/8 tZf8OlNoEToZZ53XoThAnvLJUAiMhXvYDIIzQ74FUU81y/o/YujaE2ZoGlStYyFOwDJf JP65SKKXZL7dlzHBixnWL5Go3USk7s2mVi5difRmpxQPo+7dGa1DHrrw998bnSn4ZlWx r+YA==
X-Gm-Message-State: AFeK/H2HlbvuUN2d1d4gax0Z68E54pkJXTQqzD/BnA5GYLqjIVpyKcWNVb/UDHXZFT9q89cYxI4QcJ5UytDk8g==
X-Received: by 10.107.16.217 with SMTP id 86mr1602686ioq.228.1490893246985; Thu, 30 Mar 2017 10:00:46 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 10:00:46 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 10:00:46 -0700 (PDT)
In-Reply-To: <CA+b+ERnvtjFbCi-EzP72=zZ_poWnBxkjfan3j5sogCtxiSsCjQ@mail.gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <CC4FF04D-0712-4304-BD5F-3D9F57E533A3@ericsson.com> <CY4PR14MB1368118932BAB02AE83C781FD7340@CY4PR14MB1368.namprd14.prod.outlook.com> <CA+b+ERkBj6NOK4i0sod6Pny-2+n407CjH16oyc=GDxzu_XNkYA@mail.gmail.com> <CA+b+ERnvtjFbCi-EzP72=zZ_poWnBxkjfan3j5sogCtxiSsCjQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 30 Mar 2017 12:00:46 -0500
X-Google-Sender-Auth: pcwRvMpavafsM09FSMfmsebhSw4
Message-ID: <CA+b+ERkDzVvhqr9a0zpRLK3mLfKjOCVJ+3TDw0kQAg+Gvr762Q@mail.gmail.com>
Subject: RE: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: "Ackermann, Michael" <MAckermann@bcbsm.com>
Cc: IETF Discussion <ietf@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>,  "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ecee86281cc054bf5a248
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OW5BU9LDql1bcVOCxj8D5LBzTLA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 17:00:50 -0000

--001a113ecee86281cc054bf5a248
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Michael,

Right on the spot.

SRv6 is a first serious consideration why number of enterprise networks
would benefit from and could consider IPv6 rollout.

Otherwise all discussions so far end up with "no need" as all services are
available with zoo of different protocols over v4 and amount of v4
addresses owned by given company are of no concern of depletion any time
soon.

Best,
R.

On Mar 30, 2017 11:54, "Ackermann, Michael" <MAckermann@bcbsm.com> wrote:

This is something I tried to say at the mic today, but I was too late.
If we put potentially valuable use cases into the bucket of "Exceptions",
this becomes yet another excuse to delay or avoid adoption of IPv6 by the
very large percentage of Enterprises who have yet to do so (and have no
serious plans) today.

I am hopeful that work in the IETF will provide features and hence
motivation for us sadly delinquent Enterprises to begin actually using
IPv6.    I am concerned that perception of solutions being "Exceptions" or
non standard, will cause consternation (warranted or not) and avoidance.


-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Suresh Krishnan
Sent: Thursday, March 30, 2017 9:30 AM
To: Leddy, John <John_Leddy@comcast.com>
Cc: draft-ietf-6man-rfc2460bis.all@ietf.org; 6man WG <ipv6@ietf.org>;
ietf@ietf.org
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08

Hi John,
  Thanks for chiming in. I recognize that you might have use cases that
might be better off with header insertion but I think they should be
handled as and when they come up for consideration (e.g. in the SRv6
discussions). Holding up this document is not going to help in any way in
reinterpreting what RFC2460 intended. My suggestion for proponents of safe
header insertion to write up how it is expected to work and have the
discussion then.

Thanks
Suresh

> On Mar 29, 2017, at 9:59 PM, Leddy, John <John_Leddy@comcast.com> wrote:
>
>> On Mar 14, 2017, at 9:47 PM, Suresh Krishnan <
suresh.krishnan@ericsson.com> wrote:
>>
>> NEW:
>>
>> With one exception, extension headers are not examined, processed,
>> inserted, or deleted by any node along a packet's delivery path,
>> until the packet reaches the node (or each of the set of nodes, in
>> the case of multicast) identified in the Destination Address field of
>> the IPv6 header...
>>
>> Please feel free to comment either privately or on list if you have any
concerns with this resolution going forward.
>
>
> Suresh,
>
> I still have concerns that we are eliminating a tool that may prove very
helpful in migrations without understanding its value.
>
> The Internet transition of IPV4 -> Dual Stack V4/V6 -> IPV6 Only; has
been long, operationally complex and full of unexpected challenges.
> We are only now starting to make the transition from Dual Stack to IPV6
Only, there are still many unknowns on how to complete this migration.
>
> As we contemplate finishing this major Network shift =E2=80=93 We find ou=
rselves
in the early stages of another.
>
> The transition from Physical to Virtual Infrastructure.  Again, the
migration will be long, operationally complex and full of unexpected
challenges.
>
> In the old world with Servers running Applications in Physical locations
designed for very predictable loads; using an encap/decap tunnel to emulate
a physical circuit between locations has many attractive properties =E2=80=
=93 but
that is compared to actually ordering and provisioning real circuits
between locations.
>
> In the new world of dynamic resources spun up on demand in distributed
environments across multiple providers, Applications having the
Intelligence and State to bring up their own required connectivity is very
natural.  This is where we are putting the majority of our efforts.  SRv6
enables very attractive solutions by Applications building their own
headers.
>
> The challenges come as we try to migrate and require these two
infrastructures to Interoperate for a long time.
> Burdening the new Virtual world with Old, Static circuit paradigms is not
optimal.
> Supplementing the legacy infrastructure with an assist function seems
> a reasonable solution.  (Ext Hdr insertion/deletion or encap/decap
> tunnels)
>
> The preferred assist mechanism seems to be the one that allows the New
> World to operate in its final preferred state, sending and receiving
packets with their own headers. (SRv6) But what does an Application in the
new world due when it is attempting to communicate with an Application in
the Old World?
> Shouldn=E2=80=99t it build an SRv6 header?  That would mean that the assi=
st
function would need to be the last SID in the Segment List and be capable
of removing the SRH.
> Wouldn=E2=80=99t it make sense for the assist function to do the same thi=
ng in
the reverse direction; an Old World Server talking to a New Virtual World
Application?  Insert an SRH.
>
> If this insert/delete of an SRH is prematurely prohibited;  What is a
recommended solution to the Real World problem above.  Not use case, we are
implementing.
>
> Again; I=E2=80=99m worried we are eliminating a tool that may prove very
> helpful, preclude its use in future IETF work and shutdown a path for
> Innovation in Networking,
>
> Thank you for asking and listening to my concerns,
>
> John Leddy
> Comcast
>
>
>
>
>
>



The information contained in this communication is highly confidential and
is intended solely for the use of the individual(s) to whom this
communication is directed. If you are not the intended recipient, you are
hereby notified that any viewing, copying, disclosure or distribution of
this information is prohibited. Please notify the sender, by electronic
mail or telephone, of any unintended receipt and delete the original
message without making any copies.

 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
nonprofit corporations and independent licensees of the Blue Cross and Blue
Shield Association.

--001a113ecee86281cc054bf5a248
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Michael,<div dir=3D"auto"><br></div><div dir=3D"auto">Rig=
ht on the spot.</div><div dir=3D"auto"><br></div><div dir=3D"auto">SRv6 is =
a first serious consideration why number of enterprise networks would benef=
it from and could consider IPv6 rollout.</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">Otherwise all discussions so far end up with &quot;no need=
&quot; as all services are available with zoo of different protocols over v=
4 and amount of v4 addresses owned by given company are of no concern of de=
pletion any time soon.</div><div dir=3D"auto"><br></div><div dir=3D"auto">B=
est,</div><div dir=3D"auto">R.</div></div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Mar 30, 2017 11:54, &quot;Ackermann, Michael&qu=
ot; &lt;<a href=3D"mailto:MAckermann@bcbsm.com">MAckermann@bcbsm.com</a>&gt=
; wrote:<br type=3D"attribution"><blockquote class=3D"quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is something=
 I tried to say at the mic today, but I was too late.<br>
If we put potentially valuable use cases into the bucket of &quot;Exception=
s&quot;,=C2=A0 this becomes yet another excuse to delay or avoid adoption o=
f IPv6 by the very large percentage of Enterprises who have yet to do so (a=
nd have no serious plans) today.<br>
<br>
I am hopeful that work in the IETF will provide features and hence motivati=
on for us sadly delinquent Enterprises to begin actually using IPv6.=C2=A0 =
=C2=A0 I am concerned that perception of solutions being &quot;Exceptions&q=
uot; or non standard, will cause consternation (warranted or not) and avoid=
ance.<br>
<div class=3D"quoted-text"><br>
<br>
-----Original Message-----<br>
From: ipv6 [mailto:<a href=3D"mailto:ipv6-bounces@ietf.org">ipv6-bounces@ie=
tf.org</a>] On Behalf Of Suresh Krishnan<br>
Sent: Thursday, March 30, 2017 9:30 AM<br>
To: Leddy, John &lt;<a href=3D"mailto:John_Leddy@comcast.com">John_Leddy@co=
mcast.com</a>&gt;<br>
Cc: <a href=3D"mailto:draft-ietf-6man-rfc2460bis.all@ietf.org">draft-ietf-6=
man-rfc2460bis.<wbr>all@ietf.org</a>; 6man WG &lt;<a href=3D"mailto:ipv6@ie=
tf.org">ipv6@ietf.org</a>&gt;; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.o=
rg</a><br>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08<br=
>
<br>
</div><div class=3D"elided-text">Hi John,<br>
=C2=A0 Thanks for chiming in. I recognize that you might have use cases tha=
t might be better off with header insertion but I think they should be hand=
led as and when they come up for consideration (e.g. in the SRv6 discussion=
s). Holding up this document is not going to help in any way in reinterpret=
ing what RFC2460 intended. My suggestion for proponents of safe header inse=
rtion to write up how it is expected to work and have the discussion then.<=
br>
<br>
Thanks<br>
Suresh<br>
<br>
&gt; On Mar 29, 2017, at 9:59 PM, Leddy, John &lt;<a href=3D"mailto:John_Le=
ddy@comcast.com">John_Leddy@comcast.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; On Mar 14, 2017, at 9:47 PM, Suresh Krishnan &lt;<a href=3D"mailto=
:suresh.krishnan@ericsson.com">suresh.krishnan@ericsson.com</a>&gt; wrote:<=
br>
&gt;&gt;<br>
&gt;&gt; NEW:<br>
&gt;&gt;<br>
&gt;&gt; With one exception, extension headers are not examined, processed,=
<br>
&gt;&gt; inserted, or deleted by any node along a packet&#39;s delivery pat=
h,<br>
&gt;&gt; until the packet reaches the node (or each of the set of nodes, in=
<br>
&gt;&gt; the case of multicast) identified in the Destination Address field=
 of<br>
&gt;&gt; the IPv6 header...<br>
&gt;&gt;<br>
&gt;&gt; Please feel free to comment either privately or on list if you hav=
e any concerns with this resolution going forward.<br>
&gt;<br>
&gt;<br>
&gt; Suresh,<br>
&gt;<br>
&gt; I still have concerns that we are eliminating a tool that may prove ve=
ry helpful in migrations without understanding its value.<br>
&gt;<br>
&gt; The Internet transition of IPV4 -&gt; Dual Stack V4/V6 -&gt; IPV6 Only=
; has been long, operationally complex and full of unexpected challenges.<b=
r>
&gt; We are only now starting to make the transition from Dual Stack to IPV=
6 Only, there are still many unknowns on how to complete this migration.<br=
>
&gt;<br>
&gt; As we contemplate finishing this major Network shift =E2=80=93 We find=
 ourselves in the early stages of another.<br>
&gt;<br>
&gt; The transition from Physical to Virtual Infrastructure.=C2=A0 Again, t=
he migration will be long, operationally complex and full of unexpected cha=
llenges.<br>
&gt;<br>
&gt; In the old world with Servers running Applications in Physical locatio=
ns designed for very predictable loads; using an encap/decap tunnel to emul=
ate a physical circuit between locations has many attractive properties =E2=
=80=93 but that is compared to actually ordering and provisioning real circ=
uits between locations.<br>
&gt;<br>
&gt; In the new world of dynamic resources spun up on demand in distributed=
 environments across multiple providers, Applications having the Intelligen=
ce and State to bring up their own required connectivity is very natural.=
=C2=A0 This is where we are putting the majority of our efforts.=C2=A0 SRv6=
 enables very attractive solutions by Applications building their own heade=
rs.<br>
&gt;<br>
&gt; The challenges come as we try to migrate and require these two infrast=
ructures to Interoperate for a long time.<br>
&gt; Burdening the new Virtual world with Old, Static circuit paradigms is =
not optimal.<br>
&gt; Supplementing the legacy infrastructure with an assist function seems<=
br>
&gt; a reasonable solution.=C2=A0 (Ext Hdr insertion/deletion or encap/deca=
p<br>
&gt; tunnels)<br>
&gt;<br>
&gt; The preferred assist mechanism seems to be the one that allows the New=
<br>
&gt; World to operate in its final preferred state, sending and receiving p=
ackets with their own headers. (SRv6) But what does an Application in the n=
ew world due when it is attempting to communicate with an Application in th=
e Old World?<br>
&gt; Shouldn=E2=80=99t it build an SRv6 header?=C2=A0 That would mean that =
the assist function would need to be the last SID in the Segment List and b=
e capable of removing the SRH.<br>
&gt; Wouldn=E2=80=99t it make sense for the assist function to do the same =
thing in the reverse direction; an Old World Server talking to a New Virtua=
l World Application?=C2=A0 Insert an SRH.<br>
&gt;<br>
&gt; If this insert/delete of an SRH is prematurely prohibited;=C2=A0 What =
is a recommended solution to the Real World problem above.=C2=A0 Not use ca=
se, we are implementing.<br>
&gt;<br>
&gt; Again; I=E2=80=99m worried we are eliminating a tool that may prove ve=
ry<br>
&gt; helpful, preclude its use in future IETF work and shutdown a path for<=
br>
&gt; Innovation in Networking,<br>
&gt;<br>
&gt; Thank you for asking and listening to my concerns,<br>
&gt;<br>
&gt; John Leddy<br>
&gt; Comcast<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
<br>
<br>
</div>The information contained in this communication is highly confidentia=
l and is intended solely for the use of the individual(s) to whom this comm=
unication is directed. If you are not the intended recipient, you are hereb=
y notified that any viewing, copying, disclosure or distribution of this in=
formation is prohibited. Please notify the sender, by electronic mail or te=
lephone, of any unintended receipt and delete the original message without =
making any copies.<br>
<br>
=C2=A0Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan =
are nonprofit corporations and independent licensees of the Blue Cross and =
Blue Shield Association.<br>
</blockquote></div><br></div>

--001a113ecee86281cc054bf5a248--


From nobody Thu Mar 30 11:19:40 2017
Return-Path: <jinmei.tatuya@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 B9C50129485; Thu, 30 Mar 2017 11:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.702
X-Spam-Level: 
X-Spam-Status: No, score=-1.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Njob3pAkQhtJ; Thu, 30 Mar 2017 11:19:30 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2517127B60; Thu, 30 Mar 2017 11:19:30 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id r45so46627871qte.3; Thu, 30 Mar 2017 11:19:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ARl0jkgKyJjitiWQZ0d6FZsABzzpgnt0+RV6zGNLQWQ=; b=WivoRZryw7ueFoFzVjW9HN+Vf1tpVhb+GqC6ypu8EjNjfEmg+RTIgIZej0A28Ou3ga YlwhmgMKfXngGyI0BUfSk2UG67MYcRijLeRGj6ot6X/A8NIZewQ/Es54JlhB7EJXdqqS fP0AEx3w8Fsn+zNNBunl/sJqQsEZQEQmgNFvqf+XIkDF5sgXa+wrW70Uio5DE9faiduG f6eZPjZsGulGTKAvx0VXGzoGGoJlOGixLPZ4zgSW2lSuUjDka/QzedYDqJfuWHiqdGm0 NWxm0MHthoTJQGuWt5j7brOw4MWJu4zNcprWzg4Zhj8sZ9rNFILu/rfRBDBh1OcVRZ21 wq9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ARl0jkgKyJjitiWQZ0d6FZsABzzpgnt0+RV6zGNLQWQ=; b=roNzCE1tFpwtwlRb8xH8A8WEnf1WLdtozmeDaeGCNfZObNRrZHvUDGa+bKZ4ZY8oJn BRyyvj86QEGAdW0c3uJQn99o4SomG9rFU7cpZ7G2e/1ogDn1zvaGb+LEogAmgC6ceGZE bUgjaii8Lz1vTltanxv2lL7b+qhmGp2Jn6teZJAs0CiOwwKIl2ZStyWnEZDymKrC6CYZ ZhtXRix5he6aUWeLMqYTmCvlkDumExvuzqzSzT2ExEnD1gCF9cnNF/2RQY+UoqRn+PPB Q+T9L2G6S0CCMDKm0IVXkOuJOe+BluqMmRwLXCPCDcyS+/yWtNw+cacuYNzQ4TSHh/u4 ZdwQ==
X-Gm-Message-State: AFeK/H0aZv+DDm5v7KPClvHpjeyHR05FmL0SAlNAD/fU66A0nQgPKffSR5L2uQVPOprgAN5hJOGh6RDk9lgkUg==
X-Received: by 10.200.42.151 with SMTP id b23mr1100732qta.163.1490897969544; Thu, 30 Mar 2017 11:19:29 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.61.204 with HTTP; Thu, 30 Mar 2017 11:19:28 -0700 (PDT)
In-Reply-To: <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Thu, 30 Mar 2017 11:19:28 -0700
X-Google-Sender-Auth: AzNg4_Wz-DcOKgXtJXKLwmgPGwI
Message-ID: <CAJE_bqfBt_uytbgQ+=zO4ed9jnc9p=FgPuLH-efgdjFKa+C4jQ@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Robert Raszuk <robert@raszuk.net>
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>, 6man WG <ipv6@ietf.org>,  IETF Discussion <ietf@ietf.org>, "Leddy, John" <John_Leddy@comcast.com>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0X1jOdETk0YKjMkb1lqiNn-L93I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 18:19:33 -0000

At Thu, 30 Mar 2017 11:52:41 -0500,
Robert Raszuk <robert@raszuk.net> wrote:

> Ok so till a new document updates 2460bis any further work on EHs is frozen
> as it would reference 2460bis with new text. That was my main point.

I don't get the logic...an "update" can start immediately once such a
draft new proposal is available.  The update won't be formally
completed until it gets some formal state like a standard track RFC,
and it will take time, but that wouldn't necessarily mean a further
work is "frozen"; it's not very clear to me what this term means in
this context, but it's quite common development takes place while the
spec is being discussed as a draft, and it's also not uncommon some
commercial operators even start deploying it.  On the other hand, even
if we now agreed that rfc2460bis should explicitly allow such "further
work", the discussion itself would take long and wouldn't be completed
soon.

But IMO it's irresponsible to leave the text ambiguous and let some
other people misunderstand it, possibly even more casually and/or in
the global Internet, for the comfort of some particular future work.
I think we're now trying to help avoid the latest clarification in
rfc2460bis to be interpreted as an "outright ban" of future updates
while still trying to be responsible for the soundness of the global
Internet.  In my understanding Brian's additional text is one such
attempt (I also proposed text in that sense at the time of WGLC,
although it wasn't adopted in the end).  If that text is still not
enough we can discuss how to phrase it.  And, while I suspect people
who wanted to keep the ambiguity will never be satisfied with the
result as long as the added clarification remains, I believe that's a
reasonable compromise to achieve a balance between being responsible
and not (unintentionally) discouraging future updates.

--
JINMEI, Tatuya


From nobody Thu Mar 30 11:52:47 2017
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 5D4751296BB; Thu, 30 Mar 2017 11:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LdtvjHf9RQIL; Thu, 30 Mar 2017 11:52:38 -0700 (PDT)
Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F75D126B72; Thu, 30 Mar 2017 11:52:38 -0700 (PDT)
Received: by mail-io0-x243.google.com with SMTP id f84so3829721ioj.0; Thu, 30 Mar 2017 11:52:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=5qYrU/NaBvdG3XwLePJYfVqmimSjo+UJQcEH/XMgbeY=; b=nJ+V7CGYig4sXJhq5sb/CguI4C5pkzXXaOSPsvgdrJuOfcHXIUoLqB2RDEy4V93ILz v3MfJeyZ2Y+YUT5t2bhF8djdoxThfUeDPQ0t4hu0mVy51+m/dq74PXLXrUhJ7m83qzXY 5H0tRhW/WZFuFlKSQXujRJi6coctTtD0gg+z/p2xtszaaLklfVwrf2GjWAdXM1AHk3gz 4jmVaLVvFi3S6jeUukQKS1isC7dJtLwcw15qOp/77eNrAcf/3bggEyWelKdqwUvWY8Me UzND0H/tB8veB0PLTZNB/x+6T83kkreuMC5OHfXwX3LtDm2GkeCWl7oUF1Hcy7mhMf6M yWpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=5qYrU/NaBvdG3XwLePJYfVqmimSjo+UJQcEH/XMgbeY=; b=sJDDUu2KFNrWzJIPsThwu4napnbPt0j3UEsjZrZQEOHXj9ZYhYXxSlNBjQvzHWEFdX gRZA+11WUIEyb/XNxbijJEWu1V3s8BOCEEWzfMLcJWZ0yWKC/D0nM5GFB1S/V+vNCZai 9S4Hzozn4Pp8mWs1QyR8yKxwncRiCShySfUxCFqoQYk2xJUMkqvAuKHwYigWRYDEC1oI sMsU4LfyaGks+AHTbkBsGIRpNDyVEe+0xhBIKTLrtVQ8CI+ZVOHJGARObcT0tSlMgk3w s03qFO8QjdsjqOvUG27ZP07C//Cs/14Bz2K1Rryne4saE2FWzNK3pw+0bEM+gbnYg9/e X82Q==
X-Gm-Message-State: AFeK/H1zgmMqwjP5Msi5wRGHZcvXuii2qA+oJf2JNWcIBIONYEO+DCYnBdrBjEv74muJlA==
X-Received: by 10.107.27.207 with SMTP id b198mr2307494iob.218.1490899957539;  Thu, 30 Mar 2017 11:52:37 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:28cc:dc4c:9703:6781? (t2001067c0370012828ccdc4c97036781.v6.meeting.ietf.org. [2001:67c:370:128:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id p6sm1845991iof.12.2017.03.30.11.52.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 11:52:36 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Robert Raszuk <robert@raszuk.net>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <CAJE_bqfBt_uytbgQ+=zO4ed9jnc9p=FgPuLH-efgdjFKa+C4jQ@mail.gmail.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, IETF Discussion <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <caf480e6-5d39-8056-490e-fa1fe032b157@gmail.com>
Date: Fri, 31 Mar 2017 07:52:44 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAJE_bqfBt_uytbgQ+=zO4ed9jnc9p=FgPuLH-efgdjFKa+C4jQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qA4imfnI5aJXClx1lyKHRfSpEYw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 18:52:40 -0000

On 31/03/2017 07:19, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
> At Thu, 30 Mar 2017 11:52:41 -0500,
> Robert Raszuk <robert@raszuk.net> wrote:
>=20
>> Ok so till a new document updates 2460bis any further work on EHs is f=
rozen
>> as it would reference 2460bis with new text. That was my main point.
>=20
> I don't get the logic...an "update" can start immediately once such a
> draft new proposal is available.  The update won't be formally
> completed until it gets some formal state like a standard track RFC,
> and it will take time, but that wouldn't necessarily mean a further
> work is "frozen";=20

Exactly. At this time the *quickest* way forward is to get 2460bis throug=
h
the IESG, progress the -extension-header-insertion draft ASAP, and in due=

time do an early assignment request for draft-ietf-6man-segment-routing-h=
eader

If you try that early assignment request today, it seems likely to fail.

   Brian

> it's not very clear to me what this term means in
> this context, but it's quite common development takes place while the
> spec is being discussed as a draft, and it's also not uncommon some
> commercial operators even start deploying it.  On the other hand, even
> if we now agreed that rfc2460bis should explicitly allow such "further
> work", the discussion itself would take long and wouldn't be completed
> soon.
>=20
> But IMO it's irresponsible to leave the text ambiguous and let some
> other people misunderstand it, possibly even more casually and/or in
> the global Internet, for the comfort of some particular future work.
> I think we're now trying to help avoid the latest clarification in
> rfc2460bis to be interpreted as an "outright ban" of future updates
> while still trying to be responsible for the soundness of the global
> Internet.  In my understanding Brian's additional text is one such
> attempt (I also proposed text in that sense at the time of WGLC,
> although it wasn't adopted in the end).  If that text is still not
> enough we can discuss how to phrase it.  And, while I suspect people
> who wanted to keep the ambiguity will never be satisfied with the
> result as long as the added clarification remains, I believe that's a
> reasonable compromise to achieve a balance between being responsible
> and not (unintentionally) discouraging future updates.
>=20
> --
> JINMEI, Tatuya
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


From nobody Thu Mar 30 12:00:49 2017
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 A2CEE129A99 for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 12:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id esUgYMh15cLR for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 12:00:41 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CC8B129AA1 for <ietf@ietf.org>; Thu, 30 Mar 2017 12:00:26 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id r45so47626744qte.3 for <ietf@ietf.org>; Thu, 30 Mar 2017 12:00:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=JRkJ5QbawCMIc+J4++k3hfs1cVfiLkKfiuRk0Mrv7ic=; b=dmvPS1slNT2cfCNJNYyWh0bBWWYUjurZahWQqhJtahv+GdRjES6AhFF4puMc+jtPPr 6pq4QEa1NG/BBfL97Dl4sEMU9U6I5ijY+cMAm7NhDrIqMltm32aTTqgQUJx/jBE00JrU OyPTosGpsblkCPrKla8S4J914vOoM9vysakoR4cULcMkHU42lAfeyj17Dq05FwcDOaTm RYcez0xNtFl9bzdWPSfqLIvT3PXlIp421TusJwQ+n/j5kAXLMPbZ7+OtORKYRqGPJKuk ns89EoR4N5A3fTyO5cMj8WqrfYcYRptop0sVH+v/dxI6Mkl/nmFwjq3ZUZD4otZL+p4B DWMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=JRkJ5QbawCMIc+J4++k3hfs1cVfiLkKfiuRk0Mrv7ic=; b=Y1zbB1SUDaYYfS64K+51ao9HgfwgvBaYyNgm0o0X1OU//oH3yuwpGEXGetCWg94T7s FSB+eKwzaPAsLL0Nr3ZsA6S+035Af1VmUeCcc3vleopsGuZMhsLQtpDe6oXle2wX+SUn LrGQc0egaZbu68HuQ+NxzUfBaxzdfcFASlZf3KW6yHy1/3wt9G0dVExPDAV6h5gtSiLk lSbtUjqsDQD7IQ+ucwQXggMEebDPYXZ0NQwe9eX156hHJfBax0E1yoXlecSpizvQu7db Tmkgp9vFhKzcoLeqIAzyNrksn2d7X92irFi27PHQlKwX0tF5MCHfj/goWo8OcA2Su1R4 RUgg==
X-Gm-Message-State: AFeK/H1SDzlqbrd8am/BZcTIsPiFrezSI56BAcSfwuaRhbHfAushjwEVawq9Ydr0OQcYUHJSM3hFWu8qsGYDeF8r
X-Received: by 10.200.43.185 with SMTP id m54mr1354179qtm.122.1490900423848; Thu, 30 Mar 2017 12:00:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.177.11 with HTTP; Thu, 30 Mar 2017 11:59:43 -0700 (PDT)
In-Reply-To: <F8D0F7F4-414B-44A4-B6D0-428D506D97C7@tislabs.com>
References: <F8D0F7F4-414B-44A4-B6D0-428D506D97C7@tislabs.com>
From: Warren Kumari <warren@kumari.net>
Date: Thu, 30 Mar 2017 13:59:43 -0500
Message-ID: <CAHw9_iL-UdKNsBSP1imzOg1PcjAvhk=b7Uw+nG-gDeQSOfgUxQ@mail.gmail.com>
Subject: Re: secdir review of draft-ietf-dnsop-nsec-aggressiveuse
To: Sandra Murphy <sandy@tislabs.com>
Cc: IETF Security Directorate <secdir@ietf.org>, draft-ietf-dnsop-nsec-aggressiveuse@ietf.org,  dnsops-chairs@ietf.org, The IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IlqMVv_g-RebIYrqL71fdxSCdd0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 19:00:44 -0000

On Tue, Mar 28, 2017 at 11:34 AM, Sandra Murphy <sandy@tislabs.com> wrote:
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.

Thank you very much for your review, and getting it in early, it makes
addressing them much easier.


>
> This document suggests that resolvers should use NSEC/NSEC3 proof of non-=
existence for a domain name in a received query to generate a negative repl=
y, rather than relying on the current spec of an exact match to the domain =
name.  Generating positive replies from wildcard answers is also suggested.
>
> The motivation is improvements in latency for queriers and improvements i=
n bandwidth and CPU load on recursive resolvers and validation servers.
>
> I have no serious objections about the draft.
>
> I am curious about my thought that an attacker might find this of benefit=
, as they can learn of non-existence in just one query, rather than every n=
ame in a NSEC denied range. I know zone walking is a concern to some, but I=
 do not know if ease of determining non-existence is also a concern.


I may have missed something, but I do not see the concern -- an
attacker can already learn of non-existence in just one query; that is
exactly what NSEC (already) provides.
If an attacker queries e.g the root for .belkin they get back (trimmed):
$ dig +dnssec belkin
beer. 44025 IN NSEC bentley. NS DS RRSIG NSEC

This tells the attacker that nothing exists between beer and bentley
(in one query). All that this document does is optimize the recursive
server so that, if the attacker tries to instead do e.g a dictionary
attack and ask many names between beer and bentley the recursive (and
auths) have less work to do. The attacker only advantage to the
attacker is that they have to wait slightly less time doing a
dictionary attack -- but, they would be much better off asking for the
(existing) NSEC info directly.

>
> Section 7 explicitly spells out the changes to RFC4035 are explicitly spe=
lled
> out as to what is removed and what replaces it.  Section 5 is not so clea=
rly
> delineated.

Yup. At one point we had the changes explicitly spelled out in both,
the WG felt that this was overly long and duplicating the text was
confusing.

>
> The last paragraph of 5., nothing in 5.1 or 5.2, and the last paragraph o=
f 5.3
> use SHOUD/MUST/MAY kinds of language.  For the paragraphs that don=E2=80=
=99t - should
> they?  For the paragraphs that do, is this additional behavior or a
> replacement for existing spec (i.e. like the section 7 update to RFC4035)=
.
> If a replacement, a replacement of what?  If not, where do the new paragr=
aphs
> fit?
>

I don't think that these bits to need the 2119 language - they are
more explanatory, and providing explanation / justification for the
change baing made to RFC4035 (which is updated in Section 7).


> The following is a sequential set of comments, not in importance order.
>
> page 3
>
>   This document updates RFC 4035 to allow recursive resolvers to use
>   NSEC/NSEC3 resource records to synthesize negative answers from the
>   information they have in the cache.
>
> re: recursive resolvers - is the technique not applicable to stub resolve=
rs?
> (I do see references to stub resolver caches in a web search, but you can=
=E2=80=99t
> trust the web.)

Good catch -- we fixed a similar issue in the Abstract, but missed it here.

>
>  [RFC8020], and [I-D.vixie-dnsext-resimprove] proposes first steps to
>   using NXDOMAIN information for more effective caching.  This takes
>   this technique further.
>
> Unless rfc8020 and the vixie draft are the same thing (don=E2=80=99t thin=
k so),
> should be =E2=80=9Cpropose=E2=80=9D.
>
>
> Too many uses of =E2=80=9Cthis=E2=80=9D in that last sentence - I presume=
 you mean
>   This draft takes those previous techniques further.

Thank you.  I changed these to:
[RFC8020] and [I-D.vixie-dnsext-resimprove propose steps to using
NXDOMAIN information for more effective caching. This document takes
this technique further.

>
>
> page 4
>
>   If a validating resolver receives a query for cat.example.com, it
>   contacts its resolver (which may be itself)
>
> Maybe
>
>   If a validating resolver receives a query for cat.example.com, it
>   contacts its recursive resolver (which may be itself)

Thank you -- I believe that the current is more correct; in most cases
the validating resolver will be a recursive resolver and will be
contacting a authoritative server. In a few cases (currently, in the
future this may change as validating stubs become common) it will be a
stub contacting a recursive, so the text in the draft covers both
cases.

>
> About:
>
>   and also has
>   privacy implications (e.g: typos leak out further than necessary).
>
> Does it also make certain explorations easier, where someone can find out=
 a range
> that does not exist by doing just one query rather than query every name =
in the
> range?  Or is that sort of exploration already prevented by other techniq=
ues?

Nope; as above. Attackers already have the capability to find ranges
which do not exist (querying for the NSEC record).

>
>   If a query is received for leek.example.org, it contacts its resolver
>   (which may be itself)
>
> I suggest =E2=80=9Cthe resolver contacts its <recursive> resolver=E2=80=
=9D - the query is not
> doing the contacting.

Thank you. I changed it to:
"If a query is received for leek.example.org, the system contacts its
resolver (which may be itself) to query..."

I think that this addresses your comment in a more general manner.

>
>
> page 6
>
> section 5.1 and 5.2 say =E2=80=9Cresolver can immediately return=E2=80=9D=
 - is this meant
> to specify new behavior, should they have SHOULD/MAY/MUST kinds of words?

I don't *think* so -- it means that is has the ability to; other text
suggests what it actually should to.

>
> page 7
>
>   Section 5 of [RFC2308] states that the maximum number of negative
>   cache TTL value is 3 hours (10800).
>
> I don=E2=80=99t find a maximum in RFC2308.  I do find:
>                    Values of one to three hours have been found to work w=
ell
>   and would make sensible a default.
> Did I miss something?
>

See below.

>
> =E2=80=9Cthe maximum number of negative cache TTL value is=E2=80=9D - a b=
it twisty.  Did you
> mean something like:
>
>  Section 5 of [RFC2308] states that the maximum negative cache TTL value =
is=E2=80=9D
>
> otherwise, I=E2=80=99d think =E2=80=9Cnumber of =E2=80=A6 values=E2=80=9D=
, but even so I don=E2=80=99t think there are
> multiple values here. Are there?

Nope, you did not miss anything, and yes, yes that was twisty - 'twas
an artifact of poor editing.

I changed this to be:
Section 5 of [RFC2308 suggests a maximum default negative cache TTL
value of 3 hours (10800). It is RECOMMENDED that validating resolvers
limit the maximum effective TTL value of negative responses
(NSEC/NSEC3 RRs) to this same value.

>
> page 9
>
> <truly nitty>
>
> The text says
>
>   Thanks to Mark Andrews for providing the helpful notes for
>   implementors provided in Appendix B.
>
>   The authors would like to specifically thank
>   =E2=80=A6
>   Mark Andrews also provided the
>   helpful notes for implementors (https://www.ietf.org/mail-
>   archive/web/dnsop/current/msg18332.html) which we made into
>   Appendix B.
>
> Perhaps you intended to thank him twice?  No problem, just wondering.

Nope, edit fail. Fixed.



Thank you again for your comments. I've posted / am just about to post
a new version with them addressed / incorporated.

W

>
> =E2=80=94Sandy
>
>
>
>
>
>



--=20
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Thu Mar 30 12:03:36 2017
Return-Path: <aaron.falk@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 60B0A129A35; Thu, 30 Mar 2017 12:03:28 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOblMES4xtnR; Thu, 30 Mar 2017 12:03:26 -0700 (PDT)
Received: from mail-qt0-x244.google.com (mail-qt0-x244.google.com [IPv6:2607:f8b0:400d:c0d::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34F49129A28; Thu, 30 Mar 2017 12:03:25 -0700 (PDT)
Received: by mail-qt0-x244.google.com with SMTP id n37so7453287qtb.3; Thu, 30 Mar 2017 12:03:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version; bh=BtLJqWdgGLd0pl8rvRGV9ovFMIC6X5w7DS1PmjKcxKM=; b=BRmPXln25x6H/+NhQW09XHAgyCQWWEexIA9pXgnX9GaUMOytcsNQ4h3pqjmV4zcJRR WNOIedM9QNbyPyh7qiAFLHda8lon8xyeEfPcK2Sw01hsviTbJoXKtz3EBMWWB4avQzfn OVZMcMcH04ALiQxwUtXdIq6FstaDR6+jBNXoN6YhJ2wfqSDKoqfKoXi7r6KMYYxC8Hhj CQl48F/8jtStBT7czvBLQdj+dTBaypzQJMlsJpaBjYg4kf6J3Ht/TnnUlocyrkSFH/DZ ImPVB/oQd+x11lDF58vNqxZ7v9sBkkU7mGb2OOtJfNtNlb4odrQDKJ+ur+GRsDB6IZTl 3d0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version; bh=BtLJqWdgGLd0pl8rvRGV9ovFMIC6X5w7DS1PmjKcxKM=; b=IFi8qmejLdpe4D/4+HcOHnSFLh9kORp26yx24UtufzJOI8l4ozKMgjfmHN7lfB3/8j jZJqRdSaJTQax7Oi06neSd572lP1TPKedYEIePDKkPz06rrzGS8EpGK0ICfHBOa0Am2W 33MG/tHckA3qbT2Bs/wc06b2eAsVIK1vOCdHq7Im3bW1jDZ7vXu2AJcizb9Bdul/Xv9M yUijFSUQLpOsaHD+Daw8cDOhQR3hGF8alTvrASvsj8lcU31FTGkEUEayUQOqAMAsH+lD A3diOwDnRBqgmgDWMtwvbqyLcLpjefP6xGIDwgS6UWNiMz77vZmWcPtAyf4r/EnpU7QL e20w==
X-Gm-Message-State: AFeK/H3YHowF7E3zdguEaAC2ZvIs70IPg9YigQomnlN5QGMpG75FtYpsMRmn+YL46heWvw==
X-Received: by 10.200.3.214 with SMTP id z22mr1476079qtg.3.1490900603498; Thu, 30 Mar 2017 12:03:23 -0700 (PDT)
Received: from [172.19.43.75] (t2001067c03700128b540ab43ee7be279.v6.meeting.ietf.org. [2001:67c:370:128:b540:ab43:ee7b:e279]) by smtp.gmail.com with ESMTPSA id t124sm1977595qkf.27.2017.03.30.12.03.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 12:03:22 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, 98attendees@ietf.org
Subject: Reminder: Bad Attitude PechaKucha in Chicago -- TONIGHT!
Date: Thu, 30 Mar 2017 14:03:21 -0500
Message-ID: <BF9C1F6B-F211-4BE5-AC4A-C8D344449916@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_0B172BD0-8AC0-45EE-BEA8-8D3F0371690E_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NWyKQbr_O7i7zl8TC9BLh_ymwaA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 19:03:28 -0000

--=_MailMate_0B172BD0-8AC0-45EE-BEA8-8D3F0371690E_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

DATE: 		Thursday, March 30
TIME: 		21:30 - 23:00 (estimated)
LOCATION: 	Zurich G.
BAR: 		cash, 21:00 - 23:30 (estimated)
COUNT: 		9

=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94

A Pecha Kucha is a lightning-talk presentation format, originating in =

Japan, where a speaker presents 20 image-only slides that are each on =

the screen for 20 seconds and advance automatically.  With each talk =

lasting for 6:40, it has the feature of forcing presentations -- good or =

bad -- to be focused and brief.  This is an unofficial event. Topics are =

encouraged to be a IETF-related and satirical or controversial in some =

way, although not mean-spirited.  Anyone can participate in this social =

event.  Video from the Berlin and Seoul PKs can be found =

[here](http://snaggletooth.akam.ai).

Format Details:

* Presentation slots are open to all, assigned first come, first served.
* To reserve a presentation slot, send a name and title to =

aaron.falk@gmail.com and receive confirmation.
* Presenters must agree to adhere to the Pecha Kucha format (20 slides, =

primarily image-only, automatically advancing every 20 seconds).
* There are lots of online tutorials and suggestions for how to make a =

good Pecha Kucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

[[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pecha=
=2Ehtml)], =

[[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].
--=_MailMate_0B172BD0-8AC0-45EE-BEA8-8D3F0371690E_=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">DATE:         Thursday, March 30<br>
TIME:         21:30 - 23:00 (estimated)<br>
LOCATION:     Zurich G.<br>
BAR:         cash, 21:00 - 23:30 (estimated)<br>
COUNT:         9</p>

<p dir=3D"auto">=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94</p>=


<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin and Seoul PKs can be found <a href=3D"ht=
tp://snaggletooth.akam.ai" style=3D"color:#3983C4">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#3983C4">aaron.falk@gmail.com<=
/a> and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#3983C4">1</a>], [<a href=3D"http://blog.indezine.com/20=
12/05/10-tips-to-create-and-present-pecha.html" style=3D"color:#3983C4">2=
</a>], [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha=
-kucha/" style=3D"color:#3983C4">3</a>].</li>
</ul>
</div>
</div>
</body>
</html>

--=_MailMate_0B172BD0-8AC0-45EE-BEA8-8D3F0371690E_=--


From nobody Thu Mar 30 12:26:10 2017
Return-Path: <tjc@ecs.soton.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 D01581292FC; Thu, 30 Mar 2017 12:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ZjZYj5cFtNV; Thu, 30 Mar 2017 12:26:07 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92F58126B72; Thu, 30 Mar 2017 12:26:06 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2UJQ2u0026523; Thu, 30 Mar 2017 20:26:02 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v2UJQ2u0026523
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1490901963; bh=eSbJ1LvwGAIkTkXpXudA0NKu9jA=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=puIoOd4K0mut1FooXADzlJkND9swmmnEk9Kn9+jkKlm/YkenrMJsGL0EPY00SPNJX A7M3q6tIdbAr1MxRHuN8R0doVpjIghJSaf8CKEB/x18XavZspjEugYgDZShdf0ZCFF teezY5s9e1AIlltEsq8ZXBQYyhA0SrdBLtfvYaRU=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y2YKQ21151011028gw ret-id none; Thu, 30 Mar 2017 20:26:02 +0100
Received: from t2001067c0370012814f6e8a6bc91a44d.v6.meeting.ietf.org (t2001067c0370012814f6e8a6bc91a44d.v6.meeting.ietf.org [IPv6:2001:67c:370:128:14f6:e8a6:bc91:a44d]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2UJPuSC028259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Mar 2017 20:25:57 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAJE_bqfBt_uytbgQ+=zO4ed9jnc9p=FgPuLH-efgdjFKa+C4jQ@mail.gmail.com>
Date: Thu, 30 Mar 2017 20:25:56 +0100
Cc: "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|6fa5e3b676a6186d2c95426220e13766y2YKQ203tjc|ecs.soton.ac.uk|F33C543B-1834-4B9A-ADB4-0E4EA2E889D0@ecs.soton.ac.uk>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <CAJE_bqfBt_uytbgQ+=zO4ed9jnc9p=FgPuLH-efgdjFKa+C4jQ@mail.gmail.com> <F33C543B-1834-4B9A-ADB4-0E4EA2E889D0@ecs.soton.ac.uk>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ssss
X-smtpf-Report: sid=y2YKQ2115101102800; tid=y2YKQ21151011028gw; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v2UJQ2u0026523
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2F0q2V_6xercfVeC3WDewh8588c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 19:26:10 -0000

Hi,

> On 30 Mar 2017, at 19:19, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
>=20
> At Thu, 30 Mar 2017 11:52:41 -0500,
> Robert Raszuk <robert@raszuk.net> wrote:
>=20
>> Ok so till a new document updates 2460bis any further work on EHs is =
frozen
>> as it would reference 2460bis with new text. That was my main point.
>=20
> I don't get the logic...an "update" can start immediately once such a
> draft new proposal is available.  The update won't be formally
> completed until it gets some formal state like a standard track RFC,
> and it will take time, but that wouldn't necessarily mean a further
> work is "frozen"; it's not very clear to me what this term means in
> this context, but it's quite common development takes place while the
> spec is being discussed as a draft, and it's also not uncommon some
> commercial operators even start deploying it.  On the other hand, even
> if we now agreed that rfc2460bis should explicitly allow such "further
> work", the discussion itself would take long and wouldn't be completed
> soon.
>=20
> But IMO it's irresponsible to leave the text ambiguous and let some
> other people misunderstand it, possibly even more casually and/or in
> the global Internet, for the comfort of some particular future work.
> I think we're now trying to help avoid the latest clarification in
> rfc2460bis to be interpreted as an "outright ban" of future updates
> while still trying to be responsible for the soundness of the global
> Internet.  In my understanding Brian's additional text is one such
> attempt (I also proposed text in that sense at the time of WGLC,
> although it wasn't adopted in the end).  If that text is still not
> enough we can discuss how to phrase it.  And, while I suspect people
> who wanted to keep the ambiguity will never be satisfied with the
> result as long as the added clarification remains, I believe that's a
> reasonable compromise to achieve a balance between being responsible
> and not (unintentionally) discouraging future updates.

Repeating what I said at the mic, my views echo those of Jinmei, =
Michael, Lorenzo and Brian. I agree with the decision to progress =
RFC2460-bis to IS including Suresh=E2=80=99s text. I=E2=80=99d also like =
to see Brian=E2=80=99s short amendment included, which makes explicit =
Internet scope as the default target.

Advancing 2460bis doesn=E2=80=99t freeze work on SR; that work can =
continue today. I don=E2=80=99t see the new SR header insertion draft =
completing in =E2=80=9Ca couple of weeks=E2=80=9D; it=E2=80=99s much =
more likely to take several months or even a year to progress through WG =
adoption and eventual publication, to ensure good and robust input. For =
adoption, I=E2=80=99d expect many people to want the draft to include =
text on a) why vanilla encapsulation is not sufficient and b) how the =
insertion can guaranteed to be done safely for specific scenario(s). But =
that=E2=80=99s all very possible.

And please do note that publishing 2460-bis as an Internet Standard does =
not set it in stone. Your SR work can update it, as could other future =
RFC(s) on other new mechanism(s) or innovation(s) that have yet to be =
proposed. I=E2=80=99d argue that it=E2=80=99s pretty likely we=E2=80=99ll =
see other RFCs update 2460-bis; that shouldn=E2=80=99t be a surprise if =
it=E2=80=99s a protocol that we=E2=80=99ll be using for the next 20-30 =
years or more. For each, we=E2=80=99ll just see =E2=80=9CUpdated by:=E2=80=
=9D tags in the RFC header. The current RFC2460 has accumulated nine =
such tags in 19 years, so about one every two years.

On enterprise deployment I=E2=80=99d argue that, if anything, moving to =
IS should help strengthen the case for deployment, because it confirms =
proven widescale deployment.  The four criteria for moving to IS are =
described in Section 2.2 of RFC6410, but are summarised as "a high =
degree of technical maturity and by a generally held belief that the =
specified protocol or service provides significant benefit to the =
Internet community=E2=80=9D. I=E2=80=99d hope we have very strong =
consensus on that statement.

Tim=


From nobody Thu Mar 30 12:27:34 2017
Return-Path: <tim.chown@jisc.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 792A0129436 for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 12:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rvOH6MqUGMBC for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 12:27:27 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 580A3129A30 for <ietf@ietf.org>; Thu, 30 Mar 2017 12:27:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1490902040; bh=8ZPUbbCw/MCX2WhtUc5kZEeE3Bp5V33DtvdS70ObevM=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To:Content-ID:MIME-Version:Content-Type:Content-Transfer-Encoding; b=TtjHvyP0AIH8AaL43p7XU4vauGbQXyRSZ49OUmwBd9yZPdm+irWrGIBVwr0GUSPE+nzA34dz4yS2W0RBY4iF/uHHDvW/ENGOF0K3PkjdxFXGjcHx57ZCn0clYlej/NJYmgVCkY09An2nKshwifDs8ThuRwYk/BYK/DAW1KsbJy4=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0245.outbound.protection.outlook.com [213.199.154.245]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-69-NboFHBkTN96UIBp4JcYO3Q-1; Thu, 30 Mar 2017 20:27:17 +0100
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1138.eurprd07.prod.outlook.com (10.163.188.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1005.2; Thu, 30 Mar 2017 19:27:15 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::29d9:4eb6:edcf:55dc]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::29d9:4eb6:edcf:55dc%14]) with mapi id 15.01.1019.009; Thu, 30 Mar 2017 19:27:15 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv71giYAPcbUKK9ywM4gSjvqGssVmAgAC6+QCAAAergIAAIVqAgAAFggCAAASRAIAAEj+AgAAYQACAABLvAA==
Date: Thu, 30 Mar 2017 19:27:15 +0000
Message-ID: <5E233A42-42C7-4D16-A755-7E0314BFB2D4@jisc.ac.uk>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <CAJE_bqfBt_uytbgQ+=zO4ed9jnc9p=FgPuLH-efgdjFKa+C4jQ@mail.gmail.com>
In-Reply-To: <CAJE_bqfBt_uytbgQ+=zO4ed9jnc9p=FgPuLH-efgdjFKa+C4jQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:128:14f6:e8a6:bc91:a44d]
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1138; 7:YFVkAzssIxyEys6p4Sb9HSCfwZeCqtzAN+VvUYEcCYetLWymBW4KHCpSZ3KMklOH2vNfPdWFsbB0KjWKu1kbdqELH76ef3iaNMkKi6xbB/N69cUi4eeirsXFA/hZ32MDfNnJsvBrmkPCXIWSlN58339fSKBejZ1upjE9xi47pjLr/Hw0agm2Bya4uHLsIrjF5EkWoobLVmWQauAhnTctG4WbQYicLhkxKm6QxPamH7vNrbhzjl01i/PYmuXoqyrP4yAcSmCEnwimfBaCRQ5spJoDHwcxTWGVSIw+WmmhQlhSHVl2H7GgO/+eFAfjP5umMn9IJ4nVBL5WZKWgErGmrA==; 20:i7NIVx7NO5tgFAfOvsSbeILR0bSw9wd4ZEbOuzjuyOyY1i+GQ4xvd35wh+uO59M8Vk3+uQmdDChbgwrRbWAAL5uLAQ1HGa2cCWDl+AVtGfBshUQ3vLv1W3sV4zalk32Ie/Vve5++NjM1LFa+WJgCOuUxsD+ePdH3P7emDgFqPzg=
x-ms-office365-filtering-correlation-id: 48cdb482-a1b2-41d5-2f79-08d477a2c611
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:AM3PR07MB1138; 
x-microsoft-antispam-prvs: <AM3PR07MB1138D900CFBABE6448F6A307D6340@AM3PR07MB1138.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(93006070)(93001070)(10201501046)(3002001)(6041248)(20161123555025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(20161123560025)(20161123562025)(20161123564025)(6072148); SRVR:AM3PR07MB1138; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1138; 
x-forefront-prvs: 02622CEF0A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39450400003)(39410400002)(39840400002)(39400400002)(24454002)(57306001)(7736002)(81166006)(83716003)(42882006)(99286003)(189998001)(2950100002)(8936002)(305945005)(38730400002)(3660700001)(450100002)(4326008)(2906002)(36756003)(25786009)(6436002)(53546009)(2900100001)(82746002)(74482002)(3280700002)(229853002)(33656002)(2501003)(561944003)(6116002)(50226002)(6512007)(5660300001)(102836003)(6486002)(8676002)(6246003)(53936002)(230783001)(5250100002)(86362001)(76176999)(6506006)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1138; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <044F46D857C5BE41910636F411274E49@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2017 19:27:15.6723 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1138
X-MC-Unique: NboFHBkTN96UIBp4JcYO3Q-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IFMHfagLlv05iElGl-qhOFpZEkk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 19:27:29 -0000

SGksDQoNCj4gT24gMzAgTWFyIDIwMTcsIGF0IDE5OjE5LCDnpZ7mmI7pgZTlk4kgPGppbm1laUB3
aWRlLmFkLmpwPiB3cm90ZToNCj4gDQo+IEF0IFRodSwgMzAgTWFyIDIwMTcgMTE6NTI6NDEgLTA1
MDAsDQo+IFJvYmVydCBSYXN6dWsgPHJvYmVydEByYXN6dWsubmV0PiB3cm90ZToNCj4gDQo+PiBP
ayBzbyB0aWxsIGEgbmV3IGRvY3VtZW50IHVwZGF0ZXMgMjQ2MGJpcyBhbnkgZnVydGhlciB3b3Jr
IG9uIEVIcyBpcyBmcm96ZW4NCj4+IGFzIGl0IHdvdWxkIHJlZmVyZW5jZSAyNDYwYmlzIHdpdGgg
bmV3IHRleHQuIFRoYXQgd2FzIG15IG1haW4gcG9pbnQuDQo+IA0KPiBJIGRvbid0IGdldCB0aGUg
bG9naWMuLi5hbiAidXBkYXRlIiBjYW4gc3RhcnQgaW1tZWRpYXRlbHkgb25jZSBzdWNoIGENCj4g
ZHJhZnQgbmV3IHByb3Bvc2FsIGlzIGF2YWlsYWJsZS4gIFRoZSB1cGRhdGUgd29uJ3QgYmUgZm9y
bWFsbHkNCj4gY29tcGxldGVkIHVudGlsIGl0IGdldHMgc29tZSBmb3JtYWwgc3RhdGUgbGlrZSBh
IHN0YW5kYXJkIHRyYWNrIFJGQywNCj4gYW5kIGl0IHdpbGwgdGFrZSB0aW1lLCBidXQgdGhhdCB3
b3VsZG4ndCBuZWNlc3NhcmlseSBtZWFuIGEgZnVydGhlcg0KPiB3b3JrIGlzICJmcm96ZW4iOyBp
dCdzIG5vdCB2ZXJ5IGNsZWFyIHRvIG1lIHdoYXQgdGhpcyB0ZXJtIG1lYW5zIGluDQo+IHRoaXMg
Y29udGV4dCwgYnV0IGl0J3MgcXVpdGUgY29tbW9uIGRldmVsb3BtZW50IHRha2VzIHBsYWNlIHdo
aWxlIHRoZQ0KPiBzcGVjIGlzIGJlaW5nIGRpc2N1c3NlZCBhcyBhIGRyYWZ0LCBhbmQgaXQncyBh
bHNvIG5vdCB1bmNvbW1vbiBzb21lDQo+IGNvbW1lcmNpYWwgb3BlcmF0b3JzIGV2ZW4gc3RhcnQg
ZGVwbG95aW5nIGl0LiAgT24gdGhlIG90aGVyIGhhbmQsIGV2ZW4NCj4gaWYgd2Ugbm93IGFncmVl
ZCB0aGF0IHJmYzI0NjBiaXMgc2hvdWxkIGV4cGxpY2l0bHkgYWxsb3cgc3VjaCAiZnVydGhlcg0K
PiB3b3JrIiwgdGhlIGRpc2N1c3Npb24gaXRzZWxmIHdvdWxkIHRha2UgbG9uZyBhbmQgd291bGRu
J3QgYmUgY29tcGxldGVkDQo+IHNvb24uDQo+IA0KPiBCdXQgSU1PIGl0J3MgaXJyZXNwb25zaWJs
ZSB0byBsZWF2ZSB0aGUgdGV4dCBhbWJpZ3VvdXMgYW5kIGxldCBzb21lDQo+IG90aGVyIHBlb3Bs
ZSBtaXN1bmRlcnN0YW5kIGl0LCBwb3NzaWJseSBldmVuIG1vcmUgY2FzdWFsbHkgYW5kL29yIGlu
DQo+IHRoZSBnbG9iYWwgSW50ZXJuZXQsIGZvciB0aGUgY29tZm9ydCBvZiBzb21lIHBhcnRpY3Vs
YXIgZnV0dXJlIHdvcmsuDQo+IEkgdGhpbmsgd2UncmUgbm93IHRyeWluZyB0byBoZWxwIGF2b2lk
IHRoZSBsYXRlc3QgY2xhcmlmaWNhdGlvbiBpbg0KPiByZmMyNDYwYmlzIHRvIGJlIGludGVycHJl
dGVkIGFzIGFuICJvdXRyaWdodCBiYW4iIG9mIGZ1dHVyZSB1cGRhdGVzDQo+IHdoaWxlIHN0aWxs
IHRyeWluZyB0byBiZSByZXNwb25zaWJsZSBmb3IgdGhlIHNvdW5kbmVzcyBvZiB0aGUgZ2xvYmFs
DQo+IEludGVybmV0LiAgSW4gbXkgdW5kZXJzdGFuZGluZyBCcmlhbidzIGFkZGl0aW9uYWwgdGV4
dCBpcyBvbmUgc3VjaA0KPiBhdHRlbXB0IChJIGFsc28gcHJvcG9zZWQgdGV4dCBpbiB0aGF0IHNl
bnNlIGF0IHRoZSB0aW1lIG9mIFdHTEMsDQo+IGFsdGhvdWdoIGl0IHdhc24ndCBhZG9wdGVkIGlu
IHRoZSBlbmQpLiAgSWYgdGhhdCB0ZXh0IGlzIHN0aWxsIG5vdA0KPiBlbm91Z2ggd2UgY2FuIGRp
c2N1c3MgaG93IHRvIHBocmFzZSBpdC4gIEFuZCwgd2hpbGUgSSBzdXNwZWN0IHBlb3BsZQ0KPiB3
aG8gd2FudGVkIHRvIGtlZXAgdGhlIGFtYmlndWl0eSB3aWxsIG5ldmVyIGJlIHNhdGlzZmllZCB3
aXRoIHRoZQ0KPiByZXN1bHQgYXMgbG9uZyBhcyB0aGUgYWRkZWQgY2xhcmlmaWNhdGlvbiByZW1h
aW5zLCBJIGJlbGlldmUgdGhhdCdzIGENCj4gcmVhc29uYWJsZSBjb21wcm9taXNlIHRvIGFjaGll
dmUgYSBiYWxhbmNlIGJldHdlZW4gYmVpbmcgcmVzcG9uc2libGUNCj4gYW5kIG5vdCAodW5pbnRl
bnRpb25hbGx5KSBkaXNjb3VyYWdpbmcgZnV0dXJlIHVwZGF0ZXMuDQoNClJlcGVhdGluZyB3aGF0
IEkgc2FpZCBhdCB0aGUgbWljLCBteSB2aWV3cyBlY2hvIHRob3NlIG9mIEppbm1laSwgTWljaGFl
bCwgTG9yZW56byBhbmQgQnJpYW4uIEkgYWdyZWUgd2l0aCB0aGUgZGVjaXNpb24gdG8gcHJvZ3Jl
c3MgUkZDMjQ2MC1iaXMgdG8gSVMgaW5jbHVkaW5nIFN1cmVzaOKAmXMgdGV4dC4gSeKAmWQgYWxz
byBsaWtlIHRvIHNlZSBCcmlhbuKAmXMgc2hvcnQgYW1lbmRtZW50IGluY2x1ZGVkLCB3aGljaCBt
YWtlcyBleHBsaWNpdCBJbnRlcm5ldCBzY29wZSBhcyB0aGUgZGVmYXVsdCB0YXJnZXQuDQoNCkFk
dmFuY2luZyAyNDYwYmlzIGRvZXNu4oCZdCBmcmVlemUgd29yayBvbiBTUjsgdGhhdCB3b3JrIGNh
biBjb250aW51ZSB0b2RheS4gSSBkb27igJl0IHNlZSB0aGUgbmV3IFNSIGhlYWRlciBpbnNlcnRp
b24gZHJhZnQgY29tcGxldGluZyBpbiDigJxhIGNvdXBsZSBvZiB3ZWVrc+KAnTsgaXTigJlzIG11
Y2ggbW9yZSBsaWtlbHkgdG8gdGFrZSBzZXZlcmFsIG1vbnRocyBvciBldmVuIGEgeWVhciB0byBw
cm9ncmVzcyB0aHJvdWdoIFdHIGFkb3B0aW9uIGFuZCBldmVudHVhbCBwdWJsaWNhdGlvbiwgdG8g
ZW5zdXJlIGdvb2QgYW5kIHJvYnVzdCBpbnB1dC4gRm9yIGFkb3B0aW9uLCBJ4oCZZCBleHBlY3Qg
bWFueSBwZW9wbGUgdG8gd2FudCB0aGUgZHJhZnQgdG8gaW5jbHVkZSB0ZXh0IG9uIGEpIHdoeSB2
YW5pbGxhIGVuY2Fwc3VsYXRpb24gaXMgbm90IHN1ZmZpY2llbnQgYW5kIGIpIGhvdyB0aGUgaW5z
ZXJ0aW9uIGNhbiBndWFyYW50ZWVkIHRvIGJlIGRvbmUgc2FmZWx5IGZvciBzcGVjaWZpYyBzY2Vu
YXJpbyhzKS4gQnV0IHRoYXTigJlzIGFsbCB2ZXJ5IHBvc3NpYmxlLg0KDQpBbmQgcGxlYXNlIGRv
IG5vdGUgdGhhdCBwdWJsaXNoaW5nIDI0NjAtYmlzIGFzIGFuIEludGVybmV0IFN0YW5kYXJkIGRv
ZXMgbm90IHNldCBpdCBpbiBzdG9uZS4gWW91ciBTUiB3b3JrIGNhbiB1cGRhdGUgaXQsIGFzIGNv
dWxkIG90aGVyIGZ1dHVyZSBSRkMocykgb24gb3RoZXIgbmV3IG1lY2hhbmlzbShzKSBvciBpbm5v
dmF0aW9uKHMpIHRoYXQgaGF2ZSB5ZXQgdG8gYmUgcHJvcG9zZWQuIEnigJlkIGFyZ3VlIHRoYXQg
aXTigJlzIHByZXR0eSBsaWtlbHkgd2XigJlsbCBzZWUgb3RoZXIgUkZDcyB1cGRhdGUgMjQ2MC1i
aXM7IHRoYXQgc2hvdWxkbuKAmXQgYmUgYSBzdXJwcmlzZSBpZiBpdOKAmXMgYSBwcm90b2NvbCB0
aGF0IHdl4oCZbGwgYmUgdXNpbmcgZm9yIHRoZSBuZXh0IDIwLTMwIHllYXJzIG9yIG1vcmUuIEZv
ciBlYWNoLCB3ZeKAmWxsIGp1c3Qgc2VlIOKAnFVwZGF0ZWQgYnk64oCdIHRhZ3MgaW4gdGhlIFJG
QyBoZWFkZXIuIFRoZSBjdXJyZW50IFJGQzI0NjAgaGFzIGFjY3VtdWxhdGVkIG5pbmUgc3VjaCB0
YWdzIGluIDE5IHllYXJzLCBzbyBhYm91dCBvbmUgZXZlcnkgdHdvIHllYXJzLg0KDQpPbiBlbnRl
cnByaXNlIGRlcGxveW1lbnQgSeKAmWQgYXJndWUgdGhhdCwgaWYgYW55dGhpbmcsIG1vdmluZyB0
byBJUyBzaG91bGQgaGVscCBzdHJlbmd0aGVuIHRoZSBjYXNlIGZvciBkZXBsb3ltZW50LCBiZWNh
dXNlIGl0IGNvbmZpcm1zIHByb3ZlbiB3aWRlc2NhbGUgZGVwbG95bWVudC4gIFRoZSBmb3VyIGNy
aXRlcmlhIGZvciBtb3ZpbmcgdG8gSVMgYXJlIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDIuMiBvZiBS
RkM2NDEwLCBidXQgYXJlIHN1bW1hcmlzZWQgYXMgImEgaGlnaCBkZWdyZWUgb2YgdGVjaG5pY2Fs
IG1hdHVyaXR5IGFuZCBieSBhIGdlbmVyYWxseSBoZWxkIGJlbGllZiB0aGF0IHRoZSBzcGVjaWZp
ZWQgcHJvdG9jb2wgb3Igc2VydmljZSBwcm92aWRlcyBzaWduaWZpY2FudCBiZW5lZml0IHRvIHRo
ZSBJbnRlcm5ldCBjb21tdW5pdHnigJ0uIEnigJlkIGhvcGUgd2UgaGF2ZSB2ZXJ5IHN0cm9uZyBj
b25zZW5zdXMgb24gdGhhdCBzdGF0ZW1lbnQuDQoNClRpbQ==


From nobody Thu Mar 30 13:21:04 2017
Return-Path: <mackermann@bcbsm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16CA2128708 for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 13:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level: 
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=bcbsm.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4LCyEn4LbZl for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 13:20:51 -0700 (PDT)
Received: from mx.z120.zixworks.com (bcbsm.zixworks.com [199.30.235.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48563126B72 for <ietf@ietf.org>; Thu, 30 Mar 2017 13:20:51 -0700 (PDT)
Received: from 127.0.0.1 (ZixVPM [127.0.0.1]) by Outbound.z120.zixworks.com (Proprietary) with SMTP id 8D404C1634 for <ietf@ietf.org>; Thu, 30 Mar 2017 15:20:50 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [12.107.172.81]) by mx.z120.zixworks.com (Proprietary) with SMTP id D5754C159C; Thu, 30 Mar 2017 15:20:49 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3EA0AFE04E; Thu, 30 Mar 2017 16:21:01 -0400 (EDT)
Received: from imsva2.bcbsm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E7E68FE048; Thu, 30 Mar 2017 16:21:00 -0400 (EDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (unknown [216.32.181.17]) by imsva2.bcbsm.com (Postfix) with ESMTPS; Thu, 30 Mar 2017 16:21:00 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bcbsm.onmicrosoft.com;  s=selector1-bcbsm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=I6jTIIHr3/EjAkGyxJgsVVYE2Jp5WlnW+HRXyutfXWk=; b=xJFlWiBxIWpngerfOJgLdzuHLBFaubahDb1qHpNLP6RqAmwOpUj2vqJh4vT//7E9qUmexumBTceaf8xOvevg2dvrVD1cszy2DWkp13RoxiLV9+csTi34B8ISegO+BwdKbdBEA7qa1GG/ZnEkNWJWxoQ898HJDLOz1WlRrXCk/Q4=
Received: from CY4PR14MB1368.namprd14.prod.outlook.com (10.172.158.148) by CY4PR14MB1368.namprd14.prod.outlook.com (10.172.158.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1005.10; Thu, 30 Mar 2017 20:20:46 +0000
Received: from CY4PR14MB1368.namprd14.prod.outlook.com ([10.172.158.148]) by CY4PR14MB1368.namprd14.prod.outlook.com ([10.172.158.148]) with mapi id 15.01.1005.010; Thu, 30 Mar 2017 20:20:46 +0000
From: "Ackermann, Michael" <MAckermann@bcbsm.com>
To: Tim Chown <Tim.Chown@jisc.ac.uk>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
CC: IETF Discussion <ietf@ietf.org>
Subject: RE: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv71giYAPcbUKK9ywM4gSjvqGssVmAgAC6+QCAAAergIAAIVqAgAAFggCAAASRAIAAEj+AgAAYQACAABLvAIAADMoQ
Date: Thu, 30 Mar 2017 20:20:46 +0000
Message-ID: <CY4PR14MB1368A609AEECA1DC2CE660E3D7340@CY4PR14MB1368.namprd14.prod.outlook.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <CAJE_bqfBt_uytbgQ+=zO4ed9jnc9p=FgPuLH-efgdjFKa+C4jQ@mail.gmail.com> <5E233A42-42C7-4D16-A755-7E0314BFB2D4@jisc.ac.uk>
In-Reply-To: <5E233A42-42C7-4D16-A755-7E0314BFB2D4@jisc.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: jisc.ac.uk; dkim=none (message not signed) header.d=none;jisc.ac.uk; dmarc=none action=none header.from=bcbsm.com;
x-originating-ip: [2001:67c:370:128:e93e:cd10:473c:bf2a]
x-microsoft-exchange-diagnostics: 1; CY4PR14MB1368; 7:eAvYwE0UesJpsAP1J8gLmGM59NT1giPSB44m8sHEZ1A6cI9HHdWowwgK3a5IckEsO0OdKeElF1CrmFly5Dqwu3uMBk1JLBU6fLJgxf+9SHgFyWKHnAILMqOLG/rQ5SedxT2t43xiLN90AWos3E0Q/Swhg+kmwL+uLeYWhoZ1KvDOCpko9JEcgCVAdXKSj96g7lE9hvTpLWeztiQO1i2b3H4/1CE1OIu5nGxj8yItN/XSeaF7w6c1gca5tnWzRRC8rqwxZQivTuj5/jFd2BkLkFLVRgoxduvPnusZGoohSFKpQdHMyne4WPPjDf3jKYb1YjhowHJk8P8TXwcmBYs0KA==; 20:HNOX2AS7TqGrsaBHMK3L2piTmqvVCqT0iSUrrJ/nxD35VW2pGZtNVFD5waJB57hQmF4daPJQUJvG2WqfcG3Bo9EmI12CokAnF7Be+Z3XYkbj5qT2wUEov15Fyqbpt6EgFddDAroQf6vDFLYjyLJBJ33eH/VOA3D2ukwrh/+NnzA=
x-ms-office365-filtering-correlation-id: ab0d56ad-78f4-46b5-475d-08d477aa3ffb
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:CY4PR14MB1368; 
x-microsoft-antispam-prvs: <CY4PR14MB136844E44607C58A6F2BA170D7340@CY4PR14MB1368.namprd14.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041248)(201703131423075)(201702281528075)(201703061421075)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148); SRVR:CY4PR14MB1368; BCL:0; PCL:0; RULEID:; SRVR:CY4PR14MB1368; 
x-forefront-prvs: 02622CEF0A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39400400002)(39450400003)(39830400002)(377454003)(13464003)(24454002)(53546009)(8676002)(86362001)(81166006)(3660700001)(7736002)(8936002)(7696004)(2900100001)(305945005)(230783001)(74316002)(561944003)(33656002)(80792005)(5660300001)(189998001)(2950100002)(122556002)(25786009)(38730400002)(229853002)(2501003)(9686003)(53936002)(76176999)(55016002)(6306002)(50986999)(54356999)(99286003)(6246003)(2906002)(6506006)(3280700002)(4326008)(6116002)(6436002)(77096006)(102836003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR14MB1368; H:CY4PR14MB1368.namprd14.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: bcbsm.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2017 20:20:46.4808 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6f56d3fa-5682-4261-b169-bc0d615da17c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR14MB1368
X-TM-AS-GCONF: 00
X-VPM-HOST: vmvpm02.z120.zixworks.com
X-VPM-GROUP-ID: 9d8f07ce-4bd3-4f04-88ad-b71316e0d211
X-VPM-MSG-ID: 3d169a4b-c657-4ef5-ad0b-c0585ffa39e7
X-VPM-ENC-REGIME: Plaintext
X-VPM-IS-HYBRID: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BjZjpcPGv6sTPbwVT2niWubtWyg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 20:20:56 -0000

R3JlYXQgdGhvdWdodHMvaW5mbyBhbmQgdGhleSBhbGwgbWFrZSBzZW5zZSBmcm9tIGFuIElF
VEYgcGVyc3BlY3RpdmUuIA0KRnJvbSBhbiBlbnRlcnByaXNlIHBlcnNwZWN0aXZlLCBpdCBp
cyB1bmxpa2VseSB0aGF0IGFueW9uZSBpbiB0aGF0IHdvcmxkIGtub3dzIHdoYXQgbW92aW5n
IHRvIElTIG1lYW5zIG9yIGltcGxpZXMuICAgDQpTbyB0aGUgcHJvYmxlbSB0aGF0IEkgaGF2
ZSBpbiB0cnlpbmcgdG8gZ2V0IG15IGVudGVycHJpc2UsIG9yIHRoZSBtYW55IHdlIGhhdmUg
ZGlyZWN0IChvciBldmVuIGluZGlyZWN0KSBjb25uZWN0aW9ucyB3aXRoLCB0byBldmVuIFRI
SU5LIGFib3V0IElQdjYsIGlzIGNvbWluZyB1cCB3aXRoIHJlYXNvbnMgdG8gZG8gc28uICAg
VGhlcmUgYXJlIGEgY291cGxlIG9mIHJlYXNvbnMvZmVhdHVyZXMgdGhhdCBJIGhhdmUgaG9w
ZSBjb3VsZCBiZSBjb21wZWxsaW5nLiAgQnV0IGlmIHRob3NlIGZlYXR1cmVzIGRlcGVuZCBv
biBFSHMsIG9yIGFueXRoaW5nIHVuc3VwcG9ydGVkLCBmdXR1cmUgb3IgIkV4Y2VwdGlvbmFs
IiwgIHRoZXkgd2lsbCBub3QgYmUgY29tcGVsbGluZyBhdCBhbGwuICANCk15IHdvcmxkIGlz
IGEgdG91Z2ggc2VsbC4gICBJIGp1c3QgZG8gbm90IHdhbnQgaXQgdG8gZ2V0IGFueSB0b3Vn
aGVyLiAgDQpUaGFua3MNCk1pa2UNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
RnJvbTogaXB2NiBbbWFpbHRvOmlwdjYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9m
IFRpbSBDaG93bg0KU2VudDogVGh1cnNkYXksIE1hcmNoIDMwLCAyMDE3IDM6MjcgUE0NClRv
OiA2bWFuIFdHIDxpcHY2QGlldGYub3JnPjsgZHJhZnQtaWV0Zi02bWFuLXJmYzI0NjBiaXMu
YWxsQGlldGYub3JnDQpDYzogSUVURiBEaXNjdXNzaW9uIDxpZXRmQGlldGYub3JnPg0KU3Vi
amVjdDogUmU6IElFVEYgTGFzdCBDYWxsIGNvbmNsdXNpb24gZm9yIGRyYWZ0LWlldGYtNm1h
bi1yZmMyNDYwYmlzLTA4DQoNCkhpLA0KDQo+IE9uIDMwIE1hciAyMDE3LCBhdCAxOToxOSwg
56We5piO6YGU5ZOJIDxqaW5tZWlAd2lkZS5hZC5qcD4gd3JvdGU6DQo+IA0KPiBBdCBUaHUs
IDMwIE1hciAyMDE3IDExOjUyOjQxIC0wNTAwLA0KPiBSb2JlcnQgUmFzenVrIDxyb2JlcnRA
cmFzenVrLm5ldD4gd3JvdGU6DQo+IA0KPj4gT2sgc28gdGlsbCBhIG5ldyBkb2N1bWVudCB1
cGRhdGVzIDI0NjBiaXMgYW55IGZ1cnRoZXIgd29yayBvbiBFSHMgaXMgDQo+PiBmcm96ZW4g
YXMgaXQgd291bGQgcmVmZXJlbmNlIDI0NjBiaXMgd2l0aCBuZXcgdGV4dC4gVGhhdCB3YXMg
bXkgbWFpbiBwb2ludC4NCj4gDQo+IEkgZG9uJ3QgZ2V0IHRoZSBsb2dpYy4uLmFuICJ1cGRh
dGUiIGNhbiBzdGFydCBpbW1lZGlhdGVseSBvbmNlIHN1Y2ggYSANCj4gZHJhZnQgbmV3IHBy
b3Bvc2FsIGlzIGF2YWlsYWJsZS4gIFRoZSB1cGRhdGUgd29uJ3QgYmUgZm9ybWFsbHkgDQo+
IGNvbXBsZXRlZCB1bnRpbCBpdCBnZXRzIHNvbWUgZm9ybWFsIHN0YXRlIGxpa2UgYSBzdGFu
ZGFyZCB0cmFjayBSRkMsIA0KPiBhbmQgaXQgd2lsbCB0YWtlIHRpbWUsIGJ1dCB0aGF0IHdv
dWxkbid0IG5lY2Vzc2FyaWx5IG1lYW4gYSBmdXJ0aGVyIA0KPiB3b3JrIGlzICJmcm96ZW4i
OyBpdCdzIG5vdCB2ZXJ5IGNsZWFyIHRvIG1lIHdoYXQgdGhpcyB0ZXJtIG1lYW5zIGluIA0K
PiB0aGlzIGNvbnRleHQsIGJ1dCBpdCdzIHF1aXRlIGNvbW1vbiBkZXZlbG9wbWVudCB0YWtl
cyBwbGFjZSB3aGlsZSB0aGUgDQo+IHNwZWMgaXMgYmVpbmcgZGlzY3Vzc2VkIGFzIGEgZHJh
ZnQsIGFuZCBpdCdzIGFsc28gbm90IHVuY29tbW9uIHNvbWUgDQo+IGNvbW1lcmNpYWwgb3Bl
cmF0b3JzIGV2ZW4gc3RhcnQgZGVwbG95aW5nIGl0LiAgT24gdGhlIG90aGVyIGhhbmQsIGV2
ZW4gDQo+IGlmIHdlIG5vdyBhZ3JlZWQgdGhhdCByZmMyNDYwYmlzIHNob3VsZCBleHBsaWNp
dGx5IGFsbG93IHN1Y2ggImZ1cnRoZXIgDQo+IHdvcmsiLCB0aGUgZGlzY3Vzc2lvbiBpdHNl
bGYgd291bGQgdGFrZSBsb25nIGFuZCB3b3VsZG4ndCBiZSBjb21wbGV0ZWQgDQo+IHNvb24u
DQo+IA0KPiBCdXQgSU1PIGl0J3MgaXJyZXNwb25zaWJsZSB0byBsZWF2ZSB0aGUgdGV4dCBh
bWJpZ3VvdXMgYW5kIGxldCBzb21lIA0KPiBvdGhlciBwZW9wbGUgbWlzdW5kZXJzdGFuZCBp
dCwgcG9zc2libHkgZXZlbiBtb3JlIGNhc3VhbGx5IGFuZC9vciBpbiANCj4gdGhlIGdsb2Jh
bCBJbnRlcm5ldCwgZm9yIHRoZSBjb21mb3J0IG9mIHNvbWUgcGFydGljdWxhciBmdXR1cmUg
d29yay4NCj4gSSB0aGluayB3ZSdyZSBub3cgdHJ5aW5nIHRvIGhlbHAgYXZvaWQgdGhlIGxh
dGVzdCBjbGFyaWZpY2F0aW9uIGluIA0KPiByZmMyNDYwYmlzIHRvIGJlIGludGVycHJldGVk
IGFzIGFuICJvdXRyaWdodCBiYW4iIG9mIGZ1dHVyZSB1cGRhdGVzIA0KPiB3aGlsZSBzdGls
bCB0cnlpbmcgdG8gYmUgcmVzcG9uc2libGUgZm9yIHRoZSBzb3VuZG5lc3Mgb2YgdGhlIGds
b2JhbCANCj4gSW50ZXJuZXQuICBJbiBteSB1bmRlcnN0YW5kaW5nIEJyaWFuJ3MgYWRkaXRp
b25hbCB0ZXh0IGlzIG9uZSBzdWNoIA0KPiBhdHRlbXB0IChJIGFsc28gcHJvcG9zZWQgdGV4
dCBpbiB0aGF0IHNlbnNlIGF0IHRoZSB0aW1lIG9mIFdHTEMsIA0KPiBhbHRob3VnaCBpdCB3
YXNuJ3QgYWRvcHRlZCBpbiB0aGUgZW5kKS4gIElmIHRoYXQgdGV4dCBpcyBzdGlsbCBub3Qg
DQo+IGVub3VnaCB3ZSBjYW4gZGlzY3VzcyBob3cgdG8gcGhyYXNlIGl0LiAgQW5kLCB3aGls
ZSBJIHN1c3BlY3QgcGVvcGxlIA0KPiB3aG8gd2FudGVkIHRvIGtlZXAgdGhlIGFtYmlndWl0
eSB3aWxsIG5ldmVyIGJlIHNhdGlzZmllZCB3aXRoIHRoZSANCj4gcmVzdWx0IGFzIGxvbmcg
YXMgdGhlIGFkZGVkIGNsYXJpZmljYXRpb24gcmVtYWlucywgSSBiZWxpZXZlIHRoYXQncyBh
IA0KPiByZWFzb25hYmxlIGNvbXByb21pc2UgdG8gYWNoaWV2ZSBhIGJhbGFuY2UgYmV0d2Vl
biBiZWluZyByZXNwb25zaWJsZSANCj4gYW5kIG5vdCAodW5pbnRlbnRpb25hbGx5KSBkaXNj
b3VyYWdpbmcgZnV0dXJlIHVwZGF0ZXMuDQoNClJlcGVhdGluZyB3aGF0IEkgc2FpZCBhdCB0
aGUgbWljLCBteSB2aWV3cyBlY2hvIHRob3NlIG9mIEppbm1laSwgTWljaGFlbCwgTG9yZW56
byBhbmQgQnJpYW4uIEkgYWdyZWUgd2l0aCB0aGUgZGVjaXNpb24gdG8gcHJvZ3Jlc3MgUkZD
MjQ2MC1iaXMgdG8gSVMgaW5jbHVkaW5nIFN1cmVzaOKAmXMgdGV4dC4gSeKAmWQgYWxzbyBs
aWtlIHRvIHNlZSBCcmlhbuKAmXMgc2hvcnQgYW1lbmRtZW50IGluY2x1ZGVkLCB3aGljaCBt
YWtlcyBleHBsaWNpdCBJbnRlcm5ldCBzY29wZSBhcyB0aGUgZGVmYXVsdCB0YXJnZXQuDQoN
CkFkdmFuY2luZyAyNDYwYmlzIGRvZXNu4oCZdCBmcmVlemUgd29yayBvbiBTUjsgdGhhdCB3
b3JrIGNhbiBjb250aW51ZSB0b2RheS4gSSBkb27igJl0IHNlZSB0aGUgbmV3IFNSIGhlYWRl
ciBpbnNlcnRpb24gZHJhZnQgY29tcGxldGluZyBpbiDigJxhIGNvdXBsZSBvZiB3ZWVrc+KA
nTsgaXTigJlzIG11Y2ggbW9yZSBsaWtlbHkgdG8gdGFrZSBzZXZlcmFsIG1vbnRocyBvciBl
dmVuIGEgeWVhciB0byBwcm9ncmVzcyB0aHJvdWdoIFdHIGFkb3B0aW9uIGFuZCBldmVudHVh
bCBwdWJsaWNhdGlvbiwgdG8gZW5zdXJlIGdvb2QgYW5kIHJvYnVzdCBpbnB1dC4gRm9yIGFk
b3B0aW9uLCBJ4oCZZCBleHBlY3QgbWFueSBwZW9wbGUgdG8gd2FudCB0aGUgZHJhZnQgdG8g
aW5jbHVkZSB0ZXh0IG9uIGEpIHdoeSB2YW5pbGxhIGVuY2Fwc3VsYXRpb24gaXMgbm90IHN1
ZmZpY2llbnQgYW5kIGIpIGhvdyB0aGUgaW5zZXJ0aW9uIGNhbiBndWFyYW50ZWVkIHRvIGJl
IGRvbmUgc2FmZWx5IGZvciBzcGVjaWZpYyBzY2VuYXJpbyhzKS4gQnV0IHRoYXTigJlzIGFs
bCB2ZXJ5IHBvc3NpYmxlLg0KDQpBbmQgcGxlYXNlIGRvIG5vdGUgdGhhdCBwdWJsaXNoaW5n
IDI0NjAtYmlzIGFzIGFuIEludGVybmV0IFN0YW5kYXJkIGRvZXMgbm90IHNldCBpdCBpbiBz
dG9uZS4gWW91ciBTUiB3b3JrIGNhbiB1cGRhdGUgaXQsIGFzIGNvdWxkIG90aGVyIGZ1dHVy
ZSBSRkMocykgb24gb3RoZXIgbmV3IG1lY2hhbmlzbShzKSBvciBpbm5vdmF0aW9uKHMpIHRo
YXQgaGF2ZSB5ZXQgdG8gYmUgcHJvcG9zZWQuIEnigJlkIGFyZ3VlIHRoYXQgaXTigJlzIHBy
ZXR0eSBsaWtlbHkgd2XigJlsbCBzZWUgb3RoZXIgUkZDcyB1cGRhdGUgMjQ2MC1iaXM7IHRo
YXQgc2hvdWxkbuKAmXQgYmUgYSBzdXJwcmlzZSBpZiBpdOKAmXMgYSBwcm90b2NvbCB0aGF0
IHdl4oCZbGwgYmUgdXNpbmcgZm9yIHRoZSBuZXh0IDIwLTMwIHllYXJzIG9yIG1vcmUuIEZv
ciBlYWNoLCB3ZeKAmWxsIGp1c3Qgc2VlIOKAnFVwZGF0ZWQgYnk64oCdIHRhZ3MgaW4gdGhl
IFJGQyBoZWFkZXIuIFRoZSBjdXJyZW50IFJGQzI0NjAgaGFzIGFjY3VtdWxhdGVkIG5pbmUg
c3VjaCB0YWdzIGluIDE5IHllYXJzLCBzbyBhYm91dCBvbmUgZXZlcnkgdHdvIHllYXJzLg0K
DQpPbiBlbnRlcnByaXNlIGRlcGxveW1lbnQgSeKAmWQgYXJndWUgdGhhdCwgaWYgYW55dGhp
bmcsIG1vdmluZyB0byBJUyBzaG91bGQgaGVscCBzdHJlbmd0aGVuIHRoZSBjYXNlIGZvciBk
ZXBsb3ltZW50LCBiZWNhdXNlIGl0IGNvbmZpcm1zIHByb3ZlbiB3aWRlc2NhbGUgZGVwbG95
bWVudC4gIFRoZSBmb3VyIGNyaXRlcmlhIGZvciBtb3ZpbmcgdG8gSVMgYXJlIGRlc2NyaWJl
ZCBpbiBTZWN0aW9uIDIuMiBvZiBSRkM2NDEwLCBidXQgYXJlIHN1bW1hcmlzZWQgYXMgImEg
aGlnaCBkZWdyZWUgb2YgdGVjaG5pY2FsIG1hdHVyaXR5IGFuZCBieSBhIGdlbmVyYWxseSBo
ZWxkIGJlbGllZiB0aGF0IHRoZSBzcGVjaWZpZWQgcHJvdG9jb2wgb3Igc2VydmljZSBwcm92
aWRlcyBzaWduaWZpY2FudCBiZW5lZml0IHRvIHRoZSBJbnRlcm5ldCBjb21tdW5pdHnigJ0u
IEnigJlkIGhvcGUgd2UgaGF2ZSB2ZXJ5IHN0cm9uZyBjb25zZW5zdXMgb24gdGhhdCBzdGF0
ZW1lbnQuDQoNClRpbQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCklFVEYgSVB2NiB3b3JraW5nIGdyb3Vw
IG1haWxpbmcgbGlzdA0KaXB2NkBpZXRmLm9yZw0KQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXB2Ng0KLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0NCgoKVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIGNvbW11bmljYXRp
b24gaXMgaGlnaGx5IGNvbmZpZGVudGlhbCBhbmQgaXMgaW50ZW5kZWQgc29sZWx5IGZvciB0
aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsKHMpIHRvIHdob20gdGhpcyBjb21tdW5pY2F0aW9u
IGlzIGRpcmVjdGVkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5
b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSB2aWV3aW5nLCBjb3B5aW5nLCBkaXNj
bG9zdXJlIG9yIGRpc3RyaWJ1dGlvbiBvZiB0aGlzIGluZm9ybWF0aW9uIGlzIHByb2hpYml0
ZWQuIFBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciwgYnkgZWxlY3Ryb25pYyBtYWlsIG9yIHRl
bGVwaG9uZSwgb2YgYW55IHVuaW50ZW5kZWQgcmVjZWlwdCBhbmQgZGVsZXRlIHRoZSBvcmln
aW5hbCBtZXNzYWdlIHdpdGhvdXQgbWFraW5nIGFueSBjb3BpZXMuCiAKIEJsdWUgQ3Jvc3Mg
Qmx1ZSBTaGllbGQgb2YgTWljaGlnYW4gYW5kIEJsdWUgQ2FyZSBOZXR3b3JrIG9mIE1pY2hp
Z2FuIGFyZSBub25wcm9maXQgY29ycG9yYXRpb25zIGFuZCBpbmRlcGVuZGVudCBsaWNlbnNl
ZXMgb2YgdGhlIEJsdWUgQ3Jvc3MgYW5kIEJsdWUgU2hpZWxkIEFzc29jaWF0aW9uLgo=


From nobody Thu Mar 30 13:24:55 2017
Return-Path: <markzzzsmith@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 335F3126B72; Thu, 30 Mar 2017 13:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R9zm9G5niDAr; Thu, 30 Mar 2017 13:24:50 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE20812943B; Thu, 30 Mar 2017 13:24:47 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id s68so68800442vke.3; Thu, 30 Mar 2017 13:24:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=9UCmQ5KLq8wk+DPwCIEXLbXkwUyMyI/eyt2KZvPu1Zk=; b=UHQ0Yt57+zbj0RYo3gWnYNGd9zw0cY3hYHYWIoQqrqsMU0AYb+R0IzszdPeLHwYRzD ruHpSIO/vGC2c3+fAXsz3L0+peN8c8MOKRshmSQcvwvRGoHHyt1YulMM7Jt6xVQC7ddl bJjzzFcUsod3v0AxhS/mlXqY6wCv3tdNvrATOnbUtu9qhpwTP2rNiYDei+AjjdsFQwt7 3nhFLHtFWXAfQaB80mXLTPPqJU6ZdmonoNsTnG1vksTAY+q9CcNs81lm3ULbFbX22wsI xSo3kf7t51rT24xFth42PCzIgaD2U50xrbY37MdD8zR9MwxLc5NI9tr3b+Q7Gw9wbw01 lUag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=9UCmQ5KLq8wk+DPwCIEXLbXkwUyMyI/eyt2KZvPu1Zk=; b=cHdqXJXGgk+cN6S/UcTz53mMvzJMjVmXWxa8FQjirALUGLMdm8m4Bfue9TsXwfDk3B yjC6Ad+5CTdMo0aV5LfVFBk7r6EwoDbDvpCwJx2g8X+fVTAsoXgSVAuqrnjyViO8x5J/ z0Li6c/L+5LmPOTI9xwFNC04HKikxV8AfaJr+nvFAt7jHiUWSjzRfZodEiZo6+izHJv3 /U2SYnd3wljbNB+CwLYmEMftWO7C7i6Vt4LuZBBi9VzTFbKDrzWOlDs/TlNiI89u0o5/ mNmdyc+viHY1BAKCMzg7t/IIEqvGHuA8MVZLnBBxIVZZCOW5guOomRi4hNmmqtfCyK8L DDHg==
X-Gm-Message-State: AFeK/H1w0DYSp1YCyKqdxrU4SvE/IDhTivNNt9a8ZSQ3X6rBOjfrKQt/WuoUIWjjJCdOcy0eMrsIwj6h9IkJdQ==
X-Received: by 10.176.64.34 with SMTP id h31mr910460uad.89.1490905486642; Thu, 30 Mar 2017 13:24:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.36.181 with HTTP; Thu, 30 Mar 2017 13:24:16 -0700 (PDT)
In-Reply-To: <CY4PR14MB1368118932BAB02AE83C781FD7340@CY4PR14MB1368.namprd14.prod.outlook.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <CC4FF04D-0712-4304-BD5F-3D9F57E533A3@ericsson.com> <CY4PR14MB1368118932BAB02AE83C781FD7340@CY4PR14MB1368.namprd14.prod.outlook.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 31 Mar 2017 07:24:16 +1100
Message-ID: <CAO42Z2x-wVez3A36dDSEVLWN1z5YXkLjb5Vx7b9KJzv7KTVcZg@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: "Ackermann, Michael" <MAckermann@bcbsm.com>
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>, "Leddy, John" <John_Leddy@comcast.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, 6man WG <ipv6@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6GC0s-ONdhZvRjJEKYXS-490okA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 20:24:53 -0000

The thing to keep in mind is that enterprises use technology to solve
business problems. Technology is a means to an end, not the end
itself.

For general Internet or internal networking problems, IPv6 doesn't
solve the problem any better than IPv4 does. That is why Enterprises
haven't adopted it for their Internet or general internal networks.
Adding IPv6 is actually worse - it just increases their capex and opex
for no business benefit.

I've heard SR recently called the next MPLS. So how many Enterprises
have adopted MPLS?

When Enterprises need to access IPv6 Internet services, they'll just
IPv6 enable their boundary Internet access security devices and mail
servers.

IPv6 will be used by Enterprises when it either provides a compelling
advantage over IPv4, or where a vendor's "turn key" solution uses it.
I've seen that recently with AMI smartmeter mesh networks.

Here in Victoria, AU, there are probably in the order of 1M+ IPv6 AMI
smart meters across multiple electricity distributors. They're using
IPv6 for that because that is what the vendor's end-to-end AMI
solution uses. They use IPv4 to access the OSS and servers that are
used to troubleshoot that network, and there is no real benefit for
the organisation to deploy IPv6 on their internal LANs to access those
servers.

Inventing a new IPv6 feature just to try to encourage adoption isn't
going to be that successful. The new feature has to be a compelling
solution to a problem that the enterprise has, that justifies the
additional and typically very large expense of deploying IPv6 to get
it.

Regards,
Mark.



On 31 March 2017 at 03:54, Ackermann, Michael <MAckermann@bcbsm.com> wrote:
> This is something I tried to say at the mic today, but I was too late.
> If we put potentially valuable use cases into the bucket of "Exceptions",=
  this becomes yet another excuse to delay or avoid adoption of IPv6 by the=
 very large percentage of Enterprises who have yet to do so (and have no se=
rious plans) today.
>
> I am hopeful that work in the IETF will provide features and hence motiva=
tion for us sadly delinquent Enterprises to begin actually using IPv6.    I=
 am concerned that perception of solutions being "Exceptions" or non standa=
rd, will cause consternation (warranted or not) and avoidance.
>
>
> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Suresh Krishnan
> Sent: Thursday, March 30, 2017 9:30 AM
> To: Leddy, John <John_Leddy@comcast.com>
> Cc: draft-ietf-6man-rfc2460bis.all@ietf.org; 6man WG <ipv6@ietf.org>; iet=
f@ietf.org
> Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
>
> Hi John,
>   Thanks for chiming in. I recognize that you might have use cases that m=
ight be better off with header insertion but I think they should be handled=
 as and when they come up for consideration (e.g. in the SRv6 discussions).=
 Holding up this document is not going to help in any way in reinterpreting=
 what RFC2460 intended. My suggestion for proponents of safe header inserti=
on to write up how it is expected to work and have the discussion then.
>
> Thanks
> Suresh
>
>> On Mar 29, 2017, at 9:59 PM, Leddy, John <John_Leddy@comcast.com> wrote:
>>
>>> On Mar 14, 2017, at 9:47 PM, Suresh Krishnan <suresh.krishnan@ericsson.=
com> wrote:
>>>
>>> NEW:
>>>
>>> With one exception, extension headers are not examined, processed,
>>> inserted, or deleted by any node along a packet's delivery path,
>>> until the packet reaches the node (or each of the set of nodes, in
>>> the case of multicast) identified in the Destination Address field of
>>> the IPv6 header...
>>>
>>> Please feel free to comment either privately or on list if you have any=
 concerns with this resolution going forward.
>>
>>
>> Suresh,
>>
>> I still have concerns that we are eliminating a tool that may prove very=
 helpful in migrations without understanding its value.
>>
>> The Internet transition of IPV4 -> Dual Stack V4/V6 -> IPV6 Only; has be=
en long, operationally complex and full of unexpected challenges.
>> We are only now starting to make the transition from Dual Stack to IPV6 =
Only, there are still many unknowns on how to complete this migration.
>>
>> As we contemplate finishing this major Network shift =E2=80=93 We find o=
urselves in the early stages of another.
>>
>> The transition from Physical to Virtual Infrastructure.  Again, the migr=
ation will be long, operationally complex and full of unexpected challenges=
.
>>
>> In the old world with Servers running Applications in Physical locations=
 designed for very predictable loads; using an encap/decap tunnel to emulat=
e a physical circuit between locations has many attractive properties =E2=
=80=93 but that is compared to actually ordering and provisioning real circ=
uits between locations.
>>
>> In the new world of dynamic resources spun up on demand in distributed e=
nvironments across multiple providers, Applications having the Intelligence=
 and State to bring up their own required connectivity is very natural.  Th=
is is where we are putting the majority of our efforts.  SRv6 enables very =
attractive solutions by Applications building their own headers.
>>
>> The challenges come as we try to migrate and require these two infrastru=
ctures to Interoperate for a long time.
>> Burdening the new Virtual world with Old, Static circuit paradigms is no=
t optimal.
>> Supplementing the legacy infrastructure with an assist function seems
>> a reasonable solution.  (Ext Hdr insertion/deletion or encap/decap
>> tunnels)
>>
>> The preferred assist mechanism seems to be the one that allows the New
>> World to operate in its final preferred state, sending and receiving pac=
kets with their own headers. (SRv6) But what does an Application in the new=
 world due when it is attempting to communicate with an Application in the =
Old World?
>> Shouldn=E2=80=99t it build an SRv6 header?  That would mean that the ass=
ist function would need to be the last SID in the Segment List and be capab=
le of removing the SRH.
>> Wouldn=E2=80=99t it make sense for the assist function to do the same th=
ing in the reverse direction; an Old World Server talking to a New Virtual =
World Application?  Insert an SRH.
>>
>> If this insert/delete of an SRH is prematurely prohibited;  What is a re=
commended solution to the Real World problem above.  Not use case, we are i=
mplementing.
>>
>> Again; I=E2=80=99m worried we are eliminating a tool that may prove very
>> helpful, preclude its use in future IETF work and shutdown a path for
>> Innovation in Networking,
>>
>> Thank you for asking and listening to my concerns,
>>
>> John Leddy
>> Comcast
>>
>>
>>
>>
>>
>>
>
>
>
> The information contained in this communication is highly confidential an=
d is intended solely for the use of the individual(s) to whom this communic=
ation is directed. If you are not the intended recipient, you are hereby no=
tified that any viewing, copying, disclosure or distribution of this inform=
ation is prohibited. Please notify the sender, by electronic mail or teleph=
one, of any unintended receipt and delete the original message without maki=
ng any copies.
>
>  Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are=
 nonprofit corporations and independent licensees of the Blue Cross and Blu=
e Shield Association.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Thu Mar 30 13:45:15 2017
Return-Path: <rraszuk@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 F2B81129470; Thu, 30 Mar 2017 13:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mw7lgibD3uFj; Thu, 30 Mar 2017 13:45:01 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B20201293D9; Thu, 30 Mar 2017 13:45:01 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id y18so1469693itc.1; Thu, 30 Mar 2017 13:45:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=pRGosb/buy6mVCYdGDfkT8YZSNflXKzHXljqtkvG2H8=; b=b5kT1pKZ3pXOFU88nnYOOJi+pSoYs8i34UaSy4TbP4uCOdYnImotJPP+B4bTVGEWXX 4Df4vv19iMCZcBGeV8JQlp9I+oTFAnXUhSYu81a6f0iYTpX6+O9eKuiG1KCuqs4sGOC8 IV5VQjesvKaK7SBydK5Ec9yUE7ZVz1b8JmGxDmiCWV7qYlmy6ImN8XAAbWsZlzpC0YIJ JWEHv1QRGYkUXTxUl9eqbk6INRnM5ZUqA/4MAWVSnI+oN67Ddmy/lizG+gWSImvGUuBm cv4afvZ5UmqlC0r9wkZajHT7+hI7JE7F8HL0Fr+fRQKykRC6DmGL39UY+kS7yd1Rc5vS 2MDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=pRGosb/buy6mVCYdGDfkT8YZSNflXKzHXljqtkvG2H8=; b=sG3KMp0O5+48xt0QWaqfy0vCZe49NBcidgkwkVeuCRT2BJvA5xyzFwymo3XUUhXkul Z9fOLAI4q1QcqE4yBw6UygYtEtMDhRGJiIb5eGVz137PCk/ryJzvNKmdTfohPWn3t4+s sLSM5jAIyTPPZIskGx0tdHL2aipMp0l9kADpLZYKfFJJqQ6fBrePPWwJrz5At383fGSu l80PjkrXp5yItxQtYIDxjuLG8e/hpy4rYf60cXQIlNtw25vIZFCIynhHg8aDLmnUmOed tF+L0GwOvNWWYqWAdCtydbqghRCJdPaT/NJ0uZNR9iHRV1H6EIdixiLCnR1+xkAtjdmS od4w==
X-Gm-Message-State: AFeK/H1vFgvXyqB8ETRUL6TRykiKPRuV3ufDCm0LFMwetnhghEwbCsiuoCIxwNO+zi96ovYo7E75tCu6wd7CZg==
X-Received: by 10.36.85.194 with SMTP id e185mr166821itb.39.1490906701028; Thu, 30 Mar 2017 13:45:01 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 13:44:59 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 13:44:59 -0700 (PDT)
In-Reply-To: <CAO42Z2x-wVez3A36dDSEVLWN1z5YXkLjb5Vx7b9KJzv7KTVcZg@mail.gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <CC4FF04D-0712-4304-BD5F-3D9F57E533A3@ericsson.com> <CY4PR14MB1368118932BAB02AE83C781FD7340@CY4PR14MB1368.namprd14.prod.outlook.com> <CAO42Z2x-wVez3A36dDSEVLWN1z5YXkLjb5Vx7b9KJzv7KTVcZg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 30 Mar 2017 15:44:59 -0500
X-Google-Sender-Auth: mKCh2bGIY2_AGox3ahNqnu4X-z0
Message-ID: <CA+b+ERn372ixLhuS0Z_qSm=RxHxfqzUyAuDN5bg5ndzykxJAEQ@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Mark Smith <markzzzsmith@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>, "Leddy, John" <John_Leddy@comcast.com>,  "Ackermann, Michael" <MAckermann@bcbsm.com>, 6man WG <ipv6@ietf.org>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a1143d1484f0c27054bf8c466
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-B8yXih1vW07G3Wp7f0LDsdg2Y8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 20:45:07 -0000

--001a1143d1484f0c27054bf8c466
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Mark,

And this is precisely what we are saying.

Enterprise I work for has global L3VPN network with MPLS, LDP, 3107 across
3 ASes spanning the globe. Obviously with that you also need various
InterAS options.

On top of that there is some limited need for inter-as TE so you employ
static EROs and RSVP-TE.

We have need to do efficient p2mp data distribution in WAN which again
requires another set of different protocols.

Imagine opex with all of the above.

And at this time SRv6 delivers all of the above applications with huge
reduction of need of various protocols mentioned above.

That was the point.

Cheers,
R.





On Mar 30, 2017 15:24, "Mark Smith" <markzzzsmith@gmail.com> wrote:

> The thing to keep in mind is that enterprises use technology to solve
> business problems. Technology is a means to an end, not the end
> itself.
>
> For general Internet or internal networking problems, IPv6 doesn't
> solve the problem any better than IPv4 does. That is why Enterprises
> haven't adopted it for their Internet or general internal networks.
> Adding IPv6 is actually worse - it just increases their capex and opex
> for no business benefit.
>
> I've heard SR recently called the next MPLS. So how many Enterprises
> have adopted MPLS?
>
> When Enterprises need to access IPv6 Internet services, they'll just
> IPv6 enable their boundary Internet access security devices and mail
> servers.
>
> IPv6 will be used by Enterprises when it either provides a compelling
> advantage over IPv4, or where a vendor's "turn key" solution uses it.
> I've seen that recently with AMI smartmeter mesh networks.
>
> Here in Victoria, AU, there are probably in the order of 1M+ IPv6 AMI
> smart meters across multiple electricity distributors. They're using
> IPv6 for that because that is what the vendor's end-to-end AMI
> solution uses. They use IPv4 to access the OSS and servers that are
> used to troubleshoot that network, and there is no real benefit for
> the organisation to deploy IPv6 on their internal LANs to access those
> servers.
>
> Inventing a new IPv6 feature just to try to encourage adoption isn't
> going to be that successful. The new feature has to be a compelling
> solution to a problem that the enterprise has, that justifies the
> additional and typically very large expense of deploying IPv6 to get
> it.
>
> Regards,
> Mark.
>
>
>
> On 31 March 2017 at 03:54, Ackermann, Michael <MAckermann@bcbsm.com>
> wrote:
> > This is something I tried to say at the mic today, but I was too late.
> > If we put potentially valuable use cases into the bucket of
> "Exceptions",  this becomes yet another excuse to delay or avoid adoption
> of IPv6 by the very large percentage of Enterprises who have yet to do so
> (and have no serious plans) today.
> >
> > I am hopeful that work in the IETF will provide features and hence
> motivation for us sadly delinquent Enterprises to begin actually using
> IPv6.    I am concerned that perception of solutions being "Exceptions" o=
r
> non standard, will cause consternation (warranted or not) and avoidance.
> >
> >
> > -----Original Message-----
> > From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Suresh Krishnan
> > Sent: Thursday, March 30, 2017 9:30 AM
> > To: Leddy, John <John_Leddy@comcast.com>
> > Cc: draft-ietf-6man-rfc2460bis.all@ietf.org; 6man WG <ipv6@ietf.org>;
> ietf@ietf.org
> > Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-0=
8
> >
> > Hi John,
> >   Thanks for chiming in. I recognize that you might have use cases that
> might be better off with header insertion but I think they should be
> handled as and when they come up for consideration (e.g. in the SRv6
> discussions). Holding up this document is not going to help in any way in
> reinterpreting what RFC2460 intended. My suggestion for proponents of saf=
e
> header insertion to write up how it is expected to work and have the
> discussion then.
> >
> > Thanks
> > Suresh
> >
> >> On Mar 29, 2017, at 9:59 PM, Leddy, John <John_Leddy@comcast.com>
> wrote:
> >>
> >>> On Mar 14, 2017, at 9:47 PM, Suresh Krishnan <
> suresh.krishnan@ericsson.com> wrote:
> >>>
> >>> NEW:
> >>>
> >>> With one exception, extension headers are not examined, processed,
> >>> inserted, or deleted by any node along a packet's delivery path,
> >>> until the packet reaches the node (or each of the set of nodes, in
> >>> the case of multicast) identified in the Destination Address field of
> >>> the IPv6 header...
> >>>
> >>> Please feel free to comment either privately or on list if you have
> any concerns with this resolution going forward.
> >>
> >>
> >> Suresh,
> >>
> >> I still have concerns that we are eliminating a tool that may prove
> very helpful in migrations without understanding its value.
> >>
> >> The Internet transition of IPV4 -> Dual Stack V4/V6 -> IPV6 Only; has
> been long, operationally complex and full of unexpected challenges.
> >> We are only now starting to make the transition from Dual Stack to IPV=
6
> Only, there are still many unknowns on how to complete this migration.
> >>
> >> As we contemplate finishing this major Network shift =E2=80=93 We find
> ourselves in the early stages of another.
> >>
> >> The transition from Physical to Virtual Infrastructure.  Again, the
> migration will be long, operationally complex and full of unexpected
> challenges.
> >>
> >> In the old world with Servers running Applications in Physical
> locations designed for very predictable loads; using an encap/decap tunne=
l
> to emulate a physical circuit between locations has many attractive
> properties =E2=80=93 but that is compared to actually ordering and provis=
ioning
> real circuits between locations.
> >>
> >> In the new world of dynamic resources spun up on demand in distributed
> environments across multiple providers, Applications having the
> Intelligence and State to bring up their own required connectivity is ver=
y
> natural.  This is where we are putting the majority of our efforts.  SRv6
> enables very attractive solutions by Applications building their own
> headers.
> >>
> >> The challenges come as we try to migrate and require these two
> infrastructures to Interoperate for a long time.
> >> Burdening the new Virtual world with Old, Static circuit paradigms is
> not optimal.
> >> Supplementing the legacy infrastructure with an assist function seems
> >> a reasonable solution.  (Ext Hdr insertion/deletion or encap/decap
> >> tunnels)
> >>
> >> The preferred assist mechanism seems to be the one that allows the New
> >> World to operate in its final preferred state, sending and receiving
> packets with their own headers. (SRv6) But what does an Application in th=
e
> new world due when it is attempting to communicate with an Application in
> the Old World?
> >> Shouldn=E2=80=99t it build an SRv6 header?  That would mean that the a=
ssist
> function would need to be the last SID in the Segment List and be capable
> of removing the SRH.
> >> Wouldn=E2=80=99t it make sense for the assist function to do the same =
thing in
> the reverse direction; an Old World Server talking to a New Virtual World
> Application?  Insert an SRH.
> >>
> >> If this insert/delete of an SRH is prematurely prohibited;  What is a
> recommended solution to the Real World problem above.  Not use case, we a=
re
> implementing.
> >>
> >> Again; I=E2=80=99m worried we are eliminating a tool that may prove ve=
ry
> >> helpful, preclude its use in future IETF work and shutdown a path for
> >> Innovation in Networking,
> >>
> >> Thank you for asking and listening to my concerns,
> >>
> >> John Leddy
> >> Comcast
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> > The information contained in this communication is highly confidential
> and is intended solely for the use of the individual(s) to whom this
> communication is directed. If you are not the intended recipient, you are
> hereby notified that any viewing, copying, disclosure or distribution of
> this information is prohibited. Please notify the sender, by electronic
> mail or telephone, of any unintended receipt and delete the original
> message without making any copies.
> >
> >  Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan
> are nonprofit corporations and independent licensees of the Blue Cross an=
d
> Blue Shield Association.
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
>

--001a1143d1484f0c27054bf8c466
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Mark,<div dir=3D"auto"><br></div><div dir=3D"auto">And=
 this is precisely what we are saying.</div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">Enterprise I work for has global L3VPN network with MPLS, LD=
P, 3107 across 3 ASes spanning the globe. Obviously with that you also need=
 various InterAS options.</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">On top of that there is some limited need for inter-as TE so you employ s=
tatic EROs and RSVP-TE.</div><div dir=3D"auto"><br></div><div dir=3D"auto">=
We have need to do efficient p2mp data distribution in WAN which again requ=
ires another set of different protocols.</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">Imagine opex with all of the above.</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">And at this time SRv6 delivers all of the abov=
e applications with huge reduction of need of various protocols mentioned a=
bove.</div><div dir=3D"auto"><br></div><div dir=3D"auto">That was the point=
.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Cheers,</div><div dir=
=3D"auto">R.</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><=
div dir=3D"auto"><br></div><div dir=3D"auto"><br></div></div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Mar 30, 2017 15:24, &quot;Ma=
rk Smith&quot; &lt;<a href=3D"mailto:markzzzsmith@gmail.com">markzzzsmith@g=
mail.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:1=
ex">The thing to keep in mind is that enterprises use technology to solve<b=
r>
business problems. Technology is a means to an end, not the end<br>
itself.<br>
<br>
For general Internet or internal networking problems, IPv6 doesn&#39;t<br>
solve the problem any better than IPv4 does. That is why Enterprises<br>
haven&#39;t adopted it for their Internet or general internal networks.<br>
Adding IPv6 is actually worse - it just increases their capex and opex<br>
for no business benefit.<br>
<br>
I&#39;ve heard SR recently called the next MPLS. So how many Enterprises<br=
>
have adopted MPLS?<br>
<br>
When Enterprises need to access IPv6 Internet services, they&#39;ll just<br=
>
IPv6 enable their boundary Internet access security devices and mail<br>
servers.<br>
<br>
IPv6 will be used by Enterprises when it either provides a compelling<br>
advantage over IPv4, or where a vendor&#39;s &quot;turn key&quot; solution =
uses it.<br>
I&#39;ve seen that recently with AMI smartmeter mesh networks.<br>
<br>
Here in Victoria, AU, there are probably in the order of 1M+ IPv6 AMI<br>
smart meters across multiple electricity distributors. They&#39;re using<br=
>
IPv6 for that because that is what the vendor&#39;s end-to-end AMI<br>
solution uses. They use IPv4 to access the OSS and servers that are<br>
used to troubleshoot that network, and there is no real benefit for<br>
the organisation to deploy IPv6 on their internal LANs to access those<br>
servers.<br>
<br>
Inventing a new IPv6 feature just to try to encourage adoption isn&#39;t<br=
>
going to be that successful. The new feature has to be a compelling<br>
solution to a problem that the enterprise has, that justifies the<br>
additional and typically very large expense of deploying IPv6 to get<br>
it.<br>
<br>
Regards,<br>
Mark.<br>
<br>
<br>
<br>
On 31 March 2017 at 03:54, Ackermann, Michael &lt;<a href=3D"mailto:MAckerm=
ann@bcbsm.com">MAckermann@bcbsm.com</a>&gt; wrote:<br>
&gt; This is something I tried to say at the mic today, but I was too late.=
<br>
&gt; If we put potentially valuable use cases into the bucket of &quot;Exce=
ptions&quot;,=C2=A0 this becomes yet another excuse to delay or avoid adopt=
ion of IPv6 by the very large percentage of Enterprises who have yet to do =
so (and have no serious plans) today.<br>
&gt;<br>
&gt; I am hopeful that work in the IETF will provide features and hence mot=
ivation for us sadly delinquent Enterprises to begin actually using IPv6.=
=C2=A0 =C2=A0 I am concerned that perception of solutions being &quot;Excep=
tions&quot; or non standard, will cause consternation (warranted or not) an=
d avoidance.<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: ipv6 [mailto:<a href=3D"mailto:ipv6-bounces@ietf.org">ipv6-bounc=
es@ietf.org</a>] On Behalf Of Suresh Krishnan<br>
&gt; Sent: Thursday, March 30, 2017 9:30 AM<br>
&gt; To: Leddy, John &lt;<a href=3D"mailto:John_Leddy@comcast.com">John_Led=
dy@comcast.com</a>&gt;<br>
&gt; Cc: <a href=3D"mailto:draft-ietf-6man-rfc2460bis.all@ietf.org">draft-i=
etf-6man-rfc2460bis.<wbr>all@ietf.org</a>; 6man WG &lt;<a href=3D"mailto:ip=
v6@ietf.org">ipv6@ietf.org</a>&gt;; <a href=3D"mailto:ietf@ietf.org">ietf@i=
etf.org</a><br>
&gt; Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-=
08<br>
&gt;<br>
&gt; Hi John,<br>
&gt;=C2=A0 =C2=A0Thanks for chiming in. I recognize that you might have use=
 cases that might be better off with header insertion but I think they shou=
ld be handled as and when they come up for consideration (e.g. in the SRv6 =
discussions). Holding up this document is not going to help in any way in r=
einterpreting what RFC2460 intended. My suggestion for proponents of safe h=
eader insertion to write up how it is expected to work and have the discuss=
ion then.<br>
&gt;<br>
&gt; Thanks<br>
&gt; Suresh<br>
&gt;<br>
&gt;&gt; On Mar 29, 2017, at 9:59 PM, Leddy, John &lt;<a href=3D"mailto:Joh=
n_Leddy@comcast.com">John_Leddy@comcast.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; On Mar 14, 2017, at 9:47 PM, Suresh Krishnan &lt;<a href=3D"ma=
ilto:suresh.krishnan@ericsson.com">suresh.krishnan@ericsson.com</a>&gt; wro=
te:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; NEW:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; With one exception, extension headers are not examined, proces=
sed,<br>
&gt;&gt;&gt; inserted, or deleted by any node along a packet&#39;s delivery=
 path,<br>
&gt;&gt;&gt; until the packet reaches the node (or each of the set of nodes=
, in<br>
&gt;&gt;&gt; the case of multicast) identified in the Destination Address f=
ield of<br>
&gt;&gt;&gt; the IPv6 header...<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Please feel free to comment either privately or on list if you=
 have any concerns with this resolution going forward.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Suresh,<br>
&gt;&gt;<br>
&gt;&gt; I still have concerns that we are eliminating a tool that may prov=
e very helpful in migrations without understanding its value.<br>
&gt;&gt;<br>
&gt;&gt; The Internet transition of IPV4 -&gt; Dual Stack V4/V6 -&gt; IPV6 =
Only; has been long, operationally complex and full of unexpected challenge=
s.<br>
&gt;&gt; We are only now starting to make the transition from Dual Stack to=
 IPV6 Only, there are still many unknowns on how to complete this migration=
.<br>
&gt;&gt;<br>
&gt;&gt; As we contemplate finishing this major Network shift =E2=80=93 We =
find ourselves in the early stages of another.<br>
&gt;&gt;<br>
&gt;&gt; The transition from Physical to Virtual Infrastructure.=C2=A0 Agai=
n, the migration will be long, operationally complex and full of unexpected=
 challenges.<br>
&gt;&gt;<br>
&gt;&gt; In the old world with Servers running Applications in Physical loc=
ations designed for very predictable loads; using an encap/decap tunnel to =
emulate a physical circuit between locations has many attractive properties=
 =E2=80=93 but that is compared to actually ordering and provisioning real =
circuits between locations.<br>
&gt;&gt;<br>
&gt;&gt; In the new world of dynamic resources spun up on demand in distrib=
uted environments across multiple providers, Applications having the Intell=
igence and State to bring up their own required connectivity is very natura=
l.=C2=A0 This is where we are putting the majority of our efforts.=C2=A0 SR=
v6 enables very attractive solutions by Applications building their own hea=
ders.<br>
&gt;&gt;<br>
&gt;&gt; The challenges come as we try to migrate and require these two inf=
rastructures to Interoperate for a long time.<br>
&gt;&gt; Burdening the new Virtual world with Old, Static circuit paradigms=
 is not optimal.<br>
&gt;&gt; Supplementing the legacy infrastructure with an assist function se=
ems<br>
&gt;&gt; a reasonable solution.=C2=A0 (Ext Hdr insertion/deletion or encap/=
decap<br>
&gt;&gt; tunnels)<br>
&gt;&gt;<br>
&gt;&gt; The preferred assist mechanism seems to be the one that allows the=
 New<br>
&gt;&gt; World to operate in its final preferred state, sending and receivi=
ng packets with their own headers. (SRv6) But what does an Application in t=
he new world due when it is attempting to communicate with an Application i=
n the Old World?<br>
&gt;&gt; Shouldn=E2=80=99t it build an SRv6 header?=C2=A0 That would mean t=
hat the assist function would need to be the last SID in the Segment List a=
nd be capable of removing the SRH.<br>
&gt;&gt; Wouldn=E2=80=99t it make sense for the assist function to do the s=
ame thing in the reverse direction; an Old World Server talking to a New Vi=
rtual World Application?=C2=A0 Insert an SRH.<br>
&gt;&gt;<br>
&gt;&gt; If this insert/delete of an SRH is prematurely prohibited;=C2=A0 W=
hat is a recommended solution to the Real World problem above.=C2=A0 Not us=
e case, we are implementing.<br>
&gt;&gt;<br>
&gt;&gt; Again; I=E2=80=99m worried we are eliminating a tool that may prov=
e very<br>
&gt;&gt; helpful, preclude its use in future IETF work and shutdown a path =
for<br>
&gt;&gt; Innovation in Networking,<br>
&gt;&gt;<br>
&gt;&gt; Thank you for asking and listening to my concerns,<br>
&gt;&gt;<br>
&gt;&gt; John Leddy<br>
&gt;&gt; Comcast<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The information contained in this communication is highly confidential=
 and is intended solely for the use of the individual(s) to whom this commu=
nication is directed. If you are not the intended recipient, you are hereby=
 notified that any viewing, copying, disclosure or distribution of this inf=
ormation is prohibited. Please notify the sender, by electronic mail or tel=
ephone, of any unintended receipt and delete the original message without m=
aking any copies.<br>
&gt;<br>
&gt;=C2=A0 Blue Cross Blue Shield of Michigan and Blue Care Network of Mich=
igan are nonprofit corporations and independent licensees of the Blue Cross=
 and Blue Shield Association.<br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listi=
nfo/ipv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/<wbr>listinfo/ipv6</a><br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
<br>
</blockquote></div></div>

--001a1143d1484f0c27054bf8c466--


From nobody Thu Mar 30 13:48:41 2017
Return-Path: <otroan@employees.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 A109A1294B4; Thu, 30 Mar 2017 13:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vfzLOwZp-1ez; Thu, 30 Mar 2017 13:48:33 -0700 (PDT)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id E3B701270A7; Thu, 30 Mar 2017 13:48:33 -0700 (PDT)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 30 Mar 2017 20:48:33 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 2CE12D788B; Thu, 30 Mar 2017 13:48:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=R6/E6qQB9Vdy8Fmo4vFMT5KkYaU=; b= aYHRnINlSPUF6SgDQU8JpPNMEQUriGs0Zj2raMb38isbtW7LRcztn9Rw4jZxIKhI x52yMAqTXfplknHXcCWznVlWIC5TLwQd6aogR4DSoTIVb/PwDPermZfw2xkg059K s/FKgpQSZzWNJjZNVgLskjqKvZ2T/vHVcs0loiYL2po=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=oXy8lBJKZvg8KOPLehmzRyp ML/Q45Ys+qV8Ml6zPhenVXrKn7TNJ0G0WpzUtsKe/jRMc5BK81TKkKlAzy/2b0BO OKx2aMR/YuJccSk2bWl7OIqIXzTpQ6RWuLUabmIm4i1SzqAabHrItS+foxZn9ZGj mM7OgD5ifnrswxuFxgXI=
Received: from h.hanazo.no (dhcp-8e77.meeting.ietf.org [31.133.142.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 13A96D788A; Thu, 30 Mar 2017 13:48:33 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 18B9AA6BF52F; Thu, 30 Mar 2017 15:48:34 -0500 (CDT)
From: otroan@employees.org
Message-Id: <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_6EEA9F65-61B6-4EAE-A7B6-8F3ECDF9BD3F"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Date: Thu, 30 Mar 2017 15:48:33 -0500
In-Reply-To: <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com>
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>, 6man WG <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, "Leddy, John" <John_Leddy@comcast.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
To: Robert Raszuk <robert@raszuk.net>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oahRocxJJ2yf9MRWs3QTaZHb5RQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 20:48:36 -0000

--Apple-Mail=_6EEA9F65-61B6-4EAE-A7B6-8F3ECDF9BD3F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Robert,

> Ok so till a new document updates 2460bis any further work on EHs is =
frozen as it would reference 2460bis with new text. That was my main =
point.
>=20
> And what current EH implementations are supposed to do in the mean =
time ? Would IANA allocate codepoints for EH work before 2460bis is =
formally updated which in the current IETF speed is easy 2+years ?
>=20
> Note that without the proposed clarification none of the above =
obstacles exist.

Write a document describing the mechanism using header insertion. That =
document should cover the issues raised with header insertion in =
general. I don't think the document should update 2460bis. The general =
restriction still stands.

Best regards,
Ole

--Apple-Mail=_6EEA9F65-61B6-4EAE-A7B6-8F3ECDF9BD3F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJY3W8hAAoJEL7aWKiYQt92oekP/jtEM/Mv2VGRwdthn85nF/u0
Zi8kx+ntOl9Lcydv1BOYGkCWzYDWyImzkSFCSvee4GJ94Do2obV7kVRyYX+eQGKd
UhTBf/uDjX7dUDsSk9v0qqiyw2jA3BTTn+dvhWF+9SG1B+45Cx8qr9qnir8G20sw
8Y+DssH3NF8Uq0gzNamlMgbv7LN+sXRlT9eDVV9G+NEg+6dEatjPfcNkE4FK+zjI
DlSWwfwz//nJeOLrGQC4q8QH94B+7MF1U7rrKi+XTkz0R8BW4m7yBofuK45d9aCC
T3oIEiHqOiEG3TsN0oA2YnSkvb0DhoeGq8ZIKxl7u5qCdtgDlXDTt7IrgrBvK1hG
dGBhPlvvWRluZkWlAcvZjrtr1CMGrjCO4O7B5SCUuotXiCw/nbTNk38nB7hN468y
2L2oHqDC6MQaX1IscVTcT5WFQYeVRM456fuMjEIyqxClVy8du5q7xrEUdJ5FOhr8
KRnppK5qKspw+28mJ2fMLT0TlKCsqP0Z+8Us3KtyBAfIpX3McBuCLMZaL3tGQBK6
ngcJBd+BtIwBGdbO0YFjeH9F1wOG3ZcMTtDsLnlOFPcFziz6XO1VDjg/QRrX9+jU
ZPZlKJbO5uASFeRj+aP7AYA+nSlk5iwXkeOLfvYE7fl0/CUhtgf2N9XQZVAgsj5G
hvyRCOmu2CN1ZL2JRst2
=sV/U
-----END PGP SIGNATURE-----

--Apple-Mail=_6EEA9F65-61B6-4EAE-A7B6-8F3ECDF9BD3F--


From nobody Thu Mar 30 13:50:00 2017
Return-Path: <sandy@tislabs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF2A8129552; Thu, 30 Mar 2017 13:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQaG43sGcSip; Thu, 30 Mar 2017 13:49:36 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 366AB12951B; Thu, 30 Mar 2017 13:49:26 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 7E49628B003B; Thu, 30 Mar 2017 16:49:25 -0400 (EDT)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id 787831F8036; Thu, 30 Mar 2017 16:49:14 -0400 (EDT)
Subject: Re: secdir review of draft-ietf-dnsop-nsec-aggressiveuse
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_271850B6-8E28-403F-8932-A8747B257FB4"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Sandra Murphy <sandy@tislabs.com>
In-Reply-To: <CAHw9_iL-UdKNsBSP1imzOg1PcjAvhk=b7Uw+nG-gDeQSOfgUxQ@mail.gmail.com>
Date: Thu, 30 Mar 2017 16:47:00 -0400
Cc: Sandra Murphy <sandy@tislabs.com>, IETF Security Directorate <secdir@ietf.org>, draft-ietf-dnsop-nsec-aggressiveuse@ietf.org, dnsop-chairs@ietf.org, The IETF <ietf@ietf.org>
Message-Id: <C40CFD27-6EF1-4925-8E0E-375796DE0220@tislabs.com>
References: <F8D0F7F4-414B-44A4-B6D0-428D506D97C7@tislabs.com> <CAHw9_iL-UdKNsBSP1imzOg1PcjAvhk=b7Uw+nG-gDeQSOfgUxQ@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g0Rs_P9dY-ToavuQnNz-fBoL0dU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 20:49:39 -0000

--Apple-Mail=_271850B6-8E28-403F-8932-A8747B257FB4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Top note:

My original message misspelled the dnsop-chairs alias.  Warren replied =
to everyone, so I=E2=80=99m guessing that he got a bounce from my error.

Anyone responding to Warren=E2=80=99s message, please note.


> On Mar 30, 2017, at 2:59 PM, Warren Kumari <warren@kumari.net> wrote:
>=20
> On Tue, Mar 28, 2017 at 11:34 AM, Sandra Murphy <sandy@tislabs.com> =
wrote:
>>=20
>> I am curious about my thought that an attacker might find this of =
benefit, as they can learn of non-existence in just one query, rather =
than every name in a NSEC denied range. I know zone walking is a concern =
to some, but I do not know if ease of determining non-existence is also =
a concern.
>=20
>=20
> I may have missed something, but I do not see the concern -- an
> attacker can already learn of non-existence in just one query; that is
> exactly what NSEC (already) provides.
> If an attacker queries e.g the root for .belkin they get back =
(trimmed):
> $ dig +dnssec belkin
> beer. 44025 IN NSEC bentley. NS DS RRSIG NSEC
>=20
> This tells the attacker that nothing exists between beer and bentley
> (in one query). All that this document does is optimize the recursive
> server so that, if the attacker tries to instead do e.g a dictionary
> attack and ask many names between beer and bentley the recursive (and
> auths) have less work to do. The attacker only advantage to the
> attacker is that they have to wait slightly less time doing a
> dictionary attack -- but, they would be much better off asking for the
> (existing) NSEC info directly.

Yes, silly of me, sorry, (Ill) thought retracted.

>>=20
>> The last paragraph of 5., nothing in 5.1 or 5.2, and the last =
paragraph of 5.3
>> use SHOUD/MUST/MAY kinds of language.  For the paragraphs that =
don=E2=80=99t - should
>> they?  For the paragraphs that do, is this additional behavior or a
>> replacement for existing spec (i.e. like the section 7 update to =
RFC4035).
>> If a replacement, a replacement of what?  If not, where do the new =
paragraphs
>> fit?
>>=20
>=20
> I don't think that these bits to need the 2119 language - they are
> more explanatory, and providing explanation / justification for the
> change baing made to RFC4035 (which is updated in Section 7).

So you are going to take out the normative language?  Otherwise, well, =
it confused me.


>=20
>>=20
>> page 7
>>=20
>>  Section 5 of [RFC2308] states that the maximum number of negative
>>  cache TTL value is 3 hours (10800).
>>=20
>> I don=E2=80=99t find a maximum in RFC2308.  I do find:
>>                   Values of one to three hours have been found to =
work well
>>  and would make sensible a default.
>> Did I miss something?
>>=20
>=20

> I changed this to be:
> Section 5 of [RFC2308 suggests a maximum default negative cache TTL
> value of 3 hours (10800). It is RECOMMENDED that validating resolvers
> limit the maximum effective TTL value of negative responses
> (NSEC/NSEC3 RRs) to this same value.

Quibble:

I still don=E2=80=99t see that RC2308 sets 3 as a maximum, just =E2=80=9Ch=
ave been found to work well=E2=80=9D.

Could be elsewhere in RFC2308, and I missed it.



=E2=80=94Sandy

--Apple-Mail=_271850B6-8E28-403F-8932-A8747B257FB4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJY3W7RAAoJEHplpQeet0IZn/wP/RrQPR2KbX7WtmkWyT+VS4Za
TUB8GcwFndDp57pHXQKSxKLlO7jDwU/KEqrb9XsNu9/5yYtTh6RThh1G7KdgBAUB
ivrnknHsQADtGUle1KMbUbKKm1ozazAeufX2lDdRbDL7Ri8IuoBqzZem6DjccFiA
bs8Ks5NJNpHCi18cYq7JQCWwHAmpsWHPy5HCBaz5vOb4de1CIMYEZiG3KmFbM9Aj
Q7AeRP2SiLjifqDFxxjZ/RhiGyx0xvmoKapLUDlXvSBn27BOXpYulPmyj3wnh6I2
YSVDT1GbpuYkFBTyvCgVXOb/S2XkIW5N6my6UkQewOSyPElUfgFs5MLIXyB/pPk2
6FrQoIjVIqaoqlh6aH5vbmg+N3DANZcHhxBzsOImTYOT1vpcaFiadcwqbeO7u0cb
Fv+x/lWyO/pWkPYCYfilzGvqULzlEk3KyWO4Gr44JkyrqJ8MnIjfhsJSy2OoPJPb
LsBzrMcBRg6F18KlNuS1TrB5BjI6JmWwwiUtZ0gmFayySAvs2gvx3YyQzIc9UCNq
Ic42jHnXHndtfK8qdLJ8FRYLuzVAnzEF6UKOTBPkJpd0QcqidzoXE0V3z2NAUgzZ
nxcaDW+lGOO8++0h1DXVSxGo1/D7bb8+Jc557oLqvZFGkRbB4HVumMxuMhJdjBa7
a3fSZmSAY8nynCE6pdJd
=BxAe
-----END PGP SIGNATURE-----

--Apple-Mail=_271850B6-8E28-403F-8932-A8747B257FB4--


From nobody Thu Mar 30 13:55:46 2017
Return-Path: <rraszuk@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 9166D129543; Thu, 30 Mar 2017 13:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBk_3X708ev9; Thu, 30 Mar 2017 13:55:26 -0700 (PDT)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2A501294A9; Thu, 30 Mar 2017 13:55:25 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id 68so3726303itx.0; Thu, 30 Mar 2017 13:55:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AixT/WLWTOfZZpk0BxcpNSjX4D5f6CEkuMsD1cSvhis=; b=UJjuh6gDOraEu+aNVO4UDmpFZo9vb/4Ko+NmYb/lMS4DN0XlXcj24HQmL1waTUpcvj hQ3FCmzObLIKMgH+wn24ej6kGEEwUP4/JZvhEv+Fb6IwNpMLE1cmzqXetKEriqEzwNiE ElttXj5OzRRWYDNIJK6c57IlVB9TWWKazfVqNKpveHwhKyRqqEddFJc/YHPuKnDDylmf ITL2Mv5ZQXrFpVVzSavw7MJJDWReMaZkT1E4Hxngljlb/yar66l9eDR0S7I8CHF1xfLx EW0L/vuyVRR5fpVKqv9TLnC1CkhiD0REbqV+/cLcEJVtcA+rBNsulaU1Q3lv9lBh7AlI uTEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=AixT/WLWTOfZZpk0BxcpNSjX4D5f6CEkuMsD1cSvhis=; b=jn6ekjPosguP8vp3w5UcpvRkVTMPslka904HMjhDP8dmiyTByJZObmsnpFMa+Yncyk nz0uHyGehy0uhYuOCDkz68kRP+c/p3kJjPv/0hSVQzA/uiyG9oB8ZYnm/8cN6+DIoAqs x/ibxzsgZIqG7dRoyLW0wbO9DzzVlavDybnOUYyHyapZNeO6rEMfJr5BpeXWOOu9aYdN HI5RCrkKkPUShskPncba1eMt5Hq3C3+y2K9sb67v10dAqsYoyGibXVWg0FisO1qBC5xQ K9nioXvQaVS4PB7ZOKhu5hr5zPkrvuA5hLeZX+qQWQAh1LpCdY8XeYaWpREBNRtoaxCN /ipg==
X-Gm-Message-State: AFeK/H2LOPWM52oT+VXRBNlsCfZxOV+ZDkMbBhDz6lQu511rKNkw+soMlyXnQrvF+TLaWK91e1DE0CMKa36xwA==
X-Received: by 10.36.90.144 with SMTP id v138mr303222ita.24.1490907325175; Thu, 30 Mar 2017 13:55:25 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 13:55:23 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 13:55:23 -0700 (PDT)
In-Reply-To: <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 30 Mar 2017 15:55:23 -0500
X-Google-Sender-Auth: 5sgGtpmhSpPUDVnaclKbRTtLkGI
Message-ID: <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: otroan@employees.org
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>, "Leddy, John" <John_Leddy@comcast.com>,  IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a11429e7882a8de054bf8e9d9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TkXQn-2nu88iZ3nrbXMpC9GnaR4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 20:55:28 -0000

--001a11429e7882a8de054bf8e9d9
Content-Type: text/plain; charset=UTF-8

Ole,

Correct me if I am missing someting but the entire debate is not about
describing or not header insertion.

I am under assumption that originating hosts still can legally insert it.

It is all about to modify EH in flight - right ? Moreover concerns raised
are about side effects of it like MTU .. not lack of instructions on how to
insert, modify or remove EH elements.

So what exactly are you expecting WG to deliver as next step if 2460bis
goes fwd ? Is detecting the max MTU on end to end path even in 6man's
charter ?

Cheers,
R.

On Mar 30, 2017 15:48, <otroan@employees.org> wrote:

> Robert,
>
> > Ok so till a new document updates 2460bis any further work on EHs is
> frozen as it would reference 2460bis with new text. That was my main point.
> >
> > And what current EH implementations are supposed to do in the mean time
> ? Would IANA allocate codepoints for EH work before 2460bis is formally
> updated which in the current IETF speed is easy 2+years ?
> >
> > Note that without the proposed clarification none of the above obstacles
> exist.
>
> Write a document describing the mechanism using header insertion. That
> document should cover the issues raised with header insertion in general. I
> don't think the document should update 2460bis. The general restriction
> still stands.
>
> Best regards,
> Ole
>

--001a11429e7882a8de054bf8e9d9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Ole,<div dir=3D"auto"><br></div><div dir=3D"auto">Correct=
 me if I am missing someting but the entire debate is not about describing =
or not header insertion.</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>I am under assumption that originating hosts still can legally insert it.<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto">It is all about to modif=
y EH in flight - right ? Moreover concerns raised are about side effects of=
 it like MTU .. not lack of instructions on how to insert, modify or remove=
 EH elements.</div><div dir=3D"auto"><br></div><div dir=3D"auto">So what ex=
actly are you expecting WG to deliver as next step if 2460bis goes fwd ? Is=
 detecting the max MTU on end to end path even in 6man&#39;s charter ?</div=
><div dir=3D"auto"><br></div><div dir=3D"auto">Cheers,</div><div dir=3D"aut=
o">R.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mar 30, 2017 15:48,  &lt;<a href=3D"mailto:otroan@employees.org">otroan@=
employees.org</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">Robert,<br>
<br>
&gt; Ok so till a new document updates 2460bis any further work on EHs is f=
rozen as it would reference 2460bis with new text. That was my main point.<=
br>
&gt;<br>
&gt; And what current EH implementations are supposed to do in the mean tim=
e ? Would IANA allocate codepoints for EH work before 2460bis is formally u=
pdated which in the current IETF speed is easy 2+years ?<br>
&gt;<br>
&gt; Note that without the proposed clarification none of the above obstacl=
es exist.<br>
<br>
Write a document describing the mechanism using header insertion. That docu=
ment should cover the issues raised with header insertion in general. I don=
&#39;t think the document should update 2460bis. The general restriction st=
ill stands.<br>
<br>
Best regards,<br>
Ole<br>
</blockquote></div></div>

--001a11429e7882a8de054bf8e9d9--


From nobody Thu Mar 30 14:06:20 2017
Return-Path: <otroan@employees.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 562901294D2; Thu, 30 Mar 2017 14:05:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4BtAXcfibokg; Thu, 30 Mar 2017 14:05:33 -0700 (PDT)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id BC3B51294B5; Thu, 30 Mar 2017 14:05:33 -0700 (PDT)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 30 Mar 2017 21:05:33 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 63B0AD788B; Thu, 30 Mar 2017 14:05:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=20/sY23ATwWs938r1mKHHsMmqIM=; b= so4QzReKNniG2WGVUIeLaR22wgKvI4xcVpB5YJDJkMTv1sRuq/EbF8vVZ71jmk0q +sSJ/lzyANkEcu+Dlubbq1pma0YQFU5cy/ivX9tVFbJpyDGQQgdw7g9s7nckXrKl A65jjTV9qF0KNadIaxuDMErr77080ZjRK+wuz8aPq04=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=TKFt1sXYHRZO6eUCkxICs/k uGT/Ec7vOp+RJg1X9hhYMqyTsVroBHSk7UyNA2T9q/4awkVLY4NWU+kEgmnu+Ksv Zdn4u8eN1TaYbLg3vzbBdEvqX43LYfxSsifDdiljM5p4U60Ed+y0f43xeRpoTOym 3H7y41mkALFh4EKk35RM=
Received: from h.hanazo.no (dhcp-8e77.meeting.ietf.org [31.133.142.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 52FF0D788E; Thu, 30 Mar 2017 14:05:33 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 4C92BA6BF80F; Thu, 30 Mar 2017 16:05:34 -0500 (CDT)
From: otroan@employees.org
Message-Id: <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_73849059-1387-463D-9569-A8415D49DB84"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Date: Thu, 30 Mar 2017 16:05:33 -0500
In-Reply-To: <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com>
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>, "Leddy, John" <John_Leddy@comcast.com>, IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
To: Robert Raszuk <robert@raszuk.net>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6-1GQa06DrhKoFYzUlNVoBe9oSk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 21:05:36 -0000

--Apple-Mail=_73849059-1387-463D-9569-A8415D49DB84
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Robert,

> Correct me if I am missing someting but the entire debate is not about =
describing or not header insertion.
>=20
> I am under assumption that originating hosts still can legally insert =
it.
>=20
> It is all about to modify EH in flight - right ? Moreover concerns =
raised are about side effects of it like MTU .. not lack of instructions =
on how to insert, modify or remove EH elements.
>=20
> So what exactly are you expecting WG to deliver as next step if =
2460bis goes fwd ? Is detecting the max MTU on end to end path even in =
6man's charter ?

You can write a new protocol specification independently of 2460bis that =
does whatever it has to do, and then we can argue over that document on =
its own merits.

Cheers,
Ole

--Apple-Mail=_73849059-1387-463D-9569-A8415D49DB84
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJY3XMeAAoJEL7aWKiYQt92P88QAMN8er2L40pnH7J5XocUDKH0
acB5cTMAYgtF66CnxOKSQTwpSP7/gH21tiroVx/27FySV97yYk5o8usf5joECqin
iSDnyigr6/NMV31B/xC/Berp7Mqp0h95xGOEhdMaLgnDfb1L8L7sKiwJuroRvr/G
GAuk4/l5qOg2ONcyxcCdsJldEDYbUO3aKKwGqEYo5Wi+xpDCd/pjFP1SaXTIM/ki
Qbf3PkiDCiAZbDjQDYhc8aTVQHU7/KzcUQEquXPEF8mrr1fcl/1oWw+SqL+ALR2y
/tYzMWIomuLqiOP1HDNdLT5hl+zrbflOnSxAUP3Nwsjdz54kdSKCvjO8niu41eHm
cxLVrkYcQgg3opd7n0hEydRCbq4vLgO7nNL2ZEDJv7Dev1pliqgf9BzQ2k87M09S
M0Iru6kvEGtloYUSJLoFWsAjrG5hcGIUoawo2j+ykjeASXCiec6az35rGUp/wex/
W2G7vHhH58bgIAKLLhVJ0SxT5S3aDHdf6VEdwFgbSsULn7bbgXvSlXpMrTUwJW9u
pc+zY2jpP/vOT7M0usDfQ4kTNjK1WFDZVNzEX2B5NkvQfRZv4szLsLW+qoDOinvQ
lQkMre/wOmtAUsvR/+tKO2zgQrmn8r2R4vtF4vTNpe4JHXh6gBKNb0rm+xu6xKKJ
XRwEV5ZpLY97mS4zWRP+
=UlCU
-----END PGP SIGNATURE-----

--Apple-Mail=_73849059-1387-463D-9569-A8415D49DB84--


From nobody Thu Mar 30 14:13:13 2017
Return-Path: <rraszuk@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 DAE4F129483; Thu, 30 Mar 2017 14:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id niRhNV8m2Vv6; Thu, 30 Mar 2017 14:13:09 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A4081294FF; Thu, 30 Mar 2017 14:13:05 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id y18so3793814itc.1; Thu, 30 Mar 2017 14:13:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9qHEfACCnq5wDrqZG/5dXKPkaffAc4qLLnCUgsQxEU4=; b=pkyKnu1v0obvciCDC2WXQhiztpwaexkSaSfOdulK39PJaGjnJEf/0FKYvPg3Edpv0+ UmoOE9OA3hXK6Qsf0dAX7u+zKldytmo6M6/0a9YJ8682cGHFA2t3Jpy6hZOUdjiaHUZU KrSHjb3iJJs/dYTbko9JJ5GO207/fJ0yWbg27y8arnvAU58UvMKbwhouIt3GmM+W9Ln7 H1uOsJSOydR1N9ADBN0MqiEdjfe/idI6H7GGuQZxMQszCS9aRET2ebHZiIt8ub4hsIle gyOSsHSI34XLCD2VdUoHNmD1jgKB2FJh5YeYQhvZkU/pHqdfXklrnXiohippupf+ev1r 3slw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9qHEfACCnq5wDrqZG/5dXKPkaffAc4qLLnCUgsQxEU4=; b=pXLK4WJlxlODDtBDLUEM1Nbx3ftCOhQfGt/EuIb2oK04j6PeUtMVB/ZuUewUv+J0jZ lUA4c7kukHTJVncsDUHh+j7iUtnbKmWIVBXjP7R40K3Zp13kxIBWuORzHg7QkzT8Uv2f 19KawoPBlLeHoGDmI6KsV4jyKXdhXocxWa4wuy9NskuEKlutFFdnc7xdQ3hGDUpx4qsi 1xtC2SYq3mwC2D0TtfkfTC7ejEMCwO1iId+dxrAf4tTQUx1bIDOA7mVs7vlGBqVV3NIt ZiUeBMy+Rmcdev1V/ZbsKulnQ/XlArfqvBBQ3g9xoCvGqkwEeVDym9wTjqznSOmE/4Xj MqaA==
X-Gm-Message-State: AFeK/H3Hdmhlh67eA17RL+jR7PsMu1/3j5dX5a/NDiiaCAp58dbMlboRR88gw96rDDdZ2Xh4ZSs3YXY1Z1KbAg==
X-Received: by 10.36.43.78 with SMTP id h75mr308573ita.25.1490908384722; Thu, 30 Mar 2017 14:13:04 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 14:13:03 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Thu, 30 Mar 2017 14:13:03 -0700 (PDT)
In-Reply-To: <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 30 Mar 2017 16:13:03 -0500
X-Google-Sender-Auth: AOK4OYC5rm0V-o8rlpvQ1A0Et8M
Message-ID: <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: otroan@employees.org
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>, "Leddy, John" <John_Leddy@comcast.com>,  IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a1146f426aa0381054bf92898
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iGLLVtRjYnmBrhTy-4NzwDOkTJk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 21:13:11 -0000

--001a1146f426aa0381054bf92898
Content-Type: text/plain; charset=UTF-8

What's wrong or what is missing in
https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-05

?

On Mar 30, 2017 16:05, <otroan@employees.org> wrote:

> Robert,
>
> > Correct me if I am missing someting but the entire debate is not about
> describing or not header insertion.
> >
> > I am under assumption that originating hosts still can legally insert it.
> >
> > It is all about to modify EH in flight - right ? Moreover concerns
> raised are about side effects of it like MTU .. not lack of instructions on
> how to insert, modify or remove EH elements.
> >
> > So what exactly are you expecting WG to deliver as next step if 2460bis
> goes fwd ? Is detecting the max MTU on end to end path even in 6man's
> charter ?
>
> You can write a new protocol specification independently of 2460bis that
> does whatever it has to do, and then we can argue over that document on its
> own merits.
>
> Cheers,
> Ole
>

--001a1146f426aa0381054bf92898
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">What&#39;s wrong or what is missing in=C2=A0<a href=3D"ht=
tps://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-05">https:=
//tools.ietf.org/html/draft-ietf-6man-segment-routing-header-05</a><div dir=
=3D"auto"><br></div><div dir=3D"auto">?</div></div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">On Mar 30, 2017 16:05,  &lt;<a href=3D"ma=
ilto:otroan@employees.org">otroan@employees.org</a>&gt; wrote:<br type=3D"a=
ttribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">Robert,<br>
<br>
&gt; Correct me if I am missing someting but the entire debate is not about=
 describing or not header insertion.<br>
&gt;<br>
&gt; I am under assumption that originating hosts still can legally insert =
it.<br>
&gt;<br>
&gt; It is all about to modify EH in flight - right ? Moreover concerns rai=
sed are about side effects of it like MTU .. not lack of instructions on ho=
w to insert, modify or remove EH elements.<br>
&gt;<br>
&gt; So what exactly are you expecting WG to deliver as next step if 2460bi=
s goes fwd ? Is detecting the max MTU on end to end path even in 6man&#39;s=
 charter ?<br>
<br>
You can write a new protocol specification independently of 2460bis that do=
es whatever it has to do, and then we can argue over that document on its o=
wn merits.<br>
<br>
Cheers,<br>
Ole<br>
</blockquote></div></div>

--001a1146f426aa0381054bf92898--


From nobody Thu Mar 30 14:50:31 2017
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 52C7512960F; Thu, 30 Mar 2017 14:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id URTPAMwqAydp; Thu, 30 Mar 2017 14:50:22 -0700 (PDT)
Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55B16129548; Thu, 30 Mar 2017 14:50:22 -0700 (PDT)
Received: by mail-io0-x242.google.com with SMTP id 68so4279466ioh.3; Thu, 30 Mar 2017 14:50:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=7CUCyhvMUQ4PAI3Cn4+2B3y0kH2rADicqfAqtWpYvGs=; b=ii37flu6MV9XGHe1b9kMACSAwcS5xnsR6ethpw6qJfcWORqBL9ZC7amDLfTO4DPYh8 fTU6hu3MolNqO4mTOGDpSZG+HZtJxn8S5HTA5Yp11PBgfdxObjC6yrbp4X4/610httJ2 FK3sIL/DFKhynGcPKEBVtXFiSsVaDuHMIliFOnXSvNEm/Coqjeog7nwm4KXj8YW59feh R6AJoJiV0KEUWTVx7XeRRBElPMYjKNa6FsjBtyamG9r9v9U6pCH0ijprk+1ojvALZtoc dgXYiNk7nLXvmfOzNwfYfaOeE/n9Wlz0VUeF0ZnTJiuhw9Rwyl27nxs+Fr/jRbL6arOO hAGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=7CUCyhvMUQ4PAI3Cn4+2B3y0kH2rADicqfAqtWpYvGs=; b=OY5ajjow2bb4DBbYy1rbR9lesrZRDkR/UYMBeKRNMn6+cijZCl5yVP96uyZ6toSFTx UWr7tIPPbkvXVjO6NsC8ZkytVkCdlCq+qpzQhdarvnVxzAbjobT6YrTviPw5IuafKTER f5lEaC8fWVfCyW2VtFii+WBebRCbVxQ6etgcEklv0tmlVg+1uogNR7REPxiGPrdHOiYd vGeZv16LEQl934L0KdwV04rsInFWJEeL5b0azfT1UhepVQwFpyHx1rsGbe8TyvmqdArJ wrEG6tbrwlcn/PbES3MHuyTJBUqpJS9i6EqkP/TIgMScmYVMp5p1vhh65fjRieWC0aYF ndPw==
X-Gm-Message-State: AFeK/H0sv7bmZfh2eMcKXPAKstqhrF1x4qtxG/IgitDhNm8nwoBwJp48wspRrPizBjpN+g==
X-Received: by 10.107.46.24 with SMTP id i24mr3577782ioo.84.1490910621700; Thu, 30 Mar 2017 14:50:21 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:28cc:dc4c:9703:6781? (t2001067c0370012828ccdc4c97036781.v6.meeting.ietf.org. [2001:67c:370:128:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id c91sm2091019iod.18.2017.03.30.14.50.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 14:50:21 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Robert Raszuk <robert@raszuk.net>, otroan@employees.org
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>, IETF Discussion <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com>
Date: Fri, 31 Mar 2017 10:50:29 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_f6S23fXRiwX7Aix32yCGomoRoE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 21:50:24 -0000

On 31/03/2017 10:13, Robert Raszuk wrote:
> What's wrong or what is missing in
> https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-05
> 
> ?

Once we get 2460bis out of the door, we should seriously tackle that question.
Honestly it's going to be easier then. I perhaps disagree with Ole whether we
need an Updates: 2460bis but that depends on the details.

    Brian

> 
> On Mar 30, 2017 16:05, <otroan@employees.org> wrote:
> 
>> Robert,
>>
>>> Correct me if I am missing someting but the entire debate is not about
>> describing or not header insertion.
>>>
>>> I am under assumption that originating hosts still can legally insert it.
>>>
>>> It is all about to modify EH in flight - right ? Moreover concerns
>> raised are about side effects of it like MTU .. not lack of instructions on
>> how to insert, modify or remove EH elements.
>>>
>>> So what exactly are you expecting WG to deliver as next step if 2460bis
>> goes fwd ? Is detecting the max MTU on end to end path even in 6man's
>> charter ?
>>
>> You can write a new protocol specification independently of 2460bis that
>> does whatever it has to do, and then we can argue over that document on its
>> own merits.
>>
>> Cheers,
>> Ole
>>
> 


From nobody Thu Mar 30 14:59:37 2017
Return-Path: <tim.chown@jisc.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 DE050129567 for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 14:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ocjW2gMm3LN4 for <ietf@ietfa.amsl.com>; Thu, 30 Mar 2017 14:59:27 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F019612957A for <ietf@ietf.org>; Thu, 30 Mar 2017 14:59:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1490911164; bh=2zqT1BEFXVLlP+FR3MG/S9d1oxjI/0Pm3trq6WYZ+q0=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To:Content-ID:MIME-Version:Content-Type:Content-Transfer-Encoding; b=BeGnVdMRigdSd5CC/pSqzmN58p27u3oERCz/zE64qGfREA1UXxQbOfhJ7Q2j1RLUiSjXchuWteNGIYiJJiBRy1t65b9ARFnZy6WpzE6XfMhXwR9AbGwRAmIjrLgSnCYBWUgjybyUpHo+AVoT1qRWiFKZwdkU+/28fRJG+MJfGMc=
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-he1eur02lp0177.outbound.protection.outlook.com [213.199.180.177]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-97-m-SicZteMcqoQXph4Ge7Zw-1; Thu, 30 Mar 2017 22:59:19 +0100
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1138.eurprd07.prod.outlook.com (10.163.188.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1005.2; Thu, 30 Mar 2017 21:59:18 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::29d9:4eb6:edcf:55dc]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::29d9:4eb6:edcf:55dc%14]) with mapi id 15.01.1019.009; Thu, 30 Mar 2017 21:59:18 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Robert Raszuk <robert@raszuk.net>, =?utf-8?B?T2xlIFRyw7hhbg==?= <otroan@employees.org>, "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv71giYAPcbUKK9ywM4gSjvqGssVmAgAC6+QCAAAergIAAIVqAgAAFggCAAASRAIAAEj+AgABB54CAAAHpgIAAAteAgAACGICAAAp2gIAAAnWA
Date: Thu, 30 Mar 2017 21:59:18 +0000
Message-ID: <C0210CE1-7030-4BB9-BE4F-CB693D0DB1C4@jisc.ac.uk>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com>
In-Reply-To: <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [31.133.149.62]
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1138; 7:n6Vj6a+otlRpgM+wKyryPNDwgOR7R8RKco0s2OoPv0XtUbm0ly6g+U4wBlG1m9lgGJm0CaRokyFMiOkhae3kT8TMcIbIgKFikgEHxVWSiEjwY/nMsKUXZQvtGLv8zKpD1zAEinKPbmhRTHglY6HBUY46ADw0PZD+j4fnNsudMWZxW4LmRxDca3q/ciH3P8yBggdM7GOhYA3ZPO7dbBgPVzgy4xlwtF0QO8vGoVUVmikH0UG9e0RuAXk9Iqq3caMqwRBoOTZHfAlgoKQGylE5zKWRrIbQKKqlIIGsyqoZx5MwJgudP1SNVXG6S/2HqDaV1RN5tDIL0sR4G3ctPu46Vg==; 20:9yCO++Gi85BLIyFzNYoFtpcslabzo5ZNQGgQVaPXH2GXrYqyNA6BTXqHw7ZFfuOvgT3GmpTGZbrxtQZHVaipLlYezzUjUZKDiHCeHlnR//zDDvFSiBlpVYQmKIhdoDNNdCzZWh3pLc3R7GisIaSeDvo0jgR3NWCxYvZHu7W/Tmw=
x-ms-office365-filtering-correlation-id: 6b4551e3-71eb-4050-9ff1-08d477b80387
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:AM3PR07MB1138; 
x-microsoft-antispam-prvs: <AM3PR07MB11384E2F6622D4A81855EA5BD6340@AM3PR07MB1138.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006075)(93001075)(6041248)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(20161123560025)(20161123564025)(20161123555025)(20161123562025)(6072148); SRVR:AM3PR07MB1138; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1138; 
x-forefront-prvs: 02622CEF0A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39410400002)(39450400003)(39850400002)(39400400002)(39840400002)(24454002)(54906002)(7736002)(57306001)(81166006)(83716003)(189998001)(42882006)(99286003)(6916009)(2950100002)(8936002)(110136004)(38730400002)(305945005)(3660700001)(4326008)(25786009)(2906002)(36756003)(6436002)(53546009)(6306002)(66066001)(2900100001)(82746002)(74482002)(3280700002)(229853002)(33656002)(39060400002)(6116002)(3846002)(6512007)(50226002)(5660300001)(102836003)(6486002)(86362001)(8676002)(6246003)(53936002)(230783001)(5250100002)(76176999)(93886004)(6506006)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1138; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <B41C0A78AD3F7F48A3CA4107C7846B02@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2017 21:59:18.2052 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1138
X-MC-Unique: m-SicZteMcqoQXph4Ge7Zw-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i2OySPVVp3bsJy1JX9BKHOIUxLI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 21:59:30 -0000

PiBPbiAzMCBNYXIgMjAxNywgYXQgMjI6NTAsIEJyaWFuIEUgQ2FycGVudGVyIDxicmlhbi5lLmNh
cnBlbnRlckBnbWFpbC5jb20+IHdyb3RlOg0KPiANCj4gT24gMzEvMDMvMjAxNyAxMDoxMywgUm9i
ZXJ0IFJhc3p1ayB3cm90ZToNCj4+IFdoYXQncyB3cm9uZyBvciB3aGF0IGlzIG1pc3NpbmcgaW4N
Cj4+IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1y
b3V0aW5nLWhlYWRlci0wNQ0KPj4gDQo+PiA/DQo+IA0KPiBPbmNlIHdlIGdldCAyNDYwYmlzIG91
dCBvZiB0aGUgZG9vciwgd2Ugc2hvdWxkIHNlcmlvdXNseSB0YWNrbGUgdGhhdCBxdWVzdGlvbi4N
Cj4gSG9uZXN0bHkgaXQncyBnb2luZyB0byBiZSBlYXNpZXIgdGhlbi4gSSBwZXJoYXBzIGRpc2Fn
cmVlIHdpdGggT2xlIHdoZXRoZXIgd2UNCj4gbmVlZCBhbiBVcGRhdGVzOiAyNDYwYmlzIGJ1dCB0
aGF0IGRlcGVuZHMgb24gdGhlIGRldGFpbHMuDQoNCkFncmVlZCAob24gYm90aCBwb2ludHMpLiBB
bmQgSSB0aGluayB5b3XigJlsbCBmaW5kIG1hbnkgd2hvIHdhbnQgMjQ2MGJpcyB0byBzaGlwIGFz
IHByb3Bvc2VkIGJ5IG91ciBBRCB3aWxsIGFsc28gYmUgdmVyeSB3aWxsaW5nIHRvIGhlbHAgd29y
ayB0aHJvdWdoIHRoZSBpc3N1ZXMuIA0KDQpUaW0NCg0KPiAgICBCcmlhbg0KPiANCj4+IA0KPj4g
T24gTWFyIDMwLCAyMDE3IDE2OjA1LCA8b3Ryb2FuQGVtcGxveWVlcy5vcmc+IHdyb3RlOg0KPj4g
DQo+Pj4gUm9iZXJ0LA0KPj4+IA0KPj4+PiBDb3JyZWN0IG1lIGlmIEkgYW0gbWlzc2luZyBzb21l
dGluZyBidXQgdGhlIGVudGlyZSBkZWJhdGUgaXMgbm90IGFib3V0DQo+Pj4gZGVzY3JpYmluZyBv
ciBub3QgaGVhZGVyIGluc2VydGlvbi4NCj4+Pj4gDQo+Pj4+IEkgYW0gdW5kZXIgYXNzdW1wdGlv
biB0aGF0IG9yaWdpbmF0aW5nIGhvc3RzIHN0aWxsIGNhbiBsZWdhbGx5IGluc2VydCBpdC4NCj4+
Pj4gDQo+Pj4+IEl0IGlzIGFsbCBhYm91dCB0byBtb2RpZnkgRUggaW4gZmxpZ2h0IC0gcmlnaHQg
PyBNb3Jlb3ZlciBjb25jZXJucw0KPj4+IHJhaXNlZCBhcmUgYWJvdXQgc2lkZSBlZmZlY3RzIG9m
IGl0IGxpa2UgTVRVIC4uIG5vdCBsYWNrIG9mIGluc3RydWN0aW9ucyBvbg0KPj4+IGhvdyB0byBp
bnNlcnQsIG1vZGlmeSBvciByZW1vdmUgRUggZWxlbWVudHMuDQo+Pj4+IA0KPj4+PiBTbyB3aGF0
IGV4YWN0bHkgYXJlIHlvdSBleHBlY3RpbmcgV0cgdG8gZGVsaXZlciBhcyBuZXh0IHN0ZXAgaWYg
MjQ2MGJpcw0KPj4+IGdvZXMgZndkID8gSXMgZGV0ZWN0aW5nIHRoZSBtYXggTVRVIG9uIGVuZCB0
byBlbmQgcGF0aCBldmVuIGluIDZtYW4ncw0KPj4+IGNoYXJ0ZXIgPw0KPj4+IA0KPj4+IFlvdSBj
YW4gd3JpdGUgYSBuZXcgcHJvdG9jb2wgc3BlY2lmaWNhdGlvbiBpbmRlcGVuZGVudGx5IG9mIDI0
NjBiaXMgdGhhdA0KPj4+IGRvZXMgd2hhdGV2ZXIgaXQgaGFzIHRvIGRvLCBhbmQgdGhlbiB3ZSBj
YW4gYXJndWUgb3ZlciB0aGF0IGRvY3VtZW50IG9uIGl0cw0KPj4+IG93biBtZXJpdHMuDQo+Pj4g
DQo+Pj4gQ2hlZXJzLA0KPj4+IE9sZQ0KPj4+IA0KPj4gDQo+IA0KPiAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBJ
RVRGIElQdjYgd29ya2luZyBncm91cCBtYWlsaW5nIGxpc3QNCj4gaXB2NkBpZXRmLm9yZw0KPiBB
ZG1pbmlzdHJhdGl2ZSBSZXF1ZXN0czogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9pcHY2DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IA0KDQo=


From nobody Thu Mar 30 15:14:14 2017
Return-Path: <furry13@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 3BD2F1295E7; Thu, 30 Mar 2017 15:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x_IsCxudx0mC; Thu, 30 Mar 2017 15:14:05 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79B7A12426E; Thu, 30 Mar 2017 15:14:05 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id y18so2823125itc.0; Thu, 30 Mar 2017 15:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=xfRV0uNVwkm5pRQtWVuMEUfHqVsUdlRyijKL5Hc1Tpc=; b=mxy3f9V4DCMOycfXjjH2A2qd7e2Bhi4tbFdCBO/oq0tuFiNs4quSweD7TLupsN9ZOR VPVqIO5lYozHvm01lA5L8izBNTbN9yEjDwEaveGAJdZnZhnlXFFnAIUL42UTMmmgW754 DCSW4ryK2o2p910qhLxz6GAusOu2qijTRmd/xWdleBM47m6ex0XwApIXs54EQ4w2l4Vb gny/F/YyBr17e5SXRLAsEAmgsn+5qxQIfIodwAuYZozjyfpujMgqUypeB0/eaOtT99Pq e56f60TPkt1VP2GDCYOHEtDabLE1H2FDff2KqIFBcUZ4j6rtjskb/p0/qPXwBBTptXVS pfEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=xfRV0uNVwkm5pRQtWVuMEUfHqVsUdlRyijKL5Hc1Tpc=; b=pSyyj9HXIIznRu6reg2h5u0nHaPYZtrM6AELzQBMWXeJYmxr9RpFthqO1v7UKQGnoQ v49Zmkwg3sz5lEm49q6nJdWmW6I1aelQlr80/GSk/99gHbmhLK410PSl2Kb9QGkxECsi pml+eCl2zaX9vmf6aaM3mwCcQUgIrdWydU7hc+SU1gpQik0lkszTDHuB1aY4xzoYSl/s 71NgUeEa7kYXHohUoLDMpKYSm4r0kcQ4MFWpVisleHQBMAyzSVUgrIPVZnYXrXeDjSux iSqxpkYM7rB93IX7Ybff0bh7UHKHV2TjHXogv2iBZy/PvUU4wy3Qp+Lx2eTOkU6KwBtG emug==
X-Gm-Message-State: AFeK/H17CtTMWQRTjQXatUqgwWD0rksqzHU80HS9VLtg8kmXi0LTqnTtIUk/NH5vOtAONRQafN5iBGd0pQq1eg==
X-Received: by 10.36.48.66 with SMTP id q63mr624614itq.18.1490912044818; Thu, 30 Mar 2017 15:14:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.184.197 with HTTP; Thu, 30 Mar 2017 15:13:44 -0700 (PDT)
In-Reply-To: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com>
From: Jen Linkova <furry13@gmail.com>
Date: Fri, 31 Mar 2017 00:13:44 +0200
Message-ID: <CAFU7BAS4zZ44ZRgmNSHBYvV9iWwRvn1X2Z-_-ncD-=E4mzhp9g@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, 6man WG <ipv6@ietf.org>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M7yaIJSTzXaLlc77OnsDCLbpEMU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 22:14:07 -0000

On Wed, Mar 15, 2017 at 3:47 AM, Suresh Krishnan
<suresh.krishnan@ericsson.com> wrote:
> Thanks to everyone who commented during the IETF Last Call of draft-ietf-=
6man-rfc2460bis-08. The IETF last call discussion for this draft was mainly=
 focused around the text in Section 4 that discusses the handling of extens=
ion headers. The biggest concern raised was that the current text is ambigu=
ous on whether header insertion is allowed on intermediate nodes or not. Th=
ere were some people arguing that an explicit prohibition is not necessary =
as the text is already clear, while others believed that explicitly listing=
 the prohibitions will minimize any misunderstandings in the future. There =
was also a small number of people who wanted to explicitly allow header ins=
ertion and describe how to do it, but this was clearly out of scope for thi=
s draft (but may be in scope for future work in 6man). Overall, no one argu=
ed against the fact that the intent of the text in RFC2460 was to forbid in=
sertion of extension headers on any other node but the source of the packet=
.  The only argument made against adding clarifying text was that the text =
was already clear. Given this, I believe there is consensus to add explicit=
 text about header insertion into the draft before it progresses further. I=
 have discussed this with the editor and the document shepherd and would li=
ke to propose the following text change.
>
> OLD (from -08):
>
>  The insertion of Extension Headers by any node other than the source
>  of the packet causes serious problems.  Two examples include breaking
>  the integrity checks provided by the Authentication Header Integrity
>  [RFC4302], and breaking Path MTU Discovery which can result in ICMP
>  error messages being sent to the source of the packet that did not
>  insert the header, rather than the node that inserted the header.
>
>  One approach to avoid these problems is to encapsulate the packet
>  using another IPv6 header and including the additional extension
>  header after the first IPv6 header, for example, as defined in
>  [RFC2473]
>
>  With one exception, extension headers are not processed by any node
>  along a packet's delivery path, until the packet reaches the node (or
>  each of the set of nodes, in the case of multicast) identified in the
>  Destination Address field of the IPv6 header...
>
> NEW:
>
>  With one exception, extension headers are not examined, processed,
>  inserted, or deleted by any node along a packet's delivery path,
>  until the packet reaches the node (or each of the set of nodes, in
>  the case of multicast) identified in the Destination Address field of
>  the IPv6 header...

I have some concerns with how that sentence AND the following note
comes together:

"  With one exception, extension headers are not examined, processed,
   inserted, or deleted by any node along a packet's delivery path,
   until the packet reaches the node (or each of the set of nodes, in
   the case of multicast) identified in the Destination Address field of
   the IPv6 header.  Note: If an intermediate forwarding node examines
   an extension header for any reason, it must do so in accordance with
   the provisions of [RFC7045].  "

I'm afraid that the lack of the normative language strikes back..
If 'are not examined" is to be interpreted as RFC2119 'MUST NOT',
then the following note conflicts with that statement. 'A node MUST
NOT examine EHs
but if it does it must do it as per RFC7045' - it is extremely controversia=
l.

If ''are not examined" is to be read as RFC2119 'SHOULD NOT' then I
have a very good news for
those who would still like to insert/delete EHs: they can do it  as
long as  they have
"valid reasons in particular circumstances when the particular
behavior is acceptable or even useful, but the full
   implications should be understood and the case carefully weighed
   before implementing any behavior described with this label.".
But from today's presentation I've got an impression that the
intention of this text was actually to prohibit EH insertion
(the sildes say 'no one argued against the fact that the intent of the
text in RFC2460
was to forbid insertion of extension headers on any other node but the sour=
ce
of the packet.).

So to summarize: the proposed text either explicitly prohibits the
examination (and then it contradicts the next sentence and we need to
do smth with the note and RFC7045) OR it allows EH insertion - it
depends how the text is interpreted.

--=20
SY, Jen Linkova aka Furry


From nobody Fri Mar 31 00:10:50 2017
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 62554127342 for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 00:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.396
X-Spam-Level: 
X-Spam-Status: No, score=-5.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q34aUAwZuF_o for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 00:10:44 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FD7F1205D3 for <ietf@ietf.org>; Fri, 31 Mar 2017 00:10:44 -0700 (PDT)
Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2V4pHmM046476 for <ietf@ietf.org>; Fri, 31 Mar 2017 00:53:20 -0400
Received: from e11.ny.us.ibm.com (e11.ny.us.ibm.com [129.33.205.201]) by mx0a-001b2d01.pphosted.com with ESMTP id 29h9ycp91d-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 31 Mar 2017 00:53:19 -0400
Received: from localhost by e11.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, 31 Mar 2017 00:53:17 -0400
Received: from b01cxnp23033.gho.pok.ibm.com (9.57.198.28) by e11.ny.us.ibm.com (146.89.104.198) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 31 Mar 2017 00:53:15 -0400
Received: from b01ledav005.gho.pok.ibm.com (b01ledav005.gho.pok.ibm.com [9.57.199.110]) by b01cxnp23033.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v2V4rHq537617828 for <ietf@ietf.org>; Fri, 31 Mar 2017 04:53:17 GMT
Received: from b01ledav005.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 13A3BAE04B for <ietf@ietf.org>; Fri, 31 Mar 2017 00:53:04 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav005.gho.pok.ibm.com (Postfix) with ESMTPS id E90E5AE03B for <ietf@ietf.org>; Fri, 31 Mar 2017 00:53:03 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v2V4rD4Y023465 for <ietf@ietf.org>; Fri, 31 Mar 2017 00:53:13 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v2V4rCfs023448 for ietf@ietf.org; Fri, 31 Mar 2017 00:53:12 -0400
From: narten@us.ibm.com
Date: Fri, 31 Mar 2017 00:53:12 -0400
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-TM-AS-GCONF: 00
x-cbid: 17033104-2213-0000-0000-0000017AE175
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006875; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000206; SDB=6.00841041; UDB=6.00414058; IPR=6.00619105;  BA=6.00005248; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014869; XFM=3.00000013; UTC=2017-03-31 04:53:16
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17033104-2214-0000-0000-0000551BC034
Message-Id: <201703310453.v2V4rCfs023448@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-31_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703310043
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ILmxa_VL2Lf_NfQP3GjnnN68Qr4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 07:10:47 -0000

Total of 127 messages in the last 7 days.
 
script run at: Fri Mar 31 00:53:07 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.72% |    6 |  7.57% |    99712 | robert@raszuk.net
  6.30% |    8 |  4.92% |    64836 | touch@isi.edu
  5.51% |    7 |  5.41% |    71238 | brian.e.carpenter@gmail.com
  5.51% |    7 |  4.57% |    60230 | nico@cryptonector.com
  4.72% |    6 |  3.39% |    44676 | dhc@dcrocker.net
  3.94% |    5 |  3.93% |    51800 | presnick@qti.qualcomm.com
  3.15% |    4 |  4.04% |    53144 | ynir.ietf@gmail.com
  3.15% |    4 |  2.12% |    27878 | sob@sobco.com
  3.15% |    4 |  1.91% |    25179 | chair@ietf.org
  1.57% |    2 |  3.24% |    42698 | glenn.deen@nbcuni.com
  2.36% |    3 |  2.16% |    28408 | john-ietf@jck.com
  2.36% |    3 |  1.96% |    25808 | paf@frobbit.se
  1.57% |    2 |  2.70% |    35594 | bob.hinden@gmail.com
  1.57% |    2 |  2.54% |    33419 | mackermann@bcbsm.com
  2.36% |    3 |  1.74% |    22938 | mcr+ietf@sandelman.ca
  2.36% |    3 |  1.74% |    22911 | johnl@taugh.com
  2.36% |    3 |  1.71% |    22480 | jari.arkko@piuha.net
  1.57% |    2 |  2.39% |    31426 | suresh.krishnan@ericsson.com
  1.57% |    2 |  2.17% |    28560 | gorry@erg.abdn.ac.uk
  1.57% |    2 |  2.07% |    27294 | tim.chown@jisc.ac.uk
  1.57% |    2 |  1.98% |    26014 | warren@kumari.net
  1.57% |    2 |  1.77% |    23351 | tjc@ecs.soton.ac.uk
  1.57% |    2 |  1.71% |    22556 | sandy@tislabs.com
  1.57% |    2 |  1.64% |    21598 | mark@townsley.net
  1.57% |    2 |  1.54% |    20236 | john_leddy@comcast.com
  1.57% |    2 |  1.49% |    19634 | otroan@employees.org
  1.57% |    2 |  1.42% |    18759 | cpignata@cisco.com
  1.57% |    2 |  1.31% |    17289 | michael.cameron@ericsson.com
  0.79% |    1 |  1.78% |    23416 | lucas.pardue@bbc.co.uk
  1.57% |    2 |  0.99% |    13031 | randy@psg.com
  0.79% |    1 |  1.17% |    15400 | markzzzsmith@gmail.com
  0.79% |    1 |  1.16% |    15339 | iab-chair@iab.org
  0.79% |    1 |  1.09% |    14403 | agmalis@gmail.com
  0.79% |    1 |  1.01% |    13332 | ggm@algebras.org
  0.79% |    1 |  0.92% |    12054 | matthew@kerwin.net.au
  0.79% |    1 |  0.91% |    12010 | furry13@gmail.com
  0.79% |    1 |  0.86% |    11331 | aaron.falk@gmail.com
  0.79% |    1 |  0.86% |    11261 | angela.y@email.com
  0.79% |    1 |  0.85% |    11131 | tobias.gondrom@gondrom.org
  0.79% |    1 |  0.82% |    10815 | narten@us.ibm.com
  0.79% |    1 |  0.78% |    10235 | christer.holmberg@ericsson.com
  0.79% |    1 |  0.76% |    10072 | michael.breuer@ilsf.de
  0.79% |    1 |  0.75% |     9904 | nomcom-chair-2016@ietf.org
  0.79% |    1 |  0.75% |     9874 | jefftant.ietf@gmail.com
  0.79% |    1 |  0.75% |     9860 | jinmei@wide.ad.jp
  0.79% |    1 |  0.71% |     9297 | akatlas@gmail.com
  0.79% |    1 |  0.68% |     9003 | julian.reschke@gmx.de
  0.79% |    1 |  0.67% |     8783 | willi.uebelherr@riseup.net
  0.79% |    1 |  0.63% |     8281 | ietf-secretariat@ietf.org
  0.79% |    1 |  0.62% |     8132 | fujiwara@jprs.co.jp
  0.79% |    1 |  0.59% |     7785 | barryleiba@computer.org
  0.79% |    1 |  0.59% |     7745 | adrian@olddog.co.uk
  0.79% |    1 |  0.58% |     7617 | ajs@anvilwalrusden.com
  0.79% |    1 |  0.57% |     7444 | dot@dotat.at
  0.79% |    1 |  0.55% |     7265 | harald@alvestrand.no
  0.79% |    1 |  0.55% |     7230 | j.schoenwaelder@jacobs-university.de
  0.79% |    1 |  0.54% |     7160 | iesg@ietf.org
  0.79% |    1 |  0.54% |     7124 | fgont@si6networks.com
  0.79% |    1 |  0.42% |     5530 | yaronf.ietf@gmail.com
  0.79% |    1 |  0.42% |     5511 | jouni.nospam@gmail.com
--------+------+--------+----------+------------------------
100.00% |  127 |100.00% |  1317041 | Total


From nobody Fri Mar 31 06:35:14 2017
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C51512954A; Thu, 30 Mar 2017 05:34:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Nominations sought: Jonathan B. Postel Service Award 2017
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149087724950.15432.6307168047926456030.idtracker@ietfa.amsl.com>
Date: Thu, 30 Mar 2017 05:34:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wf7OzFlLLIHRNkUmQvmQ3ndE1T8>
X-Mailman-Approved-At: Fri, 31 Mar 2017 06:35:14 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Mar 2017 12:34:09 -0000

Greetings on behalf of the Internet Society,

We are pleased to announce that candidate nominations for the 2017
Jonathan B. Postel Service Award are now open.

This prestigious annual award is presented to an individual or
organization that has made outstanding contributions in service to
the data communications community.

The signature crystal globe and a USD 20,000 prize will be presented
at the 99th Internet Engineering Task Force (IETF) meeting in
Prague, Czech Republic (16 -21 July 2017) to the chosen candidate.

Nominations are encouraged for individuals or teams of individuals
from across the data communications industry around the world,
either by self-nomination or by third party.

Please submit your nominations using this web form and do not
hesitate to share this information with your networks:
https://www.internetsociety.org/form/postel-nominations

The deadline for nominations is 3 May 2017.

More About the Award

The Jonathan B. Postel Service Award was established by the Internet
Society to honor a person who has made outstanding contributions in
service to the data communications community.

The award is focused on sustained and substantial technical
contributions, service to the community, and leadership. With
respect to leadership, the award committee places particular
emphasis on candidates who have supported and enabled others in
addition to their own specific actions.

The award is named for Dr. Jonathan B. Postel to recognize and
commemorate the extraordinary stewardship exercised by Jon Postel
over the course of a thirty-year career in networking.

Jon Postel served as the editor of the RFC series of notes from its
inception in 1969 until 1998. He also served as the ARPANET “numbers
Czar” and Internet Assigned Numbers Authority over the same period
of time. He was a founding member of the Internet Architecture (nee
Activities) Board and the first individual member of the Internet
Society, which he also served as a Trustee.

Find out more on the award, nomination procedures, and online
submission forms:
http://www.internetsociety.org/what-we-do/grants-and-awards/awards/
postel-service-award

Nominate someone here:
http://www.internetsociety.org/what-we-do/grants-and-awards/awards/
postel-service-award/procedures

For any questions please contact postel@isoc.org

Best Regards,

The Internet Society Team


From nobody Fri Mar 31 06:46:12 2017
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DA03712984A; Fri, 31 Mar 2017 06:46:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jouni.nospam@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-ippm-6man-pdm-option.all@ietf.org, ietf@ietf.org, ippm@ietf.org
Subject: Genart telechat review of draft-ietf-ippm-6man-pdm-option-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149096796486.21620.15409836640558971168@ietfa.amsl.com>
Date: Fri, 31 Mar 2017 06:46:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mlsc-PfQ-LN9swSLLWUyvTv0sx0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 13:46:05 -0000

Reviewer: Jouni Korhonen
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ippm-6man-pdm-option-??
Reviewer: Jouni Korhonen
Review Date: 2017-03-31
IETF LC End Date: 2016-09-28
IESG Telechat date: 2017-04-13

Summary: Ready for publication. I did review earlier version of the
document and the comments I raised back them have now been addressed
to an adequate level. 

Major issues: None.

Minor issues: None.

Nits/editorial comments:  None.



From nobody Fri Mar 31 07:11:50 2017
Return-Path: <rraszuk@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 2ABB51294C4; Fri, 31 Mar 2017 07:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3vyqiAFLmcsP; Fri, 31 Mar 2017 07:11:47 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C9C1120326; Fri, 31 Mar 2017 07:11:47 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id z13so40406491iof.2; Fri, 31 Mar 2017 07:11:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=isEinDZ38WgcjmpNWTQ4PfYWjZqcWehhG/DenmXpiAo=; b=OGSIjlCAx/OjgRJXpISH1EpwT//PF1SfwRtQ6U97zd0C/nVcpBQNyrgehGVO5kdO83 CBePvRHHpeYZGCcjgBnj6gwy3cQ9SXZvrRWYTDGLtBGN37F6aFL9idZOfvVgE5OOFm2L aZxkimlTIAe1UqbXvkE+gNm0D0Fxq65cw89UbjHhl0iSjqpsUHOLKCcwDYUHg8Oe3c2H r/Eou2WVdFiAO48h2VJPw+DPzYl4RVHxtbCxNrJTV4J5bSFu5uFCEDkXidJahE9plnpN 8+B7e7gY40DuIUnQ+eW/PdhrPtV3iZlJonWIwFt/7fIB1tXGtmaNoM+7DGmBNXJJuI6k R9CA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=isEinDZ38WgcjmpNWTQ4PfYWjZqcWehhG/DenmXpiAo=; b=VFvpdFhyUOwZ4kqni8Ol4QRfJttVqxRXEA7ubO4SXhLHPibRtyFSE3RBGRilawCJYa 2LRP6knSUUE69LzPre7vvth3mxXOKUgHilCb7b+95VaJB/FBlsZmcPrZvFq3cDT49/Kb jMk5ZTvfMRPn7z4O8QGWcxaE1eydF/yCqVGdnjpNHEDX92chYYbnDVjbeyG8OU888puT ynWxSUQJ/t1ujZnzepqYJHUWT+6Ue8gYimzwKUOeWy9sNwk8du7BV59i/baj0UHD7FBN pOvSi/tIGK3ZEU9OpT9zT0zTgPskrW5zi8r6Xka+kPH7wu9Mk2O8Lt2agkRjHET3Ofxa Opyw==
X-Gm-Message-State: AFeK/H00BZAn8rSQFiGn9OFP+JFQGn5d6cNs41R1lgjDY2TJErvblWIJ5zM7MjpX6x4aB4eUMKQlqMArGON1vQ==
X-Received: by 10.107.7.29 with SMTP id 29mr3384195ioh.57.1490969506524; Fri, 31 Mar 2017 07:11:46 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Fri, 31 Mar 2017 07:11:45 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Fri, 31 Mar 2017 07:11:45 -0700 (PDT)
In-Reply-To: <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 31 Mar 2017 09:11:45 -0500
X-Google-Sender-Auth: cEXM4wMcBvEXKRslhp9ltl33Am4
Message-ID: <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, otroan@employees.org,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ea6f0ced7e1054c0763df
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UyWDlsFzeFDaRP59R2ppJowJDfM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 14:11:49 -0000

--001a113ea6f0ced7e1054c0763df
Content-Type: text/plain; charset=UTF-8

I do not understand how 2460bis makes it "easier" if proposed change to the
text directly tries to prohibit what is described in a document already
long time back accepted as a 6man working group draft.

That's to the best of my memory an IETF precedent.

Cheers,
R.

On Mar 30, 2017 16:50, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

On 31/03/2017 10:13, Robert Raszuk wrote:
> What's wrong or what is missing in
> https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-05
>
> ?

Once we get 2460bis out of the door, we should seriously tackle that
question.
Honestly it's going to be easier then. I perhaps disagree with Ole whether
we
need an Updates: 2460bis but that depends on the details.

    Brian

--001a113ea6f0ced7e1054c0763df
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">I do not understand how 2460bis makes it &quot;easier&quo=
t; if proposed change to the text directly tries to prohibit what is descri=
bed in a document already long time back accepted as a 6man working group d=
raft.<div dir=3D"auto"><br></div><div dir=3D"auto">That&#39;s to the best o=
f my memory an IETF precedent.</div><div dir=3D"auto"><br></div><div dir=3D=
"auto">Cheers,</div><div dir=3D"auto">R.<div class=3D"gmail_extra" dir=3D"a=
uto"><br><div class=3D"gmail_quote">On Mar 30, 2017 16:50, &quot;Brian E Ca=
rpenter&quot; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.ca=
rpenter@gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=
=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div class=3D"quoted-text">On 31/03/2017 10:13, Robert Raszuk wrote=
:<br>
&gt; What&#39;s wrong or what is missing in<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-6man-segment-routing=
-header-05" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/htm=
l/<wbr>draft-ietf-6man-segment-<wbr>routing-header-05</a><br>
&gt;<br>
&gt; ?<br>
<br>
</div>Once we get 2460bis out of the door, we should seriously tackle that =
question.<br>
Honestly it&#39;s going to be easier then. I perhaps disagree with Ole whet=
her we<br>
need an Updates: 2460bis but that depends on the details.<br>
<font color=3D"#888888"><br>
=C2=A0 =C2=A0 Brian</font></blockquote></div><br></div></div></div>

--001a113ea6f0ced7e1054c0763df--


From nobody Fri Mar 31 07:42:29 2017
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 4B751129962; Fri, 31 Mar 2017 07:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IRDG0lOGc8qq; Fri, 31 Mar 2017 07:42:26 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71A2F129961; Fri, 31 Mar 2017 07:42:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3199; q=dns/txt; s=iport; t=1490971345; x=1492180945; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=EjXG5EVnG0/dNm6/0swbD7IjZ5L1RZDP4cSpjFPR0f8=; b=Tc/wrvnmUYAEbvw6ZAgR+eO0jmiX4XQUKaX9fpyuhAVByJGfoqhQlcWs DykIGMu5f8SS5sLj4VZJQQXaoBlxTXp6rcFUcS6KqM5sMZ6LEyfQWwZHr KzgtBVGAdVZGLNvg7SnNbNCQUJVMa7/CAugXiqsVqVbAAbUeke3aCqu0V 8=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A5AwARat5Y/4MNJK1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1SFTooSkTYfk0GCD4IOhiICg0Y/GAECAQEBAQEBAWsohRYBBSNJCQE?= =?us-ascii?q?TCxgqAgJXBwwIAQEQiXmtXYImgUeJFAEBAQcBAQEBFQ+IUwiCYoQ3AQGDIYJfB?= =?us-ascii?q?YsEhWKMBIN8ggyMSIpfhluTcR84PkclFggYFYc4IodTDxcDghQBAQE?=
X-IronPort-AV: E=Sophos;i="5.36,252,1486425600";  d="asc'?scan'208";a="225042488"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 31 Mar 2017 14:42:24 +0000
Received: from [10.86.247.170] ([10.86.247.170]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v2VEgNAa030592; Fri, 31 Mar 2017 14:42:24 GMT
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org, venue-selection@ietf.org
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
Date: Fri, 31 Mar 2017 09:42:23 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="f7bwGIEoqjncKqhTkCW411DXQhIDUx9MF"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wSJLBi3QOzOzvyV8BCnlq09WLVI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 14:42:28 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--f7bwGIEoqjncKqhTkCW411DXQhIDUx9MF
Content-Type: multipart/mixed; boundary="EXciw8canbUEgqbaW16vH6pcM8et7JbWV";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: ietf@ietf.org, venue-selection@ietf.org
Message-ID: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
In-Reply-To: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>

--EXciw8canbUEgqbaW16vH6pcM8et7JbWV
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi,


On 3/31/17 9:18 AM, IAOC Chair wrote:
> The IAOC remains committed to soliciting input on future IETF meeting l=
ocations. With this mail, we are soliciting input on some potential IETF =
locations, including one where we have met before, but for which conditio=
ns may have changed.
>
> Specifically, we seek community input on reasons we could not have a su=
ccessful meeting in any of the following cities, or of any limits to atte=
ndee accessibility or inclusiveness that should be considered:
>
> Ottawa
> San Francisco
> Austin, TX
> Barcelona
> Boston
> Busan
> Calgary
> Denver
> Helsinki
> Houston
> New Orleans
> Osaka
> Philadelphia
> Washington DC

I apologize for not following the form in the subject line, but in my
view, there is sufficient uncertainty about ability of people to gain
entry to the United States that we should not be planning meetings in
this country.  Over the last few weeks we have seen people with valid
visas turned away at the border or otherwise detained, sometimes for
days, without any cause being given.  We have people in our community
who could not get a visa in time for the Chicago meeting.  With the vote
by the European Parliament requiring Americans to have visas to enter
into EU countries, it is likely we will see a further degradation of the
situation, such as suspension of the VWP, thus bringing further
uncertainty to new and more common classes of individuals.

That translates into concerns over San Francisco, Austin, Boston,
Denver, Houston, New Orleans, Philadelphia, and Washington DC.  I would
prefer, therefore, as alternatives, Calgary, Ottawa, Toronto, Montreal,
Quebec City, and Vancouver.

Eliot



--EXciw8canbUEgqbaW16vH6pcM8et7JbWV--

--f7bwGIEoqjncKqhTkCW411DXQhIDUx9MF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJY3mrQAAoJEIe2a0bZ0nozIOwH/iyEcGoyjC+QpOLm8LS6FahJ
BMK8PqK2taJPp+2nVS51GKpEbnzyjYI6bF32IGVSCpRVw/bD0u2KExVf0DxBsZNf
dv1GEWo+e59XjD1F/wonKE8zwawfSsxVDKr57YFt/b749Cc0IDI5cfSuhD6wmf4l
71BY2VZqXZPNQVJFpZKj2yoEJE0VsFQVjDHiy4AWCoDAKBv5M/LNEQoWgZhTWMEs
kj2QQmKXGblPkNeFYfogwNj9sC+xH0MiQIFPwZC/nxLKMTjRed+33QepDBDTQO5M
tJllp5u5/+3D6/4vHk6F+HII7MN9iXoKODtXSHaTk0FF1dzA7o2azwBPy2JJVjw=
=z/qm
-----END PGP SIGNATURE-----

--f7bwGIEoqjncKqhTkCW411DXQhIDUx9MF--


From nobody Fri Mar 31 08:23:33 2017
Return-Path: <laurent.ciavaglia@nokia-bell-labs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE43126C26 for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 08:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.696
X-Spam-Level: 
X-Spam-Status: No, score=-4.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q6sLKhlaODiK for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 08:23:29 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40135.outbound.protection.outlook.com [40.107.4.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B9E91294E8 for <ietf@ietf.org>; Fri, 31 Mar 2017 08:23:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=lWPp2HFrzbN9Dp8hB+xcN6Aa+7I0714k2/cKSlu+Et4=; b=QTDGsQ7+62rh5TQwwBVaIEdJRvhbfm4GGZ3B8O+0FE83eMoEO/PZgBD0rWHzPYOs7jzrBSZDjNIL9cKN4NMh+7pjyQm5VyV4XcoIyKUkRrjp3tcWN4jSa0iqWRt7wT1Fj5qqTVqfIhAufzqAYZlqeQ2aPqSDcZpwXV2nxVJJ5xo=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=laurent.ciavaglia@nokia-bell-labs.com; 
Received: from [31.133.129.77] (31.133.129.77) by AM4PR0701MB2196.eurprd07.prod.outlook.com (2603:10a6:200:45::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1005.2; Fri, 31 Mar 2017 15:23:25 +0000
Subject: Re: IAOC requesting input on (potential) meeting cities
To: <ietf@ietf.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
From: Laurent Ciavaglia <Laurent.Ciavaglia@nokia-bell-labs.com>
Organization: Nokia Bell Labs
Message-ID: <e169ca7b-851f-2469-3659-d708a7807cd0@nokia-bell-labs.com>
Date: Fri, 31 Mar 2017 17:23:14 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
Content-Type: multipart/alternative; boundary="------------DEDFD22CB50CE80D86C02141"
X-Originating-IP: [31.133.129.77]
X-ClientProxiedBy: MWHPR1301CA0018.namprd13.prod.outlook.com (2603:10b6:301:29::31) To AM4PR0701MB2196.eurprd07.prod.outlook.com (2603:10a6:200:45::7)
X-MS-Office365-Filtering-Correlation-Id: 27cc36a7-9f76-4fbd-061a-08d47849e045
X-MS-Office365-Filtering-HT: Tenant
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081)(201703131423075)(201703031133081); SRVR:AM4PR0701MB2196; 
X-Microsoft-Exchange-Diagnostics: 1; AM4PR0701MB2196; 3:4zfR2SmtLdAlz/jRuM8yyshpzOkTrXCHbM5ghZeKhC8rtyCBiuJDawzy+wjk2AwXSyItxf7ke4uQAWMC//JruR9sLJvj3X2gCfldZWiCbqcQ18WXGHe9QqcAWt3Rz58Am3UjPEJ5+MCygtvILsW4w/jtW7giGS9VkAPgyLw+mo8wcUfxFNCYIdeB2bLkP8DoOTr5QvA4bmaFUq2QYrKA7XuPvtFSGXmY1oc8tX3dFffvUrYl7g1AH7n9Q3/LzVt02aOZAt+EsCFjL2Iyl0Ml9jb6I2RKKHOHMQd3Uz8o4h6BkxpWRw/Qj/OIK3a2wPvpUTsLFYNFUv6TWBopVVusyb4pTmbxTP+fdmYzeIaugrk=; 25:6MlzBjjiwhELrbM2DrCh6Nbhm3BtwvEUhxZEcSTdYG9UqdbIgymqXFoVkowAGBVh2YOk/GP7NxCOOKFIswzuZcQkr3GWB7jhhzuTwvuh5quv5eTsVPATMZTNwywbTA2/fNX1UlJO6YLJ0uslo1bj3J+3lVCZhWOZrCErC5BMh6NzlrO9yll+CmDkHCGnIaV8qafk5d7ZCR7DWOWDL13cDZArUaNkTxy2qc1ySI7hhJoxQSk0xGtqjUFU6J6lxGST9bML6+Wj6bSrYQ1SIj3GMKkEQh1BcssiK1Tc5I6IirfHvwzbldFkmYATF7GP/IXzFH31ooxb98fXReEcJA9uuf0mptWlbLOB0QQefBrScZlPX0/Gb2308zPUB1C2g0z1F+HzqKD0rJ68GWsmkKwOO1042tBCQT7mJFV0aNNfrYnTFElOgKYWqHNou41+pNu/sWEbv/6XBnRz6OiaF7/ULw==
X-Microsoft-Exchange-Diagnostics: 1; AM4PR0701MB2196; 31:OoYk8l4xQ3YSezsDqMilbVgGXv/1KStX1rNwBWck+EOPhVnyx6ROZHZUruezYlH9wIqai8heEY91hb5OqHpn6Myju9k3MJOAOVksfUT0t2wK16eLazI27qMfuqKMHnzeLKjX1dqN6QdwSTDB+pydJ3m9tO5TT5xnzdpcNUNrz+ZF/BILU261AJJPfXKjATquRySXu9P7JUGfqF5+ribw5uFuQ6Mz6r6m372wNscTJINWLkVSbt0luD64/KJn/Rgp9wRudjTRCHDzbTlyFtj3txuC8OPMYwnG0bKf5T4258E=; 20:6gvxiT4ASZ9mIrhL1wZP6i0c0EiStaOV4DmSXYs238SgAl/fbg5CIF/BJD3wYLHFOh5LKuSKxDCj3img3HjBG6YTWQhKEgPnsogD71fYzpER90euDdpdoZQATZPWSQ8GYOy5lDuFFOJ4oppGnsLChdHRO5DPDtfR82u7FGUpTpgwC0TbJyiI04XYRJBdM5389YOCoHtAtl/3KpLq1BgDQZRv4rtQGgeA4r62RnF/LBkTOHb5c+mlLn76a5vP3r79xis3pbTK1/a+cuDvUycDQ8HTvsY2DCPlZoI1lhtQuU7TRlnjIP8ZWCBzWutez5Pggld7cbdONlWt0zginJQ/m/YGaQeu6gm0c+2MqOKuJ2polsphlMgdynT0Xx0IeR0mtkdjfzoiGachrAt3swRdmBYoCRy0HYA1LT/orM4XX+z5jezB8scj/yh7hjrU/3xlNf2rzB14qETtP8Vi5yUtW9DqpuD2qJOFdo1T/kdz/+v/HBSx0V3KIRHLxifvEQdz
X-Microsoft-Antispam-PRVS: <AM4PR0701MB21963F1888016683BD989238E8370@AM4PR0701MB2196.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(95692535739014)(81160342030619);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123560025)(20161123562025)(6072148); SRVR:AM4PR0701MB2196; BCL:0; PCL:0; RULEID:; SRVR:AM4PR0701MB2196; 
X-Microsoft-Exchange-Diagnostics: 1; AM4PR0701MB2196; 4:r4r9T7H14RliZ4Wy+i6MfiEmCl7vlQm946YhoAmb7yEw4EVQEJ7DLtKd0NYDI2XU/dB6VBe+d83+GUbU4PTbddW4wVUjmFbtTC8vTvc/JS8IE4rlONizUt1KoAAq//UNn+T6sd45ZNTsUpPTMlnqX8g8aAiExPODshst/b/q/nM2ghYRgmCwmUYtozwEnO5PbZm01yajsIbuv1Nh7l+F3SQAHL9wVN2ASUQ9zxCsnlC9X+ww6/w/vkqN8EMVw3oe1nDdoK+EpoM7HZ7KUWPGwJ6oXr8Mzt8f7z/Lm7aPDZoJ2xqfARt00tx3Zzbv/gQBeG6n3Ci6SXgcWjf8aU7A3/pLF28FqYcXItIPMZ4LR7sWDMwG4cC5IQnQQklV2FWrI1HE5AdeGUroqfCzCNVr9UowVlLUx9bXQ3nAwroqlANm8SN5wOBpcqX+cnbPFBf09KUW4Z8ruhH2PmMUDo6zU8Q0kTsKLK3HA4M5oXuAOWTD8HBFn+xkCXlHThrawoVJd8wTL+eoM5fXChKoDXfjc9qw4bUmEDlzXjo2v2SGS5M4oZLyAUbA9EGsxAbfSSoJXLC7kTYRdWv4dm0q76Gwh4b1qJ94XVdRIb0fl75URN2n/nWcfv3FySzfl6idefXi9xlZUkXqvlZfTJ4ixL/f27SfCtshrGYHrGG5XyMdR1/yj8Ltm2mCcyKZlqgAnxyPLDvpcCpPJB2/rVPAamxK4ut3+oOUdEU57qNZUXY4bZyVXmy9+9nejQ14a+PY783tZKKK4ab6uv9m65i0TsKekD+SeRzJTuAKhO2c5DCnWYVDBKYZhIK0aastlF7tm7Pd
X-Forefront-PRVS: 02638D901B
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6049001)(39850400002)(39400400002)(39410400002)(39450400003)(39860400002)(39840400002)(24454002)(377454003)(6486002)(6246003)(33646002)(8676002)(5660300001)(66066001)(31686004)(4001350100001)(81166006)(512874002)(64126003)(6116002)(38730400002)(65806001)(53936002)(65956001)(42186005)(65826007)(189998001)(3846002)(54896002)(110136004)(53546009)(229853002)(25786009)(270700001)(6916009)(6666003)(83506001)(2950100002)(2351001)(106356001)(2906002)(50986999)(86362001)(76176999)(31696002)(36756003)(84326002)(54356999)(7736002)(90052001)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR0701MB2196; H:[31.133.129.77]; FPR:; SPF:None; MLV:nov; PTR:InfoNoRecords; LANG:en; 
Received-SPF: None (protection.outlook.com: nokia-bell-labs.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; AM4PR0701MB2196; 23:UREjJ2PLk8zONp+FP8kgINiHUL5QJ4tPQDVCqkA?= =?us-ascii?Q?nDqCxuf/18LYwHpTcGjKYDaQmXCuXIIWpbBPIITFTumH+Ew21e9qJawNnpIY?= =?us-ascii?Q?sTHO0FcIagw491G7IRS2Y/8Jw2us+NvVvyDd73XFpZktwkK4ccsnaAydkIkN?= =?us-ascii?Q?fyxjoIxfBT7DTftSSwWvGpyptLCPNC/pOMecvMugieKq0Z52E8TQVucJSWFh?= =?us-ascii?Q?dZXjG7NrqmrWom3G/8w9CdIJk+B5mcqqx/FM76bFsO3altBRTiTWbQ1Hq497?= =?us-ascii?Q?Unm3ICXJi6f+K9RIUmcsq4T27FGX/5LacmGoqSi0ngBBTHLNNPqY2EJDi8bR?= =?us-ascii?Q?MLlyrGCX1a2ZcUgXvyTwtqwgHQpgQh0mO3ZSQisCahzhcJ+mJVKLnXB80ie1?= =?us-ascii?Q?PQbBKf3/rp8Xtse1uZNgZdXkWy7CHb1+sgbwkSKJO0YZ29MXO4MIJs86PisS?= =?us-ascii?Q?VBmHaE0Th49SPLkqYYc4OBqJ4xon3jwj9U73qzK3qE5cijnlxxl3w3Ryf/dB?= =?us-ascii?Q?k3zPDAEZe8EFivEFSbdbqVGRml0h98tPg1DCcrEy9Wozyobo64OUtdhoV5xY?= =?us-ascii?Q?vlQVeYBM+v14dA48CNvciPt8xUk9Gabb6u8yqvk5rw1k4F+pw3XL9SN6ckD5?= =?us-ascii?Q?xn9a3C/HDJYo/mP7jF0u+UclKx0OE3MP+OTtzeaiyfi19Af1QvuocHeGxv5B?= =?us-ascii?Q?IIV6xGjT9a1j9YOLJq8Dge4q1rk+eATuxiaJZ4aJ3kKp2JwnCOb+di/4mBeG?= =?us-ascii?Q?VR8dipSyFuRVFYdWFUAT7iq8XEwgtVfdc1guPRcISHATaEaeQIJR8Z2gKMwz?= =?us-ascii?Q?9YCVkQMEQxj1UNtJht1+T+Ij7bYsHjBMHhyKKiuISKNFhgoI3QCqAhtmn5xD?= =?us-ascii?Q?KU+oQD+R556fiQhmre0fXIFDKPZcK4Z+YlhFt3CZ3nJoJAtyl5anGjDThQBV?= =?us-ascii?Q?4Gb9ZSQMQTBZA13Fy9B4tst6RMEjRWPN4KpC9Yqsy5ifA98iKREWMx8zNiwX?= =?us-ascii?Q?zxEJxOVnrXYrZBntuPMIFEJilmMiOGWNuJvlH7tHbtHRePul4rP4zzXXAVgs?= =?us-ascii?Q?kB1jq16XFEA5mFyBa8RsAqy6sjI24fIVvJiiN3qaBxLYWrhu1YsKO4YVzWMi?= =?us-ascii?Q?xmRojHBMCcZ7X4o+7gA4S1v45NzSZmMpaL+2dcgBZkpvJfwYVOtnmeklBdao?= =?us-ascii?Q?IKAaCKB63xGu379cfyqrzxbZTdVlGyc8lISmH+mwfw2VzlYJuAXK1otMvmeY?= =?us-ascii?Q?f7y7F3S9KnXu67mEvj0ZdngpVeitjW4fC37u1WkW6ZTMVnxjUUyyY/L6sdnG?= =?us-ascii?Q?p2kAsxgO9FvOtqyZB0a9kzTs=3D?=
X-Microsoft-Exchange-Diagnostics: 1; AM4PR0701MB2196; 6:rGZFKS/rSGkkhI/jiXYPthhFNI+LYCFBeOLzIgOus/92V+9HWrlH4L9kGu8CB6EIP3KvFP8VJ2C0SV3Z5sj/qxAbfiAbkokUMWSRN3AeVd4komBkgJ+NK9dcBpN6mJfZLNXmfPbq//tj/kt4+kMMYFSGqsTEsWz9kqdTOXC9+rDilZi7hEh04nn27g+8E/hiIL4LyUxS2oBuOQ3XOZqSdd2V/ME6bpM3wChaObqEYoxWwtY0LxN3rcnjRCAYV6xnLzfFYMvi/c5jv0dlqt8x3vrxxAL3I3ZYOR3FEG8h2bYYJAqlCdLyWvgPoeIVPSEy6+DzFTfdPNnfXl018AyFK5E80jzZ6PmkQlco+pgcnZAi/Kw65KRtpIL3n4QZnGLt0glJTg9/X+ZzZpZq/0V792PLRvxT/+TATA8OToon2Gw=; 5:BbUb3lT94JeLwWrcABqlX8/Ap4Ge/eMYFy0JYXTRsDUWy1WGFynyoYfrVG61AE+qoOf290ZYpQPzJRwQwBPifD5Pryv+8kkxE6hY1oDPgO6wn8JlhtpwBScKY+sBswPTkBOCzSR1VcGPv7OyHGrqHw==; 24:VCq12lG1kcZLh+2iVDSqVFcoZpLs9iGeK996G10WQ7C+L5CcempjbaAZ4z7YMqmeMPLwqRbzEQyY7bCOkCzOmD6exYS37lwUum6Z9OzdCHc=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; AM4PR0701MB2196; 7:fwRuWOA6szOtTSLKT319zyCQPTn2zzet3Np5w5eJ2kcNMOPuOfscmkwoSPDv5zNc7huahfaLjBaxPlA/BB8WwzdU+7czP+8GPGauf6TNspqRIR+4M0TTrG8yzIvyDJyjYbg7wYfViObZ2/AWo3niGd28PpG51ADJyH1sx0utN8fnCX4Ta+L6z1JMTLCk+Zc1fi22dtGuryBkmJN8cRm38u4lTFJMCh5MD/DIuYr0Dar5evPeofdGxZpywRNse8JgBd0OaxW0gs4BRDxiZ8hR6XVBj77IR/9rEBdVUNpaziEQIgyyQM8ozbFe2w3vVoqomMsQXTWoDpKLNhjQ5zs3+g==
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 Mar 2017 15:23:25.0122 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR0701MB2196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BoffmWp18tKXqW1z-0Ii-xGphc4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 15:23:32 -0000

--------------DEDFD22CB50CE80D86C02141
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

Apologies also for not following the requested template, but my 
impression is that US cities are over-represented in the set of proposed 
cities.

Best regards, Laurent.

On 31/03/2017 16:42, Eliot Lear wrote:
> Hi,
>
>
> On 3/31/17 9:18 AM, IAOC Chair wrote:
>> The IAOC remains committed to soliciting input on future IETF meeting locations. With this mail, we are soliciting input on some potential IETF locations, including one where we have met before, but for which conditions may have changed.
>>
>> Specifically, we seek community input on reasons we could not have a successful meeting in any of the following cities, or of any limits to attendee accessibility or inclusiveness that should be considered:
>>
>> Ottawa
>> San Francisco
>> Austin, TX
>> Barcelona
>> Boston
>> Busan
>> Calgary
>> Denver
>> Helsinki
>> Houston
>> New Orleans
>> Osaka
>> Philadelphia
>> Washington DC
> I apologize for not following the form in the subject line, but in my
> view, there is sufficient uncertainty about ability of people to gain
> entry to the United States that we should not be planning meetings in
> this country.  Over the last few weeks we have seen people with valid
> visas turned away at the border or otherwise detained, sometimes for
> days, without any cause being given.  We have people in our community
> who could not get a visa in time for the Chicago meeting.  With the vote
> by the European Parliament requiring Americans to have visas to enter
> into EU countries, it is likely we will see a further degradation of the
> situation, such as suspension of the VWP, thus bringing further
> uncertainty to new and more common classes of individuals.
>
> That translates into concerns over San Francisco, Austin, Boston,
> Denver, Houston, New Orleans, Philadelphia, and Washington DC.  I would
> prefer, therefore, as alternatives, Calgary, Ottawa, Toronto, Montreal,
> Quebec City, and Vancouver.
>
> Eliot
>
>

-- 

Laurent Ciavaglia

Nokia, Bell Labs

+33 160 402 636

route de Villejust - Nozay, France

linkedin.com/in/laurent.ciavaglia


--------------DEDFD22CB50CE80D86C02141
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">
    <tt>Hello,<br>
      <br>
      Apologies also for not following the requested template, but my
      impression is that US cities are over-represented in the set of
      proposed cities.<br>
      <br>
      Best regards, Laurent.<br>
    </tt><br>
    <div class="moz-cite-prefix">On 31/03/2017 16:42, Eliot Lear wrote:<br>
    </div>
    <blockquote
      cite="mid:9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com"
      type="cite">
      <pre wrap="">Hi,


On 3/31/17 9:18 AM, IAOC Chair wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">The IAOC remains committed to soliciting input on future IETF meeting locations. With this mail, we are soliciting input on some potential IETF locations, including one where we have met before, but for which conditions may have changed.

Specifically, we seek community input on reasons we could not have a successful meeting in any of the following cities, or of any limits to attendee accessibility or inclusiveness that should be considered:

Ottawa
San Francisco
Austin, TX
Barcelona
Boston
Busan
Calgary
Denver
Helsinki
Houston
New Orleans
Osaka
Philadelphia
Washington DC
</pre>
      </blockquote>
      <pre wrap="">
I apologize for not following the form in the subject line, but in my
view, there is sufficient uncertainty about ability of people to gain
entry to the United States that we should not be planning meetings in
this country.  Over the last few weeks we have seen people with valid
visas turned away at the border or otherwise detained, sometimes for
days, without any cause being given.  We have people in our community
who could not get a visa in time for the Chicago meeting.  With the vote
by the European Parliament requiring Americans to have visas to enter
into EU countries, it is likely we will see a further degradation of the
situation, such as suspension of the VWP, thus bringing further
uncertainty to new and more common classes of individuals.

That translates into concerns over San Francisco, Austin, Boston,
Denver, Houston, New Orleans, Philadelphia, and Washington DC.  I would
prefer, therefore, as alternatives, Calgary, Ottawa, Toronto, Montreal,
Quebec City, and Vancouver.

Eliot


</pre>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="ProgId" content="Word.Document">
      <meta name="Generator" content="Microsoft Word 12">
      <meta name="Originator" content="Microsoft Word 12">
      <link rel="File-List"
        href="2016-email-signature-bis_files/filelist.xml">
      <!--[if gte mso 9]><xml>
 <o:DocumentProperties>
  <o:Author>Laurent</o:Author>
  <o:LastAuthor>Laurent</o:LastAuthor>
  <o:Revision>2</o:Revision>
  <o:TotalTime>1</o:TotalTime>
  <o:Created>2016-04-20T22:27:00Z</o:Created>
  <o:LastSaved>2016-04-20T22:27:00Z</o:LastSaved>
  <o:Pages>1</o:Pages>
  <o:Words>18</o:Words>
  <o:Characters>103</o:Characters>
  <o:Company>Alcatel-Lucent</o:Company>
  <o:Lines>1</o:Lines>
  <o:Paragraphs>1</o:Paragraphs>
  <o:CharactersWithSpaces>120</o:CharactersWithSpaces>
  <o:Version>12.00</o:Version>
 </o:DocumentProperties>
</xml><![endif]-->
      <link rel="themeData"
        href="2016-email-signature-bis_files/themedata.thmx">
      <link rel="colorSchemeMapping"
        href="2016-email-signature-bis_files/colorschememapping.xml">
      <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:TrackMoves>false</w:TrackMoves>
  <w:TrackFormatting/>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>FR</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:DontVertAlignCellWithSp/>
   <w:DontBreakConstrainedForcedTables/>
   <w:DontVertAlignInTxbx/>
   <w:Word11KerningPairs/>
   <w:CachedColBalance/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val="Cambria Math"/>
   <m:brkBin m:val="before"/>
   <m:brkBinSub m:val="&#45;-"/>
   <m:smallFrac m:val="off"/>
   <m:dispDef/>
   <m:lMargin m:val="0"/>
   <m:rMargin m:val="0"/>
   <m:defJc m:val="centerGroup"/>
   <m:wrapIndent m:val="1440"/>
   <m:intLim m:val="subSup"/>
   <m:naryLim m:val="undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="267">
  <w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
  <w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 1"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 2"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 3"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 4"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 5"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 6"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 7"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 8"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 9"/>
  <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
  <w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/>
  <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
  <w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
  <w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
  <w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
  <w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
  <w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
  <w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
  <w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
  <w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
  <w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
  <w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
  <w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
  <w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
  <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
  <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]-->
      <style>
<!--
 /* Font Definitions */
 @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:roman;
	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:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-ansi-language:EN-GB;
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;
	mso-fareast-language:EN-US;}
.MsoPapDefault
	{mso-style-type:export-only;
	margin-bottom:10.0pt;
	line-height:115%;}
@page WordSection1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	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-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin-top:0cm;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:10.0pt;
	mso-para-margin-left:0cm;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-fareast-language:EN-US;}
</style>
<![endif]--><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="3074"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1"/>
 </o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">Laurent
            Ciavaglia<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">Nokia, Bell
            Labs<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR"><o:p> </o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">+33 160 402
            636<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">route de
            Villejust - Nozay, France<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
          normal"><span
            style="font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:
            &quot;Courier New&quot;;mso-ansi-language:FR">linkedin.com/in/laurent.ciavaglia<o:p></o:p></span></p>
      </div>
    </div>
  </body>
</html>

--------------DEDFD22CB50CE80D86C02141--


From nobody Fri Mar 31 08:32:30 2017
Return-Path: <suresh.krishnan@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 BE6EA126DED; Fri, 31 Mar 2017 08:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSV42uKaG3es; Fri, 31 Mar 2017 08:32:21 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17F6C1299D2; Fri, 31 Mar 2017 08:32:16 -0700 (PDT)
X-AuditID: c618062d-767ff700000029b8-3a-58de8830ac8f
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by  (Symantec Mail Security) with SMTP id 98.A7.10680.0388ED85; Fri, 31 Mar 2017 18:47:45 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0319.002; Fri, 31 Mar 2017 11:32:14 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Robert Raszuk <robert@raszuk.net>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Leddy, John" <John_Leddy@comcast.com>, IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, Ole Troan <otroan@employees.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv86cghjjmGk6P6rsvHH5Q4qGssVmAgAD+BwCAAAesgIAAIVmAgAAFgwCAAASPgIAAEkGAgABB5oCAAAHpgIAAAteAgAACGICAAAp2gIABEiqAgAAWegA=
Date: Fri, 31 Mar 2017 15:32:13 +0000
Message-ID: <6C78BE2C-58B6-4A3A-B42A-C8A46D68B730@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com>
In-Reply-To: <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_A461DC2B-1DEF-4AE4-945C-CF3E030DF34B"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLIsWRmVeSWpSXmKPExsUyuXRPiK5hx70Igx8v+SzaLu5jsnj19hqb xbON81ksXp59z2SxdMFyJovJbSvYLJoWNjE7sHtc72xh9jh47COjx85Zd9k9liz5yeSxe+MC pgDWKC6blNSczLLUIn27BK6M76tvsRasd62Y8OQ+ewPjfYcuRk4OCQETiX3PjzJ3MXJxCAls YJQ4uPMMI4SznFHi8ZttjCBVbEBVG3Z+ZgKxRQRUJTpPPALrYBaYwiSx6NI/sISwgIfEpE3X WCCKPCXWbTzMAlIkItDFKPH69nlWkAQLUPfrKQ/AbF4Be4ndf7cxQaxrYJeYePU12DpOgUCJ TX/3ghUxCohJfD+1BmwDs4C4xK0n85kgDheReHjxNBuELSrx8vE/VghbSWLO62vMEPVTGCUW rgyGWCYocXLmE5YJjCKzkIyahaRsFpKyWYwcQPEkiYerEyFKtCWWLXzNDBHWkZi8kBFVGML+ eP4I1ERTiddHP0LVWEvM+HWQDcJWlJjS/ZB9ASP3KkaO0uKCnNx0I4NNjMCIPybBpruD8f50 z0OMAhyMSjy8DxLuRQixJpYVV+YeYlQBan20YfUFRimWvPy8VCURXpkcoDRvSmJlVWpRfnxR aU5q8SFGaQ4WJXHeCecvRAgJpCeWpGanphakFsFkmTg4pRoYq3/rFxybYvn918KLs6deTzD5 cGUl707nZb8LcybqdK6w1f47mb1zY8eqAxJvtjx7vzY4ydC0/eAUpZ9X0jQLev/y8NTPUdkv 3C3lvvd9tse+nNCZ94u8eS3Nb/w+N+ud8zZm14kfi6pPp87Ov/tJK1cqKsf1Q9z9tDl3H4dL Pdp64Z7MZNkUdiWW4oxEQy3mouJEAJJ12X8AAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BYNUvpYx4k1JjYS5C2JAMplr-70>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 15:32:26 -0000

--Apple-Mail=_A461DC2B-1DEF-4AE4-945C-CF3E030DF34B
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_BFFE424B-2FB0-4176-9E61-E493C3568574"


--Apple-Mail=_BFFE424B-2FB0-4176-9E61-E493C3568574
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Robert,

> On Mar 31, 2017, at 9:11 AM, Robert Raszuk <robert@raszuk.net> wrote:
>=20
> I do not understand how 2460bis makes it "easier" if proposed change =
to the text directly tries to prohibit what is described in a document =
already long time back accepted as a 6man working group draft.

First of all, adopting something as a working group document only means =
that it is a starting point. Adoption of a document does not mean that =
there is WG agrees with all the text in the document. That is why the =
document goes under WG change control.
Secondly, I have no idea what you are talking about in this specific =
case. What work in=20

https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06 =
<https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06>

do you think is prohibited by this text? Can please provide a text quote =
from the draft?

Thanks
Suresh


--Apple-Mail=_BFFE424B-2FB0-4176-9E61-E493C3568574
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Robert,<div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Mar 31, 2017, at 9:11 AM, =
Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net" =
class=3D"">robert@raszuk.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div dir=3D"auto" class=3D"">I do not understand how 2460bis =
makes it "easier" if proposed change to the text directly tries to =
prohibit what is described in a document already long time back accepted =
as a 6man working group draft.</div></div></blockquote><div><br =
class=3D""></div>First of all, adopting something as a working group =
document only means that it is a starting point. Adoption of a document =
does not mean that there is WG agrees with all the text in the document. =
That is why the document goes under WG change =
control.</div><div>Secondly, I have no idea what you are talking about =
in this specific case. What work in&nbsp;</div><div><br =
class=3D""></div><div><a =
href=3D"https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header=
-06" =
class=3D"">https://tools.ietf.org/html/draft-ietf-6man-segment-routing-hea=
der-06</a></div><div><br class=3D""></div><div>do you think is =
prohibited by this text? Can please provide a text quote from the =
draft?</div><div><br =
class=3D""></div></div><div>Thanks</div><div>Suresh</div><div><br =
class=3D""></div></body></html>=

--Apple-Mail=_BFFE424B-2FB0-4176-9E61-E493C3568574--

--Apple-Mail=_A461DC2B-1DEF-4AE4-945C-CF3E030DF34B
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzMxMTUzMjEzWjAjBgkqhkiG9w0B
CQQxFgQUTL1nWk5PSpb4YxqzbBr1uL6fVjgwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQAlRTEjc+BQZ16I3q7Q0ojPALtrinLw3kpap+WmpWA6UB1jGVlGWUePSTFbyg6a
Na4LlRoMeuCEwee+DBH+PnqzwKbyeBxv2Y1vyY3Y0yckMtAQP7+LeV2UqWn6WDSv2DLuCEcqe6ap
hGO/u5iOaQMSsoUczmrHqzmJfxzAipay9nfbbkeCDsR7jIQvT19Z1ZvdspKCodx6dymX/M4BV0j5
R6iU1nloKqmwKqINUwrLScsjfzfZbhbOsgJKE/dPsHsJnVAa0uS76p4PAA9CSun/ltvzz9wBCwSI
sL2YyfFPy8KKWzOVYqQpS596Nad1wvGWqWC3vBnbXbhuTMGAPJilAAAAAAAA

--Apple-Mail=_A461DC2B-1DEF-4AE4-945C-CF3E030DF34B--


From nobody Fri Mar 31 08:39:31 2017
Return-Path: <dromasca@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B3DC112950A; Fri, 31 Mar 2017 08:39:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu <dromasca@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-pals-status-reduction.all@ietf.org, ietf@ietf.org, pals@ietf.org, dromasca@gmail.com
Subject: Genart last call review of draft-ietf-pals-status-reduction-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149097476468.4284.16899240629504751438@ietfa.amsl.com>
Date: Fri, 31 Mar 2017 08:39:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hpctbLyMiAPdZ-JoNuvmfj--3Kw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 15:39:25 -0000

Reviewer: Dan Romascanu
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pals-status-reduction-??
Reviewer: Dan Romascanu
Review Date: 2017-03-31
IETF LC End Date: 2017-03-31
IESG Telechat date: 2017-04-13

Summary:

This document describes a very useful optimization for MPLS LSP PWs
operations by defining a method for generating an aggregated PW 
status message transmitted on a MPLS LSP to indicate the status of the
PWs carried on the LSP. The document is clear, detailed and provides
all needed information for implementers to write code and for
operators to deploy. 

Major issues:

Minor issues:

Nits/editorial comments: 

1. In section 8, first paragraph: s/rages/ranges/
2. In sections 8.3, 8.4 the construct "IETF Review" is worded in three
different ways (IETF review, IETF Review, "IETF Review") - better
align





From nobody Fri Mar 31 08:42:25 2017
Return-Path: <bob.hinden@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 BB0251294E1; Fri, 31 Mar 2017 08:42:23 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uZ1wc8M2ngyJ; Fri, 31 Mar 2017 08:42:18 -0700 (PDT)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF0E81294DF; Fri, 31 Mar 2017 08:42:17 -0700 (PDT)
Received: by mail-wr0-x233.google.com with SMTP id k6so104644191wre.2; Fri, 31 Mar 2017 08:42:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=uvC6LN17n5WrIS4pB55oivGWElM8RZH2UZRG6EapTaI=; b=iZTsHsalDD65DTGOMsBV8Oqmcp7JvpKe8Rtz+OdSPqWYd74a1mM4X3SFvK+V4irPdR RCTAlsHlXVYZKnZMLD/MnwLnZlm09jOqYH0l/NcRu0xO6Jok7xS/h7esmrhXTqbFZDJh 1nXc/rBxHuplAXFCmEy7/bBAToGnPKuk4aTaA4pMTF7aXUA3t5ZuQb8iHHWO8GYwD9Oy Au3JSXFythgCRQTxN33fPFDUb5H/QPNVy8nuK4hUOdMHK9iqHJT16lP/oafoiMKfgO6y rWeJmj13koEiDlqZQ2z2+KD9rCyb7OY1JnXKTkWo/y71kEiUa5mpCy345T6uaToS02Vk cY2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=uvC6LN17n5WrIS4pB55oivGWElM8RZH2UZRG6EapTaI=; b=tVStWNXUbY/QInM9QBbIABIUIFgWFqmLgtPQj9NwPKiBh67IJJ2UPm+UgQXxI2tsLr shjLDXc6XaI9BbYG37K9TJpCxlkRYr2PU6OcAgc0U30qC+KQI5KOff/guaiX6W8lpck5 g/Fw4IiilAICuldRRHWin2i/IVXuajwfz4i3RCdgrwza1CuitdxYVJ1epSWAPmAg0ZqX fJGACFD0p/e0pTFqQYLg5FylYl9HYyDlHxqzH8TE0fMsb77sje8Rboq6dDDHkNm3Nanw FDnHOvXZ4KL4oIuMj2P59l30FwBNER1ILbhNkFJa1+XW6/ld5hi4eJT2Iwgd79qp57Yt fyWA==
X-Gm-Message-State: AFeK/H1vUVFrUyMLR4FTGnzOInfa9I5iMNZgVexRTWrwP1JHYM0aMX89wb9pNe9fC8MQcg==
X-Received: by 10.223.164.83 with SMTP id e19mr3795774wra.154.1490974936009; Fri, 31 Mar 2017 08:42:16 -0700 (PDT)
Received: from dhcp-86b9.meeting.ietf.org (dhcp-86b9.meeting.ietf.org. [31.133.134.185]) by smtp.gmail.com with ESMTPSA id 36sm7153076wrk.15.2017.03.31.08.42.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Mar 2017 08:42:15 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <87C934A6-A4A8-41A4-A849-B0EDE8D234FF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BFDEED0F-758A-4590-8A4A-0CFF5212EF69"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IAOC requesting input on (potential) meeting cities
Date: Fri, 31 Mar 2017 10:42:10 -0500
In-Reply-To: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: venue-selection@ietf.org
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gQBB0413n_mJp3YmLp5o2-jMTFs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 15:42:24 -0000

--Apple-Mail=_BFDEED0F-758A-4590-8A4A-0CFF5212EF69
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

> On Mar 31, 2017, at 9:18 AM, IAOC Chair <iaoc-chair@ietf.org> wrote:
>=20
> The IAOC remains committed to soliciting input on future IETF meeting =
locations. With this mail, we are soliciting input on some potential =
IETF locations, including one where we have met before, but for which =
conditions may have changed.
>=20
> Specifically, we seek community input on reasons we could not have a =
successful meeting in any of the following cities, or of any limits to =
attendee accessibility or inclusiveness that should be considered:
>=20
> Ottawa
> San Francisco
> Austin, TX
> Barcelona
> Boston
> Busan
> Calgary
> Denver
> Helsinki
> Houston
> New Orleans
> Osaka
> Philadelphia
> Washington DC

I have no issue with any of the cities above for future meeting sites, =
but I agree with the views that deferring future meetings in the US is =
prudent given the visa/entry issues.  We can have successful meetings in =
Canada or other places in North America.

Note, in picking venue locations in North America outside of the US, it =
important to pick locations that don=E2=80=99t require transit in the =
US.  In the list, I think Ottawa is fine, but not sure about Calgary.

Bob


>=20
> Please send input to venue-selection@ietf.org. It will help the review =
process if the Subject line had the name of the city first, Subject: =
<city>.
>=20
> As a reminder, venue-selection@ietf.org is a dropbox e-mail address: =
its archive is publicly visible, but subscription is not available.
>=20
> Thanks,
> Leslie, for the IAOC.
>=20


--Apple-Mail=_BFDEED0F-758A-4590-8A4A-0CFF5212EF69
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJY3njTAAoJEK7rdBF357uoBZsH/28POin7WJHxaKKW4375OrTv
qPWs8G2HQzwvehC/15rJtRbT1uxNMFVdedlC+2ZNfa94jNK3TABe5lMU2sGfwsWP
lc3sN5Y97oeMicfpEqdej3DKdGl7/w3huSEB7/NGO6q3kDA+gYA3q2EPj870uxu0
1tHpzNGwYGq+0xMaWC5PbjNXvmx2giFuzJpNDxf6ngpABSyV0IkN2U4NdJMymN4s
D7LDkuwUAX0asgq6dv870VBtcIfS3YXKiRpFMGIdyAD4GnJurbpwODtKmdMnEBP3
qYQVd4PCdmuzBO9I1pEC6hALJycCBPaUsjxJ9QR621/2hIFq+IJ7PHruSy76TJw=
=1EHB
-----END PGP SIGNATURE-----

--Apple-Mail=_BFDEED0F-758A-4590-8A4A-0CFF5212EF69--


From nobody Fri Mar 31 08:55:38 2017
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 C7201129532 for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 08:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gva6S-wqMwgE for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 08:55:34 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 946AB1294DF for <ietf@ietf.org>; Fri, 31 Mar 2017 08:55:34 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ctyth-0000yU-BW for ietf@ietf.org; Fri, 31 Mar 2017 15:55:33 +0000
Date: Fri, 31 Mar 2017 10:55:33 -0500
Message-ID: <m2a8811lvu.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
In-Reply-To: <87C934A6-A4A8-41A4-A849-B0EDE8D234FF@gmail.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <87C934A6-A4A8-41A4-A849-B0EDE8D234FF@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DUA9OAqyShTc2_1kVyMS-G1NU8w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 15:55:36 -0000

>> Please send input to venue-selection@ietf.org.

so, i am curious.  do people
  o think their imput is more important than that of we small people,
  o can't read or follow instructions,
  o or some other thing i do not understand?

randy


From nobody Fri Mar 31 09:09:17 2017
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 CB93C126DED for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 09:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PMfjU56V0MGt for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 09:09:12 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FBC9124D37 for <ietf@ietf.org>; Fri, 31 Mar 2017 09:09:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2395; q=dns/txt; s=iport; t=1490976552; x=1492186152; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=1Bod554/7WIAzbA2CFIuVgkCG1Kb1D2nIfkNcZUiltg=; b=WYSS6GPx/KO8nSG9l72jy2tza3lMyGn1qiG+A27c9E97S29AnAytNCE8 p4ii8XrZPbb7fJNbNggJsKHabmJeVBaNrzpCKKeZ68Kg9YxrKe5rJgfqp xRyThkY4Jwpbhn+g7kQY9VL6vmQd10tE8K/VXN0fMct98yEd3YU7AS6mO g=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DsAQBQft5Y/4kNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1SFTooSkVWTQYIPgg6GIgKDRj8YAQIBAQEBAQEBayiFFgEFI2Y?= =?us-ascii?q?LGCoCAlcGAQwIAQEQiXmtZ4ImilsBAQEBAQEBAQIBAQEBAQEBEg+IU4JqhDWDJ?= =?us-ascii?q?YJfBZBmjASDfIIMjEiBfYhiI4Y4k3EfOIEFJRYIGBWHOCKHYoIuAQEB?=
X-IronPort-AV: E=Sophos;i="5.36,252,1486425600";  d="asc'?scan'208";a="225384154"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 31 Mar 2017 16:09:11 +0000
Received: from [10.86.247.170] ([10.86.247.170]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v2VG9AXB006532; Fri, 31 Mar 2017 16:09:11 GMT
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Randy Bush <randy@psg.com>, IETF <ietf@ietf.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <87C934A6-A4A8-41A4-A849-B0EDE8D234FF@gmail.com> <m2a8811lvu.wl-randy@psg.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <d83ffbdd-e3fe-7db5-fef0-fba4d5a52ab0@cisco.com>
Date: Fri, 31 Mar 2017 11:09:07 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <m2a8811lvu.wl-randy@psg.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Wxw5bCDAA7f0jcVaFX8M40SwLbmflwjji"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nmzOOdhfAp1wCB3b45jKSNplLzc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 16:09:14 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Wxw5bCDAA7f0jcVaFX8M40SwLbmflwjji
Content-Type: multipart/mixed; boundary="FwN7dUfAvmL4gHJUv3kAvTPwJmh2KSLSa";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Randy Bush <randy@psg.com>, IETF <ietf@ietf.org>
Message-ID: <d83ffbdd-e3fe-7db5-fef0-fba4d5a52ab0@cisco.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
 <87C934A6-A4A8-41A4-A849-B0EDE8D234FF@gmail.com>
 <m2a8811lvu.wl-randy@psg.com>
In-Reply-To: <m2a8811lvu.wl-randy@psg.com>

--FwN7dUfAvmL4gHJUv3kAvTPwJmh2KSLSa
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 3/31/17 10:55 AM, Randy Bush wrote:
> so, i am curious.  do people
>   o think their imput is more important than that of we small people,
>   o can't read or follow instructions,
>   o or some other thing i do not understand?
>

I believe this is something that is worthy of discussion within the
community and not just something that should be bottled up in a mailbox,
for two reasons: first, while I have a view, I am willing to change it
based on discussion (that would be the precise opposite of your first
bullet point), and second, we currently have a document opened in a
working group where discussion of this point might migrate back to
that.  And so, it falls under your latter bullet.  Perhaps in future you
might assume that to be the case (it is, if nothing else, more polite,
and reduces such meta discussions).

Eliot


--FwN7dUfAvmL4gHJUv3kAvTPwJmh2KSLSa--

--Wxw5bCDAA7f0jcVaFX8M40SwLbmflwjji
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJY3n8jAAoJEIe2a0bZ0nozRDEH/0ccrd7chZD8NwZNQHVu2cXQ
9tMVUDTWLgTaSPzU4iqY72q1D0qxSpp2gzR2Cf+ok5gASp0G5jWrhlQQptQ0LaEu
V5gZiIxSvKXdPws55IvnOzvR3POTZ8p8lgEcfWqkp5uSzDChX5QMDY6jw/+M3PWa
gm1AdiXZPZONp2j6rTBep4p1qXC7YpVmngZUEJDgOty1czmWDRK3Ix+KhRxCFr+y
6WV055gUU03dtKANKvHbNrTqh23EX6NngAulOxByPpOVoZf99GEy2blN0t3zLRJh
knJBevBcPAuYnAls7+dQcFSXRDzgpKK9o1ZpoX8qJ9458egEykZKe0lFH+upI/c=
=WG5o
-----END PGP SIGNATURE-----

--Wxw5bCDAA7f0jcVaFX8M40SwLbmflwjji--


From nobody Fri Mar 31 09:40:18 2017
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 470E6129533 for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 09:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.698
X-Spam-Level: 
X-Spam-Status: No, score=-4.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9y9uviDsZyJ for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 09:40:10 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20107.outbound.protection.outlook.com [40.107.2.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E81D128B88 for <ietf@ietf.org>; Fri, 31 Mar 2017 09:40:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=PVpHO375jukaATpK/kaAt/o9u6TGViON/ZD2axD/Zm0=; b=U2QPpYEOLrNRq+2HFgIbzCa5e6XiRswUXAKn8XaKqnoJdJXaWP5DvNv6fnxrBL1BhJ50pyNKlvge3LnUI/1IsU9lXTwkd014JvXVAfWQjQA1x3hg9wPjYmMtVeLDiiYH8MNALpTNxbtHtvmxT8q8aShw21RQj5tEkMeqZIz2hxw=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.169.157.161) by DB5PR07MB1560.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::10) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1005.2; Fri, 31 Mar 2017 16:40:07 +0000
Message-ID: <01b701d2aa3d$335e22e0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <ietf@ietf.org>, Eliot Lear <lear@cisco.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
Date: Fri, 31 Mar 2017 17:32:07 +0100
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: [86.169.157.161]
X-ClientProxiedBy: DB6PR0202CA0029.eurprd02.prod.outlook.com (2603:10a6:4:a5::15) To DB5PR07MB1560.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::10)
X-MS-Office365-Filtering-Correlation-Id: e4aedc2c-f75b-462d-b4f9-08d478549733
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201703131423075)(201703031133081); SRVR:DB5PR07MB1560; 
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 3:uICcZBgZVybH44pI8QG1GdDeFcW/3Q5RrrpqtuG9oeo4oz3SrJicppi4D1fTvYTgp0im0a/SvpiIDalCbpwUuf5FcZgCsUQCmVjFWZjUOs5eM/V7Q2+Js5FO0+bzfcVQDmWEbnBQBkFs7CAhafyjWdzp2Z7RCbXEiV5HWWRsf+7q4LwFn4isOV5ayXzp0GN+J+lCS8u4af7WShoBttqz1NdSDLD2EaMhYmQGan4OBL4wNgadLl7aVLy8diYf49kuhZO/G+ZpEZidkCqRJ+qeiF9LnWH118c1s+oKr5G/Baj6OSUMqCVcJmdtK4NBx2L5tINWgetSBm7278F+iRT9jQ==; 25:PYTziJ21ZOr5ZS5MjJAtzm70SEkCf1bOH500rPs+XYAAbYEDCx2riGlF5r5U7U7Hp79uaXeRDB0rsRN2cjc1nrUbs1a0n8EbHaO7IPBX23Q/L4yzdiR6SIjQImlX6ewUxD/MWbSbH06Zl17hIlGP98nPNhE72TyxtM9/DgS7kDvsBdZdB9p/H+3CeeTxuUb6n3k5sDJzHyK6ecX+q8oFnek+Zi1IEEEJfpgXoX8LuDH8Yr9c6/+fBdwPi8nwt3hChczCYS1YAXHkhJWIHnEAx1N86HtFv2PTehjx6b2SeWKYxGKoLjGFxwr23Jh4rc4xxyQcrjSVAvK0p2KDytxuz+c50LsoyRvhqlRw8ICbHxaMznz8qdY35wJ98er/3HSRKnybOhmYFdb91ayEWJGKbjIupEPAQN3YbPMXr1VOXT1kVb67wReNKKZEHUrRZ+lTPEuAcGCJfyC/cZklHcgpdA==
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 31:dHywsCCtMFvi+MPWIdc88IRVptE+AtuFg/rA7vEgM5SRcRfxHvAFni7Tu6aRE9uRbWPCvEkmjzfmPf9ghwBn9gLRSXZqL7mRRonVc0qlWZOU+NoRQRRnAHv6XRDCYSNK6tVQarH2qJuYZc1c3U2IbAIDYT5hL1EjK8GHL5Sb398M/VXKnP0fg1SL+G/DL4QAAYWgr5hz+5QbxeVwhWBjw/JPfsHS8Db271YB/0gnupYgzfxibkGj10RueC/cQwfUzyhJ0yRld92pAXgE15uPoOCuJhL2rYhxEcwOg0PvVQI=
X-Microsoft-Antispam-PRVS: <DB5PR07MB1560564E1969DAF0790F130CC6370@DB5PR07MB1560.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(6041248)(20161123560025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123555025)(6072148); SRVR:DB5PR07MB1560; BCL:0; PCL:0; RULEID:; SRVR:DB5PR07MB1560; 
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 4:P9lbIrVSEbnHd+LQZB8dC768PUfhwMVsxTkNq+vauR5Bo8n45miBlq6BgD+JRiA5X2EFyRUjid3oTERHB2fUW9hNF8uekX/hUT9lbrGhwJTM9+qyLqGN3V5fpw+EXMugQDi0o0diZ5RXxpHIB1bsQB00nApJEFTLyu4BOUHcoML3DGkZQcvI+xw8BoU8tzYrYc+wR8s36/cA28sCB6t5pU/130N5WkOkKpixwllacyTLiSLqn/ArMoCq9M1RaFS092+pz/jrqPmy87U0/Zv2Yu9s4IC5wcCdxjKCMiKbjxITOJ6j1cm1ffQXsgNfUflEPRC1jBQzUGaVsSUKL5Y4gk64AcmzQm6t1E2vt8969mhwTBHVr9AdxjPdBuyf2+XnqAUmyd35TbSK6x5njwnENoYzkojKCH6kmyi94qW8RBWGSSUKTzOLRmjMZ6qwrYWR5OF1rte8gy4AHZ6IsTFNKfAKAiSHea7SQR7YQgEZS12zFCyJmzG20tNBDyRC5SYBvCWUOlwwJJbv7Dz5zYWLlv2+WmdXRmML84ysnNClscslqeN1Y2qPpDUe++2Zwvx9ida5pyPmgVo0VV9NmwWMMZk+xtA9Q6sz7Cp2qG+nU9cpeRI+ESIMWGaS+QPR6d5+HQx3UwOuuJPKPexssfYxrDVQIusPenvnTAmia7eGtYLWUJJbPMzDstxlI8WHhn+Ly9MpjxpOPvaMAvPo2D2jHX+LGestASnrgvErZ9u/2M8=
X-Forefront-PRVS: 02638D901B
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39840400002)(39450400003)(39860400002)(39850400002)(39400400002)(39410400002)(13464003)(24454002)(377454003)(9686003)(44736005)(6486002)(23676002)(50466002)(33646002)(189998001)(86362001)(53546009)(5660300001)(61296003)(4720700003)(76176999)(42186005)(50986999)(25786009)(81686999)(38730400002)(62236002)(84392002)(53936002)(8676002)(230700001)(2906002)(50226002)(305945005)(5820100001)(44716002)(3846002)(47776003)(66066001)(229853002)(6116002)(6246003)(6496005)(81166006); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR07MB1560; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjVQUjA3TUIxNTYwOzIzOmxIM1dIUHBpK0FEZFovc2YwQXRrOW5uZko5?= =?utf-8?B?R0RjYWlJVmdONWd2Q1ZDR3hIZm9qay9kcDhZYkVnVk9VWUUzRWhGVk5PWWZo?= =?utf-8?B?dWxaTkdGRWZTMGovVGJHS0VpdnQyT2MzYTBOMGJ5OWVOMDhkZnVzSDRjcmFk?= =?utf-8?B?aW5pQzRVd2IwbC92Z1QvdVExeFVTNkpSaTlhWVl0bU44eUxUQ0czWktzNkFy?= =?utf-8?B?c0dNSnBudFkrQURDVE9FdEk4bzJRNTMvb1F5ZUNZNDExZWpyY0doc0F2UCtW?= =?utf-8?B?Q3J2ZU1WQzJkUXRNek93Z2MrbEgrL0UrWTE0QXJRYk1xUG1YWXl5cG5LbEdF?= =?utf-8?B?OVFLNTNHQ2hCS3Fndk5SSDNEZFhFQWZnYjd2MmRDREx6NmlKQTZGa2x1MDFB?= =?utf-8?B?V3VldjdSSTVwdExTVXNwaGFScklDSjc2S25MZ1pzSjJSaGkyNGZiV2xtc0cw?= =?utf-8?B?bWxpTEpMb3BBQWFDVitNZU9KRy9FVUVJZ3lHT0RrTVRLU0k5WEthT1VHc2tC?= =?utf-8?B?RWhWL0t4WHVkNmVwdkVZQ21uVnc3UkRjT21tNlVnT0Q0OCtTUjlyNDUyRWJ6?= =?utf-8?B?Ty9Gb1ZMbjhkWHB4N01Kb2pqZCtka1R0VzdCZ1ZHcmNPL052eUZlWXphMElq?= =?utf-8?B?ZTk3dzBSM2V1SnVVVFc0VjcvRExkQzdXV1VxdjRrcG5IUlZ0QXJmcFdLcFRV?= =?utf-8?B?NjdrS05HVEZjckd2UmNyUWFGWjR6MEJYZnNKZFJyM01BMit0OXBVeWZXYUNy?= =?utf-8?B?UVNnSUh6VytXWXZnQklQdEpqWENGWk44TEhNYzJ1WDZIYVdDZ3kzS3EwQzJR?= =?utf-8?B?R1Nnd09DbDhwdUpMQWFyQ3paUDZjaEtIWFJNdzVYMWsyaHY0TEpuUXVndHRm?= =?utf-8?B?ZGl6OWwrelRNZWxaMEo5cS9lZGF6N1V5SUdCQ0tEWWJVeFBwajdqVXQ5STZl?= =?utf-8?B?U083RWxPdjkrRHRydVdURHBsQ0tkSHJRMEpDZUJRcDhCYzJ1T01pRmhnSjFH?= =?utf-8?B?bWYwbHljeUhxaFpuU3F5bWZPVHhKUlBnNnJtKzlmTm9RVDk1QWYrQTk5d0ZH?= =?utf-8?B?R0doMWx2b1BEV2dyUE0reVRxN3B0VjFoRktKUGxCSmhNL1hlQkQvc0FKNitj?= =?utf-8?B?Q0hLNmhlRmc4emhsUkdiQWRveVE2dUNhdHpxUy9MOGRJTHBHbmVaaEdMRFda?= =?utf-8?B?aHBpVlhNdGI0Q056MnFoYmJpQmdvVGlWeDgxTDEwcVFnTDlFYTJpZ05TSnpI?= =?utf-8?B?dUlMQVRXN29SejlkUWMzd2pKYVU0ZWJXKzFjVWxSZ1RrUDN3eThVQ3JRcUxU?= =?utf-8?B?SUhJNzc4d01mcmQ4WHRuL0V0eG9VZElFY1pVYlFpcExNaHA4ejQxUmVuTDZH?= =?utf-8?B?eWlNczRFbFJLTnE4eFhFS3g0Ym1XcTc1NlpncjVYSUpXU1FwdmcvK2g2K3ZS?= =?utf-8?B?TVBrckl1aEkxZFZlT0JPWWhTV25Qd01pZk84cXZnTm5kWmFiTERhQWp2TEdv?= =?utf-8?B?cVBuUXFSUjQ1WTNyMWROdG9XcWY1WEpNMmRMbzE2SjJZeE9ETzRRWnYvQWpP?= =?utf-8?Q?u0jdQxuZA90INsf9t/Rwj2RCrQsAaFgXKP9pLYYv12pI=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 6:VPURQkOgvmLsCcXRKzybTX5c5SP3f5ierdBXa2f3twYNxGCubKXbRuGxu3ACfog2r2pvvK+x9AAG1OoVBtmDzvq2FGydxnhxja0tnVRrIXFeI4y8r1Rmjbo3P0z8jzAbw247i3DytAhRoJBiQQPFHx9KMxOXJ1V9jdIe0PBvGKqifPh4htqEWjH19I8nu3SPAHp1rKoNZ8EraHSEYi9SQjYUWqyuFtP+6TeIaC7hQQ0q9abRtBvztgRIv/b6xT1bhDXQ5IEA6uOkDpTWnTZnZhKNFvNITo+hAMtDSjdQ/aLxsuq8cLDUDJuMFNtlZpHmd2QG3wLUCd236MXJZBFmdCKrWYkwXDzzJY1PhI3QhQmxPUl55cM6/auWxaUXm/Zuy1zCy+ZREBb+41N7FVtkRQ==; 5:Rr7+5buLLCuAzhrGGPYQJ1jgMCVKt3svIYtw7HOD4KgOSSH+2u9MM0lfXBgXSxnMB0wB8wuI0iLz+j7LXj0yvQY63QoJ5NoQ+K9XmgMrzm1Fh/OQoqu6Wx/P1gW2+bNlqnezbB0HBeECS0mRoglgXyHGpfhxkFyZqme2WPNkn+E=; 24:fdpAYQZpP6OM5LSYoyL/1KqTSt+vfLEo/hb93qyv0xF3Hc2DgwQZnFW7qrqyHuI9AbjemPS8R4bY/zKnJItJETUuCZJcqqLt5rnVHCRt6DA=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 7:VhUePEmiRUHtWj4iNfDJ+cFcG7PJ650SERLNn7EA+BsDujIGPWeUrSKhLPuXlCbaW4MLfY6Rc4F0jUiVPG0DbsbpEMnYZn8UhkreI9R6y9jY6TVglsjUB6hLh8TvVgGdOkDPnaQ6t0Mu3MTlrK6W0UV43puliYSO02OyFEUEcybRG0o0ycQxEsoCBnR/Yz1VDyoQlsL3GUJqOddDWB51qTLYL2+YAu/WTIAXcY0KeqEl0jdTM+QMnAhWFUAlOGeF+MaG3TFFsWjPiiop/gOHjxjX+/+YABx43Mdc4EEpeu+vJxoBeyZuCQjCFj8gliufOKLyacDYFe824k+u5bS2Fg==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 Mar 2017 16:40:07.2764 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1560
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/44l-X1jhppnPnGCLkOQHKfyjEVU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 16:40:14 -0000

----- Original Message -----
Sent: Friday, March 31, 2017 3:42 PM

On 3/31/17 9:18 AM, IAOC Chair wrote:
> The IAOC remains committed to soliciting input on future IETF meeting
locations. With this mail, we are soliciting input on some potential
IETF locations, including one where we have met before, but for which
conditions may have changed.
>
> Specifically, we seek community input on reasons we could not have a
successful meeting in any of the following cities, or of any limits to
attendee accessibility or inclusiveness that should be considered:
>
> Ottawa
> San Francisco
> Austin, TX
> Barcelona
> Boston
> Busan
> Calgary
> Denver
> Helsinki
> Houston
> New Orleans
> Osaka
> Philadelphia
> Washington DC

I apologize for not following the form in the subject line, but in my
view, there is sufficient uncertainty about ability of people to gain
entry to the United States that we should not be planning meetings in
this country.  Over the last few weeks we have seen people with valid
visas turned away at the border or otherwise detained, sometimes for
days, without any cause being given.  We have people in our community
who could not get a visa in time for the Chicago meeting.  With the vote
by the European Parliament requiring Americans to have visas to enter
into EU countries, it is likely we will see a further degradation of the
situation, such as suspension of the VWP, thus bringing further
uncertainty to new and more common classes of individuals.

That translates into concerns over San Francisco, Austin, Boston,
Denver, Houston, New Orleans, Philadelphia, and Washington DC.  I would
prefer, therefore, as alternatives, Calgary, Ottawa, Toronto, Montreal,
Quebec City, and Vancouver.

<tp>

Knee-jerk reaction, was my thought on reading the IAOC post.

What I read in the press last January was that the USA wanted to
introduce a three month restriction while working out how best to keep
its citizens safe in the longer term, and that the initial restrictions
have already been relaxed and - I believe - subject to legal challenge.

I realise that IAOC is looking years ahead but do think that we should
at least wait until those three months are up.

In response to Eliot, as a citizen of Europe, I have had a harder time
getting into Canada to work than even I have into the USA so I place any
USA locality (except Hawaii - wrong side of the world) above any in
Canada.

Tom Petch

Eliot




From nobody Fri Mar 31 10:00:02 2017
Return-Path: <paul@nohats.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 332361297EC; Fri, 31 Mar 2017 10:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHKfOfG61ZfN; Fri, 31 Mar 2017 09:59:58 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CF9B129574; Fri, 31 Mar 2017 09:59:56 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3vvnmT6849z1x7; Fri, 31 Mar 2017 18:59:53 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1490979593; bh=1EFKWzIRmiBsb6F5JLBbTqHX5PQqZ7O5b4BVF5OLfnc=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=oYYnHMmo17AC9nEYXRerKYjZrrJqxD7DsSGu7G7h/nBriZ7RMPRhZKIxOsBmFikdh oXfE7t0eh7I8d2+7E31CXHo1rahRLtWZX0FiczV0hjxMJvJU1fxH3EA0z7vMRv5tfB cb6x/FFUKatZ2cR4TF69Ry8PXbpEd8hTTrrFHH6Q=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 2WPd6L23xJ22; Fri, 31 Mar 2017 18:59:51 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 31 Mar 2017 18:59:51 +0200 (CEST)
Received: from [31.133.184.215] (dhcp-b8d7.meeting.ietf.org [31.133.184.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 134A2F28; Fri, 31 Mar 2017 12:59:50 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 134A2F28
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: IAOC requesting input on (potential) meeting cities
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
Date: Fri, 31 Mar 2017 11:59:49 -0500
Cc: ietf@ietf.org, venue-selection@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
To: Eliot Lear <lear@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nslo4zi5NcOnWyXm7anRbB2ydSk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 17:00:00 -0000

> On Mar 31, 2017, at 09:42, Eliot Lear <lear@cisco.com> wrote:
>=20
>=20
> That translates into concerns over San Francisco, Austin, Boston,
> Denver, Houston, New Orleans, Philadelphia, and Washington DC.  I would
> prefer, therefore, as alternatives, Calgary, Ottawa, Toronto, Montreal,
> Quebec City, and Vancouver.

I agree. I know some people who failed to get their visa in time. I booked l=
ast minute because I was waiting for the religious/racial ban to be suspende=
d. I don't know when I will be refused entry for not handing out passwords o=
r pins. I don't want to leave my laptop out of sight and I dont want to fly o=
n planes with a zillion lithium-ion batteries in the cargo hold.

The situation has been in constant flux and is unlikely to stabilize soon, s=
o we have no way of knowing the restrictions and limitations a year from now=
.

It is prudent to move the San Francisco meeting to outside the US.

Paul


From nobody Fri Mar 31 10:01:24 2017
Return-Path: <rraszuk@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 A6A9B12952D; Fri, 31 Mar 2017 10:01:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sS-g-53bFbVE; Fri, 31 Mar 2017 10:01:21 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 211921296F3; Fri, 31 Mar 2017 10:01:19 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id b140so43552657iof.1; Fri, 31 Mar 2017 10:01:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9qjhjtCeTYXuHOp5Wo3BLOJDBEPWwB3KoS9zdKWxDO0=; b=KKwUfPosKyxTyEuetMwCnTaZsAXgrYMKsyy8YLwtuvu1r4mvpo6t68cLjBlAjDFWDr 9CfJRz3s+oRN6y8i4TjEBn7f43AwD05cxWk693ZymX+ZWthaE+9vCn3/RUNSoLTOxwxQ iBpcNb/4WXBmYuoNrP+9myY+U8ELAiqjsicOEzgDc7lDYJI07TuIQGhiiQobKLxaf8EE iuKBpSFu6AHvZ5KZwuyX73qMp/olFCgf3fJ7LhBeQHkhspyr9Vv85Bxbx+4sY7q4i0Dy HK5y8IrpyksfveyU7R73vtm4bWXPruuei1v4vBSgJSr3VPGhq2GT3pa0sPjgLWOgJrs0 GEZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9qjhjtCeTYXuHOp5Wo3BLOJDBEPWwB3KoS9zdKWxDO0=; b=lSU1uIIiDfd6v1b+w1V8junsB8TzQ+M1qB0v66hkyzwGVcDfbaKag1V1UjSEvNzIa5 8KAf8M/r3ZeHhUk4ymdiYG5u9s7mC4n0PDJDP4x+0FEBMLGWGcDNHhnuIw14m7bWwioc j985pdiVXaYz+2ZemwL7UTI96hu+gwbYH2hHTDrHne7OfveyIIFZDNw2IFcrg0veYhvq jRnVayxotYkqqm7n4R0ATy5iZmQQ1whH+YGfOsPFziv7NVzJX4EGj4aj7xWdPBwWHG/z Io8Lffbd3z6IyqMJRtAb5T5GYY8KjoQGxqwClSKXEZIDadTckh4T9BriOGIm3pE3/lWW xZ9g==
X-Gm-Message-State: AFeK/H3YxafR3O8o70uJFbCe2MsEi3WC12umHYd0khHDqlKncLoMQCdlya+exxzAdDNlfVMhfsYdWV955wicIA==
X-Received: by 10.107.7.29 with SMTP id 29mr4357994ioh.57.1490979678464; Fri, 31 Mar 2017 10:01:18 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Fri, 31 Mar 2017 10:01:17 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Fri, 31 Mar 2017 10:01:17 -0700 (PDT)
In-Reply-To: <6C78BE2C-58B6-4A3A-B42A-C8A46D68B730@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <6C78BE2C-58B6-4A3A-B42A-C8A46D68B730@ericsson.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 31 Mar 2017 12:01:17 -0500
X-Google-Sender-Auth: E6x5kIRftUWjxojt1TDqHM_CxjE
Message-ID: <CA+b+ERk4mbHrTZi3JFKBh4RjUzN=SVUGONvFuEA5Ed178MzZmA@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, otroan@employees.org,  IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>,  Brian E Carpenter <brian.e.carpenter@gmail.com>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ea6f01a39d7054c09c2ad
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qZRIlHfiloB2HoIYWY67z5cAMGo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 17:01:23 -0000

--001a113ea6f01a39d7054c09c2ad
Content-Type: text/plain; charset=UTF-8

Hi Suresh,

As you requested one of many quotes from the draft which your clarification
to 2460bis directly contradicts with:

This include either:

      A host originating an IPv6 packet.

      *An SR domain ingress router encapsulating a received IPv6 packet
      into an outer IPv6 header followed by an SRH.*


Cheers,
R.

On Mar 31, 2017 10:32, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
wrote:

> Hi Robert,
>
> On Mar 31, 2017, at 9:11 AM, Robert Raszuk <robert@raszuk.net> wrote:
>
> I do not understand how 2460bis makes it "easier" if proposed change to
> the text directly tries to prohibit what is described in a document already
> long time back accepted as a 6man working group draft.
>
>
> First of all, adopting something as a working group document only means
> that it is a starting point. Adoption of a document does not mean that
> there is WG agrees with all the text in the document. That is why the
> document goes under WG change control.
> Secondly, I have no idea what you are talking about in this specific case.
> What work in
>
> https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06
>
> do you think is prohibited by this text? Can please provide a text quote
> from the draft?
>
> Thanks
> Suresh
>
>

--001a113ea6f01a39d7054c09c2ad
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Suresh,<div dir=3D"auto"><br></div><div dir=3D"auto">A=
s you requested one of many quotes from the draft which your clarification =
to 2460bis directly contradicts with:</div><div dir=3D"auto"><br></div><div=
 dir=3D"auto"><pre style=3D"font-size:12.6667px;margin-top:0px;margin-botto=
m:0px">This include either:

      A host originating an IPv6 packet.

      <b>An SR domain ingress router encapsulating a received IPv6 packet
      into an outer IPv6 header followed by an SRH.</b>
</pre><div dir=3D"auto"><br></div>Cheers,</div><div dir=3D"auto">R.</div></=
div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mar 31, 20=
17 10:32, &quot;Suresh Krishnan&quot; &lt;<a href=3D"mailto:suresh.krishnan=
@ericsson.com">suresh.krishnan@ericsson.com</a>&gt; wrote:<br type=3D"attri=
bution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word">=
Hi Robert,<div><br><div><blockquote type=3D"cite"><div>On Mar 31, 2017, at =
9:11 AM, Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net" target=3D"_=
blank">robert@raszuk.net</a>&gt; wrote:</div><br class=3D"m_-16433691490072=
47049Apple-interchange-newline"><div><div dir=3D"auto">I do not understand =
how 2460bis makes it &quot;easier&quot; if proposed change to the text dire=
ctly tries to prohibit what is described in a document already long time ba=
ck accepted as a 6man working group draft.</div></div></blockquote><div><br=
></div>First of all, adopting something as a working group document only me=
ans that it is a starting point. Adoption of a document does not mean that =
there is WG agrees with all the text in the document. That is why the docum=
ent goes under WG change control.</div><div>Secondly, I have no idea what y=
ou are talking about in this specific case. What work in=C2=A0</div><div><b=
r></div><div><a href=3D"https://tools.ietf.org/html/draft-ietf-6man-segment=
-routing-header-06" target=3D"_blank">https://tools.ietf.org/html/<wbr>draf=
t-ietf-6man-segment-<wbr>routing-header-06</a></div><div><br></div><div>do =
you think is prohibited by this text? Can please provide a text quote from =
the draft?</div><div><br></div></div><div>Thanks</div><div>Suresh</div><div=
><br></div></div></blockquote></div></div>

--001a113ea6f01a39d7054c09c2ad--


From nobody Fri Mar 31 10:46:57 2017
Return-Path: <suresh.krishnan@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 1C5F412988C; Fri, 31 Mar 2017 10:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X87Yz6StGMgj; Fri, 31 Mar 2017 10:46:48 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 200EC12948F; Fri, 31 Mar 2017 10:46:48 -0700 (PDT)
X-AuditID: c6180641-417ff700000058cf-50-58de4facf229
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by  (Symantec Mail Security) with SMTP id B5.7C.22735.DAF4ED85; Fri, 31 Mar 2017 14:46:39 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0339.000; Fri, 31 Mar 2017 13:46:44 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Robert Raszuk <robert@raszuk.net>
CC: "Leddy, John" <John_Leddy@comcast.com>, Ole Troan <otroan@employees.org>,  IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv86cghjjmGk6P6rsvHH5Q4qGssVmAgAD+BwCAAAesgIAAIVmAgAAFgwCAAASPgIAAEkGAgABB5oCAAAHpgIAAAteAgAACGICAAAp2gIABEiqAgAAWegCAABjkgIAADLGA
Date: Fri, 31 Mar 2017 17:46:43 +0000
Message-ID: <3A7C2C05-8513-4248-82F3-15CC9C75B69E@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <6C78BE2C-58B6-4A3A-B42A-C8A46D68B730@ericsson.com> <CA+b+ERk4mbHrTZi3JFKBh4RjUzN=SVUGONvFuEA5Ed178MzZmA@mail.gmail.com>
In-Reply-To: <CA+b+ERk4mbHrTZi3JFKBh4RjUzN=SVUGONvFuEA5Ed178MzZmA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_7E69E3EA-DE0B-4FD6-8576-37651C4090B8"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsUyuXSPn+56/3sRBovP8Vq0XdzHZPHq7TU2 i2cb57NYvDz7nsli6YLlTBaT21awWTQtbGJ2YPe43tnC7HHw2EdGj52z7rJ7LFnyk8lj98YF TAGsUVw2Kak5mWWpRfp2CVwZK18/ZC+Y4lCx+dBulgbGVTZdjJwcEgImEufX7mHsYuTiEBLY wCgx+dA5VghnOaPE6n+rWECq2ICqNuz8zARiiwioSnSeeMQMYjMLTGKS+PHYBMQWFvCQmLTp GgtEjafEuo2HWUAGiQhMY5TYNu8dK0iCBaj588nl7CA2r4C9xIxf96FW/2WXWDD9KVgRp0Cg xPmZk8AmMQqISXw/tYYJYpu4xK0n85kg7haReHjxNBuELSrx8vE/VghbSWLO62vMIEOZBaYw Svy+cpwFYpugxMmZT1gmMIrMQjJrFrK6WUjqIIqSJJp27meFsLUlli18zTyLkQPI1pGYvJAR Iiwvsf3tHGaYko/njzBB2KYSr49+hKqxBnr0IBuErSgxpfsh+wJG7lWMHKXFBTm56UaGmxiB UX9Mgs1xB+PeXs9DjAIcjEo8vAs07kUIsSaWFVfmHmJUAWp9tGH1BUYplrz8vFQlEV6ZHKA0 b0piZVVqUX58UWlOavEhRmkOFiVx3nflFyKEBNITS1KzU1MLUotgskwcnFINjJN/ObF/XHBA oUbro7lPQcKer3eqPZ6bcF5RZ+rVVr3A9kXjrHKT/fbn/roND9lOMD9XOhXzwav5C5NGaPnh oNVau5r31knZJKlJXXnlMGNWldOfHI/Ss+v9Cqvm3uqO7Ga3muIZfd/tZeazQq+S/OfZLgwd uYFNEQu3i94QZNU7VbH+Vz+fEktxRqKhFnNRcSIAdxVxkAIDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WUB5M43NxZHoyALAgyudc_zr9mE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 17:46:50 -0000

--Apple-Mail=_7E69E3EA-DE0B-4FD6-8576-37651C4090B8
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_4E95FC54-F505-4B9C-8079-4C3CB7615A7E"


--Apple-Mail=_4E95FC54-F505-4B9C-8079-4C3CB7615A7E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Robert,

> On Mar 31, 2017, at 12:01 PM, Robert Raszuk <robert@raszuk.net> wrote:
>=20
> Hi Suresh,
>=20
> As you requested one of many quotes from the draft which your =
clarification to 2460bis directly contradicts with:
>=20
> This include either:
>=20
>       A host originating an IPv6 packet.
>=20
>       An SR domain ingress router encapsulating a received IPv6 packet
>       into an outer IPv6 header followed by an SRH.

Excellent. Thanks for pointing out the exact text. I can confirm that =
this text  *is compliant* with the RFC2460bis text.

Thanks
Suresh


--Apple-Mail=_4E95FC54-F505-4B9C-8079-4C3CB7615A7E
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Robert,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 31, 2017, at 12:01 PM, Robert Raszuk &lt;<a href="mailto:robert@raszuk.net" class="">robert@raszuk.net</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="auto" class="">Hi Suresh,<div dir="auto" class=""><br class=""></div><div dir="auto" class="">As you requested one of many quotes from the draft which your clarification to 2460bis directly contradicts with:</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><pre style="font-size:12.6667px;margin-top:0px;margin-bottom:0px" class="">This include either:

      A host originating an IPv6 packet.

      <b class="">An SR domain ingress router encapsulating a received IPv6 packet
      into an outer IPv6 header followed by an SRH.</b>
</pre></div></div></div></blockquote><div><br class=""></div>Excellent. Thanks for pointing out the exact text. I can confirm that this text &nbsp;*is compliant* with the RFC2460bis text.</div><div><br class=""></div><div>Thanks</div><div>Suresh</div><div><br class=""></div></div></body></html>
--Apple-Mail=_4E95FC54-F505-4B9C-8079-4C3CB7615A7E--

--Apple-Mail=_7E69E3EA-DE0B-4FD6-8576-37651C4090B8
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzMxMTc0NjQ0WjAjBgkqhkiG9w0B
CQQxFgQUfRYyTIpQymzjqyLgkDSx8UcDZwcwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQBZHJjFD9n3Sx+ZwQZMJZ3CbAM33VLFI4DYpzL+SGJ+aVlG6MVxQJucv1NFKTir
wZ0PJdcaA5QIPOIL+Krm5tWWSXu0qh8j0BY1Bap5tKyBFHwKPHaDONkm0xZfbDadoHKk4wjuNRDt
6EM4WAglbjB0UFGFuDPoZPar9ijb9heO+kAy0fm99QI3lHEt7Q+IR4cVeqz8m+8Vzpyh1XKkVcIu
8NcwlNU4eWaauWQ8L7cGigwPoWU+fAMrBi1Dtv9bDA8cjbItMkGnxlJ1R89TrgDak8FRLgsHTBYw
4H8XHrcKfkRb01AMzabsfGJy3RJSleeBSPR6ng7XUl4QmO0ZL8hiAAAAAAAA

--Apple-Mail=_7E69E3EA-DE0B-4FD6-8576-37651C4090B8--


From nobody Fri Mar 31 10:56:35 2017
Return-Path: <rraszuk@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 CB143129568; Fri, 31 Mar 2017 10:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGkheQfMFoED; Fri, 31 Mar 2017 10:56:27 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74E0E126D74; Fri, 31 Mar 2017 10:56:26 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id z13so44480616iof.2; Fri, 31 Mar 2017 10:56:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=fzKR1e2OsCNy4Ek48qoBUx9x52XLH44zrToeEo6mpbg=; b=Px2BJ/b/v0NJUvPEavbgQrbQ1qyAno9Ym8t2ucQKleKCcN+09k3hyaE4LhDPXnwx1A nT9daFow9q83+JahLYZBBfXPB3aKGWLP1BVMvB7Gj7358bhuBVYMqJl8hQiFJojHRaPH TOkwabAo+sUompJawmFrP8/7MiHRMedxDysEPRlhsuNsFiP0pKfEfLlkyTXGZv1jl/2z ytY3UyMLp8OMoPkvwHi/yxeo2KK3jtigYi6ykbp5Daw7sRzIT5OUOr3aePUKvAgYB5B8 r8lDx+bdJkjafn3tUiIRjfI6KfdiojLm3HDU4mufrYbK051V7IJu4NXB7yuldA5iFDhk M6lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=fzKR1e2OsCNy4Ek48qoBUx9x52XLH44zrToeEo6mpbg=; b=Ax5vudfZnbtzjAZA3f+vL0Ij4GDfxC0AZ+nqa4BArdx3jGGTpfB4/ud96Krhj4snD5 1DCqNEOBfH9e/ge2aFKwH4vQFehTcLW2KYfmQmTAfUd8C7pZYJgOscM+uvDRD08o16wn rYWZu2th2lEXpaLDRjP5wDNDtR9wDeAAwlss9fBkbxOOuvIcT6n9xot2YZHpXqspagpu iDqRASj3nfBye85SotsZ8DZjQeutTpEPze0CgbiG8pmJRIfzHxfjqKBFmIn8cjeKbeou bm9yauhx6xrLPkjeiVm90YHr252KmEUPhdoXThDY95QUf6fZxC4YXcYf/xaZjM+cABDa HItg==
X-Gm-Message-State: AFeK/H3ROiZZt0ut4zf9gYF08gcAx7MGqzGvG0purrjzlGJkTmpYF05KkmnVqLvIKWTlKvvkQtihLwNu4RMkfw==
X-Received: by 10.107.10.21 with SMTP id u21mr5001960ioi.139.1490982985839; Fri, 31 Mar 2017 10:56:25 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Fri, 31 Mar 2017 10:56:24 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Fri, 31 Mar 2017 10:56:24 -0700 (PDT)
In-Reply-To: <3A7C2C05-8513-4248-82F3-15CC9C75B69E@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <6C78BE2C-58B6-4A3A-B42A-C8A46D68B730@ericsson.com> <CA+b+ERk4mbHrTZi3JFKBh4RjUzN=SVUGONvFuEA5Ed178MzZmA@mail.gmail.com> <3A7C2C05-8513-4248-82F3-15CC9C75B69E@ericsson.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 31 Mar 2017 12:56:24 -0500
X-Google-Sender-Auth: otEm0LLn0BekkjZ_rRWP5Pu6ZoI
Message-ID: <CA+b+ERmchYvF9uexQZ-j752OPrtzr_TQgyDov7q01EvYe1ByWQ@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, otroan@employees.org,  IETF Discussion <ietf@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man WG <ipv6@ietf.org>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ed7663cbc4f054c0a8752
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0jCvpE85UvVdDyUHlFN-HKetZ2Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 17:56:29 -0000

--001a113ed7663cbc4f054c0a8752
Content-Type: text/plain; charset=UTF-8

Even if we treat encapsulation in new IPv6 header as only an option ?

Thx
R.



On Mar 31, 2017 12:46, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
wrote:

> Hi Robert,
>
> On Mar 31, 2017, at 12:01 PM, Robert Raszuk <robert@raszuk.net> wrote:
>
> Hi Suresh,
>
> As you requested one of many quotes from the draft which your
> clarification to 2460bis directly contradicts with:
>
> This include either:
>
>       A host originating an IPv6 packet.
>
>       *An SR domain ingress router encapsulating a received IPv6 packet
>       into an outer IPv6 header followed by an SRH.*
>
>
> Excellent. Thanks for pointing out the exact text. I can confirm that this
> text  *is compliant* with the RFC2460bis text.
>
> Thanks
> Suresh
>
>

--001a113ed7663cbc4f054c0a8752
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Even if we treat encapsulation in new IPv6 header as only=
 an option ?<div dir=3D"auto"><br></div><div dir=3D"auto">Thx</div><div dir=
=3D"auto">R.<br><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div></d=
iv></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mar 3=
1, 2017 12:46, &quot;Suresh Krishnan&quot; &lt;<a href=3D"mailto:suresh.kri=
shnan@ericsson.com">suresh.krishnan@ericsson.com</a>&gt; wrote:<br type=3D"=
attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-w=
ord">Hi Robert,<div><br><div><blockquote type=3D"cite"><div>On Mar 31, 2017=
, at 12:01 PM, Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net" targe=
t=3D"_blank">robert@raszuk.net</a>&gt; wrote:</div><br class=3D"m_-89535036=
49369433095Apple-interchange-newline"><div><div dir=3D"auto">Hi Suresh,<div=
 dir=3D"auto"><br></div><div dir=3D"auto">As you requested one of many quot=
es from the draft which your clarification to 2460bis directly contradicts =
with:</div><div dir=3D"auto"><br></div><div dir=3D"auto"><pre style=3D"font=
-size:12.6667px;margin-top:0px;margin-bottom:0px">This include either:

      A host originating an IPv6 packet.

      <b>An SR domain ingress router encapsulating a received IPv6 packet
      into an outer IPv6 header followed by an SRH.</b>
</pre></div></div></div></blockquote><div><br></div>Excellent. Thanks for p=
ointing out the exact text. I can confirm that this text =C2=A0*is complian=
t* with the RFC2460bis text.</div><div><br></div><div>Thanks</div><div>Sure=
sh</div><div><br></div></div></div></blockquote></div></div>

--001a113ed7663cbc4f054c0a8752--


From nobody Fri Mar 31 11:08:39 2017
Return-Path: <suresh.krishnan@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 93B32128DF6; Fri, 31 Mar 2017 11:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ydEAKCW9-ufE; Fri, 31 Mar 2017 11:08:30 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C84912943A; Fri, 31 Mar 2017 11:08:30 -0700 (PDT)
X-AuditID: c6180641-417ff700000058cf-92-58de54c20303
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id E9.3D.22735.2C45ED85; Fri, 31 Mar 2017 15:08:21 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0339.000; Fri, 31 Mar 2017 14:08:25 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Robert Raszuk <robert@raszuk.net>
CC: "Leddy, John" <John_Leddy@comcast.com>, Ole Troan <otroan@employees.org>,  IETF Discussion <ietf@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv86cghjjmGk6P6rsvHH5Q4qGssVmAgAD+BwCAAAesgIAAIVmAgAAFgwCAAASPgIAAEkGAgABB5oCAAAHpgIAAAteAgAACGICAAAp2gIABEiqAgAAWegCAABjkgIAADLGAgAACtQCAAANRAA==
Date: Fri, 31 Mar 2017 18:08:22 +0000
Message-ID: <0206BF42-1C7C-44F2-8F18-DC9ABB6DA746@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <6C78BE2C-58B6-4A3A-B42A-C8A46D68B730@ericsson.com> <CA+b+ERk4mbHrTZi3JFKBh4RjUzN=SVUGONvFuEA5Ed178MzZmA@mail.gmail.com> <3A7C2C05-8513-4248-82F3-15CC9C75B69E@ericsson.com> <CA+b+ERmchYvF9uexQZ-j752OPrtzr_TQgyDov7q01EvYe1ByWQ@mail.gmail.com>
In-Reply-To: <CA+b+ERmchYvF9uexQZ-j752OPrtzr_TQgyDov7q01EvYe1ByWQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_DA10ED56-F762-4E5F-B1F8-2CD5587EED8F"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAIsWRmVeSWpSXmKPExsUyuXRPgu7RkHsRBvenGlm0XdzHZPHq7TU2 i2cb57NYvDz7nsli6YLlTBaT21awWTQtbGJ2YPe43tnC7HHw2EdGj52z7rJ7LFnyk8lj98YF TAGsUVw2Kak5mWWpRfp2CVwZr6+1sxV8iqj4e/IaWwPjjcAuRg4OCQETiRmL/bsYuTiEBDYw ShzY2ssO4SxnlNiw+jiQw8nBBlS0YednJhBbREBVovPEI2aQImaBKUwSu5s2gxUJC3hITNp0 jQWiyFNi3cbDLCBFIgLLGCUaHneCFbEAdf+9fBnM5hWwl9g/5TIjxLpfHBIt1yawgiQ4BQIl 1p24xghiMwqISXw/tQZsNbOAuMStJ/PBbAkBEYmHF0+zQdiiEi8f/2OFsJUkPv6ezw51HqPE +mtrWCC2CUqcnPmEZQKjyCwks2Yhq5uFpA6iKEni+cP/rBC2tsSyha+ZIWxNif3dy1kwxTUk Or9NhKo3lXh99CMjhG0tMePXQTYIW1FiSvdD9gWM3KsYOUqLC3Jy040MNzEC4/6YBJvjDsa9 vZ6HGAU4GJV4eBdo3IsQYk0sK67MPcSoAtT6aMPqC4xSLHn5ealKIrwyOUBp3pTEyqrUovz4 otKc1OJDjNIcLErivO/KL0QICaQnlqRmp6YWpBbBZJk4OKUaGNX/XXtUv+Y+V4RV77TV9wQY u/yMHIpCVhfVKxaF5fCar7Ux2rZ28iEHWZ/qS0HitsdSv5l2LJ/p5MDwfl/iVOW/exdscXmx bp7S88PrdhxqWZSzNmw1l9SECdc//SluPCHMfiNmoYv9SrWwp15RbRu4J+334j4rsGX9x4BZ ufzPmOOfFD4V9VViKc5INNRiLipOBAA+jqD/AwMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iiWBUVk6Gln-cYZYkkKakadqQoE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 18:08:33 -0000

--Apple-Mail=_DA10ED56-F762-4E5F-B1F8-2CD5587EED8F
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_55ABD291-59C1-4DA4-B953-48E2B1BBE40E"


--Apple-Mail=_55ABD291-59C1-4DA4-B953-48E2B1BBE40E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Robert,

> On Mar 31, 2017, at 12:56 PM, Robert Raszuk <robert@raszuk.net> wrote:
>=20
> Even if we treat encapsulation in new IPv6 header as only an option ?

There are two options listed in the draft with the =E2=80=9Ceither=E2=80=9D=
 clause quoted below. Both of them are compliant. In fact, in my not so =
careful reading, I do not see any text in =
draft-ietf-6man-segment-routing-header-06 =
<https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06> =
that would be contrary to this text in RFC2460bis.

Thanks
Suresh

P.S.: I am assuming you are using the word option to mean a choice and =
not an IPv6 option. If not, please clarify.

>=20
> Thx
> R.
>=20
>=20
>=20
> On Mar 31, 2017 12:46, "Suresh Krishnan" <suresh.krishnan@ericsson.com =
<mailto:suresh.krishnan@ericsson.com>> wrote:
> Hi Robert,
>=20
>> On Mar 31, 2017, at 12:01 PM, Robert Raszuk <robert@raszuk.net =
<mailto:robert@raszuk.net>> wrote:
>>=20
>> Hi Suresh,
>>=20
>> As you requested one of many quotes from the draft which your =
clarification to 2460bis directly contradicts with:
>>=20
>> This include either:
>>=20
>>       A host originating an IPv6 packet.
>>=20
>>       An SR domain ingress router encapsulating a received IPv6 =
packet
>>       into an outer IPv6 header followed by an SRH.
>=20
> Excellent. Thanks for pointing out the exact text. I can confirm that =
this text  *is compliant* with the RFC2460bis text.
>=20
> Thanks
> Suresh
>=20


--Apple-Mail=_55ABD291-59C1-4DA4-B953-48E2B1BBE40E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Robert,<div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Mar 31, 2017, at 12:56 PM, =
Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net" =
class=3D"">robert@raszuk.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div dir=3D"auto" class=3D"">Even if we treat encapsulation =
in new IPv6 header as only an option ?</div></div></blockquote><div><br =
class=3D""></div>There are two options listed in the draft with the =
=E2=80=9Ceither=E2=80=9D clause quoted below. Both of them are =
compliant. In fact, in my not so careful reading, I do not see any text =
in&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header=
-06" style=3D"font-size: 13.333333015441895px;" =
class=3D"">draft-ietf-6man-segment-routing-header-06</a>&nbsp;that would =
be contrary to this text in RFC2460bis.</div><div><br =
class=3D""></div><div>Thanks</div><div>Suresh</div><div><br =
class=3D""></div><div>P.S.: I am assuming you are using the word option =
to mean a choice and not an IPv6 option. If not, please =
clarify.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"auto" class=3D""><div dir=3D"auto" =
class=3D""><br class=3D""></div><div dir=3D"auto" class=3D"">Thx</div><div=
 dir=3D"auto" class=3D"">R.<br class=3D""><div dir=3D"auto" class=3D""><br=
 class=3D""></div><div dir=3D"auto" class=3D""><br =
class=3D""></div></div></div><div class=3D"gmail_extra"><br =
class=3D""><div class=3D"gmail_quote">On Mar 31, 2017 12:46, "Suresh =
Krishnan" &lt;<a href=3D"mailto:suresh.krishnan@ericsson.com" =
class=3D"">suresh.krishnan@ericsson.com</a>&gt; wrote:<br =
type=3D"attribution" class=3D""><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div style=3D"word-wrap:break-word" class=3D"">Hi =
Robert,<div class=3D""><br class=3D""><div class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Mar 31, 2017, at 12:01 PM, =
Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net" target=3D"_blank" =
class=3D"">robert@raszuk.net</a>&gt; wrote:</div><br =
class=3D"m_-8953503649369433095Apple-interchange-newline"><div =
class=3D""><div dir=3D"auto" class=3D"">Hi Suresh,<div dir=3D"auto" =
class=3D""><br class=3D""></div><div dir=3D"auto" class=3D"">As you =
requested one of many quotes from the draft which your clarification to =
2460bis directly contradicts with:</div><div dir=3D"auto" class=3D""><br =
class=3D""></div><div dir=3D"auto" class=3D""><pre =
style=3D"font-size:12.6667px;margin-top:0px;margin-bottom:0px" =
class=3D"">This include either:

      A host originating an IPv6 packet.

      <b class=3D"">An SR domain ingress router encapsulating a received =
IPv6 packet
      into an outer IPv6 header followed by an SRH.</b>
</pre></div></div></div></blockquote><div class=3D""><br =
class=3D""></div>Excellent. Thanks for pointing out the exact text. I =
can confirm that this text &nbsp;*is compliant* with the RFC2460bis =
text.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks</div><div class=3D"">Suresh</div><div class=3D""><br =
class=3D""></div></div></div></blockquote></div></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_55ABD291-59C1-4DA4-B953-48E2B1BBE40E--

--Apple-Mail=_DA10ED56-F762-4E5F-B1F8-2CD5587EED8F
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMzMxMTgwODE3WjAjBgkqhkiG9w0B
CQQxFgQUOC6mk3JxnBMSP0zoSn2R8b4J3fgwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQCB6O5sMcRBsqkJ77SDK7L6h1MhXev0SJ/U/WfyB4T067mE9rp3s3E88W2YH/T/
NEXD4Ab7svg9dZiUF8p4vltzaVRV6daeZCzeiMZxmgZZGry8+Vg3BYd/zUp9SphtZiK6oxSeVzIi
cfIh3pMT1g1xV7NAPIxT4zxAFKqtI2Be7tNrDm8QU6Sr6VLpSXro84CxufYhkPRLElnOqsNVJqk2
5AmsfZbdAOAXA9zI8sUscr1GuSj91chRI1wQ90WgOScBVY+HMDtIgMqnQATPJWtkL/Ggc6PAWpnj
BB4X34h844zZONPQrijefe0j8lYFuzwlXtKbaJd/3LUgaAWb5sUwAAAAAAAA

--Apple-Mail=_DA10ED56-F762-4E5F-B1F8-2CD5587EED8F--


From nobody Fri Mar 31 11:14:13 2017
Return-Path: <rraszuk@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 3B8D11200C5; Fri, 31 Mar 2017 11:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKicYDbec0_4; Fri, 31 Mar 2017 11:14:10 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 999021299AC; Fri, 31 Mar 2017 11:14:08 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id y18so17723617itc.0; Fri, 31 Mar 2017 11:14:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=e9GDzSw9LZoVDZXq/8fJf4VqjAyzisgpM/tRNpfbeaM=; b=GqcPww3ayYLw7uQFm4cH4r2TIvV7bNs+gut8W3LKPBFqYyvIakJFmhdlX2fuizg0Hp DwaSoXbikT42bccZ9OcP78mRtvaIG3usRZYKgRvYWNzwXlioRaVI193RryVHztk61tSO QkNpkWj03Lf8oMZJx4cMbDYdwwkPOw4KM6/8hOQAHP+Y4CQAqBnKQsyUhnRrSE01rHHE gNQiErw1o7c6/PngL2zbjyb6VQECI/X8bFz10tT2O+M46EustMi7QO3nV2XkBmaxDOzN 0K+kiHaPSOM8TQDHYsX6urxwXfrfFJ/OMOS4TEfDeczlKF6OIxOoLbzvUSdiYkTOm5Ag C5Qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=e9GDzSw9LZoVDZXq/8fJf4VqjAyzisgpM/tRNpfbeaM=; b=qsBlFB3F4xKJgs1buAaviIf6x0k9iCWKPrBxmmi4Cvgo5WUlK6HmEaiW4HdmNJZYC9 fOGdmixQZNSaBUS0Rk7kLLxlFdBtWpl1Mj0/9ZRXdkKyqUiI9bCKnFyPQrG4UDLeglKj WNk4xTYpsumM6jpIMjO37FWcGekIBF6J3R3qmbKBzN1W519CA82MccukX1yjJnl2KxE0 X8KoQsO/x1z04mI7SyHwtHX1vEATcIfKzvSxejz6HjM1yVC/iG5RcLxg56tEbssg2KNP JkbFbBucl2o+PFcgYhEfOM29iVhZKnku5qKNwSMSuU9/xGxM9QZ+aHQLqeZRnZux5q1s ZoGw==
X-Gm-Message-State: AFeK/H2E1NHyCj5HAbtSKMGpjcJAW96BmSQE6pzUirjCfRHU/IZPMCK96432Xessap+5r+uXmRn02O7TusJ4aQ==
X-Received: by 10.36.46.81 with SMTP id i78mr5421651ita.39.1490984047915; Fri, 31 Mar 2017 11:14:07 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Fri, 31 Mar 2017 11:14:06 -0700 (PDT)
Received: by 10.79.90.71 with HTTP; Fri, 31 Mar 2017 11:14:06 -0700 (PDT)
In-Reply-To: <0206BF42-1C7C-44F2-8F18-DC9ABB6DA746@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <6C78BE2C-58B6-4A3A-B42A-C8A46D68B730@ericsson.com> <CA+b+ERk4mbHrTZi3JFKBh4RjUzN=SVUGONvFuEA5Ed178MzZmA@mail.gmail.com> <3A7C2C05-8513-4248-82F3-15CC9C75B69E@ericsson.com> <CA+b+ERmchYvF9uexQZ-j752OPrtzr_TQgyDov7q01EvYe1ByWQ@mail.gmail.com> <0206BF42-1C7C-44F2-8F18-DC9ABB6DA746@ericsson.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 31 Mar 2017 13:14:06 -0500
X-Google-Sender-Auth: 3hXVJHe969Fm_-3tR3x3yxa5hmg
Message-ID: <CA+b+ERmL_J3O8VRQikXcb0LQ8TXW2RUg4mOK3MkVS0Sj+NqasQ@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, otroan@employees.org,  IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>,  Brian E Carpenter <brian.e.carpenter@gmail.com>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a114a93ce8abcfc054c0ac60a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wptnGaB9onu38hj33JHswNqDcxY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 18:14:12 -0000

--001a114a93ce8abcfc054c0ac60a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Suresh,

The fact that encapsulation in new v6 header is optional to me is clearly
stated in section 4.1 of that document:

 By default, a local SID bound to the End function does not allow
      the decapsulation of an outer header.  As a consequence, an End
      SID cannot be the last SID of an SRH and cannot be the DA of a
      packet without SRH.

   o  If the decapsulation is desired, then another function must be
      bound to the SID (e.g., End.DX6 defined in
      [I-D.filsfils-spring-srv6-network-programming
<https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06#ref-=
I-D.filsfils-spring-srv6-network-programming>]).
This prevents
      any unintentional decapsulation by the segment endpoint node.  The
      details of the advertisement of a SID in the control plane are
      outside the scope of this document (e.g.,
      [I-D.previdi-idr-segment-routing-te-policy
<https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06#ref-=
I-D.previdi-idr-segment-routing-te-policy>],
      [I-D.dawra-bgp-srv6-vpn
<https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06#ref-=
I-D.dawra-bgp-srv6-vpn>]
and [I-D.bashandy-isis-srv6-extensions
<https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06#ref-=
I-D.bashandy-isis-srv6-extensions>].


On Mar 31, 2017 13:08, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
wrote:

> Hi Robert,
>
> On Mar 31, 2017, at 12:56 PM, Robert Raszuk <robert@raszuk.net> wrote:
>
> Even if we treat encapsulation in new IPv6 header as only an option ?
>
>
> There are two options listed in the draft with the =E2=80=9Ceither=E2=80=
=9D clause quoted
> below. Both of them are compliant. In fact, in my not so careful reading,=
 I
> do not see any text in draft-ietf-6man-segment-routing-header-06
> <https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06> t=
hat
> would be contrary to this text in RFC2460bis.
>
> Thanks
> Suresh
>
> P.S.: I am assuming you are using the word option to mean a choice and no=
t
> an IPv6 option. If not, please clarify.
>
>
> Thx
> R.
>
>
>
> On Mar 31, 2017 12:46, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
> wrote:
>
>> Hi Robert,
>>
>> On Mar 31, 2017, at 12:01 PM, Robert Raszuk <robert@raszuk.net> wrote:
>>
>> Hi Suresh,
>>
>> As you requested one of many quotes from the draft which your
>> clarification to 2460bis directly contradicts with:
>>
>> This include either:
>>
>>       A host originating an IPv6 packet.
>>
>>       *An SR domain ingress router encapsulating a received IPv6 packet
>>       into an outer IPv6 header followed by an SRH.*
>>
>>
>> Excellent. Thanks for pointing out the exact text. I can confirm that
>> this text  *is compliant* with the RFC2460bis text.
>>
>> Thanks
>> Suresh
>>
>>
>

--001a114a93ce8abcfc054c0ac60a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Suresh,<div dir=3D"auto"><br></div><div dir=3D"auto">T=
he fact that encapsulation in new v6 header is optional to me is clearly st=
ated in section 4.1 of that document:</div><div dir=3D"auto"><br></div><div=
 dir=3D"auto"><pre style=3D"font-size:12.6667px;margin-top:0px;margin-botto=
m:0px"> By default, a local SID bound to the End function does not allow
      the decapsulation of an outer header.  As a consequence, an End
      SID cannot be the last SID of an SRH and cannot be the DA of a
      packet without SRH.

   o  If the decapsulation is desired, then another function must be
      bound to the SID (e.g., End.DX6 defined in
      [<a href=3D"https://tools.ietf.org/html/draft-ietf-6man-segment-routi=
ng-header-06#ref-I-D.filsfils-spring-srv6-network-programming">I-D.filsfils=
-spring-srv6-network-programming</a>]).  This prevents
      any unintentional decapsulation by the segment endpoint node.  The
      details of the advertisement of a SID in the control plane are
      outside the scope of this document (e.g.,
      [<a href=3D"https://tools.ietf.org/html/draft-ietf-6man-segment-routi=
ng-header-06#ref-I-D.previdi-idr-segment-routing-te-policy">I-D.previdi-idr=
-segment-routing-te-policy</a>],
      [<a href=3D"https://tools.ietf.org/html/draft-ietf-6man-segment-routi=
ng-header-06#ref-I-D.dawra-bgp-srv6-vpn">I-D.dawra-bgp-srv6-vpn</a>] and [<=
a href=3D"https://tools.ietf.org/html/draft-ietf-6man-segment-routing-heade=
r-06#ref-I-D.bashandy-isis-srv6-extensions">I-D.bashandy-isis-srv6-extensio=
ns</a>].</pre></div></div><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Mar 31, 2017 13:08, &quot;Suresh Krishnan&quot; &lt;<a href=3D"=
mailto:suresh.krishnan@ericsson.com">suresh.krishnan@ericsson.com</a>&gt; w=
rote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"=
word-wrap:break-word">Hi Robert,<div><br><div><blockquote type=3D"cite"><di=
v>On Mar 31, 2017, at 12:56 PM, Robert Raszuk &lt;<a href=3D"mailto:robert@=
raszuk.net" target=3D"_blank">robert@raszuk.net</a>&gt; wrote:</div><br cla=
ss=3D"m_3663391138060280880Apple-interchange-newline"><div><div dir=3D"auto=
">Even if we treat encapsulation in new IPv6 header as only an option ?</di=
v></div></blockquote><div><br></div>There are two options listed in the dra=
ft with the =E2=80=9Ceither=E2=80=9D clause quoted below. Both of them are =
compliant. In fact, in my not so careful reading, I do not see any text in=
=C2=A0<a href=3D"https://tools.ietf.org/html/draft-ietf-6man-segment-routin=
g-header-06" style=3D"font-size:13.333333015441895px" target=3D"_blank">dra=
ft-ietf-6man-segment-<wbr>routing-header-06</a>=C2=A0that would be contrary=
 to this text in RFC2460bis.</div><div><br></div><div>Thanks</div><div>Sure=
sh</div><div><br></div><div>P.S.: I am assuming you are using the word opti=
on to mean a choice and not an IPv6 option. If not, please clarify.</div><d=
iv><br><blockquote type=3D"cite"><div><div dir=3D"auto"><div dir=3D"auto"><=
br></div><div dir=3D"auto">Thx</div><div dir=3D"auto">R.<br><div dir=3D"aut=
o"><br></div><div dir=3D"auto"><br></div></div></div><div class=3D"gmail_ex=
tra"><br><div class=3D"gmail_quote">On Mar 31, 2017 12:46, &quot;Suresh Kri=
shnan&quot; &lt;<a href=3D"mailto:suresh.krishnan@ericsson.com" target=3D"_=
blank">suresh.krishnan@ericsson.com</a>&gt; wrote:<br type=3D"attribution">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word">Hi Rober=
t,<div><br><div><blockquote type=3D"cite"><div>On Mar 31, 2017, at 12:01 PM=
, Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net" target=3D"_blank">=
robert@raszuk.net</a>&gt; wrote:</div><br class=3D"m_3663391138060280880m_-=
8953503649369433095Apple-interchange-newline"><div><div dir=3D"auto">Hi Sur=
esh,<div dir=3D"auto"><br></div><div dir=3D"auto">As you requested one of m=
any quotes from the draft which your clarification to 2460bis directly cont=
radicts with:</div><div dir=3D"auto"><br></div><div dir=3D"auto"><pre style=
=3D"font-size:12.6667px;margin-top:0px;margin-bottom:0px">This include eith=
er:

      A host originating an IPv6 packet.

      <b>An SR domain ingress router encapsulating a received IPv6 packet
      into an outer IPv6 header followed by an SRH.</b>
</pre></div></div></div></blockquote><div><br></div>Excellent. Thanks for p=
ointing out the exact text. I can confirm that this text =C2=A0*is complian=
t* with the RFC2460bis text.</div><div><br></div><div>Thanks</div><div>Sure=
sh</div><div><br></div></div></div></blockquote></div></div>
</div></blockquote></div><br></div></div></blockquote></div></div>

--001a114a93ce8abcfc054c0ac60a--


From nobody Fri Mar 31 11:18:55 2017
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 33D82126DFB; Fri, 31 Mar 2017 11:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqvI5mmhVYLH; Fri, 31 Mar 2017 11:18:46 -0700 (PDT)
Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36C02120725; Fri, 31 Mar 2017 11:18:46 -0700 (PDT)
Received: by mail-it0-x244.google.com with SMTP id e75so2797131itd.1; Fri, 31 Mar 2017 11:18:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=OXx02gTkEjtTOC68+xl7oUQBokNg7HenrItSxIx7BZo=; b=NNlR6F+CtcP9eaa+IQeoQKcIrGenqbIIANKS1h78REdZW2QyWmP5kRh9Vg/NdSWx0W B6e2V/Lgdy/qLu4EaSz7S07gr41/Oqj56iJmnuTv7xL4EgZTsnoWvjBElMMK3AyaAuQH ZUkkCvlgmKeTsY5X7/+NpO0kczXUnttNJmPZ0zYFUyJF7gTnFZUQLr8rjgdlI4viV1Ec PKIMguS+TSdjRcDwPwMDUtg3FDFeUz/ES8FhCfn/uOSt/QVEKIWYoK43IyKH3RABSgYS ufGHVDoObFZnv6kVHTZmqVaQt0RBMSrSAXxq5weVUiOQOOq/LjAHszTZG3gwyVJ+LwnO Mdow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=OXx02gTkEjtTOC68+xl7oUQBokNg7HenrItSxIx7BZo=; b=RsxbjydjBA7wJ7Db08rGZdaCgUfJSI3Eijfs/qRdu31TRkUy0RfZeS1YPbVKt3M6fQ Z4l3T8AsJ7MP0aP6mQCmIJNyKD2rMF/T/GWP723Yb7vRFuXSBl0Ca+BMySEEu8s3KmLl 44whVMg2l668V9G1j5XUstJsxtMUKqOS2f7hEZ4n6H3/z4qbqjsaYbA6ithkIAlzTqtQ HGnotffKOPh3AsdIlC/IY9U5dRPIeW6bXklNzEuYME51zfj+WL93tAwzLx7eJmpIp42z Tgk9ik0fwLBcN2vH/8JMpTabmduhsKqV+IDxX8EpwxZpSup7soqDXyaQgt8SUJ6WvnvO KL5w==
X-Gm-Message-State: AFeK/H1l/6zgWl+m/XGgAKN8poyU40GTfWFAEDMlUi/jIBj1ZiYCBf8J5vWYkVM4/DJRIw==
X-Received: by 10.36.0.198 with SMTP id 189mr5503452ita.82.1490984325587; Fri, 31 Mar 2017 11:18:45 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:28cc:dc4c:9703:6781? (t2001067c0370012828ccdc4c97036781.v6.meeting.ietf.org. [2001:67c:370:128:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id n73sm3538071ioe.10.2017.03.31.11.18.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Mar 2017 11:18:44 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Robert Raszuk <robert@raszuk.net>, Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <6C78BE2C-58B6-4A3A-B42A-C8A46D68B730@ericsson.com> <CA+b+ERk4mbHrTZi3JFKBh4RjUzN=SVUGONvFuEA5Ed178MzZmA@mail.gmail.com> <3A7C2C05-8513-4248-82F3-15CC9C75B69E@ericsson.com> <CA+b+ERmchYvF9uexQZ-j752OPrtzr_TQgyDov7q01EvYe1ByWQ@mail.gmail.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, otroan@employees.org, IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b1109215-0bc9-188e-3df7-92a0f67e9566@gmail.com>
Date: Sat, 1 Apr 2017 07:18:54 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CA+b+ERmchYvF9uexQZ-j752OPrtzr_TQgyDov7q01EvYe1ByWQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jIHynLPGavYqLg8vH6PogH6hGoE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 18:18:48 -0000

Robert,

Actually this was thoroughly discussed (mainly with Stefano I think)
and these texts in draft-ietf-6man-segment-routing-header-06 were
carefully designed to be compatible with both RFC2460 and RFC2460bis:

Section 2.3.1:
>  The outer header with the SRH is no different from any other
>  tunneling encapsulation mechanism and allows a network operator to
>  implement traffic engineering mechanisms so to efficiently steer
>  traffic across his infrastructure.
 
Section 5.1:
>  A Source SR Node can be any node originating an IPv6 packet with its
>  IPv6 and Segment Routing Headers.  This include either:
> 
>     A host originating an IPv6 packet.
> 
>     An SR domain ingress router encapsulating a received IPv6 packet
>     into an outer IPv6 header followed by an SRH.

I suppose we need expert review of the routing header itself, but
for me there is simply no issue about compatibility with 2460(bis).

(draft-voyer-6man-extension-header-insertion is a quite different
conversation and we should not confuse the two. That would be FUD.)

Regards
   Brian

On 01/04/2017 06:56, Robert Raszuk wrote:
> Even if we treat encapsulation in new IPv6 header as only an option ?
> 
> Thx
> R.
> 
> 
> 
> On Mar 31, 2017 12:46, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
> wrote:
> 
>> Hi Robert,
>>
>> On Mar 31, 2017, at 12:01 PM, Robert Raszuk <robert@raszuk.net> wrote:
>>
>> Hi Suresh,
>>
>> As you requested one of many quotes from the draft which your
>> clarification to 2460bis directly contradicts with:
>>
>> This include either:
>>
>>       A host originating an IPv6 packet.
>>
>>       *An SR domain ingress router encapsulating a received IPv6 packet
>>       into an outer IPv6 header followed by an SRH.*
>>
>>
>> Excellent. Thanks for pointing out the exact text. I can confirm that this
>> text  *is compliant* with the RFC2460bis text.
>>
>> Thanks
>> Suresh
>>
>>
> 


From nobody Fri Mar 31 11:35:31 2017
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 7281212945F; Fri, 31 Mar 2017 11:35:29 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T5f5Zj8AJ7G2; Fri, 31 Mar 2017 11:35:27 -0700 (PDT)
Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0F2B126B71; Fri, 31 Mar 2017 11:35:26 -0700 (PDT)
Received: by mail-io0-x242.google.com with SMTP id f103so6687429ioi.2; Fri, 31 Mar 2017 11:35:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=sDMdb0NZ2SurtAK9PGMUIE16I+bMTPjorljEyyDoT9c=; b=Bg5in8An6ADxA5yMfR0/hkpq53mRZiAnyTaDjJnLSOERCrv8B+WSDz6TGOYpXBtD6f EG2EkNZxzwA+/T3wPTIene+jLuQdmMIRUDOjVpXcFO9mLeTtid/APRCSpTAey75QWKJq l71DyVuV5yX6ky/Mb6OMIf8Wax6OFK35HKUNA7K3cCfFan4TdnX07ViNyXx0wbI7SOM3 +PZGc2Q/JrQfmckDBwc345vC1bk65Iptt1aNYeq+Wnl3LUVeEZ0N8VkpgiBJU4szLeaG 4mcS+InbtcFVCGuzry6abH2rZXZYm1qPyQuiK1uzJFb8ZZ32SR7KoyaSxx68VU8ObukD ve9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=sDMdb0NZ2SurtAK9PGMUIE16I+bMTPjorljEyyDoT9c=; b=LqYvTRmcfZqhoUeQnz57YmvCl4oUUnmxnv04/vl7aB16t6HlT6Lc8StpoV0EorDJv1 kYPyJGD2IcomW+utw4QGgv5E8NiSd0Th4MpsegDozh1R1JTekdpcdTQ10T/4mvwNXYrm i1md+7m72IoKUlcexfuiMMtnzvE/X+CI0sFILDaKQx7tYLctvc9skCiqPh0AV/8IJZLj uCWL2a7BkO7rCs3Cw+1XX6A6Bjg6zRDlesjEMNRJ7qgL3htck4J5BcxqLHgTezoylKRd MU5fj5y2YCgxJWby2Fa8qA23Sx8z+vPRafBtbUG7UPc9YtfYtOJx1yNGcHZ1zM7cydhI P/5w==
X-Gm-Message-State: AFeK/H2ofx3GmXTPCqD06jLToXURgnKzMha8mq3CgzSsvnyq97TcS4O9u/bga0zeyCb/zA==
X-Received: by 10.107.1.16 with SMTP id 16mr5311052iob.44.1490985326260; Fri, 31 Mar 2017 11:35:26 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:28cc:dc4c:9703:6781? (t2001067c0370012828ccdc4c97036781.v6.meeting.ietf.org. [2001:67c:370:128:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id k63sm3556143ioi.19.2017.03.31.11.35.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Mar 2017 11:35:25 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Robert Raszuk <robert@raszuk.net>, Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <6C78BE2C-58B6-4A3A-B42A-C8A46D68B730@ericsson.com> <CA+b+ERk4mbHrTZi3JFKBh4RjUzN=SVUGONvFuEA5Ed178MzZmA@mail.gmail.com> <3A7C2C05-8513-4248-82F3-15CC9C75B69E@ericsson.com> <CA+b+ERmchYvF9uexQZ-j752OPrtzr_TQgyDov7q01EvYe1ByWQ@mail.gmail.com> <0206BF42-1C7C-44F2-8F18-DC9ABB6DA746@ericsson.com> <CA+b+ERmL_J3O8VRQikXcb0LQ8TXW2RUg4mOK3MkVS0Sj+NqasQ@mail.gmail.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, otroan@employees.org, IETF Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <1eb66a47-9bcc-ea5b-ae6a-35243aa99e87@gmail.com>
Date: Sat, 1 Apr 2017 07:35:34 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CA+b+ERmL_J3O8VRQikXcb0LQ8TXW2RUg4mOK3MkVS0Sj+NqasQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FyDO26qTlunxc9dBbnIsD5i60O0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 18:35:29 -0000

On 01/04/2017 07:14, Robert Raszuk wrote:
> Hi Suresh,
>=20
> The fact that encapsulation in new v6 header is optional to me is clear=
ly
> stated in section 4.1 of that document:
>=20
>  By default, a local SID bound to the End function does not allow
>       the decapsulation of an outer header.  As a consequence, an End
>       SID cannot be the last SID of an SRH and cannot be the DA of a
>       packet without SRH.
>=20
>    o  If the decapsulation is desired, then another function must be
>       bound to the SID=20

Sure, any tunnel needs a decapsulator as well as an encapsulator. That's
not news, so what is the problem here? I assume you'd decapsulate in
the last hop router. I don't claim to understand segment routing, so
I can't actually understand the above text. But the text elsewhere
is clear enough that either the original source or the encapsulator
builds the routing header, and that's all we need to know for
2460(bis) compatibility. So why are we still discussing?

    Brian

> (e.g., End.DX6 defined in
>       [I-D.filsfils-spring-srv6-network-programming
> <https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06#=
ref-I-D.filsfils-spring-srv6-network-programming>]).
> This prevents
>       any unintentional decapsulation by the segment endpoint node.  Th=
e
>       details of the advertisement of a SID in the control plane are
>       outside the scope of this document (e.g.,
>       [I-D.previdi-idr-segment-routing-te-policy
> <https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06#=
ref-I-D.previdi-idr-segment-routing-te-policy>],
>       [I-D.dawra-bgp-srv6-vpn
> <https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06#=
ref-I-D.dawra-bgp-srv6-vpn>]
> and [I-D.bashandy-isis-srv6-extensions
> <https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06#=
ref-I-D.bashandy-isis-srv6-extensions>].
>=20
>=20
> On Mar 31, 2017 13:08, "Suresh Krishnan" <suresh.krishnan@ericsson.com>=

> wrote:
>=20
>> Hi Robert,
>>
>> On Mar 31, 2017, at 12:56 PM, Robert Raszuk <robert@raszuk.net> wrote:=

>>
>> Even if we treat encapsulation in new IPv6 header as only an option ?
>>
>>
>> There are two options listed in the draft with the =E2=80=9Ceither=E2=80=
=9D clause quoted
>> below. Both of them are compliant. In fact, in my not so careful readi=
ng, I
>> do not see any text in draft-ietf-6man-segment-routing-header-06
>> <https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06=
> that
>> would be contrary to this text in RFC2460bis.
>>
>> Thanks
>> Suresh
>>
>> P.S.: I am assuming you are using the word option to mean a choice and=
 not
>> an IPv6 option. If not, please clarify.
>>
>>
>> Thx
>> R.
>>
>>
>>
>> On Mar 31, 2017 12:46, "Suresh Krishnan" <suresh.krishnan@ericsson.com=
>
>> wrote:
>>
>>> Hi Robert,
>>>
>>> On Mar 31, 2017, at 12:01 PM, Robert Raszuk <robert@raszuk.net> wrote=
:
>>>
>>> Hi Suresh,
>>>
>>> As you requested one of many quotes from the draft which your
>>> clarification to 2460bis directly contradicts with:
>>>
>>> This include either:
>>>
>>>       A host originating an IPv6 packet.
>>>
>>>       *An SR domain ingress router encapsulating a received IPv6 pack=
et
>>>       into an outer IPv6 header followed by an SRH.*
>>>
>>>
>>> Excellent. Thanks for pointing out the exact text. I can confirm that=

>>> this text  *is compliant* with the RFC2460bis text.
>>>
>>> Thanks
>>> Suresh
>>>
>>>
>>
>=20


From nobody Fri Mar 31 12:27:43 2017
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 017031294AA; Fri, 31 Mar 2017 12:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O5u6H-Uf7PoH; Fri, 31 Mar 2017 12:27:33 -0700 (PDT)
Received: from smtpde02.smtp.sap-ag.de (smtpde02.smtp.sap-ag.de [155.56.68.140]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4A5A1294F3; Fri, 31 Mar 2017 12:27:29 -0700 (PDT)
Received: from mail07.wdf.sap.corp (mail04.sap.corp [194.39.131.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde02.smtp.sap-ag.de (Postfix) with ESMTPS id 3vvs2l6QVDz271q; Fri, 31 Mar 2017 21:27:27 +0200 (CEST)
X-purgate-ID: 152705::1490988447-00002B31-CC3EDB7B/0/0
X-purgate-size: 579
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail07.wdf.sap.corp (Postfix) with ESMTP id 3vvs2l18NczGpLg; Fri, 31 Mar 2017 21:27:27 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 214C51A667; Fri, 31 Mar 2017 21:27:27 +0200 (CEST)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
In-Reply-To: <CA+b+ERkDzVvhqr9a0zpRLK3mLfKjOCVJ+3TDw0kQAg+Gvr762Q@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Date: Fri, 31 Mar 2017 21:27:27 +0200 (CEST)
CC: "Ackermann, Michael" <MAckermann@bcbsm.com>,  "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>,  IETF Discussion <ietf@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Reply-To: mrex@sap.com
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: <20170331192727.214C51A667@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uLrPEOpiZOEFptaAmTuaUzVtvCE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 19:27:36 -0000

Robert Raszuk wrote:
> 
> 
> SRv6 is a first serious consideration why number of enterprise networks
> would benefit from and could consider IPv6 rollout.

Are you "back from the future" and accidentally confusing dreams with
what is currently available?  ;-)


https://www.theregister.co.uk/2017/01/19/windows_10_bug_undercuts_ipv6_rollout/

  "The horrible irony of Microsoft waiting on its own team to fix
   a networking bug aside, the post goes some way to highlighting
   why it is that IPv6 is still not widely available: because it's a mess."


-Martin


From nobody Fri Mar 31 13:32:25 2017
Return-Path: <finlayson@live555.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DE1F129968 for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 13:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AchUCwq8UIOy for <ietf@ietfa.amsl.com>; Fri, 31 Mar 2017 13:32:22 -0700 (PDT)
Received: from ns.live555.com (ns.live555.com [4.79.217.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 386871299E1 for <ietf@ietf.org>; Fri, 31 Mar 2017 13:32:21 -0700 (PDT)
Received: from [127.0.0.1] (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.15.2/8.15.2) with ESMTP id v2VKWIcH046925; Fri, 31 Mar 2017 13:32:18 -0700 (PDT) (envelope-from finlayson@live555.com)
X-Authentication-Warning: ns.live555.com: Host localhost.live555.com [127.0.0.1] claimed to be [127.0.0.1]
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IAOC requesting input on (potential) meeting cities
From: Ross Finlayson <finlayson@live555.com>
In-Reply-To: <m2a8811lvu.wl-randy@psg.com>
Date: Fri, 31 Mar 2017 13:32:18 -0700
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C08BC5EC-6727-4266-8928-2531850BBF7F@live555.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <87C934A6-A4A8-41A4-A849-B0EDE8D234FF@gmail.com> <m2a8811lvu.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DB8sTa--ik0yroMzD66wJ_88A68>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 20:32:23 -0000

> On Mar 31, 2017, at 8:55 AM, Randy Bush <randy@psg.com> wrote:
>=20
>>> Please send input to venue-selection@ietf.org.
>=20
> so, i am curious.  do people
>  o think their imput is more important than that of we small people,
>  o can't read or follow instructions,
>  o or some other thing i do not understand?

Probably a combination of (1) and (2) - but it=E2=80=99s a pity that the =
OP (original poster) didn=E2=80=99t set the =E2=80=9CReply-To:=E2=80=9D =
header in their email.  That would have been a perfect use for it.

	Ross.


From nobody Fri Mar 31 16:58:38 2017
Return-Path: <stewart.bryant@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 94F5D1288B8; Fri, 31 Mar 2017 16:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GKUBLYKnpGx2; Fri, 31 Mar 2017 16:58:35 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C606412025C; Fri, 31 Mar 2017 16:58:34 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id y18so21808518itc.0; Fri, 31 Mar 2017 16:58:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=hKY6O6VIf6bp5pREjkB+ibOIrg7hPWAJqGa+qYPFV7w=; b=ubDyZqpc0iD1X1P32fjcOuqdF1c+1r+YSngy8SHIKFtIqsKzK8pZVfwAxygKbW9rz3 dAmJm+VN96+cBZquqtpZmeGZelXjbuyjLe/j9qNGB1e5+UvMY2dq2K/vQ+TIc2RbgE5A IlZ7/HfqehobiE8gBVBm7Y932UbyVUy4EvrHzHRgx15N64goIFL6tcAyRHFdQK4pbRpl xM6Roeu7VaTM18uqs+FEKS6ZZNNXsYP3RE/Eo99eQBek306Wht0pMgUa0/kKoAgFuvED eJETAOpN+hkVkWtxU7TR/lhNISPt361zs793bXQHW6pDpJK8m+FNpi8qgVF5Wkv4C2fp nMsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=hKY6O6VIf6bp5pREjkB+ibOIrg7hPWAJqGa+qYPFV7w=; b=dRDxaHwnpDR8XNR/+x9tSI+03OjYtLfoLlfxZBcWmYz7Ah890j1KQBydixX+4mx8fW b5CWUmnmyxFz0nGzpugm2ykGnE8Ygx079cwiEkpsPJMODapHwPY2UtELBDm5M9ynx2DO LFVIOTG/C3HjVAbge3lg7INW2bOmsUu+b/KzGom6A2dnsu/KKsDiYSzIs8OBcglEIDBm E+14hlGv+49MGcprDSzQ/GkwfnKw/yvlscDuUX9gcXXubD/2Jz4OTn4FthZvw0J+Qkmm OFr3e/BwJy+9s1FyPuOfViAuX+EGzWG6rygUqSERGmoxEDmbNkEfuK7H0QekNR7LLsxP NMOw==
X-Gm-Message-State: AFeK/H3WFFjkEK0+EhwlVtmsZNUcClZgiDNfAVESKcsC8AK/CctEU7/0 tosgc0oe/iaoI7v0uFo=
X-Received: by 10.36.138.65 with SMTP id v62mr464531itd.108.1491004714023; Fri, 31 Mar 2017 16:58:34 -0700 (PDT)
Received: from [172.20.7.142] (swissotel07.s.subnet.rcn.com. [216.80.61.6]) by smtp.gmail.com with ESMTPSA id n73sm4009703ioe.10.2017.03.31.16.58.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Mar 2017 16:58:33 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Eliot Lear <lear@cisco.com>, ietf@ietf.org, venue-selection@ietf.org
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <eb1bb52f-490f-a04d-64cc-a7522cd4835c@gmail.com>
Date: Sat, 1 Apr 2017 00:58:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DG6pg7ak_DEkjGYnDsGNrd2e0tI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Mar 2017 23:58:37 -0000

On 31/03/2017 15:42, Eliot Lear wrote:
> Hi,
>
>
> On 3/31/17 9:18 AM, IAOC Chair wrote:
>> The IAOC remains committed to soliciting input on future IETF meeting locations. With this mail, we are soliciting input on some potential IETF locations, including one where we have met before, but for which conditions may have changed.
>>
>> Specifically, we seek community input on reasons we could not have a successful meeting in any of the following cities, or of any limits to attendee accessibility or inclusiveness that should be considered:
>>
>> Ottawa
>> San Francisco
>> Austin, TX
>> Barcelona
>> Boston
>> Busan - looks expensive to get to
>> Calgary - also looks expensive to get to
>> Denver
>> Helsinki
>> Houston
>> New Orleans
>> Osaka
>> Philadelphia
>> Washington DC
>
To save everyone doing it, it would be good to show representative 
airfares and times from a major hub in Europe, East and West Coast, and Asia

I am sure cost and travel time will impact acceptability.

- Stewart

