[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mpls
Subject:    Re: [mpls] [E] RE: Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators
From:       "Jalil, Luay" <luay.jalil=40verizon.com () dmarc ! ietf ! org>
Date:       2022-06-10 13:41:44
Message-ID: CAO8-O7oqvdN56vNv+V0rRi=Vi53yDdhtPaog8AMQU+TO7Dtywg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


To follow up on Bruno's comments/questions, I think we need further
clarifications. Example: I saw a note against option-2 because it will
break current implementations but is that the case?

Thanks,
*Luay*


On Wed, Jun 8, 2022 at 11:34 AM <bruno.decraene@orange.com> wrote:

> Hi Loa,
> 
> I have a clarification question on the below poll, regarding the extension
> of the ELI bSPL.
> 
> Is the scope of the question specific to the MPLS Network Actions (MNA)
> framework?
> Or is the scope more general and include any extension of the ELI bSPL and
> in particular applies to draft [1]?
> 
> [1]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft- \
> 2Ddecraene-2Dmpls-2Dslid-2Dencoded-2Dentropy-2Dlabel-2Did_&d=DwIFAg&c=udBTRvFvXC5Dhq \
> g7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&m=x3v0MK \
> H1xgizJ7PZXaUMAHZ3m-SlLAkX9S2ThME68Hj8igr7oX82Vml_Ug8nBNOM&s=8sfIrVrjur--cXiz35I-e-oBUmwQ5MZFtZqy-6qtu94&e=
>  
> Thanks,
> Regards,
> --Bruno
> 
> Orange Restricted
> 
> -----Original Message-----
> From: mpls <mpls-bounces@ietf.org> On Behalf Of Loa Andersson
> Sent: Monday, May 30, 2022 11:22 PM
> To: mpls@ietf.org
> Cc: mpls-chairs@ietf.org; pals-chairs@ietf.org; DetNet Chairs <
> detnet-chairs@ietf.org>
> Subject: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network
> Action Indicators
> 
> MPLS Working Group, MPLS Open DT,
> 
> The MPLS Network Actions (MNA) framework requires a method of indicating
> the presence of a Network Action and any Ancillary Data.
> 
> Is the consensus of the working group that we do this by:
> 
> (1) allocating a new SPL for Network Action Indicators?
> 
> (2) re-purposing the ELI SPL?
> 
> (3) using some other method of indicating this such as making it an
> additional property of an ordinary label?
> 
> Please respond to the MPLS WG mail list.
> 
> Loa Andersson
> for the Open DT wg chairs
> 
> --
> Loa Andersson                        email: loa@pi.nu
> Senior MPLS Expert                          loa.pi.nu@gmail.com
> Bronze Dragon Consulting             phone: +46 739 81 21 64
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> 
> www.ietf.org_mailman_listinfo_m" rel="nofollow">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_m> \
> pls&d=DwIFAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1Z \
> yHQXQly5fgCsWF0VTh7o&m=x3v0MKH1xgizJ7PZXaUMAHZ3m-SlLAkX9S2ThME68Hj8igr7oX82Vml_Ug8nBNOM&s=QHgUyv-vdnaMYsdlQT_ggsG_SBMFtlw4d053DQ1ftUg&e=
>  
> 
> _________________________________________________________________________________________________________________________
>  
> 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.
> 
> 


[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_default" \
style="font-family:arial,sans-serif;font-size:small">To follow up on Bruno&#39;s \
comments/questions, I think we need further clarifications. Example: I saw a note \
against option-2 because it will break current implementations but is that the \
case?</div><div class="gmail_default" \
style="font-family:arial,sans-serif;font-size:small"><br></div><div \
class="gmail_default" \
style="font-family:arial,sans-serif;font-size:small">Thanks,</div><div><div dir="ltr" \
class="gmail_signature" data-smartmail="gmail_signature"><div \
dir="ltr"><div><b>Luay</b></div></div></div></div><br></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 8, 2022 at 11:34 AM \
&lt;<a href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Loa,<br> <br>
I have a clarification question on the below poll, regarding the extension of the ELI \
bSPL.<br> <br>
Is the scope of the question specific to the MPLS Network Actions (MNA) \
framework?<br> Or is the scope more general and include any extension of the ELI bSPL \
and in particular applies to draft [1]?<br> <br>
[1] <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org \
_doc_draft-2Ddecraene-2Dmpls-2Dslid-2Dencoded-2Dentropy-2Dlabel-2Did_&amp;d=DwIFAg&amp \
;c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&amp;r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fg \
CsWF0VTh7o&amp;m=x3v0MKH1xgizJ7PZXaUMAHZ3m-SlLAkX9S2ThME68Hj8igr7oX82Vml_Ug8nBNOM&amp;s=8sfIrVrjur--cXiz35I-e-oBUmwQ5MZFtZqy-6qtu94&amp;e=" \
rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=https-3A__ \
datatracker.ietf.org_doc_draft-2Ddecraene-2Dmpls-2Dslid-2Dencoded-2Dentropy-2Dlabel-2D \
id_&amp;d=DwIFAg&amp;c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&amp;r=k0DrrBeS0St-D \
1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&amp;m=x3v0MKH1xgizJ7PZXaUMAHZ3m-SlLAkX9S2ThME68Hj8igr7oX82Vml_Ug8nBNOM&amp;s=8sfIrVrjur--cXiz35I-e-oBUmwQ5MZFtZqy-6qtu94&amp;e=</a> \
<br> <br>
Thanks,<br>
Regards,<br>
--Bruno<br>
<br>
Orange Restricted<br>
<br>
-----Original Message-----<br>
From: mpls &lt;<a href="mailto:mpls-bounces@ietf.org" \
                target="_blank">mpls-bounces@ietf.org</a>&gt; On Behalf Of Loa \
                Andersson<br>
Sent: Monday, May 30, 2022 11:22 PM<br>
To: <a href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a><br>
Cc: <a href="mailto:mpls-chairs@ietf.org" target="_blank">mpls-chairs@ietf.org</a>; \
<a href="mailto:pals-chairs@ietf.org" target="_blank">pals-chairs@ietf.org</a>; \
DetNet Chairs &lt;<a href="mailto:detnet-chairs@ietf.org" \
                target="_blank">detnet-chairs@ietf.org</a>&gt;<br>
Subject: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action \
Indicators<br> <br>
MPLS Working Group, MPLS Open DT,<br>
<br>
The MPLS Network Actions (MNA) framework requires a method of indicating <br>
the presence of a Network Action and any Ancillary Data.<br>
<br>
Is the consensus of the working group that we do this by:<br>
<br>
     (1) allocating a new SPL for Network Action Indicators?<br>
<br>
     (2) re-purposing the ELI SPL?<br>
<br>
     (3) using some other method of indicating this such as making it an<br>
           additional property of an ordinary label?<br>
<br>
Please respond to the MPLS WG mail list.<br>
<br>
Loa Andersson<br>
for the Open DT wg chairs<br>
<br>
-- <br>
Loa Andersson                                    email: <a href="mailto:loa@pi.nu" \
target="_blank">loa@pi.nu</a><br> Senior MPLS Expert                                  \
<a href="mailto:loa.pi.nu@gmail.com" target="_blank">loa.pi.nu@gmail.com</a><br> \
Bronze Dragon Consulting                    phone: +46 739 81 21 64<br> <br>
_______________________________________________<br>
mpls mailing list<br>
<a href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a><br>
<a href="www.ietf.org_mailman_lis" rel="nofollow">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_lis> \
tinfo_mpls&amp;d=DwIFAg&amp;c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&amp;r=k0DrrB \
eS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&amp;m=x3v0MKH1xgizJ7PZXaUMAHZ3m-SlLAkX9S2ThME68Hj8igr7oX82Vml_Ug8nBNOM&amp;s=QHgUyv-vdnaMYsdlQT_ggsG_SBMFtlw4d053DQ1ftUg&amp;e=" \
rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=https-3A__ \
www.ietf.org_mailman_listinfo_mpls&amp;d=DwIFAg&amp;c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxp \
b6__0PomBTQ&amp;r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&amp;m=x3v0MKH1xgizJ7PZXa \
UMAHZ3m-SlLAkX9S2ThME68Hj8igr7oX82Vml_Ug8nBNOM&amp;s=QHgUyv-vdnaMYsdlQT_ggsG_SBMFtlw4d053DQ1ftUg&amp;e=</a> \
<br> <br>
_________________________________________________________________________________________________________________________<br>
 <br>
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc<br> pas etre diffuses, exploites ou copies sans \
autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<br> a \
l&#39;expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d&#39;alteration,<br> Orange decline toute \
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<br> <br>
This message and its attachments may contain confidential or privileged information \
that may be protected by law;<br> they should not be distributed, used or copied \
without authorisation.<br> If you have received this email in error, please notify \
the sender and delete this message and its attachments.<br> As emails may be altered, \
Orange is not liable for messages that have been modified, changed or falsified.<br> \
Thank you.<br> <br>
</blockquote></div>



_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic