Re: [Sidrops] I-D Action: draft-ietf-sidrops-rpki-rsc-07.txt

Job:

I understand that inheritance is purposfully being removed.  No concerns there.

However, RFC 779 says:

   IPAddressFamily     ::= SEQUENCE {    -- AFI & optional SAFI --
      addressFamily        OCTET STRING (SIZE (2..3)),
      ipAddressChoice      IPAddressChoice }

Why is the addressFamily in this document limited to two octets?

Russ

> On May 19, 2022, at 1:33 PM, Job Snijders <job=40fastly.com@dmarc.ietf.org> wrote:
> 
> Dear all,
> 
> Based on feedback from RPKI Cache Validator implementers the wire format
> was adjusted Surely For Last Time! [tm] :-)
> 
> The new RSC ASN.1 module permits the use of existing RFC 3779
> encoders/decoders, with two major constraints: inheritance is not
> permitted, and RDI is not a thing. This update enables implementers to
> use commonly deployed high-level API functions, or generate code from
> the ASN.1 module which will impose the desired constraints.
> 
> @ Chairs - I think the ball now is back in your court? :-)
> 
> Kind regards,
> 
> Job
> 
> On Thu, May 19, 2022 at 10:24:10AM -0700, internet-drafts@ietf.org wrote:
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the SIDR Operations WG of the IETF.
>> 
>>        Title           : A profile for Resource Public Key Infrastructure (RPKI) Signed Checklists (RSC)
>>        Authors         : Job Snijders
>>                          Tom Harrison
>>                          Ben Maddison
>> 	Filename        : draft-ietf-sidrops-rpki-rsc-07.txt
>> 	Pages           : 16
>> 	Date            : 2022-05-19
>> 
>> Abstract:
>>   This document defines a Cryptographic Message Syntax (CMS) profile
>>   for a general purpose listing of checksums (a 'checklist'), for use
>>   with the Resource Public Key Infrastructure (RPKI).  The objective is
>>   to allow an attestation, in the form of a listing of one or more
>>   checksums of arbitrary digital objects (files), to be signed "with
>>   resources", and for validation to provide a means to confirm a
>>   specific Internet Resource Holder produced the Signed Checklist.  The
>>   profile is intended to provide for the signing of an arbitrary
>>   checksum listing with a specific set of Internet Number Resources.
>> 
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-sidrops-rpki-rsc/
>> 
>> There is also an HTML version available at:
>> https://www.ietf.org/archive/id/draft-ietf-sidrops-rpki-rsc-07.html
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-rpki-rsc-07
>> 
>> 
>> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>> 
>> 
>> _______________________________________________
>> Sidrops mailing list
>> Sidrops@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidrops
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops