Med,

I can't find sections in the  
draft-ietf-opsawg-teas-attachment-circuit-03<https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-teas-attachment-circuit-03#name-connecting-a-virtualized-en>
  on the  Notification when BGP peers detecting Capability mismatch or  maximum 
routes exceeding. Will you add more?

Thanks, Linda

From: Linda Dunbar
Sent: Friday, December 8, 2023 2:02 PM
To: [email protected]; RTGWG ([email protected]) <[email protected]>; 
[email protected]
Subject: RE: WGLC for draft-ietf-rtgwg-net2cloud-problem-statement

Med,

Some questions to your suggestion:
You suggested referencing the 
draft-ietf-opsawg-teas-attachment-circuit-03<https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-teas-attachment-circuit-03#name-connecting-a-virtualized-en>
 for the following issues.
Section 3.1 Increased BGP Peering Errors and Mitigation Methods

Cloud DCs support more BGP peering than conventional ISPs, which can contribute 
to increased BGP peering errors such as capability mismatch, unwanted route 
leaks, missing Keepalives, and errors causing BGP ceases. Capability mismatch 
can cause BGP sessions not to be adequately established. Those issues are more 
acute to Cloud DCs than they have traditionally been, even though they may 
apply to conventional ISPs, just to a lesser degree.

Are you saying that Cloud customers using YANG to configure the BGP sessions 
are less prone to the  BGP peering errors identified above?

Thanks, Linda


From: [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>>
Sent: Thursday, December 7, 2023 4:54 AM
To: RTGWG ([email protected]<mailto:[email protected]>) 
<[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Subject: Re: WGLC for draft-ietf-rtgwg-net2cloud-problem-statement

Hi all,

FWIW, please find below my review to this document:


  *   pdf: 
https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-rtgwg-net2cloud-problem-statement-30-rev%20Med.pdf
  *   doc: 
https://github.com/boucadair/IETF-Drafts-Reviews/edit/master/draft-ietf-rtgwg-net2cloud-problem-statement-30-rev%20Med.doc

Feel free to grab whatever useful in the review.

I support advancing this spec assuming key points of the review are addressed.

Cheers,
Med

From: Jeff Tantsura <[email protected]<mailto:[email protected]>>
Sent: Tuesday, December 5, 2023 3:44 PM
To: RTGWG <[email protected]<mailto:[email protected]>>
Cc: rtgwg-chairs <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Subject: WGLC for draft-ietf-rtgwg-net2cloud-problem-statement

Dear RTGWG,

The authors have requested the RTGWG to last call the 
draft-ietf-rtgwg-net2cloud-problem-statement draft.

The authors have addressed all the comments received from the early reviews and 
shepherd (thanks Joel!).
Please indicate support or no-support by December 20 2023.

IPR:
If you are listed as a document author or contributor and haven't responded to 
the IPR call, please respond to this
email of whether or not you are aware of any relevant IPR.
The response needs to be sent to the RTGWG mailing list.
The document will not advance to the next stage until a response has been 
received from each author and each individual that has contributed to the 
document.

Thanks,
Yingzhen and Jeff

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg

Reply via email to