Re: [savi] Adopting draft-bagnulo-savi-fcfs/send

["Frank Xia" <xiayangsong at huawei.com>]

Hi Marcelo

I am sorry for the ignorance because
of my absence of SAVI work recently.

Anyway, these days are holiday :-)

I would like to prioritize SAVI work in
next few days.

BR
Frank

----- Original Message ----- 
From: "marcelo bagnulo braun" <marcelo at it.uc3m.es>
To: "Frank Xia" <xiayangsong at huawei.com>
Cc: "Christian Vogt" <christian.vogt at ericsson.com>; "SAVI Mailing List" 
<savi at ietf.org>; "Ana Kukec" <ana.kukec at fer.hr>
Sent: Thursday, January 08, 2009 6:36 AM
Subject: Re: [savi] Adopting draft-bagnulo-savi-fcfs/send


> Hi Frank,
>
> I am a bit puzzled by you mail.
>
> During consensus call for adopting the FCFS draft as a WG item, you 
> explicitly stated that you were not against FCFS as well.
> You raised a set of issues in your mail from 18 of dec, namely:
>
>
> >It seems to be hard to deal with the following scenarios:
> >1)A host is authorized to use a static address, while
> > the host does not connect the network
> >2)A IPv6 host periodically changes it's  interface ID
> >  from privacy consideration.
> >3)In dynamic address configuration,  an IP address
> >  can be reused by other hosts.
>
> I answer to each of these points in a follow up email in the same date 
> answering some of the issues and asking for calrification on others, but 
> you never answered back
>
> So either you agree with me and you feel the issues can be solved as i 
> suggested or you should anser soemthing back. IETF work on rough 
> consensus, which is build on disucssions. Saying that you don't like 
> something and not describing why this is so it is hardly a good way to 
> make progress. I don't think it is ok not to reply for weeks and then 
> simply restate that you don't like something with no arguments.
>
> Regards, marcelo
>
>
> Frank Xia escribió:
> > Hi Christian
> >
> > It seems to be a little bit rush :-).
> >
> > I don't think people have enough
> > time to read your previous email.
> >
> > For my understanding,  it is hard
> > to hard to say "STRONG" support
> > for the FCFS principle.
> > At least, I can not  find strong support
> > through this long discussions in the mailing list.
> >
> > IMHO, the decision should be based
> > rough consensus by WG.  IETF is based
> > on mailing list.
> > BR
> > Frank
> >
> > ----- Original Message ----- From: "Christian Vogt" 
> > <christian.vogt at ericsson.com>
> > To: "SAVI Mailing List" <savi at ietf.org>
> > Cc: "Ana Kukec" <ana.kukec at fer.hr>
> > Sent: Wednesday, January 07, 2009 9:34 PM
> > Subject: [savi] Adopting draft-bagnulo-savi-fcfs/send
> >
> >
> > > Folks -
> > >
> > > We had a discussion regarding the adoption of individual Internet drafts
> > > as official documents of the SAVI working group.  I would like to
> > > conclude this discussion for the following two Internet drafts:
> > >
> > > - draft-bagnulo-savi-fcfs
> > > - draft-bagnulo-savi-send
> > >
> > > The feedback we got at the SAVI meeting in Minneapolis and on this
> > > mailing list shows that there is strong support for the FCFS principle,
> > > which is the baseline of both of the above Internet drafts.  A couple of
> > > issues have been identified, and these will have to be addressed.  But
> > > the issues are no showstoppers in my opinion.  In fact, many of them
> > > apply to specific instantiations of the FCFS principle rather than to
> > > the FCFS principle itself.
> > >
> > > I have therefore decided to adopt the above Internet drafts as SAVI
> > > working group documents.  Draft-bagnulo-savi-fcfs will be continued
> > > as draft-ietf-savi-fcfs with Erik Nordmark, Marcelo Bagnulo, and Fred
> > > Baker as editors.  Draft-bagnulo-savi-send will be continued
> > > as draft-ietf-savi-send with Ana Kukec, Marcelo Bagnulo, Jianping Wu,
> > > and Jun Bi as editors.
> > >
> > > Of course, the documents are far from completion; there is much work
> > > ahead.  And part of this work will be to address the issues that were
> > > raised during the foregoing discussion.  Those are in summary:
> > >
> > > - Lack of support for pre-configured, static addresses (Frank Xia).
> > >
> > > - Possible DoS attacks where an attacker tricks a SAVI device into
> > >   blocking an address that a victim host is about to configure (Guang
> > >   Yao).
> > >
> > > - Possible loss of synchronizing between a host and the responsible SAVI
> > >   device regarding the host's right to use an address (Guang Yao).
> > >
> > > - Need to protect target addresses in Neighbor Discovery messages
> > >   similarly to source addresses in regular packets (Guang Yao).
> > >
> > > - Filtering load for switches (Lin Tao):  How much load do we impose on
> > >   a switch by requiring it to filter out and monitoring certain
> > >   packets.
> > >
> > > - Strength of binding anchors (Dong Zhang):  SAVI will work with various
> > >   binding anchors of different security strength.  SAVI specifications
> > >   should provide guidance for selecting a binding anchor.  We already
> > >   decided to provide such guidance in SAVI specifications.
> > >
> > > As a starting point, I would like the current, unmodified versions of
> > > above Internet drafts to be re-submitted with their new names
> > > (draft-ietf-savi-*).  Editors, please go ahead and do so.
> > >
> > > - Christian
> > >
> > >
> > > _______________________________________________
> > > savi mailing list
> > > savi at ietf.org
> > > https://www.ietf.org/mailman/listinfo/savi
> >
> > _______________________________________________
> > savi mailing list
> > savi at ietf.org
> > https://www.ietf.org/mailman/listinfo/savi