0x0002 IM CN Subsystem Signaling Flag 0x0003 DNS Server IPv6 Address 0x0004 Policy Control rejection code 0x0005 Selected Bearer Control Mode 0x0006 Reserved 0x0007 DSMIPv6 Home Agent Address 0x0008 DSMIPv6 Home Network Prefix 0x0009 DSMIPv6 IPv4 Home Agent Address 0x000A Reserved 0x000B Reserved 0x000C P-CSCF IPv4 Address 0x000D DNS Server IPv4 Address 0x000E MSISDN 0x000F IFOM-Support 0x0010 IPv4 Link MTU OxFF00 to 0xFFFF Reserved for operator specific use Flow Template information element is 257 octets, which, based on the existing encoding, can hold maximum of four full sized IPv6 packet filters per Traffic Flow Template infor- mation element. A maximum size IPv6 packet filter can be 60 octets. However, an existing TFT up to 16 filters can have added to it. There are only few IPv6 specific TFT filter components: a full 16-octet IPv6 address, 8-bit traffic class, and a 20-bit flow label. 4.4.8 Initial E-UTRAN Attach Example with IPv4 and IPv6 Address Configuration Figure 4.27 illustrates the steps for an initial E-UTRAN attach, with the associated IPv4 and IPv6 address configuration. The example is not exhaustive from the signaling steps and individual messages point of view and therefore lacks details (see [13, 15] for more complete signaling flows). This is visible specifically in the signaling steps between the UE and the MME. Note that we have not even included the eNodeB in the example. However, we think those additional 3GPP specific details of the bearer and radio resource management are not essential for an address configuration example. The overall scenario we have selected is based on the assumption that the network and the UE support PDN Type IPv4v6, and the addresses are configured dynamically. 1. The UE initiates the attach procedure and sends the PDN Connectivity Request message via the eNodeB to the MME. The message contains PCO information element for requesting IP level configuration such as DNS server addresses and informing the network that the UE does not want to use DHCPv4 to configure its