A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group
WG of the IETF.
Title : Finding and Using Geofeed Data
Authors : Randy Bush
M
Rob Wilton \(rwilton\) wrote:
> Stephane or Warren can probably can correct me as a butcher the
> explanation, but ...
> ... I think that the issue is that the appendix is given as sequence of
> steps to follow, and in Step 1 (A.1), the certificate is generated
> using an elli
mornin rob,
new diff attached
> So, solely for my understanding, if 8805 was updated in an
> incompatible way
then it would not be 8805. it would not be a geofeed file. so the
kiddies then can have fun with a complete do-over and write their own
finding-blarffles draft.
> This makes me questi
> This I-D already defines a new content type: id-ct-geofeedCSVwithCRLF.
clearly without enough words :)
> OLD:
>
>Borrowing detached signatures from [RFC5485], after text file
>canonicalization (Sec 2.2), the Cryptographic Message Syntax (CMS)
>[RFC5652] would be used to create a de
> On Apr 12, 2021, at 7:33 PM, Randy Bush wrote:
>
3. The definition of canonicalization refers to section 2.2 of RFC
5485 (which talks about ASCII) vs RFC8805 which talks about UTF-8. Is
this disparity an issue?
>>>
>>> russ, how do you want to handle?
>>
>> This is really a
The write-up can be seen in the datatraker at
https://datatracker.ietf.org/doc/draft-ietf-opsawg-vpn-common/. I'd be
happy to address any comments.
I recommend that this document is held until the L3NM draft is also ready so
that they can proceed together, although this is not strictly required.
Hi Randy,
Thanks. Please see inline ...
> -Original Message-
> From: Randy Bush
> Sent: 12 April 2021 22:37
> To: Rob Wilton (rwilton)
> Cc: Ops Area WG ; draft-ietf-opsawg-finding-
> geofeeds@ietf.org
> Subject: Re: AD review of draft-ietf-opsawg-finding-geofeeds-04
>
> hi rob et
