IP Version 6 Working Group Discussion Archive - Thread Index

• Consensus call on adopting: draft-carpenter-6man-uri-zoneid-01.txt, Brian Haberman
  • Re: Consensus call on adopting: draft-carpenter-6man-uri-zoneid-01.txt, Kerry Lynn
    • Message not available
      • Re: Consensus call on adopting: draft-carpenter-6man-uri-zoneid-01.txt, Tim Chown
  • Re: Consensus call on adopting: draft-carpenter-6man-uri-zoneid-01.txt, Roger Jørgensen
• [Fwd: I-D Action: draft-carpenter-6man-uri-zoneid-01.txt], Brian E Carpenter
• Protocol Action: 'RFC3627 to Historic status' to Informational RFC (draft-ietf-6man-3627-historic-01.txt), The IESG
• Protocol Action: 'An uniform format for IPv6 extension headers' to Proposed Standard (draft-ietf-6man-exthdr-06.txt), The IESG
• Fwd: I-D Action: draft-cai-softwire-6rd-mib-01.txt, Shishio Tsuchiya
• Querry regarding Hop-by-Hop extension header processing., sreenatha
• I-D Action: draft-ietf-6man-ipv6-atomic-fragments-00.txt, internet-drafts
• Fwd: RA-Guard: Advice on the implementation (feedback requested), Fernando Gont
• A small survey of support of IPv6 atomic fragments, Fernando Gont
  • Re: A small survey of support of IPv6 atomic fragments, Fernando Gont
    • Re: A small survey of support of IPv6 atomic fragments, Timothy Hartrick
• Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Brian E Carpenter
  • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Fernando Gont
    • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Brian E Carpenter
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Fernando Gont
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Brian E Carpenter
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Fernando Gont
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Brian E Carpenter
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Fernando Gont
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Brian Haberman
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Fernando Gont
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Brian E Carpenter
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Fernando Gont
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Brian E Carpenter
      • Re: I-D Action: draft-gont-6man-flowlabel-security-02.txt, Fernando Gont
• re: draft-gashinsky-6man-v6nd-enhance-00 comments..., Joel jaeggli
• ID Tracker State Update Notice: RFC 2874, The IESG
• [Editorial Errata Reported] RFC6434 (3091), RFC Errata System
  • Re: [Editorial Errata Reported] RFC6434 (3091), Brian Haberman
    • Re: [Editorial Errata Reported] RFC6434 (3091), Sam Silvester
      • Re: [Editorial Errata Reported] RFC6434 (3091), Brian Haberman
      • Re: [Editorial Errata Reported] RFC6434 (3091), Thomas Narten
      • RE: [Editorial Errata Reported] RFC6434 (3091), john.loughney
      • Re: [Editorial Errata Reported] RFC6434 (3091), Tom Taylor
• Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments, Brian Haberman
  • Re: Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments, Simon Perreault
  • Re: Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments, Arturo Servin
    • Reassembly of atomic fragments (was: Re: Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments), Fernando Gont
      • Re: Reassembly of atomic fragments (was: Re: Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments), Arturo Servin
  • Re: Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments, Tore Anderson
  • Re: Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments, Timothy Hartrick
  • Re: Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments, Brian Haberman
  • <Possible follow-ups>
  • Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments, RJ Atkinson
    • Re: Consensus call on adopting: draft-gont-6man-ipv6-atomic-fragments, Tina TSOU
• [Technical Errata Reported] RFC5722 (3089), RFC Errata System
  • Re: [Technical Errata Reported] RFC5722 (3089), Simon Perreault
  • Re: [Technical Errata Reported] RFC5722 (3089), Fernando Gont
  • Re: [Technical Errata Reported] RFC5722 (3089), gorry
    • Re: [Technical Errata Reported] RFC5722 (3089), Fernando Gont
• New revision of draft-gont-6man-flowlabel-security, Fernando Gont
  • Re: New revision of draft-gont-6man-flowlabel-security, Florian Weimer
    • Re: New revision of draft-gont-6man-flowlabel-security, Fernando Gont
• RE:Pre-draft: SEAL as an IPv6 extension header(was:Fragmentation-related Security issues) (Templin, Fred L), Sreenatha setty
  • RE: RE:Pre-draft: SEAL as an IPv6 extension header(was:Fragmentation-related Security issues) (Templin, Fred L), Templin, Fred L
    • RE: RE:Pre-draft: SEAL as an IPv6 extension header(was:Fragmentation-related Security issues) (Templin, Fred L), Templin, Fred L
      • RE: RE:Pre-draft: SEAL as an IPv6 extensionheader(was:Fragmentation-related Security issues) (Templin, Fred L), Sreenatha setty
      • RE: RE:Pre-draft: SEAL as an IPv6 extensionheader(was:Fragmentation-related Security issues) (Templin, Fred L), Templin, Fred L
      • The SEAL IPv6 Destination Option, Templin, Fred L
• Fwd: New Version of draft-gont-6man-nd-extension-headers-02.txt, Fernando Gont
• I-D Action: draft-ietf-6man-exthdr-06.txt, internet-drafts
• RE:Pre-draft: SEAL as an IPv6 extension header (was:Fragmentation-related Security issues), Sreenatha setty
  • RE: RE:Pre-draft: SEAL as an IPv6 extension header (was:Fragmentation-related Security issues), Templin, Fred L
• Last Call: <draft-ietf-6man-3627-historic-01.txt> (RFC3627 to Historic status) to Informational RFC, The IESG
• AD review of draft-ietf-6man-3627-historic, Jari Arkko
• FW: New Version Notification for draft-hsingh-6man-enhanced-dad-04.txt, Hemant Singh (shemant)
• ND Proxy and LinkLocal Unicast Packets, HIROKI ISHIBASHI
• [Editorial Errata Reported] RFC6434 (3073), RFC Errata System
• Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Brian E Carpenter
  • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Karl Auer
  • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Brian E Carpenter
    • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Brian Haberman
  • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Tomoyuki Sahara
    • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, t.petch
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Brian E Carpenter
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, t.petch
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Brian E Carpenter
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, JINMEI Tatuya / 神明達哉
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Brian Haberman
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Brian E Carpenter
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Fernando Gont
  • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Juergen Schoenwaelder
    • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, t.petch
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Juergen Schoenwaelder
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Brian E Carpenter
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Juergen Schoenwaelder
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, Brian E Carpenter
      • Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt, t.petch
• Atomic fragments: converging on something?, Fernando Gont
  • Re: Atomic fragments: converging on something?, Mohacsi Janos
  • Re: Atomic fragments: converging on something?, Timothy Hartrick
    • Re: Atomic fragments: converging on something?, Fernando Gont
      • Re: Atomic fragments: converging on something?, Rémi Després
      • Re: Atomic fragments: converging on something?, Fernando Gont
      • Re: Atomic fragments: converging on something?, Rémi Després
• Request To Advance: draft-ietf-6man-3627-historic-01.txt, Brian Haberman
• Requests for agenda time, Brian Haberman
  • Re: Requests for agenda time, Brian Haberman
• Re: Prefix Delegation questions, Ming-Hong Wu
  • Re: Prefix Delegation questions, Ole Troan
    • Re: Prefix Delegation questions, Ming-Hong Wu
      • Re: Prefix Delegation questions, Alexandru Petrescu
• I-D Action: draft-ietf-6man-udpzero-05.txt, internet-drafts
• Re: [TICTOC] IPv6 Router Advertisement Option for NTP Server Configuration, Dave Hart
• RFC 6434 on IPv6 Node Requirements, rfc-editor
• New IETF I-D on IPv6 smurf amplifiers, Fernando Gont
  • RE: New IETF I-D on IPv6 smurf amplifiers, Eric Vyncke (evyncke)
    • Re: New IETF I-D on IPv6 smurf amplifiers, Fernando Gont
• Protocol Action: 'An IPv6 Routing Header for Source Routes with RPL' to Proposed Standard (draft-ietf-6man-rpl-routing-header-07.txt), The IESG
• Protocol Action: 'RPL Option for Carrying RPL Information in Data-Plane Datagrams' to Proposed Standard (draft-ietf-6man-rpl-option-06.txt), The IESG
• IPv6 Router Advertisement Option for NTP Server Configuration, Bhatia, Manav (Manav)
  • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Doug Barton
    • IPv6 Router Advertisement Option for Foobar Configuration, Brian E Carpenter
      • Re: IPv6 Router Advertisement Option for Foobar Configuration, Doug Barton
      • Re: IPv6 Router Advertisement Option for Foobar Configuration, Brian E Carpenter
      • Re: IPv6 Router Advertisement Option for Foobar Configuration, Doug Barton
      • Re: IPv6 Router Advertisement Option for Foobar Configuration, Roger Jørgensen
      • RE: IPv6 Router Advertisement Option for Foobar Configuration, STARK, BARBARA H
      • Re: IPv6 Router Advertisement Option for Foobar Configuration, Jared Mauch
      • Re: IPv6 Router Advertisement Option for Foobar Configuration, Warren Kumari
    • RE: IPv6 Router Advertisement Option for NTP Server Configuration, Bhatia, Manav (Manav)
      • RE: IPv6 Router Advertisement Option for NTP Server Configuration, Samita Chakrabarti
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Hing-Kam (Kam) Lam
      • RE: IPv6 Router Advertisement Option for NTP Server Configuration, Wuyts Carl
      • re: IPv6 Router Advertisement Option for NTP Server Configuration, Dacheng Zhang(Dacheng)
      • RE: IPv6 Router Advertisement Option for NTP Server Configuration, Eric Vyncke (evyncke)
      • RE: IPv6 Router Advertisement Option for NTP Server Configuration, Bhatia, Manav (Manav)
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Sander Steffann
      • 答复: IPv6 Router Advertisement Option for NTP Server Configuration, Dacheng Zhang(Dacheng)
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Sander Steffann
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Simon Perreault
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Warren Kumari
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Doug Barton
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Brian E Carpenter
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Scott Schmit
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, sthaug
  • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Brian Haberman
    • RE: IPv6 Router Advertisement Option for NTP Server Configuration, Bhatia, Manav (Manav)
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Brian Haberman
      • Re: IPv6 Router Advertisement Option for NTP Server Configuration, Bjoern A. Zeeb
• draft-ietf-6man-rpl-routing-header-07, Park, Kundok
  • RE: draft-ietf-6man-rpl-routing-header-07, Park, Kundok
    • Re: draft-ietf-6man-rpl-routing-header-07, Robert Cragie
      • Re: draft-ietf-6man-rpl-routing-header-07, Jonathan Hui
      • Re: draft-ietf-6man-rpl-routing-header-07, Mukul Goyal
      • Re: draft-ietf-6man-rpl-routing-header-07, Jonathan Hui
      • Re: draft-ietf-6man-rpl-routing-header-07, Mukul Goyal
      • Re: draft-ietf-6man-rpl-routing-header-07, Jonathan Hui
      • Re: draft-ietf-6man-rpl-routing-header-07, Mukul Goyal
      • Re: draft-ietf-6man-rpl-routing-header-07, Jonathan Hui
      • Re: draft-ietf-6man-rpl-routing-header-07, Mukul Goyal
      • Re: draft-ietf-6man-rpl-routing-header-07, Jonathan Hui
      • Re: draft-ietf-6man-rpl-routing-header-07, Mukul Goyal
      • Re: draft-ietf-6man-rpl-routing-header-07, Jonathan Hui
      • Re: draft-ietf-6man-rpl-routing-header-07, Robert Cragie
      • Re: draft-ietf-6man-rpl-routing-header-07, Jonathan Hui (johui)
      • Re: draft-ietf-6man-rpl-routing-header-07, Mukul Goyal
  • draft-ietf-6man-rpl-routing-header-07, Mukul Goyal
  • <Possible follow-ups>
  • Re: draft-ietf-6man-rpl-routing-header-07, Mukul Goyal
    • Re: draft-ietf-6man-rpl-routing-header-07, Jonathan Hui
      • Re: draft-ietf-6man-rpl-routing-header-07, Mukul Goyal
• I-D Action: draft-ietf-6man-3627-historic-01.txt, internet-drafts
• Question on IPV4/IPV6 Multicast interoperability, Ghanashyam Satpathy
  • RE: Question on IPV4/IPV6 Multicast interoperability, Tina TSOU
    • Re: Question on IPV4/IPV6 Multicast interoperability, Ghanashyam Satpathy
      • Re: Question on IPV4/IPV6 Multicast interoperability, Simon Perreault
• Some feedback on draft-andrews-6man-force-fragmentation-00, Fernando Gont
• I-D Action: draft-ietf-6man-rpl-routing-header-07.txt, internet-drafts
• Fragmentation-related security issues, Fernando Gont
  • Re: Fragmentation-related security issues, Mark Andrews
    • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Mark Andrews
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Mark Andrews
      • Re: Fragmentation-related security issues, Fernando Gont
  • Re: Fragmentation-related security issues, Florian Weimer
    • Re: Fragmentation-related security issues, sthaug
      • Re: Fragmentation-related security issues, Mark Andrews
      • Re: Fragmentation-related security issues, sthaug
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Mark Andrews
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Bjoern A. Zeeb
      • Re: Fragmentation-related security issues, sthaug
      • Re: Fragmentation-related security issues, Bjoern A. Zeeb
      • Re: Fragmentation-related security issues, sthaug
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Bjoern A. Zeeb
      • Re: Fragmentation-related security issues, Mark Andrews
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, sthaug
      • Re: Fragmentation-related security issues, sthaug
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Mark Andrews
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Fernando Gont
      • RE: Fragmentation-related security issues, Dan Wing
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Bjoern A. Zeeb
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Bjoern A. Zeeb
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Fernando Gont
    • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Brian E Carpenter
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Vishwas Manral
      • RE: Fragmentation-related security issues, Dan Wing
      • Re: Fragmentation-related security issues, Fernando Gont
      • RE: Fragmentation-related security issues, Dan Wing
      • Re: Fragmentation-related security issues, Brian E Carpenter
      • RE: Fragmentation-related security issues, Dan Wing
      • Message not available
      • RE: Fragmentation-related security issues, Dan Wing
      • RE: Fragmentation-related security issues, Manfredi, Albert E
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Fernando Gont
      • Message not available
      • RE: Fragmentation-related security issues, Dan Wing
      • Message not available
      • RE: Fragmentation-related security issues, ChenGang
      • Re: Fragmentation-related security issues, Jared Mauch
      • Re: Fragmentation-related security issues, Doug Barton
      • Re: Fragmentation-related security issues, Jared Mauch
      • RE: Fragmentation-related security issues, Dan Wing
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Doug Barton
      • RE: Fragmentation-related security issues, Eric Vyncke (evyncke)
      • Re: Fragmentation-related security issues, Doug Barton
      • RE: Fragmentation-related security issues, Dan Wing
      • Re: Fragmentation-related security issues, Jared Mauch
      • RE: Fragmentation-related security issues, Dan Wing
      • Re: Fragmentation-related security issues, Jared Mauch
      • RE: Fragmentation-related security issues, Dan Wing
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Tina TSOU
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Doug Barton
      • Re: Fragmentation-related security issues, Mark Andrews
      • Re: Fragmentation-related security issues, sthaug
      • Re: Fragmentation-related security issues, Doug Barton
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Tore Anderson
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Tore Anderson
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, Tore Anderson
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Philip Homburg
      • Fragment ID generation and Flow Label generation (was: Re: Fragmentation-related security issues), Fernando Gont
      • Re: Fragment ID generation and Flow Label generation, Fernando Gont
      • Re: Fragment ID generation and Flow Label generation, Brian E Carpenter
      • Re: Fragment ID generation and Flow Label generation, Fernando Gont
      • Re: Fragment ID generation and Flow Label generation (was: Re: Fragmentation-related security issues), Philip Homburg
    • RE: Fragmentation-related security issues, Dan Wing
  • RE: Fragmentation-related security issues, Templin, Fred L
  • <Possible follow-ups>
  • Re: Fragmentation-related security issues, RJ Atkinson
    • Re: Fragmentation-related security issues, Fernando Gont
  • Re: Fragmentation-related security issues, RJ Atkinson
    • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, RJ Atkinson
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, RJ Atkinson
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, RJ Atkinson
      • Re: Fragmentation-related security issues, Philip Homburg
      • Re: Fragmentation-related security issues, RJ Atkinson
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, RJ Atkinson
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Shane Amante
  • Re: Fragmentation-related security issues, RJ Atkinson
    • Re: Fragmentation-related security issues, Doug Barton
  • Re: Fragmentation-related security issues, RJ Atkinson
    • Re: Fragmentation-related security issues, Brian E Carpenter
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Fernando Gont
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Brian E Carpenter
      • Re: Fragmentation-related security issues, Jared Mauch
      • Re: Fragmentation-related security issues, Mark Andrews
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Fernando Gont
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Joel M. Halpern
      • To firewall or not to firewall (was: Re: Fragmentation-related security issues), Fernando Gont
      • Re: To firewall or not to firewall (was: Re: Fragmentation-related security issues), Jared Mauch
      • Re: To firewall or not to firewall, Brian E Carpenter
      • RE: To firewall or not to firewall (was: Re: Fragmentation-related security issues), Templin, Fred L
      • Re: Fragmentation-related security issues, Fernando Gont
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Havard Eidnes
      • RE: Fragmentation-related security issues, Eric Vyncke (evyncke)
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Brian E Carpenter
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Brian Haberman
      • Re: Fragmentation-related security issues, Brian E Carpenter
      • Re: Fragmentation-related security issues, Florian Weimer
      • Re: Fragmentation-related security issues, Fernando Gont
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Re: Fragmentation-related security issues, Florian Weimer
      • RE: Fragmentation-related security issues, Templin, Fred L
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Pre-draft: SEAL as an IPv6 extension header (was: Fragmentation-related Security issues), Templin, Fred L
      • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, Brian E Carpenter
      • RE: Fragmentation-related security issues, Templin, Fred L
      • Non-traditional PMTUD [was Re: Fragmentation-related security issues], Brian E Carpenter
      • Re: Non-traditional PMTUD [was Re: Fragmentation-related security issues], Fernando Gont
      • Re: Non-traditional PMTUD [was Re: Fragmentation-related security issues], Fred Baker
      • Re: Non-traditional PMTUD [was Re: Fragmentation-related security issues], Brian E Carpenter
    • Re: Fragmentation-related security issues, Fernando Gont
      • Re: Fragmentation-related security issues, RJ Atkinson
      • Re: Fragmentation-related security issues, Fernando Gont
• New IETF I-D on "Stable Privacy Addresses", Fernando Gont
• I-D Action: draft-ietf-6man-rpl-routing-header-06.txt, internet-drafts
• I-D Action: draft-ietf-6man-rpl-option-06.txt, internet-drafts
  • RE: I-D Action: draft-ietf-6man-rpl-option-06.txt, Park, Kundok
    • Re: I-D Action: draft-ietf-6man-rpl-option-06.txt, Jonathan Hui
      • RE: I-D Action: draft-ietf-6man-rpl-option-06.txt, Park, Kundok
      • Re: I-D Action: draft-ietf-6man-rpl-option-06.txt, Jonathan Hui
      • RE: I-D Action: draft-ietf-6man-rpl-option-06.txt, Park, Kundok
      • Re: I-D Action: draft-ietf-6man-rpl-option-06.txt, Jonathan Hui
• draft-andrews-6man-force-fragmentation-00.txt, Mark Andrews
  • Re: draft-andrews-6man-force-fragmentation-00.txt, Simon Perreault
    • Re: draft-andrews-6man-force-fragmentation-00.txt, Mark Andrews
• RE: Mail regarding draft-ietf-6man-node-req-bis, john.loughney
• Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC, Jari Arkko
  • Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC, Basavaraj.Patil
    • Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC, Sri Gundavelli
      • Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC, Basavaraj.Patil
      • Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC, Sri Gundavelli
• please review new version of the enhanced-dad draft, Hemant Singh (shemant)
• [Fwd: I-D Action: draft-carpenter-6man-uri-zoneid-00.txt], Brian E Carpenter
  • Re: [Fwd: I-D Action: draft-carpenter-6man-uri-zoneid-00.txt], Brian Haberman
    • Re: [Fwd: I-D Action: draft-carpenter-6man-uri-zoneid-00.txt], Brian E Carpenter
• Re: draft-andrews-dnsext-ipv6-fragmentation, Mark Andrews
• Character set for Line ID, Suresh Krishnan
  • Re: Character set for Line ID, Thomas Narten
    • Re: Character set for Line ID, Bob Hinden
      • Re: Character set for Line ID, Thomas Narten
      • Re: Character set for Line ID, Bob Hinden
      • Re: Character set for Line ID, Suresh Krishnan
  • Re: Character set for Line ID, Glen Turner
    • Re: Character set for Line ID, Suresh Krishnan
  • <Possible follow-ups>
  • Re: Character set for Line ID, RJ Atkinson
    • Re: Character set for Line ID, Bob Hinden
    • Re: Character set for Line ID, Suresh Krishnan
  • Re: Character set for Line ID, RJ Atkinson
  • Re: Character set for Line ID, RJ Atkinson
• 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Brian Haberman
  • Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Brian E Carpenter
  • Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Randy Bush
    • Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Victor Kuarsingh
      • RE: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Tina TSOU
  • Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Tore Anderson
  • Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Arturo Servin
  • Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Matsuzaki Yoshinobu
  • Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Shishio Tsuchiya
    • RE: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Boswell, James
  • Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Warren Kumari
  • RE: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, George, Wes
  • Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt, Brian Haberman
• I-D Action: draft-ietf-6man-3627-historic-00.txt, internet-drafts
  • ready for WGLC? (was RE: I-D Action: draft-ietf-6man-3627-historic-00.txt), George, Wes
• Last Call: <draft-ietf-6man-exthdr-05.txt> (An uniform format for IPv6 extension headers) to Proposed Standard, The IESG
• AD review of draft-ietf-6man-exthdr, Jari Arkko
  • Re: AD review of draft-ietf-6man-exthdr, Suresh Krishnan
• Discussion on feasibility of route configuration over DHCPv6, Tomek Mrugalski
• I-D Action: draft-ietf-6man-rpl-routing-header-05.txt, internet-drafts
• I-D Action: draft-ietf-6man-rpl-option-05.txt, internet-drafts
• New MIF agenda posted, Hui Deng
• I-D Action: draft-ietf-6man-impatient-nud-00.txt, internet-drafts
• further responses for comments at the mic in 6man for draft-hsingh-6man-enhanced-dad-02.txt, Hemant Singh (shemant)
  • RE: further responses for comments at the mic in 6man fordraft-hsingh-6man-enhanced-dad-02.txt, Hemant Singh (shemant)
• Link-local IPv6 addresses in URIs, Kerry Lynn
  • Re: Link-local IPv6 addresses in URIs, Brian E Carpenter
    • Re: Link-local IPv6 addresses in URIs, Brian E Carpenter
      • Re: Link-local IPv6 addresses in URIs, Carsten Bormann
      • Re: Link-local IPv6 addresses in URIs, Kerry Lynn
      • Re: Link-local IPv6 addresses in URIs, Tomoyuki Sahara
      • Re: Link-local IPv6 addresses in URIs, Kerry Lynn
      • Re: Link-local IPv6 addresses in URIs, François-Xavier Le Bail
      • Re: Link-local IPv6 addresses in URIs, François-Xavier Le Bail
      • Re: Link-local IPv6 addresses in URIs, Brian E Carpenter
      • Re: Link-local IPv6 addresses in URIs, François-Xavier Le Bail
      • Re: Link-local IPv6 addresses in URIs, Brian Haberman
      • Re: Link-local IPv6 addresses in URIs, Brian E Carpenter
      • Link-local IPv6 addresses in the DNS, Mark Andrews
      • Re: Link-local IPv6 addresses in the DNS, Philip Homburg
      • Re: Link-local IPv6 addresses in the DNS, Brian E Carpenter
      • Re: Link-local IPv6 addresses in the DNS, Kerry Lynn
      • Re: Link-local IPv6 addresses in the DNS, Kerry Lynn
      • Re: Link-local IPv6 addresses in the DNS, Brian E Carpenter
      • Re: Link-local IPv6 addresses in the DNS, Brian E Carpenter
      • Re: Link-local IPv6 addresses in the DNS, Mark Andrews
      • Re: Link-local IPv6 addresses in the DNS, Philip Homburg
      • RE: Link-local IPv6 addresses in the DNS, Christian Huitema
      • Re: Link-local IPv6 addresses in URIs, Brian Haberman
      • RE: Link-local IPv6 addresses in URIs, Manfredi, Albert E
• multiple policy tables handling in draft-ietf-6man-addr-select-opt-01, Dmitry Anipko
  • Re: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01, Arifumi Matsumoto
    • RE: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01, Dmitry Anipko
      • Re: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01, Arifumi Matsumoto
• draft-ietf-6man-addr-select-considerations-04, Seiichi Kawamura
• Conflict between RA and DHCP in MIF case, Hui Deng
  • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ole Troan
    • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Karl Auer
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ole Troan
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Karl Auer
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Mark Andrews
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Karl Auer
      • Re: Conflict between RA and DHCP in MIF case, Doug Barton
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Mark Andrews
      • RE: [dhcwg] Conflict between RA and DHCP in MIF case, Hemant Singh (shemant)
      • RE: [dhcwg] Conflict between RA and DHCP in MIF case, Hemant Singh (shemant)
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ole Troan
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Karl Auer
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ole Troan
    • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ted Lemon
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ole Troan
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ted Lemon
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ole Troan
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ted Lemon
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Thomas Narten
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ted Lemon
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Marc Blanchet
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ole Troan
      • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ted Lemon
      • Re: [mif] [dhcwg] Conflict between RA and DHCP in MIF case, Tao Sun
  • Re: Conflict between RA and DHCP in MIF case, Karl Auer
  • Re: [mif] Conflict between RA and DHCP in MIF case, Brian E Carpenter
  • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ted Lemon
  • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Mohacsi Janos
    • Re: [dhcwg] Conflict between RA and DHCP in MIF case, Ted Lemon
• Need minute taker and Jabber scribe, Bob Hinden
  • Re: Need minute taker and Jabber scribe, Marshall Eubanks
    • Re: Need minute taker and Jabber scribe, Bob Hinden
• draft-ietf-6man-rpl-option questions, Richard Kelsey
  • Re: draft-ietf-6man-rpl-option questions, Jonathan Hui
  • <Possible follow-ups>
  • Re: draft-ietf-6man-rpl-option questions, Reddy, Joseph
    • Re: draft-ietf-6man-rpl-option questions, Jonathan Hui
      • RE: draft-ietf-6man-rpl-option questions, Reddy, Joseph
• draft-chakrabarti-nordmark-energy-aware-nd-01.txt Published, Samita Chakrabarti
• Some thoughts on draft-ietf-6man-udpchecksums-01, Gorry Fairhurst
• RFC 4443 versus RFC 4942, François-Xavier Le Bail
  • Re: RFC 4443 versus RFC 4942, Washam Fan
    • Re: RFC 4443 versus RFC 4942, François-Xavier Le Bail
• 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Brian Haberman
  • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Chris Grundemann
    • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Brian Haberman
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Roger Jørgensen
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Brian Haberman
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Brian E Carpenter
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Roger Jørgensen
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Brian E Carpenter
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Chris Grundemann
      • RE: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Dave Thaler
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Brian E Carpenter
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Roger Jørgensen
      • Message not available
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Tim Chown
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Brian E Carpenter
      • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Chris Grundemann
      • -06 candidate, Arifumi Matsumoto
      • Re: -06 candidate, Mark Andrews
      • Re: -06 candidate, Brian E Carpenter
      • Re: -06 candidate, Mark Andrews
      • ULA macro in the policy table Re: -06 candidate, Arifumi Matsumoto
      • Re: ULA macro in the policy table Re: -06 candidate, Mark Andrews
      • Re: ULA macro in the policy table Re: -06 candidate, Arifumi Matsumoto
      • Re: ULA macro in the policy table Re: -06 candidate, Mark Andrews
      • Re: -06 candidate, Arifumi Matsumoto
  • <Possible follow-ups>
  • Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt, Brian E Carpenter