My RPI based VPN is still plugged in and appears to be still working.
I suspect that's also true of Brian Carpenter's.
Charles Eckel \(eckelcu\) wrote:
> We anticipate having support for L2 VPN available for the IETF 111
Hackathon.
> Adding Sean to the thread to comment on the
I didn’t think you were actually looking for a non-xml solution, but as you
mentioned in an earlier mail there’s my org-rfc setup which makes all this yang
stuff pretty simple. The source of the YANG module is in the single org-mode
formatted draft source, along with support for YANG validation
Hi Michael,
We anticipate having support for L2 VPN available for the IETF 111 Hackathon.
Adding Sean to the thread to comment on the availability of this service and
whether a device other than a previously supported Raspberry Pi will be
required.
Cheers,
Charles
> On Jun 11, 2021, at 8:46
Terra System wrote:
> Hello. What is the password of this room
> https://gather.town/app/L4fNNdm1NJa1sE2v/ietf How can I do to join?
You'll find the password here: https://www.ietf.org/how/meetings/110/110gather/
but I suspect it may change as we approach 111.
>> We have created a
Carsten Bormann wrote:
cb> How about
>>
cb> {::include foo--??-??.yang}
>>
cb> and, if there is no such file, kramdown-rfc expands the wild card in
cb> the directory and uses the numerically latest file?
>>
>> You'd use shell globs?
> Yes. Any need to go
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and
Approach WG of the IETF.
Title : Delegated Authority for Bootstrap Voucher Artifacts
Authors : Michael
Hi WG, Thomas Werner and I wrote draft-richardson-anima-jose-voucher last year.
The draft-ietf-anima-brski-async-enroll-02 document wants to do everything
with JOSE signed JSON rather than CMS signed JSON.
(I continue to argue that COSE-signed-CBOR will be better if doing things
over native BTLE)
Toerless Eckert wrote:
> I think multiple redirects can make a lot of sense, as Mcr said for
> resale chains for example. I wouldn't be too bothered with DoS attacks
> an attepting to come up with a tiny number. I'd rather go with a
> number larger than what i can think of
Toerless Eckert wrote:
> AFAIK, a 307 redirect can redirect to any other location and not only a
> different origin, e.g.:
> GET https://mycloudreg.example.com/.well-known/brski/requestvoucher
-> 307, Location: https://mycloudreg.example2.com/whatthecke/strangeurl
> AFAIK,
Hello.
What is the password of this room
https://gather.town/app/L4fNNdm1NJa1sE2v/ietf
How can I do to join?
Michael Richardson escreveu no dia sexta,
11/06/2021 à(s) 14:46:
>
> At the beginning of May, the participants in the Thursday BRSKI Design team
> call expressed interest in doing some
Netmod and anima moved to bcc.
>You'd use shell globs?
I think it might be better to use PCRE.
Horrible idea to use PCRE instead of globs.
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
On 2021-06-14, at 18:26, Michael Richardson wrote:
>
>cb> How about
>
>cb> {::include foo--??-??.yang}
>
>cb> and, if there is no such file, kramdown-rfc expands the wild card in
>cb> the directory and uses the numerically latest file?
>
> You'd use shell globs?
Yes. Any
Hello all,
I just submitted an update of BRSKI-AE which contains the following list of
changes to the 01 version:
o Defined call flow and objects for interactions in use case2. Object
format based on draft for JOSE signed voucher artifacts and
aligned the remaining objects with
Carsten Bormann wrote:
>> One possibility is that kramdown-rfc ought to look for, and include
>> the latest foo--MM-DD.yang file, when told to ::include foo.yang.
>> Alternatively, it could perhaps do the -MM-DD substitution itself.
cb> How about
cb> {::include
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and
Approach WG of the IETF.
Title : Support of asynchronous Enrollment in BRSKI (BRSKI-AE)
Authors : Steffen
I think multiple redirects can make a lot of sense, as Mcr said for resale
chains for example.
I wouldn't be too bothered with DoS attacks an attepting to come up with a tiny
number.
I'd rather go with a number larger than what i can think of being useful. 10
for example.
I could build a
Let me fork off a question:
AFAIK, a 307 redirect can redirect to any other location and not only
a different origin, e.g.:
GET https://mycloudreg.example.com/.well-known/brski/requestvoucher
-> 307, Location: https://mycloudreg.example2.com/whatthecke/strangeurl
AFAIK, there is no text
I can’t help you with your dark desires to use XML, but I would propose the
following fix for that:
— use xi:include or src= for the XML source (I forget which one works), with a
static name
— simply generate a symlink from the most recent .yang to the static name in
the Makefile
— use
Carsten Bormann wrote:
> On 14. Jun 2021, at 03:09, Michael Richardson
> wrote:
>>
>> 1) how to process yang files with -DD-MM into XML. 2) how to
>> generate yang tree files. 3) how do I get my YANG includes
>> downloaded, and do I put them into my repo? 4) how
> One possibility is that kramdown-rfc ought to look for, and include the
> latest foo--MM-DD.yang file, when told to ::include foo.yang.
> Alternatively, it could perhaps do the -MM-DD substitution itself.
How about
{::include foo--??-??.yang}
and, if there is no such file,
Carsten Bormann wrote:
> On 14. Jun 2021, at 03:09, Michael Richardson
wrote:
>>
>> 1) how to process yang files with -DD-MM into XML.
>> 2) how to generate yang tree files.
>> 3) how do I get my YANG includes downloaded, and do I put them into my
repo?
>> 4) how
Hi Michael!
There isn’t a standard of any sort, but as an active author of a large number
of drafts, I’ve been force to automate as much as possible:
- validating the schema
- validating examples
- generating tree diagrams
- stitching all off the above into an XML file
- on a
Hi Michael,
you can check my project YANG-I-D [1] for some ideas.
The most elegant way of including YANG modules in RFCs would be to treat the
RFC source as a compound XML document combining xml2rfc with YANG modules in
the YIN syntax - if only xml2rfc could process it.
Lada
[1]
23 matches
Mail list logo
