Re: [Sidrops] Which 8210-bis error code should be used?

Claudio Jeker <cjeker@diehard.n-r-g.com> Thu, 18 May 2023 08:45 UTC

Return-Path: <cjeker@diehard.n-r-g.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26624C13AE21 for <sidrops@ietfa.amsl.com>; Thu, 18 May 2023 01:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.193
X-Spam-Level:
X-Spam-Status: No, score=-4.193 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 itN1PSbS-_JY for <sidrops@ietfa.amsl.com>; Thu, 18 May 2023 01:45:48 -0700 (PDT)
Received: from diehard.n-r-g.com (diehard.n-r-g.com [62.48.3.9]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA512) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7F62C13AE25 for <sidrops@ietf.org>; Thu, 18 May 2023 01:45:46 -0700 (PDT)
Received: (qmail 49307 invoked by uid 1000); 18 May 2023 08:45:43 -0000
Date: Thu, 18 May 2023 10:45:43 +0200
From: Claudio Jeker <cjeker@diehard.n-r-g.com>
To: Randy Bush <randy@psg.com>
Cc: "Borchert, Oliver (Fed)" <oliver.borchert=40nist.gov@dmarc.ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>, "Borchert, Oliver (Fed)" <oliver.borchert@nist.gov>
Message-ID: <ZGXltyD1HgpLboPF@diehard.n-r-g.com>
References: <BLAPR09MB632225B977B3138A7E05793E98789@BLAPR09MB6322.namprd09.prod.outlook.com> <m28rdms05t.wl-randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <m28rdms05t.wl-randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/BZYxOcFNLDQYVNxGpFXlMA7r7a0>
Subject: Re: [Sidrops] Which 8210-bis error code should be used?
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 May 2023 08:45:50 -0000

On Wed, May 17, 2023 at 10:01:34PM -0700, Randy Bush wrote:
> > When processing the ASPA PDU of
> > https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-8210bis-10,
> > the profile draft
> > https://www.ietf.org/archive/id/draft-ietf-sidrops-aspa-profile-13.txt
> > and in particular Appendix A mentions that: “Note that two PDUs are
> > always generated per Customer ASID: one with AFI Flags = IPv4 and one
> > with AFI Flags = IPv6.”. This requires when using 8210bis to propagate
> > the data to the router (client) that 2 separate PDU’s need to be
> > generated because a single ASPA PDU only contains provider information
> > for a single AFI.
> > 
> > Question:
> > =========
> > What error code should I use when the router only receives in total
> > one of them?
> 
> 42 - bad internet-draft

Glad that you agree that draft-ietf-sidrops-8210bis is bad.

-- 
:wq Claudio