Subject: [fmc] Minutes of the Bar BoF in Orlando on Monday

From: Behcet Sarikaya <[email-masked]>
Date: Tue, 12 Mar 2013 09:16:05 -0500

Yes, we did have the meeting yesterday. Not many people attended but the
meeting was pretty productive.

Issues discussed:

Industry involvement. Pierrick mentioned that other SDOs like BBF can be
involved in matters related to the address sharing, aka host id, possibly
by the next meeting in early June. Rudiger also agreed to provide help from
his side. The aim here is to get them ask IETF for some solution work.

There was agreement to work on the address sharing/prefix sharing problem
as the main issue. UE mobility which was identified in the last year's BoF
and multiple device issue will be possibly included.

We also discussed mailing list activity. The list members are encouraged to
keep the list active with technical discussions. We need more mails on the
list.

One thing I would like to add is to call for solution related drafts. If we
have such drafts they could be the basis for more technical discussions on
the list.

Regards,

Behcet

On Mon, Mar 11, 2013 at 9:26 AM, Behcet Sarikaya <[email-masked]>wrote:

> Folks let's make it 5pm to enable people attending the plenary.
>
> So start at 5pm. The rest is the same.
>
>
>
> On Sun, Mar 10, 2013 at 7:44 PM, Behcet Sarikaya <[email-masked]>wrote:
>
>> Folks, as Dirk mentioned, we will have a meeting in Orlando
>>
>> on Monday March 11 at 6pm in Grand Sierra B room
>>
>> We hope to discuss:
>> Address sharing issues draft,
>>
>> http://tools.ietf.org/html/draft-boucadair-intarea-host-identifier-scenarios-02
>>
>> Those problems cover e.g. unwanted sharing of
>> o  Blacklist for misbehaviour
>> o  Enforced policy (tayloring service offering)
>> o  Access denial due to failing service invoking
>> o  Missing correct correlation between internal address:port and external
>> address:port required for policy issues
>>
>>
>> Prefix sharing issues draft,
>>
>> http://www.ietf.org/internet-drafts/draft-sarikaya-fmc-prefix-sharing-usecase-01.txt
>>
>> and more importantly, the next steps.
>>
>>
>> See you.
>>
>> Behcet
>>
>
>