Jouni Korhonen | 4 Jul 20:44 2015
Picon

Draft agenda out..

Folks,

The very draft agenda is out, see:
http://www.ietf.org/proceedings/93/agenda/agenda-93-dmm

The slots are mostly in FIFO order. And the agenda is already full and I 
am tempted to drop stuff out in order to arrange longer slots. 
Concentarte on topics you actually want feedback, discussion and get the 
feel of the room..

Just to be more prepared send your material to the chairs by Thursday 
noon 16th July (PDT). Failing that you might lose your slot.. I want to 
upload all material during Friday/Saturday since we meet on Monday and 
folks travel during the weekend. If you want to have some decision made 
let the chairs also know that in advance..

- Jouni & Dapeng
Seil Jeon | 25 Jun 01:33 2015
Picon

FW: New Version Notification for draft-sijeon-dmm-use-cases-api-source-01.txt

We just have submitted the update of the use cases and API extension draft (-01), based on the discussion in
the list.

Regards,
Seil Jeon

-----Original Message-----
From: internet-drafts@...
[mailto:internet-drafts@...] 
Sent: Thursday, June 25, 2015 12:27 AM
To: Young-Han Kim; Younghan Kim; Sergio Figueiredo; Seil Jeon; Seil Jeon; Sergio Figueiredo
Subject: New Version Notification for draft-sijeon-dmm-use-cases-api-source-01.txt

A new version of I-D, draft-sijeon-dmm-use-cases-api-source-01.txt
has been successfully submitted by Seil Jeon and posted to the IETF repository.

Name:		draft-sijeon-dmm-use-cases-api-source
Revision:	01
Title:		Use Cases and API Extension for Source IP Address Selection
Document date:	2015-06-24
Group:		Individual Submission
Pages:		7
URL:            https://www.ietf.org/internet-drafts/draft-sijeon-dmm-use-cases-api-source-01.txt
Status:         https://datatracker.ietf.org/doc/draft-sijeon-dmm-use-cases-api-source/
Htmlized:       https://tools.ietf.org/html/draft-sijeon-dmm-use-cases-api-source-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-sijeon-dmm-use-cases-api-source-01

Abstract:
   This draft specifies and analyzes the expected cases regarding the
   selection of a proper source IP address and address type based on the
(Continue reading)

Marco Liebsch | 22 Jun 22:04 2015
Picon

Planning WebEx about FPC draft update /RE: draft-ietf-dmm-fpc-cpdp-00 - update plans

Please find a link to a doodle below to find a suitable date for a WebEx where we
can discuss and agree on the FPC draft update.

 

Please also think about the open items I addressed in my previous eMails or any additional
item you have in mind and which we need to consider for a draft update. Please use the mailing
list or the issue tracker to address these items for discussion.

 

http://doodle.com/5s9dhzcy6w8ds6ae

 

Thanks,

Marco

 

 

 

From: dmm [mailto:dmm-bounces-EgrivxUAwEY@public.gmane.org] On Behalf Of Marco Liebsch
Sent: Freitag, 19. Juni 2015 15:36
To: dmm-EgrivxUAwEY@public.gmane.org
Subject: [DMM] draft-ietf-dmm-fpc-cpdp-00 - update plans

 

Folks,

draft-ietf-dmm-fpc-cpdp-00  is out since May. So far we did not receive any serious issue to address, which is good.

Driving the draft towards a more mature state, I see the following main items to address:

 

(1)    Completion of properties and attributes

(2)    Adoption of a standard conform modelling

 

In terms of (1), the importance to include QoS attributes has been raised from different sides.

I’ll make a proposal how to cover this in an update on the DMM ML using a separate eMail.

Other attributes we may need to cover are about monitoring/reporting.

 

In terms of (2) we heard different opinions about keeping this document at the level of information models
or be more specific by adopting data modeling. So far the document is pretty hybrid ;-), core part is more about
clear definition and description of messages and information to apply between Client and Agent. In the appendix
the draft includes a (so far experimental) YANG model.

 

Please state your opinion here to see what the WG expects from the document. If we adopt information modeling,
this seems straightforward from a version which is complete in terms of messages/attributes.
If we adopt data modeling, we may need to spend more cycles in agreeing formats, alignment, etc.

 

Hope we can discuss on the ML. I’d also like to schedule a WebExt before the draft deadline. Will send a
doodle around for that.

 

marco

 

 

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Marco Liebsch | 19 Jun 16:31 2015
Picon

How to cover QoS in draft-ietf-dmm-fpc-cpdp-00

Folks,

as announced in my previous eMail, please find below a proposal how to address QoS in
draft-ietf-dmm-fpc-cpdp-00.

 

The draft adopts a model to abstract forwarding and policy configuration for DMM using
logical ports which bind properties. This can be applied at Agents to any Data-Plane Node (DPN)
configuration, routers, network controllers, switches.

 

Adding QoS properties per port should be in-line with RFC7222 in case of GBR and MBR.

More needs to be considered for aggregates, such as per-MN-AMBR, per-Session-AMBR.
Here, the Control-Plane logic may accomplish configuration of the Data-Plane for an
MN or Session using a single port or multiple ports.

 

This can be tackled by permitting a Client to bind an AMBR attribute/value to a single port or
to a group of ports. Whether the aggregate applies per-MN or per Session, should be kept
in the application logic and be kept transparent to the Data-Plane.

Information coming with an AMBR attribute needs to comprise a list
of port identifies (PRT_ID) to which the aggregate applies, like:

 

QOS_AMBR_CONF:

  Aggregate Bitrate  //gives the maximum aggregate value

  List of Port-IDs   //defines the group of ports where metering applies          

    

Please let me know if anything is missing.

 

marco

 

 

 

 

 

 

 

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Marco Liebsch | 19 Jun 15:36 2015
Picon

draft-ietf-dmm-fpc-cpdp-00 - update plans

Folks,

draft-ietf-dmm-fpc-cpdp-00  is out since May. So far we did not receive any serious issue to address, which is good.

Driving the draft towards a more mature state, I see the following main items to address:

 

(1)    Completion of properties and attributes

(2)    Adoption of a standard conform modelling

 

In terms of (1), the importance to include QoS attributes has been raised from different sides.

I’ll make a proposal how to cover this in an update on the DMM ML using a separate eMail.

Other attributes we may need to cover are about monitoring/reporting.

 

In terms of (2) we heard different opinions about keeping this document at the level of information models
or be more specific by adopting data modeling. So far the document is pretty hybrid ;-), core part is more about
clear definition and description of messages and information to apply between Client and Agent. In the appendix
the draft includes a (so far experimental) YANG model.

 

Please state your opinion here to see what the WG expects from the document. If we adopt information modeling,
this seems straightforward from a version which is complete in terms of messages/attributes.
If we adopt data modeling, we may need to spend more cycles in agreeing formats, alignment, etc.

 

Hope we can discuss on the ML. I’d also like to schedule a WebExt before the draft deadline. Will send a
doodle around for that.

 

marco

 

 

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Sri Gundavelli (sgundave | 18 Jun 02:05 2015
Picon

DMM WT#4 - 2 Discussion

Thanks for all the discussion on the WT#4 call. Attendees: Marco Liebsch, Danny Moses, Jouni Korhonen, Dapeng Liu, Seil, Vic Liu, Fu Qiao,  Sri ..

The Poll is now closed for the next call.

Date: Tuesday, June 23rd at 7AM PDT
WebEx Details below
Agenda:
  1. Seil Jeon will present his new proposal
  2. Anthony Chen will talk about "Functions of Anchor” (Tentative)
  3. Follow up discussion on the attribute based node selection/Deployment models
  4. Follow up discussion on the CP/DP interface in relation to the WT4 discussions




div,p,td,span {word-wrap: break-word;word-break: normal;} table {border-collapse: separate; border: 0;border-spacing: 0;border-color: white; width:100%!important;width:525px; max-width:525px!important; min-width: 279px!important;} tr {line-height: 20px;} td,a {font-size: 15px;font-family: Arial;color: #666666;padding:0;}
Hi, Sri Gundavelli,
You are the host for this WebEx meeting.
Host key: 480131 (Use this to reclaim host privileges.)
 
DMM WT#4 Discussion
Tuesday, June 23, 2015
7:00 am  |  Pacific Daylight Time (San Francisco, GMT-07:00)  |  1 hr 30 mins
 
Join WebEx meeting
Meeting number: 209 370 954
Meeting password: DMM
 
Join by phone
+1-408-525-6800 Call-in toll number (US/Canada)
+1-866-432-9903 Call-in toll-free number (US/Canada)
Access code: 209 370 954
Global call-in numbers  |  Toll-free calling restrictions
 
Add this meeting to your calendar.
 
Can't join the meeting? Contact support.
 
IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. You should inform all meeting attendees prior to recording if you intend to record the meeting.
Attachment (WebEx_Meeting.ics): application/octet-stream, 5613 bytes
_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Moses, Danny | 17 Jun 10:20 2015
Picon

New revision of the draft-moses-dmm-dhcp-ondemand-mobility I-D

Hi,
 
We have uploaded a new revision of the draft-moses-dmm-dhcp-ondemand-mobility I-D.
 
This revision includes the following:
  1. Support for requesting a specific type for an IPv6 prefix as well as an IPv6 address
  2. Add a new DHCPv6 option for a client to request a specific prefix (expressing its desire to be served by a specific Mobility Anchor)
  3. Added diagrams and corrected text
 
The first addition was in reply for a request from several people to include prefix delegation support.
 
Please review and send us comments.
 
Thanks,
        Alper and Danny
 
 

---------------------------------------------------------------------
A member of the Intel Corporation group of companies

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Sri Gundavelli (sgundave | 9 Jun 17:39 2015
Picon

DMM WT#4 Conf Call

Poll is now closed for the first meeting.

Date: Tuesday, June 16th at 7AM PDT

Agenda:
  1. Fu Qiao will present on "Virtual CPE Support in DMM Architectures" 
  2. Anthony Chen will talk about "Functions of Anchor"
  3. I will provide an update on the Deployment Models/Architectural Considerations
  4. Discussion on the DMM Function Selection based on Service Attributes


DMM WT#4 Updates
Tuesday, June 16, 2015
7:00 am  |  Pacific Daylight Time (San Francisco, GMT-07:00)  |  2 hrs
 
Join WebEx meeting
Meeting number: 205 745 742
Meeting password: dmm
 
Join by phone
+1-408-525-6800 Call-in toll number (US/Canada)
+1-866-432-9903 Call-in toll-free number (US/Canada)
Access code: 205 745 742
Global call-in numbers  |  Toll-free calling restrictions
 
Add this meeting to your calendar.
 
Can't join the meeting? Contact support.
 
IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. You should inform all meeting attendees prior to recording if you intend to record the meeting.
div,p,td,span {word-wrap: break-word;word-break: normal;} table {border-collapse: separate; border: 0;border-spacing: 0;border-color: white; width:100%!important;width:525px; max-width:525px!important; min-width: 279px!important;} tr {line-height: 20px;} td,a {font-size: 15px;font-family: Arial;color: #666666;padding:0;}
Attachment (WebEx_Meeting.ics): application/octet-stream, 5609 bytes
_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Templin, Fred L | 8 Jun 23:29 2015
Picon

Scaling properties of AERO

Hi,

I finally had a chance to sit back and think about the scaling properties of AERO,
and I think it is within reason for each AERO link to service O(10^9) Clients. Here
is what I wrote in the latest AERO draft version:

   "Scaling properties of the AERO routing system are therefore limited
   by the number of BGP routes that can be carried by Relays.  Assuming
   O(10^6) as a maximum number of BGP routes, this means that at most
   O(10^6) Clients can be serviced by Relays within a single BGP
   instance.  A means of increasing scaling would be to assign a
   different set of Relays for each set of ASPs, and still have each
   Server peer with each Relay but with a distinct BGP instance for each
   Relay set.  Another possibility would be for Servers to institute
   route filters within a single BGP instance so that each set of Relays
   only receives BGP updates for the ASPs they aggregate.

   Assuming up to O(10^3) sets of Relays, scaling can then accommodate
   O(10^9) Clients with no additional overhead for Servers and Relays.
   In this way, each set of Relays services a specific set of ASPs that
   they advertise to peers outside of the AERO link, and each Server
   configures ASP-specific routes that list the correct set of Relays as
   next hops."

https://datatracker.ietf.org/doc/draft-templin-aerolink/

Comments?

Thanks - Fred
fred.l.templin@...
h chan | 5 Jun 20:45 2015

Enhanced mobility anchoring

The first part of the teleconference was at 9:30-10:30 Central Daylight Time on Friday May 22.

The second part of the teleconference was at 9:30-10:30 Central Daylight Time on Wednesday May 27.

 

Attendance: Seil Jon, Carlos Bernardos, Fred Templin, Jong-Hyouk Lee, Anthony Chan

 

Seil presented using the slides at:

https://www.dropbox.com/s/rpy6gfxon76qwhm/2015.05.22_enhanced%20mobility%20anchoring_%28Seil_Jeon%29.pdf?dl=0

 

Different cases are described based on different configurations of the functions defined in RFC7429.

 

Carlos commented that Anchoring Function as defined in RFC7429 is only describing one of the functions of a mobility anchor in the control plane. For example in MIP, the mobility anchor also has data plane functions. Suggest discussions on the functions of anchor.

 

Fred suggested to generalize case #3 into 2 cases for which LM may be either centralized or distributed. The case with distributed LM is consistent with AERO.

 

Discussions on the anchor functions were made.

 

Anthony discussed that there are different functions of the anchor in different proposed solutions. What are common among them seems to be on allocation of IP prefixes and route advertisement.

 

Seil suggests to split the AF definition into control plane: AF-CP and data plane: AF-DP.

Jong-Hyouk suggests text for such changes.

Here, AF-CP are the functions of Control Plane anchor, whereas the AF-DP are the functions of Data Plane anchor. The name given to the functions of prefix allocation and router advertisement is then AF-CP.

 

Carlos commented that anchoring should be a data plane concept, while control plane functions are making it to happen.

 

Seil asked whether to change the name to address management.

 

Before we can find a suitable name, it may be possible to simply describe IP address anchoring as in slide #5 in the attached file.

 

H Anthony Chan

 

From: h chan
Sent: Tuesday, May 19, 2015 12:37 PM
To: 'dmm <at> ietf.org'
Subject: RE: Enhanced mobility anchoring

 

Let us schedule 2 teleconferences (one hour each) to accommodate everyone in the doodle list:

 

1st teleconference: Friday May 22 at 9:30-10:30AM US Central Time

 

2nd teleconference: Wednesday May 27 at 9:30-10:30AM US Central Time

 

Thanks.

 

H Anthony Chan

Attachment (EnhancedMobilityAnchor.20150527.4.pptx): application/vnd.openxmlformats-officedocument.presentationml.presentation, 117 KiB
_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Templin, Fred L | 1 Jun 18:57 2015
Picon

Forwarding/Control Plane separation in AERO

Hi,

Much has been said about managing forwarding and control plane separation
in DMM. AERO now has a new method for doing this based on DHCPv6.

In AERO, the control plane is managed by the AERO Server. AERO Clients use
DHCPv6 PD messaging in order to register themselves with AERO Servers and
to update their access network addresses based on mobility events. The
AERO Server in turn maintains PD state for each AERO Client and also provides
default forwarding services for each Client. However, it would be desirable
for Servers to offload forwarding services to Forwarding Agents that can
handle high-speed data plane operations and therefore offload the Server.

In order to support this offload, when the AERO Server prepares a Reply to
a Client's DHCPv6 Request/Renew/Rebind/Release message, it forwards
the Reply to the Forwarding Agent instead of directly to the Client. The
Forwarding Agent then creates forwarding state and returns the Reply
to the Server, which then forwards the Reply to the Client. Now, the Server
and Forwarding Agent both have the necessary state synchronization, or
if any control messages are lost the Client will retransmit. Future data
packets can then flow through the Forwarding Agent without burdening
the Server.

This behavior now documented in Section 3.16 of the AERO spec:

https://datatracker.ietf.org/doc/draft-templin-aerolink/

With this behavior, the AERO Server and Forwarding Agent act as two halves
of a whole router, with the Server handling the control plane and the
Forwarding Agent handling the data plane. Each Server can further associate
with multiple Forwarding Agents if there is a desire to distribute the data
plane function to multiple agents.

This is a simple and effective solution for DMM forwarding and control
plane separation. I would be happy to talk more about this either on
the list or at the upcoming IETF. Comments?

Thanks - Fred
fred.l.templin@...

Gmane