Re: [i2rs] RIB definition ...

Here is another draft that intends to cover the VN (VLAN, L2VPN, L3VPN, etc.) and VC (TE LSP, PW, etc.) applications http://tools.ietf.org/html/draft-hares-use-case-vn-vc-00 Best regards, Mach From: i2rs-boun...@ietf.org [i2rs-boun...@ietf.org] on

Re: [i2rs] Thoughts on draft-chen-idr-rr-based-traffic-steering-usecase as an I2RS Use Case

Hi Russ, Thanks for bringing up this discussion! Please see my reply inline... Best regards, Mach -Original Message- From: i2rs-boun...@ietf.org [mailto:i2rs-boun...@ietf.org] On Behalf Of Russ White Sent: Monday, July 15, 2013 8:45 PM To: i2rs@ietf.org Cc: zh...@gsta.com

Re: [i2rs] Thoughts on draft-chen-idr-rr-based-traffic-steering-usecase as an I2RS Use Case

- From: rras...@gmail.com [mailto:rras...@gmail.com] On Behalf Of Robert Raszuk Sent: Friday, July 19, 2013 9:56 PM To: Mach Chen Cc: Russ White; i2rs@ietf.org; i...@ietf.org; zh...@gsta.com Subject: Re: [i2rs] Thoughts on draft-chen-idr-rr-based-traffic-steering-usecase as an I2RS Use Case

Re: [i2rs] Thoughts on draft-chen-idr-rr-based-traffic-steering-usecase as an I2RS Use Case

Hi Robert, Please see my reply inline... -Original Message- From: rras...@gmail.com [mailto:rras...@gmail.com] On Behalf Of Robert Raszuk Sent: Monday, July 22, 2013 6:35 PM To: Mach Chen Cc: Russ White; i2rs@ietf.org; i...@ietf.org; zh...@gsta.com; wangsb Subject: Re: [i2rs

Re: [i2rs] Multi-Headed Control

Hi Joel, We discussed various models of conflict resolution for the case when one client adjusts a piece of data, and then another client goes to change that data. Are there any specifications about the unit of the data ? I did not find this in the architecture and IM documents. decide

Re: [i2rs] Multi-Headed Control

. This may need some guide/clarify text in the architecture. Best regards, Mach -Original Message- From: Joel M. Halpern [mailto:j...@joelhalpern.com] Sent: Wednesday, January 15, 2014 11:17 AM To: Mach Chen; KwangKoog Lee Cc: i2rs@ietf.org; Guanxiaoran Subject: Re: [i2rs] Multi-Headed

Re: [i2rs] WG Adoption call for draft-clarke-i2rs-traceability-03 from 11/24 to 12/9/14

I have read the draft, it documents a useful function of I2RS. I support the adoption of draft to be a WG document. Best regards, Mach From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of Susan Hares Sent: Tuesday, November 25, 2014 1:03 PM To: i2rs@ietf.org Cc: 'Jeffrey Haas'; 'Alia Atlas'

[i2rs] Shepherd review on draft-ietf-i2rs-architecture-06

Hi Authors, I just finished the shepherd review on draft-ietf-i2rs-architecture-06, it's well written and easy for reading. I have the following comments for this version, most of them are editorial comments. 1. Some (not well-known) of the acronyms may need to be expanded in their first

Re: [i2rs] Shepherd review on draft-ietf-i2rs-architecture-06

. Halpern [mailto:j...@joelhalpern.com] Sent: Thursday, December 04, 2014 11:04 PM To: Mach Chen; draft-ietf-i2rs-architect...@tools.ietf.org Cc: i2rs@ietf.org Subject: Re: [i2rs] Shepherd review on draft-ietf-i2rs-architecture-06 Thanks for the review. The editorial items we clealry should apply

Re: [i2rs] Shepherd review on draft-ietf-i2rs-architecture-06

-traceability is different from other references. So let's make it as an informational reference. Best regards, Mach -Original Message- From: Joel Halpern [mailto:joel.halp...@ericsson.com] Sent: Friday, December 05, 2014 9:26 AM To: Mach Chen; Joel M. Halpern; draft-ietf-i2rs-architect

Re: [i2rs] New Version Notification - draft-wang-i2rs-rib-data-model-02.txt

Hi Feng, Thanks for your comments! Yes, you are right. We have considered using the “feature” and “if-feature” to achieve the optional rib capabilities, but this version does not reflect that. We will update it in a later revision. Best regards, Mach From: feng.chon...@zte.com.cn

Re: [i2rs] Questions suggestions to draft-ietf-i2rs-usecase-reqs-summary-00

are not so clear when the use case draft composed. Your suggestions are good, and we will incorporate the suggestions into the next revision. Best regards, Mach From: Linda Dunbar Sent: Thursday, February 26, 2015 3:16 AM To: Susan Hares; Mach Chen; i2rs@ietf.org Subject: Questions suggestions

Re: [i2rs] WG Adoption call for draft-wang-i2rs-rib-data-model-02 (

Support as a co-author. Best regards, Mach From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of Susan Hares Sent: Tuesday, March 10, 2015 10:49 PM To: i2rs@ietf.org Cc: 'Jeffrey Haas'; 'Alia Atlas' Subject: [i2rs] WG Adoption call for draft-wang-i2rs-rib-data-model-02 ( This is a 3 WG

Re: [i2rs] 3 week adoption call for draft-clemm-i2rs-yang-network-topo-04.txt (3/10 to 3/31)

I have read this model draft, it is well written and useful, so I support the adoption! Best regards, Mach From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of Susan Hares Sent: Tuesday, March 10, 2015 11:01 PM To: i2rs@ietf.org Cc: 'Jeffrey Haas' Subject: [i2rs] 3 week adoption call for

[i2rs] Use case for nexthop in another routing instance.

Hi, I just reviewed the I2RS minutes of IETF 92th. There is a question as below: Anoop: what is the use case for next hop in another routing instance? One of the use cases is VRF-2-VRF communication within a single PE, this can be achieved by configuring the RT or static VRF route. When

Re: [i2rs] feedback on draft-ietf-i2rs-rib-data-model-03

Hi Chris, Thanks for your comments! Please see my reply inline... > From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of Chris Bowers > Sent: Monday, November 09, 2015 9:32 PM > To: i2rs@ietf.org > Subject: [i2rs] feedback on draft-ietf-i2rs-rib-data-model-03 > > I2RS WG and draft authors,

Re: [i2rs] feedback on draft-ietf-i2rs-rib-data-model-03

...@gmail.com] Sent: Tuesday, December 01, 2015 4:32 AM To: Mach Chen Cc: Jeffrey (Zhaohui) Zhang; Nitin Bahadur; Manish Kumar (manishkr); Chris Bowers; i2rs@ietf.org Subject: Re: [i2rs] feedback on draft-ietf-i2rs-rib-data-model-03 From my perspective, adding encap for a next-hop in the RIB makes

Re: [i2rs] FW: I-D Action: draft-ietf-i2rs-rib-data-model-04.txt

ay, November 23, 2015 7:30 PM > To: Susan Hares; i2rs@ietf.org > Subject: Re: [i2rs] FW: I-D Action: draft-ietf-i2rs-rib-data-model-04.txt > > Sue, > > From: i2rs <i2rs-boun...@ietf.org> on behalf of Susan Hares > <sha...@ndzh.com> > Date: Monday, November 23, 201

Re: [i2rs] I-D Action: draft-ietf-i2rs-rib-data-model-04.txt

model just treats a tunnel as the nexthop, it does not intend to create a tunnel and just uses an existing one. Best regards, Mach > -Original Message- > From: Acee Lindem (acee) [mailto:a...@cisco.com] > Sent: Tuesday, November 24, 2015 3:56 AM > To: Mach Chen; i2rs@ietf.org >

Re: [i2rs] Problem using rib-data-model RPC with rib-info-model Information (draft-ietf-i2rs-rib-data-model-05 + draft-ietf-i2rs-rib-info-model-08)

nexthops. Best regards, Mach From: Edwin Cordeiro [mailto:edwi...@gmail.com] Sent: Saturday, June 25, 2016 3:25 PM To: Mach Chen Cc: i2rs Subject: Re: [i2rs] Problem using rib-data-model RPC with rib-info-model Information (draft-ietf-i2rs-rib-data-model-05 + draft-ietf-i2rs-rib-info-model-08) Hi

Re: [i2rs] [RTG-DIR] RtgDir review: draft-ietf-i2rs-traceability-06.txt

OK, thanks for your prompt response! Best regards, Mach > -Original Message- > From: rtg-dir [mailto:rtg-dir-boun...@ietf.org] On Behalf Of Susan Hares > Sent: Monday, January 18, 2016 7:10 PM > To: Mach Chen; rtg-...@tools.ietf.org > Cc: rtg-...@ietf.org; draft-ietf-i2

Re: [i2rs] Problem using rib-data-model RPC with rib-info-model Information (draft-ietf-i2rs-rib-data-model-05 + draft-ietf-i2rs-rib-info-model-08)

, Mach From: Edwin Cordeiro [mailto:edwi...@gmail.com] Sent: Monday, June 27, 2016 4:02 PM To: Mach Chen Cc: i2rs Subject: Re: [i2rs] Problem using rib-data-model RPC with rib-info-model Information (draft-ietf-i2rs-rib-data-model-05 + draft-ietf-i2rs-rib-info-model-08) Hi Mach, I mean the RIB

Re: [i2rs] I-D Action: draft-ietf-i2rs-rib-data-model-06.txt

This version addresses the comments from Edwin and Routing Directorate QA review (John). Thanks, Mach > -Original Message- > From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of > internet-dra...@ietf.org > Sent: Monday, July 04, 2016 2:39 PM > To: i-d-annou...@ietf.org > Cc:

Re: [i2rs] WG LC for draft-ietf-i2rs-rib-data-model - 3rd WG LC (12/7 to 12/21)

Hi Sue, I am not aware of any IPR related to this document. Best regards, Mach From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of Susan Hares Sent: Friday, December 08, 2017 9:13 AM To: i2rs@ietf.org Cc: 'Russ White' ; 'Alia Atlas' Subject: [i2rs] WG LC for

Re: [i2rs] IPR recall for draft-ietf-i2rs-rib-data-model - Urgent

kat...@gmail.com>; wang_little_s...@sina.com; h...@packetdesign.com; Mach Chen <mach.c...@huawei.com>; amit.d...@ericsson.com; sriganeshk...@gmail.com; nitin_baha...@yahoo.com; draft-ietf-i2rs-rib-data-mo...@ietf.org; 'Russ White' <r...@riw.us> Subject: IPR recall for draft-ietf-i

Re: [i2rs] Alvaro Retana's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)

Hi Alvaro, Thanks for the comments, please see my replies inline... > -Original Message- > From: Alvaro Retana [mailto:aretana.i...@gmail.com] > Sent: Tuesday, April 03, 2018 3:15 PM > To: The IESG > Cc: draft-ietf-i2rs-rib-data-mo...@ietf.org; Susan Hares

Re: [i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)

Hi Alissa, Thanks for your comments! Please see my responses inline... > -Original Message- > From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of Alissa Cooper > Sent: Tuesday, April 03, 2018 11:10 PM > To: The IESG > Cc: i2rs@ietf.org;

Re: [i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)

Hi Tom, > -Original Message- > From: t.petch [mailto:ie...@btconnect.com] > Sent: Sunday, April 08, 2018 7:42 PM > To: Mach Chen <mach.c...@huawei.com>; Alissa Cooper > <ali...@cooperw.in>; The IESG <i...@ietf.org> > Cc: i2rs@ietf.org; draft-ietf-i2rs-

Re: [i2rs] Suresh Krishnan's Discuss on draft-ietf-i2rs-rib-data-model-10: (with DISCUSS and COMMENT)

Thanks Suresh, Martin and Sue, The issues will be addressed in verion-11. Best regards, Mach > -Original Message- > From: Susan Hares [mailto:sha...@ndzh.com] > Sent: Thursday, April 05, 2018 10:08 PM > To: 'Martin Bjorklund' > Cc: sur...@kaloom.com; i...@ietf.org;

Re: [i2rs] Ignas Bagdonas' No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)

Hi Ignas, Thanks for your comments! Please see my replies inline... > -Original Message- > From: Ignas Bagdonas [mailto:ibagd...@gmail.com] > Sent: Thursday, April 05, 2018 7:14 PM > To: The IESG > Cc: draft-ietf-i2rs-rib-data-mo...@ietf.org; Susan Hares

Re: [i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)

Hi Tom, Thanks for your comments! It will be fixed in the upcoming version-11. Best regards, Mach > -Original Message- > From: t.petch [mailto:ie...@btconnect.com] > Sent: Wednesday, April 11, 2018 5:22 PM > To: Alissa Cooper <ali...@cooperw.in>; Mach Chen <mach.

Re: [i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)

Hi Benoit, OK, will use you suggested text below. Thanks, Mach From: Benoit Claise [mailto:bcla...@cisco.com] Sent: Monday, April 16, 2018 10:08 PM To: Mach Chen <mach.c...@huawei.com>; t.petch <ie...@btconnect.com>; Alissa Cooper <ali...@cooperw.in> Cc: i2rs@ietf.org; draft-

[i2rs] IESG comments resolved//FW: I-D Action: draft-ietf-i2rs-rib-data-model-12.txt

Hi, Most of the IESG comments are addressed in version 11, below is the diff from version 10 https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-rib-data-model-11 Some nits fixed in version 12, below is the diff from version 11.

Re: [i2rs] RFC 8431 on A YANG Data Model for the Routing Information Base (RIB)

Hi Alex, That's the intention, this model conforms to the NMDA architecture. Best regards, Mach > -Original Message- > From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of Alex Campbell > Sent: Thursday, September 27, 2018 7:12 AM > To: i2rs@ietf.org > Subject: Re: [i2rs] RFC 8431 on