<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ospf-af-alt" target="https://datatracker.ietf.org/doc/html/draft-ietf-ospf-af-alt-10">
   <front>
      <title>Support of Address Families in OSPFv3</title>
      <author initials="M." surname="Barnes" fullname="Michael Barnes">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="S." surname="Mirtorabi" fullname="Sina Mirtorabi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="R." surname="Aggarwal" fullname="Rahul Aggarwal">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="A." surname="Roy" fullname="Abhay Roy">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Lindem" fullname="Acee Lindem">
         <organization>Ericsson</organization>
      </author>
      <date month="December" day="15" year="2009" />
      <abstract>
	 <t>This document describes a mechanism for supporting multiple address families (AFs) in OSPFv3 using multiple instances.  It maps an AF to an OSPFv3 instance using the Instance ID field in the OSPFv3 packet header.  This approach is fairly simple and minimizes extensions to OSPFv3 for supporting multiple AFs. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ospf-af-alt-10" />
   
</reference>
