The Subnetwork Encapsulation and Adaptation Layer (SEAL)
draft-templin-seal-23

[Ballot discuss]
On the IESG call, I would like to talk about if, given the IANA considerations, we need to add more the IESG note about the deployability of this.

[Ballot discuss]
On the IESG call, I would like to talk about why informational not experimental given the IANA considerations and also given the IANA considerations if we need to add an IESG note on this.

[Ballot comment]
I will change my position to "No Objection" when the course of action suggested by Jari (in e-mail on 5/20) is carried out; draft-templin-seal-23.txt shows "Intended status: Informational":

I have no problem with going ahead with this content and an Experimental RFC.

(I did not have any problem with the original content either. You and the RFC Editor should work out which text actually goes out, you changed quite a bit and they had already done their editing.)

RFC-Editor, Fred: I take it that we are back in the original plan, i.e., Experimental RFC and the IANA considerations as they were. If yes, I could just withdraw the draft from the new consideration of the IESG. Perhaps you want to send an e-mail to that effect to the IESG.

Jari

[Ballot comment]
I will change my position to "No Objection" when the course of action suggested by Jari (in e-mail on 5/20) is carried out (the ballot still shows the intended status as Informational):

I have no problem with going ahead with this content and an Experimental RFC.

(I did not have any problem with the original content either. You and the RFC Editor should work out which text actually goes out, you changed quite a bit and they had already done their editing.)

RFC-Editor, Fred: I take it that we are back in the original plan, i.e., Experimental RFC and the IANA considerations as they were. If yes, I could just withdraw the draft from the new consideration of the IESG. Perhaps you want to send an e-mail to that effect to the IESG.

Jari

This RFC-to-be was submitted to the RFC Editor to be published as
Experimental: draft-templin-seal-23.txt

Please let us know if this document conflicts with the IETF standards
process or other work being done in the IETF community.

Four week timeout expires on 23 September 2008.


The Subnetwork Encapsulation and Adaptation Layer (SEAL)

For the purpose of this document, subnetworks are defined as
virtual topologies that span connected network regions bounded by
encapsulated border nodes. These virtual topologies may span
multiple IP- and/or sub-IP layer forwarding hops, and can introduce
failure modes due to packet duplication and/or links with diverse
Maximum Transmission Units (MTUs). This document specifies a
Subnetwork Encapsulation and Adaptation Layer (SEAL) that
accommodates such virtual topologies over diverse underlying link
technologies.