A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.
Title : IPv6-Only PE Design for IPv4-NLRI with IPv6-NH
Authors : Gyan Mishra
Hi Loa,
We changed the draft’s name before posting it at the very last minute and I
failed to update the chairs/Mankamana with the new name for the agenda.
My apologies for that. The agenda should list this one instead:
draft-sr-bess-evpn-vpws-gateway-00
I see now Loa,
Agreed the draft name is missing gateway!
Thanks,
Sami
From: Loa Andersson
Date: Sunday, March 20, 2022 at 6:57 PM
To: Boutros, Sami , BESS ,
bess-cha...@ietf.org
Cc: bess-...@ietf.org
Subject: Re: [bess] [**EXTERNAL**] can't find a document that is listed
Sami,
That might
Sami,
That might be the be the draft intended, but the agenda lists
draft-sr-bess-interconnect-evpn-vpws-00
which is another (non-existing) draft.
Might be a good idea if the chairs updated the agenda, But I still think
this don't leave enough time to prepare.
/Loa
On 2022-03-21 01:14,
Actually the draft is there.
https://datatracker.ietf.org/doc/html/draft-sr-bess-evpn-vpws-gateway-00.html
Thanks,
Sami
From: BESS on behalf of Loa Andersson
Date: Sunday, March 20, 2022 at 7:11 AM
To: BESS , bess-cha...@ietf.org
Cc: bess-...@ietf.org
Subject: [**EXTERNAL**] [bess] can't
I have reread the draft. let me try asking the quesiton the opposite way.
1) If the argument length is zero, then an Ingress PE will always ignore
the SRv6 Endpoint behavior, as it will not do anything differently if it
understands or does not understand the behavior.
2) If the argument
Hi Yubao,
Your questions have nothing to do with the changes in the new version. Your
question relates to aspects that have been clarified from a very early
version of the document.
https://datatracker.ietf.org/doc/html/draft-ietf-bess-srv6-services-13#section-3.2.1
BGP speakers that do not
Hi Joel,
Please see inline below.
On Sun, Mar 20, 2022 at 11:34 AM Joel M. Halpern
wrote:
> I seem to be missing something.
>
> The ingress PE (domain edge) applies the destination SID (possibly as
> part of a SID list). Either it is deciding to use the destination SID,
> or something else is
Hi Ketan,
Thanks for your clarification. It's very clear now in that update.
After read the new version, now I have other questions:
When an ASBR receives a L3VPN route along with an implicit-null MPLS label,
and that ASBR doesn't recognize the SRv6-specific TLVs,
Is there a risk
BESS Working Group, BESS chairs,
On the agenda for the BESS meeting at IETF 113, the first draft to be
discussed is listed as:
draft-sr-bess-interconnect-evpn-vpws-00
However looking at bess wg page and search the data tracker I can't find
the document. It looks like it was never posted.
I seem to be missing something.
The ingress PE (domain edge) applies the destination SID (possibly as
part of a SID list). Either it is deciding to use the destination SID,
or something else is deciding to use the destination SID.
Ignoring the issue of argument manipulation, if the Ingress
11 matches
Mail list logo
