internet | 29 Aug 17:01 2014
Picon

I-D Action: draft-ietf-v6ops-mobile-device-profile-10.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Operations Working Group of the IETF.

        Title           : An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
        Authors         : David Binet
                          Mohamed Boucadair
                          Ales Vizdal
                          Gang Chen
	Filename        : draft-ietf-v6ops-mobile-device-profile-10.txt
	Pages           : 19
	Date            : 2014-08-29

Abstract:
   This document defines an IPv6 profile that a number of operators
   recommend in order to connect 3GPP mobile devices to an IPv6-only or
   dual-stack wireless network (including 3GPP cellular network and IEEE
   802.11 network).

   This document defines a different profile than the one for general
   connection to IPv6 cellular networks defined in the IPv6 for Third
   Generation Partnership Project (3GPP) Cellular Hosts document.  In
   particular, this document identifies also features to deliver IPv4
   connectivity service over an IPv6-only transport.

   Both hosts and devices with capability to share their WAN (Wide Area
   Network) connectivity are in scope.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/
(Continue reading)

Fred Baker (fred | 25 Aug 19:20 2014
Picon

PMTUD issue discussion

http://datatracker.ietf.org/doc/draft-v6ops-pmtud-ecmp-problem
http://tools.ietf.org/html/draft-v6ops-pmtud-ecmp-problem
 "Close encounters of the ICMP type 2 kind (near misses with ICMPv6
 PTB)", Matt Byerly, Matt Hite, Joel Jaeggli, 2014-08-24,

As requested at IETF 90, Joel has edited and reposted his draft. There are two questions before the house:
 - do we want to make this a working group draft?
 - what do we want to do next?

Note that, by charter, what we are not permitted to do is change implementations or protocols; we are
allowed to define operational procedure. That said, we *can* make recommendations to other working
groups, asking them to change something.

So, for example, we might ask 6man to do something specific, or we might ask tcpm to do something specific.
Something specific that we might ask tcpm to do would be to get operational experience with RFC 4821 and
commit it back to open source, for example.

_______________________________________________
v6ops mailing list
v6ops@...
https://www.ietf.org/mailman/listinfo/v6ops

fred | 25 Aug 13:47 2014
Picon

new draft: draft-v6ops-pmtud-ecmp-problem

A new draft has been posted, at
http://datatracker.ietf.org/wg/v6ops/charter/draft-v6ops-pmtud-ecmp-problem. Please take a
look at it and comment.

_______________________________________________
v6ops mailing list
v6ops@...
https://www.ietf.org/mailman/listinfo/v6ops

internet | 21 Aug 16:11 2014
Picon

I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-04.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Operations Working Group of the IETF.

        Title           : IPv6 Roaming Behavior Analysis
        Authors         : Gang Chen
                          Hui Deng
                          Dave Michaud
                          Jouni Korhonen
                          Mohamed Boucadair
                          Vizdal Ales
	Filename        : draft-ietf-v6ops-ipv6-roaming-analysis-04.txt
	Pages           : 19
	Date            : 2014-08-21

Abstract:
   This document identifies a set of failure cases that may be
   encountered by IPv6-enabled mobile customers in roaming scenarios.
   The analysis reveals that the failure causes include improper
   configurations, incomplete functionality support in equipment, and
   inconsistent IPv6 deployment strategies between the home and the
   visited networks.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-roaming-analysis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-roaming-analysis-04

A diff from the previous version is available at:
(Continue reading)

The IESG | 19 Aug 18:18 2014
Picon

Document Action: 'Enterprise IPv6 Deployment Guidelines' to Informational RFC (draft-ietf-v6ops-enterprise-incremental-ipv6-06.txt)

The IESG has approved the following document:
- 'Enterprise IPv6 Deployment Guidelines'
  (draft-ietf-v6ops-enterprise-incremental-ipv6-06.txt) as Informational
RFC

This document is the product of the IPv6 Operations Working Group.

The IESG contact persons are Joel Jaeggli and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-v6ops-enterprise-incremental-ipv6/

Technical Summary

This document summarizes a proposed framework for enterprise network
architects and administrators as they plan the introduction of IPv6
support in their environments, specifically dual stack and eventually IPv6
only.

Working Group Summary

This draft was first submitted as
draft-ietf-v6ops-enterprise-incremental-ipv6-00.txt in August 2012. The
document has been revised several times since introduced. The document
outlines considerations, both technical and logistical, that enterprise
adopters of IPv6 should consider as they advance or even begin introducing
support for IPv6 across their respective enterprises.

The draft has been discussed at length and in detail.

(Continue reading)

internet | 13 Aug 16:04 2014
Picon

I-D Action: draft-ietf-v6ops-mobile-device-profile-09.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Operations Working Group of the IETF.

        Title           : An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
        Authors         : David Binet
                          Mohamed Boucadair
                          Ales Vizdal
                          Cameron Byrne
                          Gang Chen
	Filename        : draft-ietf-v6ops-mobile-device-profile-09.txt
	Pages           : 18
	Date            : 2014-08-13

Abstract:
   This document defines an IPv6 profile that a number of operators
   recommend in order to connect 3GPP mobile devices to an IPv6-only or
   dual-stack wireless network (including 3GPP cellular network and IEEE
   802.11 network).

   This document defines a different profile than the one for general
   connection to IPv6 cellular networks defined in the IPv6 for Third
   Generation Partnership Project (3GPP) Cellular Hosts document.  In
   particular, this document identifies also features to deliver IPv4
   connectivity service over an IPv6-only transport.

   Both hosts and devices with capability to share their WAN (Wide Area
   Network) connectivity are in scope.

The IETF datatracker status page for this draft is:
(Continue reading)

internet | 11 Aug 15:21 2014
Picon

I-D Action: draft-ietf-v6ops-mobile-device-profile-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Operations Working Group of the IETF.

        Title           : An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
        Authors         : David Binet
                          Mohamed Boucadair
                          Ales Vizdal
                          Cameron Byrne
                          Gang Chen
	Filename        : draft-ietf-v6ops-mobile-device-profile-08.txt
	Pages           : 18
	Date            : 2014-08-11

Abstract:
   This document defines an IPv6 profile that a number of operators
   recommend in order to connect 3GPP mobile devices to an IPv6-only or
   dual-stack wireless network (including 3GPP cellular network and IEEE
   802.11 network).

   This document defines a different profile than the one for general
   connection to IPv6 cellular networks defined in the IPv6 for Third
   Generation Partnership Project (3GPP) Cellular Hosts document.  In
   particular, this document identifies also features to deliver IPv4
   connectivity service over an IPv6-only transport.

   Both hosts and devices with capability to share their WAN (Wide Area
   Network) connectivity are in scope.

The IETF datatracker status page for this draft is:
(Continue reading)

神明達哉 | 8 Aug 18:41 2014
Picon

comments on draft-gont-v6ops-ipv6-ehs-in-real-world-00

I've read the draft and have a few comments on it:

Section 4: for the probing measurement you should have sent packets
without the extension headers in question to identify the point where
the packets are dropped and make it more likely that it's dropped
because of that extension header.  It may be easily inferred from the
context, but I think it's helpful to note that explicitly.  As I read
the rest of the draft I found it would probably just suffice to refer
to Appendix A.1 from this section.

Section 4
   Packets dropped by the destination AS are less of a
   concern, since they can be assumed to be the result of an explicit
   policy of the organization to which the packets are destined (who can
   make its own decision regarding what kind of traffic is
   "acceptable").
I agree with the sense of this sentence, but I think the "since"
clause is a bit too strong.  For cases like ordinary household users
connected to ISPs, the situation shouldn't be so different from the
case where the packet is dropped in a transit AS in practice.

Section 4: the numbers in tables 1 and 2 are confusing to me.  For
example, in the following cell of table 1:

   +--------------+-----------------+
   |   Dataset    |       DO8       |
   +--------------+-----------------+
   |     Web      |      11.88%     |
   |              | (17.60%-20.80%) |
   +--------------+-----------------+
(Continue reading)

fred | 8 Aug 13:47 2014
Picon

new draft: draft-gont-v6ops-ipv6-ehs-in-real-world

~c draft-gont-v6ops-ipv6-ehs-in-real-world@...

A new draft has been posted, at
http://datatracker.ietf.org/wg/v6ops/charter/draft-gont-v6ops-ipv6-ehs-in-real-world.
Please take a look at it and comment.

_______________________________________________
v6ops mailing list
v6ops@...
https://www.ietf.org/mailman/listinfo/v6ops

Fernando Gont | 8 Aug 06:04 2014

New I-D: IPv6 Extension Headers in the Real World

Folks,

We have published a new I-D on the topic of IPv6 Extension Headers
(EHs). The I-D is available at:
<http://www.ietf.org/internet-drafts/draft-gont-v6ops-ipv6-ehs-in-real-world-00.txt>.

Abstract:
   IPv6 Extension Headers allow for the extension of the IPv6 protocol,
   and provide support for some core functionality such as IPv6
   fragmentation.  However, IPv6 Extension Headers are deemed to present
   a challenge to IPv6 implementations and networks, and are known to be
   intentionally filtered in some existing IPv6 deployments.  This
   summarizes the issues associated with IPv6 extension headers, and
   presents real-world data regarding the extent to which packets with
   IPv6 extension headers are filtered in the public Internet, and where
   in the network such filtering occurs.  Additionally, it provides some
   guidance to operators in troubleshooting IPv6 blackholes resulting
   from the use of IPv6 extension headers.  Finally, this document
   provides some advice to protocol designers, and discusses areas where
   further work might be needed.

Comments and suggestions are welcome.

Thanks!

Best regards,
Fernando

-------- Forwarded Message --------
Subject: New Version Notification for
(Continue reading)

RJ Atkinson | 6 Aug 15:18 2014
Picon

Re: [OPSEC] I-D Action: draft-gont-opsec-ipv6-eh-filtering-00.txt

Earlier, on 18th July 2014, Warren Kumari wrote:
> Related to this is
> 
> http://tools.ietf.org/html/draft-taylor-v6ops-fragdrop-02
>  -- Why
> Operators Filter Fragments and What It Implies
> 
> This expired, but I suspect we may need to revive it...
> 
> W

(ASIDE:  I've trimmed off the int-area list to reduce list
cross-posting.  My sense is that between v6ops and opsec, 
the applicable audience will be covered adequately.)

I agree that the above draft ought to be revived.

As a community, it would be very helpful to have an
Informational status RFC describing "Why Operators
Filter Fragments and What it Implies".

From my point of view, this need not be an IETF-track
document.  It would serve the purpose equally well as
an ISE-track document with Informational status.  

(Just to be clear, I don't object to it being IETF-track,
but the ISE-track has a faster time-to-RFC and generally
is a lower-overhead process.)

Yours,
(Continue reading)


Gmane