Re: [v6ops] I-D Action: draft-ietf-v6ops-design-choices-10.txt

Hi,

On 15 October 2016 at 06:26, Philip Matthews <philip_matthews@magma.ca>
wrote:

> Folks:
>
> After a long delay due to demands of $DAYJOB, we are finally back to
> working on this I-D.
>
> Here is a summary of the major changes:
> * Section 2.1 ("Addresses").  This section was very contentious in
> Yokohama (yes, it was that long ago ...). We have been discussing what to
> do with this, but have not come to any conclusions yet, so for now we have
> removed the old contents and just put "TBD".
> * Section 2.3 ("IGPs"). Some significant changes here. First, we added an
> IPv6-centric comparison of OSPF, IS-IS, and EIGRP.  We just list
> similarities and differences, without making recommendations. We think this
> helps give better context before we discuss our survey of what people have
> deployed.  We also added more facts around single-topology vs.
> multi-topology for IS-IS, and reworded the section discussing RIP and RIPng.
>

The discussion included, but the table excluded
   Use OSPFv3 running over IPv6 for routing both IPv4 and IPv6

Is it worthwhile referencing RFC 7404
  Using Only Link-Local Addressing inside an IPv6 Network
as an example of the minimal amount of IPv6 interface configuration
required to support an IGP?

* Various minor changes: updated the year, affiliation, etc.
>

> ietf-v6ops-host-addr-availability
> Cerf, D. (sic)

Is now RFC 7934.

s/draft-ietf-v6ops-ula-usage-recommendations/draft-ietf-v6ops-ula-usage-considerations/

Thanks,
    John

We are still discussing what, if anything, we should say in the addressing
> section.  It is hard to say something here that is insightful without
> causing some people to take offense.
>
> Comments welcome.
>
> - Philip and Victor
>
>
>
> On 2016-10-14, at 15:22 , Internet-Drafts@ietf.org wrote:
>
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the IPv6 Operations of the IETF.
> >
> >        Title           : Some Design Choices for IPv6 Networks
> >        Authors         : Philip Matthews
> >                          Victor Kuarsingh
> >       Filename        : draft-ietf-v6ops-design-choices-10.txt
> >       Pages           : 22
> >       Date            : 2016-10-14
> >
> > Abstract:
> >   This document presents advice on certain routing-related design
> >   choices that arise when designing IPv6 networks (both dual-stack and
> >   IPv6-only).  The intended audience is someone designing an IPv6
> >   network who is knowledgeable about best current practices around IPv4
> >   network design, and wishes to learn the corresponding practices for
> >   IPv6.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-v6ops-design-choices/
> >
> > There's also a htmlized version available at:
> > https://tools.ietf.org/html/draft-ietf-v6ops-design-choices-10
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-design-choices-10
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> >
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

-- 
*John Mann*
Network Architect, Infrastructure Automation & Delivery

*Infrastructure Services, eSolutions*
Monash University
738 Blackburn Road
Clayton VIC 3168
Australia

T: +61 3 9905 4774
M: +61 419 568 470
E: john.mann@monash.edu
W: monash.edu