[prev in list] [next in list] [prev in thread] [next in thread]
List: ms-ospf
Subject: Re: [Lsr] LSR meeting comment on draft-acee-lsr-ospf-transport-instance
From: "Aijun Wang" <wangaijun () tsinghua ! org ! cn>
Date: 2021-03-10 9:06:07
Message-ID: 009501d7158c$9b9e8160$d2db8420$ () tsinghua ! org ! cn
[Download RAW message or body]
This is a multipart message in MIME format.
[Attachment #2 (multipart/alternative)]
This is a multipart message in MIME format.
Hi, Authors:
I think other use case, such as 3.2 and 3.3 can also be solved by other means.
Following the direction of using different routing instances to transfer such \
information is not one feasible way.
Best Regards
Aijun Wang
China Telecom
From: lsr-bounces@ietf.org <lsr-bounces@ietf.org> On Behalf Of Uma Chunduri
Sent: Tuesday, March 9, 2021 4:48 AM
To: lsr@ietf.org
Subject: [Lsr] LSR meeting comment on draft-acee-lsr-ospf-transport-instance
Dear Authors,
Just want to quickly clarify my comment today on this draft.
We know there was a significant discussion many years ago when similar work was done \
during RFC 6822 (ISIS-MI) and RFC 6823 (GenInfo). The usefulness of this is evident \
with the more recent publication https://datatracker.ietf.org/doc/rfc8202/. I am \
certainly not in the group and would not question 'why' this is needed in OSPF.
However, section 3.1 use cases are difficult to understand and quite frankly either \
through the reference (ETSI-WP28-MEC) or the cases listed. As long as there is \
overlay in those networks (with the 3GPP preferred option expanded rapidly for \
multiple interfaces beyond N9, F1, W1 etc after REL16+) the usefulness of this core \
network and application info into the underlay and routing layer is limited and even \
more so for UEs.
So please either expand the use case (sec 3.1) to see how this is applicable or leave \
it out for future scenarios.
--
Uma C.
[Attachment #5 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:宋体;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:等线;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@等线";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"\@宋体";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:宋体;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:宋体;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:等线;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:等线;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ZH-CN link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal><span lang=EN-US \
style='font-size:10.5pt;font-family:等线;color:#1F497D'>Hi, \
Authors:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US \
style='font-size:10.5pt;font-family:等线;color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:10.5pt;font-family:等线;color:#1F497D'>I think other use case, \
such as 3.2 and 3.3 can also be solved by other means.<o:p></o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:10.5pt;font-family:等线;color:#1F497D'>Following the direction of \
using different routing instances to transfer such information is not one feasible \
way.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US \
style='font-size:10.5pt;font-family:等线;color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:10.5pt;font-family:等线;color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal style='text-align:justify;text-justify:inter-ideograph'><span \
lang=EN-US style='font-size:10.5pt;font-family:等线;color:#1F497D'>Best \
Regards<o:p></o:p></span></p><p class=MsoNormal \
style='text-align:justify;text-justify:inter-ideograph'><span lang=EN-US \
style='font-size:10.5pt;font-family:等线;color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal style='text-align:justify;text-justify:inter-ideograph'><span \
lang=EN-US style='font-size:10.5pt;font-family:等线;color:#1F497D'>Aijun \
Wang<o:p></o:p></span></p><p class=MsoNormal \
style='text-align:justify;text-justify:inter-ideograph'><span lang=EN-US \
style='font-size:10.5pt;font-family:等线;color:#1F497D'>China Telecom</span><span \
lang=EN-US style='font-size:10.5pt;font-family:等线;color:#1F497D'><o:p></o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:10.5pt;font-family:等线;color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><b><span \
lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span \
lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> \
lsr-bounces@ietf.org <lsr-bounces@ietf.org> <b>On Behalf Of </b>Uma \
Chunduri<br><b>Sent:</b> Tuesday, March 9, 2021 4:48 AM<br><b>To:</b> \
lsr@ietf.org<br><b>Subject:</b> [Lsr] LSR meeting comment on \
draft-acee-lsr-ospf-transport-instance<o:p></o:p></span></p><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span lang=EN-US>Dear \
Authors,<o:p></o:p></span></p><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span lang=EN-US>Just want to \
quickly clarify my comment today on this draft.<o:p></o:p></span></p></div><div><p \
class=MsoNormal style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span lang=EN-US>We know there \
was a significant discussion many years ago when similar work was done during \
RFC 6822 (ISIS-MI) and RFC 6823 (GenInfo). The usefulness of this is evident \
with the more recent publication <a \
href="https://datatracker.ietf.org/doc/rfc8202/">https://datatracker.ietf.org/doc/rfc8202/</a>. \
I am certainly not in the group and would not question 'why' this is needed in \
OSPF.<o:p></o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span lang=EN-US>However, \
section 3.1 use cases are difficult to understand and quite frankly either \
through the reference (</span><span lang=EN-US \
style='font-size:10.5pt;font-family:"Courier \
New";color:black;background:#FFFDF5'>ETSI-WP28-MEC)</span><span lang=EN-US> or \
the cases listed. As long as there is overlay in those networks (with the 3GPP \
preferred option expanded rapidly for multiple interfaces beyond N9, F1, W1 etc \
after REL16+) the usefulness of this core network and application info into the \
underlay and routing layer is limited and even more so for \
UEs. <o:p></o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span lang=EN-US>So please \
either expand the use case (sec 3.1) to see how this is applicable or leave it \
out for future scenarios.<o:p></o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US>--<o:p></o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span lang=EN-US>Uma \
C.<o:p></o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal \
style='margin-left:21.0pt;mso-para-margin-left:1.75gd'><span \
lang=EN-US><o:p> </o:p></span></p></div></div></div></body></html>
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic