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

On 9/30/15, 2:34 AM, "thomas.mo...@orange.com" mailto: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 [I-D.ietf-bess-mvpn-extranet

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

Hi Alvaro, 2015-09-30, Alvaro Retana (aretana): 2015-09-28, Jeffrey (Zhaohui) Zhang: Alvaro, > I-D.ietf-bess-ir and I-D.ietf-bess-mvpn-extranet should be Normative References. I thought about this further, and would like to keep them both as informational for the follow

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

On 9/28/15, 10:39 AM, "thomas.mo...@orange.com" mailto: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 really indicates that if yo

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

Hi Jeffrey, Alvaroo, 2015-09-28, Jeffrey (Zhaohui) Zhang: Alvaro, > I-D.ietf-bess-ir and I-D.ietf-bess-mvpn-extranet should be Normative References. I thought about this further, and would like to keep them both as informational for the following reasons. The extranet draft is referred t

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

Alvaro, > I-D.ietf-bess-ir and I-D.ietf-bess-mvpn-extranet should be Normative > References. I thought about this further, and would like to keep them both as informational for the following reasons. The extranet draft is referred to in the draft as following: ... The label may be shared wi

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

Hi Alvaro, [resending, because I had mailer daemon from junipernetworks.onmicrosoft.com] 2015-09-24, Alvaro Retana (aretana): Also, some of the text [...] may not be accesible to the average reader,... As a side note, while what you wrote is true, I would say that it will be hard to fix. M

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

Jeffrey, all, [resending this one too...] (below) 2015-09-25, Jeffrey (Zhaohui) Zhang: *From:*Alvaro Retana (aretana) [mailto:aret...@cisco.com] 5. Section 4. (Security Considerations) Are there really no security considerations? * Section 3.1. (Control State) Says that: "To s

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

Jeffrey, all, (below) 2015-09-25, Jeffrey (Zhaohui) Zhang: *From:*Alvaro Retana (aretana) [mailto:aret...@cisco.com] 5. Section 4. (Security Considerations) Are there really no security considerations? * Section 3.1. (Control State) Says that: "To speed up convergence…P

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

Hi Alvaro, 2015-09-24, Alvaro Retana (aretana): Also, some of the text [...] may not be accesible to the average reader,... As a side note, while what you wrote is true, I would say that it will be hard to fix. Most mVPN-related specs are deemed to remain fairly inaccessible to somebody not

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

On 9/25/15, 2:11 PM, "Jeffrey (Zhaohui) Zhang" mailto:zzh...@juniper.net>> 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 Considerations) Are

[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 an