[trill] Suggested new text for sections 3.4 and 4.3 of draft-ietf-trill-transport-over-mpls-01

2016-09-22 Thread Andrew G. Malis
I just reviewed draft-ietf-trill-transport-over-mpls-01, with particular attention to the pseudowire encapsulation used in sections 3.4 and 4.3. While technically correct, the details were a bit on the sparse side, especially for section 3.4. I’ve got some suggested replacement text: Section 3.4:

Re: [trill] [RTG-DIR] Routing Area Directorate QA review of draft-ietf-trill-transport-over-mpls-02

2017-02-27 Thread Andrew G. Malis
I’ve got some comments on Matthew’s review, inline. On Mon, Feb 27, 2017 at 10:44 AM, Bocci, Matthew (Nokia - GB) < matthew.bo...@nokia.com> wrote: > Routing Area Directorate QA review of draft-ietf-trill-transport- > over-mpls-02 > > > > Hi, > > > > I have been assigned the QA reviewer for this

Re: [trill] [RTG-DIR] Routing Area Directorate QA review of draft-ietf-trill-transport-over-mpls-02

2017-03-20 Thread Andrew G. Malis
Kingston, On Sun, Mar 19, 2017 at 4:35 PM, Kingston Smiler wrote: > > Typically PBB-VPLS is used to avoid exposing the customer MAC in service > provider network. In case of TRILL packet over MPLS, already the customer > MAC is encapsulated inside the TRILL header. Having said that, do we reall

Re: [trill] [RTG-DIR] Routing Area Directorate QA review of draft-ietf-trill-transport-over-mpls-02

2017-05-30 Thread Andrew G. Malis
esolves your comments? > > My apologies for taking so long. > > > > Regards, > > Umair > > > > *From:* trill [mailto:trill-boun...@ietf.org] *On Behalf Of *Andrew G. > Malis > *Sent:* Monday, March 20, 2017 12:40 PM > *To:* Kingston Smiler > *Cc:* Bocci,

Re: [trill] [RTG-DIR] Routing Area Directorate QA review of draft-ietf-trill-transport-over-mpls-02

2017-06-03 Thread Andrew G. Malis
to resolve your Comments. > > > > Regards, > > Umair > > > > *From:* Andrew G. Malis [mailto:agma...@gmail.com] > *Sent:* Tuesday, May 30, 2017 9:21 PM > *To:* Mohammed Umair > *Cc:* Bocci, Matthew (Nokia - GB); rtg-...@ietf.org; > draft-ietf-trill-transport-over-

Re: [trill] draft-ietf-trill-transport-over-mpls - WG LC (11/11 to 11/25)

2017-11-21 Thread Andrew G. Malis
Sue, I found that this draft has several places where interoperability between implementations could be difficult because there are several implementation choices that can be made, and the draft doesn’t make any particular recommendations or require any of the choices to be implemented. 1. There

Re: [trill] Comments on draft-ietf-trill-transport-over-mpls-06

2018-01-17 Thread Andrew G. Malis
Donald, I agree with your recommended changes. While we’re discussing the draft, I've previously commented that it has several places where interoperability between implementations could be difficult because there are several implementation choices that can be made, and the draft doesn’t make any

Re: [trill] I-D Action: draft-ietf-trill-transport-over-mpls-07.txt

2018-01-20 Thread Andrew G. Malis
Donald, Thanks, my comments are resolved. Cheers, Andy On Fri, Jan 19, 2018 at 7:16 PM, Donald Eastlake wrote: > This revision is intended to resolve the comments from Andy Malis and > myself. > > Thanks, > Donald > === > Donald E. Eastlake 3rd +1-508-333-2270 (

Re: [trill] draft-ietf-trill-transport-over-MPLS - 1 week extension to WG LC (11/11/2017 to 11/25/2017) - 1/19/2018 to 1/26/2018

2018-01-20 Thread Andrew G. Malis
Sue, My comments have been resolved, and I feel that this draft is ready for publication. And to answer your first question, yes, this is needed functionality. Thanks, Andy On Sat, Jan 20, 2018 at 12:17 AM, Susan Hares wrote: > This begins a 1 week extension to the WG LC for > draft-ietf-tri

Re: [trill] Kathleen Moriarty's Discuss on draft-ietf-trill-transport-over-mpls-07: (with DISCUSS)

2018-03-07 Thread Andrew G. Malis
Kathleen, I don’t want to speak for the authors. However, I did contribute to this draft (although not this specific section). So that said, here’s my two cents …. I agree that first sentence could have been worded better, but the bottom line is that depending on the model used, the security cons