in-line as ever On Wed, Jul 31, 2013 at 7:14 AM, Carlos Pignataro (cpignata) < [email protected]> wrote:
> > On Jul 31, 2013, at 12:57 PM, Joe Marcus Clarke <[email protected]> wrote: > > Section 2: > > read scope: ... > > write scope: ... > > JMC: Should there be an event or notification scope in addition to read > and write? > > > +1 to this point. I think that it should also include some words about > pub/sub. > [Alia] I think about the read scope as including the event or notification scope - at least unless and until we have to have the extra complexity of terminology. I don't see where or why read scope and notification scope need to be separate concepts?? > Section 6.6 covers some of this though, so perhaps a forward reference. > [Alia] In the terminology section?? If we needed notification scope, ok - but I don't see an argument for it to be separated... Alia > Thanks, > > -- Carlos. >
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
