gmane.ietf.idr archive

384 archived articles, newest first (page 4 of 4). Latest articles →

Re: 答复: draft-li-idr-flowspec-rpd- 05.txt - WG Adoption call (10/14 to 10/28/201 9)
Mon, 28 Oct 2019 01:02:05 +0000
Huaimo Chen <[email protected]> • #18657
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Sun, 27 Oct 2019 10:25:46 -0700
Uma Chunduri <[email protected]> • #18656
回复: 答复: draft-li-idr-flowsp ec-rpd-05.txt - WG Adoption call (10/14 to 10 /28/2019)
Sun, 27 Oct 2019 14:43:20 +0800
"Zhuyq" <[email protected]> • #18655
答复: draft-li-idr-flowspec-rpd- 05.txt - WG Adoption call (10/14 to 10/28/201 9) -
Sat, 26 Oct 2019 21:00:00 +0000
"Chengli (Cheng Li)" <[email protected]> • #18654
Re: 答复: 答复: draft-li-idr-flowsp ec-rpd-05.txt - WG Adoption call (10/14 to 10 /28/2019)
Sat, 26 Oct 2019 10:29:36 -0400
"Susan Hares" <[email protected]> • #18653
答复: 答复: draft-li-idr-flowsp ec-rpd-05.txt - WG Adoption call (10/14 to 10 /28/2019)
Sat, 26 Oct 2019 08:23:15 +0000
Haoweiguo <[email protected]> • #18652
答复: draft-li-idr-flowspec-rpd- 05.txt - WG Adoption call (10/14 to 10/28/201 9)
Sat, 26 Oct 2019 08:20:15 +0000
Wenhuizhi <[email protected]> • #18651
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Sat, 26 Oct 2019 07:43:03 +0000
wangzitao <[email protected]> • #18650
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Sat, 26 Oct 2019 06:39:54 +0000
"Dongjie (Jimmy)" <[email protected]> • #18649
Re: WG Last Call IPR call - draft-ietf-idr-eag-distribution-09.txt
Fri, 25 Oct 2019 22:15:57 -0700
Jeff Tantsura <[email protected]> • #18648
Re: WG Last Call IPR call - draft-ietf-idr-eag-distribution-09.txt
Sat, 26 Oct 2019 03:51:54 +0000
wangzitao <[email protected]> • #18647
Re: WG Last Call IPR call - draft-ietf-idr-eag-distribution-09.txt
Sat, 26 Oct 2019 00:37:07 +0000
Qin Wu <[email protected]> • #18646
idr - Requested sessions have been scheduled for IETF 106
Fri, 25 Oct 2019 14:11:59 -0700
"\"IETF Secretariat\"" <[email protected]> • #18645
Re: WG LG - IPR call - draft-ietf-idr-flowspec-path-redirect-09.txt (10/25 to 11/15/2019).
Fri, 25 Oct 2019 13:11:41 -0700
Arjun Sreekantiah <[email protected]> • #18644
答复: Adoption: draft-li-idr-bgp -ls-sr-policy-path-segment-03.txt and draft-l i-sr-policy-path-segment-01.txt - 1 week exte nsion [10/14 to 10/21/2019]
Fri, 25 Oct 2019 19:55:53 +0000
"Chengli (Cheng Li)" <[email protected]> • #18643
IDR Status - delta - 10/23/2019
Fri, 25 Oct 2019 12:10:19 -0400
"Susan Hares" <[email protected]> • #18642
draft-ietf-idr-rfc8203bis-05 - Just a few nits before submission.
Fri, 25 Oct 2019 11:33:33 -0400
"Susan Hares" <[email protected]> • #18641
WG Last Call IPR call - draft-ietf-idr-eag-distribution-09.txt
Fri, 25 Oct 2019 11:16:30 -0400
"Susan Hares" <[email protected]> • #18640
Re: WG LG - IPR call - draft-ietf-idr-flowspec-path-redirect-09.txt (10/25 to 11/15/2019).
Fri, 25 Oct 2019 15:13:02 +0000
"Acee Lindem (acee)" <[email protected]> • #18639
WG LG - IPR call - draft-ietf-idr-flowspec-path-redirect-09.txt (10/25 to 11/15/2019).
Fri, 25 Oct 2019 11:02:37 -0400
"Susan Hares" <[email protected]> • #18638
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019) -
Fri, 25 Oct 2019 10:51:21 -0400
"Susan Hares" <[email protected]> • #18637
Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
Fri, 25 Oct 2019 10:33:15 -0400
"Susan Hares" <[email protected]> • #18636
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Fri, 25 Oct 2019 09:25:24 +0000
"Xiejingrong (Jingrong)" <[email protected]> • #18635
答复: draft-li-idr-flowspec-rpd- 05.txt - WG Adoption call (10/14 to 10/28/201 9)
Fri, 25 Oct 2019 17:02:49 +0800
"Aijun Wang" <[email protected]> • #18634
RFC 8654 on Extended Message Support for BGP
Thu, 24 Oct 2019 16:15:40 -0700 (PDT)
[email protected] • #18633
Re: [GROW] [Sidrops] Deprecation of AS_SET and AS_CONFED_SET -- feedback requested
Thu, 24 Oct 2019 16:38:14 -0400
Warren Kumari <[email protected]> • #18632
Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
Thu, 24 Oct 2019 11:06:38 -0400
"Susan Hares" <[email protected]> • #18631
draft-dunbar-idr-sdwan-port-safi: One SDWAN Port property advertisement per BGP UPDATE or multiple Ports property packed in one BGP UPDATE ?
Thu, 24 Oct 2019 14:58:33 +0000
Linda Dunbar <[email protected]> • #18630
Re: Solicit feedback to BGP UPDATE encoding options for SDWAN WAN port properties propagation among SDWAN edges (pros & cons to draft-dunbar-idr-sdwan-port-safi and alternatives)
Thu, 24 Oct 2019 06:11:02 +0000
"Wanghaibo (Rainsword)" <[email protected]> • #18629
Re: Solicit feedback to BGP UPDATE encoding options for SDWAN WAN port properties propagation among SDWAN edges (pros & cons to draft-dunbar-idr-sdwan-port-safi and alternatives)
Wed, 23 Oct 2019 20:51:56 +0000
Linda Dunbar <[email protected]> • #18628
Re: [Sidrops] [GROW] Deprecation of AS_SET and AS_CONFED_SET -- feedback requested
Wed, 23 Oct 2019 14:20:21 -0400
Jeffrey Haas <[email protected]> • #18627
Re: [GROW] [Sidrops] Deprecation of AS_SET and AS_CONFED_SET -- feedback requested
Wed, 23 Oct 2019 15:45:17 +0000
"Sriram, Kotikalapudi \(Fed\)" <[email protected]> • #18626
Re: Is the SR Policy SAFI described in draft-ietf-idr-segment-routing-te-policy-07 under the MP-NLRI (code =14) or under the Tunnel Path attribute (code = 23)?
Wed, 23 Oct 2019 14:40:17 +0000
Linda Dunbar <[email protected]> • #18625
Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
Wed, 23 Oct 2019 09:09:12 +0000
Shraddha Hegde <[email protected]> • #18624
Re: Is the SR Policy SAFI described in draft-ietf-idr-segment-routing-te-policy-07 under the MP-NLRI (code =14) or under the Tunnel Path attribute (code = 23)?
Wed, 23 Oct 2019 11:05:17 +0200
stefano previdi <[email protected]> • #18623
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Tue, 22 Oct 2019 22:15:09 -0400
Robert Raszuk <[email protected]> • #18622
Is the SR Policy SAFI described in draft-ietf-idr-segment-routing-te-policy-07 under the MP-NLRI (code =14) or under the Tunnel Path attribute (code = 23)?
Tue, 22 Oct 2019 23:23:53 +0000
Linda Dunbar <[email protected]> • #18621
Re: are the Tunnel Encap Attribute in a BGP UPDATE applicable to all the NLRI listed in the MP_REACH_NLRI path attribute?
Tue, 22 Oct 2019 20:37:02 +0000
John Scudder <[email protected]> • #18620
are the Tunnel Encap Attribute in a BGP UPDATE applicable to all the NLRI listed in the MP_REACH_NLRI path attribute?
Tue, 22 Oct 2019 20:27:32 +0000
Linda Dunbar <[email protected]> • #18619
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Tue, 22 Oct 2019 20:25:49 +0000
Linda Dunbar <[email protected]> • #18618
Re: Call for IETF106 IDR agenda items
Mon, 21 Oct 2019 19:12:40 +0000
Linda Dunbar <[email protected]> • #18617
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Mon, 21 Oct 2019 23:54:41 +0800
"[email protected]" <[email protected]> • #18616
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Mon, 21 Oct 2019 15:52:05 +0000
ruoxin huang <[email protected]> • #18615
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Mon, 21 Oct 2019 15:44:50 +0000
reta Yang <[email protected]> • #18614
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Mon, 21 Oct 2019 10:31:10 -0400
Xufeng Liu <[email protected]> • #18613
Call for IETF106 IDR agenda items
Sat, 19 Oct 2019 07:22:58 +0000
"Dongjie (Jimmy)" <[email protected]> • #18612
答复: draft-li-idr-flowspec-rpd- 05.txt - WG Adoption call (10/14 to 10/28/201 9)
Sat, 19 Oct 2019 10:18:15 +0800
"Ou Liang" <[email protected]> • #18611
Re: Early allocation expiration for draft-ietf-idr-eag-distribution [was: Re: [idr] 2nd attempt - WG LC on draft -ietf-idr-eag-distribution (10/21/2018 to 11/3/2018) - ]
Fri, 18 Oct 2019 14:21:39 -0700
Jeff Tantsura <[email protected]> • #18610
I-D Action: draft-ietf-idr-eag-distribution-09.txt
Fri, 18 Oct 2019 14:17:41 -0700
[email protected] • #18609
Re: draft-ietf-spring-segment-routing-policy
Fri, 18 Oct 2019 15:05:35 +0000
"Ketan Talaulikar (ketant)" <[email protected]> • #18608
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Fri, 18 Oct 2019 16:03:42 +0000
Keyur Patel <[email protected]> • #18607
Re: draft-ietf-spring-segment-routing-policy
Fri, 18 Oct 2019 14:39:59 +0000
<[email protected]> • #18606
Re: [spring] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
Fri, 18 Oct 2019 13:39:04 +0000
"Rakesh Gandhi (rgandhi)" <[email protected]> • #18605
Re: [spring] Adoption: draft-li-idr-bgp-ls-sr -policy-path-segment-03.txt and draft-li-sr-policy-path-segme nt-01.txt - 1 week extension [10/14 to 10/21/2019]
Fri, 18 Oct 2019 17:12:23 +0800 (CST)
<[email protected]> • #18604
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Fri, 18 Oct 2019 11:00:33 +0200
Robert Raszuk <[email protected]> • #18603
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Fri, 18 Oct 2019 07:51:06 +0000
Haoyu Song <[email protected]> • #18602
Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
Fri, 18 Oct 2019 07:27:54 +0000
"Ketan Talaulikar (ketant)" <[email protected]> • #18601
Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
Fri, 18 Oct 2019 07:04:51 +0000
"Chengli (Cheng Li)" <[email protected]> • #18600
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Fri, 18 Oct 2019 06:23:42 +0000
Huzhibo <[email protected]> • #18599
Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
Fri, 18 Oct 2019 06:19:16 +0000
"Wanghaibo (Rainsword)" <[email protected]> • #18598
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Fri, 18 Oct 2019 06:16:30 +0000
"Wanghaibo (Rainsword)" <[email protected]> • #18597
Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
Fri, 18 Oct 2019 05:50:39 +0000
"Ketan Talaulikar (ketant)" <[email protected]> • #18596
Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
Fri, 18 Oct 2019 11:42:27 +0800
"Weiqiang Cheng" <[email protected]> • #18595
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Fri, 18 Oct 2019 03:28:28 +0000
jasonlu(陆素建) <[email protected]> • #18594
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Fri, 18 Oct 2019 00:43:00 +0000
Keyur Patel <[email protected]> • #18593
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Fri, 18 Oct 2019 00:30:27 +0000
Keyur Patel <[email protected]> • #18592
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Fri, 18 Oct 2019 01:22:25 +0200
Robert Raszuk <[email protected]> • #18591
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thu, 17 Oct 2019 23:06:45 +0000
"Rajiv Asati (rajiva)" <[email protected]> • #18590
Re: draft-ietf-spring-segment-routing-policy
Thu, 17 Oct 2019 17:48:58 +0000
"Ketan Talaulikar (ketant)" <[email protected]> • #18589
Re: draft-ietf-spring-segment-routing-policy
Thu, 17 Oct 2019 14:54:03 +0000
<[email protected]> • #18588
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thu, 17 Oct 2019 06:30:54 -0400
Robert Raszuk <[email protected]> • #18587
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thu, 17 Oct 2019 11:33:08 +0200
Ondrej Zajicek <[email protected]> • #18586
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thu, 17 Oct 2019 10:25:13 +0200
Robert Raszuk <[email protected]> • #18585
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thu, 17 Oct 2019 08:08:11 +0000
Srihari Sangli <[email protected]> • #18584
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thu, 17 Oct 2019 09:47:12 +0200
Robert Raszuk <[email protected]> • #18583
Re: draft-ietf-spring-segment-routing-policy
Thu, 17 Oct 2019 06:27:22 +0000
"Ketan Talaulikar (ketant)" <[email protected]> • #18582
Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thu, 17 Oct 2019 05:31:25 +0000
Srihari Sangli <[email protected]> • #18581
Re: Opsdir early review of draft-ietf-idr-rfc8203bis-04
Thu, 17 Oct 2019 08:15:32 +0300
Dan Romascanu <[email protected]> • #18580
Re: Opsdir early review of draft-ietf-idr-rfc8203bis-04
Wed, 16 Oct 2019 22:32:39 +0000
John Scudder <[email protected]> • #18579
I-D Action: draft-ietf-idr-rfc8203bis-05.txt
Wed, 16 Oct 2019 15:28:55 -0700
[email protected] • #18578
Re: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)
Wed, 16 Oct 2019 10:45:15 -0700
LEI LIU <[email protected]> • #18577
Re: I-D Action: draft-ietf-idr-performance-routing -02.txt
Wed, 16 Oct 2019 20:12:53 +0800
"徐小虎(义先)" <[email protected]> • #18576
Re: [spring] I-D Action: draft-ietf-idr-performance-routing-02.txt
Wed, 16 Oct 2019 12:02:44 +0000
"UTTARO, JAMES" <[email protected]> • #18575
Re: [spring] I-D Action: draft-ietf-idr-performance-routing-02.txt
Wed, 16 Oct 2019 11:59:02 +0000
"UTTARO, JAMES" <[email protected]> • #18574
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.