[bess] Rtgdir last call review of draft-ietf-bess-mvpn-expl-track-09

Reviewer: Carlos Pignataro Review result: Has Nits This is a very well written and detailed document. I have only one concern, which I believe should be addressed before moving this document forward: I found the rational and specific details on what this document "Updates" from thre

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

Reviewer: Carlos Pignataro Review result: Has Issues Reviewer: Carlos Pignataro Review result: Has Nits (and one potential Issue) I am the OPS-DIR reviewer and in general I do not have operational concerns with this document. The main issue I have is in regards to the redefinition of the MSB of

[bess] Opsdir telechat review of draft-ietf-bess-evpn-etree-13

Reviewer: Carlos Pignataro Review result: Ready Thank you for considering and addressing all the comments and requests from my previous OpsDir review of -12! Carlos Pignataro. ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo

Re: [bess] Rtgdir last call review of draft-ietf-bess-mvpn-expl-track-09

Hi, Eric, On Sep 13, 2018, at 9:52 AM, Eric C Rosen mailto:ero...@juniper.net>> wrote: On 9/12/2018 11:26 PM, Carlos Pignataro wrote: I found the rational and specific details on what this document "Updates" from three previous RFCs to be lacking, and confusing. Carlos, Thanks

Re: [bess] draft-hao-bess-inter-nvo3-vpn

> On Apr 13, 2015, at 11:48 AM, Robert Raszuk wrote: > > Transport of RFC4364 can be realized with IPv4 or IPv6 just fine. > > Please see: > > MPLS in IP or GRE > https://tools.ietf.org/html/rfc4023 > > MPLS in UDP > https://tools.ietf.org/html/rfc7510

Re: [bess] [mpls] [Editorial Errata Reported] RFC7510 (4350)

Hi Xiaohu, > On Apr 29, 2015, at 4:40 AM, Xuxiaohu wrote: > > Hi Carlos, > >> -Original Message----- >> From: Carlos Pignataro (cpignata) [mailto:cpign...@cisco.com >> <mailto:cpign...@cisco.com>] >> Sent: Wednesday, April 29, 2015 2:58 AM >

Re: [bess] [mpls] [Editorial Errata Reported] RFC7510 (4350)

lso add > other references to the registry, specifically the document that defines the > tunnel mechanism for each of the other tunnel types. > > Ross (speaking as co-author of RFC 7510) > > From: Carlos Pignataro (cpignata) [mailto:cpign...@cisco.com] > Sent: Wednesday, April

Re: [bess] I-D Action: draft-ietf-idr-tunnel-encaps-01.txt

Hi, Eric, Thanks for sending this out — I am interested in this document, and will give it a critical review (in particular the sections you call out below). In the mean time, however, I wanted to send a few high-level comments (prepended with “CMP”) from scanning through it. I hope these are u

Re: [bess] I-D Action: draft-ietf-idr-tunnel-encaps-01.txt

Eric, Thanks for the response — please find some follow-ups inline. > On Feb 15, 2016, at 12:22 PM, Eric C Rosen wrote: > > On 2/11/2016 6:38 PM, Carlos Pignataro (cpignata) wrote: >> Hi, Eric, >> >> Thanks for sending this out — I am interested in this docum

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

“MUST”? Thanks! Carlos. On Aug 16, 2017, at 8:54 PM, Ali Sajassi (sajassi) mailto:saja...@cisco.com>> wrote: Hi Carlos, Thanks for your review and comments. Please see inline for my responses. On 8/7/17, 2:46 PM, "Carlos Pignataro (cpignata)" mailto:cpign...@cisco.com>