[bess] Re: [Idr] New Version Notification for draft-hares-idr-bess-tea-templates-00.txt

2025-03-04 Thread Susan Hares 
Jeff:

Thanks for the input.   I'll add these topics to the IDR wiki page, the draft, 
and  my presentations.

Sue

From: Jeffrey Haas 
Sent: Tuesday, March 4, 2025 8:32 AM
To: Susan Hares 
Cc: BESS ; [email protected]
Subject: Re: [Idr] New Version Notification for 
draft-hares-idr-bess-tea-templates-00.txt

Thanks, Sue, for kicking this off. As usual, my input is a bit late, but 
hopefully still early enough for discussion at the upcoming session. Two 
additional topics appropriate for TEA templating that&
External ([email protected])
  Report This 
Email
  
FAQ
  GoDaddy Advanced Email Security, Powered by 
INKY

Thanks, Sue, for kicking this off.

As usual, my input is a bit late, but hopefully still early enough for 
discussion at the upcoming session.

Two additional topics appropriate for TEA templating that's come up in prior 
review:
- Route selection impacts.  This overlaps somewhat with validation.
- Attribute (in this case, contents of the TEA) escape considerations.  This 
normally overlaps in the security considerations.

-- Jeff



On Mar 3, 2025, at 3:03 PM, Susan Hares 
mailto:[email protected]>> wrote:

IDR and BESS WGs:

draft-hares-idr-bess-tea-templates provides guidance for authors
writing  text to define tunnel TLVs of Sub-TLVs for the BGP tunnel 
encapsulation attribute (TEA) [See RFC9012].

The goal behind this draft (or the web version on the IDR wiki:
(https://wiki.ietf.org/group/idr/TEA-templates)
is to help new and experience authors quickly write correct text
that has necessary information for interoperable standards.

The non-goal is to cause rewriting of good text in your drafts.

During IETF-122, I will review these guidelines (in BESS and IDR (Friday))
and provide working examples from the drafts specifying tunnels for
SR, SDWAN, NV03 (geneve), and multicast routing.

This draft is part of the IDR chairs continuing attempt to delays in
publications.

This draft comes with an offer to help write/edit text for
Tunnel TLV or Sub-TLVs for the TEA attribute.

Cheers, Sue Hares


From: [email protected] 
mailto:[email protected]>>
Sent: Monday, March 3, 2025 2:35 PM
To: Susan Hares mailto:[email protected]>>
Subject: New Version Notification for draft-hares-idr-bess-tea-templates-00.txt


A new version of Internet-Draft draft-hares-idr-bess-tea-templates-00.txt has
been successfully submitted by Susan Hares and posted to the
IETF repository.

Name: draft-hares-idr-bess-tea-templates
Revision: 00
Title:Guidance for Authors writing text for the BGP Tunnel Encapsulation 
Attribute
Date: 2025-03-03
Group:Individual Submission
Pages:10
URL:  
https://www.ietf.org/archive/id/draft-hares-idr-bess-tea-templates-00.txt
Status:   
https://datatracker.ietf.org/doc/draft-hares-idr-bess-tea-templates/
HTMLized: 
https://datatracker.ietf.org/doc/html/draft-hares-idr-bess-tea-templates


Abstract:

   The BGP (RFC4271) Tunnel Encapsulation Attribute (TEA) is defined in
   RFC9012.  Currently proposed BGP specifications in the IDR and BESS
   Working groups have defined new tunnels and new parameter

[bess] Re: [Idr] New Version Notification for draft-hares-idr-bess-tea-templates-00.txt

2025-03-04 Thread Jeffrey Haas 
Thanks, Sue, for kicking this off.

As usual, my input is a bit late, but hopefully still early enough for 
discussion at the upcoming session.

Two additional topics appropriate for TEA templating that's come up in prior 
review:
- Route selection impacts.  This overlaps somewhat with validation.
- Attribute (in this case, contents of the TEA) escape considerations.  This 
normally overlaps in the security considerations.

-- Jeff


> On Mar 3, 2025, at 3:03 PM, Susan Hares  wrote:
> 
> IDR and BESS WGs:
>  
> draft-hares-idr-bess-tea-templates provides guidance for authors
> writing  text to define tunnel TLVs of Sub-TLVs for the BGP tunnel 
> encapsulation attribute (TEA) [See RFC9012].
>  
> The goal behind this draft (or the web version on the IDR wiki:
> (https://wiki.ietf.org/group/idr/TEA-templates 
> )
> is to help new and experience authors quickly write correct text
> that has necessary information for interoperable standards.
>  
> The non-goal is to cause rewriting of good text in your drafts.
>  
> During IETF-122, I will review these guidelines (in BESS and IDR (Friday))
> and provide working examples from the drafts specifying tunnels for
> SR, SDWAN, NV03 (geneve), and multicast routing.  
>  
> This draft is part of the IDR chairs continuing attempt to delays in
> publications.  
>  
> This draft comes with an offer to help write/edit text for
> Tunnel TLV or Sub-TLVs for the TEA attribute.
>  
> Cheers, Sue Hares 
>  
>  
> From: [email protected]  
> mailto:[email protected]>> 
> Sent: Monday, March 3, 2025 2:35 PM
> To: Susan Hares mailto:[email protected]>>
> Subject: New Version Notification for 
> draft-hares-idr-bess-tea-templates-00.txt
>  
>  
> A new version of Internet-Draft draft-hares-idr-bess-tea-templates-00.txt has
> been successfully submitted by Susan Hares and posted to the
> IETF repository.
>  
> Name: draft-hares-idr-bess-tea-templates
> Revision: 00
> Title:Guidance for Authors writing text for the BGP Tunnel Encapsulation 
> Attribute
> Date: 2025-03-03
> Group:Individual Submission
> Pages:10
> URL:  
> https://www.ietf.org/archive/id/draft-hares-idr-bess-tea-templates-00.txt 
> 
> Status:   
> https://datatracker.ietf.org/doc/draft-hares-idr-bess-tea-templates/ 
> 
> HTMLized: 
> https://datatracker.ietf.org/doc/html/draft-hares-idr-bess-tea-templates 
> 
>  
>  
> Abstract:
>  
>The BGP (RFC4271) Tunnel Encapsulation Attribute (TEA) is defined in
>RFC9012.  Currently proposed BGP specifications in the IDR and BESS
>Working groups have defined new tunnels and new parameters for these
>tunnels in Sub-TLV.  The Segment Routing usage of the TEA has
>suggested a number of new Sub-TLVs.  This document provides
>guidelines to help authors quickly write correct text for new tunnels
>(defined in tunnel TLVs) and new Sub-TLVs.  These guidelines are
>given as "templates" to aid new authors.  More experience authors
>should view these templates as a list of expected content.
>  
>One additional challenge for tunnels using the PMSI tunnels is to
>carefully define the interaction between PMSI tunnels and TEA
>tunnels.
>  
>  
>  
> The IETF Secretariat
>  
>  
> ___
> Idr mailing list -- [email protected] 
> To unsubscribe send an email to [email protected] 
___
BESS mailing list -- [email protected]
To unsubscribe send an email to [email protected]