Original text:
The CONTINUATION frame includes optional padding.  Padding fields and flags are identical to those defined for DATA.  7. Error codes are 32-bit fields that are used in

Reviewer comments:
HTTP/2 has different properties to HTTP/1 regarding server-side load, because load balancers etc. currently exploit HTTP/1's short connections. HTTP/2 has much longer-lived connections, making it more difficult to load balance traffic. A mechanism to direct the client to use a different server/port would mitigate this. While GOAWAY could be used to do this, it introduces latency as the new connection is set up.
Alt-Svc?
URL
NAME is this really in the next milestone? It doesn't seem like we're ready yet.
Should get out a draft momentarily; if we don't make it, that's fine, but if we can, it'd be good to have a bit of discussion first.
NAME this missed the boat. Can I request that you put together something we can discuss in London instead.
Yes, it's on the list for discussion there. The boat technically is delayed at dock...
Discussed in London; agreed to using ALTSVC frame for this.

Revised text:
The CONTINUATION frame includes optional padding.  Padding fields and flags are identical to those defined for DATA. <ins> 6.11. The ALTSVC frame (type=0xa) advertises the availability of an alternative service to the client.  It can be sent at any time for an existing client-initiated stream or stream 0, and is intended to allow servers to load balance or otherwise segment traffic; see AltSvc for details (in particular, Section 2.4, which outlines client handling of alternative services). An ALTSVC frame on a client-initiated stream indicates that the conveyed alternative service is associated with the origin of that stream. An ALTSVC frame on stream 0 indicates that the conveyed alternative service is associated with the origin contained in the Origin field of the frame.  An association with an origin that the client does not consider authoritative for the current connection MUST be ignored. The ALTSVC frame is intended for receipt by clients; a server that receives an ALTSVC frame MUST treat it as a connection error of type PROTOCOL_ERROR. The ALTSVC frame contains the following fields: PID_LEN: An unsigned, 8-bit integer indicating the length, in bytes, of the PROTOCOL-ID field. Reserved: for future use. Port: An unsigned, 16-bit integer indicating the port that the alternative service is available upon. Max-Age: An unsigned, 32-bit integer indicating the freshness lifetime of the alternative service association, as per AltSvc, Section 2.2. Protocol-ID: A sequence of bytes (length determined by PID_LEN) containing the ALPN protocol identifier of the alternative service. HOST_LEN: An unsigned, 8-bit integer indicating the length, in 8-bit characters, of the Host field. Host: A sequence of characters (length determined by HOST_LEN) containing an ASCII string indicating the host that the alternative service is available upon. Origin: An optional sequence of characters (length determined by ORGN_LEN) containing ASCII serialisation of an origin (RFC6454, Section 6.2) that the alternate service is applicable to. The ALTSVC frame does not define any flags. </ins> 7. Error codes are 32-bit fields that are used in