Hi Sri,
On Tue, Jul 22, 2014 at 10:16 AM, Sri Gundavelli (sgundave) <[email protected]> wrote: > Behcet, > > Check some of the documents in MPLS/Routing areas. Sorry, I am familiar with those areas, they are not in Intarea :-). > > DMM to most part is about deployment. Without bringing the deployment > aspects, documenting DMM solutions will be immature. I am looking at this Softwire document: http://tools.ietf.org/html/draft-ietf-softwire-map-deployment-04 This document is looking into models on how MAP can be deployed on large-scale carrier networks. But the catch is that MAP which is the solution protocol is already defined in a different document by Softwire. So the deployment models IF NEEDED follows the solution selection process. May I suggest you to please come up with a draft including your ideas on the architecture and solution and have it discussed like any other protocol proposals? You may wish to add any deployment concerns there in your draft if you like. Also any architecture work will have implications on the solution and if they are done at the WG level that practically means that a lot of bias on the solutions which are already proposed will be imposed. I don't think that is what the WG wants to do. Regards, Behcet > > > Sri > > > On 7/22/14 8:08 AM, "Behcet Sarikaya" <[email protected]> wrote: > >>Hi Brian, >> >> >>On Tue, Jul 22, 2014 at 9:58 AM, Brian Haberman >><[email protected]> wrote: >>> >>> >>> On 7/22/14 10:49 AM, Jouni Korhonen wrote: >>>> Folks, >>>> >>>> The agenda has been slightly updated (shuffling around the slots and >>>> arranging more time to the charter/next steps discussion). Some >>>> presenters are affected slightly (-5 minutes). see >>>> http://www.ietf.org/proceedings/90/agenda/agenda-90-dmm >>>> >>>> Regarding the re-chartering and the next steps. We have a tight >>>>deadline >>>> to meet if we want to ship the new charter text to the next IESG >>>> telechat. Brian will reveal the gory details of the expected >>>> re-chartering process and timelines. >>>> >>>> We are also supposed to come up (again) with a rought agreement of the >>>> deployment architecture(s) that DMM "functional elements" map into. >> >>Sorry but I don't understand why we have to work on deployment >>architectures? >> >>I don't remember any such work before in IP mobility. Is there any RFC >>that can educate me on this? >> >>I understand that some architecture work is needed. As far as I know >>almost all solution drafts have an architecture. >>Wouldn't that be enough? >> >>Kind regards, >> >>Behcet >> >>>This >>>> will be discussed as a part of the re-chartering slot and recapping the >>>> discussions we had earlier. >>>> >>>> We are also supposed to come up with a rough agreement how to progress >>>> from now on. This could mean (note the conditionality here) a series of >>>> interim meetings and setting up small groups (or design teams) to work >>>> on the initial set of the solution space drafts. We need to step out of >>>> the "progress every second IETF meeting" mode ;) >>> >>> http://www.ietf.org/iesg/statement/interim-meetings.html >>> >>>> >>>> Also keep in mind that the start of the new work poses some >>>> serialization whether we want or now: first stabilize charter & reach >>>> rough consensus on the deployment models/functional elements. These can >>>> be done in parallel. Note that rough consensus does not mean a ready >>>> spec or spec at all. Second execute with the solutions space.. the >>>> deployment models work might benefit from having a slight heads up >>>> before other drafts. These can be done in parallel, though. As a >>>> reminder, the charter may change on the route before it gets approved >>>> but we can do the opportunistic thing and start working as if the >>>> charter were already "approved" when the WG ships it. >>>> >>>> - Jouni & Dapeng >>>> >>>> _______________________________________________ >>>> dmm mailing list >>>> [email protected] >>>> https://www.ietf.org/mailman/listinfo/dmm >>> >>> >>> _______________________________________________ >>> dmm mailing list >>> [email protected] >>> https://www.ietf.org/mailman/listinfo/dmm >>> >> >>_______________________________________________ >>dmm mailing list >>[email protected] >>https://www.ietf.org/mailman/listinfo/dmm > _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
