IETF Logo Mail Archive

Re: [dhcwg] Request for adoption of draft-fkhp-dhc-dhcpv6-pd-relay-requirements

Naveen Kottapalli <naveen.sarma@gmail.com> Tue, 01 October 2019 03:38 UTC

Return-Path: <naveen.sarma@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 1EDBE1200A1 for <dhcwg@ietfa.amsl.com>; Mon, 30 Sep 2019 20:38:46 -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_HELO_NONE=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 Kv3_WvZVO-DL for <dhcwg@ietfa.amsl.com>; Mon, 30 Sep 2019 20:38:43 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 60109120025 for <dhcwg@ietf.org>; Mon, 30 Sep 2019 20:38:43 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id c6so44026188ioo.13 for <dhcwg@ietf.org>; Mon, 30 Sep 2019 20:38:43 -0700 (PDT)
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=LRRu9JlTyEKLsPq5mxIi66fiohAUwX48YCtC1XGEXS4=; b=dFjGI5W7KlnfDkqAVX2JSLXr3EHYFTe9MEf0NULaFP5QzgIlLdVn481O68L/vgWQ+4 fwrJImMbIPNFfO77w/rXSfCLEZiyk/oieNVWcJxclY72lIkjv5RzlzY6iUYBDjA5p32+ Iq1yqyIj4PZ0qJvvcAUwhhXlyuprXBhigWe8C124e+GpmWlHG4IuzsH3o/FrJIZdvVRm 2FMq4Y73u+qnVm0TpefAf0LotQiyhlYN462qowjiJX6zJ+/BZ6paKFrn+ZEhCG3WJbpV E/y18ahjThRmTM6DmXCUuoQobFShGQasW+XX14FA2bp5ggDQHODoNN7wcos5OjP08kXf VEtQ==
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=LRRu9JlTyEKLsPq5mxIi66fiohAUwX48YCtC1XGEXS4=; b=RxudMNlhTmBAiUY4qsLafxD2K8VLpF0i4IBhPRUTzKAYVgjuLA7GjFA2dIHOmBKis1 VB1weDaG+e6MRW3sBAR5SR9eoaUQyu+p0kBQBOG5RTGe6EmVM9hvYdgLlvgw+2gp2EG5 SpVqemFRfhc8v7esVpIF+u8x1L+vwJfDvgJyfaiXPK63FoL6TvacxQHumteHZjsC6QWN xESmCISDnVXELoNjhaNQHbHozagn2asYwUoXnLNEL19E3h9+YgJKsZZ/rlOXO/WaSFfe BAmuE5X0TSuOK50W8JwjyJUb+qffmIl1AktBr9Nu0k459JQws6DJOPKf7c9dqefxy602 a0YQ==
X-Gm-Message-State: APjAAAU2W82TX8pljdgbXlFTPqRuItbOKhjLI+cEm1mvEaE9afKWJHGb 22ztT6Rg1F/isDN1e4FfC2RWGRPc43CeB0WN4ro=
X-Google-Smtp-Source: APXvYqxJfArACg5fkD24fzglMXxaBLYDDr7g+NIjPpjGWYnaYQJiL4qJyD5nTcLasFw0LT5gLOPiELiYCIB0daY4NoM=
X-Received: by 2002:a02:c958:: with SMTP id u24mr22064884jao.113.1569901122612; Mon, 30 Sep 2019 20:38:42 -0700 (PDT)
MIME-Version: 1.0
References: <CANFmOt=R1yAGLsM-TZKLPfujfmzLyMHRK_8895g17QvdpQ5n1A@mail.gmail.com> <b0d04f8f-da76-7181-6b4c-26da532c477d@gmail.com> <c5ec1a09-dbe6-fc32-d9da-d2f8abc1957d@gmail.com> <CAGGiuEbJJsp+Lh=sBYXGzYJP-siJwFBh0Y6zQbRw3pM2Wj4b9A@mail.gmail.com>
In-Reply-To: <CAGGiuEbJJsp+Lh=sBYXGzYJP-siJwFBh0Y6zQbRw3pM2Wj4b9A@mail.gmail.com>
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Tue, 01 Oct 2019 09:08:31 +0530
Message-ID: <CANFmOtnADjv5EKW627tcamF7hhse5ym=nB8vUpyf1jJ4fS55ow@mail.gmail.com>
To: Li HUANG <bleuoisou@gmail.com>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bef0df0593d116f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/FkuyfHsmV1JLwgK_FanOlhaQNAc>
Subject: Re: [dhcwg] Request for adoption of draft-fkhp-dhc-dhcpv6-pd-relay-requirements
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: Tue, 01 Oct 2019 03:38:46 -0000

Are you looking for the implementation of the requirements (node)?

On Mon, 30 Sep 2019, 19:44 Li HUANG, <bleuoisou@gmail.com> wrote:

> 22:10.hk S8 m800
>
>
> Good Day,
>
>
> Looking for some who would and be able to get the solution.  Since OS
> publisher would not support for user without company contract at commercial
> group.
>
>
> This is a pay way inquiry to some who can make this deal off recommandated
> by IETF hopefully.
>
>
> Sincerely yours
> Li HUANG
>
> On Mon, Sep 30, 2019, 20:55 Alexandre Petrescu <
> alexandre.petrescu@gmail.com> wrote:
>
>> Is this a requirements draft, a problem statement draft or a solution
>> draft?
>>
>> The filename has 'requirements' in it, but there are two sections:
>> 'Problems Observed' and 'Requirements'.  The former makes for a Problem
>> Statement draft.
>>
>> Its Intended Status is 'Standards Track'.  But typical Requirement and
>> Problem Statement drafts are intended as INFORMATIONAL.
>>
>> Alex
>>
>> Le 26/09/2019 à 09:42, Alexandre Petrescu a écrit :
>> > Hi,
>> >
>> > If the question on whether or not adoption is supported, then my answer
>> > is yes, I support adoption.
>> >
>> > If the question is to receive feedback of the draft, then my answer is
>> > this: I support requirement R-1 'relay MUST maintain a local routing
>> > table dynamically updated with prefixes and next hops as they [the
>> > prefixes] are delegated to clients'.
>> >
>> > Alex
>> >
>> > Le 26/09/2019 à 08:58, Naveen Kottapalli a écrit :
>> >> Hello DHC WG,
>> >>
>> >> We would like to request for the adoption of our draft
>> >> draft-fkhp-dhc-dhcpv6-pd-relay-requirements
>> >> <
>> https://datatracker.ietf.org/doc/html/draft-fkhp-dhc-dhcpv6-pd-relay-requirements> that
>>
>> >> was submitted in June-2019.  As a background, please find the details
>> >> of draft below.
>> >>
>> >> The draft addresses the below problems by defining the requirements of
>> >> a DHCPv6 Relay agent when relaying the delegated prefixes.
>> >>
>> >> 1.  Client / Relay / Server goes out of sync resulting in route
>> >> mismanagement which in turn results in traffic issues.
>> >> 2.  Relay rejects client messages due to unknown or stale prefix.
>> >> 3.  Relay generates messages ‘on behalf’ of the server
>> >> 4.  Issues observed when more than 1 prefix is delegated to clients
>> >>
>> >> We would like to hear feedback from the forum on the draft and will be
>> >> happy to address the issues in draft (if any).
>> >>
>> >> Yours,
>> >> Naveen.
>> >>
>> >> _______________________________________________
>> >> dhcwg mailing list
>> >> dhcwg@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/dhcwg
>> >>
>> >
>> > _______________________________________________
>> > dhcwg mailing list
>> > dhcwg@ietf.org
>> > https://www.ietf.org/mailman/listinfo/dhcwg
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

v2.23.0 | Report a Bug | By Email