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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 20 September 2017 15:29 UTC

Return-Path: <Fred.L.Templin@boeing.com>
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 294DE132D51 for <ipv6@ietfa.amsl.com>; Wed, 20 Sep 2017 08:29:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 e9lm_MV8uhqS for <ipv6@ietfa.amsl.com>; Wed, 20 Sep 2017 08:29:43 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E376B1330B3 for <ipv6@ietf.org>; Wed, 20 Sep 2017 08:29:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v8KFTfmo056858; Wed, 20 Sep 2017 08:29:42 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v8KFTTvv056563 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 20 Sep 2017 08:29:29 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 20 Sep 2017 08:29:28 -0700
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1320.000; Wed, 20 Sep 2017 08:29:28 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Timothy Winters <twinters@iol.unh.edu>
CC: Tim Chown <Tim.Chown@jisc.ac.uk>, Russ White <russ@riw.us>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: I-D Action: draft-ietf-6man-rfc6434-bis-01.txt
Thread-Topic: I-D Action: draft-ietf-6man-rfc6434-bis-01.txt
Thread-Index: AQHS/vWZz4CRyQUZXk66qsY4QNXMZaK82JDAgAF89YD//+mu8IAAeXIA//+SsvA=
Date: Wed, 20 Sep 2017 15:29:28 +0000
Message-ID: <4c02155867b7433790dba442a9460cc0@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> <CAOSSMjURSuSMajzNxTFSA8+TKp3NKyLDDJjBXAe=g5cCgTL_tA@mail.gmail.com>
In-Reply-To: <CAOSSMjURSuSMajzNxTFSA8+TKp3NKyLDDJjBXAe=g5cCgTL_tA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: multipart/alternative; boundary="_000_4c02155867b7433790dba442a9460cc0XCH150608nwnosboeingcom_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0iH8op5uvXW1txayCKQP2aa0UjY>
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 15:29:53 -0000

Hi Tim,

The specific case I am considering is documented here:

https://datatracker.ietf.org/doc/draft-templin-v6ops-pdhost/

But in general the RFC1122 considerations for hosts that act as routers,
including what is meant by “weak end system” and “strong end system”,
should probably be discussed in the IPv6 docs.

Thanks - Fred

From: Timothy Winters [mailto:twinters@iol.unh.edu]
Sent: Wednesday, September 20, 2017 7:56 AM
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
Subject: Re: I-D Action: draft-ietf-6man-rfc6434-bis-01.txt

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<mailto:Fred.L.Templin@boeing.com>> wrote:
Hi Tim,

> -----Original Message-----
> From: Tim Chown [mailto:Tim.Chown@jisc.ac.uk<mailto:Tim.Chown@jisc.ac.uk>]
> Sent: Wednesday, September 20, 2017 2:01 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>>
> Cc: ipv6@ietf.org<mailto:ipv6@ietf.org>; Russ White <russ@riw.us<mailto: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<mailto: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<mailto: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