Hello folks,
Here are few clarification questions and comments on the Forwarding Path
Signaling Management WT discussion material (oh, maybe it's time we start
numbering these WTs :-)
http://www.ietf.org/proceedings/interim/2014/10/07/dmm/slides/slides-interim-2014-dmm-3-1.pdf
- Are we not
Alper,
Inline Š
On 10/16/14 1:32 AM, Alper Yegin alper.ye...@yegin.org wrote:
Hello folks,
Here are few clarification questions and comments on the Forwarding Path
Signaling Management WT discussion material (oh, maybe it's time we
start numbering these WTs :-)
Charlie – Are you asking the WG/chairs for draft adoption ? The current
version can be a good starting point and can be taken up as the –00 version of
the WG draft. Off course, you still have plenty of comments on additional types
values that the draft still needs to address :), but the
Hi,
On roaming:
Sri, I guess you meant inter-controller interface, right? IMU, roaming is
about coordination between controller belonging to different administrative (or
routing?) domain.
Sri already clarified this, but I think it is important to insist on the fact
that the wort item shall
Hi Pierrick,
Yes; Typo. Its inter-controller interface.
We have to look at DMM as a mobility domain and the interactions/protocol
interfaces are between the entities within that domain. The roaming is
more about a business relation and about security agreements. I do not
believe we need to model
Please see inline for my opinion about your questions to slide 6-8.
-Original Message-
From: dmm [mailto:dmm-boun...@ietf.org] On Behalf Of Sri Gundavelli
(sgundave)
Sent: Donnerstag, 16. Oktober 2014 10:58
To: Alper Yegin; dmm@ietf.org
Subject: Re: [DMM] Forwarding Path Signaling
Folks,
IESG has approved our new charter. Now we can execute at the full speed
in the solution space!
- Jouni Dapeng
___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm
Sri,
- Should QoS really be part of this work? I think notŠ
[Sri] There is QoS support in all mobility architecture. QoS is tied to
subscription and a key function of the mobility gateway. The CP entity
should be able to provide the QoS parameters to the DP entity
I'd say let's not deal
