Re: [babel] AD review of draft-ietf-babel-v4viav6

Martin Vigoureux <martin.vigoureux@nokia.com> Sat, 06 November 2021 22:05 UTC

Return-Path: <martin.vigoureux@nokia.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9506B3A1192; Sat, 6 Nov 2021 15:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.23
X-Spam-Level:
X-Spam-Status: No, score=-5.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-3.33, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 lkdcVDdtqlrV; Sat, 6 Nov 2021 15:04:55 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0724.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe1f::724]) (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 296253A1196; Sat, 6 Nov 2021 15:04:55 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PPLn7ETIrVoXkxBM4x8hltWFLS654ZGcMQkMLa3fiJzvyCTh7hGnDBOOXFnlCwkxrAgaiY0JTxXtnL54kEBwgLwLgoeJhEJD3EDZawnTb8jK224D8xqGQ9iscKCMkqHDG/RPjcmjSiVGKzbdrxWTAdJa0wUMrIobGpAFScKmTZIvm1RerE1B9ghTwS56o4JuB2WLMq6ZKUX+BncuFbsa6Jj4+jGd3zB04J8lv/Qsc1nbyQcdH1duoCTqeWo0rHPo8dvDi/kPsVspzKmWaHrURqLZmVHf6H1vlSA34Odt/NTcSsF8QtinkBPuK4sjNqZYWrCxBH+0lAFDT/WusY07jQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=OUe8Z8KCH/OmWrs9xOLiCTVU4WhicKRkEDqYxDO1vIw=; b=ieN9KypZ4naF1QDND/07Yq9JTNjq6QSzNz/8jq8LFV5ORELOWNe61yG4YDszJ5zZdCqliq/KDxoazYpDUOZgW720Y1sRz5x55B2vpteMGJts612D4nnzNY3m2jLDBYg3YLgcmxLj0Cn5X+l9zffNk5nqCSGS5nvWl0DsZUiNFtpXVKPJo0rFrdWfu8TRguBoE0wIC2/PXvTetm66IWp0zQaDnCXS5j78PhNpEZnMEvcibbkNaJMQiqztSV4KMxyaA+NYL5s8Dcof9dBG12UrHiTKM4j5W+pNuqqTJvVt3nmR2PWoL6FqNc5+qkLuhhfnHR0I8fQD63ghv65s1XmZ9w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OUe8Z8KCH/OmWrs9xOLiCTVU4WhicKRkEDqYxDO1vIw=; b=XYMJuLHIA8lq2LXLlTE3sMBiOqBhZLovR6p4vism5lVVCs9QBYuXgUusUaVQ/iSIwgc5KT3fTBtG+2HtmW7g2a8uBWCRTTH9/C0MZyPEbt1jI4gdDCNF2HW3mBI2BVuGMjZnwtLjsWmu1wWiXccO+76ABd+es8Ch8rd47rvT1m4=
Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=nokia.com;
Received: from AM6PR07MB5560.eurprd07.prod.outlook.com (2603:10a6:20b:6f::22) by AM5PR0701MB2996.eurprd07.prod.outlook.com (2603:10a6:203:46::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4690.4; Sat, 6 Nov 2021 22:04:49 +0000
Received: from AM6PR07MB5560.eurprd07.prod.outlook.com ([fe80::602d:c982:a27b:a643]) by AM6PR07MB5560.eurprd07.prod.outlook.com ([fe80::602d:c982:a27b:a643%7]) with mapi id 15.20.4690.011; Sat, 6 Nov 2021 22:04:49 +0000
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, Babel at IETF <babel@ietf.org>, babel-chairs <babel-chairs@ietf.org>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87k0hnpw4z.wl-jch@irif.fr> <c1f90d9e-f0d8-2cb3-06b7-0c3b6b65bb6f@nokia.com> <CAF4+nEE+x_nkeG_FMDrGHiaOfc9HwwryDie69ue=imgjov2Hhw@mail.gmail.com>
From: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <eaeb98f4-ac20-99d9-908e-3b1483127f29@nokia.com>
Date: Sat, 06 Nov 2021 23:04:38 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
In-Reply-To: <CAF4+nEE+x_nkeG_FMDrGHiaOfc9HwwryDie69ue=imgjov2Hhw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: CH2PR05CA0034.namprd05.prod.outlook.com (2603:10b6:610::47) To AM6PR07MB5560.eurprd07.prod.outlook.com (2603:10a6:20b:6f::22)
MIME-Version: 1.0
Received: from [172.30.2.231] (131.228.2.21) by CH2PR05CA0034.namprd05.prod.outlook.com (2603:10b6:610::47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4690.12 via Frontend Transport; Sat, 6 Nov 2021 22:04:46 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: cad67b6e-82d9-4d74-3c5d-08d9a171738a
X-MS-TrafficTypeDiagnostic: AM5PR0701MB2996:
X-Microsoft-Antispam-PRVS: <AM5PR0701MB29960EB61AF2C4F00180CB628C8F9@AM5PR0701MB2996.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: Gddj7IQerzvqQQT9XEw2j59m+TKoXFJWbeHk6/BwMabMsZ/fPJBKvv4NodzsN0cBmI7uLhSNvEub2Qx17MRmVjJlXAWVbtulJywXFqrvnU5vkmV2urkPHxuVFBQXEaYs9wiUGaBE3jq4R5N3/Sr6rmHh/lZbtFlEqUCl2OoVktkCvn7/3g3yDOsJE+kW2+FvC+Qz3dNF+FGCJ70GEJcab3Jw8EmYefX2EoQyT/5F+QeCJNw79x6RGDIqLQhL4q9mNlAcWTUNkMJ5hSf9B2E1H+FKodtVolwUSJBkjOF+xgXD+kD/R4WT/pqcpaWSRazPPTQg6Ro8n9RtK7wozo3zxN1hfp+PB1ACifVAeMOazwRRaqZqLBp+WSDevf+fGgYM2Xel9wUgxCwy9hWTvfOzZBGakahY6XjV9sumupQtv7meAMW6PujKd9npYQKnlS7JdIQ2HSYasmxGxZs7eLwxXJiM3NWKQVpeEbsoUVfmAyAKnqpJUUyolG9Z4AlMOB9m/CECarUN+NuhnH/LbGTjDhS7W1XivKkuZmkx0d3G0+fSS/NW/CpLzYTZwqsG4A/eICsH/qotZj053R1skQPf3YvOBWjDjvaYE3lZTv/RiSWSFMVZipnhfkzRqCHkTiL3hdO7Azk7SC0W4CDOG+1t5PSyofcnn/Cujb6QdG5jMxlveDY8oHda8aZLogAsUqiPiewo0afRhWfiPFVHZLj8OG5mxXNOrL/GAVElyGjYOHIAXIh27KFawoQBALo2D9LWURfAPWv6bzhYybABJzE8gUTW4NJ/7nJ7NoqwPAra/3AY7nn/Ddrc4SiXCd7FEUsSX/rc0GBStngYrQ7xPGIEzcw/2fjwpLR7Rspk0gbiEL0=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM6PR07MB5560.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(44832011)(82960400001)(66574015)(54906003)(508600001)(66476007)(66556008)(6486002)(30864003)(86362001)(6916009)(31696002)(6666004)(26005)(31686004)(36756003)(8676002)(186003)(4326008)(5660300002)(316002)(16576012)(38350700002)(38100700002)(2906002)(66946007)(2616005)(52116002)(83380400001)(8936002)(966005)(40140700001)(956004)(45980500001)(43740500002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: XGxSp7F3Qf5u1aXOcytrHSW/vVS7XxupJqneLztbawgiv0pOdpN62AjKzH+4mexSMbcDCe0CDLLHd+S9yMPYWtApjdYiqhwIi9WLqB46u3HMrCFEHbpzgEmwVUUH9XT6m9HR4xePs55j+CHvldhRzAcbhDHBl2NAdODknmbFXGODs409qSxBK4+ki08pTB1+iqNUUYAcKQKgdlcPkrbuAHQBWDm7pf2bPKBdEtbMP1hwrX3vknBp7/zxAXlqYSR+kUdJBpVQFsbExzgQT0hGFOLScIa2e1vTuFHMHHpWiNcqLMrFJlGzmeyFj0r3lnc1v+kim7BikAPnyx0rcHSo+joW0Cai1RanVjCPRrljjn7AU0IiBArzZdT/XeFOhSY/y8cRYV0n5K6/NXdmUmz0Q4LGCC0sSEmuKHvStro9o6SqSTzicVwOJb/cHCYK3QlJ65Hmgnlk6KiHfrOasA9ahCzb5mwU4o2EcBi/+rw3CYL2estmi3L7qZK3rkbJsC8l0IrTTq72T6ytBzC9jx6kj8w9jvA/2ELPRnCyU2RnppHd6DnIyUgEBNHDPdZPeQKPSI59rA+Ah2/arJuQahjmMcFrsxIB5xnZ5O7GE8FDCkfavoxBwD0C8DbbXlxo9v/lR074Ujf+fW0OqkchRfaPLp2+5N3LPtuAReDKyjzvBwAYbA1wharI/xsK/WWA667OF1iV3oQYzUFi+1r7M9Ffq1yFX2z4aI8RyG44bH6AZMy09cewminATJmSOgSCcOmQXNw7ploy1K5gE6X4y/4mzgOnTGZmQ8vtxM+211M2FlhYmXWqy6qXN9Rvpn+THf3UhCpM9vPy29RrB11yI6qG+aXftGxwmCelOhu7VLcfCCSLLM9k5whRWZ1t+ojuiErXuC4WGjiaEsLzf5d3V5bx6JDbPIGXMLGYeXH6+ju0ZEWtkQe45NuIaH+1qw/eOVYpQ2Af812LQ1g2Sva/UliEmBgG3JvOnZfdbq6SiFM+Xgxpqffatkru8iH/6rQJA9NYcfL2ELYvPzq5RGScInJWbqy0VZI/53jN8VcQrHbVIaRuw5bLxXYyDiS0toBSIuA7m3+bru0aj8pYOCF1UA+3akH00wj+JrnQgSYC5eUIJJ6Uia+fQ6g+jS+hqN0K9HlFvaFFTmVj8yVIryzSiyvGJGJQvfCnVfysIaZm6oiws4WH2LGqxksxnj7B3zDBREwEmRBnOng1dI6/n6tbwAnzToELugMkaNLF6WCfspTlDzzp3qUpxw2UN0zJIAbLxZuFxqSHlObabQHV4YFqhac2MQ1r2Oaub1JSuM7h3S4pxbKTmxt+zQzcYUbdy7M81HvHkOeb6ao0wmCa6FmmQh1Ly+WSRJa7IyAtc1MUcG/5zhtXCJV47Uw4W7uXiyJgrphho5fQS57N2fCsU6VPDCIZkGXZuziSjUQPKBZgUDBuk5FO/ewDkJCjYL9NVHGakH1wj+dX5DZ498An+hWnKDMwCebELNchpmkQOcJrzb804WqmCKWdQlIlq49gWRVM8O+vp69VjgWblAwp+ry8gB2gNGtEWR2Wa1DINZpo+WIm7pE65s3+VFsVyiz+EPc+ZWh8IOmUQKnpOSnrBEPxjEyHPjCyfrKFSRg5GokRMvjI8l8VLu+Y7VATPt/eKgPLhKitK9kaOgk6d37bS6/6KbGIiQ==
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cad67b6e-82d9-4d74-3c5d-08d9a171738a
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB5560.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Nov 2021 22:04:49.3050 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: Hh1N35jZpHzNOzNrOyNLiBDwJJ36KYvjUc0AGnzGvN0T6Yvq9JRKVPqITiESpty1OYRkWpG/XHBPIiZonC3xorVxNk6q/mX53WmODZLeKxY=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2996
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/iG3Biwp4TZCHs7Ot0AKt8VRLkHA>
Subject: Re: [babel] AD review of draft-ietf-babel-v4viav6
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Nov 2021 22:05:01 -0000

Hi Donald,

please see in-line.

regards,
-m

Le 2021-11-06 à 5:22, Donald Eastlake a écrit :
> Hi,
> 
> See below.
> 
> On Fri, Nov 5, 2021 at 2:26 PM Martin Vigoureux 
> <martin.vigoureux@nokia.com <mailto:martin.vigoureux@nokia.com>> wrote:
>  > Juliusz,
>  >
>  > thank you. Please see in-line.
>  >
>  > regards,
>  > martin
>  >
>  > Le 2021-11-04 à 20:18, Juliusz Chroboczek a écrit :
>  > > Thank for your review, Martin.
>  > >
>  > >>     A Babel node that needs to announce an IPv4 route over an 
> interface
>  > >>     that has no assigned IPv4 address MAY make a v4-via-v6 
> announcement.
>  > >
>  > >> If the Babel node needs to do so, what other option does it have? 
> If none,
>  > >> then MAY may not be the right keyword.
>  > >
>  > > I think "needs" is the wrong word here.  What I meant to say is that
>  > > a node that would like to advertise a V4 route may choose to make
>  > > a v4-via-v6 announcement, but of course whether it actually does is
>  > > a matter of local policy (subject to configuration).
>  > >
>  > > I'll try to find a better formulation.  (Any suggestions?)
>  > I like Toke's proposal from which I would in fact remove "can".
>  >
>  > >>     If the outgoing interface has been assigned an IPv4 address, 
> then, in
>  > >>     the interest of maximising compatibility with existing 
> routers, the
>  > >>     sender SHOULD prefer an ordinary IPv4 announcement; even in that
>  > >>     case, however, it MAY send a v4-via-v6 announcement.
>  > >
>  > >> I don't understand that part. Why do you allow a node with a v4 
> interface
>  > >> to use a v4-via-v6 announcement of a v4 route?
>  > >
>  > > The v4-via-v6 next-hop is usually a link-local address, which is 
> likely to
>  > > be more stable than a v4 address.  If it is known that all the 
> routers in
>  > > the domain support the extension, then it may be better for the 
> network to
>  > > make a v4-via-v6 announcement.
>  > >
>  > > At any rate, there's no good reason to forbid this behaviour.
>  > I'm not asking for that. I'd however suggest that you incorporate the
>  > explanation you have given above, in the draft.
>  >
>  > >> I'm not an ICMP expert, and I may not have understood what you are 
> aiming
>  > >> for here. While the first proposal (using loopback) seems ok to 
> me, the
>  > >> other don't. I think that it is not good practice to be using 1918
>  > >> addresses beyond private networks,
>  > >
>  > > This was discussed at the Babel meeting of 4 March 2021, and the
>  > > discussion continued on this very list throughout the month of 
> March.  It
>  > > would have been appreciated if you had participated in the 
> discussion back
>  > > then, and I find it somewhat discouraging that I need to summarise the
>  > > discussion before even reaching the IESG.
>  > I understand. It's not always easy for an AD to monitor all the
>  > discussions of all the WG he/she oversees, but you are right in the
>  > sense that I should have done my homework better by going back into the
>  > archives and meetings before sending my e-mail. Point taken.
>  >
>  > > I refer you to my slides of 4 March 2021, and the discussion on 
> this list
>  > > starting on 14 March 2021 titled "Dummy Source Address".
>  > >
>  > > The case of a router that has a loopback address is pretty obvious, the
>  > > loopback address should be used as the source address of the ICMP 
> packet.
>  > > That case, however, is not very interesting -- if the router has
>  > > a loopback address, then it might as well use it as the next hop.
>  > >
>  > > The problem we're trying to solve here is that of a router that has no
>  > > IPv4 address at all.  While you might argue that RFC 1812 does not 
> allow
>  > > this case, such routers are being deployed, and the alternatives to 
> this
>  > > proposal require either tunnelling (MAP-E) or address-translation 
> (MAP-T,
>  > > NAT464, etc.), either of which breaks a number of desirable 
> properties of
>  > > the Internet.
>  > >
>  > > The proper solution would be to avoid sending router-to-host ICMP 
> packets,
>  > > as described in my slides of 4 March 2021.  This is not a new 
> observation:
>  > > the whole point of ECN, for example, is to replace the unreliable
>  > > router-to-host "Source Quench" signalling with reliable end-to-end
>  > > signalling.  Unfortunately, PMTUd is deployed in the wild, and we 
> need to
>  > > do something about it.
>  > >
>  > > Hence, we need to send ICMP packets, and we need something to put 
> in the
>  > > source address.  The most robust solution is to use a distinguished
>  > > address allocated to the local network.  Failing that, you may 
> either use
>  > > an RFC 1918 address, or the dummy address.  Nobody finds these 
> solutions
>  > > attractive, but remember that the alternative is NAT464 or other packet
>  > > translation technologies.
>  > It looks to me that the problem you're trying to solve is an ICMP
>  > problem, not a Babel one, although it appears in the context of Babel.
>  > If that is the case, then you shouldn't try to solve it as one section
>  > in a Babel document or at least you shouldn't say that an implementation
>  > can choose whatever source IP it wants.
> 
> I don't think the draft says that a Babel router without any assigned 
> IPv4 address can use whatever source IPv4 address it wants. It suggests 
> the following:
> 
>  1. Using an IPv4 address that has been assigned to the router or some
>     other interface of the router.
>  2. Using "a source address from a prefix known to be unused".  For
>     example, if we are talking about a network not having IPv4
>     connectivity to the Internet or only IPv4 connected to the Internet
>     via NAT, the network manager may know of an unused local prefix,
>     quite possibly an RFC 1918 prefix.
>  3. Using the IPv4 dummy address as source address.
> 
> The idea on point 2 is that a receiver of the ICMP would get more 
> information about which router had issued ICMP if there is at least a 
> good chance that they use different source IPv4 addresses. Admittedly, 
> if the routers are going to be individually configured with some IPv4 
> address known to be unused in an isolated or NAT bounded network, this 
> is not really different from case 1. So 2 only makes separate sense if 
> you have a scheme to just configure the prefix on your routers and then 
> let them autogenerate an IPv4 address with that prefix...

The draft clearly says:
    There are various ways to meet this requirement, and choosing between
    them is left to the implementation.  For example,
This clearly says that the implementation can choose amongst various 
ways. What follows are only examples of some ways.

> 
> For point 3 see below.
> 
>  > >> and overall, I fail to understand how a response to the ICMP packet
>  > >> could reach back the originator if it has used 1918/dummy as SA.
>  > >
>  > > The dummy address is being used as the *source* address, and hence 
> doesn't
>  > > prevent routing of the packet.  Some over-zealous packet filters might
>  > > look at the source address, in which case you'll end up with an ICMP
>  > > blackhole -- but that's already something you need to deal with.
>  > I understood that, but I still have concerns
>  > - rfc 7600 is Experimental while this document is Standard Track so you
>  > are taking a level up the procedures defined in 7600 (the use of the
>  > Dummy Address for ICMP). A way around that may be to register your own
>  > special purpose IPv4 address, or be clearer that it's an Experimental
>  > mechanism (though I'm less sure about that).
> 
> I do not think the status of RFC 7600 has a controlling effect in this 
> case. The protocol in Experimental RFC 7600 needed a dummy IPv4 address 
> so, I assume, it was the motivation for the allocation of 192.0.0.8. But 
> there is nothing about that allocation that is temporary or tied to the 
> protocol in RFC 7600. These questions are answered by the column entries 
> for 192.0.0.8 in the IANA Registry at
> https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
My comment is not related to 7600 and Dummy being tied or not, or Dummy 
being temporary, or not.
7600 defined a procedure for using something else than loopback or 
interface@ as SA. By construction, this is an Experimental procedure. 
This draft, as currently written, is making that procedure a Standard 
Track one.

> As indicated by the "Termination Date" column, this is a permanent 
> allocation of an IPv4 address. As indicated by the 
> "Reserved-by-Protocol" column, this IPv4 address is not reserved for the 
> RFC 7600 protocol. And perhaps most important, when 192.0.0.8 was 
> assigned, it was given pretty much the most general name it could be 
> given: "IPv4 dummy address".
>       It might have been nice to assign a separate IPv4 unicast address 
> as the "Babel v4-via-v6 IPv4 dummy address" but isn't it obvious that 
> would be a strict subset of the 192.0.0.8 "IPv4 dummy address"? Given 
> the above factors and that there is deployed code using 192.0.0.8 for 
> this purpose, I favor sticking with 192.0.0.8 in this draft.
> 
> However, something like the following should be added to the draft's 
> IANA Consideration:
>       "IANA is requested to add [this document] as an additional 
> reference for 192.0.0.8 in the IANA IPv4 Special-Purpose Address Registry."
> 
>  > - it's still not clear to me how ping or traceroute work with that
>  > scheme. These require a message to be sent back to the source. If a
>  > Babel source node used Dummy as SA, how can a message reach it in return?
> 
> OK, a node with no routable IPv4 address cannot successfully originate 
> IPv4 pings or run IPv4 traceroute. But I'm not sure why such a node 
> would want to do that.
Maybe that should be clarified, because that section generally talks 
about ICMP so one could expect that all functionalities of ICMP are 
expected to work, while they in fact don't.

>        A node with an IPv4 address can send IPv4 traffic and (modulo 
> network blockage) get back ICMPs. Furthermore, it can also send pings 
> and do traceroute to other reachable nodes with IPv4 addresses. It will 
> not be able to ping nodes that don't have an IPv4 address. And it will 
> get back somewhat uninformative traceroute responses from nodes along 
> the path it is tracerouting if those nodes don't have iPv4 addresses. 
> But it seems to me that ping and traceroute will still be of significant 
> use.As it currently stands the draft doesn't detail much the limitations of 
using ICMPv4 for ping/trace when the sender and/or the replier don't 
have a v4 address. If the choice of the solution is left to the 
implementer then he/she should have at hand the elements enabling 
him/her to make the right choice depending of his/her context and objective.
As said, the issue is an icmp problem, not a babel one, so I'm not sure 
you want to go down that path.

> 
> Thanks,
> Donald
> =============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   2386 Panoramic Circle, Apopka, FL 32703 USA
> d3e3e3@gmail.com <mailto:d3e3e3@gmail.com>
> 
>  > > -- Juliusz
>