IETF Discussion

• Thread Index

• Opsdir last call review of draft-ietf-cbor-array-tags-07
  • From: Linda Dunbar via Datatracker
• Opsdir last call review of draft-ietf-cbor-array-tags-07
  • From: Linda Dunbar via Datatracker
• Opsdir last call review of draft-ietf-pce-stateful-pce-auto-bandwidth-10
  • From: Joe Clarke via Datatracker
• Re: Genart last call review of draft-ietf-curdle-ssh-curves-09
  • From: Mark D. Baushke
• Re: Genart last call review of draft-ietf-curdle-ssh-curves-09
  • From: Christer Holmberg
• Re: Genart last call review of draft-ietf-curdle-ssh-curves-09
  • From: Mark D. Baushke
• v3 format rollout schedule
  • From: Heather Flanagan
• Re: Genart last call review of draft-ietf-curdle-ssh-curves-09
  • From: Christer Holmberg
• Secdir last call review of draft-ietf-cdni-request-routing-extensions-05
  • From: Linda Dunbar via Datatracker
• Re: Genart last call review of draft-ietf-curdle-ssh-curves-09
  • From: Mark D. Baushke
• Genart last call review of draft-ietf-pce-lsp-control-request-08
  • From: Francesca Palombini via Datatracker
• Secdir last call review of draft-ietf-curdle-ssh-curves-09
  • From: Tobias Gondrom via Datatracker
• Re: [rmcat] Genart last call review of draft-ietf-rmcat-nada-11
  • From: Xiaoqing Zhu (xiaoqzhu)
• Re: [rmcat] Secdir last call review of draft-ietf-rmcat-nada-11
  • From: Xiaoqing Zhu (xiaoqzhu)
• Re: Last Call: <draft-ietf-tls-sni-encryption-05.txt> (Issues and Requirements for SNI Encryption in TLS) to Informational RFC
  • From: Benjamin Kaduk
• Re: Yangdoctors early review of draft-ietf-bfd-unsolicited-01
  • From: Jeffrey Haas
• Opsdir last call review of draft-ietf-intarea-frag-fragile-15
  • From: Zitao Wang via Datatracker
• 答复: Secdir last call review of draft-ietf-6man-segment-routing-header-22
  • From: Xialiang (Frank, Network Standard & Patent Dept)
• Re: Genart last call review of draft-ietf-iasa2-rfc2031bis-05
  • From: Rob Sayre
• Re: Genart last call review of draft-ietf-lpwan-ipv6-static-context-hc-21
  • From: Pete Resnick
• Re: Genart last call review of draft-ietf-iasa2-rfc2031bis-05
  • From: Livingood, Jason
• Secdir last call review of draft-ietf-ippm-stamp-07
  • From: Russ Housley via Datatracker
• Re: Genart last call review of draft-ietf-lpwan-ipv6-static-context-hc-21
  • From: dominique.barthel
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Genart last call review of draft-ietf-curdle-ssh-curves-09
  • From: Christer Holmberg via Datatracker
• Re: Opsdir last call review of draft-ietf-cdni-request-routing-extensions-05
  • From: Ori Finkelman
• Re: Why do we need to go with 128 bits address space ?
  • From: Robert Raszuk
• Re: Why do we need to go with 128 bits address space ?
  • From: Alexandre Petrescu
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Leif Johansson
• Re: Why do we need to go with 128 bits address space ?
  • From: Fred Baker
• Re: [Gen-art] Genart last call review of draft-ietf-lpwan-ipv6-static-context-hc-21
  • From: Alissa Cooper
• Re: [Gen-art] Genart last call review of draft-ietf-teas-yang-te-types-09
  • From: Alissa Cooper
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: John Wroclawski
• Re: Why do we need to go with 128 bits address space ?
  • From: Fred Baker
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: Yangdoctors early review of draft-ietf-bfd-unsolicited-01
  • From: Reshad Rahman (rrahman)
• Re: Why do we need to go with 128 bits address space ?
  • From: Robert Raszuk
• Re: Genart last call review of draft-ietf-cdni-request-routing-extensions-05
  • From: Ori Finkelman (IETF)
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: Why do we need to go with 128 bits address space ?
  • From: Keith Moore
• Re: [Gen-art] Genart telechat review of draft-ietf-lamps-cms-mix-with-psk-06
  • From: Alissa Cooper
• Re: Yangdoctors early review of draft-ietf-bfd-unsolicited-01
  • From: Reshad Rahman (rrahman)
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: Why do we need to go with 128 bits address space ?
  • From: Robert Raszuk
• Re: Yangdoctors early review of draft-ietf-bfd-unsolicited-01
  • From: Jeffrey Haas
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• RE: Last Call: <draft-ietf-tls-sni-encryption-05.txt> (Issues and Requirements for SNI Encryption in TLS) to Informational RFC
  • From: Mike Bishop
• Re: Secdir last call review of draft-ietf-6man-segment-routing-header-22
  • From: Darren Dukes (ddukes)
• Re: Secdir last call review of draft-ietf-ospf-xaf-te-07
  • From: Kathleen Moriarty
• Re: [Gen-art] [manet] Genart last call review of draft-ietf-manet-dlep-lid-extension-05
  • From: Alissa Cooper
• Re: Secdir last call review of draft-ietf-ospf-xaf-te-07
  • From: Acee Lindem (acee)
• Secdir last call review of draft-ietf-ospf-xaf-te-07
  • From: Kathleen Moriarty via Datatracker
• Re: Why do we need to go with 128 bits address space ?
  • From: Robert Raszuk
• Re: Improving reading of drafts and other documents
  • From: Alexandre Petrescu
• Opsdir last call review of draft-ietf-ecrit-data-only-ea-18
  • From: Jürgen Schönwälder via Datatracker
• Is the IETF missing a disclosure policy?
  • From: Rob Sayre
• Tsvart last call review of draft-ietf-6man-segment-routing-header-22
  • From: Joseph Touch via Datatracker
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: S Moonesamy
• Secdir telechat review of draft-ietf-lamps-cms-mix-with-psk-06
  • From: Phillip Hallam-Baker via Datatracker
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Alissa Cooper
• Opsdir last call review of draft-ietf-tls-sni-encryption-05
  • From: Dan Romascanu via Datatracker
• Genart last call review of draft-ietf-cdni-request-routing-extensions-05
  • From: Dan Romascanu via Datatracker
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Opsdir last call review of draft-ietf-cdni-request-routing-extensions-05
  • From: Zitao Wang via Datatracker
• Predictable Numeric Identifiers (Fwd: [Pearg] Call for Adoption: Two drafts on Numeric IDs)
  • From: Fernando Gont
• Re: Why do we need to go with 128 bits address space ?
  • From: Fernando Gont
• Re: Why do we need to go with 128 bits address space ?
  • From: John Levine
• Opsdir last call review of draft-ietf-core-senml-etch-05
  • From: Carlos Pignataro via Datatracker
• RE: Why do we need to go with 128 bits address space ?
  • From: Pengshuping (Peng Shuping)
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: S Moonesamy
• Re: What's the Internet's biggest flaw? (was Re: [irtf-discuss] Why do we need to go with 128 bits address space ?)
  • From: Masataka Ohta
• Re: Opsdir last call review of draft-ietf-6man-segment-routing-header-22
  • From: Darren Dukes (ddukes)
• Re: Yangdoctors early review of draft-ietf-bfd-unsolicited-01
  • From: Reshad Rahman (rrahman)
• Re: Yangdoctors early review of draft-ietf-bfd-unsolicited-01
  • From: Martin Bjorklund
• Re: Yangdoctors early review of draft-ietf-bfd-unsolicited-01
  • From: Reshad Rahman (rrahman)
• Re: Yangdoctors early review of draft-ietf-bfd-unsolicited-01
  • From: Mahesh Jethanandani
• Re: What's the Internet's biggest flaw? (was Re: [irtf-discuss] Why do we need to go with 128 bits address space ?)
  • From: Nico Williams
• Re: What's the Internet's biggest flaw? (was Re: [irtf-discuss] Why do we need to go with 128 bits address space ?)
  • From: Andrew G. Malis
• What's the Internet's biggest flaw? (was Re: [irtf-discuss] Why do we need to go with 128 bits address space ?)
  • From: Keith Moore
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Carsten Bormann
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Robert Moskowitz
• Yangdoctors early review of draft-ietf-bfd-unsolicited-01
  • From: Martin Björklund via Datatracker
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Andrew Sullivan
• Re: [manet] Secdir last call review of draft-ietf-manet-dlep-lid-extension-05
  • From: Stan Ratliff
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Christian de Larrinaga
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Christian de Larrinaga
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Bob Hinden
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Brian E Carpenter
• Yangdoctors early review of draft-ietf-mpls-base-yang-10
  • From: Ebben Aries via Datatracker
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Phillip Hallam-Baker
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: S Moonesamy
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Joe Abley
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Andrew Sullivan
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Andrew Sullivan
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Christian de Larrinaga
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: S Moonesamy
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: Andrew Sullivan
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Michael
• Re: Internationalization
  • From: S Moonesamy
• Re: Last Call: <draft-ietf-iasa2-rfc2031bis-05.txt> (The IETF-ISOC Relationship) to Informational RFC
  • From: S Moonesamy
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Keith Moore
• Re: [rmcat] Secdir last call review of draft-ietf-rmcat-nada-11
  • From: Gorry Fairhurst
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: [rmcat] Secdir last call review of draft-ietf-rmcat-nada-11
  • From: Gorry Fairhurst
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Keith Moore
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Mark Smith
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Keith Moore
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• Re: Genart last call review of draft-ietf-lsr-isis-rfc5306bis-04
  • From: Russ Housley
• Opsdir telechat review of draft-ietf-netmod-artwork-folding-08
  • From: Ron Bonica via Datatracker
• RE: Genart last call review of draft-ietf-lsr-isis-rfc5306bis-04
  • From: Les Ginsberg (ginsberg)
• Re: [rmcat] Secdir last call review of draft-ietf-rmcat-nada-11
  • From: Xiaoqing Zhu (xiaoqzhu)
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Phillip Hallam-Baker
• Re: [rmcat] Secdir last call review of draft-ietf-rmcat-nada-11
  • From: Colin Perkins
• Re: Why do we need to go with 128 bits address space ?
  • From: Behcet Sarikaya
• Genart telechat review of draft-ietf-lamps-cms-mix-with-psk-06
  • From: Robert Sparks via Datatracker
• Re: [rmcat] Secdir last call review of draft-ietf-rmcat-nada-11
  • From: Mirja Kuehlewind
• Re: Why do we need to go with 128 bits address space ?
  • From: Musa Stephen Honlue
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Mark Smith
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Fernando Gont
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Roland Bless
• Re: Why do we need to go with 128 bits address space ?
  • From: Carsten Bormann
• Re: Does routing table size still matter (Re: Why do we need to go with 128 bits address space ?)
  • From: Masataka Ohta
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• RE: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Chengli (Cheng Li)
• Re: Secdir Last Call assignment: draft-ietf-mile-jsoniodef
  • From: Derrell Piper
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Tom Herbert
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Fernando Gont
• Genart last call review of draft-ietf-lsr-isis-rfc5306bis-04
  • From: Russ Housley via Datatracker
• Re: Why do we need to go with 128 bits address space ?
  • From: Nico Williams
• Does routing table size still matter (Re: Why do we need to go with 128 bits address space ?)
  • From: Nico Williams
• Re: HTTP code for error business logic
  • From: Matthew A. Miller
• Re: Why do we need to go with 128 bits address space ?
  • From: Scott O. Bradner
• Re: HTTP code for error business logic
  • From: Илья Страхов
• Re: Why do we need to go with 128 bits address space ?
  • From: Robert Moskowitz
• Re: Why do we need to go with 128 bits address space ?
  • From: tom petch
• Re: [Gen-art] [Iasa20] Genart last call review of draft-ietf-iasa2-rfc5377bis-02
  • From: Elwyn Davies
• Genart last call review of draft-ietf-6man-segment-routing-header-22
  • From: Roni Even via Datatracker
• Re: Why do we need to go with 128 bits address space ?
  • From: Keith Moore
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Mark Allman
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Lixia Zhang
• Re: HTTP code for error business logic
  • From: Alexander Neilson
• Re: Why do we need to go with 128 bits address space ?
  • From: Robert Moskowitz
• Re: HTTP code for error business logic
  • From: Илья Страхов
• Re: HTTP code for error business logic
  • From: Alexander Neilson
• Re: Why do we need to go with 128 bits address space ?
  • From: Sam Kerner
• Re: HTTP code for error business logic
  • From: Cenk Gündoğan
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Roland Bless
• Re: HTTP code for error business logic
  • From: Илья Страхов
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Brian Carpenter
• Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
  • From: Roland Bless
• Re: HTTP code for error business logic
  • From: Alexander Neilson
• Re: Why do we need to go with 128 bits address space ?
  • From: Mark Smith
• Re: Why do we need to go with 128 bits address space ?
  • From: Masataka Ohta
• HTTP code for error business logic
  • From: Илья Страхов
• Why do we need to go with 128 bits address space ?
  • From: shyam bandyopadhyay
• Secdir last call review of draft-ietf-6man-segment-routing-header-22
  • From: Liang Xia via Datatracker
• Re: [Iasa20] Genart last call review of draft-ietf-iasa2-rfc5377bis-02
  • From: Joel M. Halpern
• Genart last call review of draft-ietf-iasa2-rfc5377bis-02
  • From: Elwyn Davies via Datatracker
• Re: Improving reading of drafts and other documents
  • From: Michael Richardson
• Re: Improving reading of drafts and other documents
  • From: Pete Resnick
• Re: Improving reading of drafts and other documents
  • From: Behcet Sarikaya
• Re: Improving reading of drafts and other documents
  • From: Behcet Sarikaya
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: RFC ISE (Adrian Farrel)
• Opsdir last call review of draft-ietf-6man-segment-routing-header-22
  • From: Will LIU via Datatracker
• Re: Improving reading of drafts and other documents
  • From: lloyd.wood@xxxxxxxxxxx
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Michael Richardson
• Re: Improving reading of drafts and other documents
  • From: Mary B
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: RFC ISE (Adrian Farrel)
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: RFC ISE (Adrian Farrel)
• Re: Improving reading of drafts and other documents
  • From: Carsten Bormann
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Andrew G. Malis
• Re: Improving reading of drafts and other documents
  • From: Mary B
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Ted Hardie
• Re: Improving reading of drafts and other documents
  • From: Carsten Bormann
• Re: Genart last call review of draft-klensin-idna-rfc5891bis-04
  • From: Vijay Gurbani
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: RFC ISE (Adrian Farrel)
• Improving reading of drafts and other documents
  • From: Robert Moskowitz
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Benjamin Kaduk
• Re: Genart last call review of draft-ietf-oauth-resource-indicators-05
  • From: Brian Campbell
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Warren Kumari
• Re: Genart last call review of draft-klensin-idna-rfc5891bis-04
  • From: John C Klensin
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: RFC ISE (Adrian Farrel)
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Warren Kumari
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: ned+ietf
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Warren Kumari
• Re: Genart last call review of draft-ietf-rmcat-nada-11
  • From: Joel M. Halpern
• Re: Genart last call review of draft-ietf-rmcat-nada-11
  • From: Xiaoqing Zhu (xiaoqzhu)
• Mailing List: Evolving Documents
  • From: Warren Kumari
• Re: Genart last call review of draft-klensin-idna-rfc5891bis-04
  • From: Vijay Gurbani
• Re: Genart last call review of draft-klensin-idna-rfc5891bis-04
  • From: John C Klensin
• Genart last call review of draft-klensin-idna-rfc5891bis-04
  • From: Vijay Gurbani via Datatracker
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Samuel Weiler
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Andrew G. Malis
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: RFC ISE (Adrian Farrel)
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Andrew G. Malis
• Re: Request for comments : IANA Policy for the Independent Stream
  • From: Job Snijders
• Request for comments : IANA Policy for the Independent Stream
  • From: RFC ISE (Adrian Farrel)
• Re: [rmcat] Secdir last call review of draft-ietf-rmcat-nada-11
  • From: Gorry Fairhurst
• Genart last call review of draft-ietf-netmod-artwork-folding-08
  • From: Roni Even via Datatracker
• Secdir last call review of draft-ietf-rmcat-nada-11
  • From: Sean Turner via Datatracker
• IETF blog post on STIR
  • From: Peterson, Jon
• Re: Problems with datatracker?
  • From: Carsten Bormann
• Problems with datatracker?
  • From: Robert Moskowitz
• Re: Rtgdir telechat review of draft-ietf-babel-rfc6126bis-11
  • From: Juliusz Chroboczek
• Secdir last call review of draft-ietf-manet-dlep-lid-extension-05
  • From: Nancy Cam-Winget via Datatracker
• Re: Last Call: <draft-ietf-iasa2-rfc5377bis-02.txt> (Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents) to Informational RFC
  • From: S Moonesamy
• Re: The mailing list web archive seems broken
  • From: Henrik Levkowetz
• Re: Last Call: <draft-ietf-iasa2-rfc5377bis-02.txt> (Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents) to Informational RFC
  • From: Joel M. Halpern
• Re: Genart last call review of draft-klensin-idna-unicode-review-02
  • From: Joel M. Halpern
• RE: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: John C Klensin
• Re: Last Call: <draft-ietf-iasa2-rfc5377bis-02.txt> (Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents) to Informational RFC
  • From: S Moonesamy
• Re: Genart last call review of draft-klensin-idna-unicode-review-02
  • From: John C Klensin
• Re: Genart last call review of draft-klensin-idna-unicode-review-02
  • From: Barry Leiba
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Carsten Bormann
• Re: Errata Processing Stats/Queue?
  • From: Henrik Levkowetz
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Robert Moskowitz
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: tjw ietf
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Robert Moskowitz
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Carsten Bormann
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Robert Moskowitz
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Benjamin Kaduk
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Robert Moskowitz
• Re: Errata Processing Stats/Queue?
  • From: Michael Richardson
• Re: Errata Processing Stats/Queue?
  • From: Henrik Levkowetz
• Re: [I2nsf] Yangdoctors last call review of draft-ietf-i2nsf-consumer-facing-interface-dm-05
  • From: Mr. Jaehoon Paul Jeong
• Genart last call review of draft-klensin-idna-unicode-review-02
  • From: Joel Halpern via Datatracker
• Re: Energy saving as an IETF goal
  • From: Benjamin Kaduk
• Secdir last call review of draft-ietf-iasa2-rfc7776bis-02
  • From: Melinda Shore via Datatracker
• Re: Errata Processing Stats/Queue?
  • From: Randy Bush
• Re: Errata Processing Stats/Queue?
  • From: Brian E Carpenter
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Brian E Carpenter
• Re: Errata Processing Stats/Queue?
  • From: Sean Turner
• Re: Errata Processing Stats/Queue?
  • From: Sean Turner
• RE: Errata Processing Stats/Queue?
  • From: Adrian Farrel
• Re: Errata Processing Stats/Queue?
  • From: Henrik Levkowetz
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: John R Levine
• Re: [Gen-art] Genart last call review of draft-ietf-babel-hmac-07
  • From: Alissa Cooper
• Re: [Gen-art] Genart last call review of draft-ietf-babel-dtls-05
  • From: Alissa Cooper
• Re: [Gen-art] [babel] Genart last call review of draft-ietf-babel-rfc6126bis-10
  • From: Alissa Cooper
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: John C Klensin
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Salz, Rich
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Mikael Abrahamsson
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Meetecho IETF support
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Meetecho IETF support
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Meetecho IETF support
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Mikael Abrahamsson
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Mikael Abrahamsson
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Mikael Abrahamsson
• Re: Errata Processing Stats/Queue?
  • From: Eric Rescorla
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: Patrik Fältström
• 答复: Yangdoctors last call review of draft-ietf-ccamp-layer0-types-01
  • From: Zhenghaomian
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: John R Levine
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: John C Klensin
• Re: Energy saving as an IETF goal
  • From: Keith Moore
• Re: Energy saving as an IETF goal
  • From: Erik Nygren
• Re: Errata Processing Stats/Queue?
  • From: Clint Chaplin
• Re: Errata Processing Stats/Queue?
  • From: Richard Barnes
• Re: Errata Processing Stats/Queue?
  • From: Clint Chaplin
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: Jaap Akkerhuis
• Re: Errata Processing Stats/Queue?
  • From: Richard Barnes
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: John Levine
• Re: Errata Processing Stats/Queue?
  • From: Brian E Carpenter
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Eliot Lear
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Warren Kumari
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Andrew G. Malis
• RE: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Linda Dunbar
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Nico Williams
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Nico Williams
• Re: Errata Processing Stats/Queue?
  • From: Richard Barnes
• Re: [Gen-art] Genart telechat review of draft-ietf-dnssd-push-23
  • From: Alissa Cooper
• Re: Errata Processing Stats/Queue?
  • From: Eric Rescorla
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Andrew G. Malis
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Carsten Bormann
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Michael StJohns
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Kathleen Moriarty
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Warren Kumari
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Peter Saint-Andre
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Tim Chown
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Andrew G. Malis
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Andrew G. Malis
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Peter Saint-Andre
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Tim Chown
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Errata Processing Stats/Queue?
  • From: Robert Sparks
• RE: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Linda Dunbar
• Re: Errata Processing Stats/Queue?
  • From: Benjamin Kaduk
• Re: Errata Processing Stats/Queue?
  • From: Benjamin Kaduk
• Re: [I2nsf] Yangdoctors last call review of draft-ietf-i2nsf-consumer-facing-interface-dm-05
  • From: Jan Lindblad
• Re: Errata Processing Stats/Queue?
  • From: Warren Kumari
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: ned+ietf
• Re: Errata Processing Stats/Queue?
  • From: Carsten Bormann
• Re: Errata Processing Stats/Queue?
  • From: Eric Rescorla
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: [I2nsf] Yangdoctors last call review of draft-ietf-i2nsf-consumer-facing-interface-dm-05
  • From: Mr. Jaehoon Paul Jeong
• Re: Errata Processing Stats/Queue?
  • From: Eric Rescorla
• Re: Errata Processing Stats/Queue?
  • From: Stewart Bryant
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Errata Processing Stats/Queue?
  • From: Stephen Farrell
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Errata Processing Stats/Queue?
  • From: Stephen Farrell
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Tim Wicinski
• Re: Errata Processing Stats/Queue?
  • From: Kathleen Moriarty
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: Jaap Akkerhuis
• Re: [Gen-art] Genart last call review of draft-ietf-mpls-rfc8287-len-clarification-02
  • From: Ines Robles
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Tim Chown
• Re: Rtgdir telechat review of draft-ietf-babel-rfc6126bis-11
  • From: Yingzhen Qu
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Mikael Abrahamsson
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Nico Williams
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Yoav Nir
• Genart last call review of draft-ietf-lpwan-ipv6-static-context-hc-21
  • From: Pete Resnick via Datatracker
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: John Levine
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: John Levine
• Re: Should IETF stop using GitHub?
  • From: Bron Gondwana
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Salz, Rich
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Mark Nottingham
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Keith Moore
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Brian E Carpenter
• RE: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Linda Dunbar
• Re: why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Peter Saint-Andre
• why is it still mandatary to have Jabber scribing for WG session given Etherpad can allow anyone to post questions?
  • From: Linda Dunbar
• Re: Genart last call review of draft-ietf-curdle-ssh-ed25519-ed448-07
  • From: Viktor Dukhovni
• Genart telechat review of draft-ietf-curdle-ssh-ed25519-ed448-09
  • From: Linda Dunbar via Datatracker
• Re: [lamps] Genart last call review of draft-ietf-lamps-cms-mix-with-psk-05
  • From: Russ Housley
• Re: Errata Processing Stats/Queue?
  • From: Michael Richardson
• Re: [Gen-art] Genart last call review of draft-ietf-intarea-frag-fragile-13
  • From: Alissa Cooper
• Re: [MMUSIC] [Gen-art] Genart last call review of draft-ietf-mmusic-ice-sip-sdp-36
  • From: Roman Shpount
• Re: Should IETF stop using GitHub because of bogus lawsuits?
  • From: John Levine
• Re: [Gen-art] Genart last call review of draft-ietf-mpls-rfc8287-len-clarification-02
  • From: Carlos Pignataro (cpignata)
• Re: [Gen-art] Genart last call review of draft-ietf-mpls-rfc8287-len-clarification-02
  • From: Alissa Cooper
• RE: [Gen-art] Genart last call review of draft-ietf-curdle-ssh-ed25519-ed448-07
  • From: Linda Dunbar
• Re: [Gen-art] Genart last call review of draft-ietf-manet-dlep-latency-extension-04
  • From: Alissa Cooper
• Re: [Gen-art] Genart last call review of draft-ietf-curdle-ssh-ed25519-ed448-07
  • From: Alissa Cooper
• Re: Errata Processing Stats/Queue?
  • From: Benjamin Kaduk
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: [MMUSIC] [Gen-art] Genart last call review of draft-ietf-mmusic-ice-sip-sdp-36
  • From: Roman Shpount
• Re: Errata Processing Stats/Queue?
  • From: Carsten Bormann
• Re: Errata Processing Stats/Queue?
  • From: Joel M. Halpern
• Re: [Gen-art] Genart last call review of draft-ietf-mmusic-ice-sip-sdp-36
  • From: Alissa Cooper
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Errata Processing Stats/Queue?
  • From: Benjamin Kaduk
• Re: Errata Processing Stats/Queue?
  • From: Michael Richardson
• Re: Errata Processing Stats/Queue?
  • From: Michael Richardson
• Re: Last Call: <draft-klensin-idna-rfc5891bis-04.txt> (Internationalized Domain Names in Applications (IDNA): Registry Restrictions and Recommendations) to Proposed Standard
  • From: John R Levine
• Re: Should IETF stop using GitHub?
  • From: Eliot Lear
• Re: Errata Processing Stats/Queue?
  • From: Stewart Bryant
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Errata Processing Stats/Queue?
  • From: Stewart Bryant
• Re: Errata Processing Stats/Queue?
  • From: Stewart Bryant
• IETF 105 Highlights
  • From: IETF Chair
• Re: Errata Processing Stats/Queue?
  • From: John C Klensin
• Re: Errata Processing Stats/Queue?
  • From: Stewart Bryant
• Re: Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Errata Processing Stats/Queue?
  • From: Stewart Bryant
• Re: Errata Processing Stats/Queue?
  • From: Brian Haberman
• Errata Processing Stats/Queue?
  • From: Fernando Gont
• Re: Last Call: <draft-klensin-idna-rfc5891bis-04.txt> (Internationalized Domain Names in Applications (IDNA): Registry Restrictions and Recommendations) to Proposed Standard
  • From: John C Klensin
• RE: [manet] Genart last call review of draft-ietf-manet-dlep-lid-extension-05
  • From: Rick Taylor
• Genart last call review of draft-ietf-manet-dlep-lid-extension-05
  • From: Stewart Bryant via Datatracker
• Re: Last Call: <draft-klensin-idna-rfc5891bis-04.txt> (Internationalized Domain Names in Applications (IDNA): Registry Restrictions and Recommendations) to Proposed Standard
  • From: John Levine
• Genart last call review of draft-ietf-rmcat-nada-11
  • From: Joel Halpern via Datatracker
• Genart last call review of draft-ietf-oauth-jwt-introspection-response-05
  • From: Linda Dunbar via Datatracker
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Benjamin Kaduk
• Re: [netmod] Secdir last call review of draft-ietf-netmod-artwork-folding-08
  • From: Kent Watsen
• Re: [Gen-art] Genart last call review of draft-ietf-ospf-xaf-te-06
  • From: Alissa Cooper
• Re: [Gen-art] Genart last call review of draft-ietf-lamps-cms-shakes-11
  • From: Alissa Cooper
• Re: [Gen-art] [babel] Genart last call review of draft-ietf-babel-applicability-06
  • From: Alissa Cooper
• Opsdir last call review of draft-ietf-babel-hmac-08
  • From: Dan Romascanu via Datatracker
• Secdir Last Call review of draft-ietf-iasa2-rfc5377bis-02
  • From: Valery Smyslov
• Re: We gotta stop meeting like this
  • From: Fernando Gont
• Re: We gotta stop meeting like this
  • From: Fernando Gont
• Re: Should IETF stop using GitHub?
  • From: Nico Williams
• Videos of Montreal pechakucha &tc talks
  • From: Aaron Falk
• Re: Should IETF stop using GitHub?
  • From: Randy Bush
• Re: Forming and confirming consensus (was: Re: Should IETF stop using GitHub?)
  • From: Michael Richardson
• Re: Last Call: <draft-klensin-idna-rfc5891bis-04.txt> (Internationalized Domain Names in Applications (IDNA): Registry Restrictions and Recommendations) to Proposed Standard
  • From: John C Klensin
• Re: Should IETF stop using GitHub?
  • From: Eliot Lear
• Genart last call review of draft-ietf-iasa2-rfc2031bis-05
  • From: Peter Yee via Datatracker
• Re: [Lsr] Last Call: <draft-ietf-ospf-yang-23.txt> (YANG Data Model for OSPF Protocol) to Proposed Standard
  • From: Acee Lindem (acee)
• Re: Last Call: <draft-klensin-idna-rfc5891bis-04.txt> (Internationalized Domain Names in Applications (IDNA): Registry Restrictions and Recommendations) to Proposed Standard
  • From: Alessandro Vesely
• Re: Should IETF stop using GitHub?
  • From: tom petch
• Re: Forming and confirming consensus (was: Re: Should IETF stop using GitHub?)
  • From: tom petch
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-klensin-idna-unicode-review-02.txt> (IDNA Review for New Unicode Versions) to Proposed Standard
  • From: Donald Eastlake
• Re: Consensus confirmation calls (was Re: Forming and confirming consensus (was: ...)
  • From: Nico Williams
• Re: Consensus confirmation calls (was Re: Forming and confirming consensus
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: John C Klensin
• Re: Consensus confirmation calls (was Re: Forming and confirming consensus (was: ...)
  • From: Joe Touch
• Consensus confirmation calls (was Re: Forming and confirming consensus (was: ...)
  • From: Nico Williams
• Re: Should IETF stop using GitHub?
  • From: Joel M. Halpern
• Re: Should IETF stop using GitHub?
  • From: Randy Bush
• Re: Forming and confirming consensus (was: Re: Should IETF stop using GitHub?)
  • From: Eric Rescorla
• Re: Forming and confirming consensus (was: Re: Should IETF stop using GitHub?)
  • From: Carsten Bormann
• Re: Forming and confirming consensus
  • From: Keith Moore
• Re: Forming and confirming consensus (was: Re: Should IETF stop using GitHub?)
  • From: John C Klensin
• Re: Forming and confirming consensus (was: Re: Should IETF stop using GitHub?)
  • From: Melinda Shore
• Re: Forming and confirming consensus (was: Re: Should IETF stop using GitHub?)
  • From: Eric Rescorla
• Forming and confirming consensus (was: Re: Should IETF stop using GitHub?)
  • From: John C Klensin
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: John Levine
• Re: Should IETF stop using GitHub?
  • From: ned+ietf
• Re: Should IETF stop using GitHub?
  • From: Carsten Bormann
• Re: Should IETF stop using GitHub?
  • From: Eric Rescorla
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Lars Eggert
• VS: Should IETF stop using GitHub?
  • From: Christer Holmberg
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Carsten Bormann
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Christopher Wood
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: John Levine
• Re: Should IETF stop using GitHub?
  • From: Ted Lemon
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Benjamin Kaduk
• Re: Should IETF stop using GitHub?
  • From: Ted Lemon
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Bron Gondwana
• Re: Should IETF stop using GitHub?
  • From: Benjamin Kaduk
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Nico Williams
• Re: Should IETF stop using GitHub?
  • From: Carsten Bormann
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Toerless Eckert
• Re: Secdir last call review of draft-ietf-mmusic-rfc4566bis-36
  • From: Paul Kyzivat
• Re: Should IETF stop using GitHub?
  • From: Marc Petit-Huguenin
• Secdir last call review of draft-ietf-mmusic-rfc4566bis-36
  • From: Catherine Meadows via Datatracker
• Re: Should IETF stop using GitHub?
  • From: John Levine
• Secdir last call review of draft-ietf-mpls-rfc8287-len-clarification-02
  • From: Kyle Rose via Datatracker
• Re: Should IETF stop using GitHub?
  • From: Mark Nottingham
• Re: Should IETF stop using GitHub?
  • From: Brian E Carpenter
• Secdir last call review of draft-ietf-idr-bgp-extended-messages-35
  • From: Rich Salz via Datatracker
• Secdir last call review of draft-ietf-grow-bmp-adj-rib-out-06
  • From: Catherine Meadows via Datatracker
• Secdir last call review of draft-ietf-netmod-artwork-folding-08
  • From: Robert Sparks via Datatracker
• Genart telechat review of draft-ietf-dnssd-push-23
  • From: Robert Sparks via Datatracker
• Re: We gotta stop meeting like this
  • From: Eliot Lear
• Re: [netmod] Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice
  • From: Kent Watsen
• Re: Supervision under previous admin relationships (was Re: RFC Series Editor (RSE) Statement of Work)
  • From: John C Klensin
• Re: Supervision under previous admin relationships (was Re: RFC Series Editor (RSE) Statement of Work)
  • From: Andrew Sullivan
• Re: [Saa] We gotta stop meeting like this
  • From: Alissa Cooper
• Re: Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice
  • From: Richard Barnes
• Re: We gotta stop meeting like this
  • From: Alissa Cooper
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Mark Nottingham
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Mark Nottingham
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Alissa Cooper
• Re: Supervision under previous admin relationships (was Re: RFC Series Editor (RSE) Statement of Work)
  • From: Andrew Sullivan
• Re: [netmod] Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice
  • From: Paul Kyzivat
• Re: [netmod] Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice
  • From: Erik Auerswald
• Re: Should IETF stop using GitHub?
  • From: Rich Kulawiec
• Re: We gotta stop meeting like this
  • From: Job Snijders
• Re: We gotta stop meeting like this
  • From: Stephan Wenger
• Re: Rtgdir telechat review of draft-ietf-babel-rfc6126bis-11
  • From: Juliusz Chroboczek
• Re: Rtgdir telechat review of draft-ietf-babel-rfc6126bis-11
  • From: Juliusz Chroboczek
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Brian E Carpenter
• Re: Supervision under previous admin relationships (was Re: RFC Series Editor (RSE) Statement of Work)
  • From: Stephen Farrell
• Re: Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice
  • From: Paul Kyzivat
• Rtgdir telechat review of draft-ietf-babel-rfc6126bis-11
  • From: Yingzhen Qu via Datatracker
• Re: Supervision under previous admin relationships (was Re: RFC Series Editor (RSE) Statement of Work)
  • From: Michael StJohns
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Michael StJohns
• Re: baffled Re: Energy saving as an IETF goal (mostly, I hope. off topic)
  • From: George Michaelson
• Supervision under previous admin relationships (was Re: RFC Series Editor (RSE) Statement of Work)
  • From: Andrew Sullivan
• Re: We gotta stop meeting like this
  • From: Ted Lemon
• Re: We gotta stop meeting like this
  • From: Toerless Eckert
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Benjamin Kaduk
• Re: We gotta stop meeting like this
  • From: Ted Lemon
• Re: Should IETF stop using GitHub?
  • From: Salz, Rich
• Re: We gotta stop meeting like this
  • From: Toerless Eckert
• Re: Should IETF stop using GitHub?
  • From: Nico Williams
• Re: Should IETF stop using GitHub?
  • From: Wes Hardaker
• Re: baffled Re: Energy saving as an IETF goal (mostly, I hope. off topic)
  • From: Ted Lemon
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Michael StJohns
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Randy Bush
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Michael StJohns
• Re: baffled Re: Energy saving as an IETF goal (mostly, I hope. off topic)
  • From: Toerless Eckert
• Re: Should IETF stop using GitHub?
  • From: Christopher Wood
• Re: [Gen-art] Genart last call review of draft-ietf-rtgwg-enterprise-pa-multihoming-08
  • From: Alissa Cooper
• Re: We gotta stop meeting like this
  • From: Matthew A. Miller
• Re: Should IETF stop using GitHub?
  • From: Nico Williams
• Re: Should IETF stop using GitHub?
  • From: Lars Eggert
• Re: Should IETF stop using GitHub?
  • From: Nico Williams
• Re: [Lsr] Last Call: <draft-ietf-ospf-yang-23.txt> (YANG Data Model for OSPF Protocol) to Proposed Standard
  • From: tom petch
• Opsdir last call review of draft-ietf-mile-jsoniodef-10
  • From: Linda Dunbar via Datatracker
• Re: [LLC-Board] [IETF LLC] Report Ahead of IETF-105
  • From: Livingood, Jason
• Re: [ipwave] [Gen-art] Genart last call review of draft-ietf-ipwave-ipv6-over-80211ocb-46
  • From: Alexandre Petrescu
• Re: Should IETF stop using GitHub?
  • From: lloyd.wood@xxxxxxxxxxx
• Re: Should IETF stop using GitHub?
  • From: Alexandre Petrescu
• Re: [I2nsf] Yangdoctors last call review of draft-ietf-i2nsf-consumer-facing-interface-dm-05
  • From: Mr. Jaehoon Paul Jeong
• Re: Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice
  • From: Kent Watsen
• Re: [LLC-Board] LLC Board and contracts -- plenary comments
  • From: Livingood, Jason
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Alissa Cooper
• Re: Should IETF stop using GitHub?
  • From: Ladislav Lhotka
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Michael StJohns
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Alissa Cooper
• Re: RSOC name
  • From: Brian E Carpenter
• RE: We gotta stop meeting like this
  • From: Michel Py
• Re: Should IETF stop using GitHub?
  • From: Nico Williams
• Re: Should IETF stop using GitHub?
  • From: Nico Williams
• Re: Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice
  • From: Paul Kyzivat
• Re: Should IETF stop using GitHub?
  • From: Alissa Cooper
• Re: VS: Should IETF stop using GitHub?
  • From: Keith Moore
• VS: Should IETF stop using GitHub?
  • From: Christer Holmberg
• Re: Should IETF stop using GitHub?
  • From: Ladislav Lhotka
• Re: Should IETF stop using GitHub?
  • From: Keith Moore
• Re: Should IETF stop using GitHub?
  • From: Theodore Y. Ts'o
• Re: Should IETF stop using GitHub?
  • From: Simon Leinen
• Re: Should IETF stop using GitHub?
  • From: Ladislav Lhotka
• Re: Remote participation ( was Leading a moving target)
  • From: Meetecho IETF support
• Re: Should IETF stop using GitHub?
  • From: Dirk Kutscher
• Re: [I2nsf] Yangdoctors last call review of draft-ietf-i2nsf-consumer-facing-interface-dm-05
  • From: Jan Lindblad
• Re: Should IETF stop using GitHub?
  • From: Ladislav Lhotka
• Re: Should IETF stop using GitHub?
  • From: Lars Eggert
• Re: Should IETF stop using GitHub?
  • From: Martin Thomson
• Re: Should IETF stop using GitHub?
  • From: George Michaelson
• Re: Should IETF stop using GitHub?
  • From: Martin Thomson
• Genart last call review of draft-ietf-lamps-cms-mix-with-psk-05
  • From: Robert Sparks via Datatracker
• Genart last call review of draft-ietf-iasa2-rfc7776bis-02
  • From: Stewart Bryant via Datatracker
• Genart last call review of draft-ietf-oauth-resource-indicators-05
  • From: Stewart Bryant via Datatracker
• Re: Should IETF stop using GitHub?
  • From: Dirk Kutscher
• Re: [rfc-i] RSOC name
  • From: Kathleen Moriarty
• Re: [rfc-i] RSOC name
  • From: Christian Huitema
• 答复: I-D Action: draft-li-cross-area-ietf-work-00.txt
  • From: Lizhenbin
• Re: RSOC name
  • From: Kathleen Moriarty
• Re: Should IETF stop using GitHub?
  • From: Randy Bush
• Re: RSOC name
  • From: ned+ietf
• Re: Should IETF stop using GitHub?
  • From: Bob Hinden
• Re: Should IETF stop using GitHub?
  • From: Stewart Bryant
• Re: Should IETF stop using GitHub?
  • From: Marc Petit-Huguenin
• Re: Should IETF stop using GitHub?
  • From: Salz, Rich
• Re: Should IETF stop using GitHub?
  • From: Ted Lemon
• Re: Should IETF stop using GitHub?
  • From: Salz, Rich
• Re: Should IETF stop using GitHub?
  • From: Dirk Kutscher
• Genart last call review of draft-ietf-mpls-rfc8287-len-clarification-02
  • From: Ines Robles via Datatracker
• Re: [I2nsf] Yangdoctors last call review of draft-ietf-i2nsf-consumer-facing-interface-dm-05
  • From: Mr. Jaehoon Paul Jeong
• Re: RSOC name
  • From: Eliot Lear
• Re: LLC Board and contracts -- plenary comments
  • From: Leif Johansson
• Re: RSOC name
  • From: Stephen Farrell
• Re: RSOC name
  • From: John C Klensin
• Re: Should IETF stop using GitHub?
  • From: Alexandre Petrescu
• Re: RSOC name
  • From: Mike StJohns
• Re: RSOC name
  • From: Michael StJohns
• Re: RSOC name
  • From: Brian E Carpenter
• Re: RSOC name
  • From: Andrew Sullivan
• Re: RSOC name
  • From: Joel M. Halpern
• Re: RSOC name
  • From: Stephen Farrell
• Re: [Lsr] Last Call: <draft-ietf-ospf-yang-23.txt> (YANG Data Model for OSPF Protocol) to Proposed Standard
  • From: Acee Lindem (acee)
• Re: RSOC name
  • From: Michael StJohns
• Re: Genart last call review of draft-ietf-ospf-yang-23
  • From: Acee Lindem (acee)
• Re: The mailing list web archive seems broken
  • From: Benjamin Kaduk
• Re: A few individual comments based on tonight's discussions
  • From: Melinda Shore
• Re: RSOC name
  • From: Stan Kalisch
• Re: RSOC name
  • From: Stephen Farrell
• Re: RSOC name
  • From: Ted Lemon
• Re: RSOC name
  • From: Mike StJohns
• RSOC name
  • From: Donald Eastlake
• Re: Should IETF stop using GitHub?
  • From: Nico Williams
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Michael StJohns
• Re: Should IETF stop using GitHub?
  • From: Brian E Carpenter
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Stephen Farrell
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Michael Richardson
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Michael Richardson
• Re: A few individual comments based on tonight's discussions
  • From: Michael StJohns
• Re: A few individual comments based on tonight's discussions
  • From: Pete Resnick
• Re: Should IETF stop using GitHub?
  • From: Livingood, Jason
• Re: Yangdoctors last call review of draft-ietf-ospf-yang-23
  • From: Acee Lindem (acee)
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Joel M. Halpern
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Wes Hardaker
• Re: Should IETF stop using GitHub?
  • From: Leif Johansson
• Re: Should IETF stop using GitHub?
  • From: Michael StJohns
• Should IETF stop using GitHub?
  • From: Stewart Bryant
• Secdir review of draft-ietf-lamps-cms-hash-sig-08
  • From: Radia Perlman
• Re: A few individual comments based on tonight's discussions
  • From: Martin Thomson
• Re: We gotta stop meeting like this
  • From: Keith Moore
• Re: We gotta stop meeting like this
  • From: Keith Moore
• Re: We gotta stop meeting like this
  • From: Rob Sayre
• Re: We gotta stop meeting like this
  • From: Ted Lemon
• Re: We gotta stop meeting like this
  • From: Keith Moore
• Re: We gotta stop meeting like this
  • From: Rob Sayre
• Re: We gotta stop meeting like this
  • From: Ted Lemon
• Re: We gotta stop meeting like this
  • From: Rob Sayre
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Keith Moore
• Re: We gotta stop meeting like this
  • From: Rob Sayre
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Michael StJohns
• RE: We gotta stop meeting like this
  • From: Andrew Alston
• Re: Leading a moving target
  • From: Mark Andrews
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Livingood, Jason
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Ole Jacobsen
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Brian E Carpenter
• Re: RFC Series Editor (RSE) Statement of Work
  • From: Brian E Carpenter
• Re: We gotta stop meeting like this
  • From: Ted Lemon
• Re: We gotta stop meeting like this
  • From: Rob Sayre