Re: [Pals] Kathleen Moriarty's Discuss on draft-ietf-pals-p2mp-pw-03: (with DISCUSS)

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Fri, 01 September 2017 02:14 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAC8313301C; Thu, 31 Aug 2017 19:14:31 -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 jxnsEjlqzaJW; Thu, 31 Aug 2017 19:14:30 -0700 (PDT)
Received: from mail-pg0-x232.google.com (mail-pg0-x232.google.com [IPv6:2607:f8b0:400e: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 0ACC2132ED1; Thu, 31 Aug 2017 19:14:30 -0700 (PDT)
Received: by mail-pg0-x232.google.com with SMTP id 83so3993096pgb.4; Thu, 31 Aug 2017 19:14: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=lAM+ZCPebbs3fvm65Sqjjr6B51MeWqAv/r5G1KbcwwA=; b=TO/Ts0+hJMgFPs3BxxC6+3swhdPu3/Qv9Fd7BiEByMKNw8Uz3nl6PzLmKjZfy8Qhyc rUoa/XzVvdbYpe63du/xyni3bbj8VaqsX6ZB5H4ZCmZVHcvqflEAT8Cf0ycmhrYVYFOI 0KODIUCZwQtVE0KAdOgX2U3dJTZYcv/KEes+9mfpk+0Vulw1EzGY5gGOuo+9tY1HqZhe RildgGTM2KTWU2DlT1geqTDrm8LxzEYSvC/FVh1qQxeclwJZrTNbm1YSjBHpHiYZ95/Z fTHigViTZAjiX8eyd5LxtMWv6Q0XjH+IfAzanqJFOnDwRrIYhqt+S1Z72Fhv2P4UbzbP YJCg==
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=lAM+ZCPebbs3fvm65Sqjjr6B51MeWqAv/r5G1KbcwwA=; b=f5dS8uflI+UeLvca0nQwgTLM8fzGy5V1rrHoKrbvnB7kajMPGIe7r7lYVW12Ov4bGR JvGGnWBGFYZNMceHBL14m0cUCWHTZx4H+lnimuYiRbs6p4FKgVNjBlkp29zu9LoxRJEe lOqASlDLEkUE/UWoMSVV8x+lSzGMO0XY2J1nDAXVoHCmTPFBVjSfApNMhA3lejU0TmDw 9gpsKi98Q1WlCaYat9q+Ui/LLz8RoeNIWKM0seFVK0rlSmBptTsSzx/CoflQqhFSGmEI CkMkYcYdBRiKsk3wOSkef3/VsqGLXkkOUGJbv1gQ7NqOdn1X/JKzRovnj8g8zAJyKCeq 1Ycw==
X-Gm-Message-State: AHPjjUibVTgCcsfNQ0xDpPrTGaQmT+k7MX9aiw9ZxkkHbzLx9s4vakjh NIFNkY8BHT7StcPj3FE8OPhHEPc+Qg==
X-Google-Smtp-Source: ADKCNb5yssDHvcekWXtWAMSy21dn1zcKYUKiQ0ov6z5w7pvUf5BR3uy3ENP1hid5gZjxRZcc38aH2oFjor6sfaQdyFM=
X-Received: by 10.98.83.196 with SMTP id h187mr508235pfb.319.1504232069580; Thu, 31 Aug 2017 19:14:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.144.1 with HTTP; Thu, 31 Aug 2017 19:13:49 -0700 (PDT)
In-Reply-To: <233ebf05-b663-2a78-e962-5edf2940e85f@gmail.com>
References: <150412137722.21566.9884376358367891967.idtracker@ietfa.amsl.com> <233ebf05-b663-2a78-e962-5edf2940e85f@gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 31 Aug 2017 22:13:49 -0400
Message-ID: <CAHbuEH6g20MST3rJLrU541A6QJO69O1pDrH7Mo2SS939Nb1n7Q@mail.gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pals-p2mp-pw@ietf.org, pals-chairs@ietf.org, pals@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/lrL6OZZY5gYSbBinwzso9qNkZSc>
Subject: Re: [Pals] Kathleen Moriarty's Discuss on draft-ietf-pals-p2mp-pw-03: (with DISCUSS)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 02:14:32 -0000

Hi Stewart,

Thanks for your response.  Inline.

On Thu, Aug 31, 2017 at 8:02 AM, Stewart Bryant
<stewart.bryant@gmail.com> wrote:
>
>
> On 30/08/2017 20:29, Kathleen Moriarty wrote:
>>
>> Kathleen Moriarty has entered the following ballot position for
>> draft-ietf-pals-p2mp-pw-03: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-pals-p2mp-pw/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> I haven't sen a response to the SecDir review, so please point me to one
>> if
>> there has been a response.  I fully agree with Tero that MD5 is not
>> adequate
>> and hasn't been for some time.  What is the plan to rectify this and
>> deprecate
>> use of the TCP MD5 signature for LDP? RFC8077, says that LDP MD5
>> authentication
>> key option as described in the section 2.9 of RFC5036 MUST be implemented.
>> I
>> asked on my ballot for RFC8077 when a deprecation process would start in
>> support of Stephen's abstain and would like an update on that process.
>>
>> https://mailarchive.ietf.org/arch/msg/secdir/ga2pIVcGw9WEgBX5MXA9MCmSs_s
>>
>>
>>
>>
>
> Hi Kathleen,
>
> I have proposed some text that tells implementers and operators that MD5 is
> inadequate and that they should be prepared for an upgraded default hash for
> LDP. I don't think we do any more at this stage.

OK, I'll look out for the text.  Thanks.

>
> I have just spoken to Loa, one of the MPLS chairs, and we have agreed to
> write a short draft within the next month to start the process of
> deprecating MD5 and selecting and standardizing a new default hash for LDP.
> We will discuss this draft with the MPLS WG via the MPLS list and at the
> next IETF.

That is very helpful, thank you.  Alvaro mentioned some of the
challenges, reminding of past discussions on this topic.  Would it be
helpful to engage security/crypto folks at routing vendors who would
be familiar with the challenges?  I'm thinking this could be helpful
to get recommendations and a transition plan that takes everything
into account that's needed for a successful transition.
>
> Best Regards
>
> Stewart
>



-- 

Best regards,
Kathleen