[bess] [Technical Errata Reported] RFC8214 (5571)

2018-12-10 Thread RFC Errata System
The following errata report has been submitted for RFC8214, "Virtual Private Wire Service Support in Ethernet VPN". -- You may review the report below and at: http://www.rfc-editor.org/errata/eid5571 -- Type: Technical Report

Re: [bess] Secdir last call review of draft-ietf-bess-evpn-df-election-framework-06

2018-12-10 Thread Rabadan, Jorge (Nokia - US/Mountain View)
Hi Russ, Thank you very much for your review. We'll publish a new version once we make all the changes suggested by the different reviewers. Please see some comments in-line with [JORGE]. Thank you. Jorge -Original Message- From: Russ Housley Date: Sunday, December 9, 2018 at 3:29 AM

Re: [bess] Referencing material behind a paywall

2018-12-10 Thread Heather Flanagan
On 12/7/18 9:20 PM, Adrian Farrel wrote: Hi, [Changed the subject line, tried to reduce the recipients (but it's still a bit much), added the RSE in case she has advice] It's tricky. Sometimes we need to reference material that is behind a paywall or simply in a paper journal. Sometimes we n

Re: [bess] Referencing material behind a paywall

2018-12-10 Thread Carsten Bormann
On Dec 10, 2018, at 21:41, Heather Flanagan wrote: > > similar to IPR declarations For those people who believe in “IPR”, copyrights (which is the mechanism used to protect specifications that are behind paywalls) are “IPR". So this is very logical, even if the impact of this kind of IPR on l

Re: [bess] Referencing material behind a paywall

2018-12-10 Thread Stephen Farrell
On 10/12/2018 20:41, Heather Flanagan wrote: > Ekr offered an interesting proposal that would have this kind of > reference be treated in a fashion similar to IPR declarations. Not a bad idea. I'd also make it like the downref registry [1] though, since once we've got a normative reference in on