[Idr] MP-BGP Extension and the Procedures for IPv4/IPv6 Mapping Advertisement

Acee Lindem <acee.ietf@gmail.com> Mon, 18 March 2024 14:05 UTC

Return-Path: <acee.ietf@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 053C7C151989 for <idr@ietfa.amsl.com>; Mon, 18 Mar 2024 07:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NV2FlkQ9IiZk for <idr@ietfa.amsl.com>; Mon, 18 Mar 2024 07:05:15 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F511C151710 for <idr@ietf.org>; Mon, 18 Mar 2024 07:05:15 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id af79cd13be357-788598094c4so226589085a.0 for <idr@ietf.org>; Mon, 18 Mar 2024 07:05:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710770713; x=1711375513; darn=ietf.org; h=to:date:message-id:subject:mime-version:from:from:to:cc:subject :date:message-id:reply-to; bh=mxdrZH1osE713YIPi1CAfdjigNSuAHomJnDoDC6AC+A=; b=IAhIcwl24tJOM4HYcyKXH+kV/E6mOcOKUFlkpZDvw5Pw6eReP/su67qz4QhLzq85GV HsnEXR1NumrNLw4Di/ZgeIhIVeWa3N38ZV7DqqcC8HetkZYDiGboNGjee4vS+1KDa9wW F7csuSwkifVo1sCP85nNRxyGOCXP3rMejb5pXdydkngzOIEl0uPBCSpCSlgevI0C+Ijn Zaey6s5HxE+pA2DO6dRuSLn9h+/hX9chaL6BYK751LpvLQqOOMjqs7Q5BlOV3K+D8bBZ rGG8Lku8/G24s3B/3Zut6UHAc2rTgs/PfJMzvkDPFUw2jaCdiPtqpaNHn2vdLePU6gWx 3a9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710770713; x=1711375513; h=to:date:message-id:subject:mime-version:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=mxdrZH1osE713YIPi1CAfdjigNSuAHomJnDoDC6AC+A=; b=MjW8XOQgAMB7EY7XxxsesSTHiPdkUiZiD8LfhgeFaWSpkh5+2tMLhSwlPqw16LlUvO YiDh1AE6oqJ18aTKmzyPBHs+vZZeEy9beOkzK257iA+CYMIwEwcYzpmmVz89y9Cw8s58 JX0g6krF79AHQgR1n8utzk4Iu/4ZsPTNH2dLEgcY7rNVt2gFA6ad/wmAPWRPmeMVzIaE 1bhBX3GrnHtskDxPSAFOxaUPsET2JlLPrcMofnJeaIUGW7k3jmZtnEkZ7qsSPug19Biv +BR3Mja4agAtl+dv9rRAN8qAtVBctYcCzSBDQZU8QrB1k4xtbVhIjpdLJ5+uhKDBPoKo P1ew==
X-Gm-Message-State: AOJu0YyCsH4QrMLtxoFlbYduaV5EbfPXPtCiYB4XnJ9pqT91IllbZUR2 3OPRgJ8oOiouZqHr5lWZHTQszZfLLiBwvJnTlhxAhwhk9mONorEX2ar4A0um
X-Google-Smtp-Source: AGHT+IHChdO0fozItC1xkCSjit6c6uI1gkY3vUzRvLdOveV44B8Y/i2FMZrv0/fgVJb3WQCAtYlo1w==
X-Received: by 2002:a05:620a:5cca:b0:789:ebd1:445a with SMTP id xr10-20020a05620a5cca00b00789ebd1445amr7279821qkn.42.1710770713598; Mon, 18 Mar 2024 07:05:13 -0700 (PDT)
Received: from smtpclient.apple ([2605:a601:9186:ba00:a565:43eb:999a:3ece]) by smtp.gmail.com with ESMTPSA id u2-20020a05620a120200b00789e2961225sm3517694qkj.61.2024.03.18.07.05.13 for <idr@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Mar 2024 07:05:13 -0700 (PDT)
From: Acee Lindem <acee.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8316075D-F44A-47AD-A5DB-298BE15E58C5"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Message-Id: <A60F08E3-16BC-4E55-90E0-3039F8FA044F@gmail.com>
Date: Mon, 18 Mar 2024 10:05:03 -0400
To: idr <idr@ietf.org>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/jgEpwvL5ghrfIUnN1y17Q3i6r7U>
Subject: [Idr] MP-BGP Extension and the Procedures for IPv4/IPv6 Mapping Advertisement
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2024 14:05:19 -0000

Apologies if this has already been covered but it was clear from yesterday’s IDR meeting chat  that I’m not the only one who questions the necessity of this BGP extension.  

Why can you just use one of the IPv6 addresses ranges reserved for embedded IPv4 addresses as described in section 2.2.5 of RFC 4291? 

https://datatracker.ietf.org/doc/html/rfc4291#section-2.5.5

If you use these embedded IPv4 using the standard mappings there no reason to advertise explicit mappings. There is already precedence for doing this - https://datatracker.ietf.org/doc/rfc6992/


Thanks,
Acee