IP Version 6 Working Group Discussion Archive - Date Index
[Prev Page] [Next Page] [Thread Index]
[IETF Main Archive Directory]
- Feb 05 2009
- Feb 04 2009
- Jan 29 2009
- Jan 29 2009
- Jan 26 2009
- Jan 25 2009
- Jan 24 2009
- Jan 23 2009
- Re: End System PMTUD behavior question, Thomas Peterson
- RE: End System PMTUD behavior question, Dunn, Jeffrey H.
- RE: End System PMTUD behavior question, Dunn, Jeffrey H.
- RE: End System PMTUD behavior question, Dunn, Jeffrey H.
- RE: End System PMTUD behavior question, Pekka Savola
- Re: End System PMTUD behavior question, Mark Andrews
- RE: End System PMTUD behavior question, Dunn, Jeffrey H.
- One of a kind Longines reps, Bill Michel
- Re: End System PMTUD behavior question, Mark Andrews
- Jan 22 2009
- Jan 21 2009
- RE: End System PMTUD behavior question, Dunn, Jeffrey H.
- RE: End System PMTUD behavior question, Dunn, Jeffrey H.
- RE: End System PMTUD behavior question, Hemant Singh (shemant)
- Re: Standard status of RFC 3879, Brian E Carpenter
- Re: Standard status of RFC 3879, Ed Jankiewicz
- Re: End System PMTUD behavior question, Thomas Peterson
- RE: End System PMTUD behavior question, Dunn, Jeffrey H.
- RE: Standard status of RFC 3879, Pekka Savola
- Re: End System PMTUD behavior question, Rémi Denis-Courmont
- RE: Standard status of RFC 3879, Christian Huitema
- End System PMTUD behavior question, Dunn, Jeffrey H.
- Re: Standard status of RFC 3879, Bob Hinden
- Vacheron Constantin cheaper than you could imagine!, Darnell Roe
- Re: Call for Agenda Items for IETF74 in San Francisco, Tim Chown
- Standard status of RFC 3879, Christian Huitema
- Jan 20 2009
- Jan 18 2009
- Jan 16 2009
- Jan 15 2009
- Jan 09 2009
- Jan 07 2009
- Jan 07 2009
- Jan 05 2009
- Jan 03 2009
- Jan 02 2009
- Dec 31 2008
- Dec 29 2008
- Dec 23 2008
- Dec 23 2008
- Dec 22 2008
- Dec 15 2008
- Dec 13 2008
- Dec 12 2008
- Dec 09 2008
- Dec 09 2008
- Dec 05 2008
- Dec 03 2008
- Dec 02 2008
- Nov 21 2008
- Nov 20 2008
- Nov 20 2008
- Nov 17 2008
- Nov 17 2008
- Re: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, Brian E Carpenter
- Re: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, Daniel Park
- Re: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, Brian E Carpenter
- Re: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, Basavaraj Patil
- Re: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, Brian E Carpenter
- Re: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, Daniel Park
- Re: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, Daniel Park
- RE: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, teemu.savolainen
- Re: Current agenda, Bob Hinden
- Re: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, Basavaraj Patil
- Scribes needed, Brian Haberman
- RE: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, john.loughney
- RE: Node Requirement: New issue 5: Support for RFC 5006, teemu.savolainen
- FW: New Version Notification for draft-thubert-3122bis-00, Pascal Thubert (pthubert)
- Re: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX, Brian E Carpenter
- Re: Node Requirement: New issue 5: Support for RFC 5006, Brian E Carpenter
- Nov 15 2008
- Nov 14 2008
- Nov 13 2008
- Nov 12 2008
- Nov 08 2008
- Nov 07 2008
- Nov 06 2008
- Nov 05 2008
- Nov 04 2008
- Nov 03 2008
- Re: [dhcwg] /128 address allocation and "localized IPv6 address space exhaustion", was RE: Brokenness of specs w.r.t. client behavior with M&O bits, H. Peter Anvin
- RE: [dhcwg] /128 address allocation and "localized IPv6 address space exhaustion", was RE: Brokenness of specs w.r.t. client behavior with M&O bits, Christian Huitema
- Re: [dhcwg] /128 address allocation and "localized IPv6 address space exhaustion", was RE: Brokenness of specs w.r.t. client behavior with M&O bits, H. Peter Anvin
- I-D Action:draft-ietf-6man-node-req-bis-02.txt, Internet-Drafts
- Node Requirements Bis and issue tracker, john.loughney at nokia.com
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, teemu.savolainen
- Re: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, hyunwook cha
- RE: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, teemu.savolainen
- RE: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, teemu.savolainen
- Re: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Rémi Denis-Courmont
- Nov 02 2008
- Oct 31 2008
- Oct 30 2008
- Re: [dhcwg] /128 address allocation and "localized IPv6 addressspace exhaustion", was RE: Brokenness of specs w.r.t. client behavior with M&O bits, Ole Troan
- RE: [dhcwg] /128 address allocation and "localized IPv6 addressspace exhaustion", was RE: Brokenness of specs w.r.t. client behavior with M&O bits, Templin, Fred L
- Re: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Pekka Savola
- /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, teemu.savolainen
- What is the IETF consensus on the" Brokenness of specs w.r.t. client behavior with M&O bits", Joseph Hyunwook Cha
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, hyunwook cha
- Oct 28 2008
- Oct 26 2008
- Oct 24 2008
- Oct 23 2008
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Tony Hain
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Tony Hain
- Re: [dhcwg] Cost of multicast [was Re: Brokenness of specs w.r.t. client behavior with M&O bits], Iljitsch van Beijnum
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, teemu.savolainen
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, teemu.savolainen
- Re: [dhcwg] Cost of multicast [was Re: Brokenness of specs w.r.t. client behavior with M&O bits], David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: RANGER, EricLKlein
- Oct 22 2008
- Oct 21 2008
- Oct 19 2008
- Oct 18 2008
- Oct 17 2008
- Re: Last Call: draft-ietf-tcpm-tcp-soft-errors (TCP's Reaction to Soft Errors) to Informational RFC, JINMEI Tatuya / 神明達哉
- RE: RANGER, Templin, Fred L
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Bernie Volz (volz)
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Wes Beebee (wbeebee)
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Ted Lemon
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Ted Lemon
- Re: Requesting adoption of draft-krishnan-ipv6-exthdr-06.txt as wg item, Suresh Krishnan
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Templin, Fred L
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Dunn, Jeffrey H.
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, TJ
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Markku Savela
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Ralph Droms
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Ralph Droms
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Ralph Droms
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Oct 16 2008
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Pekka Savola
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Ralph Droms
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: Requesting adoption of draft-krishnan-ipv6-exthdr-06.txt as wg item, Arnaud Ebalard
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: Requesting adoption of draft-krishnan-ipv6-exthdr-06.txt as wg item, Erik Kline
- Re: Requesting adoption of draft-krishnan-ipv6-exthdr-06.txt as wg item, Arnaud Ebalard
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Brian E Carpenter
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, hyunwook cha
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David Conrad
- Re: Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Joseph Hyunwook Cha
- Oct 15 2008
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Bob Hinden
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Christian Huitema
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Brian E Carpenter
- Re: Cost of multicast [was Re: Brokenness of specs w.r.t. client behavior with M&O bits], Mark Smith
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Ted Lemon
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Pekka Savola
- RANGER, Templin, Fred L
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Thomas Narten
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Thomas Narten
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Fazla Kilolardan Kurtulun, Klasmed
- Re: in6_pktinfo etc still missing in POSIX specs, Stig Venaas
- Re: in6_pktinfo etc still missing in POSIX specs, Mark Andrews
- Oct 14 2008
- Requesting adoption of draft-krishnan-ipv6-exthdr-06.txt as wg item, Suresh Krishnan
- Re: in6_pktinfo etc still missing in POSIX specs, Mark Andrews
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Brian E Carpenter
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Pekka Savola
- Re: in6_pktinfo etc still missing in POSIX specs, Thomas Narten
- Re: Cost of multicast [was Re: Brokenness of specs w.r.t. client behaviorwith M&O bits], Thomas Narten
- Re: Cost of multicast [was Re: Brokenness of specs w.r.t. client behavior with M&O bits], Thomas Narten
- in6_pktinfo etc still missing in POSIX specs, Pekka Savola
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, trejrco
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, David W. Hankins
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: Cost of multicast [was Re: Brokenness of specs w.r.t. client behavior with M&O bits], Iljitsch van Beijnum
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Kadirvel Chockalingam Vanniarajan
- Re: Brokenness of specs w.r.t. client behavior with M&O bits, Joseph Hyunwook Cha
- Re: Brokenness of specs w.r.t. client behavior with M&O bits, Pekka Savola
- RE: Cost of multicast [was Re: Brokenness of specs w.r.t. client behaviorwith M&O bits], Manfredi, Albert E
- Oct 13 2008
- Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Ralph Droms
- Cost of multicast [was Re: Brokenness of specs w.r.t. client behavior with M&O bits], Thomas Narten
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Greg.Rabil
- RE: Brokenness of specs w.r.t. client behavior with M&O bits, Greg.Rabil
- Re: Brokenness of specs w.r.t. client behavior with M&O bits, Ralph Droms
- RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits, Bernie Volz (volz)
- Re: Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: Brokenness of specs w.r.t. client behavior with M&O bits, Thomas Narten
- Re: Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Re: Brokenness of specs w.r.t. client behavior with M&O bits, Alain Durand
- Re: Brokenness of specs w.r.t. client behavior with M&O bits, Iljitsch van Beijnum
- Brokenness of specs w.r.t. client behavior with M&O bits, Thomas Narten
- Re: [dhcwg] Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", Ralph Droms
- RE: Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", Bernie Volz (volz)
- Re: Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", Brian Haberman
- Oct 10 2008
- Oct 08 2008
- Oct 08 2008
- Oct 06 2008
- Oct 06 2008
- Re: [dhcwg] Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", hyunwook cha
- Re: Neighbor Discovery from non-neighbors, JINMEI Tatuya / 神明達哉
- RE: Neighbor Discovery from non-neighbors, Hemant Singh (shemant)
- I-D Action:draft-ietf-6man-ipv6-subnet-model-02.txt, Internet-Drafts
- Re: [dhcwg] Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", Ralph Droms
- RE: [dhcwg] Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", Bernie Volz (volz)
- Re: [dhcwg] Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", Ralph Droms
- RE: [dhcwg] Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", Bernie Volz (volz)
- Re: [dhcwg] Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", Ralph Droms
- RE: Neighbor Discovery from non-neighbors, Hemant Singh (shemant)
- RE: Neighbor Discovery from non-neighbors, Hemant Singh (shemant)
- Oct 05 2008
- Oct 04 2008
- Oct 03 2008
- Re: IPv6 Firewire - fffe, Brian E Carpenter
- RE: Neighbor Discovery from non-neighbors, Hemant Singh (shemant)
- Re: IPv6 Firewire - fffe (was: what problem is solved by proscribing non-64 bit prefixes?), Alexandru Petrescu
- RE: Neighbor Discovery from non-neighbors, Hemant Singh (shemant)
- Re: what problem is solved by proscribing non-64 bit prefixes?, Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 bit prefixes?, michael.dillon
- Re: what problem is solved by proscribing non-64 bit prefixes?, Alexandru Petrescu
- Re: what problem is solved by proscribing non-64 bit prefixes?, Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 bit prefixes?, Pekka Savola
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 bit prefixes?, Brian E Carpenter
- Oct 02 2008
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- FW: IPv6 Subnet Model, Hemant Singh (shemant)
- RE: Neighbor Discovery from non-neighbors, Hemant Singh (shemant)
- RE: what problem is solved by proscribing non-64 bit prefixes?, Pekka Savola
- Re: [v4v6interim] v4v6interim at ietf.org Mailing list, Nathan Ward
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- Re: Why would anyone want to use a 64 bit interface identifier?, Jeroen Massar
- Re: Neighbor Discovery from non-neighbors, Pekka Savola
- Re: Why would anyone want to use a 64 bit interface identifier?, Mark Andrews
- Re: Neighbor Discovery from non-neighbors, JINMEI Tatuya / 神明達哉
- Neighbor Discovery from non-neighbors, Pekka Savola
- Re: what problem is solved by proscribing non-64 bit prefixes?, Christopher Morrow
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- Oct 01 2008
- Re: the IPv6 Ethernet lost bits - fffe, Francis Dupont
- Re: what problem is solved by proscribing non-64 bit prefixes?, slblake
- RE: what problem is solved by proscribing non-64 bit prefixes?, Antonio Querubin
- Re: what problem is solved by proscribing non-64 bit prefixes?, Brian E Carpenter
- Re: what problem is solved by proscribing non-64 bit prefixes?, Brian Dickson
- Re: what problem is solved by proscribing non-64 bit prefixes?, Brian E Carpenter
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 bit prefixes?, Antonio Querubin
- RE: the IPv6 Ethernet lost bits - fffe, Chip Popoviciu (cpopovic)
- RE: Why would anyone want to use a 64 bit interface identifier?, TJ
- Re: Why would anyone want to use a 64 bit interface identifier?, Alexandru Petrescu
- Re: the IPv6 Ethernet lost bits - fffe, Alexandru Petrescu
- RE: Why would anyone want to use a 64 bit interface identifier?, TJ
- RE: the IPv6 Ethernet lost bits - fffe, TJ
- Re: Why would anyone want to use a 64 bit interface identifier?, Alexandru Petrescu
- RE: Why would anyone want to use a 64 bit interface identifier? (was: what problem is solved by proscribing non-64 bit prefixes?), TJ
- RE: the IPv6 Ethernet lost bits - fffe, Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- Re: v4v6interim at ietf.org Mailing list, Cullen Jennings
- RE: Why would anyone want to use a 64 bit interface identifier? (was: what problem is solved by proscribing non-64 bit prefixes?), Dunn, Jeffrey H.
- RE: v4v6interim at ietf.org Mailing list, Stark, Barbara
- Re: Why would anyone want to use a 64 bit interface identifier? (was: what problem is solved by proscribing non-64 bit prefixes?), Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 bit prefixes?, Azinger, Marla
- RE: what problem is solved by proscribing non-64 bit prefixes?, Azinger, Marla
- Re: the IPv6 Ethernet lost bits - fffe, Jeroen Massar
- RE: the IPv6 Ethernet lost bits - fffe, TJ
- RE: the IPv6 Ethernet lost bits - fffe, TJ
- Re: the IPv6 Ethernet lost bits - fffe, Tim Chown
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- Re: the IPv6 Ethernet lost bits - fffe, Jeroen Massar
- Re: the IPv6 Ethernet lost bits - fffe (was: what problem is solved by proscribing non-64 bit prefixes?), Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 bit prefixes?, Alexandru Petrescu
- Re: what problem is solved by proscribing non-64 bit prefixes?, Mohacsi Janos
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 bit prefixes?, Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 bit prefixes?, michael.dillon
- RE: what problem is solved by proscribing non-64 bit prefixes?, michael.dillon
- Re: what problem is solved by proscribing non-64 bit prefixes?, Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 bit prefixes?, Dunn, Jeffrey H.
- Sep 30 2008
- RE: what problem is solved by proscribing non-64 bit prefixes?, TJ
- Re: what problem is solved by proscribing non-64 bit prefixes?, Brian Dickson
- RE: what problem is solved by proscribing non-64 bit prefixes?, Manfredi, Albert E
- Re: what problem is solved by proscribing non-64 bit prefixes?, Brian E Carpenter
- Re: v6ops-addcon and longer than 64 bit prefixes, Brian E Carpenter
- Re: what problem is solved by proscribing non-64 bit prefixes?, Brian Dickson
- Re: what problem is solved by proscribing non-64 bit prefixes?, Alexandru Petrescu
- Re: what problem is solved by proscribing non-64 bit prefixes?, Pekka Savola
- RE: what problem is solved by proscribing non-64 bit prefixes?, michael.dillon
- Re: what problem is solved by proscribing non-64 bit prefixes?, Brian Dickson
- RE: what problem is solved by proscribing non-64 bit prefixes? (was: v6ops-addcon and longer than 64 bit prefixes), Dunn, Jeffrey H.
- RE: v6ops-addcon and longer than 64 bit prefixes, Azinger, Marla
- Re: what problem is solved by proscribing non-64 bit prefixes? (was: v6ops-addcon and longer than 64 bit prefixes), Alexandru Petrescu
- RE: v4v6interim at ietf.org Mailing list, Dan Wing
- Re: v4v6interim at ietf.org Mailing list, Mark Townsley
- Re: v6ops-addcon and longer than 64 bit prefixes, Fred Baker
- RE: v4v6interim at ietf.org Mailing list, Narayanan, Vidya
- Re: Re: Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", HYUN WOOK CHA
- Re: Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", Ted Lemon
- Re: Request for Advices on the draft "draft-cha-ipv6-ra-mo-00.txt", HYUN WOOK CHA
- Sep 28 2008
- Sep 28 2008
- Sep 27 2008
- Sep 25 2008
- Sep 25 2008
- Sep 24 2008
- Sep 22 2008
- Sep 18 2008
- Sep 17 2008
- Sep 16 2008
- Sep 15 2008
- Sep 12 2008
- Sep 03 2008
- Sep 02 2008
- Aug 28 2008
- Aug 21 2008
- Aug 21 2008
- Aug 13 2008
- Aug 05 2008
- Aug 04 2008
- Jul 31 2008
- Jul 30 2008
- Jul 25 2008
- Jul 21 2008
- Jul 18 2008
- Jul 17 2008
- Jul 14 2008
- I-D Action:draft-ietf-6man-reserved-iids-01.txt, Internet-Drafts
- Overlapping fragments in IPv6 and firewalls, Suresh Krishnan
- [Fwd: I-D Action:draft-krishnan-ipv6-exthdr-03.txt], Suresh Krishnan
- Re: 6MAN WG Last Call:draft-ietf-6man-reserved-iids-00.txt, Brian E Carpenter
- Re: 6MAN WG Last Call:draft-ietf-6man-reserved-iids-00.txt, Ed Jankiewicz
- Re: Request for Agenda Items, Brian Haberman
- Re: 6MAN WG Last Call:draft-ietf-6man-reserved-iids-00.txt, Brian Haberman
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Erik Nordmark
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Erik Nordmark
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Erik Nordmark
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Erik Nordmark
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Erik Nordmark
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, MILES DAVID
- Jul 11 2008
- Jul 10 2008
- Re: Minimum IPv6 MTU, Jeroen Massar
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- Minimum IPv6 MTU, Fernando Gont
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Wes Beebee (wbeebee)
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, JINMEI Tatuya / 神明達哉
- I-D Action:draft-ietf-6man-ipv6-subnet-model-01.txt, Internet-Drafts
- New version of subnet draft is available, Hemant Singh (shemant)
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Wes Beebee (wbeebee)
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Suresh Krishnan
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Suresh Krishnan
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Thomas Narten
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, JINMEI Tatuya / 神明達哉
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, JINMEI Tatuya / 神明達哉
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Thomas Narten
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Thomas Narten
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, Hemant Singh (shemant)
- Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt, JINMEI Tatuya / 神明達哉
- Jul 09 2008
Mail converted by MHonArc
