Re: [bess] Status of draft-ietf-l3vpn-acceptown-community

[Took Adrian off.] Hi! Any ideas on when we might see the update? Thanks! Alvaro. On 2/8/15, 5:50 PM, Adrian Farrel adr...@olddog.co.uk wrote: Hi authors, Good news /bad news :-) The IESG reviewed your document on Thursday on the telechat and approved it for publication as an RFC. Well

[bess] AD Review of draft-ietf-bess-spbm-evpn

Hi! I think the general readability of the document could improve. See below for some suggestions. While that is not a showstopper, I would like to see my comments about the Security Considerations (see below) addressed before starting the IETF Last Call. Thanks! Alvaro. Major: 1.

Re: [bess] Poll for adoption: draft-morin-bess-mvpn-fast-failover

bess WG: As those of you following this thread may have already noticed, no IPR had been disclosed related to this document, or any of the documents it replaces ([1] and [2]), at the time this adoption poll started..nor by the time the poll was to end on Oct/16. On Oct/17 the WG received a note

[bess] AD Review of draft-ietf-bess-virtual-subnet-02

Dear authors: I just finished reading this document. All of what is described in this document is straight forward, so much so that it requires no change to existing technology, which makes me think that users/operators have been able to do this all along. Is that correct? Is there anything

Re: [bess] AD Review of draft-ietf-bess-virtual-subnet-02

On 11/10/15, 2:18 AM, "Xuxiaohu" > wrote: Xiaohu: Hi! We have updated the draft according to your comments and suggestions. I just have a couple of small items. Please see my comments below.. I'm going to start the IETF Last Call and put this

[bess] AD Review of draft-ietf-bess-mvpn-extranet-03

Hi! I just finished reading this document. As mentioned by the WG chairs at the meeting in Yokohama, the technology in bess can be complex and hard to penetrate for the average (or novice) reader. While the target of documents like this one is not always the average (or novice) reader, it is

Re: [bess] AD Review of draft-ietf-bess-mvpn-bidir-ingress-replication-02

On 9/28/15, 10:39 AM, "thomas.mo...@orange.com" > wrote: Jeffrey/Thomas: Hi! First of all, please note that the Gen-ART review that came in today had the same comment about the Normative references…which

Re: [bess] AD Review of draft-ietf-bess-mvpn-bidir-ingress-replication-02

On 9/30/15, 2:34 AM, "thomas.mo...@orange.com" > wrote: Thomas: Hi! . . . Current: The label may be shared with other P-tunnels, subject to the anti-ambiguity rules for extranet

[bess] AD Review of draft-ietf-bess-mvpn-bidir-ingress-replication-02

Hi! I just finished reading this document. In general I think that there are some things that could be done to improve the readability/clarity. While the authors address the items below, I’ll start he IETF Last Call and put the document on the IESG Agenda (probably for Oct/15). Please post

Re: [bess] AD Review of draft-ietf-bess-mvpn-bidir-ingress-replication-02

On 9/25/15, 2:11 PM, "Jeffrey (Zhaohui) Zhang" > wrote: Jeffrey: Hi! . . . Major: 1. I-D.ietf-bess-ir and I-D.ietf-bess-mvpn-extranet should be Normative References. Zzh> Done. I-D.ietf-bess-ir wasn’t moved. . . . 1. Section 4. (Security

Re: [bess] Stephen Farrell's Discuss on draft-ietf-bess-virtual-subnet-06: (with DISCUSS and COMMENT)

Stephen: Hi! Xiaohu posted an update that we hope addresses your concerns. Pelase take a look. Thanks! Alvaro. ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess

Re: [bess] Alia Atlas' Discuss on draft-ietf-bess-virtual-subnet-06: (with DISCUSS)

Alia: Hi! Xiaohu posted an update which I think should address your concerns. Please take a look. Thanks! Alvaro. On 12/2/15, 11:13 PM, "Alia Atlas" > wrote: That works for me. Thanks, Alia On Dec 2, 2015 11:08 PM, "Xuxiaohu"

Re: [bess] AD Review of draft-ietf-bess-mvpn-extranet-03

On 11/17/15, 4:33 PM, "Eric C Rosen" wrote: >[Eric] Alvaro, thanks for your review. I just posted revision -04, >with a number of edits made in response to your comments. Thanks! I've requested IETF Last Call and put the document on the Telechat agenda. Alvaro.

Re: [bess] Joel Jaeggli's Discuss on draft-ietf-bess-mvpn-extranet-06: (with DISCUSS and COMMENT)

On 2/28/16, 5:37 PM, "Joel Jaeggli" wrote: Joel: Hi! How are you? ... >-- >DISCUSS: >-- > >After further discussion related to the ops dir

Re: [bess] AD Review of draft-ietf-bess-multicast-damping-03

On 2/24/16, 11:58 AM, "Thomas Morin" <thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>> wrote: Thomas: Hi! There are several places where we're still not in sync. Please se below. Maybe talking in person would be good. Thanks! Alvaro. 2016-02-23,

[bess] FW: Last Call: (Multicast VPN state damping) to Proposed Standard

idr and pim WGs: Hi! Please take a look at this document and send comments to the bess WG. The IETF Last Call expires on Apr/13, but the document is scheduled to be reviewed by the IESG on May/5, so there's enough time to address comments. Thanks! Alvaro. On 3/23/16, 3:18 PM,

Re: [bess] AD Review of draft-ietf-bess-evpn-vpws-07

One more thing…you’re missing the reference to RFC5226. Thanks! Alvaro. ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess

Re: [bess] AD Review of draft-ietf-bess-evpn-vpws-07

On 2/3/17, 4:41 PM, "Sami Boutros" wrote: > Thanks for your review. Please have a look at attached draft w/ most of the > comments > addressed. Looking at the published version -08. I have some answers to your answers below. I also see that there may be other

Re: [bess] AD Review of draft-ietf-bess-evpn-vpws-07

On 2/16/17, 3:57 PM, "Alvaro Retana (aretana)" <aret...@cisco.com<mailto:aret...@cisco.com>> wrote: On 2/3/17, 4:41 PM, "Sami Boutros" <sbout...@vmware.com> wrote: > Thanks for your review. Please have a look at attached draft w/ most of

Re: [bess] AD Review of draft-ietf-bess-evpn-vpws-07

On 2/3/17, 4:41 PM, "Sami Boutros" wrote: [Oops…sent the last two too early… ☹ ]   Sami: Hi > Thanks for your review. Please have a look at attached draft w/ most of the > comments > addressed.   Looking at the published version -08.   I have some answers to your answers

[bess] FW: WG Action: Formed L2VPN Service Model (l2sm)

FYI… On 11/4/16, 1:58 PM, "iesg on behalf of The IESG" on behalf of iesg-secret...@ietf.org> wrote: A new IETF WG has been formed in the Operations and Management Area. For additional information, please

[bess] AD Review of draft-ietf-bess-evpn-etree-09

Dear authors: I just finished reading this document. In general, the document could benefit from an editorial pass to improve readability; I put in some suggestions below, but I’m sure I didn’t mention all. I don’t think that my comments (even the Major ones) will be hard to resolve – most

Re: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-vpws-11: (with COMMENT)

Hi! Yes, the WG was made aware of the IPR at the WGLC: https://mailarchive.ietf.org/arch/msg/bess/I5_GI44221EZJGQGWHVdv0ukbGk/?qid=08649c721ebdb111c215f6854ff0c241 Alvaro. On 4/11/17, 12:34 PM, "Mirja Kühlewind" wrote:

Re: [bess] Alia Atlas' Discuss on draft-ietf-bess-evpn-vpws-11: (with DISCUSS and COMMENT)

Sami: Hi! Let’s go ahead and add the text to explain the operation with VXLAN – I think that the reference to rfc7348 should be Normative. I’ll take care of dealing with the downref when we’re ready with the new text. Thanks! Alvaro. On 4/12/17, 2:14 PM, "Sami Boutros"

Re: [bess] Opsdir last call review of draft-ietf-bess-evpn-etree-12

ints in rfc7385 (i.e., 0xFB is defined as experimental). Cheers, Ali From: "Alvaro Retana (aretana)" <aret...@cisco.com<mailto:aret...@cisco.com>> Date: Monday, August 21, 2017 at 6:26 PM To: Cisco Employee <saja...@cisco.com<mailto:saja...@cisco.com>>, &q

Re: [bess] Adam Roach's Discuss on draft-ietf-bess-evpn-vpws-13: (with DISCUSS and COMMENT)

On 5/11/17, 1:19 AM, "Adam Roach" wrote: Adam: Hi! > -- > DISCUSS: > -- > > Looking at the Shepherd write up and the Ballot, I see no

Re: [bess] AD Review of draft-ietf-bess-evpn-etree-09

On 5/9/17, 8:51 PM, "Ali Sajassi (sajassi)" > wrote: Ali: Hi! We’re on the right path, but not there yet. Please see my comments inline below. Thanks! Alvaro. … > > M1. Both the Introduction and the Abstract mention that “this document > >

Re: [bess] draft-ietf-bess-evpn-overlay-08

I know it’s there. I’ve been working on the spring documents which are taking up more time than I expected. BTW, you can follow at home here: https://datatracker.ietf.org/doc/ad/alvaro.retana/ Thanks! Alvaro. On 6/23/17, 2:10 AM, "Ali Sajassi (sajassi)"

Re: [bess] AD Review of draft-ietf-bess-evpn-etree-09

On 5/12/17, 7:15 PM, "Ali Sajassi (sajassi)" > wrote: Ali: Hi! Sorry for the long RTT, busy days… I have two remaining comments (below). Once the registry is defined, then we can start the IESTF LC. Thanks! Alvaro. … > > > M6. Definition of

[bess] FW: Last Call: (YANG Data Model for L3VPN Service Delivery) to Proposed Standard

FYI… Please take a look. If anyone has comments, please reply to the thread in the i...@ietf.org list. Thanks! Alvaro. On 9/13/17, 10:04 AM, "IETF-Announce on behalf of The IESG" wrote: The IESG has received a request

Re: [bess] Opsdir last call review of draft-ietf-bess-evpn-etree-12

his document 0xFB-0xFE Experimental[RFC7385] 0xFFReserved [RFC7385] From: Cisco Employee <saja...@cisco.com<mailto:saja...@cisco.com>> Date: Monday, August 21, 2017 at 5:14 PM To: "Alvaro Retana (aretana)" <aret...