IP Version 6 Working Group Discussion Archive - Thread Index

• The results of your email commands, (continued)
  • The results of your email commands, isis-update-bounces
  • The results of your email commands, isms-bounces
  • The results of your email commands, isis-wg-bounces
  • The results of your email commands, isis-update-bounces
  • The results of your email commands, l2tpext-bounces
  • The results of your email commands, isis-wg-bounces
  • The results of your email commands, isms-bounces
  • The results of your email commands, isis-update-bounces
  • The results of your email commands, l2tpext-bounces
  • The results of your email commands, isis-update-bounces
  • The results of your email commands, isis-wg-bounces
  • The results of your email commands, isms-bounces
  • The results of your email commands, l2tpext-bounces
  • The results of your email commands, isis-wg-bounces
  • The results of your email commands, isis-update-bounces
  • The results of your email commands, isms-bounces
  • The results of your email commands, l2tpext-bounces
  • The results of your email commands, isis-wg-bounces
  • The results of your email commands, isms-bounces
  • The results of your email commands, isis-update-bounces
  • The results of your email commands, l2tpext-bounces
  • The results of your email commands, isms-bounces
  • The results of your email commands, isis-wg-bounces
  • The results of your email commands, isis-update-bounces
  • The results of your email commands, l2tpext-bounces
  • The results of your email commands, isis-update-bounces
  • The results of your email commands, isms-bounces
  • The results of your email commands, l2tpext-bounces
  • The results of your email commands, isis-wg-bounces
  • The results of your email commands, isms-bounces
  • The results of your email commands, isis-wg-bounces
  • The results of your email commands, l2tpext-bounces
  • The results of your email commands, isis-update-bounces
• Superior replica watches for you, Karina Bruce
• CFP For HITBSecConf2008 - Malaysia Now Open, Praburaajan
• Fwd: [Int-area] RSVP for IPv6 implementors: your use of RAO value 3, Bob Hinden
  • Re: [Int-area] RSVP for IPv6 implementors: your use of RAO value 3, Vishwas Manral
• Fwd: your comments for 6man, draft-ietf-6man-addr-select-sol-00.txt, Ruri Hiromi
• I-D Action:draft-ietf-6man-ipv6-subnet-model-00.txt, Internet-Drafts
  • RE: I-D Action:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
    • Re: I-D Action:draft-ietf-6man-ipv6-subnet-model-00.txt, Suresh Krishnan
      • RE: I-D Action:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
• Photos and Presentation Materials from HITBSecConf2008 - Dubai Released, Praburaajan
• Rappel : merhaba ben arzu 0546 332 12 20 ara tan?sal?m telefonum arzu ben 0546 332 12 20 et selam ben ece 0546 332 12 20 telefonum ararmisin 0546 332 12 20 tanisalim veulent être ton ami(e), merhaba ben arzu 0546 332 12 20 ara tan?sal?m telefonum arzu ben 0546 332 12 20 et selam ben ece 0546 332 12 20 telefonum ararmisin 0546 332 12 20 tanisalim
  • <Possible follow-ups>
  • Rappel : merhaba ben arzu 0546 332 12 20 ara tan?sal?m telefonum arzu ben 0546 332 12 20 et selam ben ece 0546 332 12 20 telefonum ararmisin 0546 332 12 20 tanisalim veulent être ton ami(e), merhaba ben arzu 0546 332 12 20 ara tan?sal?m telefonum arzu ben 0546 332 12 20 et selam ben ece 0546 332 12 20 telefonum ararmisin 0546 332 12 20 tanisalim
• Etkili ve Ekonomik Reklam, Ucretsiz ve Guvenli Iletisim, Net-Pa ®
• The safest and most secure Online casino in the world......., Kory Vela
• sensitizing, Malachowski Fatheree
• Play at the world's leading online casino....., Arturo Cox
• Come and get your MASSIVE $2400 BONUS NOW!, Jay Patel
• HOW To BLOCK IPv6 ADDRESSES in Windows XP, ather zaidi
  • RE: HOW To BLOCK IPv6 ADDRESSES in Windows XP, Christian Huitema
    • Re: HOW To BLOCK IPv6 ADDRESSES in Windows XP, tom.petch
      • RE: HOW To BLOCK IPv6 ADDRESSES in Windows XP, TJ
• Network Scanning, Prasanna Ram Venkatachalam
  • Re: Network Scanning, Jeroen Massar
    • RE: Network Scanning, Brian McGehee
      • RE: Network Scanning, TJ
      • RE: Network Scanning, Sean Siler
      • Re: Network Scanning, Jeroen Massar
      • RE: Network Scanning, Manfredi, Albert E
      • Re: Network Scanning, David Malone
  • <Possible follow-ups>
  • Re: Network Scanning, Jeroen Massar
• polysyllable, Merila Hadsall
• question about trailing padding of ancillary data chain (RFC3542), JINMEI Tatuya / 神明達哉
• RFC 5172 on Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol, rfc-editor
• ipv6 routing.., vikas *
• viscerogenic, Randy Katzenberger
• node-req-bis - making a note about multicast, Julien Abeillé
  • Re: node-req-bis - making a note about multicast, Thomas Narten
• RFC3484 and ORCHID addresses (fwd), Pekka Savola
  • Re: RFC3484 and ORCHID addresses (fwd), David Malone
  • Re: RFC3484 and ORCHID addresses (fwd), Brian E Carpenter
• RFC3484 destination address selection rule 2 is buggy, Pekka Savola
  • Re: RFC3484 destination address selection rule 2 is buggy, Francis Dupont
    • Re: RFC3484 destination address selection rule 2 is buggy, Alain Durand
    • Re: RFC3484 destination address selection rule 2 is buggy, Pekka Savola
      • Re: RFC3484 destination address selection rule 2 is buggy, Francis Dupont
      • Re: RFC3484 destination address selection rule 2 is buggy, Sebastien Roy
    • Re: RFC3484 destination address selection rule 2 is buggy, Rémi Denis-Courmont
    • Re: RFC3484 destination address selection rule 2 is buggy, Sebastien Roy
  • Re: RFC3484 destination address selection rule 2 is buggy, Rémi Denis-Courmont
    • Re: RFC3484 destination address selection rule 2 is buggy, Mohacsi Janos
  • Re: RFC3484 destination address selection rule 2 is buggy, JINMEI Tatuya / 神明達哉
    • Re: RFC3484 destination address selection rule 2 is buggy, Pekka Savola
      • RE: RFC3484 destination address selection rule 2 is buggy, Hemant Singh (shemant)
      • Re: RFC3484 destination address selection rule 2 is buggy, JINMEI Tatuya / 神明達哉
      • Re: RFC3484 destination address selection rule 2 is buggy, Pekka Savola
  • <Possible follow-ups>
  • Re: RFC3484 destination address selection rule 2 is buggy, Gabi Nakibly
    • Re: RFC3484 destination address selection rule 2 is buggy, Fred Baker
      • Re: RFC3484 destination address selection rule 2 is buggy, Sebastien Roy
      • Re: RFC3484 destination address selection rule 2 is buggy, Brian E Carpenter
      • Re: RFC3484 destination address selection rule 2 is buggy, Fred Baker
      • Re: RFC3484 destination address selection rule 2 is buggy, Bob Hinden
      • RE: RFC3484 destination address selection rule 2 is buggy, Hemant Singh (shemant)
      • Re: RFC3484 destination address selection rule 2 is buggy, Fred Baker
      • Re: RFC3484 destination address selection rule 2 is buggy, Brian E Carpenter
      • Re: RFC3484 destination address selection rule 2 is buggy, Bob Hinden
      • Re: RFC3484 destination address selection rule 2 is buggy, Fred Baker
  • Re: RFC3484 destination address selection rule 2 is buggy, Gabi Nakibly
    • Re: RFC3484 destination address selection rule 2 is buggy, Sebastien Roy
• Need Jabber scribe and minute taker for 6man, Bob Hinden
• Review of draft-wbeebee-on-link-and-off-link-determination-02, Suresh Krishnan
  • RE: Review of draft-wbeebee-on-link-and-off-link-determination-02, Wes Beebee (wbeebee)
    • Re: Review of draft-wbeebee-on-link-and-off-link-determination-02, Ralph Droms
      • Re: Review of draft-wbeebee-on-link-and-off-link-determination-02, Ralph Droms
      • Re: Review of draft-wbeebee-on-link-and-off-link-determination-02, Erik Nordmark
      • RE: Review of draft-wbeebee-on-link-and-off-link-determination-02, Manfredi, Albert E
      • Re: Review of draft-wbeebee-on-link-and-off-link-determination-02, JINMEI Tatuya / 神明達哉
      • RE: Review of draft-wbeebee-on-link-and-off-link-determination-02, Hemant Singh (shemant)
      • Re: Review of draft-wbeebee-on-link-and-off-link-determination-02, Erik Nordmark
      • Re: Review of draft-wbeebee-on-link-and-off-link-determination-02, JINMEI Tatuya / 神明達哉
      • Re: Review of draft-wbeebee-on-link-and-off-link-determination-02, Ralph Droms
  • Re: Review of draft-wbeebee-on-link-and-off-link-determination-02, Erik Nordmark
• draft-krishnan-ipv6-exthdr-01, JINMEI Tatuya / 神明達哉
• 6man Agenda for the Philadelphia IETF Updated, ext Bob Hinden
• RFC 5175 on IPv6 Router Advertisement Flags Option, rfc-editor
• RE: Security Requirements for IPv6 Node Req summary, Tim Enos
  • Re: Security Requirements for IPv6 Node Req summary, Vishwas Manral
    • RE: Security Requirements for IPv6 Node Req summary, Dunn, Jeffrey H.
      • Re: Security Requirements for IPv6 Node Req summary, Brian E Carpenter
      • RE: Security Requirements for IPv6 Node Req summary, Dunn, Jeffrey H.
      • Re: Security Requirements for IPv6 Node Req summary, Brian E Carpenter
      • Re: Security Requirements for IPv6 Node Req summary, Bob Hinden
      • Re: Security Requirements for IPv6 Node Req summary, Brian E Carpenter
      • Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, james woodyatt
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Suresh Krishnan
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Vishwas Manral
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Vishwas Manral
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Vishwas Manral
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, JINMEI Tatuya / 神明達哉
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, JINMEI Tatuya / 神明達哉
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Suresh Krishnan
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Manfredi, Albert E
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Suresh Krishnan
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Markku Savela
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Suresh Krishnan
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Manfredi, Albert E
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Suresh Krishnan
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Manfredi, Albert E
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Suresh Krishnan
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Manfredi, Albert E
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Suresh Krishnan
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Markku Savela
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Manfredi, Albert E
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Vishwas Manral
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Manfredi, Albert E
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Suresh Krishnan
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Brian E Carpenter
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Suresh Krishnan
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Vishwas Manral
      • Re: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Jim Hoagland
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
      • Distinguishing unknown extension headers and unknown upper layer headers (Was: Review comments for draft-krishnan-ipv6-exthdr-01.txt), Jim Hoagland
      • RE: Review comments for draft-krishnan-ipv6-exthdr-01.txt, Hemant Singh (shemant)
  • <Possible follow-ups>
  • Re: Security Requirements for IPv6 Node Req summary, Tim Enos
• 6man Agenda for the Philadelphia IETF, Bob Hinden
  • Security Requirements for IPv6 Node Req summary, john.loughney
    • Re: Security Requirements for IPv6 Node Req summary, Vishwas Manral
      • RE: Security Requirements for IPv6 Node Req summary, john.loughney
      • Re: Security Requirements for IPv6 Node Req summary, Brian E Carpenter
      • Re: Security Requirements for IPv6 Node Req summary, Bob Hinden
      • RE: Security Requirements for IPv6 Node Req summary, Dunn, Jeffrey H.
      • Re: Security Requirements for IPv6 Node Req summary, Vishwas Manral
      • RE: Security Requirements for IPv6 Node Req summary, Dunn, Jeffrey H.
      • RE: Security Requirements for IPv6 Node Req summary, Manfredi, Albert E
      • RE: Security Requirements for IPv6 Node Req summary, Tony Hain
      • Re: Security Requirements for IPv6 Node Req summary, Vishwas Manral
      • Re: Security Requirements for IPv6 Node Req summary, Brian E Carpenter
      • Re: Security Requirements for IPv6 Node Req summary, Vishwas Manral
      • RE: Security Requirements for IPv6 Node Req summary, Dunn, Jeffrey H.
• RE: ipv6 Digest, Vol 46, Issue 33, Mike Taylor
  • Re: ipv6 Digest, Vol 46, Issue 33, Ed Jankiewicz
  • IPv6 as an export issue, Thomas Narten
    • Re: IPv6 as an export issue, Alexandru Petrescu
  • <Possible follow-ups>
  • Re: ipv6 Digest, Vol 46, Issue 33, mtaylor . design
    • Re: ipv6 as an export issue, Ed Jankiewicz
      • Re: ipv6 as an export issue, Eric Klein
      • Re: ipv6 as an export issue, Merike Kaeo
• FW: [Int-area] FW: [RRG] Subnetwork Encapsulation and Adaptation Layer(SEAL), Templin, Fred L
• FW: Making IPsec *not* mandatory in Node Requirement, Julien Abeille (jabeille)
• Use longest-matching prefix to the next hop, FUJIKAWA Kenji
  • RE: Use longest-matching prefix to the next hop, Hemant Singh (shemant)
    • Re: Use longest-matching prefix to the next hop, FUJIKAWA Kenji
      • RE: Use longest-matching prefix to the next hop, Hemant Singh (shemant)
      • RE: Use longest-matching prefix to the next hop, Hemant Singh (shemant)
      • Re: Use longest-matching prefix to the next hop, FUJIKAWA Kenji
    • Re: Use longest-matching prefix to the next hop, arifumi
      • RE: Use longest-matching prefix to the next hop, Hemant Singh (shemant)
• FW: New Version Notification for draft-wbeebee-on-link-and-off-link-determination-02, Hemant Singh (shemant)
  • Re: FW: New Version Notification for draft-wbeebee-on-link-and-off-link-determination-02, JINMEI Tatuya / 神明達哉
    • RE: FW: New Version Notification for draft-wbeebee-on-link-and-off-link-determination-02, Hemant Singh (shemant)
• I-D Action:draft-ietf-6man-node-req-bis-01.txt, Internet-Drafts
• Updates to Node Requirements-bis, john.loughney
  • Re: Updates to Node Requirements-bis, Bob Hinden
  • RE: Updates to Node Requirements-bis, Hemant Singh (shemant)
    • RE: Updates to Node Requirements-bis (UNCLASSIFIED), Duncan, Richard J CTR DISA JITC
      • RE: Updates to Node Requirements-bis (UNCLASSIFIED), john.loughney
      • RE: Updates to Node Requirements-bis (UNCLASSIFIED), Duncan, Richard J CTR DISA JITC
      • Re: Updates to Node Requirements-bis (UNCLASSIFIED), Ed Jankiewicz
      • RE: Updates to Node Requirements-bis (UNCLASSIFIED), john.loughney
      • RE: Updates to Node Requirements-bis (UNCLASSIFIED), Manfredi, Albert E
      • Re: Updates to Node Requirements-bis, Brian E Carpenter
      • RE: Updates to Node Requirements-bis, Manfredi, Albert E
      • RE: Updates to Node Requirements-bis, Dunn, Jeffrey H.
      • RE: Updates to Node Requirements-bis, Bound, Jim
      • Re: Updates to Node Requirements-bis (UNCLASSIFIED), Fred Baker
      • RE: Updates to Node Requirements-bis (UNCLASSIFIED), Pekka Savola
      • RE: Updates to Node Requirements-bis (UNCLASSIFIED), Manfredi, Albert E
      • Re: Updates to Node Requirements-bis (UNCLASSIFIED), Vishwas Manral
      • RE: Updates to Node Requirements-bis (UNCLASSIFIED), Manfredi, Albert E
      • IGPs [Re: Updates to Node Requirements-bis], Brian E Carpenter
      • Re: Updates to Node Requirements-bis (UNCLASSIFIED), Fred Baker
      • Making IPsec *not* mandatory in Node Requirement ( was Re: Updates to Node Requirements-bis (UNCLASSIFIED)), Alain Durand
      • Re: Making IPsec *not* mandatory in Node Requirement, Nobuo OKABE
      • Re: Making IPsec *not* mandatory in Node Requirement, Alain Durand
      • Re: Making IPsec *not* mandatory in Node Requirement, Nobuo OKABE
      • the role of the node "requirements" document, Pekka Savola
      • RE: the role of the node "requirements" document, Hemant Singh (shemant)
      • Re: the role of the node "requirements" document, Brian Haberman
      • RE: the role of the node "requirements" document, john.loughney
      • RE: the role of the node "requirements" document, Hemant Singh (shemant)
      • Re: the role of the node "requirements" document, Ed Jankiewicz
      • Re: the role of the node "requirements" document, Brian E Carpenter
      • RE: the role of the node "requirements" document, Julien Abeille (jabeille)
      • RE: the role of the node "requirements" document, michael.dillon
      • RE: the role of the node "requirements" document, michael.dillon
      • RE: the role of the node "requirements" document, Hemant Singh (shemant)
      • Re: the role of the node "requirements" document, Ed Jankiewicz
      • Re: the role of the node "requirements" document, James Carlson
      • RE: the role of the node "requirements" document, john.loughney
      • Re: the role of the node "requirements" document, Thomas Narten
      • Re: the role of the node "requirements" document, James Carlson
      • Re: the role of the node "requirements" document, Jean-Michel Combes
      • RE: the role of the node "requirements" document, Bound, Jim
      • RE: the role of the node "requirements" document, James Carlson
      • Re: the role of the node "requirements" document, Ed Jankiewicz
      • Re: the role of the node "requirements" document, Dow Street
      • RE: the role of the node "requirements" document, Kevin Kargel
      • Re: the role of the node "requirements" document, Sean Lawless
      • RE: the role of the node "requirements" document, Manfredi, Albert E
      • RE: the role of the node "requirements" document, Kevin Kargel
      • RE: the role of the node "requirements" document, john.loughney
      • Re: the role of the node "requirements" document, Dow Street
      • RE: the role of the node "requirements" document, Kevin Kargel
      • RE: the role of the node "requirements" document, Patrick Grossetete
      • Re: the role of the node "requirements" document, James Carlson
      • Re: the role of the node "requirements" document, Brian E Carpenter
      • Re: the role of the node "requirements" document, Ed Jankiewicz
      • RE: the role of the node "requirements" document, Julien Abeille (jabeille)
      • RE: the role of the node "requirements" document, john.loughney
      • RE: the role of the node "requirements" document, Julien Abeille (jabeille)
      • Re: the role of the node "requirements" document, Nobuo OKABE
      • RE: the role of the node "requirements" document, Bound, Jim
      • RE: the role of the node "requirements" document, Dunn, Jeffrey H.
      • Re: the role of the node "requirements" document, james woodyatt
      • Re: the role of the node "requirements" document, Thomas Narten
      • Re: Making IPsec *not* mandatory in Node Requirement, Thomas Narten
      • Re: Making IPsec *not* mandatory in Node Requirement, Vishwas Manral
      • Re: Making IPsec *not* mandatory in Node Requirement, Basavaraj Patil
      • Re: Making IPsec *not* mandatory in Node Requirement, Vishwas Manral
      • Re: Making IPsec *not* mandatory in Node Requirement, Basavaraj Patil
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • Re: Making IPsec *not* mandatory in Node Requirement, Jean-Michel Combes
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • RE: Making IPsec *not* mandatory in Node Requirement, Julien Abeille (jabeille)
      • RE: Making IPsec *not* mandatory in Node Requirement, john.loughney
      • RE: Making IPsec *not* mandatory in Node Requirement, Julien Abeille (jabeille)
      • Re: Making IPsec *not* mandatory in Node Requirement, Thomas Narten
      • RE: Making IPsec *not* mandatory in Node Requirement, Kevin Kargel
      • RE: Making IPsec *not* mandatory in Node Requirement, Julien Abeille (jabeille)
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • RE: Making IPsec *not* mandatory in Node Requirement, Julien Abeille (jabeille)
      • RE: Making IPsec *not* mandatory in Node Requirement, john.loughney
      • RE: Making IPsec *not* mandatory in Node Requirement, Julien Abeille (jabeille)
      • RE: Making IPsec *not* mandatory in Node Requirement, john.loughney
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • Re: Making IPsec *not* mandatory in Node Requirement, Ed Jankiewicz
      • RE: Making IPsec *not* mandatory in Node Requirement, Manfredi, Albert E
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • RE: Making IPsec *not* mandatory in Node Requirement, Manfredi, Albert E
      • IPsec and 6LoWPAN (was: Re: Making IPsec *not* mandatory in Node Requirement), Jonathan Hui
      • RE: IPsec and 6LoWPAN (was: Re: Making IPsec *not* mandatory in Node Requirement), Bound, Jim
      • RE: IPsec and 6LoWPAN (was: Re: Making IPsec *not* mandatory inNode Requirement), Pascal Thubert (pthubert)
      • Re: IPsec and 6LoWPAN (was: Re: Making IPsec *not* mandatory inNode Requirement), Jonathan Hui
      • RE: IPsec and 6LoWPAN (was: Re: Making IPsec *not* mandatory inNode Requirement), Bound, Jim
      • Re: IPsec and 6LoWPAN (was: Re: Making IPsec *not* mandatory inNode Requirement), Jonathan Hui
      • Re: IPsec and 6LoWPAN (was: Re: Making IPsec *not* mandatory inNode Requirement), Eunsook \"Eunah\" Kim
      • RE: IPsec and 6LoWPAN (was: Re: Making IPsec *not* mandatory inNode Requirement), Bound, Jim
      • RE: IPsec and 6LoWPAN (was: Re: Making IPsec *not* mandatory inNodeRequirement), Pascal Thubert (pthubert)
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • Re: Making IPsec *not* mandatory in Node Requirement, Brian Dickson
      • Re: Making IPsec *not* mandatory in Node Requirement, Vishwas Manral
      • RE: Making IPsec *not* mandatory in Node Requirement, Tony Hain
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • RE: Making IPsec *not* mandatory in Node Requirement, Hemant Singh (shemant)
      • Re: Making IPsec *not* mandatory in Node Requirement, Thomas Narten
      • Re: Making IPsec *not* mandatory in Node Requirement, Julien Laganier
      • Re: Making IPsec *not* mandatory in Node Requirement, James Carlson
      • Re: Making IPsec *not* mandatory in Node Requirement, Julien Laganier
      • Re: Making IPsec *not* mandatory in Node Requirement, Alain Durand
      • Re: Making IPsec *not* mandatory in Node Requirement, Thomas Narten
      • Re: Making IPsec *not* mandatory in Node Requirement, Basavaraj Patil
      • RE: Making IPsec *not* mandatory in Node Requirement, john.loughney
      • Re: Making IPsec *not* mandatory in Node Requirement, Nobuo OKABE
      • RE: Making IPsec *not* mandatory in Node Requirement, Hesham Soliman
      • RE: Making IPsec *not* mandatory in Node Requirement, Bound, Jim
      • Re: Making IPsec *not* mandatory in Node Requirement ( was Re: Updates to Node Requirements-bis (UNCLASSIFIED)), Jean-Michel Combes
      • Re: Making IPsec *not* mandatory in Node Requirement ( was Re: Updates to Node Requirements-bis (UNCLASSIFIED)), Mark Smith
• [no subject], Unknown
• toward sloving the address selection problems, Arifumi Matsumoto
• Update for ikev2-ipv6-config draft, Pasi.Eronen
  • Re: Update for ikev2-ipv6-config draft, Julien Laganier
• Protocol Action: 'Negotiation for IPv6 datagram compression using IPv6 Control Protocol' to Proposed Standard, The IESG
• I-D Action:draft-ietf-6man-reserved-iids-00.txt, Internet-Drafts
• I-D Action:draft-ietf-6man-node-req-bis-00.txt, Internet-Drafts
  • RE: I-D Action:draft-ietf-6man-node-req-bis-00.txt, john.loughney
    • Re: I-D Action:draft-ietf-6man-node-req-bis-00.txt, Vishwas Manral
  • Re: I-D Action:draft-ietf-6man-node-req-bis-00.txt, Brian E Carpenter
    • Re: I-D Action:draft-ietf-6man-node-req-bis-00.txt, Vishwas Manral
    • RE: I-D Action:draft-ietf-6man-node-req-bis-00.txt, john.loughney
• I-D ACTION:draft-ietf-ipv6-compression-nego-v2-02.txt, Internet-Drafts
• HSBC Bank reminder: confirm your HSBC Bank client details!, HSBC
• ietf.org mailing list memberships reminder, mailman-owner
  • <Possible follow-ups>
  • ietf.org mailing list memberships reminder, mailman-owner
• I-D Action:draft-ietf-6man-addr-select-sol-00.txt, Internet-Drafts
• packet filter firewall for ipv6, ather zaidi
  • Re: packet filter firewall for ipv6, Mohacsi Janos
  • Re: packet filter firewall for ipv6, Fred Baker
• Checksum in IPv6 header, Rahim Choudhary
  • Re: Checksum in IPv6 header, Fred Baker
    • Re: Checksum in IPv6 header, Rahim Choudhary
      • RE: Checksum in IPv6 header, Templin, Fred L
      • Re: Checksum in IPv6 header, Vishwas Manral
      • RE: Checksum in IPv6 header, Alex Conta
      • RE: Checksum in IPv6 header, Rahim Choudhary
      • RE: Checksum in IPv6 header, Alex Conta
      • RE: Checksum in IPv6 header, Manfredi, Albert E
      • RE: Checksum in IPv6 header, Alex Conta
      • RE: Checksum in IPv6 header, Manfredi, Albert E
      • RE: Checksum in IPv6 header, Alex Conta
      • Message not available
      • Re: Checksum in IPv6 header, Vishwas Manral
      • Re: Checksum in IPv6 header, Iljitsch van Beijnum
      • Re: Checksum in IPv6 header, Rahim Choudhary
      • Re: Checksum in IPv6 header, Iljitsch van Beijnum
      • Re: Checksum in IPv6 header, Vishwas Manral
      • Re: Checksum in IPv6 header, Vishwas Manral
      • Re: Checksum in IPv6 header, Rahim Choudhary
      • Re: Checksum in IPv6 header, Antonio Querubin
      • Re: Checksum in IPv6 header, Fred Baker
      • Re: Checksum in IPv6 header, Mark Smith
      • Re: Checksum in IPv6 header, Fred Baker
  • RE: Checksum in IPv6 header, TJ
  • RE: Checksum in IPv6 header, TJ
• Request To Advance: <draft-ietf-ipv6-compression-nego-v2-01.txt>, Brian Haberman
• Last Call: draft-ietf-ipv6-compression-nego-v2 (Negotiation for IPv6 datagram compression using IPv6 Control Protocol) to Proposed Standard, The IESG
• AD review of draft-ietf-ipv6-compression-nego-v2, Jari Arkko
  • Re: AD review of draft-ietf-ipv6-compression-nego-v2, James Carlson
    • Re: AD review of draft-ietf-ipv6-compression-nego-v2, Jari Arkko
      • Re: AD review of draft-ietf-ipv6-compression-nego-v2, James Carlson
      • Re: AD review of draft-ietf-ipv6-compression-nego-v2, Jari Arkko
• RFC 4294 Update, Ed Jankiewicz
  • RE: RFC 4294 Update, john.loughney
• ipv6 requirements for a sensor/constrained device, Julien Abeillé
  • Re: ipv6 requirements for a sensor/constrained device, Arul Kumar Chellappan
    • RE: ipv6 requirements for a sensor/constrained device (UNCLASSIFIED), Duncan, Richard J CTR DISA JITC
  • RE: ipv6 requirements for a sensor/constrained device (UNCLASSIFIED), Duncan, Richard J CTR DISA JITC
• [RFC 4862] about hardware address, Yukiyo Akisada
  • Re: about hardware address, JINMEI Tatuya / 神明達哉
    • Re: about hardware address, JINMEI Tatuya / 神明達哉
      • Re: about hardware address, Yukiyo Akisada
• RFC 4193, Prabhu Harihar
  • Re: RFC 4193, Mark Andrews
    • Re: RFC 4193, Prabhu Harihar
      • Re: RFC 4193, Mark Andrews
  • RE: RFC 4193, michael.dillon
• Router Lifetime: max value to be accepted by a host, Sandeep P A
  • Re: Router Lifetime: max value to be accepted by a host, Erik Kline
    • RE: Router Lifetime: max value to be accepted by a host, Dunn, Jeffrey H.
• 6MAN WG Consensus Call: Adopting draft-krishnan-ipv6-reserved-iids-02.txt, Brian Haberman
• 6MAN WG Consensus Call: Adopting draft-arifumi-6man-addr-select-sol-00.txt, Brian Haberman
  • Re: 6MAN WG Consensus Call: Adopting draft-arifumi-6man-addr-select-sol-00.txt, Arifumi Matsumoto
• IETF 70 6MAN Minutes, Brian Haberman
  • RE: IETF 70 6MAN Minutes, Hemant Singh (shemant)
  • Re: IETF 70 6MAN Minutes, Arifumi Matsumoto
    • Re: IETF 70 6MAN Minutes, Brian Haberman
• Timing out NS and sending data to the default router, Wes Beebee (wbeebee)
• RFC 5095 on Deprecation of Type 0 Routing Headers in IPv6, rfc-editor
• IPv6 ND stateful address autoconfiguration, Sandeep.P A
  • Re: IPv6 ND stateful address autoconfiguration, Vlad Yasevich
    • RE: IPv6 ND stateful address autoconfiguration, Sandeep P A
      • Re: IPv6 ND stateful address autoconfiguration, Vlad Yasevich
      • Re: IPv6 ND stateful address autoconfiguration, Iljitsch van Beijnum
• HITBSecConf2007 Malaysia Videos Now Available, Praburaajan
• draft-eronen-ipsec-ikev2-ipv6-config-01: I and Pasi met today, Hemant Singh (shemant)
• Stupid ULA discussion, Iljitsch van Beijnum
  • Re: Stupid ULA discussion, Christopher Morrow
  • Re: Stupid ULA discussion, Mark Smith
  • RE: Stupid ULA discussion, michael.dillon
  • Re: Stupid ULA discussion, Brian Dickson
    • RE: Stupid ULA discussion, Suresh Krishnan
      • RE: Stupid ULA discussion, Manfredi, Albert E
      • Re: Stupid ULA discussion, Erik Nordmark
    • Re: Stupid ULA discussion, james woodyatt
      • RE: Stupid ULA discussion, Templin, Fred L
  • Re: Stupid ULA discussion, Brian E Carpenter
    • RE: Stupid ULA discussion, Tony Hain
  • Re: Stupid ULA discussion, Per Heldal
    • Re: Stupid ULA discussion, Brian E Carpenter
      • Re: Stupid ULA discussion, Per Heldal
• Off-link and on-link, Suresh Krishnan
  • RE: Off-link and on-link, Hemant Singh (shemant)
    • Re: Off-link and on-link, Erik Nordmark
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • Re: Off-link and on-link, Erik Nordmark
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • RE: Off-link and on-link, Hesham Soliman
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • Re: Off-link and on-link, Ralph Droms
      • RE: Off-link and on-link, Bernie Volz (volz)
      • Re: Off-link and on-link, Ralph Droms
      • Re: Off-link and on-link, Erik Nordmark
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • Re: Off-link and on-link, Ralph Droms
      • RE: Off-link and on-link, Hesham Soliman
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • Re: Off-link and on-link, Ralph Droms
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • Re: Off-link and on-link, Francis Dupont
      • Re: Off-link and on-link, Ralph Droms
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • RE: Off-link and on-link, Hemant Singh (shemant)
      • RE: Off-link and on-link, Hesham Soliman
      • RE: Off-link and on-link, Hemant Singh (shemant)
  • Re: Off-link and on-link, Erik Nordmark
  • RE: Off-link and on-link, Hesham Soliman
• Getting rid of MAYs in RFC4294, Suresh Krishnan
  • RE: Getting rid of MAYs in RFC4294, john.loughney
• Question on IPv6 jumbograms, Manfredi, Albert E
  • RE: Question on IPv6 jumbograms, Suresh Krishnan
    • 6man mailing list, Bob Hinden
      • RE: 6man mailing list, Suresh Krishnan
      • Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • Re: Here is the reference to 6.3.4 text that is ambigious text, Josh Littlefield
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Suresh Krishnan
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • Re: Here is the reference to 6.3.4 text that is ambigious text, Thomas Narten
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • Re: Here is the reference to 6.3.4 text that is ambigious text, Erik Nordmark
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • Re: Here is the reference to 6.3.4 text that is ambigious text, Erik Nordmark
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Hemant Singh (shemant)
      • RE: Here is the reference to 6.3.4 text that is ambigious text, Bernie Volz (volz)
  • Re: Question on IPv6 jumbograms, Vishwas Manral
  • Re: Question on IPv6 jumbograms, Elwyn Davies
• [Fwd: Itojun gathering at 70th IETF], Brian Haberman
• Source Address Selection just from Routing Information, FUJIKAWA Kenji
  • Re: Source Address Selection just from Routing Information, Rémi Denis-Courmont
    • Re: Source Address Selection just from Routing Information, FUJIKAWA Kenji
• Vancouver 6MAN Agenda updated, Brian Haberman
  • Message not available
    • Node Requirements in Vancouver RE: Vancouver 6MAN Agenda updated, john.loughney
      • Re: Node Requirements in Vancouver RE: Vancouver 6MAN Agenda updated, Thomas Narten
      • Re: Node Requirements in Vancouver RE: Vancouver 6MAN Agenda updated, Soininen Jonne (NSN-FI/Espoo)
      • RE: Node Requirements in Vancouver RE: Vancouver 6MAN Agenda updated, john.loughney
      • Re: Node Requirements in Vancouver RE: Vancouver 6MAN Agenda updated, Brian E Carpenter
      • Re: Node Requirements in Vancouver RE: Vancouver 6MAN Agenda updated, Pekka Savola
      • RE: Node Requirements in Vancouver RE: Vancouver 6MAN Agenda updated, Bound, Jim
      • RE: Node Requirements in Vancouver RE: Vancouver 6MAN Agenda updated, john.loughney
      • Re: Node Requirements in Vancouver RE: Vancouver 6MAN Agenda updated, Brian E Carpenter
• A question about IPV6 and IPV4 prefixes, Mohammad Behdadfar
  • Re: A question about IPV6 and IPV4 prefixes, Frank Habicht
    • Re: A question about IPV6 and IPV4 prefixes, JINMEI Tatuya / 神明達哉
• slot request for address selection solution draft, Arifumi Matsumoto
• RE: [dhcwg] Q for draft-krishnan-dhc-ndc-option-00, Wes Beebee (wbeebee)
  • Re: [dhcwg] Q for draft-krishnan-dhc-ndc-option-00, Suresh Krishnan
• Source Address Selection, FUJIKAWA Kenji
• IPv6 address notation for example IPv6 architectures, Alexandru Petrescu
  • Re: IPv6 address notation for example IPv6 architectures, JORDI PALET MARTINEZ
    • Re: IPv6 address notation for example IPv6 architectures, Alexandru Petrescu
      • Re: IPv6 address notation for example IPv6 architectures, JORDI PALET MARTINEZ
  • Re: IPv6 address notation for example IPv6 architectures, Geoff Huston