IETF Logo Mail Archive

Re: [v6ops] I-D Action: draft-pioxfolks-6man-pio-exclusive-bit.txt

"Mudric, Dusan (Dusan)" <dmudric@avaya.com> Mon, 30 October 2017 14:38 UTC

Return-Path: <dmudric@avaya.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3B813F421; Mon, 30 Oct 2017 07:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.919
X-Spam-Level:
X-Spam-Status: No, score=-6.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=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 wVLXDAKrrrDK; Mon, 30 Oct 2017 07:38:12 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (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 A0D1413F43A; Mon, 30 Oct 2017 07:38:11 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2GbAACVOPdZ/yYyC4dcGQEBAQEBAQEBAQEBBwEBAQEBgxFOZG4nB4N1ih+RDZZCghEKJYUWAhqERT8YAQIBAQEBAQEBA2gogmpGWAEBAQEBASMCPiwBAQEBAxIREUUMBAIBCA0BAwQBAQECAgYdAwICAjAUAQgIAgQOBQgaigEBD51TimqCJyECilsBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYEPgh+CB4FUhRKFExWCfi+CMgWiAwKHZI8rhgCDdocijF+JMYE5HzlPgRl6FYMthF93jBABgRABAQE
X-IPAS-Result: A2GbAACVOPdZ/yYyC4dcGQEBAQEBAQEBAQEBBwEBAQEBgxFOZG4nB4N1ih+RDZZCghEKJYUWAhqERT8YAQIBAQEBAQEBA2gogmpGWAEBAQEBASMCPiwBAQEBAxIREUUMBAIBCA0BAwQBAQECAgYdAwICAjAUAQgIAgQOBQgaigEBD51TimqCJyECilsBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYEPgh+CB4FUhRKFExWCfi+CMgWiAwKHZI8rhgCDdocijF+JMYE5HzlPgRl6FYMthF93jBABgRABAQE
X-IronPort-AV: E=Sophos;i="5.44,320,1505793600"; d="scan'208";a="222271460"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by de307622-de-outbound.net.avaya.com with ESMTP; 30 Oct 2017 10:38:09 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC04.global.avaya.com) ([135.11.85.15]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Oct 2017 10:38:08 -0400
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC04.global.avaya.com ([135.11.85.15]) with mapi id 14.03.0352.000; Mon, 30 Oct 2017 10:38:08 -0400
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: Erik Kline <ek@google.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
Thread-Topic: [v6ops] I-D Action: draft-pioxfolks-6man-pio-exclusive-bit.txt
Thread-Index: AQHTShfKGEba7qTQr0qhCB80QLkriaL8gzDw
Date: Mon, 30 Oct 2017 14:38:07 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E4585AE4B5E@AZ-US1EXMB03.global.avaya.com>
References: <9142206A0C5BF24CB22755C8EC422E4585AE25F8@AZ-US1EXMB03.global.avaya.com> <CAAedzxo7cWrRyGnjT+94YiW2dEvo4zyxBYbviTk4VpeVcp+98A@mail.gmail.com>
In-Reply-To: <CAAedzxo7cWrRyGnjT+94YiW2dEvo4zyxBYbviTk4VpeVcp+98A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 10.0.250.9
dlp-reaction: no-action
x-originating-ip: [135.11.85.47]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/IFBGUhWulXyCK41LQJ5M1DTI2as>
Subject: Re: [v6ops] I-D Action: draft-pioxfolks-6man-pio-exclusive-bit.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 14:38:15 -0000

Hi Erik,

Please see below for more questions and comments.

Thanks,
Dusan.

> -----Original Message-----
> From: Erik Kline [mailto:ek@google.com]
> Sent: Friday, October 20, 2017 10:53 PM
> To: Mudric, Dusan (Dusan)
> Cc: v6ops@ietf.org; internet-drafts@ietf.org
> Subject: Re: [v6ops] I-D Action: draft-pioxfolks-6man-pio-exclusive-bit.txt
> 
> On 20 October 2017 at 22:56, Mudric, Dusan (Dusan) <dmudric@avaya.com>
> wrote:
> > Hi,
> >
> >
> >
> > https://tools.ietf.org/html/draft-pioxfolks-6man-pio-exclusive-bit-02#section-
> 5.2.2.2
> >
> > It is free to assign any address formed
> >
> >    from an exclusive prefix to any available interface
> >
> >
> >
> > Is it? What if a host has two interfaces connected to two ISPs that assign
> > exclusive prefixes? Each interface would end up with two ‘exclusive’
> > prefixes. Can they be still called ‘exclusive’?
> 
> In the sense that no other node on either network will receive traffic
> to any address within the prefix(es), yes.


[[Dusan]] Why would the host assign the exclusive prefix from one interface (connected to one local link) to another interface (connected to a second local link)? Should not the prefix be used on the local link? Using a prefix from the first link on a second link means the host can create an address on the second link that starts with the first prefix. A packet with that source address can be dropt by the edge router connected to the second link.

Second question: I think this draft is important for hosts using draft-templin-v6ops-pdhost or draft-ietf-v6ops-unique-ipv6-prefix-per-host. Is there a plan to advance the draft?

Thanks,
Dusan.

v2.23.0 | Report a Bug | By Email