Re: [Sidrops] WGLC = draft-ietf-sidrops-aspa-verification - ENDS 03/22/2023 (Mar 22 2023)

Job Snijders <job@fastly.com> Fri, 28 April 2023 12:11 UTC

Return-Path: <job@fastly.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 2B0DEC151B39 for <sidrops@ietfa.amsl.com>; Fri, 28 Apr 2023 05:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_NONE=-0.0001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.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 GLlTnN-FODha for <sidrops@ietfa.amsl.com>; Fri, 28 Apr 2023 05:11:27 -0700 (PDT)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (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 39E92C151544 for <sidrops@ietf.org>; Fri, 28 Apr 2023 05:11:19 -0700 (PDT)
Received: by mail-wr1-x430.google.com with SMTP id ffacd0b85a97d-3003b97fa12so6046661f8f.2 for <sidrops@ietf.org>; Fri, 28 Apr 2023 05:11:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; t=1682683877; x=1685275877; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=UYLIEktYiqsp0SXtEecoAktKMZD54HmKRUo701xouks=; b=i32/ur7O3BgrHLtBdlkXGEWR6a6N2W0rynMA/LZKI3r3dxkB/Iwn0cccRl5GMhqzfJ E6Iw27l9DLUAVcb0nT9AD+LUx0ZwTsmZkVMW+5EJZ6nv0cFw/+rrbP//DCrKpRCTLkS2 vTObWGM1Oz6J8094eGPGOEx7hV5kLCWXGwCXg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682683877; x=1685275877; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=UYLIEktYiqsp0SXtEecoAktKMZD54HmKRUo701xouks=; b=UjgjpcQspn5KswjM1+9syjF+b9wBk1SMYpo/68x3rsPAdWeb+dvAt5ybpmyDaQB5AD Xu2y4nN/0NGxAniLqKi9+ReqXjype9ELZIHmVtoXrr66VOnXKcM4AgJ8nZlgY5g229dE 2N18LhSrWz1f1txsKKvX79PM7dZ4pyss5Aao6Z+LDVsATc0MpmRKZ6WeeIgZlMibV6Rm Djp2QNu3HHBNqVsKMz1c88MogSFyC/qkVE1OPAlhMIWbw1oMFR5icNkysq52lokGnFzP 4Nkc8CFvMsamqKS+FUFB+6Qlj2dM37I0iYMr/fMsrAAbNMFpVqjYWDL4MdIAsLi4aOHb gTUg==
X-Gm-Message-State: AC+VfDynt9MhevmrNaNV2PIlsjRTUeYp5E72nQEDmuE+BrWvtBFcryym Pald3pCxgIlCUBOlX28yI6ozpTCssn724++AOHfMyhKe5oR5I7dJg/aEnJszlYMi+j7d8kTe5w6 EyoIvASNuYs4B3ZrQaCzuVh+cgtdoH5PbxOUb8NtYMaNNpGhGJnzs7xOsX17cLOuT6w==
X-Google-Smtp-Source: ACHHUZ5sTNKoA3JwJ6ifDf1XcFLra/E9kBdufzWLIVTpQJsXrbkFONWjOUoQacEaNegevHu0JCygjA==
X-Received: by 2002:a5d:4902:0:b0:2fe:fde1:23a2 with SMTP id x2-20020a5d4902000000b002fefde123a2mr3676602wrq.50.1682683876697; Fri, 28 Apr 2023 05:11:16 -0700 (PDT)
Received: from feather.sobornost.net ([41.251.6.221]) by smtp.gmail.com with ESMTPSA id p8-20020a05600c358800b003f1738d0d13sm37294828wmq.1.2023.04.28.05.11.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 28 Apr 2023 05:11:15 -0700 (PDT)
Date: Fri, 28 Apr 2023 12:11:08 +0000
From: Job Snijders <job@fastly.com>
To: sidrops@ietf.org
Message-ID: <ZEu33CnI-qObXObh@feather.sobornost.net>
References: <ZCGcYHJ9PyrjgR+V@diehard.n-r-g.com> <SA1PR09MB8142EA7F33880679E9B509D384889@SA1PR09MB8142.namprd09.prod.outlook.com> <SA1PR09MB81426E1BB66D6DF31860F26984889@SA1PR09MB8142.namprd09.prod.outlook.com> <ed0146b09da346b2b48cb9701240926c@akamai.com> <SA1PR09MB81427D28EF661F9DAB05FB9B84889@SA1PR09MB8142.namprd09.prod.outlook.com> <c62da49ce2a142999260371a0af7b673@akamai.com> <SA1PR09MB81428936A8B2BC30C04C4B2684629@SA1PR09MB8142.namprd09.prod.outlook.com> <20230420115248.16ded6f2@glaurung.nlnetlabs.nl> <ZEq3xJVjT11fcImG@feather.sobornost.net> <20230428095607.66d80e07@glaurung.nlnetlabs.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20230428095607.66d80e07@glaurung.nlnetlabs.nl>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/eSlwUawJd0JHq_ZersdWrSX3q9c>
Subject: Re: [Sidrops] WGLC = draft-ietf-sidrops-aspa-verification - ENDS 03/22/2023 (Mar 22 2023)
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: Fri, 28 Apr 2023 12:11:33 -0000

On Fri, Apr 28, 2023 at 09:56:07AM +0200, Martin Hoffmann wrote:
> > I've added an Appendix to the aspa-profile internet-draft showcasing
> > various eContent payloads and how they transform into RTR PDUs.
> > 
> > I also explicitly noted that a single eContent payload always
> > results in two RTR PDUs, and how multiple eContents payloads for the
> > same Customer ASID also result in exactly two RTR ASPA PDUs.
> 
> That is very helpful, indeed. Thanks!
> 
> Do you think it might be possible to somehow also show the decoded
> ASPA eContent content in the first column to make it easier to spot
> what is going one? I suspect that when an implementation converts from
> object payload to RTR payload, they longs since moved past the encoded
> formats.

I couldn't make that fit well enough with the way xml2rfc generates
tables. I was also concerned about loss of information if these
encodings are expressed in high level language. Of course a canonical
way of representing DER in human-readable format would be XER, but
that's very verbose. By providing the DER-encoded payload, my hope is
that potential for ambiguity is removed.

If people need help encoding/decoding ASN.1/DER/HEX/PEM always feel free
to ping me offlist.

Kind regards,

Job

ps. For the benefit of the group, the Base64-encoded blobs can be
decoded using openssl's asn1parse. First find the offset of the ASPA:

    $ cat << EOF | base64 -d | openssl asn1parse -inform DER
    > MDQGCyqGSIb3DQEJEAEx
    > oCUEIzAhAgMA/mMwGjAL
    > AgUA+lbqAQQCAAEwCwIF
    > APpW6gIEAgAC
    > EOF
        0:d=0  hl=2 l=  52 cons: SEQUENCE
        2:d=1  hl=2 l=  11 prim: OBJECT            :id-ct-ASPA
       15:d=1  hl=2 l=  37 cons: cont [ 0 ]
       17:d=2  hl=2 l=  35 prim: OCTET STRING      [HEX DUMP]:3021020300FE63301A300B020500FA56EA0104020001300B020500FA56EA0204020002

Then decode the ASPA at byte 17 itself:

    $ cat << EOF | base64 -d | openssl asn1parse -i -inform DER -strparse 17
    > MDQGCyqGSIb3DQEJEAEx
    > oCUEIzAhAgMA/mMwGjAL
    > AgUA+lbqAQQCAAEwCwIF
    > APpW6gIEAgAC
    > EOF
        0:d=0  hl=2 l=  33 cons: SEQUENCE
        2:d=1  hl=2 l=   3 prim:  INTEGER           :FE63
        7:d=1  hl=2 l=  26 cons:  SEQUENCE
        9:d=2  hl=2 l=  11 cons:   SEQUENCE
       11:d=3  hl=2 l=   5 prim:    INTEGER           :FA56EA01
       18:d=3  hl=2 l=   2 prim:    OCTET STRING      [HEX DUMP]:0001
       22:d=2  hl=2 l=  11 cons:   SEQUENCE
       24:d=3  hl=2 l=   5 prim:    INTEGER           :FA56EA02
       31:d=3  hl=2 l=   2 prim:    OCTET STRING      [HEX DUMP]:0002