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:37 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 D02EF120077 for <dhcwg@ietfa.amsl.com>; Mon, 30 Sep 2019 20:37:43 -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 ZdWuL4XZdG1K for <dhcwg@ietfa.amsl.com>; Mon, 30 Sep 2019 20:37:42 -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 19569120025 for <dhcwg@ietf.org>; Mon, 30 Sep 2019 20:37:42 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id w12so16053081iol.11 for <dhcwg@ietf.org>; Mon, 30 Sep 2019 20:37:42 -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=LbTUxcDuxm/83MqvxTxJT6MNGxbYtZzWFn4I4AR0MdA=; b=Eengi5XTgJqX9XsdRMuydZY92wiJ2zguBoKULTN5hcoAtkz6wrNQ7MpVkZiI66cI8u hnBuz5sTQh/sqf6xbINIW6hVyZJcMgGXCHF53G94iRk+ghi56EtVc9i52xCvb/hY5YGM D6PC36MDFbl8YBrZdn6vtgsf/m51Eu/pc5y3eXlNB2vAxKLWU7omvtDiC8JxNldEff+u AE3/72Ff3DqitJZ7qCXem2p59bQUGRM8aLvMdf05Gk0i2Ipz4nds5VpzUqFEHhh89sxz RcBEWojID0f8laSBNNDBh8/45+im/uXXaXW7fT488wdhbbG4taQMMKCLhSU/em8sXM5I ekjw==
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=LbTUxcDuxm/83MqvxTxJT6MNGxbYtZzWFn4I4AR0MdA=; b=oelH6JrjfcOVqUb4vmqLv8GQO6rLlAH1VTicCv4aoS9r9PRjMnwztXkv/2EJ5zM9RR tYpGrI9TbxAEAjCEnBo8HNThO3WrmQvAj+OlTIUAXADt01AiY/znTBddCTDIorD6Ki/D sbnomd/hbG+kB+E3dXsAsLunMHmL+U8JA5LmBTqKu3a256uVXFAgeUQJzcoy7ap3wCxy pqiY9DLvVYt3jcaME+yDZIEfeqfo69pwksnwk8uP+gK3v6Y+kgfe9kCmt7HgFX1PUUBp lWyvAOcoxlJd4ACTwNnFwkvBSb66XYnnpERxjiSHpUws7EE2F67/AEZNGgpNFaN1UksH dxDw==
X-Gm-Message-State: APjAAAVb/S3InW517B7blxlVv55sdyNeqkXE/gmhx0Jl8+mHTUtmvtfZ HWZHI2Uu4dFKtLOJTluyhQPZkTJxAlKI+SbRvQg=
X-Google-Smtp-Source: APXvYqw+ovmgG2yjtYK88WhbvrtvTd5HTDPAx4lwBwK/lzczz1gkQVA+lP1obciUwngrsjYESf60wY2Wc8nVD79RUvo=
X-Received: by 2002:a5e:8b43:: with SMTP id z3mr2445808iom.114.1569901061198; Mon, 30 Sep 2019 20:37:41 -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>
In-Reply-To: <c5ec1a09-dbe6-fc32-d9da-d2f8abc1957d@gmail.com>
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Tue, 01 Oct 2019 09:07:29 +0530
Message-ID: <CANFmOtkBXgZQm5Hag14Lx4+6538-NbgU3xQLXrj+CR67-BAvRw@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="00000000000016117f0593d11385"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/eQhxj6Y7cYfipLzcmjvBKZiNhtY>
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:37:44 -0000

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.

On Mon, 30 Sep 2019, 18:25 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
>

v2.23.0 | Report a Bug | By Email