IETF Logo Mail Archive

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

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Wed, 20 September 2017 20:49 UTC

Return-Path: <albert.e.manfredi@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 108FD134212 for <ipv6@ietfa.amsl.com>; Wed, 20 Sep 2017 13:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 42lzHHaTbuMo for <ipv6@ietfa.amsl.com>; Wed, 20 Sep 2017 13:49:23 -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 AAAA11320B5 for <ipv6@ietf.org>; Wed, 20 Sep 2017 13:49:22 -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 v8KKnLQv013509; Wed, 20 Sep 2017 13:49:21 -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 v8KKnHI2013464 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 20 Sep 2017 13:49:17 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) 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 13:49:16 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1320.000; Wed, 20 Sep 2017 13:49:16 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
CC: IPv6 List <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: AQHTMk8dUsATtgvuN0uZCK2ByUXQ5KK+O/Wg
Date: Wed, 20 Sep 2017 20:49:16 +0000
Message-ID: <bde510ce4cae4c14bf4ad03e66984038@XCH15-06-11.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> <4c02155867b7433790dba442a9460cc0@XCH15-06-08.nw.nos.boeing.com> <8998DDAA-4ECF-499C-902F-582B2657C47C@gmail.com> <68f8bb19ac064b89ac0d10cd5056eb84@XCH15-06-08.nw.nos.boeing.com> <ea810ec11cd44ea0ac1f505fdea76553@XCH15-06-11.nw.nos.boeing.com> <34936f48-ddd9-0b1e-d7fb-ad13b69e2f12@gmail.com>
In-Reply-To: <34936f48-ddd9-0b1e-d7fb-ad13b69e2f12@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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/cRT-MsvpnohilUQO4fsO_bLI-s4>
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 20:49:24 -0000

-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 

>> I think this issue also relates to what an IP address refers to.
>> I'm under the impression that in IPv6, we insist this must be the
>> address of an interface, rather than a host. In IPv4, it's more
>> ambiguous, which is also problematic (IMO). If we insist that IPv6
>> addresses belong to interfaces, then the weak model would not apply
>> to IPv6, no?
>
> Again, see RFC 8028.

A somewhat different emphasis, because RFC 8028 talks about a host's individual interface with multiple prefixes, as opposed to a hosts two interfaces, each with only one prefix. Still, seems to me that RFC 8028 is advocating a strong model:

   In a multi-prefix network with multiple
   exits, the host's characterization of each default router SHOULD
   include the prefixes it has announced (extending Section 6.3.4 of
   [RFC4861]).  In other words, the PIO is reinterpreted to also imply
   that the advertising router would be a reasonable first hop for any
   packet using a source address in any advertised prefix, regardless of
   Default Router Preference.

This says that a host would transmit packets, with a given prefix, via a router that announces that prefix. The problems occur when a multi-homed host, using the weak model, lies about its source interface. It forms a packet with the "wrong" IP source address.

Bert

v2.23.0 | Report a Bug | By Email