
From nobody Thu Nov  4 10:53:45 2021
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 DEEB73A11C4; Thu,  4 Nov 2021 10:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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 WPsnGTyyfivN; Thu,  4 Nov 2021 10:53:30 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130107.outbound.protection.outlook.com [40.107.13.107]) (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 1932D3A1228; Thu,  4 Nov 2021 10:53:28 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SgVsa2ufixmD+n1GVrWbSiG2WIhSlg3SdlZ/yaFJzCRfGzAE0UHqZ/fQzUrrJYuY2fHLTkS44B/RlpyPWMrpS/Uf3+3LLAf7+06zDXyr/GCvsa78wrEUZLcXGdATJbVJ3i/8Hkcpj1Z9MEVy+6ofsHH8jngHX21KeOtKvX7THrfeZ4LxOiTSdZ+RA/1zv3x7270ymbgwkQf9ECuImxseWhTcSz/6zAWtR0TxTn2CdqLhllFvqtdxuZRfMN7MU255IpMe+vRbhpJT1GBtumKJSU1EQHgkWP03Ugej8IIlSeY+zkViQVbCfEUUHl0eYtZj6FDX7UrrtFxSqVAq8HrcuQ==
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=9Nr6Gf41yhUyEv7ydPU6eFwzPV671ZB4hnucNiUN8CU=; b=HYcGBOyqvMKAOFYVxsRa/IfFYXJEh6//E1vuifANNE7ngfnGdOdXXKoUFgT6CPfOeTjpvbSW9X6zaMrgaEtPLxySObGTMxkNw5+fHfpVk8Hld4MugBbdQ4pYITidzWmJT0NY9mJ25k10iU60pBIThjAX0QVPD1enppVlOwwwXvUDFpXx2TiycqA+TPndlg60ZduWQVKCioaDh381a38L30hwZ7PqjC5x5n5BfPy1uu32mO8/qjrvgjnmRxwixoOgc4gbjOq9jPFKG9Q5H2O+9ohENRnSm18e9ftAZJD0F7z8u6EXgjEY1WjMxmieXk+VmuTjVaETfhzPVtWc/LVxXg==
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=9Nr6Gf41yhUyEv7ydPU6eFwzPV671ZB4hnucNiUN8CU=; b=clOhdMjBlWgP36zzpolcKWbelgjrSuCHfVweaOPe0o79TdET7HJgay22BBCQWpsKckuaNEHt+dc/rMR7+OTRXJNCj9DoCJMW5PCP3heespkO9P+LALPiZpKhDfEjNtRA87YntF/socX98VbCWuaH5cUnXJZ8vS9J7yq93+thDAY=
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 AM5PR0701MB2913.eurprd07.prod.outlook.com (2603:10a6:203:43::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4690.5; Thu, 4 Nov 2021 17:53:23 +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.4669.010; Thu, 4 Nov 2021 17:53:23 +0000
From: Martin Vigoureux <martin.vigoureux@nokia.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Babel at IETF <babel@ietf.org>, babel-chairs <babel-chairs@ietf.org>
Message-ID: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com>
Date: Thu, 4 Nov 2021 18:53:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: CH0PR03CA0316.namprd03.prod.outlook.com (2603:10b6:610:118::23) 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 CH0PR03CA0316.namprd03.prod.outlook.com (2603:10b6:610:118::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4669.10 via Frontend Transport; Thu, 4 Nov 2021 17:53:21 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 06063396-1d6f-456d-0eb4-08d99fbbff14
X-MS-TrafficTypeDiagnostic: AM5PR0701MB2913:
X-Microsoft-Antispam-PRVS: <AM5PR0701MB2913430EA20543F93E9BA8B68C8D9@AM5PR0701MB2913.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:7691;
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: nQvcmIHnaAgam+GS6ruCpT9XiQRiZ3g2NKCpWf+ox536JkNdGrBe68fPoRZHHIRdXMTkf89rIFs0q7HtWPquoWpGjJp2OHwMz7wy62zdPvVT19lmcI9g+XZu9SKGh0QOPdtPZT9waDaeegh33U1n6EL8O6sB7IfIx/uO5W1D+Xv6lm6dS+XX3ovMx2lpEYzj7mp8IeBu79YQ1ZgGxajlFgH9Rtc3KvJePviK5qEMeXIbtkTnnG8c5uIZwXD7U6uPuxVPVZW6Xc6C2XII6z0q3il+ckcRFUtfsbzgwv38WrFedKDGSQ+TaT6Z7uROm1LsmNeUnq3WREgQaTresJefBxrQdRkjSZoegb0l/nvMszGJ5kIttJqlSYCrO3ot+Na6N5pbqhw1qvmmSaKDGg0+NbBILhucksZRDMNUTvR9W3Cq0N5/CQ7Onsj6gCFm/aMoVC9LmKJXUD0xTUtLB9MddYWb2mcarIz6JVgDHN+99Z0zHc4iw2e+qwqQBX4YsSu5Ay+yAW5exHKLGmuxtKJrYCuYf1MWPAvc8I4hMid6Y3KaJO7niA4ZaDzhZ3oQiCOFBBFV0GBcqYTLDmflexBA6uYnwR4BnqZbDHD6v+6ieSa88S7qSbJab7JazNS7d+bk8KCzTDVAHY8Y9lQRPe0AedPwNrk8D+VPIVeL5tO36QANLO8vAt1coCi5k6ikO1hBC6uC0HeNqGdvazZU+b+IeeSrMY+6lMU0FZ+ClvFq4jYFhGvLQS/1kZvLNB0SYB3mY7COQ0DehGmcjShDxp+Fxw==
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)(83380400001)(86362001)(956004)(66574015)(31696002)(2906002)(44832011)(31686004)(66946007)(82960400001)(66476007)(66556008)(6666004)(5660300002)(4326008)(2616005)(316002)(6486002)(52116002)(36756003)(8676002)(508600001)(54906003)(38100700002)(38350700002)(26005)(186003)(6916009)(8936002)(16576012)(45980500001)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?K2dSMkhEMHUvTHB3L0JtdHRKRk1aTCtQUWx1QzdWRlNWVjdGWVliNUwrOE9Z?= =?utf-8?B?bVlDQ1BISzRuZSt5NDlmWGRNZFo3ZkpQb05HMGR2ZjZhRkNuaCt6TUVSM2kv?= =?utf-8?B?eEtKRU9ONmdLamxuTWlCR2hsQjZzcVBIMVNxUStOZ2lKbkhNRGR1WGRDZTVw?= =?utf-8?B?eHI2MW1MaHk5cSs4RURKZ1pvSGZEL2xRTjlwQ3hQWGxOTlBnbGJxVlFmaEZP?= =?utf-8?B?aDZueU9DMGp2c1ZSRWJMR1hYZGlTcFBkS2NpVXVNdlhUNTdCSkJnMndKZk4y?= =?utf-8?B?QzgwSDBhT0dOZXlERUNGcGVIaXR0cnE0ZGNud1h6Y2haVDZJa281R0lmR0VO?= =?utf-8?B?T0Rxc0R3aHFYcm9IdXI1djJTbUYwbGU5QnVDaDVRM0lBWjl4ekw0b2RtYStB?= =?utf-8?B?WEZRK3dMUGphMnM3Y25pZTdWL3FJeG1UQ25MSzJxL2xXMXNUVGh1SmUxejlm?= =?utf-8?B?K1Njd2w1S3AwdWNwOGlUUUhLVDh2Y21vbzF1TFhGYnBZWW4vRy9wQlBXVG04?= =?utf-8?B?QU9BTTI1YXNma05qOVZXdGx5WDNvVkl3V05BRWxrTmY2WUhHSjZoSHdUVzBt?= =?utf-8?B?T25mZ2pxK1ZITXRNeEduejJadHJhd3FWWkMyVldLWHpPbWxMU1VFMTRiWWd2?= =?utf-8?B?OGlFemw3NW1NTkIxdmxkeFFhNnI1WTNaK1ExSk1DUVY0c1hwQmh0U3g3dzRP?= =?utf-8?B?WjVJMDE3a1NVRUlkWit5S0phTld3Y3ZLai9EanAzTG9FV1ZlK3Btbm5GV1FY?= =?utf-8?B?aXpickYxL2RuK3VST3dVZVM3bmh3YUxxcFdBaEZIVW5qa0Z6Z3pxb3NnOW5h?= =?utf-8?B?MW03QW1HWFZidkUrT0czeHVVekRqaHlhWGJ0czNKZTVWODZ5RDlhQ2VKMEF0?= =?utf-8?B?clNrUE5CQ1RHamRHRUdZOEgxQVdMRWtUVjJqVjIwNlduemJhMllDMytyM3BD?= =?utf-8?B?V2hRQjVOd1lhTHd5b0FSMU1XVm5CbGVaSGxra204cC9yb2NRUFhjeEMrSEQ4?= =?utf-8?B?bEpvKzNPQW01MllBaGEzb1Y3OGJuak54eEZ4TTYzOUduWkFDM29VMG5RUjhz?= =?utf-8?B?bjN0RGc1UllOWFhsVU5YRVlvSExzY2VPQ2xEdFlOV0dSZUg1Q3lDeVc0andM?= =?utf-8?B?R2JuSGZla0w0bURmYmZKb3l3eXVPQkFWZTUwSzR2ai84Vm0xT25PNFZMZGl6?= =?utf-8?B?V1RpaVBGN2g0NWl2MHVRRlRRbCtjSnZ2V1FpTkErSWtIL2orV054c2Qwekda?= =?utf-8?B?OERxMXBYdDNFRHE0M0NRQkJXVTBraTVteHdOUmFxUWdTNGxHZ1N5TkFSWDNk?= =?utf-8?B?NEpqRlBWM3BOQ0VxZWhreHRIckN6QWE4K05nS2E0OStoNDZZRzJsbitKNlho?= =?utf-8?B?aUFuNTArYjdNM29BNWdQTFUvK0QwbjdXa0s3RkpGbVdlS2JiUTdJd3RaMi9t?= =?utf-8?B?bVBZZzBVODN5WVJIY2M1QmJZRjFMbGRtSGdMU3lsNXpycVFwczB4NUxSMkpa?= =?utf-8?B?UzRzRWN1VVVpT1NHMVdNQzlPOFhlZlhCU0owMnY1Q0tGa3Zwd2xFYkhqOFRH?= =?utf-8?B?azBrT2JtWWRseTZVVEYwdUpFRGJsOW8ra0VlWU1aZzFiYzFmOUUvb0tOL1B1?= =?utf-8?B?UU5EbkJINFByempWb1VVYjNnSTA5dDdJS1luWVpPWWdndXZFVjl1OUZYR29y?= =?utf-8?B?V2NyMFpILzQ4S2JScHRhVmZ5N0s0eWpSRE41QW1XZXJ0KzQySDVFL2s4Sk5J?= =?utf-8?B?clYvT1VEWTFMaCtUSnZxSnhSMlI1QkI0Uzd4bzFxUTZ3d1A4WlhKR1JxbVNF?= =?utf-8?B?RzREVUhhSUFVQXpvOW56VUlYTllCdHZ2S2NuUW8vM1dCcndYMTJXWVM0b3Va?= =?utf-8?B?eGFrd3pPbHlzVjRuZXVsNExSMS9ST05CeXNsZmZLM3YvY2ZsMHRmUk1jOTFw?= =?utf-8?B?R015d0RWcGR0WktmSEVXNmVOaWI4K3gyMG1mYzNndzZXRDNTMWdwdjlRdmJt?= =?utf-8?B?aElLRmd4ZFdQc2hBNjJ3NnFTN0dOYjZmWVNWLzZ3dlFwZE5qVmZSZGVkekVv?= =?utf-8?B?cVBwYVpkQ1FqOGV3TnJhZkpjS3prYUIySkZ1WnhiMUJHSDZQWWNsS3gyUG9q?= =?utf-8?B?emFCYXpJcWQ5bHd2RGM0aFQ1eWwzUmxHdVRPbzJJcE1QQzF4eEdRL3hWTHFZ?= =?utf-8?B?ZXRmaGMybGdMc3R5emFmVE9VcDFwUTlCbnN6Wjd6Q2RvNklEbjI2Qkkzek9G?= =?utf-8?B?RWYyN1dURjBramZqRHdPRFQvaVh3PT0=?=
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 06063396-1d6f-456d-0eb4-08d99fbbff14
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB5560.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Nov 2021 17:53:23.7550 (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: 62KojRYloCaL2GJSbi6saPJcbyVirF12B0ATKQkVAT9HIv47e7EziY8kXuGTYrAJ0cZnX/QihWtRrv8e3ankN0nnW7WTOs4ilYvCKWx6QrA=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2913
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/p0f-GFNNHjiFb-uwfWvCwQlXH9M>
Subject: [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: Thu, 04 Nov 2021 17:53:43 -0000

Juliusz, WG,

hello.

Thank you for your work. I have reviewed that document and have only few 
questions.

-m

    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.


    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?


    There are various ways to meet this requirement, and choosing between
    them is left to the implementation.  For example, if a router has an
    interface that has been assigned an IPv4 address, or if an IPv4
    address has been assigned to the router itself (to the "loopback
    interface"), then that IPv4 address may be "borrowed" to serve as the
    source of originated ICMPv4 packets.  If no IPv4 address is
    available, a router may choose a source address from a prefix known
    to be unused, for example from a suitably chosen private address
    range [RFC1918].  If no more suitable address is available, then a
    router MAY use the IPv4 dummy address 192.0.0.8 as the source address
    of the IMCPv4 packets that it sends.  Note however that using the
    same address on multiple routers may hamper debugging and fault
    isolation, e.g., when using the "traceroute" utility.
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, 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. rfc1812 in fact seems to 
forbid that (section 4.3.2.4), though I didn't check if this requirement 
had been updated by other RFCs.
Anyway, could you elaborate on the above?


Nits
s/RFC5549/RFC8950/
s/IMCPv4/ICMPv4/


From nobody Thu Nov  4 12:01:37 2021
Return-Path: <toke@toke.dk>
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 ACAE53A15B4; Thu,  4 Nov 2021 12:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
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 xO5FG8Oj8a-7; Thu,  4 Nov 2021 12:01:22 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (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 D8DF43A1420; Thu,  4 Nov 2021 12:00:57 -0700 (PDT)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1636052453; bh=mSzbfHqEgVfQfqXzPMPIhchEu4TZKtsPiFWmVdBtDl4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=vmZB3iAe/aYDoYy89SIMCDW5V73pRT07/tca7I/ZkTR1EaSJ0CTRCeotvOBo+hMzl 8RUVnyL4Y9ZtWrvtyzd58l+UI+QSRYfN6CRkfY0XXPsyjhsAH4dcLAla+ZifHbRX/N mMNW3UKdY1S0JH7tnQJ2HhNWmXLqtO7uYRG6JVMS12ORAa1K5nnjhznAFW7U8gWCze kmHoE28YrIVVFLNO415o/If0/U8tnP/3gvpiKJCMB8bghWnGxj79AgVnNdSCXAdMLj 3v5NrQH65dPV/XDcwAJGXyxfyxPQjpg0EWCh3vgqWpRwEvl0shzPo1iWz83UVx54lt KDBnDGrbC/0mA==
To: Martin Vigoureux <martin.vigoureux@nokia.com>, Juliusz Chroboczek <jch@irif.fr>
Cc: babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>
In-Reply-To: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com>
Date: Thu, 04 Nov 2021 20:00:52 +0100
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87v9173fvf.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/Bbc8myIte1lJf2Mf4heZKZcEMkM>
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: Thu, 04 Nov 2021 19:01:35 -0000

Martin Vigoureux <martin.vigoureux@nokia.com> writes:

> Juliusz, WG,
>
> hello.
>
> Thank you for your work. I have reviewed that document and have only few 
> questions.
>
> -m
>
>     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.
>
>
>     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?

One reason to do this could be to lower implementation complexity in an
environment where you don't have a mature networking stack to deploy.
If you route everything via v6 you don't have to implement ARP at all :)

>     There are various ways to meet this requirement, and choosing between
>     them is left to the implementation.  For example, if a router has an
>     interface that has been assigned an IPv4 address, or if an IPv4
>     address has been assigned to the router itself (to the "loopback
>     interface"), then that IPv4 address may be "borrowed" to serve as the
>     source of originated ICMPv4 packets.  If no IPv4 address is
>     available, a router may choose a source address from a prefix known
>     to be unused, for example from a suitably chosen private address
>     range [RFC1918].  If no more suitable address is available, then a
>     router MAY use the IPv4 dummy address 192.0.0.8 as the source address
>     of the IMCPv4 packets that it sends.  Note however that using the
>     same address on multiple routers may hamper debugging and fault
>     isolation, e.g., when using the "traceroute" utility.
> 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, 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. rfc1812 in fact seems to 
> forbid that (section 4.3.2.4), though I didn't check if this requirement 
> had been updated by other RFCs.
> Anyway, could you elaborate on the above?

The idea is that we want there to be *some* ICMP errors going out, even
if there is no v4 addresses configured anywhere. And using a private
address or the dummy 192.0.0.8 (which comes from RFC7600, BTW), makes
this possible. Many networks will happily route such packets; and, for
instance, having traceroute return multiple hops with the dummy address
is better than not having any replies at all.

We recently fixed Linux to use this dummy address, BTW: 

https://git.kernel.org/torvalds/c/321827477360

Prior to that change it would just cheerfully send out ICMP messages
with a source address of 0.0.0.0, which obviously doesn't work at all.

-Toke


From nobody Thu Nov  4 12:18:46 2021
Return-Path: <jch@irif.fr>
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 80DEA3A1479; Thu,  4 Nov 2021 12:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 UflmWMu4fkX5; Thu,  4 Nov 2021 12:18:42 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 2DA863A1476; Thu,  4 Nov 2021 12:18:41 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 1A4JIcb9010848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 4 Nov 2021 20:18:38 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/82085) with ESMTP id 1A4JIcWD007732; Thu, 4 Nov 2021 20:18:38 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 397AFE989B; Thu,  4 Nov 2021 20:18:38 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id PwxcysJyCMsj; Thu,  4 Nov 2021 20:18:36 +0100 (CET)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 3F97AE9898; Thu,  4 Nov 2021 20:18:36 +0100 (CET)
Date: Thu, 04 Nov 2021 20:18:36 +0100
Message-ID: <87k0hnpw4z.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: Babel at IETF <babel@ietf.org>, babel-chairs <babel-chairs@ietf.org>
In-Reply-To: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 04 Nov 2021 20:18:38 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 04 Nov 2021 20:18:38 +0100 (CET)
X-Miltered: at korolev with ID 6184320E.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 6184320E.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 6184320E.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@irif.fr>
X-j-chkmail-Enveloppe: 6184320E.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 6184320E.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 6184320E.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/jS_c8DB4rnQ1cZc2Mo1WFUPol5I>
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: Thu, 04 Nov 2021 19:18:46 -0000

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?)

>    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 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 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.

> 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.

-- Juliusz




From nobody Thu Nov  4 12:32:17 2021
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 DB1ED3A14C3; Thu,  4 Nov 2021 12:32:15 -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 A-Ar5jaYMzb9; Thu,  4 Nov 2021 12:32:11 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2071d.outbound.protection.outlook.com [IPv6:2a01:111:f400:7e1a::71d]) (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 2CDE13A14BD; Thu,  4 Nov 2021 12:32:11 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ew7OQKlIa8wLWBfqtbAnezyE/ZDmmqNydRJedB23kIC2esu6FBxgmYOPU7X4haRd9LiTpEsYsGaYlpDE7oOxqL4zrllyBjVxlvT6ky5A7L1a3nDFffaPcXvngep0cqnPfomCZVFBURBlzeaXJleVxCFvd8tO+zeCuhUhhz3vjPimB1CvwovcXtUtrWMeswBRv5oVe/1AbR8kRo0QYs9nkN7xZ+z3W1DJQgUH2JioTVAN8xBd+c8ri9TSdturBlgcFLBpHzJxu1NJes5ebdrT5Hfd/PNkCaoqLUopiNVfW/ZPJlqoytL11LOccanvJHRq32a2ktx1r130dJdC6QLJ+Q==
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=GFPul6N++AyB6pSosqPTKsiDfD+1RSlStSRn7037zAE=; b=WT7bKAy73UZTja9VU2k8DtQcFzCuo4cCuYim3/JduVU8rh9evWsmfqWD1iHH0vniAkxqzSyusId8k7uHWLzkowVrT5FL7yD4XiT8FDRc2rZg4stvW48B45qp039gqd2135Dh/SZDb8WE/FfdPMspdvl8LKUj6GdtEOIwokWkvkoqlvUC3EwieaLOxOcEiojAu00x8d6I+bjVzcM/waJjiYeIXsu213CRgSA+P+fKzs7sqt2uyF0nEdj+qujeFUArbXtCXFiFqAMKqmv2vI0QcO/6wMjN+3VqFkanfWOZpaHgqjJs6iu40UjQnp0x0hg+WYoaKSjN5CXdAtMVizKNuw==
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=GFPul6N++AyB6pSosqPTKsiDfD+1RSlStSRn7037zAE=; b=Hgg8Gh6rGmbQB0FeO01eeCRq/g2+0jIu0rNbxZYoD08sRSCde8pJeuyhnhMKY6+TP5fGTXBTG0e3AdHI23xVTims980XVz//1mx9ayR/mNoB0ZhirHq3PHGf1Y5UhK/qtFAqEjoOPvcT/LWl6BFjwChBBLKFqCsrbuAdl35UQ/g=
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 AM7PR07MB6325.eurprd07.prod.outlook.com (2603:10a6:20b:13e::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4669.5; Thu, 4 Nov 2021 19:31:59 +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.4669.010; Thu, 4 Nov 2021 19:31:59 +0000
To: =?UTF-8?Q?Toke_H=c3=b8iland-J=c3=b8rgensen?= <toke@toke.dk>, Juliusz Chroboczek <jch@irif.fr>
Cc: babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87v9173fvf.fsf@toke.dk>
From: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <6118de6b-2ae6-f690-7be6-7fe00984878f@nokia.com>
Date: Thu, 4 Nov 2021 20:31:46 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
In-Reply-To: <87v9173fvf.fsf@toke.dk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: CH0PR03CA0201.namprd03.prod.outlook.com (2603:10b6:610:e4::26) 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 CH0PR03CA0201.namprd03.prod.outlook.com (2603:10b6:610:e4::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4669.13 via Frontend Transport; Thu, 4 Nov 2021 19:31:55 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 93bf0495-3a5c-4e92-21a4-08d99fc9c4ff
X-MS-TrafficTypeDiagnostic: AM7PR07MB6325:
X-Microsoft-Antispam-PRVS: <AM7PR07MB63251D12DED62DCA225C02848C8D9@AM7PR07MB6325.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: 1Ykz/UnlzJxj0ZSFDvAUC5zCFliou9HhMftZBkAHMFFht49u4guGIwPH8msooopE6aTlfshCZVt0NwdBEbvLDM8hd2Xjhtjmu102hYBige7sYuouEXmDvYXALEIRC+iM6IwxfjFJ53C6/rHLy8Y0zHKSTpnRj+AvJrSZvm1MU7/2EV77SFo+TJdcFJWGENcGBvfQbXtSEAEOxscZGEs/uvTkPYJHXFbHSWH4luikhiB7YxhRjGCwLrs/YuHNzqCB2SdFGnvcczjyl3Y/qO4giEM9Yfj8rU7gtI9rsi2RM6lycJF316UWfkzxdB3o2jwhqeiISqQDQHlcLsmKXagSalyV5/QZtfiI1VGjyVOmfiOfYEFyq2Ut6ZtRK1FJ8eWBAyU5PTMPRSc5gntK6/GpkJat9NvPlR6AZpoYSNu2udDlcfq2RCCGMNvOT74US4pN//XTP9qJlKkkf3kpgY5ASIPN8NjmMN6xiFZeenEX0AYY76kiZcwDziPbi/nbLc6pnQBXvDtUkcch0unzfDv5V228o/m4w9iv2bhJ+IpmP3JOpI1Gia9ICrYEFBUP7yaF8XGySVIy2AhfiBksRx/pJd5zOg/vj9DuZ5iNB0XmRwn3j6asB9Qy/dcGUvBGS+CGEKd0zQ8rKJQ9vrSwZyUy8u8ierSTxY8oYTf65D2fgKWzM3P19ObkQ6URLpGsy8BDnK1EllCcAHOYav68K6UsBdyAA0H+xlkHDfYUfP7HJ/8I8N3rwDxreyR6odRBL7HZKbOlXxzct5OzPBSA919/QcCwX5sUk+e8DmvRdMRhTpFCO2mZjJNXZUZai4r41XUJFQY/C4PJUYwasgksUGiX5ubMomqUKVORH9WDOAx31aE=
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)(38350700002)(38100700002)(82960400001)(16576012)(54906003)(4326008)(186003)(26005)(36756003)(83380400001)(5660300002)(8676002)(508600001)(44832011)(86362001)(52116002)(66556008)(2906002)(66574015)(966005)(66476007)(956004)(6486002)(31696002)(110136005)(6666004)(8936002)(316002)(2616005)(31686004)(66946007)(43740500002)(45980500001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?R29HNWE3SmFMZlEranNXTlNrQkJ4blM3U1lpdDJUampnTjVzRkVBNU1lVklo?= =?utf-8?B?MmZFSDM5Z0gvK1VOc1U3dU5kMXRMbS94d3pCQnQ5QmUrd0VIN211NGZDV3FF?= =?utf-8?B?RDI4WUFER29XWDcvV3VCdVBhQjkwYU45U1JUY1Aza0VYZVVTRi96OVZzRTJQ?= =?utf-8?B?WTJadWtLb0hLUysyVUFUSStJeWJoUFVRUlNCQzdMUzNMZlRjWTBUSFU5ckly?= =?utf-8?B?aEpNdlF0L2g4OGNnT3hnY0lqRjlDRTc5RlFZNGcwN25UdGNJNmZjeXBFM1pL?= =?utf-8?B?bHdjc3FZVGRrRnJPS2ZDT1JHR2dZQjhqaTNwMlNjbmhmSVhxdG9FSEdqcWRR?= =?utf-8?B?ZG9rcWxxWWRGNSt4Yld6Tk0zb1VGTVdhS29xT3N5MEJNWEl3NHVHZzR1bTB0?= =?utf-8?B?ZmZrTWU5M1JoclF2a1gyM3VMS0NTQUkyWTFlVzRRRG5FTkpZRzFmdE5wTTlS?= =?utf-8?B?a1NPNGdhMzExKzRXWkhYVDE5d0tnUmhJUU9WaFhzd3BEWkpKaEV6RHVxd2Vj?= =?utf-8?B?bjN1akxWSlF6ZlU1bEVyNkF3OVlUOUU1Z0hrcS9KSnNhNlZLVnF2TkFrVjN4?= =?utf-8?B?YytuS1VyNFBOQlR3UEF5TWFIWjVRQmZ2UzNPTmxLdnNKbmxIaGExZFRPSU91?= =?utf-8?B?WEZoWVg0V0RmeXpCalhHQ0RWamtpeWpOOFltZ1JFZjQ2MFNwUlhLMmwxTDRU?= =?utf-8?B?UzRNaGppNkEwT0UxWVBEU3paQXJIeFBkTnlMWkZNNVNoTGtLeHBNcUdZY1RQ?= =?utf-8?B?Vk44aUhDdU9XSFd1eDRjL2JTZTRmUlE2MVpXNG9pM2RHaWxVOVppQ1hPelBV?= =?utf-8?B?N01qOGhEa0ZOZThvT0IveGFUSzZabTlZT1RtSGZtNUt4eXE1cVUwU1RjK2Nr?= =?utf-8?B?Y3hJM3NYS3JaTHFIL3M0dW90emxzUXhUTjU1QmZBaUJ6c2pseFBtdDJrWGlF?= =?utf-8?B?cmprNm82RjkzQlFVbVQwOTVGU3MzaWFYQ1JVODFEQm1WTUEzM1RBbUVUanA4?= =?utf-8?B?VnQxakQweENTOWFJVDZkRmwvM0VaWlBPcW53MGxxTnlRaVBEbHhJSkZ3OWN2?= =?utf-8?B?ak9qSFp0cXVRL2dGbWY0K3FXVHhPS0gxTG5iS0tsaHV5d1RrVFNFQmZjQ1J1?= =?utf-8?B?SkVxMDk3TEFZZ1BHVHdQeHY0RHV6VFhVUWFxRTg4dHhOSlMwcGxRT2hyTXBQ?= =?utf-8?B?TmRlMWsxK1hFTmtoaktIdFlPaGY4QnVPZlBDWUdCWFd5eHlrcHZFWUZYcTVh?= =?utf-8?B?YXNNYWlvY0FGcVZWNXJaV0R4TXROMkVpdlB2WS9maytMY20rY0xEVHpNempr?= =?utf-8?B?U1JXczBOdVN6bitNTDJEME1INUgvQldmMjBDSlFlN2xsTFc2b2pJdlBURTk5?= =?utf-8?B?Z0M0alI3NDV4Y0FiZ1VRekFqd3NDQjFxTlg1QmRka0pPT01TWmFEN2VQelJV?= =?utf-8?B?NmZhdXhHdUxBNlljVmpaU3hpU3BqSG9PUlA4L0MwNytQZTYzZERPWjVKbXdn?= =?utf-8?B?blhuS2M2M0xFMks2UTE1QnNIUGdKeGhnUHhaNDFLMnZoQS9KeEJOempTN3Y0?= =?utf-8?B?UndCOXFDenhsdktYeFk5Mlo5Uk9zZ1BCa25tek03bk9pL0hkdWZNeWRNS2Q0?= =?utf-8?B?TDViMlBpcy9SM0NkdDI5S3N3d21LRC9VTmVMandjcTc1cG54dFhXNnpvdlhv?= =?utf-8?B?NExSMERhd3BDVEkxOEZjTFRlVmhyV09RbzgwNmlJNVNoMklFbGxsdlFYNTk0?= =?utf-8?B?QWVKZXNEWkdvaG5icUJlRjlkTERoWlhodFczSjFaUjB5TE1icmNrYXRtcTdt?= =?utf-8?B?KzB0NEhzMUJzMEk0S3NOUTJlN0owQWJRejV3aW83d0VDSHI3ODZ6cWowRUZs?= =?utf-8?B?N0o3OGVDZ0FLY3YzbytpWWZxaGdycXFsUkNoaHBPYTk5RlVqV0tKZ05hRVlw?= =?utf-8?B?TitpRUwxWXlKYXRFR2ZNS1FHdklaUTdRbU1RaDhrRTBXeGE2ZmRqQUdNUWh4?= =?utf-8?B?eUdYeHpuOFI5dTVja2RlMk5hZlhEN1FhNnVXU2I0aFV1RVQ4NitzY2dyc3By?= =?utf-8?B?WTJBVS91UlJnOUNHdEhPTW9QNWhCU0JGRGFWQlpoYUpDME1wUU1oT0RuRjBO?= =?utf-8?B?Sm9YL2lGZmdiQ3N0anRrb1JjMXpPWG5MVG54Y0tEQzFPTHhkdllLbXpiYm9v?= =?utf-8?B?cFBlalhpZmVVOUIwVXlUWllTeHNLaUFPNjNKQUd3bVdTK01PNVl2WmUzTWo1?= =?utf-8?B?bE55UGFyVExwdi9IbjJNa0d0cml3PT0=?=
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 93bf0495-3a5c-4e92-21a4-08d99fc9c4ff
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB5560.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Nov 2021 19:31:59.3662 (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: 2iI9EfmDJKTd/22V+lZlZt8XtYureEaZMoVO5AblrHFQy11GnlGEOopDryhsp9mIbksGYciVn6ccm2T/pqCG9pVbIblOyiNqhHwvGAtQzdM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR07MB6325
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/XW0ndjZtCDQsk1rSywJQSKZVo94>
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: Thu, 04 Nov 2021 19:32:16 -0000

Hi Toke,

thank you for your rapid feedback.
Please see in-line.

regards
-m

Le 2021-11-04 à 20:00, Toke Høiland-Jørgensen a écrit :
> Martin Vigoureux <martin.vigoureux@nokia.com> writes:
> 
>> Juliusz, WG,
>>
>> hello.
>>
>> Thank you for your work. I have reviewed that document and have only few
>> questions.
>>
>> -m
>>
>>      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.
>>
>>
>>      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?
> 
> One reason to do this could be to lower implementation complexity in an
> environment where you don't have a mature networking stack to deploy.
> If you route everything via v6 you don't have to implement ARP at all :)
humm, but that's not via v6 in this case because the interface is v4, or 
I'm missing something?

> 
>>      There are various ways to meet this requirement, and choosing between
>>      them is left to the implementation.  For example, if a router has an
>>      interface that has been assigned an IPv4 address, or if an IPv4
>>      address has been assigned to the router itself (to the "loopback
>>      interface"), then that IPv4 address may be "borrowed" to serve as the
>>      source of originated ICMPv4 packets.  If no IPv4 address is
>>      available, a router may choose a source address from a prefix known
>>      to be unused, for example from a suitably chosen private address
>>      range [RFC1918].  If no more suitable address is available, then a
>>      router MAY use the IPv4 dummy address 192.0.0.8 as the source address
>>      of the IMCPv4 packets that it sends.  Note however that using the
>>      same address on multiple routers may hamper debugging and fault
>>      isolation, e.g., when using the "traceroute" utility.
>> 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, 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. rfc1812 in fact seems to
>> forbid that (section 4.3.2.4), though I didn't check if this requirement
>> had been updated by other RFCs.
>> Anyway, could you elaborate on the above?
> 
> The idea is that we want there to be *some* ICMP errors going out, even
> if there is no v4 addresses configured anywhere. And using a private
> address or the dummy 192.0.0.8 (which comes from RFC7600, BTW), makes
> this possible. Many networks will happily route such packets; and, for
> instance, having traceroute return multiple hops with the dummy address
> is better than not having any replies at all.
Are you saying non private networks have routes for 192.0.0.8 or even 
rfc1918 addresses?
I indeed saw that 7600 was proposing the use of that dummy address as 
SA, but 1/ it's Experimental while this draft is in the Standard Track, 
2/ it didn't appear to me that it was for the same use.
It might be fine to send a Destination Unreachable with 192.0.0.8 as SA 
because it's a one way message, but it is not clear to me how 
ping/traceroute works when this address is used as SA in echo request, 
because a reply needs to get back to the sender.
Again, I may be misinterpreting your use case, but I'm wary about a 
draft saying that an implementation can choose whatever source address 
it wants for ICMP messages when rfc1812 clearly doesn't say so.

Not sure if it is relevant, but have you looked into rfc5837?

> 
> We recently fixed Linux to use this dummy address, BTW:
> 
> https://git.kernel.org/torvalds/c/321827477360
> 
> Prior to that change it would just cheerfully send out ICMP messages
> with a source address of 0.0.0.0, which obviously doesn't work at all.
> 
> -Toke
> 


From nobody Thu Nov  4 12:38:50 2021
Return-Path: <jch@irif.fr>
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 0FE523A1509; Thu,  4 Nov 2021 12:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 BQIvKsKW-_W5; Thu,  4 Nov 2021 12:38:46 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 AF3E53A1504; Thu,  4 Nov 2021 12:38:45 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 1A4JccC8017913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 4 Nov 2021 20:38:38 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/82085) with ESMTP id 1A4Jcc9c014264; Thu, 4 Nov 2021 20:38:38 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 76517E9AB0; Thu,  4 Nov 2021 20:38:38 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id wucg5y0skHrF; Thu,  4 Nov 2021 20:38:36 +0100 (CET)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id E2336E9AAE; Thu,  4 Nov 2021 20:38:36 +0100 (CET)
Date: Thu, 04 Nov 2021 20:38:36 +0100
Message-ID: <87h7crpv7n.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= <toke@toke.dk>, babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>
In-Reply-To: <6118de6b-2ae6-f690-7be6-7fe00984878f@nokia.com>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87v9173fvf.fsf@toke.dk> <6118de6b-2ae6-f690-7be6-7fe00984878f@nokia.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 04 Nov 2021 20:38:38 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 04 Nov 2021 20:38:38 +0100 (CET)
X-Miltered: at korolev with ID 618436BE.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 618436BE.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 618436BE.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@irif.fr>
X-j-chkmail-Enveloppe: 618436BE.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 618436BE.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 618436BE.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/NLTzZv6NDrNxgW-r6ese6iDDi3A>
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: Thu, 04 Nov 2021 19:38:48 -0000

> Not sure if it is relevant, but have you looked into rfc5837?

Yes, I was aware of this document.  Unfortunately, it only helps with
identifying the interface in the case where the router has an IPv4 address
(the "easy case" in my previous mail).  It's also not applicable to ICMP
MTU Exceeded (see Section 4).

-- Juliusz



From nobody Thu Nov  4 12:53:43 2021
Return-Path: <toke@toke.dk>
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 C59853A0061; Thu,  4 Nov 2021 12:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
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 qQgnHiubQFP0; Thu,  4 Nov 2021 12:53:36 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [IPv6:2a0c:4d80:42:2001::664]) (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 E460D3A005F; Thu,  4 Nov 2021 12:53:35 -0700 (PDT)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1636055612; bh=lp/N2+dKP9G5uLe/4GEviXS6gJYhnwmTFO2/GBNgIMs=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=VdR4zwYaKdlpJnpTozA02d/TGps2LCOeD7ZslW3nt2MzqSwdei3qYisjkp/iw60Ou HnLX4nXOboR6iyVxOlH7sIZNyFxUiQVReGfTi2oBU/ujokfxTe5ew0g9bnG2nzkZUz kDpaT86o3Jt57RDUO3ywVW+A1yVo++LEngIQQQMwPsJZM3o+Eqb0Yqrgfio6KDG5QT bSI1uDPTfky1bhTDrbGxFzs11Ht0pkNNruMycgGCb+MV4rSzVK+9cW8Lpshn71Mf2Y hvD6RzuOWIde0ox3cyIGzpRRVEBD87fVW+wTz3Bnr+O/07tZPNf0fZrb+sKfj6IwFn 8xm7BRp2FE/mA==
To: Juliusz Chroboczek <jch@irif.fr>, Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>
In-Reply-To: <87k0hnpw4z.wl-jch@irif.fr>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87k0hnpw4z.wl-jch@irif.fr>
Date: Thu, 04 Nov 2021 20:53:32 +0100
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87sfwb3dfn.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/sbaSh0HfEbYFh0tqWKSROPHWxoM>
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: Thu, 04 Nov 2021 19:53:42 -0000

Juliusz Chroboczek <jch@irif.fr> writes:

> 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?)

Does it need to include the MAY/SHOULD/MUST language? Otherwise, how
about simply:

"A Babel node can use a v4-via-v6 announcement to announce an IPv4 route
over an interface that has no assigned IPv4 address." ?

-Toke


From nobody Fri Nov  5 06:21:12 2021
Return-Path: <jch@irif.fr>
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 5C62E3A0A66 for <babel@ietfa.amsl.com>; Fri,  5 Nov 2021 06:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 GeptNdCmxW53 for <babel@ietfa.amsl.com>; Fri,  5 Nov 2021 06:21:07 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 7340D3A0A19 for <babel@ietf.org>; Fri,  5 Nov 2021 06:21:07 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 1A5DL0tE030510; Fri, 5 Nov 2021 14:21:00 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 690E5F6794; Fri,  5 Nov 2021 14:21:00 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 3hJOIt9qHwJ3; Fri,  5 Nov 2021 14:20:58 +0100 (CET)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id AE303F6792; Fri,  5 Nov 2021 14:20:58 +0100 (CET)
Date: Fri, 05 Nov 2021 14:20:58 +0100
Message-ID: <87pmreoi11.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= <toke@toke.dk>
Cc: Babel at IETF <babel@ietf.org>
In-Reply-To: <87sfwb3dfn.fsf@toke.dk>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87k0hnpw4z.wl-jch@irif.fr> <87sfwb3dfn.fsf@toke.dk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 05 Nov 2021 14:21:00 +0100 (CET)
X-Miltered: at korolev with ID 61852FBC.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 61852FBC.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 61852FBC.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/vQv1QS2cHesv-K4ow9s9l9ZfEGs>
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: Fri, 05 Nov 2021 13:21:10 -0000

> Does it need to include the MAY/SHOULD/MUST language? Otherwise, how
> about simply:
> 
> "A Babel node can use a v4-via-v6 announcement to announce an IPv4 route
> over an interface that has no assigned IPv4 address." ?

Right, thanks.

-- Juliusz


From nobody Fri Nov  5 06:33:30 2021
Return-Path: <jch@irif.fr>
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 7A29C3A0C95; Fri,  5 Nov 2021 06:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 w_TtkRBC5iEE; Fri,  5 Nov 2021 06:33:25 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 CA1253A0C9A; Fri,  5 Nov 2021 06:33:24 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 1A5DXLMH005274; Fri, 5 Nov 2021 14:33:21 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 5AF73F69C6; Fri,  5 Nov 2021 14:33:21 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id u0yI76P81G7z; Fri,  5 Nov 2021 14:33:19 +0100 (CET)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 2053BF69C3; Fri,  5 Nov 2021 14:33:19 +0100 (CET)
Date: Fri, 05 Nov 2021 14:33:19 +0100
Message-ID: <87o86yohgg.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: Babel at IETF <babel@ietf.org>, babel-chairs <babel-chairs@ietf.org>
In-Reply-To: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 05 Nov 2021 14:33:21 +0100 (CET)
X-Miltered: at korolev with ID 618532A1.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 618532A1.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 618532A1.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/w82qOeKoymoNiZkmP5FiLDZ73Kc>
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: Fri, 05 Nov 2021 13:33:30 -0000

I'm unfortunately unable to upload a new draft at this time.  The changes
are in the git repository.

>    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.

Replaced following Toke's suggestion:

  A Babel node can use a v4-via-v6 announcement to announce an IPv4 route
  over an interface that has no assigned IPv4 address.

>    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?

Not changed, for reasons explained in my previous mail.

> I think that it is not good practice to be using 1918 addresses beyond
> private networks, 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.

I've reworded this section to omit mention of 1918.  Donald, since you're
the body who initially suggested we use 1918, could you please check if
the new formulation is okay with you?

> s/RFC5549/RFC8950/

The extension was inspired by 5549, and I want to give full credit to the
original authors.  Please see paragraph (11) of

  https://datatracker.ietf.org/doc/draft-ietf-babel-v4viav6/shepherdwriteup/

> s/IMCPv4/ICMPv4/

Done, thanks.

-- Juliusz


From nobody Fri Nov  5 11:26:02 2021
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 89A1D3A138D; Fri,  5 Nov 2021 11:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.232
X-Spam-Level: 
X-Spam-Status: No, score=-5.232 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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 HqSW1qRxnRF8; Fri,  5 Nov 2021 11:25:57 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20097.outbound.protection.outlook.com [40.107.2.97]) (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 2B08C3A138E; Fri,  5 Nov 2021 11:25:57 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dfulL70UHLv2PPNw2GIgmV19TkeYK9zGgrB6Qrw65SvxawiNLKIW9eHZfa5NHFEaw0rZDF/BugAr6/DAfQ0JFZ7yB34REe2/SPcd306UJklDcy1Hud8aOU3me6A3+cs7YJz58QkNf6OV8RvkC0kJMB1neHXnmurkN1/TF9N6L+9wSsx///U1H5FuRGCZ1FLx+n5zED4oudgZiuWch5ot7tGulKwO8xksB09LkemDtcPT1XGwZts9zGZx7bshFJbsNWIldf7XNTepr5h0zZrACUUBhgNazkXxObPDV42zXUrg+ftF7JHWXTXzu221y/Xii1FIKVYaf2yKi+Az/fBuvQ==
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=rkgyQSKI7YWrZcd1LSSWYUF4PpmmgoJPDxJK+VOJJD0=; b=HBX/liNJw4gJvfW4MldC4/kEdu6JyClxsa3Jyv/ZHsIxgN+wBjT0zNM0uLgjGK2aWfMNuzgEoehBdpOZlfHuWX9ekB1Oir7Q1xpC5zJF0co8binicqKUKABxPZSOsu9Hui+Ip8r0hH1G4ZFVnJ3/GW6MDRSvBdqDBxp1fuduC7taSoMYfTirtPBrswNp0MTpeVXl6ab3rfYtblg6uKq6DG+T2YOf4c/qC6lqOO5+bBdTcOd7R8w9FOo8+AbFaj56C7JwQZetB4U6Y+8jJHSixAgpszyArBJ5cPRYguJxkCWOiemYpjGPduF815VPpom8ynCFdQ6SnNqSV02JrxXSNg==
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=rkgyQSKI7YWrZcd1LSSWYUF4PpmmgoJPDxJK+VOJJD0=; b=yK1VOUDBn8LRHV8es3n8O+utPn5rXlU1igG89TEgyN+LTsONVnWh4yeVObh+jZv5+y6ojHO13W8gzezYesfAPT0Itlnx8N1tiSKH3RAev6mH/OYrD09p/vpMaUyLClB5+VHJYpkM1B0AR1f9jDt/npF07jugZLECfxTMsHrijlc=
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 AM5PR0701MB2372.eurprd07.prod.outlook.com (2603:10a6:203:d::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4690.5; Fri, 5 Nov 2021 18:25:53 +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.4669.010; Fri, 5 Nov 2021 18:25:53 +0000
To: Juliusz Chroboczek <jch@irif.fr>
Cc: 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>
From: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <c1f90d9e-f0d8-2cb3-06b7-0c3b6b65bb6f@nokia.com>
Date: Fri, 5 Nov 2021 19:25:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
In-Reply-To: <87k0hnpw4z.wl-jch@irif.fr>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: CH0PR13CA0045.namprd13.prod.outlook.com (2603:10b6:610:b2::20) 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 CH0PR13CA0045.namprd13.prod.outlook.com (2603:10b6:610:b2::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4690.5 via Frontend Transport; Fri, 5 Nov 2021 18:25:50 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: d9a99830-1fe0-4faf-77f2-08d9a089b3c5
X-MS-TrafficTypeDiagnostic: AM5PR0701MB2372:
X-Microsoft-Antispam-PRVS: <AM5PR0701MB23723F38A87F83C50B011BC18C8E9@AM5PR0701MB2372.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: gJXJUvgX664d+xWlkg/2baoNMmiBDDHl9zJNQdX0iFZ2cJerp869F0zf0xkMhcXfeWz99OQCsbibTPYPy+/Ea/ZiJk0QRZKN0IvmhnxRl/8E+m2StUeZVvy0cUWkCXUKyBffkTxeHNsktk8yD4enQMJaYah6zE1RB8kTLP5plW3XYSUUCCzLV21zu1V+gb3wtGg3y+mKoMvzO/Xebq9tQNrElcy6aemUhfTrhDBlR8RUboYlSRXYzQKP4U8IkPIW7sRfChGBh0zDJfMx73k2EnYREw25Bf6ejC6T5Od+UBV16Aa6VU1bFJc9xY+HBdDG5WrVAe/orC6ATOl1iqby3zJzI1rwipU+QDwFijq9gjc7wRy1/W4lCjJKnGZ5GQUnL5qI3U4YBYcT9US9v1N2buwdn8n5BgC663jj4SFAZ7A6dkbwwFiEVNwvD//muor8BRb1r5iJjbBZGCoO1SW+cLHgAo7XgzmVew4Gm9FzLu159YGBwoy3wczxbksWxXl8DOhPPBR4qZt/MW0MpIWOzpJTGFtBPfaAtH2A+P6a4y3vnWUXWTZ/Zi8Ybd+2cFfJPtwFRI33Oa+EC/xnDNfRhCCazDqvHR8wn3CEmni4TgLxbV8dWO799M4fShIWl6IuPbC53MTsqyBTYwq+NyCzO/HfdjNB12rI3X86zvnSnziDPpNAkSi2ipniTo2LaNEsv+IYe+Pfyff/l7RtNpxduQuiSwg+VIeIjPEshIxeuyGSuf3mrGrAhJMnadRLcXhxWZru6KT207jVau1O/SAEyw==
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)(4326008)(66556008)(66476007)(5660300002)(66946007)(2906002)(86362001)(31686004)(66574015)(6916009)(6486002)(8936002)(508600001)(6666004)(16576012)(956004)(44832011)(2616005)(316002)(83380400001)(38350700002)(38100700002)(36756003)(186003)(82960400001)(26005)(31696002)(52116002)(54906003)(8676002)(45980500001)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?T2liRzh6UFQybFloalQ5MlZXd2c3eVk3ZGdtdnBoKzZIZllaV1NhTUlBdUc1?= =?utf-8?B?eE4ydXVmQjZsYytCdUVIMFZRaCtiR3hPVjdzWmtHa2JaMEZIbk5RazRlNHpp?= =?utf-8?B?VEZ0VTVzUnVhNU5oUzRzL2xua25jbGczc2loSG9PQXFnSW5IZXZrbExXWlpm?= =?utf-8?B?K3F4RFVZaGtDQ0k5TW1tWDV1dWJXaDdyN1RnTzN4NWpqY3d4S2JXSkx1VHRq?= =?utf-8?B?RURjUEV3OHhEZTFtY05rT0ZzcGpDSDkwRU9XVEROUFpScGJ3MnVYbkhtUVVU?= =?utf-8?B?bjF6dFlaaFIwSFdPR2E2QkVJcXErUy9IV29wbW1uNkJtN1JmR0xmUjhRMTBl?= =?utf-8?B?WWdzekZhenAwOFJiZDJJWndwS0pIdmVwK3VHZFg5VkVYcnl0UW9BOEw1WXNI?= =?utf-8?B?MXNxV3dIdGhkaWJGbVhvWkpqOXk4TWFFS2g4dEF1QW10NXB1R1FFd2MxRDNH?= =?utf-8?B?Qmp1c1B2cGJhM2cwTTBiRVVIekMwb3VjNG14V0J6TDhaQnlUVHErTnl1NzRD?= =?utf-8?B?K01xSVJPYkNLaEJCbTBZOFFZMGZ1SUhaYW92Rm9UQ1pVbEhHdktETkMxZ2pL?= =?utf-8?B?a1plKyt0ZThBc3pvUjZxa1hja011b2NsNlgrSkpibGgwS3pZMW93cjZ3QXVa?= =?utf-8?B?UHAydk81SnJpNEEvUVJ6UXVtTUY4N0x0UWRHYWt3SjRLNFduVHpEVFBvS2I4?= =?utf-8?B?Q2NEZXNGeW9xWFNBdllrblRvZVlTMWtWYklTSncwZ1V6NFV1emdJYm84d29a?= =?utf-8?B?aFlCY3N3ZVZJTmJIWm9oRFZRdXR1cDRCcmNOZG04R0JqRWJpc1loRXRHNDc0?= =?utf-8?B?RnNGL1FSSFM1UzN2SEFkUlFxdnNiK2NMUFZpTW42OXc3Zm9GQUZvQ0IzZUlu?= =?utf-8?B?Z0JQN0t5K0N4NWNnK3dFZmk5ZHJ0MHNkclJ5TnpqSmVrSEZyV0N2M0NqT0tE?= =?utf-8?B?dkM3U3dYeE0ycnhJTDB2a00wZFVRMWxJbzZDQXZ3djE4UTQvMFBveExZeTRv?= =?utf-8?B?akJQMVArcVhvUUNTTThLV3YzcnI4YitreCtYUzFadGRQNzdRaVJ1Q1ByL095?= =?utf-8?B?M0JhblR5SGVWVExlZmZPSEllOWlEQkxUNkJqSXNsZFlBV09qL3QyeEV1dkd1?= =?utf-8?B?dzFBaW10cjFpdExJR2lFZyt5M2paOEpjZmF2b1JPcDBBVlBVVEQzUXRBQWVj?= =?utf-8?B?M3F4bFZkS0ozSkVpYU5KYVR3cjhua0RocWRDTXErbnVZejJoS3h0QnZVcXky?= =?utf-8?B?elNqL243SW9PcTNXSkZoRVJZZGhtbUN3V3JVVm5HR0V3dGpnQlRQQU0vVmR2?= =?utf-8?B?Yi9LM1gzSExibG9IK1FaRnRuNTd5MkV5L0RvdVNKcEVFcEhrS2hUcHVVcWgx?= =?utf-8?B?dHhWZkVKSk1HOWVxaHhJaWFEcHcwK1ZJL1JNbWp6UEk0VUcrWFBXbXRGUjZ0?= =?utf-8?B?NGF5M2ltWmdCa0dMT2ZENmplRDI4eVhBdGlHN0h0RXE0UEhmN1IrZU5iVGgx?= =?utf-8?B?Rysrak9BMDk0bHlsRi9wOFVYSFBmNVJPUG10MFhEajhaY01PQkdNTCtBRzVt?= =?utf-8?B?amRUTDZDYXBuNjdWMzJLU0hyemFSYVRXWmhsSHVReCtOaTI1OU1LZEI4WG1v?= =?utf-8?B?dEVoUjBrSWFtOUwrWjZicWRIMGtubzAyTnZMd0lGZkxkNFNYOGppaVh5amZU?= =?utf-8?B?UGd1NEZtSmJ6cHhoR3drTWNoTmJFckJyWjVaWGNpNGI4eFBGVTNPTUtkaG1B?= =?utf-8?B?WEM4L2J6SU14Z241aitRTnlvMGtHeHBTWGdZeWZxWDc5dWRENzgyaTMrSDNL?= =?utf-8?B?a1ZROUFSU1ViTHFKc0ROcEZNY3ZBallZK1dMWVp0U3lUOFpwVkVJbnd0SmRP?= =?utf-8?B?R25zcVVHS2V2Tk1BTVZPZXRmY0dkTExBdnhPb2FMV0ttOE1xeTgxb3p2QU1W?= =?utf-8?B?Z29VeU92ck5DbkttbGl5dmd3OTNwZHo1MlEwa2pjbVFpalN3Q3Nza0FPUUxG?= =?utf-8?B?bVplTVhiQ0ppNW5MeWxrUzcwWEs4N2JtN1lkLzJwZmY5WUtGU0lNTDZCd0Z1?= =?utf-8?B?ZmNGUzY0R0lERGg4RnNLYWlmY1R2WklhQ0NYZlk3azBVZ0diUG12RmV6RFNw?= =?utf-8?B?RnY0VnZVRjBKSmZsRVNSK0NHZ3JHbk03bmhwRkp5K0FuU1hhZHU5Q083Vks1?= =?utf-8?B?V2xKbWwrYk1aczNjMjJ3Zm1PR0I1RjgySUJSUi8vRmU0T25SYm1WZVR3NHN3?= =?utf-8?B?emNTZEdwYXErSmZGZWFJY1FsUmZRPT0=?=
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d9a99830-1fe0-4faf-77f2-08d9a089b3c5
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB5560.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Nov 2021 18:25:53.8211 (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: NNmDMzGPwHiqrsOS/Wncay0Pn97uT1qMDKeNUlOSFIGYUuWk6isQ/+WOMz6Z5Mc/RKKnEhM176dSYrtSUIJRmZHaycJkO7M2kskxo94BVRA=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2372
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/U-e5Mq4j_F_peDeAzISKRFbzElw>
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: Fri, 05 Nov 2021 18:26:01 -0000

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.


>> 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).
- 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?


> 
> -- Juliusz
> 
> 
> 
> 


From nobody Fri Nov  5 21:23:06 2021
Return-Path: <d3e3e3@gmail.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 2C4183A123F; Fri,  5 Nov 2021 21:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 TBwY7k-joQlm; Fri,  5 Nov 2021 21:23:00 -0700 (PDT)
Received: from mail-il1-x12b.google.com (mail-il1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 130D53A123E; Fri,  5 Nov 2021 21:23:00 -0700 (PDT)
Received: by mail-il1-x12b.google.com with SMTP id i9so11462243ilu.8; Fri, 05 Nov 2021 21:23:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1ROO+781Jf0E27BFvvdiLfOmgmXzhIdZtPGfudmTCh4=; b=MgF+tKEG3Mw559fUQgbb9bwWat40LaqP8f5bHzlRQUmb/soFa9ZAjkX3TFQ4K2FkUC 9E8hcTFgHG5vUpUHArfwd74W2ye3iFNoVsF5sxveNyCq9YbCbshHBG1bBTpuH+XX+1Cv Kq1I7oJsK+yODESxzDqVMUa9DArwq1EMpNnTKsV28DWNnx9Xwlo2erjqc6VMWKMkFwtq 2AE3YNZRdd/LxVPdaUJlyZtKwRXBsTZW3nfK7Z0LH+rSoXsnjA1HBnRpJPCrb/v43buL BH9GeYT4gA8ChgYQpNwXci8tGwVJ/fSmW/YWk8590RJ0n50bF891XjPQaVW/auVpFgqI s3sQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1ROO+781Jf0E27BFvvdiLfOmgmXzhIdZtPGfudmTCh4=; b=2ak6RVmSbXoF0gsq/Ez6qh96MJVgKJOC/GENDIIqj2kz54JsWQxxkWrr1CbFBJ6/Gm Jbz25PdAv/vehFr83AoUgS0KQYaZhHcKls/mT8zsWORQAlsDrw44SYqOchBeIzFpKN3Z dT6T8jJyGEItDYzL4cJOjqWQJjR0Tq/UnHs0ANaSXAf0V0ejXwLhGQmcFOIQUPJejoLd rxUSFOxajkFU9QBx8algo+NsBZ8F8+IU3RaqEIwxNgEVbLDrgZwCrd9TKoGN7FKhq+4j awpPds0n2wIjgMeQ0LIlDJCF8q5xSsTfOFmW24J8vAKrF0HMRHa5U3TJGVIjOSnMhNXB 62VQ==
X-Gm-Message-State: AOAM53259upr41ioGG0ewkykrPClVE+pviWGDkdYIMRYyx0548fZGcqC L7XoutqMX6ObXYfyWfGZbCul8JHuX/XmCPWm0+w=
X-Google-Smtp-Source: ABdhPJyr+rW9Jcg0W/WSiv4Kcsk3gGyaHmZ2g2hx6quh1YzvvGzkKqvhtmrS3Pq31WxMlxc7yUHcsrNwxvETC80aITA=
X-Received: by 2002:a92:c263:: with SMTP id h3mr31031417ild.322.1636172577869;  Fri, 05 Nov 2021 21:22:57 -0700 (PDT)
MIME-Version: 1.0
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87k0hnpw4z.wl-jch@irif.fr> <c1f90d9e-f0d8-2cb3-06b7-0c3b6b65bb6f@nokia.com>
In-Reply-To: <c1f90d9e-f0d8-2cb3-06b7-0c3b6b65bb6f@nokia.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sat, 6 Nov 2021 00:22:46 -0400
Message-ID: <CAF4+nEE+x_nkeG_FMDrGHiaOfc9HwwryDie69ue=imgjov2Hhw@mail.gmail.com>
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, Babel at IETF <babel@ietf.org>, babel-chairs <babel-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004b95ad05d0171df1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/W96QQUNl2Hma72VEyKdvz_BsJps>
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 04:23:05 -0000

--0000000000004b95ad05d0171df1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

See below.

On Fri, Nov 5, 2021 at 2:26 PM Martin Vigoureux <martin.vigoureux@nokia.com=
>
wrote:
> Juliusz,
>
> thank you. Please see in-line.
>
> regards,
> martin
>
> Le 2021-11-04 =C3=A0 20:18, Juliusz Chroboczek a =C3=A9crit :
> > Thank for your review, Martin.
> >
> >>     A Babel node that needs to announce an IPv4 route over an interfac=
e
> >>     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, th=
e
> >>     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, th=
e
> >> 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 allo=
w
> > this case, such routers are being deployed, and the alternatives to thi=
s
> > 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 th=
e
> > 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 solution=
s
> > 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...

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-speci=
al-registry.xhtml
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.
      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.

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

> > -- Juliusz

--0000000000004b95ad05d0171df1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br><br>See below.<br><br>On Fri, Nov 5, 2021 at 2:26 P=
M Martin Vigoureux &lt;<a href=3D"mailto:martin.vigoureux@nokia.com">martin=
.vigoureux@nokia.com</a>&gt; wrote:<br>&gt; Juliusz,<br>&gt;<br>&gt; thank =
you. Please see in-line.<br>&gt;<br>&gt; regards,<br>&gt; martin<br>&gt;<br=
>&gt; Le 2021-11-04 =C3=A0 20:18, Juliusz Chroboczek a =C3=A9crit :<br>&gt;=
 &gt; Thank for your review, Martin.<br>&gt; &gt;<br>&gt; &gt;&gt; =C2=A0 =
=C2=A0 A Babel node that needs to announce an IPv4 route over an interface<=
br>&gt; &gt;&gt; =C2=A0 =C2=A0 that has no assigned IPv4 address MAY make a=
 v4-via-v6 announcement.<br>&gt; &gt;<br>&gt; &gt;&gt; If the Babel node ne=
eds to do so, what other option does it have? If none,<br>&gt; &gt;&gt; the=
n MAY may not be the right keyword.<br>&gt; &gt;<br>&gt; &gt; I think &quot=
;needs&quot; is the wrong word here.=C2=A0 What I meant to say is that<br>&=
gt; &gt; a node that would like to advertise a V4 route may choose to make<=
br>&gt; &gt; a v4-via-v6 announcement, but of course whether it actually do=
es is<br>&gt; &gt; a matter of local policy (subject to configuration).<br>=
&gt; &gt;<br>&gt; &gt; I&#39;ll try to find a better formulation. =C2=A0(An=
y suggestions?)<br>&gt; I like Toke&#39;s proposal from which I would in fa=
ct remove &quot;can&quot;.<br>&gt;<br>&gt; &gt;&gt; =C2=A0 =C2=A0 If the ou=
tgoing interface has been assigned an IPv4 address, then, in<br>&gt; &gt;&g=
t; =C2=A0 =C2=A0 the interest of maximising compatibility with existing rou=
ters, the<br>&gt; &gt;&gt; =C2=A0 =C2=A0 sender SHOULD prefer an ordinary I=
Pv4 announcement; even in that<br>&gt; &gt;&gt; =C2=A0 =C2=A0 case, however=
, it MAY send a v4-via-v6 announcement.<br>&gt; &gt;<br>&gt; &gt;&gt; I don=
&#39;t understand that part. Why do you allow a node with a v4 interface<br=
>&gt; &gt;&gt; to use a v4-via-v6 announcement of a v4 route?<br>&gt; &gt;<=
br>&gt; &gt; The v4-via-v6 next-hop is usually a link-local address, which =
is likely to<br>&gt; &gt; be more stable than a v4 address.=C2=A0 If it is =
known that all the routers in<br>&gt; &gt; the domain support the extension=
, then it may be better for the network to<br>&gt; &gt; make a v4-via-v6 an=
nouncement.<br>&gt; &gt;<br>&gt; &gt; At any rate, there&#39;s no good reas=
on to forbid this behaviour.<br>&gt; I&#39;m not asking for that. I&#39;d h=
owever suggest that you incorporate the<br>&gt; explanation you have given =
above, in the draft.<br>&gt;<br>&gt; &gt;&gt; I&#39;m not an ICMP expert, a=
nd I may not have understood what you are aiming<br>&gt; &gt;&gt; for here.=
 While the first proposal (using loopback) seems ok to me, the<br>&gt; &gt;=
&gt; other don&#39;t. I think that it is not good practice to be using 1918=
<br>&gt; &gt;&gt; addresses beyond private networks,<br>&gt; &gt;<br>&gt; &=
gt; This was discussed at the Babel meeting of 4 March 2021, and the<br>&gt=
; &gt; discussion continued on this very list throughout the month of March=
.=C2=A0 It<br>&gt; &gt; would have been appreciated if you had participated=
 in the discussion back<br>&gt; &gt; then, and I find it somewhat discourag=
ing that I need to summarise the<br>&gt; &gt; discussion before even reachi=
ng the IESG.<br>&gt; I understand. It&#39;s not always easy for an AD to mo=
nitor all the<br>&gt; discussions of all the WG he/she oversees, but you ar=
e right in the<br>&gt; sense that I should have done my homework better by =
going back into the<br>&gt; archives and meetings before sending my e-mail.=
 Point taken.<br>&gt;<br>&gt; &gt; I refer you to my slides of 4 March 2021=
, and the discussion on this list<br>&gt; &gt; starting on 14 March 2021 ti=
tled &quot;Dummy Source Address&quot;.<br>&gt; &gt;<br>&gt; &gt; The case o=
f a router that has a loopback address is pretty obvious, the<br>&gt; &gt; =
loopback address should be used as the source address of the ICMP packet.<b=
r>&gt; &gt; That case, however, is not very interesting -- if the router ha=
s<br>&gt; &gt; a loopback address, then it might as well use it as the next=
 hop.<br>&gt; &gt;<br>&gt; &gt; The problem we&#39;re trying to solve here =
is that of a router that has no<br>&gt; &gt; IPv4 address at all.=C2=A0 Whi=
le you might argue that RFC 1812 does not allow<br>&gt; &gt; this case, suc=
h routers are being deployed, and the alternatives to this<br>&gt; &gt; pro=
posal require either tunnelling (MAP-E) or address-translation (MAP-T,<br>&=
gt; &gt; NAT464, etc.), either of which breaks a number of desirable proper=
ties of<br>&gt; &gt; the Internet.<br>&gt; &gt;<br>&gt; &gt; The proper sol=
ution would be to avoid sending router-to-host ICMP packets,<br>&gt; &gt; a=
s described in my slides of 4 March 2021.=C2=A0 This is not a new observati=
on:<br>&gt; &gt; the whole point of ECN, for example, is to replace the unr=
eliable<br>&gt; &gt; router-to-host &quot;Source Quench&quot; signalling wi=
th reliable end-to-end<br>&gt; &gt; signalling.=C2=A0 Unfortunately, PMTUd =
is deployed in the wild, and we need to<br>&gt; &gt; do something about it.=
<br>&gt; &gt;<br>&gt; &gt; Hence, we need to send ICMP packets, and we need=
 something to put in the<br>&gt; &gt; source address.=C2=A0 The most robust=
 solution is to use a distinguished<br>&gt; &gt; address allocated to the l=
ocal network.=C2=A0 Failing that, you may either use<br>&gt; &gt; an RFC 19=
18 address, or the dummy address.=C2=A0 Nobody finds these solutions<br>&gt=
; &gt; attractive, but remember that the alternative is NAT464 or other pac=
ket<br>&gt; &gt; translation technologies.<br>&gt; It looks to me that the =
problem you&#39;re trying to solve is an ICMP<br>&gt; problem, not a Babel =
one, although it appears in the context of Babel.<br>&gt; If that is the ca=
se, then you shouldn&#39;t try to solve it as one section<br>&gt; in a Babe=
l document or at least you shouldn&#39;t say that an implementation<br>&gt;=
 can choose whatever source IP it wants.<br><br>I don&#39;t think the draft=
 says that a Babel router without any assigned IPv4 address can use whateve=
r source IPv4 address it wants. It suggests the following:<br><ol><li>Using=
 an IPv4 address that has been assigned to the router or some other interfa=
ce of the router.</li><li>Using &quot;a source address from a prefix known=
=C2=A0to be unused&quot;.=C2=A0 For example, if we are talking about a netw=
ork not having IPv4 connectivity to the Internet or only IPv4 connected to =
the Internet via NAT, the network manager=C2=A0may know of an unused local =
prefix, quite possibly an RFC 1918 prefix.</li><li>Using the IPv4 dummy add=
ress as source address.</li></ol><div>The idea on point 2 is that a receive=
r 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 add=
resses. Admittedly, if the routers are going to be individually configured =
with some IPv4 address known to be unused in an isolated or NAT bounded net=
work, this is not really different from case 1. So 2 only makes separate se=
nse if you have a scheme to just configure the prefix on your routers and t=
hen let them autogenerate an=C2=A0IPv4 address with that prefix...</div><di=
v><br></div><div>For point 3 see below.</div><div><br>&gt; &gt;&gt; and ove=
rall, I fail to understand how a response to the ICMP packet<br>&gt; &gt;&g=
t; could reach back the originator if it has used 1918/dummy as SA.<br>&gt;=
 &gt;<br>&gt; &gt; The dummy address is being used as the *source* address,=
 and hence doesn&#39;t<br>&gt; &gt; prevent routing of the packet.=C2=A0 So=
me over-zealous packet filters might<br>&gt; &gt; look at the source addres=
s, in which case you&#39;ll end up with an ICMP<br>&gt; &gt; blackhole -- b=
ut that&#39;s already something you need to deal with.<br>&gt; I understood=
 that, but I still have concerns<br>&gt; - rfc 7600 is Experimental while t=
his document is Standard Track so you<br>&gt; are taking a level up the pro=
cedures defined in 7600 (the use of the<br>&gt; Dummy Address for ICMP). A =
way around that may be to register your own<br>&gt; special purpose IPv4 ad=
dress, or be clearer that it&#39;s an Experimental<br>&gt; mechanism (thoug=
h I&#39;m less sure about that).</div><div><br></div><div>I do not think th=
e 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 tha=
t allocation that is temporary or tied to the protocol in RFC 7600. These q=
uestions are answered by the column entries for 192.0.0.8 in the IANA Regis=
try at</div><div><a href=3D"https://www.iana.org/assignments/iana-ipv4-spec=
ial-registry/iana-ipv4-special-registry.xhtml">https://www.iana.org/assignm=
ents/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml</a><br></d=
iv><div>As indicated by the &quot;Termination Date&quot; column, this is a =
permanent allocation of an IPv4 address. As indicated by the &quot;Reserved=
-by-Protocol&quot; column, this IPv4 address is not reserved for the RFC 76=
00 protocol. And perhaps most important, when 192.0.0.8 was assigned, it wa=
s given pretty much the most general name it could be given: &quot;IPv4 dum=
my address&quot;.</div><div>=C2=A0 =C2=A0 =C2=A0It might have been nice to =
assign a separate IPv4 unicast address as the &quot;Babel v4-via-v6 IPv4 du=
mmy address&quot; but isn&#39;t it obvious that would be=C2=A0a strict subs=
et of the 192.0.0.8 &quot;IPv4 dummy address&quot;? 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.</div><div><br></div><div>However, so=
mething like the following should be added to the draft&#39;s IANA Consider=
ation:<br></div><div>=C2=A0 =C2=A0 =C2=A0&quot;IANA is requested to add [th=
is document] as an additional reference for 192.0.0.8 in the IANA=C2=A0IPv4=
 Special-Purpose Address Registry.&quot;</div><div><br>&gt; - it&#39;s stil=
l not clear to me how ping or traceroute work with that<br>&gt; scheme. The=
se require a message to be sent back to the source. If a<br>&gt; Babel sour=
ce node used Dummy as SA, how can a message reach it in return?<br><br>OK, =
a node with no routable IPv4 address cannot successfully originate IPv4 pin=
gs or run IPv4 traceroute. But I&#39;m not sure why such a node would want =
to do that.</div><div>=C2=A0 =C2=A0 =C2=A0 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 IP=
v4 addresses. It will not be able to ping nodes that don&#39;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&#39;t have =
iPv4 addresses. But it seems to me that ping and traceroute will still be o=
f significant use.<br><br>Thanks,<br>Donald<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=C2=A0Donal=
d E. Eastlake 3rd =C2=A0 +1-508-333-2270 (cell)<br>=C2=A02386 Panoramic Cir=
cle, Apopka, FL 32703 USA<br>=C2=A0<a href=3D"mailto:d3e3e3@gmail.com">d3e3=
e3@gmail.com</a><br><br>&gt; &gt; -- Juliusz<br><br></div></div>

--0000000000004b95ad05d0171df1--


From nobody Sat Nov  6 15:05:02 2021
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, 6 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: =?utf-8?B?WEd4U3A3RjNRZjV1MWFYT2N5dHJIU1cvdlZTN1h4dXBKcW5lTHp0YmF3Z2l2?= =?utf-8?B?MHBPZHBONjJBakt6SCs0bWV4U01iY0RDZTBDRExMSGQrUzl5TVBZV3RBcGpk?= =?utf-8?B?WWlxaHdJaTlXTHFCNDZ1M0hNckNGRUhicHpnRW13VlVVSDlYVDZtOUhSNHhl?= =?utf-8?B?UHM1NWorQ0h2bGRoUnpBY2JoREhCbDJOQWRPRGtubWJGWEdPRHM0MDlxU3hC?= =?utf-8?B?SzQra2kwOHBUQjEraXFOVVVZQWNLUUtnZGxjUGtyYnVBSFFCV0RtN3BmMmJQ?= =?utf-8?B?S0JkRXRiTVAxaHdyWDN2a25CcDcvenhBWGxxWVNSK2tVZEpCcFZRRnNiRXh6?= =?utf-8?B?Z1FUMGhHRk9MU2NJYTJlMXZUdUZITUhIcFdpTmNxTE1yRkpsR3ptZXlGajBy?= =?utf-8?B?M2xuYzF2K2tpbTdCaWtBUG55eDByY0hTbytqb1cwQ2FpMVJhblZqQ1BScmxq?= =?utf-8?B?am43QVUwSWlCQXJ6WmRUL1hlRk9oU1kveThjUllWMG41SzYvTlhkbVVtejBR?= =?utf-8?B?NExHQ0Mwc1NFbXVLSHZTdHJvOW82U3FTVHppY1Z3T0piL2NIQ1lLM1FsSjY1?= =?utf-8?B?SG1nbmxrNktpSGZyT2FzQTlhaEN6YjVtd1U0bzJFY0JpLytydzNDWUwyZXN0?= =?utf-8?B?bWkzTDdxWkszcmtiSnNDOGwwSXJUVHE3MlQ2eXRCekM5ang2a2o4dzlqdkEv?= =?utf-8?B?MkVMUFJuQ3lVMlJucHBIZDZEbkl5VWdFQk5IRFBkWlBlUUtQU0k1OXJBK0Fo?= =?utf-8?B?Mi9hckp1UWFoam1NY0Zyc3hJQjV4blo1TzdHRThGRENrZmF2b3hCd0QwQzhE?= =?utf-8?B?YmJYbHhvOXYvbFIwNzRVamYrZlcwT3FrY2hSZmFQTHAyKzVOM0xQdHVBUmVE?= =?utf-8?B?S3lqenZCd0FZYkExd2hhckkveHNLL1dXQTY2N09GMWlWM29RWXpVRmkrMXI3?= =?utf-8?B?TTlGZnExeUZYMno0YUk4UnlHNDRiSDZBWk15MDljZXdtaW5BVEptU09nU0Nj?= =?utf-8?B?T21RWE53N3Bsb3kxSzVnRTZYNHkvNG16Z09uVEdabVE4dnR4TSsyMTFNMkZs?= =?utf-8?B?aFltWFdxeTZxWE45UnZwbitUSGYzVWhDcE05dlB5MjlSckIxMXlJNnFHK2FY?= =?utf-8?B?ZnRHeHdtQ2VsT2h1N1ZMY2ZDQ1NMTE05azV3aFJXWjF0K29qdWlFclh1QzRX?= =?utf-8?B?R2ppYUVzTHpmNWQzVjVieDZKRGJQSUdYTUxHWWVYSDYranUwWkVXdGtRZTQ1?= =?utf-8?B?TnVJYUgrMXF3L2VPVllwUTJBZjgxMkxRMWcyU3ZhL1VsaUVtQmdHM0p2T25a?= =?utf-8?B?ZmRicTZTaUZNK1hneHBxZmZhdGtydThpSC82clFKQTlOWWNmTDJFTFl2UHpx?= =?utf-8?B?NVJHU2NJbkpXYnF5MFZaSS81M2pOOFZjUXJIYlZJYVJ1dzViTHhYWXlEaVMw?= =?utf-8?B?dG9CU0l1QTdtMyticnUwYWo4cFlPQ0YxVUErM2FrSDAwd2orSnJuUWdTWUM1?= =?utf-8?B?ZVVJSko2VWlhK2ZRNmcralMraHFOMEs5SGxGdmFGRlRtVmo4eVZJcnl6U2l5?= =?utf-8?B?dkdKR0pRdmZDblZmeXNJYVptNm9pd3M0V0gyTEdxeGtzeG5qN0IzekRCUkV3?= =?utf-8?B?RW1SQm5PbmcxZEk2L242dGJ3QW56VG9FTHVnTWthTkxGNldDZnNwVGxEenpw?= =?utf-8?B?M3FVcHh3MlVOMHpKSUFiTHhadUZ4cVNIbE9iYWJRSFY0WUZxaGFjMk1RMXIy?= =?utf-8?B?T2F1YjFKU3VNN2gzUzRweGJLVG14dCt6UXpjWVViZHk3TTgxSHZIa09lYjZh?= =?utf-8?B?bzB3bUNhNkZtbVFoMUx5K1dTUkphN0l5QXRjMU1VY0cvNXpodFhDSlY0N1V3?= =?utf-8?B?NFc3dVhpeUpncnBoaG81ZlFTNTdOMmZDc1U2VlBEQ0laa0dYWnV6aVNqVVFQ?= =?utf-8?B?S0JaZ1VEQnVrNUZPL2V3RGtKQ2pZTDlOVkhHYWtIMXdqK2RYNURaNDk4QW4r?= =?utf-8?B?aFduS0RNd0NlYkVMTmNocG1rUU9jSnJ6YjgwNFdxbUNLV2RRbElscTQ5Z1dS?= =?utf-8?B?Vk04Tyt2cDY5VmpnV2JsQXdwK3J5OGdCMmdOR3RFV1IyV2ExRElOWnBvK1dJ?= =?utf-8?B?bTdwRTY1czMrVkZzVnlpeitFUGMrWldoOElPbVVRS25wT1NuckJFUHhqRXlI?= =?utf-8?B?UGpDeWZyS0ZTUmc1R29rUk12akk4bDhWTHUrWTdWQVRQdC9lS2dQTGhLaXRL?= =?utf-8?B?OWthT2drNmQzN2JTNi82S2JHSWlRPT0=?=
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
> 


From nobody Sun Nov  7 15:32:54 2021
Return-Path: <jch@irif.fr>
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 7C1A53A11AA; Sun,  7 Nov 2021 15:32:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 FIkj9TwY0rjZ; Sun,  7 Nov 2021 15:32:47 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 077AD3A1193; Sun,  7 Nov 2021 15:32:45 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 1A7NWcHI009123; Mon, 8 Nov 2021 00:32:38 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 25803B0D71; Mon,  8 Nov 2021 00:32:38 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id tjiQOwlEl0sS; Mon,  8 Nov 2021 00:32:36 +0100 (CET)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 4CC95B0D6F; Mon,  8 Nov 2021 00:32:36 +0100 (CET)
Date: Mon, 08 Nov 2021 00:32:36 +0100
Message-ID: <87r1brley3.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: Babel at IETF <babel@ietf.org>, babel-chairs <babel-chairs@ietf.org>
In-Reply-To: <c1f90d9e-f0d8-2cb3-06b7-0c3b6b65bb6f@nokia.com>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87k0hnpw4z.wl-jch@irif.fr> <c1f90d9e-f0d8-2cb3-06b7-0c3b6b65bb6f@nokia.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 08 Nov 2021 00:32:39 +0100 (CET)
X-Miltered: at korolev with ID 61886216.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 61886216.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 61886216.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/qILy-7TdiOtRLn6zFWZhUZ7lsF4>
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: Sun, 07 Nov 2021 23:32:53 -0000

> 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.

That's right.

> 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.

What do you suggest, then?

> >> 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,

That cannot work, as explained in my message of 14 April 2021:

    By the time the IPv4 module has decided it needs to send an ICMPv4 packet,
    it does not necessarily know whether the issue it's reporting is due to
    Babel or to some routing protocol.  In fact, there might not even be
    a well defined responsible protocol -- if a router running both Babel and
    BGP finds out that it has no route to a given destination, is the ICMPv4
    packet associated with Babel or BGP?

    Thus, any implementable procedure for sending ICMPv4 must be independent
    of any given routing protocol -- so it's not reasonable to have a Babel
    dummy address, distinct from a hypothetical BGP dummy address or an OSPF
    dummy address.  If we define a dummy address, that address must be common
    across all routing protocols.

> or be clearer that it's an Experimental mechanism

This draft was initially submitted as Experimental, but the WG group
insisted that I put it on the Standards Track, which I duly did in -02.
I still think it would be better to keep it Experimental, but I am merely
an empty vessel that carries the opinions of the WG.

> - 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?

As you rightly note, it cannot.  This is no different from an IPv6 router
that has only been assigned link-local or site-local addresses, it is able
to forward IPv6 packets but cannot originate either IPv6 or ICMPv6.

Martin, ICMP is a best-effort protocol: even in IPv4, the fact that
a packet from A to B is crossing a router R does not imply that R can
reach A.  Source Quench got this wrong, and was therefore replaced by ECN,
which piggybacks on end-to-end packets.  PMTUd got it wrong again, and
that's why it's so unreliable; but that's a design flaw in PMTUd, not an
issue that can possibly be fixed in ICMP.

-- Juliusz


From nobody Tue Nov  9 03:48:06 2021
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 4CFBC3A0F46; Tue,  9 Nov 2021 03:48:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.231
X-Spam-Level: 
X-Spam-Status: No, score=-5.231 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, RCVD_IN_MSPIKE_H2=-0.001, 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 XpV4FY2XdiO2; Tue,  9 Nov 2021 03:48:02 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60128.outbound.protection.outlook.com [40.107.6.128]) (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 CCDCD3A0FCA; Tue,  9 Nov 2021 03:47:57 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Qv4llE40I0mbV0Yclzs3NVhNWIDWLhx9DrrLFDtyqTQv8D2HqxpBY+rA9FcuLAjCMrszI4edjyu1SGZXpn/0MPdwnSr8DZSUCkm5A6BqFeJIitd1xvVmWtONYUeSJBrVB74zmx10F+AZojMJgUCfTu436Bl2x3sL2C4nd07cWIsqfvVWkuVmjq7GJYnVrgiv9fjsTcSBbERyGbBXW6MgUx6NxWDQSpQgHdtg+rEfZY8Gmw4TPLC8DjpTvl0A6oK43Px0cxUlOXW+usAxqkVt75xwQXaI7wnwbKGoVpJvk4IABII0JHl9DqOWXKa3whoTcaKLGzsXw38qAHXgBVv43Q==
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=+YhETMwIOZciF8w/6Ns9lf8bG9NBYF5rJ2xtXVZTJfU=; b=XIHAHE8fNn1alYAbXTx7hi0QzK+rXHldzl7qfFUWCcIqtqDX6dFp+BlWG0gxNlGRouSNa0gaFsY6S2mzPCHR3WsQW8+fN3X742MYB6APjXET8TqJ0JgzK9Y0GP26jZPlLOkNCbdg6cowUm3GoCmlhI6oGTgHR1bpmh+dI8yB9DiWuj3p8KXisBHSGdFLOU362ZwLjS87GsGSoFm+8qhchnJTjHAC0GdDHzaiCQPdS8ffg9n7T7yIL5MDPsr20bIAIAmAsVZ/7iOkzBE1tEf+/hHyapfZbhxLXG3VUOwQqr7xwnDnQQsaBlxUE6mv421CeOyUg+uLQG296hg4Z626vg==
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=+YhETMwIOZciF8w/6Ns9lf8bG9NBYF5rJ2xtXVZTJfU=; b=umxg5UphR+gQiBOTbD3JiiEwI8eJSi707pvD79vt62a+/nerf0uKPBZzLqPWFFXkqqEdi+6krlfjEADIjqdY7f6yaLn20v9dgZo+Q7lwpDVyqJ+nd/uc3O/XUv0gLltOp7K2AF8V14vP4kBzyF9qShM4mm0iC3As8JYiI9pnk7I=
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 AS8PR07MB7399.eurprd07.prod.outlook.com (2603:10a6:20b:2a3::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4690.8; Tue, 9 Nov 2021 11:47:50 +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.015; Tue, 9 Nov 2021 11:47:50 +0000
To: Juliusz Chroboczek <jch@irif.fr>
Cc: 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> <87r1brley3.wl-jch@irif.fr>
From: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <736a921a-4c60-d341-c569-6592467d01fc@nokia.com>
Date: Tue, 9 Nov 2021 12:47:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
In-Reply-To: <87r1brley3.wl-jch@irif.fr>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: CH2PR04CA0020.namprd04.prod.outlook.com (2603:10b6:610:52::30) 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 CH2PR04CA0020.namprd04.prod.outlook.com (2603:10b6:610:52::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4669.11 via Frontend Transport; Tue, 9 Nov 2021 11:47:48 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f4d3bd9f-49ce-40b6-a38d-08d9a376c1f1
X-MS-TrafficTypeDiagnostic: AS8PR07MB7399:
X-Microsoft-Antispam-PRVS: <AS8PR07MB739941EACBA1D54B4A6C1E1C8C929@AS8PR07MB7399.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: PR0m+SyR19whzRzJHIfp7tN7wu4Wy6lC1k2EZPqzn5YRQA4iU+3TkCuw/JZ24JhsUZ8V2Td+u+BelPf+kK3wtsZoGwgOm7sFmFWp4D9Ta60365dzNLy4JxMvV1cAppj1IhdF1LYdD8SIJmAbf5ZN0DdA9drGvmmjgq7ZyxPmnVcV9NEu2q6woXpTEYREfSCnxPNNBAVKUxsy850LIScalH8NO1u+Z1yaFWne6Qc8+XbcMjXA0Yuj+qszXe3ff3rjRE8ULEr7KXHHY6LypS1FuZPDu8+n/xgCc6f+Mqan6t4Vzi3OAHAxdROoN+PxnThOc+tf0LlHtBkK0gI9btEfgFANZk1A0szZknvsVclojJKcbA4bHHKS3jCKd8ygyePutNAGlOfDEGHq9CS+7L8cvflO0Qxt5Nk5p5N1ODY799jC3Li9K1dxShhKvZpy6rK4yECC7xe2GGDlGUiCxEQIgKAie6NtUUtB8Ha3RGnOLzGuE2/D3GFpE9mBYnbTNwBJielPDIKXixtJRGzXjauwX3JeEmdpTnPf+niZJjJBLmQhA65V0XQBv8hj71678gDxpO+2YqqRGaPQPOhlsVKBR3pDaVNRvvNNWWfkCsZAU/lRgcEn0YQjM0hYNVQONcfTraPI0AZR4O5o8Gat4Pp2sSXZqSefkdSsKn9iZu6bzntJPDoMViFiEJwNjRwuXbOJ1WjdR95BdrSTDV4hLkzvC3c/ODmT9hsgiBJtn9//w36b7EMi2WZjOj7AEByRv+BtjWgkodqbxM5HgRQTuqGgUqxQSpAp2ERooaYfbt1WNyoAlwSLYkBeq3V00caa7AQqgY2vRwGfWtd84MeR3jZ6BC79pkpv9if/tK38dGVQk9E=
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)(508600001)(38350700002)(5660300002)(38100700002)(83380400001)(52116002)(82960400001)(966005)(36756003)(6666004)(6916009)(2906002)(956004)(316002)(66476007)(54906003)(6486002)(66574015)(66946007)(86362001)(31686004)(4326008)(8936002)(44832011)(2616005)(186003)(26005)(8676002)(31696002)(66556008)(16576012)(45980500001)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?cWw5Y3FrUXlmWDZsOGJUanZLRUxTY3ptV284M1c0SW4rQTUrcnloSUkxdHov?= =?utf-8?B?eklsTkhwUGNnek9ZMWhvU2wyWVBTZUwzSFBTQ1ZIL2V0RERXazZPWUNkUTdi?= =?utf-8?B?NWtVTG9wbDhRUGpSdUc1VStQQWVBVUhnZlZ6WUJQSXgrVlFIN1RqcEVRK1NB?= =?utf-8?B?cHNVMy9mZFZqTjJKcEZDbmZUcWY4Wm5aa1FidGNWRTdMVG9BZ3FzMGxuZkZ0?= =?utf-8?B?c1gwVUkybDRmVENhRENNbGZIMzEyL044Rk96dk9wc1ZOLzluWTdqSi9zMS8v?= =?utf-8?B?VS9scTcyWVVnbXl6VWwwWVdOMU9raXpnTzM3Q2lMV2dJeGtBb1NxQlY0NGZw?= =?utf-8?B?VU5TVjRMTUJCTXd2Yy81S0lOM0tyYXJQN1l5N3ZyYUF2cHI1c2FTSEc5b2No?= =?utf-8?B?Q1lCcEhhR2tIUlpVSmJFd1lMZHJKWXRFaEFYSjlyaTVneHh2U0JTSi9WQ0c0?= =?utf-8?B?YmRLenJlWHc1Vm9lb0JmK3pPdHFIT3o4b3dVMHlOdWxrdWpFdlhxcFd6WFZF?= =?utf-8?B?b0V0Q2YrS3V6c2dmMjJGTTBtdk1xbk1wMDI4SzFwdDdFNU1ZU3NDMEUweWxE?= =?utf-8?B?UXdIZnBVb1IxTHlRcjVwY0RiMndlMEpZN0Y5a0o5QzkxSWNoSGF2dW5tQVVU?= =?utf-8?B?V0dKYk4xMDl4SHZSL1NtZWR4L2ZyWGw1Z3E2TE5xRHZobmorV0lVZWVrR3Uv?= =?utf-8?B?aE5HbUNjbHlVZytMbkh2NDBtZmZpSE9jZXo3TFlZejRaQXJRSEpnRE5jN0JF?= =?utf-8?B?UDBEYkRmZDNsRUVEbExuVnN1MFVaMElKd1lVNFZuWVhZdTFqYlRLa2dlMXBG?= =?utf-8?B?SXJTNGVFZUNRV1U5Z0hMSXNNSXhmdlRXNDVWTk4vMkVEdlcrc01vTzJJV1lL?= =?utf-8?B?TzZjM0hkNDlqZkxXVVJQa3FzdDhTSXZVWmFyZlhXMWdhYVV1UDlFTGJWTkdF?= =?utf-8?B?TmRQME9VQnRhY2ZXVkEwRi9ralZxNVhJMmFPS1FEeUlzaUwxVUduZGszTjhy?= =?utf-8?B?N1RJcXdGdjNoOVRIVUJEZWhIaCtrTGJoTkljQlZoMUhVS1o2c2xNclZVVklm?= =?utf-8?B?UGp2bnVWY0FIWUJNNXhxN2U2WGxMY0p1eWVkTi9hT3pvVENQbEV4RGhSQjRS?= =?utf-8?B?emU2QjdxQ2NnbEpMdFp4blM2VjNDdERSSlhQdWRlR2tBK1p1TjdMQlgyN3Vi?= =?utf-8?B?WGVEOE5EKy94VEJ3QTJ2a2kvZ2hEZFhQZTNvS0ZxcTBrTWdvTkkrR24vZ3VK?= =?utf-8?B?QUVDd0N2R0RJK0p5Ui9JaUNldkhCdTIxSlhmd2NaeVZvVTA5RVNmREg0UFFI?= =?utf-8?B?VzF0WmdqUmtQTGxSSUE2WVV4VVlFWENpcGFIOEw0cFZvc2wzZmNZZUN2YjZK?= =?utf-8?B?WXU1VkZBZ3dQbGtmMkN1SmpNRkRac09FYnBDeldocWJsOFdXWGI1ck1jK29Y?= =?utf-8?B?UTVLVU1SSE9GcnlUNFpWU1dzekQvOHpseGphSTRFSEl1Vm9reEdOYjhnZ0Jo?= =?utf-8?B?ZFlHLzR2bkl5R2h2d2JoYTZWMkhrNzJ1V041OHd0TjgwaCtGSzVwMUxqMUth?= =?utf-8?B?Q05TbGdreE1TaFE3WGJzRldQdWxubnlOTWcrSXBNZWFkUU9iQWU3YXRHalZY?= =?utf-8?B?aDVXaHVaSGJkVkFMdThuKzhVQW5DRnRrUjQ5aEhJK0tLY3RYME9oSkhkbXFJ?= =?utf-8?B?ZFZIUnVpSnlxNHQ4MUwwcGY0TEdTSkJGK1JCaWpRQUdDVHEvb2RWNzhQS0tt?= =?utf-8?B?aTRDS0xTa2Jram9PNUZjRW1hZUoyY0l0bmdjY3lXNysxa1NSU2RBaXR0WGhv?= =?utf-8?B?Q3BGU3hFdHQzZ1FiUGE3Z1lSR290aUUzZXY4azZxWHkxaGRRYXZ1andBL1ZQ?= =?utf-8?B?aU00MzgvM1FTenRBL0lJSU5XMHdvendUbUdUYWlzM1o4S1BjbmdBcnd2S2E4?= =?utf-8?B?UmJveElHSSttSTBjRTRXM0R0dFRIbWRERVZhMWFxem5qVERqRC9pa2hFdHZ4?= =?utf-8?B?dUtENEJRR2lHOTZZZHBsa1Z4NHdHYXhnVFZKMVNFc2daYyt6YUlYMFNXWEdy?= =?utf-8?B?WG45R0xwUGtZcHIvYTlrU1pUNXZPaStXekJmQ3VGSmYzNGIwUUU4MlJDb1Z1?= =?utf-8?B?eFZHZC90azhaZ1QxQU9VV2RaeC8zNlRTdFZhbjc2ZmZMTlZmSmNDRFdqY2Ir?= =?utf-8?B?OTViSVkza0J6V242QSsvZHpjVVZyTG5QalFubk50eGpwZTdXSDFiVlE0VWJk?= =?utf-8?B?Mi9jaEloY3o5bFVTVTAyZDNyV0N3PT0=?=
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f4d3bd9f-49ce-40b6-a38d-08d9a376c1f1
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB5560.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Nov 2021 11:47:50.6342 (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: 6SGl6YW89ROcN9hAX1ReIpkWyoFc/nrU0ANAePmd1uasHQCcSu7EzmTgZXGbLDIykC9xn1aU8vBJtL2u+q1lkJI58hAhzKupxz8ICyDZvK4=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS8PR07MB7399
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/fbgfFHGhTEY7v4FWPA081ODrS1U>
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: Tue, 09 Nov 2021 11:48:05 -0000

Juliusz,

thank you for your feedback. I have asked around and the Standard Track 
/ Experimental conflict I was perceiving may not be that bad/critical, 
though a bit of word-smithing may be needed to clarify the situation.
The objective of the below (which doesn't change much) is to keep the 
standard track status of this draft, to avoid this section turning into 
an ICMP specification, and to correctly reference what's being used to 
lift any ambiguity.

Let me know.

regards,
-m

OLD:
There are various ways to meet this requirement, and choosing between 
them is left to the implementation.  For example, if a router has an 
interface that has been assigned an IPv4 address, or if an IPv4 address 
has been assigned to the router itself (to the "loopback interface"), 
then that IPv4 address may be "borrowed" to serve as the source of 
originated ICMPv4 packets.  If no IPv4 address is available, a router 
may use some address from a prefix assigned to the local network that is 
known to not be used by any node in that network.  If no more suitable 
address is available, then a router MAY use the IPv4 dummy address 
192.0.0.8 as the source address of the ICMPv4 packets that it sends.
Note however that using the same address on multiple routers may hamper 
debugging and fault isolation, e.g., when using the "traceroute" utility.

NEW:
In such a situation, a router can use the IPv4 address which has been 
assigned to the router itself (i.e., the loopback interface), as the 
source address of the ICMPv4 packets that it sends. However, in the case 
where no such address exists, a Babel router, needing to send ICMPv4 
packets, could use the experimental mechanism described in <xref 
target="RFC7600"/> which uses the IPv4 dummy address (192.0.0.8) <ref to 
iana registry> as the source address of ICMPv4 packets. Note however 
that some ICMPv4 functionalities such a ping or trace-route are likely 
not to work or not to work as expected when using such mechanism.

and add two informative references:
rfc7600
https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml

Le 2021-11-08 à 0:32, Juliusz Chroboczek a écrit :
>> 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.
> 
> That's right.
> 
>> 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.
> 
> What do you suggest, then?
> 
>>>> 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,
> 
> That cannot work, as explained in my message of 14 April 2021:
> 
>      By the time the IPv4 module has decided it needs to send an ICMPv4 packet,
>      it does not necessarily know whether the issue it's reporting is due to
>      Babel or to some routing protocol.  In fact, there might not even be
>      a well defined responsible protocol -- if a router running both Babel and
>      BGP finds out that it has no route to a given destination, is the ICMPv4
>      packet associated with Babel or BGP?
> 
>      Thus, any implementable procedure for sending ICMPv4 must be independent
>      of any given routing protocol -- so it's not reasonable to have a Babel
>      dummy address, distinct from a hypothetical BGP dummy address or an OSPF
>      dummy address.  If we define a dummy address, that address must be common
>      across all routing protocols.
> 
>> or be clearer that it's an Experimental mechanism
> 
> This draft was initially submitted as Experimental, but the WG group
> insisted that I put it on the Standards Track, which I duly did in -02.
> I still think it would be better to keep it Experimental, but I am merely
> an empty vessel that carries the opinions of the WG.
> 
>> - 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?
> 
> As you rightly note, it cannot.  This is no different from an IPv6 router
> that has only been assigned link-local or site-local addresses, it is able
> to forward IPv6 packets but cannot originate either IPv6 or ICMPv6.
> 
> Martin, ICMP is a best-effort protocol: even in IPv4, the fact that
> a packet from A to B is crossing a router R does not imply that R can
> reach A.  Source Quench got this wrong, and was therefore replaced by ECN,
> which piggybacks on end-to-end packets.  PMTUd got it wrong again, and
> that's why it's so unreliable; but that's a design flaw in PMTUd, not an
> issue that can possibly be fixed in ICMP.
> 
> -- Juliusz
> 


From nobody Thu Nov 11 05:49:51 2021
Return-Path: <jch@irif.fr>
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 4A8873A1025; Thu, 11 Nov 2021 05:49:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 NVGiRBaQK1rV; Thu, 11 Nov 2021 05:49:47 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 D0A7A3A1024; Thu, 11 Nov 2021 05:49:46 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 1ABDngbY013238; Thu, 11 Nov 2021 14:49:42 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id C5A02147E0; Thu, 11 Nov 2021 14:49:42 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id qnX2VM3Y3w4U; Thu, 11 Nov 2021 14:49:41 +0100 (CET)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 063F3147DD; Thu, 11 Nov 2021 14:49:40 +0100 (CET)
Date: Thu, 11 Nov 2021 14:49:40 +0100
Message-ID: <87mtmapzt7.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: Babel at IETF <babel@ietf.org>, babel-chairs <babel-chairs@ietf.org>
In-Reply-To: <736a921a-4c60-d341-c569-6592467d01fc@nokia.com>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87k0hnpw4z.wl-jch@irif.fr> <c1f90d9e-f0d8-2cb3-06b7-0c3b6b65bb6f@nokia.com> <87r1brley3.wl-jch@irif.fr> <736a921a-4c60-d341-c569-6592467d01fc@nokia.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 11 Nov 2021 14:49:42 +0100 (CET)
X-Miltered: at korolev with ID 618D1F76.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 618D1F76.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 618D1F76.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/zJkBj7waQOiLBTmDQ3VFuTN7j1s>
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: Thu, 11 Nov 2021 13:49:50 -0000

> However, in the case where no such address exists, a Babel router,
> needing to send ICMPv4 packets, could use the experimental mechanism
> described in <xref target="RFC7600"/> which uses the IPv4 dummy address
> (192.0.0.8) <ref to iana registry> as the source address of ICMPv4
> packets.

Excellent idea.  I'll give the WG a few days to react, then implement your
suggestion.

Thanks,

-- Juliusz


From nobody Thu Nov 11 10:31:03 2021
Return-Path: <dschinazi.ietf@gmail.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 6E0FD3A0814; Thu, 11 Nov 2021 10:31:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 nKYsQM5l5-YI; Thu, 11 Nov 2021 10:30:56 -0800 (PST)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C08613A0817; Thu, 11 Nov 2021 10:30:56 -0800 (PST)
Received: by mail-pf1-x435.google.com with SMTP id c4so6343444pfj.2; Thu, 11 Nov 2021 10:30:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DmsMdHGZnpyegIKP8yYCMl0LdVdanY43MHQRfDMjzZQ=; b=KfYol8e+9khZvu8BO+IPswTO3VfKKr4aCdBz7EoxKSOp/7V4QIwM100f9G2cr6k8TC nEQeUPUX63a0H14g23/3pg589LjDOaDfe9AXCBxAXCA5FnM+nCHMkFvl9Gz/Adr5BYOI +wmtbqGqVSgn6MFlE7axXZ+ASOgqQ7ESvxWclzD4qq+TsmPjoWPxMWnlBt7StwwVANUl P0l1+J7cnLRygLOqsi1l7vmlrJTODbJxpse030/BCNGcOejZ2thfwsO5I8JqyLb7h2rB x3yh55KClsulTYSrIO9KnZIcH3HKaQMhUpEoFRehKZjPB9u4evcknvj55n8MX6MwluSu vZaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DmsMdHGZnpyegIKP8yYCMl0LdVdanY43MHQRfDMjzZQ=; b=w/YRoaoXpdVIV++R6d5DJaY1sxaoZo4fPb/EtfMgfvb83ii0C4Sax+opy/sXXxmT/M 6RQtCX7c8WhblPbyCzu6cg0c7/JI3aj+9hl5h6k5RAemy/sYL0PUfeAn3AvKj2P2uV72 HD1RyNl0yjlivT9jtd20DPHfA69NlNhP0fjZGC6cYpJbmS/Uuq92Qnb1G3/WUYNNOuG0 No6+Ck/+F2SKL/6d6AD6lPw91PJtXYQRJhGr/6rGkI3wVhuCylB2B/jmNw9r4XG2NkmD MZ0z5OoL0pHz/7+UDRBpvSoH8oPlDiCPz197vZqDWDS3ZjcBGOzAD4wg5hgDtU/I3ZU5 ffJw==
X-Gm-Message-State: AOAM531et5tinl1RbE9SpFLv5KSP2IhPi5ja3Szb1j35GHUScIP957u2 GAeY/D9s7Qd6RG/masomFMnxuh1FyqY0zsYg4q1R2Jwg
X-Google-Smtp-Source: ABdhPJwq+MnOHZxeM5J6T9WK3Zi1iYARzczBshptsd83iOKr4mXaKHHPYXqUr49QzOQ1FvbEOx00Ns+3r1+nNAs2Ecw=
X-Received: by 2002:aa7:99cf:0:b0:49f:9d3c:ac0f with SMTP id v15-20020aa799cf000000b0049f9d3cac0fmr8410509pfi.39.1636655455537; Thu, 11 Nov 2021 10:30:55 -0800 (PST)
MIME-Version: 1.0
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87k0hnpw4z.wl-jch@irif.fr> <c1f90d9e-f0d8-2cb3-06b7-0c3b6b65bb6f@nokia.com> <87r1brley3.wl-jch@irif.fr> <736a921a-4c60-d341-c569-6592467d01fc@nokia.com> <87mtmapzt7.wl-jch@irif.fr>
In-Reply-To: <87mtmapzt7.wl-jch@irif.fr>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 11 Nov 2021 10:30:44 -0800
Message-ID: <CAPDSy+4_zbHK2sr=ihsvXe4SyMt789mLw1PSkg+=NrcHW0kX5Q@mail.gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Martin Vigoureux <martin.vigoureux@nokia.com>, babel-chairs <babel-chairs@ietf.org>, Babel at IETF <babel@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000c0dd005d0878bc4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/QupZTUlWUzUjQb3x4AheuTSbsKs>
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: Thu, 11 Nov 2021 18:31:02 -0000

--0000000000000c0dd005d0878bc4
Content-Type: text/plain; charset="UTF-8"

This suggestion sounds good to me.

David

On Thu, Nov 11, 2021 at 5:49 AM Juliusz Chroboczek <jch@irif.fr> wrote:

> > However, in the case where no such address exists, a Babel router,
> > needing to send ICMPv4 packets, could use the experimental mechanism
> > described in <xref target="RFC7600"/> which uses the IPv4 dummy address
> > (192.0.0.8) <ref to iana registry> as the source address of ICMPv4
> > packets.
>
> Excellent idea.  I'll give the WG a few days to react, then implement your
> suggestion.
>
> Thanks,
>
> -- Juliusz
>
> _______________________________________________
> babel mailing list
> babel@ietf.org
> https://www.ietf.org/mailman/listinfo/babel
>

--0000000000000c0dd005d0878bc4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This suggestion sounds good to me.<div><br></div><div>Davi=
d</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Thu, Nov 11, 2021 at 5:49 AM Juliusz Chroboczek &lt;<a href=3D"ma=
ilto:jch@irif.fr">jch@irif.fr</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">&gt; However, in the case where no such addres=
s exists, a Babel router,<br>
&gt; needing to send ICMPv4 packets, could use the experimental mechanism<b=
r>
&gt; described in &lt;xref target=3D&quot;RFC7600&quot;/&gt; which uses the=
 IPv4 dummy address<br>
&gt; (192.0.0.8) &lt;ref to iana registry&gt; as the source address of ICMP=
v4<br>
&gt; packets.<br>
<br>
Excellent idea.=C2=A0 I&#39;ll give the WG a few days to react, then implem=
ent your<br>
suggestion.<br>
<br>
Thanks,<br>
<br>
-- Juliusz<br>
<br>
_______________________________________________<br>
babel mailing list<br>
<a href=3D"mailto:babel@ietf.org" target=3D"_blank">babel@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/babel" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/babel</a><br>
</blockquote></div>

--0000000000000c0dd005d0878bc4--


From nobody Fri Nov 12 02:40:46 2021
Return-Path: <toke@toke.dk>
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 71AEC3A0CC5; Fri, 12 Nov 2021 02:40:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
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 HJqSfiDzSllV; Fri, 12 Nov 2021 02:40:40 -0800 (PST)
Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (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 EC4D53A0CCB; Fri, 12 Nov 2021 02:40:24 -0800 (PST)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1636713611; bh=0eSTfCfDzCKpielaDj2VmGRpZB6brVbXVWscDEYiHDw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=DJuAXKTdTCIrJ9UwX2W/vrmyOp5+yd2jOa5jMog8DWOZytMqvvap0cCMyajQmEnoY wqD7/mZHuVpnBNzUYZHhDqVaAsX+jaABU+p810SsfwXctBmZs5lAUq9hGhwBNcIIhr AxALUwHf3lwowmzLAjxSuKfq/OuNOD8kaj2gFysEACfQQ0UWFRg7mYK6zfSddXTsxo 5yTLP3rn9WdXT4FWyYDVXM9nNHkNPl0O07yQVbqYGX58JpnSRFgl1WsLOJhf3PvckI A17A9FpE06Tb4V5XVU5HrzrH16VgFMSwpHd3SKsGqs09v5fkQZKSCw++PTDp1IevmV XmJl8LT/HyH/g==
To: David Schinazi <dschinazi.ietf@gmail.com>, Juliusz Chroboczek <jch@irif.fr>
Cc: babel-chairs <babel-chairs@ietf.org>, Martin Vigoureux <martin.vigoureux@nokia.com>, Babel at IETF <babel@ietf.org>
In-Reply-To: <CAPDSy+4_zbHK2sr=ihsvXe4SyMt789mLw1PSkg+=NrcHW0kX5Q@mail.gmail.com>
References: <22bde274-9914-8cfd-a61d-be8832c84706@nokia.com> <87k0hnpw4z.wl-jch@irif.fr> <c1f90d9e-f0d8-2cb3-06b7-0c3b6b65bb6f@nokia.com> <87r1brley3.wl-jch@irif.fr> <736a921a-4c60-d341-c569-6592467d01fc@nokia.com> <87mtmapzt7.wl-jch@irif.fr> <CAPDSy+4_zbHK2sr=ihsvXe4SyMt789mLw1PSkg+=NrcHW0kX5Q@mail.gmail.com>
Date: Fri, 12 Nov 2021 11:40:10 +0100
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <877dddpshh.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/t5X4RfwL6sLgVlzjhnfWKalctn8>
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: Fri, 12 Nov 2021 10:40:46 -0000

David Schinazi <dschinazi.ietf@gmail.com> writes:

> This suggestion sounds good to me.

+1

-Toke

