IETF Logo Mail Archive

Re: I-D Action: draft-ietf-6man-rfc6434-bis-01.txt

Timothy Winters <twinters@iol.unh.edu> Wed, 20 September 2017 14:56 UTC

Return-Path: <twinters@iol.unh.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B805813214D for <ipv6@ietfa.amsl.com>; Wed, 20 Sep 2017 07:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
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 TS-RrFRqTwtq for <ipv6@ietfa.amsl.com>; Wed, 20 Sep 2017 07:56:38 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (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 A1238124F57 for <ipv6@ietf.org>; Wed, 20 Sep 2017 07:56:38 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id b82so2970960qkc.4 for <ipv6@ietf.org>; Wed, 20 Sep 2017 07:56:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=26KEatbLvA0vpHNkTnydIZHOxBVywIdxKz/0PSd/zDQ=; b=T2CmG+gkCUvI4tSEsXJ/tUZdo7udb+ViLR4mjsACLcQT7gUBWJfow44NUKOsaNymsy Cjxcxe9jPK96NoO/YKLCvzq3lceiE6Q1ovbftQiRgXGq5ikfC4VufcuGbBCuVw+l65MB YI86HPCAtZanSFjrkzbwt13i8vFpAA0A6IpGU=
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=26KEatbLvA0vpHNkTnydIZHOxBVywIdxKz/0PSd/zDQ=; b=i+wzEnQBOXGfdQwkdnLqAnH6+IV11qAttdDa3B7xHml2CNnBmzJgb5KTMoelVaozgv CqjrDt+TcA9v8gag/Ofj8CjsE3k6JJeDL+lfmkM8VYDlH9Wzssv4FzX8YP1xXiHGfwXl /N+OvmfbsuHKPx/YBXp//vFyrZFBgFb9+tKJObbocKLQxYh+w76JuXaBMpqhWguos1xX HArVNdbmz1gwKzqKQYcVQvTLRezyjtcYCc/7lHwe84/HTztmjYiGK9QPdXGNfGsYeyF/ GTJ3W4w2s4dWviqOJTmFBLIF2oPzPXbzYPiJDXS+wC5xvLdC+xZwnqoZTO1X2ZKUOZdi X3vA==
X-Gm-Message-State: AHPjjUibrj6MW4qC5oK5b1/FQsVgtfkC42sL5d5VY95Ohh6+Q1QPs7MZ o8Jel04I26aYcriV26RAZLZXH7oQNgqK9D/0zngPQA==
X-Google-Smtp-Source: AOwi7QDVZWTKDODhA69I6x0m0wGleNxbXyxf909YyiWMrjGevaueyB0MFnGCXQm/gOFkdyYN/aJ2aUrjC/3Hho+poRk=
X-Received: by 10.55.17.73 with SMTP id b70mr7389055qkh.270.1505919397461; Wed, 20 Sep 2017 07:56:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.55.6 with HTTP; Wed, 20 Sep 2017 07:56:16 -0700 (PDT)
In-Reply-To: <2065f43f2b10419981b4d527d0f5e281@XCH15-06-08.nw.nos.boeing.com>
References: <149909644776.22718.16227939850699261560@ietfa.amsl.com> <fef7bb88-1ebd-bba6-219a-dbc810f0a1b8@gmail.com> <CAOSSMjXDqWm_EvZqmCACoTESZpj-vMywkL8GqByYnC=DFKAa8Q@mail.gmail.com> <5a4d61e7-9ca4-b741-ddf3-2e3d3714d55c@gmail.com> <596CA8F9.6090806@foobar.org> <fef776d1cc3c4854a7e9cf1d1851e165@XCH15-06-08.nw.nos.boeing.com> <908A44DC-D32F-4A06-9B65-D9B497A9E3C9@jisc.ac.uk> <2065f43f2b10419981b4d527d0f5e281@XCH15-06-08.nw.nos.boeing.com>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Wed, 20 Sep 2017 10:56:16 -0400
Message-ID: <CAOSSMjURSuSMajzNxTFSA8+TKp3NKyLDDJjBXAe=g5cCgTL_tA@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-rfc6434-bis-01.txt
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, Russ White <russ@riw.us>, "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="001a1147407cbf40b60559a02e3d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gQKyJgpV-YIpil6czB7VuTODkuQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 14:56:42 -0000

Hi Fred,

The first thing that came to mind reading your email is your are talking
about a CE Router (RFC 7084).   Acts as a Host on the WAN, but a Router on
the LAN interface.

I would not be in favor of trying to document that behavior in node
requirements.  I would prefer to keep it simple, or are you thinking of a
case that's not covered in RFC 7084?

Regards,
Tim

On Wed, Sep 20, 2017 at 10:50 AM, Templin, Fred L <Fred.L.Templin@boeing.com
> wrote:

> Hi Tim,
>
> > -----Original Message-----
> > From: Tim Chown [mailto:Tim.Chown@jisc.ac.uk]
> > Sent: Wednesday, September 20, 2017 2:01 AM
> > To: Templin, Fred L <Fred.L.Templin@boeing.com>
> > Cc: ipv6@ietf.org; Russ White <russ@riw.us>
> > Subject: Re: I-D Action: draft-ietf-6man-rfc6434-bis-01.txt
> >
> > Hi,
> >
> > > On 19 Sep 2017, at 18:23, Templin, Fred L <Fred.L.Templin@boeing.com>
> wrote:
> > >
> > > I realize that this goes back to the previous node requirements docs
> (RFC6434
> > > and RFC4294), but shouldn't this document cite RFC1122 and RFC1812?
> >
> > RFC1122 could be added in the intro.
> >
> > I’d suggest RFC1812 could be reviewed/cited in
> draft-ietf-v6ops-ipv6rtr-reqs-00, something for Russ to consider.
>
> OK, thanks. One of the reasons I ask is because I think our IPv6
> node/router
> requirements documents are missing something important that appeared
> in these earlier standards - the model of a host that also acts as a
> router.
>
> RFC1122 calls them "end systems", or "hosts with embedded gateway".
> They host their own local applications and can also forward packets on
> behalf of nodes connected to a downstream interface. The model has
> significant implications for Internet of Things.
>
> Do we want to import that language into our IPv6 requirements docs?
>
> Thanks - Fred
>
> > Tim
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



-- 

Now offering testing for SDN applications and controllers in our SDN switch
test bed. Learn more today http://bit.ly/SDN_IOLPR

v2.23.0 | Report a Bug | By Email