Re: [v6ops] I-D Action: draft-palet-v6ops-p2p-links-00.txt

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Sun, 11 March 2018 09:22 UTC

Return-Path: <prvs=1608b02863=jordi.palet@consulintel.es>
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 A2B5B126D05 for <v6ops@ietfa.amsl.com>; Sun, 11 Mar 2018 01:22:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 6rbhuH3cqqIh for <v6ops@ietfa.amsl.com>; Sun, 11 Mar 2018 01:22:25 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97F34124B0A for <v6ops@ietf.org>; Sun, 11 Mar 2018 01:22:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1520760142; x=1521364942; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=yDTo0hhu QUpKNhoefHNlFvBtyhNnQywpwuzwX2TPP4I=; b=Hd4zJGJo7aqOUWK80fwQ34Qj GsVgJ0ogurIdA0TN2OaOB6bc9XF26eNQW8Sy2jx4QD5qnJMj710Ee55waWQuQu8b Vu1UcqALjO2fp0l77lehe5IRs3bJn351KIhvg9KUaIlkeBMnQRxYLPcOF4vVv5uL VxK82yz5xM8Hz735fS4=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Sun, 11 Mar 2018 10:22:22 +0100
X-Spam-Processed: mail.consulintel.es, Sun, 11 Mar 2018 10:22:22 +0100
Received: from [10.10.10.129] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50005721920.msg for <v6ops@ietf.org>; Sun, 11 Mar 2018 10:22:21 +0100
X-MDRemoteIP: 2001:470:1f09:495:a429:4af6:da27:11ce
X-MDHelo: [10.10.10.129]
X-MDArrival-Date: Sun, 11 Mar 2018 10:22:21 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1608b02863=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.a.0.180210
Date: Sun, 11 Mar 2018 10:22:16 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IPv6 Operations <v6ops@ietf.org>
Message-ID: <68D92685-CE2E-461B-8ABF-6ACCF8D465E5@consulintel.es>
Thread-Topic: [v6ops] I-D Action: draft-palet-v6ops-p2p-links-00.txt
References: <152027294685.14511.12101390842726850001@ietfa.amsl.com> <df5935b4-8c6a-e620-4ed4-dae793a50ee1@gmail.com> <F88BA0B6-3174-4DBC-B674-6DCF521CF946@employees.org> <68f08ca9-db92-94fc-670c-98708a02ae64@gmail.com>
In-Reply-To: <68f08ca9-db92-94fc-670c-98708a02ae64@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OJuNlfyj6YzF_vA3pMqWwqapcL0>
Subject: Re: [v6ops] I-D Action: draft-palet-v6ops-p2p-links-00.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: Sun, 11 Mar 2018 09:22:27 -0000

Hi Brian, Ole,

Thanks a lot for your inputs, very useful. I'm already editing a v-01 and will incorporate them.

Regarding Ole suggestions, I think this text can fix it:

3.2. ULA (Unique Local Addresses)

   Some networks use ULAs for numbering the point-to-point links.  This
   approach may cause numerous problems and therefore is strongly
   discouraged.  For example, if the CE needs to send an ICMPv6 message
   to a host outside that network (to the Internet), the packet with ULA
   source address will not get thru and PMTUD will break, which in turn
   will completely break that IPv6 connection when the MTU is not the
   same for all the path.

   However, this approach is valid if, following section 2.2 of RFC4443, 
   and despite using ULA for the point-to-point link, the router is 
   configured with at least one GUA and the source of the ICMPv6 
   message is always a GUA.

I'm going to use also a similar text for the unnumbered (link-local) section 3.3.

What do you think?

Saludos,
Jordi
 

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Brian E Carpenter <brian.e.carpenter@gmail.com>
Fecha: domingo, 11 de marzo de 2018, 0:02
Para: Ole Troan <otroan@employees.org>
CC: JORDI PALET MARTINEZ <jordi.palet@theipv6company.com>, IPv6 Operations <v6ops@ietf.org>
Asunto: Re: [v6ops] I-D Action: draft-palet-v6ops-p2p-links-00.txt

    On 11/03/2018 10:32, Ole Troan wrote:
    >> I think you should refer to RFC7608, "IPv6 Prefix Length Recommendation for Forwarding", BCP 198, which makes it clear that *any* prefix length is valid.
    >>
    >> Also split the references into Informational and Normative. For example RFC3627 is definitely not normative!
    >>
    >> About ULAs:
    >> 1) link-locals in ICMP message are equally bad and are sometimes seen in the wild. That should be mentioned, I think.
    >> 2) isn't it OK to use a ULA (or link-local) on a particular link if and only if you program the router to use a GUA in ICMP messages? In other words the rule is not: don't use ULA or link-local. It's actually: do give the router at least one GUA and use that GUA in ICMP messages.
    > 
    > That's not the rule. The rule is stated in RFC4443, section 2.2.
    
    Thanks. It would be good to add a reference. The operative phrase in 4443
    seems to be this: "However, it MAY be selected in an alternative way if this
    would lead to a more informative choice of address reachable from the
    destination of the ICMPv6 packet." What I think the current draft should
    do is specify how to apply that option, if the RFC4443 rule leads to
    using a link-local source.
    
    This isn't exactly a new discussion:
    https://www.ietf.org/mail-archive/web/ipv6/current/msg13393.html
    The issue is mentioned in RFC7404 section 2.1.
    
    RFC7404 asserts this:
    "[RFC6724] recommends that IPv6 addresses that are greater than link-
     local scope be used as the source IPv6 address for all generated
     ICMPv6 messages sent to a non-link-local address, with the exception
     of ICMPv6 redirect messages."
    I can't find any such statement in RFC6724.
     
        Brian
    
    
    
    
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.