Re: Question about Interface Groups (formerly, DPN Groups)
Charlie Perkins <[email protected]> Mon, 22 Jan 2018 10:07:17 -0800
| Newsgroups | gmane.ietf.mip6 |
|---|---|
| Message-ID | <f3582519-6b18-d62c-9e66-e0c707c6815c__6681.99143042347$1516644429$gmane$org@earthlink.net> |
This is a multi-part message in MIME format.
--===============6470624912430224135==
Content-Type: multipart/alternative;
boundary="------------CC44AF377D4F1FDB24D967DC"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------CC44AF377D4F1FDB24D967DC
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Hello Lyle,
An Interface Group on a DPN would also have have attributes for Peer
Interface Groups residing on other DPNs. So, the data plane
configuration can already exhibit the ("cross-DPN") interconnection
between Interface Groups even if the interfaces of the Group all reside
on the same DPN.
Could you give an example of an Interface Group that perforce requires
to reside on multiple DPNs? Is it a case that could be handled better
by defining a virtual DPN to host the Interface Group? I understand the
word "containment" but I'm not at all clear about what sort of Group
requires the extra complication to expedite the stated purpose, which is
DPN selection. If there are other purposes, I would be inclined to
define other structures for them that do not have the effect of
complicating the Interface Group definition.
Regards,
Charlie P.
On 1/22/2018 5:11 AM, Bertz, Lyle T [CTO] wrote:
>
> <adding mailing list>
>
> No, I don’t think they should reside under a DPN. Groups like these
> also span multiple DPNs which would make containment graphs far too
> confusing.
>
> *From:*Charlie Perkins [mailto:[email protected]]
> *Sent:* Sunday, January 21, 2018 10:51 PM
> *To:* Bertz, Lyle T [CTO] <[email protected]>
> *Cc:* Marco Liebsch <[email protected]>; Satoru Matsushima
> <[email protected]>; Sri Gundavelli (sgundave)
> <[email protected]>; Moses, Danny <[email protected]>; Weaver,
> Farni [CTO] <[email protected]>; Matsushima Satoru
> <[email protected]>
> *Subject:* Question about Interface Groups
>
> Hello folks,
>
> Can we have it so that all the Interfaces of an "Interface Group"
> (formerly, "DPN Group") reside on the same DPN?
>
> If so, I can make good sense out of the text in the document, but
> otherwise I think there are big problems.
>
> I have some other questions, but this is the main thing right now. If
> the answer to my question is "Yes" I think I will have a sensible
> revision tomorrow.
>
> I have some more questions, not quite as important, which I will put
> in separate emails.
>
> Regards,
> Charlie P.
>
> On 1/18/2018 5:26 AM, Bertz, Lyle T [CTO] wrote:
>
> Charlie,
>
> Glad to hear things are going well. I’m looking forward to your
> document update.
>
> Lyle
>
>
> ------------------------------------------------------------------------
>
> This e-mail may contain Sprint proprietary information intended for
> the sole use of the recipient(s). Any use by others is prohibited. If
> you are not the intended recipient, please contact the sender and
> delete all copies of the message.
--------------CC44AF377D4F1FDB24D967DC
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello Lyle,<br>
<br>
An Interface Group on a DPN would also have have attributes for Peer
Interface Groups residing on other DPNs. So, the data plane
configuration can already exhibit the ("cross-DPN") interconnection
between Interface Groups even if the interfaces of the Group all
reside on the same DPN.<br>
<br>
Could you give an example of an Interface Group that perforce
requires to reside on multiple DPNs? Is it a case that could be
handled better by defining a virtual DPN to host the Interface
Group? I understand the word "containment" but I'm not at all clear
about what sort of Group requires the extra complication to expedite
the stated purpose, which is DPN selection. If there are other
purposes, I would be inclined to define other structures for them
that do not have the effect of complicating the Interface Group
definition.<br>
<br>
Regards,<br>
Charlie P.<br>
<br>
<br>
<div class="moz-cite-prefix">On 1/22/2018 5:11 AM, Bertz, Lyle T
[CTO] wrote:<br>
</div>
<blockquote type="cite"
cite="mid:[email protected]">
<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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><adding
mailing list><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">No,
I don’t think they should reside under a DPN. Groups like
these also span multiple DPNs which would make containment
graphs far too confusing.
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">
Charlie Perkins [<a class="moz-txt-link-freetext" href="mailto:[email protected]">mailto:[email protected]</a>]
<br>
<b>Sent:</b> Sunday, January 21, 2018 10:51 PM<br>
<b>To:</b> Bertz, Lyle T [CTO]
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br>
<b>Cc:</b> Marco Liebsch
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a>; Satoru Matsushima
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a>; Sri Gundavelli
(sgundave) <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a>; Moses, Danny
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a>; Weaver, Farni [CTO]
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a>; Matsushima Satoru
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br>
<b>Subject:</b> Question about Interface Groups<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello folks,<br>
<br>
Can we have it so that all the Interfaces of an "Interface
Group" (formerly, "DPN Group") reside on the same DPN?<br>
<br>
If so, I can make good sense out of the text in the document,
but otherwise I think there are big problems.<br>
<br>
I have some other questions, but this is the main thing right
now. If the answer to my question is "Yes" I think I will
have a sensible revision tomorrow.<br>
<br>
I have some more questions, not quite as important, which I
will put in separate emails.<br>
<br>
Regards,<br>
Charlie P.<o:p></o:p></p>
<div>
<p class="MsoNormal">On 1/18/2018 5:26 AM, Bertz, Lyle T [CTO]
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Charlie,</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Glad
to hear things are going well. I’m looking forward to
your document update.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Lyle</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<hr>
<font size="1" face="Arial" color="Gray"><br>
This e-mail may contain Sprint proprietary information intended
for the sole use of the recipient(s). Any use by others is
prohibited. If you are not the intended recipient, please
contact the sender and delete all copies of the message.<br>
</font>
</blockquote>
<br>
</body>
</html>
--------------CC44AF377D4F1FDB24D967DC--
--===============6470624912430224135==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm
--===============6470624912430224135==--