[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Interim attendance survey
Sharon Chisholm wrote:
hi
There were a number of people who said they could attend depending on
location and dates. Let's try some other dates
3. Week of May 8th
4. Week of May 15th
5. Week of June 5th
I want to make sure there is time to publish
an updated draft before the I-D cutoff for Montreal.
I think the most realistic choices would be in
Montreal, either before (Th, July 6 - Sat, July 8)
or after (Fri July 14 - Sun July 16) IETF #66.
where 1 was week of May 22nd and 2 was week of May 29th.
Of course, we could also consider a series of teleconference, but it is
difficult to get a timeslot that works for everyone.
I am considering another approach.
Putting your document on the shelf and forcing
the WG to write a Requirements specification first.
The current draft doesn't even have a Requirements section.
We have no agreement on why we need notifications
in NETCONF and what specific roles they serve.
We don't event agree on whether notification content
is part of the problem space or not.
I could argue that the SYSLOG WG should standardize the
protocol and contents for system logging messages, not NETCONF.
There are some people (including myself) who think
that if we are going to work on data models, we should
work on configuration data models, not notification content.
Sharon
Andy
-----Original Message-----
From: Andy Bierman [mailto:ietf@andybierman.com]
Sent: Tuesday, March 28, 2006 9:14 AM
To: Romascanu, Dan (Dan)
Cc: Chisholm, Sharon [CAR:ZZ00:EXCH]; Netconf (E-mail)
Subject: Re: Interim attendance survey
Romascanu, Dan (Dan) wrote:
I am not sure either about what week we are talking.
If this is about the week of May 22, I cannot make it at all.
If it's the week of May 29, I could possibly make May 29-31, but need
to be back to Israel in the morning of June 1st.
The first week of June would be much better.
I am just trying to get an idea of who would show up.
So far (besides the authors and 1 co-chair, which doesn't
even count) there are about 2 people who can attend
an interim at the end of May in London.
I don't think there is enough interest to hold an interim.
If the interim is too late, then there won't
enough time afterwards to get a new draft out
before the I-D cutoff for Montreal.
Dan
Andy
-----Original Message-----
From: owner-netconf@ops.ietf.org
[mailto:owner-netconf@ops.ietf.org] On Behalf Of Sharon Chisholm
Sent: Tuesday, March 28, 2006 2:21 PM
To: Netconf (E-mail)
Subject: RE: Interim attendance survey
hi
I take it this date is based on availability of a venue or something?
I have a personal commitment in Ottawa the morning of May
27th. If we do that week, if we can do it earlier in the week
to ensure I'm back (not jet lagged might be too much to ask
for), I'd really appreciate it.
Sharon
-----Original Message-----
From: owner-netconf@ops.ietf.org
[mailto:owner-netconf@ops.ietf.org] On Behalf Of Andy Bierman
Sent: Monday, March 27, 2006 7:54 PM
To: Orly Nicklass
Cc: Netconf (E-mail)
Subject: Re: Interim attendance survey
Orly Nicklass wrote:
Option 2 that might turn to 3 if it takes place 1st or 2nd
weekend of
June in the US.
Nope. Last week in May in London, UK
Andy
--
to unsubscribe send a message to netconf-request@ops.ietf.org
with the word 'unsubscribe' in a single line as the message text
body.
archive: <http://ops.ietf.org/lists/netconf/>
--
to unsubscribe send a message to netconf-request@ops.ietf.org
with the word 'unsubscribe' in a single line as the message text
body.
archive: <http://ops.ietf.org/lists/netconf/>
--
to unsubscribe send a message to netconf-request@ops.ietf.org with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>