Re: [tram] Adam Roach's Discuss on draft-ietf-tram-stun-pmtud-10: (with DISCUSS and COMMENT)

Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> Mon, 08 April 2019 10:37 UTC

Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23EEF12004F; Mon, 8 Apr 2019 03:37:57 -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, DKIMWL_WL_HIGH=-0.001, 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=ericsson.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 kSSrLHlEliDN; Mon, 8 Apr 2019 03:37:55 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40076.outbound.protection.outlook.com [40.107.4.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00653120019; Mon, 8 Apr 2019 03:37:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3uZbhaS8BEkEN6ClIZLGTNW5QxrmSlGrEQOx7cn1VLM=; b=J1jqgZOA8UZkeiLUVSpo/hoEDqo34IcjoLY8b/u0tCz6Q/qbWYX9d7M+XHQpMYDAkbbBjieieKZ8wW7DWxjBoI+LiK1ZYJ2YozJdW+WmDtaakVp3aCqml9KqLNMdywAqtbJHqSvPJT1Wt5u+ApRZSCwrvLfJtQv0udVlhBeah8M=
Received: from HE1PR0702MB3689.eurprd07.prod.outlook.com (52.133.6.143) by HE1PR0702MB3563.eurprd07.prod.outlook.com (52.133.6.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.11; Mon, 8 Apr 2019 10:37:52 +0000
Received: from HE1PR0702MB3689.eurprd07.prod.outlook.com ([fe80::8016:9a82:4ff3:a264]) by HE1PR0702MB3689.eurprd07.prod.outlook.com ([fe80::8016:9a82:4ff3:a264%6]) with mapi id 15.20.1792.007; Mon, 8 Apr 2019 10:37:52 +0000
From: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
CC: IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>, "draft-ietf-tram-stun-pmtud@ietf.org" <draft-ietf-tram-stun-pmtud@ietf.org>, "Asveren, Tolga" <tasveren@rbbn.com>, "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] Adam Roach's Discuss on draft-ietf-tram-stun-pmtud-10: (with DISCUSS and COMMENT)
Thread-Index: AQHUkuV9WRgg08P2B0upj6+dKkdDsg==
Date: Mon, 8 Apr 2019 10:37:52 +0000
Message-ID: <HE1PR0702MB3689CBA26E11064001B01227832C0@HE1PR0702MB3689.eurprd07.prod.outlook.com>
References: <153834237082.13405.1228259718885034461.idtracker@ietfa.amsl.com> <CAKKJt-fouMOJa+eGUwEmQL+Uv5Fqe5KNM_fC0YxmhYojpFNzaA@mail.gmail.com> <CA447D15-2E65-4340-9FF5-4700A53335ED@logmein.com> <CAKKJt-cG=R5ide_qHx5hNKbYwxhDKmwk0tOQutNPYBJp8L7HUA@mail.gmail.com> <MWHPR15MB1200F7BE766A80509FBFBE75FAA00@MWHPR15MB1200.namprd15.prod.outlook.com> <CAKKJt-eXBSJQeKkvNDhhFrpoOkwZvO=GYsZshh6=50htiHKnGw@mail.gmail.com> <VI1PR07MB61277B1650EE2008D81F0F4E83800@VI1PR07MB6127.eurprd07.prod.outlook.com> <CAKKJt-ewHuocx7nfohdr0+7V2XDmFxTWOVXLffmKAd_QoOpdmA@mail.gmail.com> <2EE82D0D-5024-4C71-8F25-0506D5530814@cisco.com> <VI1PR07MB5421C9288884AE5513D64A5083630@VI1PR07MB5421.eurprd07.prod.outlook.com> <E6DA48D1-A520-4AEE-842C-19F059921E32@cisco.com> <487146f2-f343-3c56-aeca-2e3fcfe54675@ericsson.com> <5A81A440-4ABF-4818-A1AE-83F5EF78D0EF@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com;
x-originating-ip: [37.136.23.131]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4b37de99-6dbd-4c2c-a9e7-08d6bc0e40ec
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:HE1PR0702MB3563;
x-ms-traffictypediagnostic: HE1PR0702MB3563:
x-microsoft-antispam-prvs: <HE1PR0702MB3563CC23695412ECA5221555832C0@HE1PR0702MB3563.eurprd07.prod.outlook.com>
x-forefront-prvs: 0001227049
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(136003)(346002)(376002)(396003)(40764003)(45074003)(199004)(189003)(55016002)(6116002)(3846002)(7696005)(68736007)(6916009)(6246003)(66066001)(9686003)(71190400001)(71200400001)(53936002)(4326008)(25786009)(86362001)(476003)(81166006)(81156014)(102836004)(52536014)(446003)(26005)(106356001)(8676002)(6506007)(105586002)(14444005)(256004)(53546011)(76176011)(229853002)(14454004)(478600001)(54906003)(8936002)(93886005)(2906002)(99286004)(316002)(7736002)(5660300002)(186003)(74316002)(6436002)(33656002)(305945005)(97736004)(486006)(44832011)(69594002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0702MB3563; H:HE1PR0702MB3689.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: EdntH5yur04QLy3DSXl79j0kaHQ2+HJB7CB5CMVYbCjdzlLz242wpIerLg+Q5gAfJh4PreRg1NRn+gXwUrmPUc8VKHTJz/6d8cLf5aKkoy3EFFGWlJ2gHIO9pwzelEGVAz6aUZHFrtFH3XQvTqZZT7uO1Q0QZGuA638hSky/HncR13SIrzwhhiSNuG7NX4OOdVEh/KJ8fG202T3csnk/us6n5jGnMIQ1blp260Byuo3lozhsDCz9/pCNW1gfuFSyFHHo249CusXswpCjZj7e9+EaUtGjle9CKrzQNiWhgtYXIoCwnWm7JQsrXeC/k7gGZPvJbqIM3YM7/DuXuT/GBcCNA2vU7cIWG2uY+yDY88+6MGhToH8gkwX96kJ+gQJylw7mVKArOo+NPSBDdu0uRLBNDmIhoNz/X5VuyXsAKeM=
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4b37de99-6dbd-4c2c-a9e7-08d6bc0e40ec
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Apr 2019 10:37:52.2488 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3563
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/hcm6QOHGkGX6H_pnj3l_twIvQ2w>
Subject: Re: [tram] Adam Roach's Discuss on draft-ietf-tram-stun-pmtud-10: (with DISCUSS and COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2019 10:37:57 -0000

Hi Gonzalo S,

what is your time plan for working on this?

Cheers,

Gonzalo

On 22-Mar-19 20:43, Gonzalo Salgueiro (gsalguei) wrote:
> Hi Gonzalo - 
> 
> I apologize but this PMTUD draft has gotten little attention beyond outlining proposals for clearing some of the raised DISCUSSes.  This one has taken a back seat as we are actively prioritizing completion of the STUN draft before some AD’s step down.  I think we should have that one completed by Prague or very soon after and then we will work on this PMTUD draft.
> 
> Cheers,
> 
> Gonzalo
> 
> 
>> On Mar 22, 2019, at 3:52 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> wrote:
>>
>> Hi Gonzalo S,
>>
>> could you please give me a status update on this?
>>
>> Thanks,
>>
>> Gonzalo
>>
>> On 19-Feb-19 20:13, Gonzalo Salgueiro (gsalguei) wrote:
>>> Hi Gonzalo - 
>>>
>>> We have made a decision on the PADDING but are still working through some of the comments raised in DISCUSS.  We hope to have this finished after finalizing STUN, which should be very close.
>>>
>>> Cheers,
>>>
>>> Gonzalo
>>>
>>>> On Feb 18, 2019, at 8:17 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> wrote:
>>>>
>>>> Hi Gonzalo S,
>>>>
>>>> what is the current status of this?
>>>>
>>>> Cheers,
>>>>
>>>> Gonzalo
>>>>
>>>> On 18-Jan-19 20:12, Gonzalo Salgueiro (gsalguei) wrote:
>>>>> Thanks, Spencer.  We will proceed with bringing the definition of
>>>>> PADDING into the current draft.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Gonzalo
>>>>>
>>>>>> On Jan 14, 2019, at 9:25 AM, Spencer Dawkins at IETF
>>>>>> <spencerdawkins.ietf@gmail.com <mailto:spencerdawkins.ietf@gmail.com>>
>>>>>> wrote:
>>>>>>
>>>>>> Hi, Gonzalo,
>>>>>>
>>>>>> On Mon, Jan 14, 2019 at 8:05 AM Gonzalo Camarillo
>>>>>> <gonzalo.camarillo@ericsson.com
>>>>>> <mailto:gonzalo.camarillo@ericsson.com>> wrote:
>>>>>>
>>>>>>   What is the next step here?
>>>>>>
>>>>>>   Gonzalo
>>>>>>
>>>>>>   On 13-Dec-18 16:27, Spencer Dawkins at IETF wrote:
>>>>>>> Hi, Simon, 
>>>>>>>
>>>>>>> On Thu, Dec 13, 2018 at 7:12 AM Simon Perreault
>>>>>>> <Simon.Perreault@logmein.com
>>>>>>   <mailto:Simon.Perreault@logmein.com> <mailto:Simon.Perreault@logmein.com
>>>>>>   <mailto:Simon.Perreault@logmein.com>>> wrote:
>>>>>>>
>>>>>>>     - Pull the definition of PADDING into this document. Declare
>>>>>>   that
>>>>>>>     we've gathered sufficient experience with PADDING that it now
>>>>>>>     warrants being elevated to Standards Track. That is, it's been
>>>>>>>     proven to work.____
>>>>>>>
>>>>>>>     __ __
>>>>>>>
>>>>>>>     This is plausible. It solves the first-order problem. ____
>>>>>>>
>>>>>>>     __ __
>>>>>>>
>>>>>>>     I note that RFC 5780 defined a number of new attributes. Is
>>>>>>   pulling
>>>>>>>     PADDING forward the right thing to do, or are there others that
>>>>>>>     would also qualify (so, perhaps a status change for RFC
>>>>>>   5780)? ____
>>>>>>>
>>>>>>>     __ __
>>>>>>>
>>>>>>>     I don’t think the others have been implemented much, so
>>>>>>   that’s why I
>>>>>>>     think only pulling PADDING makes sense. If I remember
>>>>>>   correctly, I
>>>>>>>     only implemented PADDING in Numb (I don’t have access to the
>>>>>>   source
>>>>>>>     code anymore so can’t be sure).____
>>>>>>>
>>>>>>>     __ __
>>>>>>>
>>>>>>>     Anyone else with an opinion?
>>>>>>>
>>>>>>>
>>>>>>> That's helpful information. 
>>>>>>>
>>>>>>> We should wait for anyone else with information to weigh in, but
>>>>>>   if it's
>>>>>>> correct that the other experimental attributes haven't been
>>>>>>   implemented
>>>>>>> and deployed in a way that would provide guidance for
>>>>>>   standards-track
>>>>>>> use, I think defining PADDING in this document makes more sense
>>>>>>   to me
>>>>>>> than adding a downref to an experimental RFC that we wouldn't
>>>>>>   consider
>>>>>>> if the reference was using anything except PADDING.  
>>>>>>
>>>>>>
>>>>>> No one has objected in the past month (which included holidays, but I
>>>>>> would have asked this question with a week or two timeout, if the
>>>>>> holidays had not been coming up). 
>>>>>>
>>>>>> I think bringing the definition of PADDING into the current draft is
>>>>>> the right thing to do. 
>>>>>>
>>>>>> If TRAM people thought that the other experimental attributes in RFC
>>>>>> 5780 don't have enough implementation experience to justify moving
>>>>>> them past Experimental status, changing the status of RFC 5780 to
>>>>>> Historic might be appropriate at some point, but that's not related to
>>>>>> the conversation we're having now, and I haven't asked a question
>>>>>> about that, so I'll ignore that for now.
>>>>>>
>>>>>> Thanks for your help with this.
>>>>>>
>>>>>> Spencer
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Spencer
>>>>>>>
>>>>>>>     ____
>>>>>>>
>>>>>>>     __ __
>>>>>>>
>>>>>>>     Simon____
>>>>>>>
>>>>>>
>>>>>
>>>
>