Monday, March 27, 2017< ^ >
Room Configuration
Room Occupants

[13:47:31] Meetecho joins the room
[13:57:28] Simon Romano joins the room
[14:06:27] Dirk v. Hugo joins the room
[14:07:44] ddolson joins the room
[14:08:42] Dirk v. Hugo leaves the room
[14:13:07] Alex Petrescu joins the room
[14:13:18] <Alex Petrescu> I will jabber scribe
[14:13:26] Robert Butler joins the room
[14:13:28] vojislav vucetic joins the room
[14:13:37] <Alex Petrescu> Marco Liebsch is presenting
[14:13:57] <Alex Petrescu> slide 1. Add Domain-reference to Topology model
[14:14:19] <Alex Petrescu> slide title "1. Add Domain-reference to Topology model"
[14:14:57] <Alex Petrescu> slide title "Domain-reference points a set of data-plane resources (aka network-slice)"
[14:15:21] Dirk von Hugo joins the room
[14:15:32] <Alex Petrescu> slide title "2. Add some text to node-reference"
[14:16:33] Roger Murray joins the room
[14:16:40] <Alex Petrescu> slide title "Node reference points both ael or virtual DPN"
[14:17:13] <Alex Petrescu> slide title "3. Miscellaneous"
[14:18:24] Dirk von Hugo leaves the room
[14:19:03] <Alex Petrescu> slide title "1. Change Port to Vport"
[14:20:09] <Alex Petrescu> slide title "2. Next-hop and tunnel attribute"
[14:20:25] Temp Test joins the room
[14:21:07] <Alex Petrescu> Suresh Krishnan approaching (Area Director AD)
[14:21:29] <Alex Petrescu> AD: difficult ti visualize, is is it like segment routing domain? only i fmake part of domain?
[14:21:38] <Alex Petrescu> ML: you could see as... end of tunnel
[14:21:59] <Alex Petrescu> SK: SFC domain is this, segment routing domain; always thought they are outside domain - do you think they are part of domain?
[14:22:10] <Alex Petrescu> Satoru Matsushima talking
[14:22:26] <Alex Petrescu> SM: next hop indicates that service path ID as next hop, outside of mobility domain
[14:22:32] Temp Test leaves the room
[14:22:37] Robert Butler leaves the room
[14:22:52] <Alex Petrescu> SM: connected to outside of network, some sort of SFC stuff... then the mobile network must be capable to point to that ID in the path, that's how I  see.
[14:23:11] <Alex Petrescu> SM: SFT and SRP as integrat just as next-hop, and then the child will be the body to indicate...
[14:23:38] <Alex Petrescu> SK (AD)- if you enter the domain, ... what happens if there is some packets that do not match what the domain has done.
[14:23:59] <Alex Petrescu> SK: if 2 ways to do the same thing, then maybe conflict, maybe more text needed to explain how you see this working.
[14:24:09] <Alex Petrescu> ML: yes, maybe more text needed.
[14:24:48] Robert Butler joins the room
[14:24:49] <Alex Petrescu> slide title "3. Agent's featuers and capabilities discovery"
[14:25:11] <Alex Petrescu> slite title "4. monitor event reference"
[14:25:40] Rick Alfvin joins the room
[14:26:26] <Alex Petrescu> slide title "FpcAgent has been an ODL Project"
[14:26:49] <Alex Petrescu> slide title "Next"
[14:27:27] Rick Alfvin leaves the room
[14:27:55] <Alex Petrescu> Sri Gundavelli (Chair)
[14:28:07] <Alex Petrescu> SG: what are the other issues: willyou solve in next month?
[14:28:39] <Alex Petrescu> ML: the other issues we discussed yesterday, see how far to go, conclude them through virtual meetings after this IETF.  Or open items like hopcount which are contradicting, depends on the original feedback
[14:28:45] <Alex Petrescu> SG: questions?
[14:29:02] <Alex Petrescu> SG: thanks for all contributions, amazing work.
[14:29:25] <Alex Petrescu> Anthony to present Distributed Mobility Anchroring
[14:29:30] <Alex Petrescu> Anthony H Chan
[14:29:40] <Alex Petrescu> slide title "Enahanced Mobility anchroring wt"
[14:29:47] <Alex Petrescu> slide title "changes in 03 from 02"
[14:30:41] <Alex Petrescu> slide title "Describe Distributed Mobility Ancroring
[14:31:40] <Alex Petrescu> "alide title "Network Mobility"
[14:31:58] Robert Butler leaves the room
[14:32:09] <Alex Petrescu> SG: any questions?
[14:32:16] <Alex Petrescu> SG: good reviews we need.
[14:32:20] <Alex Petrescu> SG: editorial is one thing.
[14:32:27] <Alex Petrescu> SG: thecnical the document should be sound.
[14:32:37] <Alex Petrescu> SG: volunteers to review document and feedback?
[14:32:44] <Alex Petrescu> SG: Marco, X, Carlos...
[14:32:55] <Alex Petrescu> SG: theyll do some focus reviews, if you can update it, take forward.
[14:33:03] <Alex Petrescu> SG: in next months (not next meeting)(
[14:33:38] <Alex Petrescu> Danny Moses is going to present Ondemand Mobility Management extensions, or something akin to it.
[14:33:42] ddolson leaves the room
[14:33:54] <Alex Petrescu> Seil is talking
[14:34:02] <Alex Petrescu> Seil: upload the material to the server please.
[14:34:09] <Alex Petrescu> SG: we'll upload right after meeting.
[14:34:34] <Alex Petrescu> Slide title "Socket...
[14:34:43] <Alex Petrescu> "slide tit;e "Updates since IETF-9&"
[14:34:45] <Alex Petrescu> 97
[14:36:45] <Alex Petrescu> slide title "locking vs Non-Blocking Function"
[14:36:49] <Alex Petrescu> Blocking
[14:39:46] <Alex Petrescu> Lorenzo Collitti approaching
[14:39:55] <Alex Petrescu> LC: not ok if the setsockopt it blocks
[14:40:11] <Alex Petrescu> LC: setsockopt goes in the kernel; something that blocks willnot get upstreamed (implemented)
[14:40:26] <Alex Petrescu> LC: if you want to be implemented in any clean way in linux, then no setsockpt
[14:40:32] <Alex Petrescu> SK: just set the flag
[14:40:45] <Alex Petrescu> LC: could not use setsocktopt to do IP address provisioning
[14:40:53] <Alex Petrescu> LC: something more control-plane oriented, some library
[14:41:03] <Alex Petrescu> DM: more specific please
[14:41:08] <Alex Petrescu> CM: suggestion more specific
[14:41:18] <Alex Petrescu> SK: point is that setsockotp is not designed to do this
[14:41:28] <Alex Petrescu> KS: not just beat on forever wait forever to happen
[14:41:33] <Alex Petrescu> DM: maybe a watchdog
[14:41:46] <Alex Petrescu> DM: a solution that prevents setsockopt to wait forever
[14:41:52] <Alex Petrescu> SG: different demantics it has
[14:41:56] <Alex Petrescu> DM: define a new function?
[14:42:05] <Alex Petrescu> DM: but linux you cant define a function that returns?
[14:42:15] <Alex Petrescu> SG: receive, waith for something to happen, need ...
[14:42:26] <Alex Petrescu> SK not SG
[14:42:40] <Alex Petrescu> SK: you can not wait for it
[14:42:49] <Alex Petrescu> SK: you dont know whats gonna heppn
[14:43:02] <Alex Petrescu> DM: there are other socket functions that dont return immediately
[14:43:10] <Alex Petrescu> DM: like when you start TCP session wait for ACK
[14:43:19] <Alex Petrescu> SK: poll on something socjet descriptor
[14:43:28] <Alex Petrescu> SK: how do that with setsockopt?
[14:43:39] <Alex Petrescu> DM: no need of loop, there are tasks or similar, dormant
[14:43:48] <Alex Petrescu> SK: cant do peoples programming models, some do threading
[14:43:56] <Alex Petrescu> DM: reason is that suggest how to do that
[14:44:11] <Alex Petrescu> DM, SK: ...
[14:44:20] <Alex Petrescu> Erik Kline: could do entirel nonblocking
[14:44:33] <Alex Petrescu> DM: alternative: define a non blocking call, return saying operation started
[14:44:42] <Alex Petrescu> DM: at some point, a callback function called by kernel
[14:44:48] <Alex Petrescu> SK: need to write make sense
[14:44:53] <Alex Petrescu> SK: maybe use netlink?
[14:45:00] <Alex Petrescu> SK: OS-specific, routing socket for BSD
[14:45:07] <Alex Petrescu> SK: setsockopt is not the right funciton
[14:45:38] <Alex Petrescu> EK: need maybe split it into two: still want setsockcopt, but needs something get a source a ddress, needs to fail, all that stuff is simmediate
[14:45:48] <Alex Petrescu> EK: need a separata funciton, like getaddrinfo
[14:46:03] <Alex Petrescu> EK: there is anotherthing that is called "provisioning" - provision me this type of prefix
[14:46:09] <Alex Petrescu> EK: have a ...
[14:46:26] <Alex Petrescu> EK: think of it more like getaddrinfo (rather than setsockopt)
[14:46:42] <Alex Petrescu> EK: arguably getaddr info was not specified to...
[14:46:46] <Alex Petrescu> DM: i fI understand...
[14:47:07] <Alex Petrescu> DM: call setsockopt, and either return a result, or with some status saying "process started"
[14:47:11] <Alex Petrescu> EK: not what I said.
[14:47:24] <Alex Petrescu> EK: what I said is number 1 and, split it into two.
[14:47:33] <Alex Petrescu> DM: it's called a "session ..."
[14:47:35] Dirk von Hugo joins the room
[14:48:15] <Alex Petrescu> EK: before I call setsockopt, and before I call connect(), I need to call a function like getaddrinfo to start the provisioning process.
[14:48:26] <Alex Petrescu> DM: why cant setsockopt start the provisioning...
[14:48:35] <Alex Petrescu> EK: in linux it's going to be done in userspace.
[14:48:43] <Alex Petrescu> EK: something in kernel now...
[14:49:08] <Alex Petrescu> EK: going down in kernel to have it triggered is probably not the best design anymore
[14:49:18] <Alex Petrescu> DM: I will talk to you later, or discuss on list
[14:49:23] <Alex Petrescu> David Dolson is DD
[14:49:36] <Alex Petrescu> DD: proposal is disconnected from what people think is reasonable to do
[14:49:51] <Alex Petrescu> DD: need implementation, that would
[14:50:10] <Alex Petrescu> DD: my hunch this would be used to express preference, but not to start provisioning
[14:50:17] <Alex Petrescu> DD: this is similar with dhclient.
[14:50:26] <Alex Petrescu> DD: to kick off any socket stuff...
[14:50:34] <Alex Petrescu> DD: to get the addres seems to be a different flow
[14:50:39] <Alex Petrescu> DM: agreed
[14:50:59] <Alex Petrescu> SK: setsockopt ...
[14:51:07] <Alex Petrescu> DM: unless provisioning a request immediately
[14:51:15] <Alex Petrescu> SK: set some flag
[14:51:28] <Alex Petrescu> DM: but if I want a non persistent address, the address exists already
[14:51:32] <Alex Petrescu> SK: that's a disconnect
[14:51:50] <Alex Petrescu> SK: if want to re-use, no need to do any
[14:51:56] <Alex Petrescu> SK: if you want a T-shirt - analogy
[14:52:32] <Alex Petrescu> SK: this is not related to setsockotp, this is not how setsockopt is used
[14:52:42] <Alex Petrescu> DM: you say dont use setsocokpt:?
[14:52:49] <Alex Petrescu> SK: no, I say different,...
[14:52:59] <Alex Petrescu> SG: take it to list
[14:53:08] <Alex Petrescu> SG: document?  List of options, and get feedback of WG
[14:53:27] <Alex Petrescu> LC: setsockokpt is not synch, does not do anything, just sets a pref for future
[14:53:39] <Alex Petrescu> LC: you get an answer when you try to do smth, like with connect()
[14:53:54] <Alex Petrescu> LC: kernel doesnt know what you want until you tell it what you want
[14:54:08] <Alex Petrescu> LC: untilk you say "do this" it does not knowwhat to do
[14:54:21] <Alex Petrescu> LC: you want a preference, that may need to be "mandatory".
[14:54:28] <Alex Petrescu> CM: I will take it to the list
[14:54:37] <Alex Petrescu> Dapeng Liu is talking (co-chair)_
[14:54:56] <Alex Petrescu> DL: when you do something, when you want to do the connection, based on preference, then you may need to get a fail.
[14:55:04] <Alex Petrescu> DM: dont block until the prefix was provided
[14:55:13] <Alex Petrescu> SK: not do anything untul its needed
[14:55:35] <Alex Petrescu> EK: if you make a kernel that requires a src address, and cant work, it will tell it to you with a errno
[14:55:42] <Alex Petrescu> EK: UDP may you use?
[14:56:16] <Alex Petrescu> EK: need a separate call (nto setsockopt), the equivalent of getaddrinfo - get prefix preference, that starts the provisioning call.
[14:56:19] <Alex Petrescu> DM: not if.
[14:56:25] <Alex Petrescu> EK: wrong, its the same problem
[14:56:36] <Alex Petrescu> EK kernel snad sync
[14:56:51] <Alex Petrescu> EK: it's all like getaddrinfo - you need to make the DNS call before getaddrinfo
[14:57:08] <Alex Petrescu> DM: would it be a good idea to explorea of to explore adding oiption to getaddrinfo?
[14:57:16] <Alex Petrescu> EK: it was an example of kind of API you need
[14:57:21] <Alex Petrescu> EK: you need a different call
[14:57:30] <Alex Petrescu> EK" you need one blokcing variant
[14:57:46] <Alex Petrescu> SK: different angle
[14:57:56] <Alex Petrescu> EK: change socket API implementation?  change connecT()?
[14:58:05] <Alex Petrescu> EK: different example
[14:58:21] <Alex Petrescu> EK: sock option - sett the receive buffer size - nothing is going to be used until you call recv()
[14:58:38] <Alex Petrescu> EK: same here, until you run that call (that you have to write) then ...
[14:58:46] <Alex Petrescu> EK: need to spin on it
[14:59:08] <Alex Petrescu> EK: you can have anothe r function which polls, that waits before you do connect.
[14:59:27] <Alex Petrescu> SG: please propose all options on the list, so that WG comments
[14:59:45] <Alex Petrescu> DM: if I can think of several options then I will, right now people think there are is just one option
[14:59:52] <Alex Petrescu> DL: good discussion today.
[15:00:12] <Alex Petrescu> DL: anothe r good suggestion - try to implem emtn the proposal -thne you can know from the user perspoective
[15:00:21] <Alex Petrescu> DM: I added a section witho code example
[15:00:33] <Alex Petrescu> DM: difficult to implement because need to support from network
[15:00:42] <Alex Petrescu> DL: but standrad needs to be implement, otherwise not useful
[15:00:51] <Alex Petrescu> SG: maybe some feedback from community
[15:00:56] <Alex Petrescu> SG: some more specific feedback
[15:01:04] <Alex Petrescu> SG: advice how to use the API may not be enough
[15:01:14] <Alex Petrescu> SG: need feedback from guys who implement the API
[15:01:46] <Alex Petrescu> EK: you may make a mock implementation in a library (rather than having support from network)
[15:01:57] <Alex Petrescu> SG: DHCP implementation proposal you may need to do
[15:02:03] <Alex Petrescu> (that was DL, not SG)
[15:02:14] <Alex Petrescu> slide title "Support Future Pn-Demand Types"
[15:02:20] <Alex Petrescu> On-Demand
[15:03:01] <Alex Petrescu> (mock implementation is "mock-up" implementation)
[15:04:25] <Alex Petrescu> DM: we'll work on fixing the blocking - nonblocking issue, and then we'll...
[15:04:27] <Alex Petrescu> Chairs:"ok
[15:04:54] <Alex Petrescu> slide title "Changes from 04 to 05"
[15:06:32] <Alex Petrescu> RFC7934
[15:06:39] <Alex Petrescu> SK: fine
[15:06:45] <Alex Petrescu> SK: concern how this uses DHCP?
[15:06:50] <Alex Petrescu> SK: encapsulated in DHCP?
[15:06:59] <Alex Petrescu> SK: server behaves differently?  no address abailable?
[15:07:06] <Alex Petrescu> SK: server behave change req
[15:07:14] <Alex Petrescu> DM: not think to go to DH before WG adoption here
[15:07:23] <Alex Petrescu> SK: take it on the DHC mailing list
[15:07:29] <Alex Petrescu> SK: really concern
[15:07:33] <Alex Petrescu> DM: not thinking to avoid DHC
[15:07:39] <Alex Petrescu> (DHC is DHC WG)
[15:07:48] <Alex Petrescu> SG: Danny please do a presentation to a the DHC WG
[15:07:57] <Alex Petrescu> DM: next time, I prefer, with an adopted draft
[15:08:08] <Alex Petrescu> LC: do you , waht is this doc justify the use of IP addresses?
[15:08:18] <Alex Petrescu> LC: this is how, something that does nto follow that BCP
[15:08:33] <Alex Petrescu> DM: DHCP supports reqeusting an IP addres, if that is removed from DHCPv6 I noporlbme
[15:08:48] <Alex Petrescu> DM: looks awkawrd to not ask DHCP
[15:09:03] <Alex Petrescu> SG: if you look at all mobility work: UE gets a prefix, it's written there
[15:10:32] <Alex Petrescu> EK: clarification
[15:10:42] <Alex Petrescu> EK: the app requests an address inside the Host
[15:12:19] <Alex Petrescu> LC: then you want to add such attribute to all DHCP parameters (DNS address is stable)
[15:13:22] <Alex Petrescu> SK comments
[15:16:52] Roger Murray leaves the room
[15:19:13] <Alex Petrescu> DM: request WG adoption?
[15:19:18] <Alex Petrescu> DM: could be discussed
[15:19:34] <Alex Petrescu> SG: we need feedback from DHC WG before we even have it adopted?
[15:19:48] <Alex Petrescu> SK: no added value of being a WG draft.
[15:20:15] <Alex Petrescu> SK: it's Chairs call
[15:20:20] <Alex Petrescu> SG: it's a quick one, sanity check
[15:20:41] <Alex Petrescu> ICMPv6 RA and RS extensions for mobility
[15:20:49] <Alex Petrescu> this is the next presentation
[15:20:59] <Alex Petrescu> It is from Wu-chi Fench
[15:21:06] <Alex Petrescu> Wu-chi Feng
[15:21:21] <Alex Petrescu> slide title "on demand mobility through RS/RA"
[15:21:29] <Alex Petrescu> slide title "Motivation"
[15:22:46] <Alex Petrescu> slide title "Related Work"
[15:23:01] <Alex Petrescu> slide title "Is there interest here?"
[15:23:40] <Alex Petrescu> SK: not knowing, there is no draft
[15:23:52] <Alex Petrescu> SK: in general it's a bad idea, I habe a lot of scars
[15:23:57] <Alex Petrescu> SK: we aim much lower
[15:24:04] <Alex Petrescu> SK: information dissemination labe.;:l?
[15:24:11] <Alex Petrescu> SK: consensus in any group is hard to
[15:24:16] <Alex Petrescu> SK: cant say until we have a draft
[15:24:23] <Alex Petrescu> SK: RS is optional
[15:24:36] <Alex Petrescu> SK: what if no RS, what is RA telling?
[15:24:42] <Alex Petrescu> SK: nodes that dont ask for smth, what?
[15:24:52] <Alex Petrescu> SK: we tried in 6man, in mip6, mext, in mif?
[15:25:06] <Alex Petrescu> SK: before we do , look at al work that was done, and see why it failed.
[15:25:12] <Alex Petrescu> SK: there was lot of opposition
[15:25:17] <Alex Petrescu> SK: how can we fix mistakes?
[15:25:27] <Alex Petrescu> WF: exactly why we are here
[15:25:41] <Alex Petrescu> WF: before we go there, with all the people with these battle scars
[15:25:48] <Alex Petrescu> SK: bad idea, unless there is more info
[15:26:00] <Alex Petrescu> WF: we see RS/RA in 3GPP nonstandard ways
[15:26:05] <Alex Petrescu> EK: explain that
[15:26:19] <Alex Petrescu> WF: it's a "TS 23.smth" part of this, RA/RS, wait a minute
[15:26:23] <Alex Petrescu> WF: now we try...
[15:26:36] <Alex Petrescu> SK: we have a liaison, we get a message across
[15:26:44] <Alex Petrescu> SK: other people here go to 3GPP
[15:26:55] <Alex Petrescu> SK: I send a mesaage to the group, if they are interested, I can report back.
[15:27:02] <Alex Petrescu> (that was WF)
[15:27:40] <Alex Petrescu> WF: this is wat we awnat to see: if there is interest, then we do, if issues, at least we know before.
[15:27:50] <Alex Petrescu> SK: it can be made to wkrok
[15:28:10] <Alex Petrescu> EK: slide historically RS/RA not kind of I want feature, this is new feature...
[15:28:17] <Alex Petrescu> EK: violates the ondemand nature.
[15:28:31] <Alex Petrescu> EK: session prefix, no lionger "on demand".
[15:28:53] <Alex Petrescu> EK: maybe it's a subscriber feature, maybe my SIM card tells so, the persisntent one in the RA.  Not reuse PIO, find a new one.
[15:28:59] <Alex Petrescu> WF: option fields down in the RA
[15:29:03] <Alex Petrescu> EK: lot of other options
[15:29:11] <Alex Petrescu> WF: address options, not in the header
[15:29:28] <Alex Petrescu> DM: 3GPP acts like... we cant prevent them
[15:29:48] <Alex Petrescu> SK: 1st thing, 3PGPP should not squat on our points
[15:30:00] <Alex Petrescu> SK: can not just take the good points, they need to go to IANA action
[15:30:10] <Alex Petrescu> SK: they can pick a number of thin air
[15:30:16] <Alex Petrescu> SK: 3GPP friendly they are
[15:30:32] <Alex Petrescu> SK: 3GPP cant pick option code and use it
[15:30:48] <Alex Petrescu> WF: I will send a message out to the mailing list, if you want to pitch in, we can figure out
[15:30:54] <Alex Petrescu> SK: thants to do that!
[15:30:58] Roger Murray joins the room
[15:31:22] <Alex Petrescu> DM: helpful to describe what we are doing now.  It's not violating we do, but we found a way to message IETF stuff in a way that is not in violation.
[15:31:40] <Alex Petrescu> DM: example: they dont use RS, but use RA, have own protocol to request stuff, and then use RA to receive the info back
[15:32:13] <Alex Petrescu> RM: why use RA?  RA is not provisioning only one ...
[15:32:24] <Alex Petrescu> LC: I dont oppose this at all
[15:32:40] <Alex Petrescu> LC: we need to mind, people work on prefix coloring, it's different
[15:32:54] <Alex Petrescu> LC: RA prefix color did not go anywhere
[15:33:08] <Alex Petrescu> LC: Req Response?  RS/RA is different semantics
[15:33:23] <Alex Petrescu> LC: better with setsokopt
[15:33:32] <Alex Petrescu> LC: on demand allocation of IP addresses
[15:33:50] <Alex Petrescu> LC: RS/RA intended for stuff doesnt change, and todens start with client
[15:33:58] <Alex Petrescu> LC: prefixes that are always there...
[15:34:20] <Alex Petrescu> LC: matter on how the semantics; if it's req/resp driven then RS/RA is not the right way.
[15:34:33] <Alex Petrescu> LC: some platforms that dont do DHCPv6 at all, so RS/RA is ok.
[15:34:48] <Alex Petrescu> SK: rfc7066 - how v6 is used on 3gpp hosts, deviation from that.
[15:34:56] <Alex Petrescu> SK: years old, take a lok.
[15:35:00] <Alex Petrescu> look.
[15:35:18] <Alex Petrescu> Seil Jeon is going to present Sttateless mobility funcitons
[15:36:14] <Alex Petrescu> slide title "Motivation"
[15:37:49] <Alex Petrescu> slide title "Mobility state management"
[15:39:12] <Alex Petrescu> slide title "Discussion"
[15:41:52] <Alex Petrescu> DL: CPTP?
[15:42:07] <Alex Petrescu> SJ: this goes further: cp function and also dp function
[15:42:18] <Alex Petrescu> SJ: separation of CP from DP
[15:42:31] <Alex Petrescu> SJ: give more flexibility
[15:42:43] <Alex Petrescu> Praveen Muley (Nokia)
[15:42:58] <Alex Petrescu> PM: 70% of ... can run.  Benefit is in the scaled up scenario
[15:43:12] <Alex Petrescu> PM: another use case: upgrade precision: faster and seamless upgrade
[15:43:20] <Alex Petrescu> SG: vram?
[15:43:36] <Alex Petrescu> PM: move the state out of gateway, upgrades, easier scaling, upload 3rd party software
[15:44:16] <Alex Petrescu> ML: we know of the value: next steps; problem statement?  in this WG?  or implmepelnteation specific?
[15:44:36] <Alex Petrescu> SJ: some point can be standized, right procedure is to investigate use-cases.
[15:44:48] <Alex Petrescu> SJ: in this WG or other
[15:45:00] <Alex Petrescu> Prakash Suthar --
[15:45:09] <Alex Petrescu> PS: I like this, I want to cliollaboartate on this.
[15:45:14] <Alex Petrescu> PS: the cost is very high
[15:45:21] <Alex Petrescu> PS: dataplane stateless,
[15:45:28] <Alex Petrescu> PS: not very complext o implement,
[15:45:34] <Alex Petrescu> PS: physical and virtual appliances
[15:45:42] <Alex Petrescu> PS: most mobile gways move into virtual
[15:45:50] <Alex Petrescu> PS: if you can do a stateless dataplane.
[15:46:02] <Alex Petrescu> PS: make a big archi, we'd like to collaboarate.
[15:46:16] <Alex Petrescu> Satoru: EUID?  do you have a specific data-plane tech to make...?
[15:46:34] <Alex Petrescu> SJ: some ggeneric.  But here is IETF, no needd... maybe here is PMIP
[15:46:56] <Alex Petrescu> SM: maybe you want to adopt a specific DP tech (like GTP, or GRE, or statefull operation requiring).
[15:47:15] <Alex Petrescu> SM: I will ask my colleagues who work on GTP stuff, to be able to handle GTP as a next hop.
[15:47:31] <Alex Petrescu> SM: this is whya I want to go on.
[15:47:47] <Alex Petrescu> PS: even if control plane, lots more cycles to make it efficient
[15:47:55] <Alex Petrescu> PS: a far more complex problem.
[15:48:07] <Alex Petrescu> PS: control plane to make stateless...
[15:48:17] <Alex Petrescu> PS: BGP restart if cp dies and dp goes opn.
[15:48:49] <Alex Petrescu> Virtual CPE deployment considerations, is next, presenter is
[15:49:07] <Alex Petrescu> Presenter isByju Pularikkal
[15:49:08] Roger Murray leaves the room
[15:49:09] vojislav vucetic leaves the room
[15:49:14] <Alex Petrescu> Byju Pularikkal
[15:49:29] <Alex Petrescu> slide title "Virtual CPE Deployment Considerations"
[15:49:48] <Alex Petrescu> slide title "Draft Objectives and Scope"
[15:50:37] <Alex Petrescu> slide title "Architecture Models"
[15:50:46] <Alex Petrescu> Slide Title "Architecture Model-01"
[15:51:16] <Alex Petrescu> slide title "Architecture Model-02"
[15:52:15] <Alex Petrescu> sldie title "Architecture Model -03"
[15:52:38] <Alex Petrescu> slide title "FPC Capabilities required"
[15:53:27] <Alex Petrescu> slide title "Conclusions and Next steps"
[15:54:01] <Alex Petrescu> DL: any feedback you got from editors?
[15:54:16] <Alex Petrescu> BP: I can work with editors, amendment to existing draft, or a standalone doc
[15:54:25] <Alex Petrescu> Leon from China Mobile
[15:54:34] <Alex Petrescu> L: my colleague is on author list
[15:54:46] <Alex Petrescu> L: how is this lrelated to DMM charter?
[15:54:54] <Alex Petrescu> L: how about the first model?
[15:54:59] <Alex Petrescu> slide "Architecture Model -01"
[15:55:21] <Alex Petrescu> BP: (Leon is Liang Jeng)
[15:55:41] <Alex Petrescu> BP: this is the right model (the -03) who is aligned with dMM
[15:55:54] <Alex Petrescu> LJ: changed affiliation (China Mobile) a certain person
[15:56:06] <Alex Petrescu> SK: AD hat, I dont think the group is chartered to do this, no milestones
[15:56:13] <Alex Petrescu> SK: conversation the group must have with me
[15:56:19] <Alex Petrescu> SK: not in scope
[15:56:30] <Alex Petrescu> SK: you can work on int, take out stuff not in scope here.
[15:56:36] <Alex Petrescu> BP: ok
[15:56:51] <Alex Petrescu> DL: mobility ability negotiation
[15:57:06] <Alex Petrescu> Presenter is H Anthony Chan
[15:57:13] <Alex Petrescu> title
[15:57:23] <Alex Petrescu> Presenter not in meeting name is Z. Chan
[15:57:31] <Alex Petrescu> The presenter delegated is H Anthony Chan
[15:57:42] <Alex Petrescu> slide title "IP mobility management related"
[15:58:08] <Alex Petrescu> slide title "Two categories"
[15:59:00] <Alex Petrescu> slide title "Problems"
[15:59:33] <Alex Petrescu> slide title "More..."
[15:59:57] <Alex Petrescu> slide title "Example scenarios"
[16:00:30] <Alex Petrescu> slide title "MAN-Mobility Abaility Negotiation"
[16:01:14] <Alex Petrescu> slide title "MAN-Mobility Abaility Neogitation"
[16:01:46] <Alex Petrescu> slide title "Other issues"
[16:01:55] <Alex Petrescu> Carlos Bernardos
[16:02:10] <Alex Petrescu> CB: we did similar, a paer we compare mobility options, how they could be combined, authors look at that
[16:02:15] <Alex Petrescu> AC: not an author I am
[16:02:22] <Alex Petrescu> DL; send paper to the list
[16:02:26] <Alex Petrescu> CB: I will send the papers
[16:02:38] <Alex Petrescu> CB: the paper is not currently referred by the draft
[16:02:51] <Alex Petrescu> SG: few years back : MN-AR interface was there few years back
[16:03:01] <Alex Petrescu> SG: that was intendt doe rh MN to negotiate
[16:03:06] <Alex Petrescu> SG: define a new interface?
[16:03:16] <Alex Petrescu> AC: not a new interface, just new messages
[16:03:28] <Alex Petrescu> SG: Julien wrote a draft MN-AR iface, a ref iface
[16:03:37] <Alex Petrescu> SG: it was a WG item, did not move forward
[16:03:43] <Alex Petrescu> SG: take a look at that word
[16:03:49] <Alex Petrescu> AC: look at the differen toptions?
[16:03:56] <Alex Petrescu> SG: let the WG give feedback
[16:04:02] <Alex Petrescu> AC: we should continue
[16:04:06] <Alex Petrescu> SG: if intereste then yues
[16:04:21] <Alex Petrescu> SK: MN-AR iface was a WG item in netlmm WG years ago
[16:04:27] <Alex Petrescu> SK: there was work beofre
[16:04:48] <Alex Petrescu> SK: the year may be 2008
[16:05:06] <Alex Petrescu> SK: use work that was done before, lots more iusses remaining
[16:05:15] <Alex Petrescu> AC: maybe they have read that already
[16:05:28] <Alex Petrescu> AC: I will ... I will propose new discussion.
[16:05:43] <Alex Petrescu> AC: anyone interested to kjoin the work you are wleocme
[16:05:54] <Alex Petrescu> Presentation from Fred Templin, was not in the agenda, but.
[16:06:15] <Alex Petrescu> FT is going to present, SG is looking for the slides
[16:06:36] <Alex Petrescu> slide title "A simple BGP -based mobile routing system for the Aeronatutical Telecommunications Network"
[16:06:44] <Alex Petrescu> slide title "Backround"
[16:07:17] <Alex Petrescu> SATCOM, LDACS, VHF...
[16:07:36] <Alex Petrescu> EK: does that mean gogo give me IPv6?
[16:07:46] <Alex Petrescu> FTP: carries this or not ?  It's in the passenger domain
[16:07:49] <Alex Petrescu> (FTP is FT)
[16:08:00] <Alex Petrescu> slide title "Mobility Subgroup Solution Discussion"
[16:09:05] <Alex Petrescu> slide status "Draft Status"
[16:09:26] <Alex Petrescu> DL: the group is also doing stds?
[16:09:32] <Alex Petrescu> FT: std is called ICAO9896
[16:09:41] <Alex Petrescu> FT: very IETF centric, but their own specs
[16:09:47] <Alex Petrescu> SG: questions?
[16:09:55] <Alex Petrescu> EK: how are the prefixes allocated?
[16:09:59] <Alex Petrescu> EK: prefix per plane?
[16:10:04] <Alex Petrescu> FT: a plane gets /56
[16:10:13] <Alex Petrescu> FT:
[16:10:22] <Alex Petrescu> EK: every new datalink needs to ... keeps own prefix?
[16:10:27] <Alex Petrescu> EK: register/deregister
[16:10:32] <Alex Petrescu> FT: lowerlevel signalling
[16:10:43] <Alex Petrescu> EK: provisioning happens somewhere else?  at the operator?
[16:10:47] <Alex Petrescu> EK: at factory?
[16:10:55] <Alex Petrescu> FT: ICAO gets a service mobility prefix like a /32
[16:11:07] <Alex Petrescu> FTP: builds a /56 based on the plane serial nunmber?
[16:11:14] <Alex Petrescu> EK: all planes come out of same same /32?
[16:11:21] <Alex Petrescu> EK: ANA its own prefix?
[16:11:31] <Alex Petrescu> FT: air traffic control domain, and the airline operations domain
[16:11:43] <Alex Petrescu> FT: different airlines, united, alaskan, get... not same...
[16:11:53] <Alex Petrescu> EK: if I want to attack all planes everywhere, this slash 32...
[16:12:01] <Alex Petrescu> FT: gateway announced on the Internet or no?
[16:12:07] <Alex Petrescu> EK: ever got a /32 from RIR?
[16:12:13] <Alex Petrescu> FT: not got that prefix yet.
[16:12:18] <Alex Petrescu> FT: even shorter /30
[16:12:23] <Alex Petrescu> EK: which RIR?
[16:12:30] <Alex Petrescu> FT: same topic comes up every time/
[16:12:38] <Alex Petrescu> EK: disconnected?
[16:12:40] <Alex Petrescu> FT: possibliy
[16:12:47] <Alex Petrescu> FT: gateway it to ?
[16:12:55] <Alex Petrescu> FT: safety reliability, avoid DoS from Internet
[16:13:03] <Alex Petrescu> SK: not read the draft, but.
[16:13:06] <Alex Petrescu> SK: concern about
[16:13:29] <Alex Petrescu> SK: about large impact on fht e global routing table... gets advertised multiple times, not going to fly.
[16:13:35] <Alex Petrescu> SK: no pun intended
[16:13:43] <Alex Petrescu> FT: absolutely not that Connexion by Boeing.
[16:13:56] <Alex Petrescu> FT: pairs the mnps , model this in network emulators, I modelled.
[16:14:03] <Alex Petrescu> FT: not milliojn planes...
[16:14:10] <Alex Petrescu> FT: virtual machines
[16:14:14] <Alex Petrescu> SK: NEMO-like?
[16:14:29] <Alex Petrescu> FT: inter -AS mobility, intra AS mobility  with NEMO or AERO
[16:14:36] <Alex Petrescu> SK: ok
[16:14:49] <Alex Petrescu> SK: run this by IDR WG (if there is inter-domain stuff)
[16:14:59] <Alex Petrescu> FT: put it into routing WGs?
[16:15:05] <Alex Petrescu> SK: IDR WG
[16:15:10] <Alex Petrescu> SK: talk to Alia, Alvaro
[16:15:16] <Alex Petrescu> SK:
[16:15:21] <Alex Petrescu> SK: send me an email
[16:15:41] <Alex Petrescu> EK: auth in BGP stuff, inteneded to have auth?  secure pki kind?
[16:15:48] <Alex Petrescu> FT: between the BGP routers an IPsec
[16:16:02] <Alex Petrescu> FT: does plane need tio participate in BGP
[16:16:06] <Alex Petrescu> FT: no
[16:16:18] <Alex Petrescu> FT: the plane does not do any BGP updates
[16:16:27] <Alex Petrescu> EK: so the ground does.
[16:16:38] <Alex Petrescu> SH: that's it
[16:17:17] Meetecho leaves the room
[16:17:23] Dirk von Hugo leaves the room
[16:33:01] Simon Romano leaves the room
[16:35:01] Alex Petrescu leaves the room
[17:55:45] Simon Romano joins the room
[18:18:11] Roger Murray joins the room
[18:18:12] Roger Murray leaves the room
[18:26:06] Simon Romano leaves the room