Ali,
The reverted text looks good. Thank you.
Wen
Juniper Business Use Only
From: Ali Sajassi (sajassi)
Date: Tuesday, June 4, 2024 at 1:27 AM
To: Wen Lin , Ali Sajassi (sajassi)
, Luc André Burdet
, bess@ietf.org
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
the value of an IPv4 address.”
Cheers,
Ali
From: Wen Lin
Date: Monday, June 3, 2024 at 6:26 PM
To: Ali Sajassi (sajassi) , Luc André
Burdet , Ali Sajassi (sajassi) ,
bess@ietf.org
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
@ Luc, Thanks for the link.
@Ali
3, 2024 at 11:31 AM
To: Luc André Burdet , Wen Lin , Ali
Sajassi (sajassi) , bess@ietf.org
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
[External Email. Be cautious of content]
Luc,
That is the matter of implementation and in standards we don’t specify how
caused some confusion because of getting into a specific implementation.
Cheers,
Ali
From: Luc André Burdet
Date: Monday, June 3, 2024 at 6:08 AM
To: Wen Lin , Ali Sajassi (sajassi)
, Ali Sajassi (sajassi)
, bess@ietf.org
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
Hi
| Cisco | laburdet.i...@gmail.com | Tel: +1 613 254 4814
From: Wen Lin
Date: Thursday, May 30, 2024 at 23:31
To: Ali Sajassi (sajassi) , Ali Sajassi (sajassi)
, bess@ietf.org
Subject: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
Hi Ali,
Thank you for the investigation. I think it wil
,
Wen
Juniper Business Use Only
From: Ali Sajassi (sajassi)
Date: Thursday, May 30, 2024 at 11:13 PM
To: Wen Lin , Ali Sajassi (sajassi)
, bess@ietf.org
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
[External Email. Be cautious of content]
Hi Wen,
Both texts say
, Ali Sajassi (sajassi)
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
Hi Ali,
Thanks for your explanation.
To illustrate the differences between RFC7432 and RFC7432-bis, I have included
excerpts from both documents below. To constructing an ordered list under
n Lin , bess@ietf.org , Ali Sajassi
(sajassi)
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
[External Email. Be cautious of content]
Hi Wen,
The text in RFC7432bis for section 8.5 is basically a clarification to RFC7432
and has been around for several years (i.e., in
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
Hi Ali,
Under RFC7432, the ordered list used for electing the DF/BDF is formed based
solely on the numerical value of each router’s IP address, the originating
router’s IP address. RFC7432-bis introduces a refinement, i.e
on RFC7432 and others based on RFC7432-bis.
Thanks,
Wen
Juniper Business Use Only
From: Ali Sajassi (sajassi)
Date: Wednesday, May 29, 2024 at 11:48 PM
To: Wen Lin , bess@ietf.org ,
i-d-annou...@ietf.org
Cc: bess@ietf.org
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
with different address
families.
Cheers,
Ali
From: Wen Lin
Date: Wednesday, May 29, 2024 at 12:47 PM
To: Ali Sajassi (sajassi) , bess@ietf.org ,
i-d-annou...@ietf.org
Cc: bess@ietf.org
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
Hi Ali,
Thank you for providing
address families.
Thanks,
Wen
Juniper Business Use Only
From: Ali Sajassi (sajassi)
Date: Wednesday, May 15, 2024 at 1:55 PM
To: Wen Lin , bess@ietf.org ,
i-d-annou...@ietf.org
Cc: bess@ietf.org
Subject: Re: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
[External Email. Be cautious
: I-D Action: draft-ietf-bess-rfc7432bis-09.txt
Thank you for the updated draft.
I think we need to explicitly specify how we set the Originating Router’s IP
address – when it will be to IPv6 or IPv4 address for both Ethernet Segment
Route and Inclusive Multicast Ethernet Tag Route. Today
Thank you for the updated draft.
I think we need to explicitly specify how we set the Originating Router’s IP
address – when it will be to IPv6 or IPv4 address for both Ethernet Segment
Route and Inclusive Multicast Ethernet Tag Route. Today, there is no
mentioning about it in the draft.
7.4.
14 matches
Mail list logo
