Re: [trill] Eric Rescorla's No Objection on draft-ietf-trill-p2mp-bfd-08: (with COMMENT)

Eric Rescorla <ekr@rtfm.com> Wed, 24 January 2018 18:40 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0E19127342 for <trill@ietfa.amsl.com>; Wed, 24 Jan 2018 10:40:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=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 nMHZxCsOSaYL for <trill@ietfa.amsl.com>; Wed, 24 Jan 2018 10:40:26 -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 324A012DA72 for <trill@ietf.org>; Wed, 24 Jan 2018 10:40:26 -0800 (PST)
Received: by mail-yw0-x22b.google.com with SMTP id q6so1864059ywg.3 for <trill@ietf.org>; Wed, 24 Jan 2018 10:40:26 -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=ZL9JM+yD4GIsBxBiXXx/PJB3fcWxbFEZWrFDnCtkqzg=; b=b0Kzu/XvxypvyZaRpzBSmYQ/ZcnHKo0+JDu5ygoCs+krJspi9b655632vDNrLYBBYF Em+sgPa7TJAVJoO80FNHUp9wGMRrcjR4tj2y4iBAZywfbo8DiA0Upd3kNNGl0O5/Kg8z XzPRVI55uMUyw2iO4OZtlRrnboC0e0t7ypJekVBIzElVcVj1bB33A3Qtu/nxvZwDsRV8 +y/iFZ44iR8Y9fVv6qrLaMAhJWyHTPrMIWJEHMWIpSofPOKZ3DBmbrkngdPUD36l/wtl FG0wXuXz7CsQc1Jl+ZLgr5SP3QRiWZvdQK0p/l9g9sjOYiEP+283KVgLFokFv/G8lbOh q69g==
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=ZL9JM+yD4GIsBxBiXXx/PJB3fcWxbFEZWrFDnCtkqzg=; b=q+u3nz+R874M4LmdhnHR5lZfhqeBUGOnxpuzt0MhSNqYIpp/KfhVLSo7pVz9ZCBHVb OV/zv+14qHxZRWIGZ0i6pWYWL+PpU+AndZyiUTnV/lRp5lmRR2kABHvXZAjb+R0E9tRP ZuwNNoru/WV7JnpYklqY9WArzzuLwfvmxRTPzEd7C3tbgwfZoUNFpbS3iDTRk/2zBBbK 04P3VIKVrzasw9+ssNI8byyAsdFepGsiN1LxFRJu6p4UitYWPY5t75pheR4i/G2WDdWk 2lxysWVSkMoqbu4GYnuapqZT8uB7N0lka9j7Qq24k3Z8wpXacKuMFaFljXvWVDUte4/g t3IQ==
X-Gm-Message-State: AKwxytd4X8Vh9MUlBQXcqcMAma+5rp7Etd4WRHwom9loVURqystq/E3h 0EGOqlaKNnCI/xukixzLCQf382rn+3oVvKuxvdbnFA==
X-Google-Smtp-Source: AH8x225JfiDU6aegXSXBNQhFTRcOw/pZWnxbNcBAjPU4looj/5S20go2elV/mRfKu3y1wLfdtJ8Hi+AGltQ8VLWgqSU=
X-Received: by 10.13.226.194 with SMTP id l185mr6359244ywe.47.1516819225090; Wed, 24 Jan 2018 10:40:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.160.201 with HTTP; Wed, 24 Jan 2018 10:39:44 -0800 (PST)
In-Reply-To: <4552F0907735844E9204A62BBDD325E7AAFAF80F@NKGEML515-MBX.china.huawei.com>
References: <151629775024.3841.11679795774117326021.idtracker@ietfa.amsl.com> <4552F0907735844E9204A62BBDD325E7AAFAF80F@NKGEML515-MBX.china.huawei.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 24 Jan 2018 10:39:44 -0800
Message-ID: <CABcZeBOW=gHNfCkScZaz0Wg1b0YDDLQ3H0PuOggx18dYmXQ_CQ@mail.gmail.com>
To: "Zhangmingui (Martin)" <zhangmingui@huawei.com>
Cc: The IESG <iesg@ietf.org>, "trill-chairs@ietf.org" <trill-chairs@ietf.org>, "draft-ietf-trill-p2mp-bfd@ietf.org" <draft-ietf-trill-p2mp-bfd@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Content-Type: multipart/alternative; boundary="001a114fc3d619b4fd056389ffb1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/agQWptAnPJB9eCPk0cyfRM8DmAQ>
Subject: Re: [trill] Eric Rescorla's No Objection on draft-ietf-trill-p2mp-bfd-08: (with COMMENT)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2018 18:40:29 -0000

OK. This doesn't seem like it blocks this document, but I'll have to take a
closer look when the referenced document comes up.

On Mon, Jan 22, 2018 at 1:40 AM, Zhangmingui (Martin) <
zhangmingui@huawei.com> wrote:

> Hi Eric,
>
> Thanks for your review. When the referred document mentions Section 6.7,
> it actually points to the Section 6.7 of RFC5880.
>
> Thanks,
> Mingui
>
> > -----Original Message-----
> > From: Eric Rescorla [mailto:ekr@rtfm.com]
> > Sent: Friday, January 19, 2018 1:49 AM
> > To: The IESG
> > Cc: draft-ietf-trill-p2mp-bfd@ietf.org; Susan Hares;
> trill-chairs@ietf.org;
> > shares@ndzh.com; trill@ietf.org
> > Subject: Eric Rescorla's No Objection on draft-ietf-trill-p2mp-bfd-08:
> (with
> > COMMENT)
> >
> > Eric Rescorla has entered the following ballot position for
> > draft-ietf-trill-p2mp-bfd-08: No Objection
> >
> > 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-trill-p2mp-bfd/
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > I'm hoping this can be resolved quickly, as it's probably just a missing
> cite. If it
> > turns out that there's actually missing content, this may turn into a
> DISCUSS.
> >
> >    Multipoint BFD provides its own authentication but does not provide
> >    encryption (see Security Considerations in [I-D.ietf-bfd-
> >    multipoint]). As specified in this document, the point-to-multipoint
> >
> > I skimmed the reference here, but wasn't able to figure out what the
> > authentication was. In particular, the document says:
> >
> >       If the A bit is set, the packet MUST be authenticated under the
> >       rules of section 6.7, based on the authentication type in use
> >       (bfd.AuthType.)  This may cause the packet to be discarded.
> >
> > But there is no 6.7. So, this makes me worry that I don't understand any
> of this.
> >
>
>