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

Naveen Kottapalli <naveen.sarma@gmail.com> Wed, 02 October 2019 16:36 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 402BF12016E for <dhcwg@ietfa.amsl.com>; Wed, 2 Oct 2019 09:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 iNduSqs2PKhJ for <dhcwg@ietfa.amsl.com>; Wed, 2 Oct 2019 09:36:37 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 0E8D21201DC for <dhcwg@ietf.org>; Wed, 2 Oct 2019 09:36:37 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id h144so58329991iof.7 for <dhcwg@ietf.org>; Wed, 02 Oct 2019 09:36:37 -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=WoEJL8sA7OMiZ5tQPHbpqFUH0mCf7LvxY5ICkzzcD+Q=; b=GRkMuLWg7kffvqfewaHz2qesH+exNcLO0b3+AuIfKW1uZmQnAVEXkUlHclAP6GW/K0 raYaXl0C1QxiYsnhp8Xcm1WkZPhu5K8X/k1rKScxqQJdzxBt4iCg3Uqwxfadr8u+ZZP6 9NHNXBuaJKKZWrArQaeWcYwdBr0R5Qv4XpaUoMoz4KZ9TcMqMGJ50ACP5YWQPAy+eGgJ qLZBh9DCs7V7uwypMTOaVWRB3OdK47svK2AXOdAf/xZRAxzEV4MNvAZYAMpJHUwDise/ kj5nduJ90xPIGw9qNgEhFF+ok8Jdmt9/u1DwKwtiGOh3tluCQhnS8b0kO0Lq6cKLgQjD C9fQ==
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=WoEJL8sA7OMiZ5tQPHbpqFUH0mCf7LvxY5ICkzzcD+Q=; b=CW3eCrp2c23QBHGvm2ILthUWX+slGEphL8/SWgFj66UpOOB+ncHD27Cx6Z6dYK05Ke bygT2MqaE4RiWfez0j5i4KiL2x6FCbRdsaKOAIMhtkDuN8FRzqzkBnyxY97218sDZCEe GfaEhlmDUDhS5/mVLaeYK0OaZV2lSTtn8pv4Yk8SVm5xwFJoQcJKAY+33AVe6CXkHcQs i884IPmUmOGOSVCik4T3V0Q2wRO6+UVAxoz6v+5Z9bO7uysrzz3T4WPyBg8P4fLFBEry zz75KnFByat93xc3NwTsHk/S+r1xmDQ0JOmoeXpp4EmBZMZTkCtgWa7+hvWf/EaluSz+ cFeA==
X-Gm-Message-State: APjAAAUvQy1fq+I6LhIOb48xAVIZqzKgMhujIp/RGQ1LNTgVPtJ4Y/br +o1T8VzSwQd6xBZ3l5uBK5cfsa91rSeQrDr/NZM=
X-Google-Smtp-Source: APXvYqw0zvXXn4L8XYBaIm2Dw2qJJuZ1AnfyyrDWk5F4hmqVC0RgnV56Fu19brxNeFSYkPQPFf4++d975Afi2hyGob8=
X-Received: by 2002:a92:d58f:: with SMTP id a15mr5040578iln.259.1570034196196; Wed, 02 Oct 2019 09:36:36 -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> <CANFmOtkBXgZQm5Hag14Lx4+6538-NbgU3xQLXrj+CR67-BAvRw@mail.gmail.com> <f60fce6c-6a02-c156-5ff2-87afc56d20f7@gmail.com>
In-Reply-To: <f60fce6c-6a02-c156-5ff2-87afc56d20f7@gmail.com>
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Wed, 02 Oct 2019 22:06:24 +0530
Message-ID: <CANFmOtmMnbPqd0g6UdxcWVx5tvWgZb+HhdpA7pK=KheryLR5yw@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008cbd7f0593f012db"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/zViBVyt9fRmRd_B_f9mokjeLdfs>
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: Wed, 02 Oct 2019 16:36:39 -0000

Sure. Will change in next update.

On Tue, 1 Oct 2019, 16:05 Alexandre Petrescu, <alexandre.petrescu@gmail.com>
wrote:

>
>
> Le 01/10/2019 à 05:37, Naveen Kottapalli a écrit :
> > The document started with problem statement and how it can be addressed.
> > The approach we to address the problem is by defining the requirements
> > of the node that are to be handled.
>
> In this case, it should have Intended Status: INFORMATIONAL. (not Stds
> Track), I think.
>
> Alex
>
> >
> > On Mon, 30 Sep 2019, 18:25 Alexandre Petrescu,
> > <alexandre.petrescu@gmail.com <mailto: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 <mailto:dhcwg@ietf.org>
> >      >> https://www.ietf.org/mailman/listinfo/dhcwg
> >      >>
> >      >
> >      > _______________________________________________
> >      > dhcwg mailing list
> >      > dhcwg@ietf.org <mailto:dhcwg@ietf.org>
> >      > https://www.ietf.org/mailman/listinfo/dhcwg
> >
> >     _______________________________________________
> >     dhcwg mailing list
> >     dhcwg@ietf.org <mailto:dhcwg@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/dhcwg
> >
>