| 125 | |
| 126 | == INTAREA == |
| 127 | The intarea working group met in Berlin for a two hour session. The |
| 128 | draft containing the Analysis of Solution Candidates to Reveal a Host |
| 129 | Identifier (HOST_ID) in Shared Address Deployments describing has been |
| 130 | published as RFC6967. The draft describing the use of the IPv6 Flow |
| 131 | Label for Server Load Balancing has completed WGLC Will be progressed |
| 132 | after this meeting. Brian Haberman presented some background |
| 133 | information about the implementation status experiment described in |
| 134 | RFC6982. |
| 135 | |
| 136 | There was a presentation describing a fragmentation strategy for |
| 137 | GRE. There were some questions about how ECN information would be |
| 138 | handled in the fragments. There were not enough participants who had |
| 139 | read the draft and the chair requested volunteers to review the |
| 140 | draft. There were two volunteers to do so. After receiving the reviews |
| 141 | a call for adoption would be issued on the mailing list. |
| 142 | |
| 143 | There was a presentation concerning a set of drafts that describe how |
| 144 | applications can use metadata to signal traffic characteristics to the |
| 145 | network. There was lively discussion of this topic and the general |
| 146 | sense of the room about these drafts was overall negative. It was also |
| 147 | the opinion of several people who spoke up that tsvwg was the proper |
| 148 | venue for this work. |
| 149 | |
| 150 | There was a presentation about a draft describing a stateless |
| 151 | userplane for virtual evolved packet core networks. It was presented |
| 152 | in intarea to increase awareness for this work being performed in the |
| 153 | mobility related working groups in the intarea. There was widespread |
| 154 | interest in this draft and further discussion will happen on the |
| 155 | mailing list. |
| 156 | |
| 157 | There was a presentation concerning issues with IP links on |
| 158 | spontaneous wireless networks. There was a lot of interest in this |
| 159 | draft and since the issues raised in the draft are common across |
| 160 | several types of wireless links intarea may be a good place to host |
| 161 | this work. Further discussion and potential adoption will happen on |
| 162 | the mailing list. |
| 163 | |
| 164 | The draft regarding scaling ARP for large data centers had been |
| 165 | revised based on comments received at the IETF86 intarea meeting as |
| 166 | well as on the mailing list. There were not enough people in the room |
| 167 | who had read the draft and a call for adoption of this draft would be |
| 168 | issued on the mailing list after the meeting. |
| 169 | |
| 170 | == SOFTWIRE == |
| 171 | The Softwire Working Group met at the IETF meeting in Berlin for a two |
| 172 | and a half hour session. Since the Orlando meeting, Deployment |
| 173 | Considerations for Dual-Stack Lite has been published as RFC6908 and |
| 174 | the 6RD RADIUS draft has been published as RFC6930. The draft |
| 175 | documenting Public 4over6 has been submitted to the IESG as an |
| 176 | Informational document. The working group also adopted 3 new drafts as |
| 177 | working group documents: lightweight 4over6, MAP MIB and MAP |
| 178 | Radius. Two multicast related documents in the working group will be |
| 179 | submitted to IESG soon: DS-Lite multicast and multicast-prefix-option, |
| 180 | while the third, mesh multicast, will start a working group last call |
| 181 | soon. WGLC has completed successfully on both the DS-Lite MIB and Mesh |
| 182 | MIB drafts. These drafts will be sent for review by the MIB doctors |
| 183 | before submitting to IESG. A call for adoption of the 6RD MIB draft |
| 184 | has been issued on the mailing list, but a further review is needed |
| 185 | on both document quality and necessity before adoption. |
| 186 | |
| 187 | The chairs received more than 20 requests for presentations. The wg |
| 188 | documents including the unified CPE, lw4over6 and 4rd documents were |
| 189 | prioritized and presented first. The goal was to get open issues on wg |
| 190 | documents resolved first before discussing any new work. The meeting |
| 191 | also allocated some time for discussion about the dhcp extensions for |
| 192 | both MAP and lw4over6. WG discussed some related issues, especially on |
| 193 | the tickets recorded by the Issue Tracker. There are still some open |
| 194 | issues. Since the wg document of MAP DHCP has changed quite a bit, a |
| 195 | consensus check will be performed on the mailing list regarding the |
| 196 | scope of the draft. A draft describing use cases for MAP-T was |
| 197 | presented and there was widespread support in the room to adopt |
| 198 | it. The draft will be adopted as a wg item pending confirmation on the |
| 199 | mailing list. There were some presentations related to lw4over6 and |
| 200 | MAP-T and further discussion about this will take place on the mailing |
| 201 | list. |
| 202 | |