Hi Carsten,
>>> Examples from the HTTP ecosystem (GNAP, HTTPAPI, HTTPBIS) didn’t have any
>>> “===“ decoration, though. (Why the heck was this left open as a choice for
>>> the author? I like “%%%” decoration instead, should I use that as a
>>> personal fashion statement?)
>>
>> Because
On 2021-12-17, at 17:31, Kent Watsen wrote:
>
>> Examples from the HTTP ecosystem (GNAP, HTTPAPI, HTTPBIS) didn’t have any
>> “===“ decoration, though. (Why the heck was this left open as a choice for
>> the author? I like “%%%” decoration instead, should I use that as a
>> personal fashion
> (15 equals signs left, 16 equals signs right) seems to be the favorite
> lead-in; however, draft-wing-dnsop-structured-dns-error-page-01.txt had a
> version indented by 2 characters that has 14+15 accordingly. About 5 %
> 10+11, apparently before RFC 8792 was published so there was less
Now you made me curious.
No RFCs use RFC 8792 encoding yet (except for RFC 8792 itself), as you said.
I-Ds:
"Grant Negotiation and Authorization Protocol", Justin Richer, Aaron
Parecki, Fabien Imbault, 2021-10-25,
(Using this for JSON text.)
"Problem Details for HTTP APIs", Mark
Hi Benoit,
>>> `pyang` and I think `yanglint` also know how to extract folded
>>> and elements.
>> Just a correction; pyang doesn't extract anything, but rfcstrip does,
>> and it supports folded artwork, and in the latest greatest 1.3 release
>> it even reconizes the proper RFC8792-defined
Trimming the cc:
From: netmod on behalf of Benoit Claise
Sent: 14 December 2021 08:17
Dear all,
>> `pyang` and I think `yanglint` also know how to extract folded
>> and elements.
> Just a correction; pyang doesn't extract anything, but rfcstrip does,
> and it supports folded artwork, and in
Dear all,
`pyang` and I think `yanglint` also know how to extract folded
and elements.
Just a correction; pyang doesn't extract anything, but rfcstrip does,
and it supports folded artwork, and in the latest greatest 1.3 release
it even reconizes the proper RFC8792-defined magic strings ;-)
Do
Kent Watsen writes:
>> On Dec 12, 2021, at 5:11 PM, Michael Richardson
>> wrote:
>>
>>
>> Carsten Bormann wrote:
>>> On 2021-12-12, at 22:17, Michael Richardson wrote:
>>
I'm working on draft-richardson-anima-rfc8366bis, trying to make it
RFC8791.
>>> […]
What I don't know
Kent Watsen wrote:
>
>
> > On Dec 12, 2021, at 5:11 PM, Michael Richardson
> > wrote:
> >
> >
> > Carsten Bormann wrote:
> >> On 2021-12-12, at 22:17, Michael Richardson
> >> wrote:
> >
> >>> I'm working on draft-richardson-anima-rfc8366bis, trying to make it
> >>> RFC8791.
> >> […]
> >>>
> On Dec 12, 2021, at 5:11 PM, Michael Richardson wrote:
>
>
> Carsten Bormann wrote:
>> On 2021-12-12, at 22:17, Michael Richardson wrote:
>
>>> I'm working on draft-richardson-anima-rfc8366bis, trying to make it RFC8791.
>> […]
>>> What I don't know how to deal with:
>
>> RFC 8792?
>
>
On 12. Dec 2021, at 23:11, Michael Richardson wrote:
>
> So if RFC8792 is the solution, then I think that I probably prefer to have
> ::include do it.
Try {::include-fold …} in 1.5.22.
The fold flag will do nothing if not needed, and RFC-8792-fold1 otherwise.
(I have only implemented
Carsten Bormann wrote:
> On 2021-12-12, at 22:17, Michael Richardson wrote:
>> I'm working on draft-richardson-anima-rfc8366bis, trying to make it
RFC8791.
> […]
>> What I don't know how to deal with:
> RFC 8792?
If I put \ into the original .yang file, then it won't
On Sun, Dec 12, 2021 at 04:17:02PM -0500, Michael Richardson wrote:
>
> What I don't know how to deal with:
>
> .../draft-richardson-anima-rfc8366bis.xml(397): Warning: Too long line found
> (L382), 1 characters longer than 72 characters:
> namespace
On 2021-12-12, at 22:17, Michael Richardson wrote:
> I'm working on draft-richardson-anima-rfc8366bis, trying to make it RFC8791.
[…]
> What I don't know how to deal with:
RFC 8792?
(ducks)
Grüße, Carsten
___
netmod mailing list
netmod@ietf.org
I'm working on draft-richardson-anima-rfc8366bis, trying to make it RFC8791.
I'm getting many too long line found. I sure wish for description, that
pyang had a wrap option, but I can cope with doing that manually.
What I don't know how to deal with:
15 matches
Mail list logo