< draft-elkins-ietf-remote-viewing-hubs-00.txt		draft-elkins-ietf-remote-viewing-hubs-01.txt >
	skipping to change at page 1, line 14 ¶		skipping to change at page 1, line 14 ¶
	Intended Status: Informational Inside Products		Intended Status: Informational Inside Products
	H. Chowdhary		H. Chowdhary
	NIXI		NIXI
	T. Santosh		T. Santosh
	MEITY		MEITY
	V. Hegde		V. Hegde
	Independent		Independent
	Expires: January 4, 2018 July 3, 2017		Expires: January 4, 2018 July 3, 2017
	Remote Viewing Hubs		Remote Viewing Hubs
	draft-elkins-ietf-remote-viewing-hubs-00		draft-elkins-ietf-remote-viewing-hubs-01
	Abstract		Abstract
	For many reasons, remote participation in IETF meetings has increased.		For many reasons, remote participation in IETF meetings has increased.
	As the Internet grows, so does the participation by engineers worldwide.		As the Internet grows, so does the participation by engineers worldwide.
	Remote participation with more than one person is considered a hub.		Remote participation with more than one person is considered a hub.
	Three types of remote hubs are defined. Some exist today; other types		Three types of remote hubs are defined. Some exist today; other types
	may exist in the future. Each has its own characteristics.		may exist in the future. Each has its own characteristics.
	skipping to change at page 3, line 25 ¶		skipping to change at page 3, line 25 ¶
	4.1 Coordinators . . . . . . . . . . . . . . . . . . . . . . . . 5		4.1 Coordinators . . . . . . . . . . . . . . . . . . . . . . . . 5
	4.2 Session Management . . . . . . . . . . . . . . . . . . . . . 6		4.2 Session Management . . . . . . . . . . . . . . . . . . . . . 6
	4.3 Anti-Harassment Procedures . . . . . . . . . . . . . . . . . 6		4.3 Anti-Harassment Procedures . . . . . . . . . . . . . . . . . 6
	4.4 Adherence to Proper Procedures . . . . . . . . . . . . . . . 6		4.4 Adherence to Proper Procedures . . . . . . . . . . . . . . . 6
	4.5 Recording . . . . . . . . . . . . . . . . . . . . . . . . . 6		4.5 Recording . . . . . . . . . . . . . . . . . . . . . . . . . 6
	4.6 Technical Functioning . . . . . . . . . . . . . . . . . . . 6		4.6 Technical Functioning . . . . . . . . . . . . . . . . . . . 6
	4.6.1 Bandwidth . . . . . . . . . . . . . . . . . . . . . . . 6		4.6.1 Bandwidth . . . . . . . . . . . . . . . . . . . . . . . 6
	4.6.2 Physical Room Layout . . . . . . . . . . . . . . . . . . 6		4.6.2 Physical Room Layout . . . . . . . . . . . . . . . . . . 6
	4.6.3 Audio . . . . . . . . . . . . . . . . . . . . . . . . . 7		4.6.3 Audio . . . . . . . . . . . . . . . . . . . . . . . . . 7
	4.7 Responsibilities/Functions of the RVH Coordinators . . . . . 7		4.7 Responsibilities/Functions of the RVH Coordinators . . . . . 7
	4.8 Language of the communication of RVH . . . . . . . . . . . . 8		4.8 Language of the communication of RVH . . . . . . . . . . . . 7
	5 Remote Support Tools . . . . . . . . . . . . . . . . . . . . . 8		5 Remote Support Tools . . . . . . . . . . . . . . . . . . . . . 8
	5.1 Communications . . . . . . . . . . . . . . . . . . . . . . . 8		5.1 Communications . . . . . . . . . . . . . . . . . . . . . . . 8
	6 IETF Secretariat Support . . . . . . . . . . . . . . . . . . . . 8		6 IETF Secretariat Support . . . . . . . . . . . . . . . . . . . . 8
	6.1 Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . 8		6.1 Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	6.2 Wiki / Web Page . . . . . . . . . . . . . . . . . . . . . . 8		6.2 Wiki / Web Page . . . . . . . . . . . . . . . . . . . . . . 8
	6.3 Registration . . . . . . . . . . . . . . . . . . . . . . . . 8		6.3 Registration . . . . . . . . . . . . . . . . . . . . . . . . 8
	7 IETF Liaison . . . . . . . . . . . . . . . . . . . . . . . . . . 8		7 IETF Liaison . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	8 Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8		8 Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	9 Mentoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 9		9 Mentoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	10 Legal Issues . . . . . . . . . . . . . . . . . . . . . . . . . 9		10 Legal Issues . . . . . . . . . . . . . . . . . . . . . . . . . 9
	skipping to change at page 5, line 14 ¶		skipping to change at page 5, line 14 ¶
	(including NOTE-WELL and blue sheets).		(including NOTE-WELL and blue sheets).
	One or more onsite coordinators may be present.		One or more onsite coordinators may be present.
	3 Relationship to IETF Meetings		3 Relationship to IETF Meetings
	The RVH will be at the time of the IETF meeting. An RVH may decide		The RVH will be at the time of the IETF meeting. An RVH may decide
	to have multiple rooms with multiple simultaneous sessions mirroring		to have multiple rooms with multiple simultaneous sessions mirroring
	those at the face-to-face meeting or it may choose to have a single		those at the face-to-face meeting or it may choose to have a single
	room with selected Working Group sessions. This is at the discretion		room with selected Working Group sessions. This is at the discretion
	of the RPH. The sessions to be held at the RPH SHOULD be		of the RVH. The sessions to be held at the RVH SHOULD be
	communicated to the IETF Secretariat for posting in the Wiki.		communicated to the IETF Secretariat for posting in the Wiki.
	It SHOULD also mention any restrictions such as:		It SHOULD also mention any restrictions such as:
	1. Only employees of the hosting organization are allowed		1. Only employees of the hosting organization are allowed
	2. Restrictions on carrying laptops or recording devices		2. Restrictions on carrying laptops or recording devices
	3. Specific proof of identity required to access the premises		3. Specific proof of identity required to access the premises
	3.1 Registration		3.1 Registration
	An attendee at an RPH MAY register and this MAY be noted by the IETF		An attendee at an RVH MAY register and this MAY be noted by the IETF
	Secretariat. This MAY be checked by the onsite co-ordinator, if		Secretariat. This MAY be checked by the onsite coordinator, if any.
	any.
	There may be an online attendance portal having blue sheets provided		There may be an online attendance portal having blue sheets provided
	by IETF Secretariat. The following information may be asked:		by IETF Secretariat. The following information may be asked:
	a. Name		a. Name
	b. Organization		b. Organization
	c. Registration Number		c. Registration Number
	d. Location		d. Location
	3.2 Cost		3.2 Cost
	There may be a charge to attend an RPH. This may be subsidized by		There may be a charge to attend an RVH. This may be subsidized by
	entities wishing to do so.		entities wishing to do so.
	3.3 Timing		3.3 Timing
	An RPH SHOULD be designated at a minimum of 30 days before the IETF		An RVH SHOULD be designated at a minimum of 30 days before the IETF
	meeting.		meeting.
	4 Functioning at Remote Viewing Hubs		4 Functioning at Remote Viewing Hubs
	4.1 Coordinators		4.1 Coordinators
	At least one or preferably two (2) coordinators SHOULD be appointed		At least one or preferably two (2) coordinators SHOULD be appointed
	by the RPH. Contact information MUST be provided to the IETF		by the RVH. Contact information MUST be provided to the IETF
	Secretariat for inclusion in the calendar / Wiki.		Secretariat for inclusion in the calendar / Wiki.
	4.2 Session Management		4.2 Session Management
	Session management as described in RFC2418: IETF Working Group		Session management as described in RFC2418: IETF Working Group
	Guidelines and Procedures [RFC2418] Section 3.3 Session Management		Guidelines and Procedures [RFC2418] Section 3.3 Session Management
	does not apply to Remote Viewing Hubs.		does not apply to Remote Viewing Hubs.
	The coordinators may wish to explain the NOTE Well which is shown at		The coordinators may wish to explain the NOTE Well which is shown at
	the start of the meeting. Mike queuing discipline and fairness do		the start of the meeting. Mike queuing discipline and fairness do
	skipping to change at page 8, line 6 ¶		skipping to change at page 8, line 4 ¶
	5. Submit the count of attendees to the IETF Secretariat.		5. Submit the count of attendees to the IETF Secretariat.
	6. Set up the space with the appropriate furniture, equipment and		6. Set up the space with the appropriate furniture, equipment and
	materials for the IETF WG session each day.		materials for the IETF WG session each day.
	7. Create a documentation process through photos and keep an		7. Create a documentation process through photos and keep an
	organized archive for the sessions.		organized archive for the sessions.
	4.8 Language of the communication of RVH		4.8 Language of the communication of RVH
	The RVH may communicate in any language desired.		The RVH may communicate in any language desired.
	5 Remote Support Tools		5 Remote Support Tools
	The remote support tools used are at the discretion of the RVH.		The remote support tools used are at the discretion of the RVH.
	5.1 Communications		5.1 Communications
	The remote communications methods today include Jabber and MeetEcho.		The remote communications methods today include Jabber and MeetEcho.
	These shall be used. If new methods arise, then they may be used as		These shall be used. If new methods arise, then they may be used as
	well.		well.
	6 IETF Secretariat Support		6 IETF Secretariat Support
	6.1 Calendar		6.1 Calendar
	The IETF Secretariat will maintain a calendar of locations and times		The IETF Secretariat will maintain a calendar of locations and times
	for all RVH's for that IETF meeting. Historical information SHOULD		for all RVHs for that IETF meeting. Historical information SHOULD
	be kept according to the section on Metrics.		be kept according to the section on Metrics.
	6.2 Wiki / Web Page		6.2 Wiki / Web Page
	The IETF Secretariat will maintain a Wiki or web page indicating		The IETF Secretariat will maintain a Wiki or web page indicating
	which working group sessions are being held at the RVH. This		which working group sessions are being held at the RVH. This
	information SHOULD be kept historically according to the section on		information SHOULD be kept historically according to the section on
	Metrics.		Metrics.
	6.3 Registration		6.3 Registration
	The IETF Secretariat MAY account for all registrations at an RPH.		The IETF Secretariat MAY account for all registrations at an RVH.
	Historical information MAY be kept according to the section on		Historical information MAY be kept according to the section on
	Metrics.		Metrics.
	7 IETF Liaison		7 IETF Liaison
	An IETF liaison is not needed for an RVH.		An IETF liaison is not needed for an RVH.
	8 Metrics		8 Metrics
	The following metrics SHOULD be kept for RVH's:		The following metrics SHOULD be kept for RVHs:
	- Location (Economy / name of country)		- Location (Economy / name of country)
	- Name		- Name
	- Name of coordinators		- Name of coordinators
	- Number of attendees registered		- Number of attendees registered
	- Number of sessions		- Number of sessions
	- The Working Groups followed		- The Working Groups followed
	- Number of participants in each session (regardless of time)		- Number of participants in each session (regardless of time)
	Metrics may Include the following questions to the RVH. Potential		Metrics may Include the following questions to the RVH. Potential
	skipping to change at page 9, line 42 ¶		skipping to change at page 9, line 40 ¶
	Participation in an RVH will not be considered a contribution to the		Participation in an RVH will not be considered a contribution to the
	IETF. Issues of Intellectual Property Rights, confidentiality, trade		IETF. Issues of Intellectual Property Rights, confidentiality, trade
	marks, etc. as noted by the appropriate section in RFC5378: Rights		marks, etc. as noted by the appropriate section in RFC5378: Rights
	Contributors Provide to the IETF Trust [RFC5378] do not apply to an		Contributors Provide to the IETF Trust [RFC5378] do not apply to an
	RVH.		RVH.
	10.2 Note Well		10.2 Note Well
	A "note well" as is commonly used at face-to-face meetings need not		A "note well" as is commonly used at face-to-face meetings need not
	be shown at an RPH session.		be shown at an RVH session.
	10.3 IETF Brand / Logo		10.3 IETF Brand / Logo
	The IETF logo may be used to in an RVH with the prior approval of the		The IETF logo may be used to in an RVH with the prior approval of the
	IETF trustees.		IETF trustees.
	11 Security Considerations		11 Security Considerations
	There are no security considerations.		There are no security considerations.
	12 IANA Considerations		12 IANA Considerations
	There are no IANA considerations.		There are no IANA considerations.
	13 References		13 References
	13.1 Normative References		13.1 Normative References
End of changes. 13 change blocks.
	14 lines changed or deleted		13 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/