Hi, Mohamed:

 

Let’s focus on the technical arguments:

 

“Since adherence of TLVs to the MP-TLV procedures is now made explicit, the 
processing at the receiving router is thus more determinist.”

 

But the argument point of the thread is that the Unlimited Boundary of MP-TLV 
will cause potential memory crash of the receiver, which is one added security 
attack vector. 

The document should provide some mitigate suggestions on such issue, not 
instead of making it vague, or emphasize the opposite.

 

The IESG is the final step to evaluate the document, and I am glad to know you 
have read my summary unsolved challenges draft 
https://datatracker.ietf.org/doc/draft-wang-lsr-unsolved-challenge-of-mp-tlv/

To make the discussion more constructive, I would like to hear your Explicit 
Responses to the “unsolved challenges”( I have summarized them also in another 
thread to the IESG).

 

The Clear and Explicit Responses will help also the other IESG experts to 
evaluate this document in more neutral way, and will also benefit the IETF 
community.

The IESG experts’ review should focus on the technical review and arguments, 
not the Editor’s review which will be done by the RFC editor later.

 

 

Best Regards

 

Aijun Wang

China Telecom

 

发件人: mohamed.boucad...@orange.com [mailto:mohamed.boucad...@orange.com] 
发送时间: 2025年3月31日 13:51
收件人: Aijun Wang <wangai...@tsinghua.org.cn>; 'Robert Raszuk' 
<rob...@raszuk.net>; 'Tony Li' <tony...@tony.li>; 'Les Ginsberg' 
<ginsb...@cisco.com>
抄送: 'The IESG' <i...@ietf.org>; draft-ietf-lsr-multi-...@ietf.org; 'lsr-chairs' 
<lsr-cha...@ietf.org>; 'lsr' <lsr@ietf.org>; 'Yingzhen Qu' 
<yingzhen.i...@gmail.com>
主题: RE: [Lsr] Re: Mohamed Boucadair's Yes on draft-ietf-lsr-multi-tlv-11: (with 
COMMENT)

 

Hi Aijun, 

 

Let’s me first remind some basics:

*       Being unrespectful is not a technical argument
*       Repeating the same argument does not strengthen that argument (*) 
*       The IESG review is still ongoing

 

Please keep that in mind for your future postings to maintain this discussion 
constructive as it was till now. Thank you.

 

Now back to the excerpt you quoted below. The argument made by the authors to 
my comment is: Since adherence of TLVs to the MP-TLV procedures is now made 
explicit, the processing at the receiving router is thus more determinist.

 

Cheers,

Med

 

(*)I read your two drafts draft-wang-lsr-isis-big-tlv and 
draft-wang-lsr-unsolved-challenge-of-mp-tlv.

 

De : Aijun Wang <wangai...@tsinghua.org.cn <mailto:wangai...@tsinghua.org.cn> > 
Envoyé : lundi 31 mars 2025 03:03
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com 
<mailto:mohamed.boucad...@orange.com> >; 'Robert Raszuk' <rob...@raszuk.net 
<mailto:rob...@raszuk.net> >; 'Tony Li' <tony...@tony.li 
<mailto:tony...@tony.li> >; 'Les Ginsberg' <ginsb...@cisco.com 
<mailto:ginsb...@cisco.com> >
Cc : 'The IESG' <i...@ietf.org <mailto:i...@ietf.org> >; 
draft-ietf-lsr-multi-...@ietf.org <mailto:draft-ietf-lsr-multi-...@ietf.org> ; 
'lsr-chairs' <lsr-cha...@ietf.org <mailto:lsr-cha...@ietf.org> >; 'lsr' 
<lsr@ietf.org <mailto:lsr@ietf.org> >; 'Yingzhen Qu' <yingzhen.i...@gmail.com 
<mailto:yingzhen.i...@gmail.com> >
Objet : 答复: [Lsr] Re: Mohamed Boucadair's Yes on draft-ietf-lsr-multi-tlv-11: 
(with COMMENT)

 

 

The update version 13, just make the following unsupported declaration:

 


Note that support for MP-TLV may result in an implementation being

        more robust in handling unexpected occurrences of MP-TLV.

 

There are more untrue and contrary descriptions within the revision document 
after the IESG expert’s review.

It’s so ridiculous.

 

Best Regards

 

Aijun Wang

China Telecom

 

 

发件人: forwardingalgori...@ietf.org <mailto:forwardingalgori...@ietf.org>  
[mailto:forwardingalgori...@ietf.org] 代表 mohamed.boucad...@orange.com 
<mailto:mohamed.boucad...@orange.com> 
发送时间: 2025年3月29日 16:41
收件人: Robert Raszuk <rob...@raszuk.net <mailto:rob...@raszuk.net> >; Tony Li 
<tony...@tony.li <mailto:tony...@tony.li> >; Les Ginsberg <ginsb...@cisco.com 
<mailto:ginsb...@cisco.com> >
抄送: The IESG <i...@ietf.org <mailto:i...@ietf.org> >; 
draft-ietf-lsr-multi-...@ietf.org <mailto:draft-ietf-lsr-multi-...@ietf.org> ; 
lsr-chairs <lsr-cha...@ietf.org <mailto:lsr-cha...@ietf.org> >; lsr 
<lsr@ietf.org <mailto:lsr@ietf.org> >; Yingzhen Qu <yingzhen.i...@gmail.com 
<mailto:yingzhen.i...@gmail.com> >
主题: [Lsr] Re: Mohamed Boucadair's Yes on draft-ietf-lsr-multi-tlv-11: (with 
COMMENT)

 

Hi Les, all, 

 

First, I confirm that my comment was exactly how Rob interpreted it, not what 
was in Les example :-)

 

Putting that aside, I hear the argument raised by Tony and Chris. I consider 
the pending comment close. 

 

Les, I checked -13 and I’m fine with it. Thanks for the reactivity and for 
accommodating.

 

Thank you all for the constructive discussion.

 

Cheers,

Med

 

De : Robert Raszuk <rob...@raszuk.net <mailto:rob...@raszuk.net> > 
Envoyé : samedi 29 mars 2025 01:24
À : Tony Li <tony...@tony.li <mailto:tony...@tony.li> >
Cc : Les Ginsberg <ginsb...@cisco.com <mailto:ginsb...@cisco.com> >; BOUCADAIR 
Mohamed INNOV/NET <mohamed.boucad...@orange.com 
<mailto:mohamed.boucad...@orange.com> >; The IESG <i...@ietf.org 
<mailto:i...@ietf.org> >; draft-ietf-lsr-multi-...@ietf.org 
<mailto:draft-ietf-lsr-multi-...@ietf.org> ; lsr-chairs <lsr-cha...@ietf.org 
<mailto:lsr-cha...@ietf.org> >; lsr <lsr@ietf.org <mailto:lsr@ietf.org> >; 
Yingzhen Qu <yingzhen.i...@gmail.com <mailto:yingzhen.i...@gmail.com> >
Objet : Re: [Lsr] Mohamed Boucadair's Yes on draft-ietf-lsr-multi-tlv-11: (with 
COMMENT)

 

 

Hi Tony,

 

Ok so the answer here is that since we have no upper bounds today on the number 
of atomic TLVs just the fact that we go one level down and allow grouping 
single TLV type into multiple parts causes not a significant risk one should 
worry about. 

 

If this is the answer I rest my case :) 

 

Thx,

R.

 

 

 

On Sat, Mar 29, 2025 at 1:16 AM Tony Li <tony...@tony.li 
<mailto:tony...@tony.li> > wrote:


Hi Robert,

> Sorry if I was not very clear but my point was that MP-TLV may be coming in 
> multiple LSPs - something which to the best of my understanding is not the 
> case today with any TLV type. On that basis as LSP length natural boundary is 
> gone it seems sky is the limit now. 


This is incorrect.  A TLV may appear in many different framgments.  For 
example, a router may have multiple adjacencies.  These may be spread out 
across fragments.

T

____________________________________________________________________________________________________________
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.
____________________________________________________________________________________________________________
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.
_______________________________________________
Lsr mailing list -- lsr@ietf.org
To unsubscribe send an email to lsr-le...@ietf.org

Reply via email to