XSPA TC call

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
METHOD:REQUEST
VERSION:2.0
PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T090000Z
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T100000Z
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
STATUS:CONFIRMED
TRANSP:OPAQUE
DTSTAMP:20170308T003258Z
DTSTART;VALUE=DATE-TIME;TZID=America/Los_Angeles:20170309T100000
DTEND;VALUE=DATE-TIME;TZID=America/Los_Angeles:20170309T110000
SEQUENCE:0
SUMMARY:XSPA TC call
LAST-MODIFIED:20170308T003258Z
ORGANIZER:
ATTENDEE;CUTYPE=GROUP:MAILTO:
DESCRIPTION:https://global.gotomeeting.com/join/610350533\n\nOr\, call i
 n using your telephone.\nDial +1 (571) 317-3112\nAccess Code
  & Meeting ID: 610-350-533\n\nAgenda: Administrivia:\n-    A
 pproval of the last meeting minutes from 8/5/2015:\nhttps://
 lists.oasis-open.org/archives/xspa/201508/msg00001.html\n-  
   Followed up with the comment resolution process with OASIS
  on 3/8/2016:\nhttps://lists.oasis-open.org/archives/xspa/20
 1603/msg00000.html\n- Scheduling the next meeting.\n\nSAML P
 rofile:\n-    The latest draft was posted at: \nhttps://www.
 oasis-open.org/apps/org/workgroup/xspa/document.php?document
 _id=57755\nThe following issues are outstanding:\no    Verif
 ying the correctness of OIDs for normative value sets for th
 e US realm (needs peer review).\no    The question whether t
 o include two separate attributes &quot\;supported-obligatio
 ns&quot\; and &quot\;supported-refrains&quot\; or keep them 
 merged into a single attribute &quot\;supported-caveats&quot
 \; considering the conceptual similarity and potential overl
 ap of attribute value sets. The use-case for this attribute 
 needs to be clarified and articulated.\no    The question wh
 ether the &quot\;CD pointer&quot\; attribute should remain i
 n the specs\, as some members suggested that the stakeholder
 s may no longer need this attribute.\no    If CD pointer att
 ribute is to stay\, should the CD type be specified as a sep
 arate attribute or does the URL\, or the metadata of the dat
 a object\, suffice for specifying the protocol and type/form
 at?\n\n-    There seems to be a need for a standard vocabula
 ry for common obligation and advice values. \n-    There see
 ms to be a need for providing a mapping to encode the attrib
 utes as OpenID Claims.\nGroup: OASIS Cross-Enterprise Securi
 ty and Privacy Authorization (XSPA) TC\nCreator: Mohammad Ja
 fari
URL:https://www.oasis-open.org/apps/org/workgroup/xspa/event.php?event_id=45008
UID:https://www.oasis-open.org/apps/org/workgroup/xspa/event.php?event_id=45008
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR