Re: [dhcwg] Erik Kline's Yes on draft-ietf-dhc-dhcpv6-pd-relay-requirements-04: (with COMMENT)
"Ms. Li HUANG" <bleuoisou@gmail.com> Wed, 06 January 2021 01:44 UTC
Return-Path: <bleuoisou@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 073013A10BA; Tue, 5 Jan 2021 17:44:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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 7mw1umVTvIJT; Tue, 5 Jan 2021 17:44:28 -0800 (PST)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 1F1343A10BE; Tue, 5 Jan 2021 17:44:28 -0800 (PST)
Received: by mail-io1-xd2c.google.com with SMTP id q137so1272902iod.9; Tue, 05 Jan 2021 17:44:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RDsYIEE0lOSlvn0PmGien35LofYkHjDt3hFEHwE+1Fs=; b=R3m5HFKEVIp6+4mQnbWQv0B4Giq8dkomEcHCXF3jWYojeWFxod9FhLI7lit8n9oWdV Xkz44SEztji5JwCQ2So1fmpW3SfRwykmIz4ipzJxf4tQzIEhGnW3KpCO7m1QA6uQ6hIf ZY5vMO2fF3Yt/IHyKDhoYAsbXSMBy80Xc+ysjSNWWn8wd1Om7vSKdlFLXDxVLP2SYISx n61wuX1xy4WScDXdnh4P0txcwjv45opWSnrzE8Je15mPvhg5RhRU9N+vcgKCSKKghut/ r6rJP3VS+BCmffzxAhhYV1PbQZ46860Z/gVCQxh9WhqWq2kPZGDV0jlSylbgPV3GB6N1 jrYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RDsYIEE0lOSlvn0PmGien35LofYkHjDt3hFEHwE+1Fs=; b=mCD7toZroUTFW//nlDbEc3Zad+9jjX96bzY+fldNPGc3SkJeTUg2Z+eo8KT7jL1X35 NrRhbrp5xKpUSVgnNlyD0SuZDnNwNCti8d+kTH3ADR2nw3J2dawu1oYxuiUYPhEae+zX l4xHdrs5b0Rk3LHzCSuMikuSfzxtFzCBKHKauSzrOpKfZjUDwEA3IhXW9UiMgE+QmuIE jh1OJhpgkmmGp9+xvvSV9YwrXy/noHBGJnDVoVSZxZUYmL5Ize3xIcq/nt/zdOKMzGAU zzJn1Lxc1BNLydUegmXbTujGhe3g8aPmy+t32N3u6ZZobM1VqRDH5T6kLb6DDUgcq4c0 2EOg==
X-Gm-Message-State: AOAM530bET2gIoof6HKY8EeKyfNqeaa+/aIdp2C1xHniXhuPm2i6jO33 DHMf6JQAt04iSmduOrVuOBKmRILhpQl+xRHehgo=
X-Google-Smtp-Source: ABdhPJykVFSMk+N43vAUJd7kgpojm4LC6uw3sPFJraBoZjg3M8StwbdQmk0HHjOj7aHHASaMz4Uy8qXNM5bl7k3BlPo=
X-Received: by 2002:a5d:9641:: with SMTP id d1mr1378407ios.123.1609897467386; Tue, 05 Jan 2021 17:44:27 -0800 (PST)
MIME-Version: 1.0
References: <160816993406.2961.11066542485570806471@ietfa.amsl.com> <92F5EBD1-18C4-4ACF-ABF5-6B257CB72D13@gmx.com>
In-Reply-To: <92F5EBD1-18C4-4ACF-ABF5-6B257CB72D13@gmx.com>
From: "Ms. Li HUANG" <bleuoisou@gmail.com>
Date: Wed, 06 Jan 2021 09:44:15 +0800
Message-ID: <CAGGiuEY=vr+7FCUMGVsccS7OtbO-J60iPwq-1WaS-diZFbCSuA@mail.gmail.com>
To: ianfarrer@gmx.com
Cc: Erik Kline <ek.ietf@gmail.com>, draft-ietf-dhc-dhcpv6-pd-relay-requirements@ietf.org, dhc-chairs@ietf.org, Bernie Volz <volz@cisco.com>, The IESG <iesg@ietf.org>, dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ab201805b83176e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/gPQpw0hQ_oIWbFttPwv4a3g5Tq0>
Subject: Re: [dhcwg] Erik Kline's Yes on draft-ietf-dhc-dhcpv6-pd-relay-requirements-04: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 01:44:30 -0000
09:41.hk S8 Jan. 06 2021 Good Day, It means nothing this when , ISP without officially acclaimed in a document that it is supporting the DHCP-PD ... over months no feedback on it ?! Sincerely Li HUANG On Thu, Dec 17, 2020, 20:42 <ianfarrer@gmx.com> wrote: > Hi Erik > > Thanks for your comments. Please see inline below. > > Ian > > > On 17. Dec 2020, at 02:52, Erik Kline via Datatracker <noreply@ietf.org> > wrote: > > > > Erik Kline has entered the following ballot position for > > draft-ietf-dhc-dhcpv6-pd-relay-requirements-04: Yes > > > > 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-dhc-dhcpv6-pd-relay-requirements/ > > > > > > > > ---------------------------------------------------------------------- > > COMMENT: > > ---------------------------------------------------------------------- > > > > [[ questions ]] > > > > [ general ] > > > > * Should this aim for BCP? > > [if - We used RFC7084 as the template for this as another device > requirements document, which is not BCP. Beyond that, I’m not > sure how this decision gets made.] > > > > > [ section 4.2 ] > > > > * Seems like the MUST in R-4 is contingent upon implementation of > > the MAY that precedes it. It might worth sneaking in some condition > > phrase like, "If such a mechanism is implemented ... MUST ...". > > [if - Changed] > > > > > * It seems to me that R-5 would prevent a client from monitoring the > > CMTS/BNG for correctly installed routes by sending it a packet with > > a destination address in its delegated prefix and checking that it gets > > reflected back (similar to other checks done for tunnels). (I recognize > > this is not guaranteed to work in all environments.) > > > > What should a client wishing to keep an eye on this stuff do? Just ping > > a public service with an address in each source prefix of interest? > > [If - If an ISP used the method you describe as a client <-> relay health > check as > part of their service design, then the R-5 drop policy can be disabled. > > Otherwise, yes pinging a public service sourced from a delegated prefix > address > would work. If ICMP errors are enabled on the relay, then this would also > give > the client better visibility if the cause of a failure is due to the relay > having lost the > PD.] > > > > > > > [[ nits ]] > > > > [ section 2.1 ] > > > > * "This document serves" -> "This document discusses", or > > "This document is concerned with", or something, perhaps? > > > > > > > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www.ietf.org/mailman/listinfo/dhcwg >
- [dhcwg] Erik Kline's Yes on draft-ietf-dhc-dhcpv6… Erik Kline via Datatracker
- Re: [dhcwg] Erik Kline's Yes on draft-ietf-dhc-dh… ianfarrer
- Re: [dhcwg] Erik Kline's Yes on draft-ietf-dhc-dh… Ms. Li HUANG