rfc9698v3.txt		rfc9698.txt
	skipping to change at line 172 ¶		skipping to change at line 172 ¶
	The server processes the command successfully. It knows that the		The server processes the command successfully. It knows that the
	client used OAuth, and that it and its JMAP alter ego use the same		client used OAuth, and that it and its JMAP alter ego use the same
	OAuth backend subsystem. Because of that it infers that the (next)		OAuth backend subsystem. Because of that it infers that the (next)
	access token is just as usable via JMAP as via IMAP. It includes a		access token is just as usable via JMAP as via IMAP. It includes a
	JMAPACCESS capability in its reply (again, real capability lists are		JMAPACCESS capability in its reply (again, real capability lists are
	much longer):		much longer):
	S: 1 OK [CAPABILITY IMAP4rev1 JMAPACCESS] done		S: 1 OK [CAPABILITY IMAP4rev1 JMAPACCESS] done
	C: 1b GETJMAPACCESS		C: 1b GETJMAPACCESS
	S: * JMAPACCESS "https://example.com/jmap"		S: * JMAPACCESS "https://example.com/.well-known/jmap"
	S: 1b OK done		S: 1b OK done
	SASL OAuth is specified by [RFC7628], and the argument in this		SASL OAuth is specified by [RFC7628], and the argument in this
	example is abbreviated from the more realistic length used in RFC		example is abbreviated from the more realistic length used in RFC
	7628.		7628.
	Example 2:		Example 2:
	A client connects, sees no SASL method it recognizes, and issues a		A client connects, sees no SASL method it recognizes, and issues a
	LOGIN command.		LOGIN command.
	skipping to change at line 194 ¶		skipping to change at line 194 ¶
	S: * OK [CAPABILITY IMAP4rev2] example2		S: * OK [CAPABILITY IMAP4rev2] example2
	C: 2 LOGIN "arnt" "trondheim"		C: 2 LOGIN "arnt" "trondheim"
	The server sees that the password is accepted, knows that it and its		The server sees that the password is accepted, knows that it and its
	JMAP alter ego use the same password database, and issues a		JMAP alter ego use the same password database, and issues a
	JMAPACCESS capability:		JMAPACCESS capability:
	S: * OK [CAPABILITY IMAP4rev2 JMAPACCESS] done		S: * OK [CAPABILITY IMAP4rev2 JMAPACCESS] done
	S: 2 OK done		S: 2 OK done
	C: 2b JMAPACCESS		C: 2b JMAPACCESS
	S: * JMAPACCESS "https://example.com/.s/[jmap]"		S: * JMAPACCESS "https://example.com/.well-known/jmap"
	S: 2b OK done		S: 2b OK done
	The URL uses the same quoting rules as most other IMAP strings.		The URL uses the same quoting rules as most other IMAP strings.
	Example 3:		Example 3:
	A client connects, sees no SASL method it recognizes, and issues a		A client connects, sees no SASL method it recognizes, and issues a
	LOGIN command with a correct password.		LOGIN command with a correct password.
	S: * OK [CAPABILITY IMAP4rev1 IMAP4rev2] example3		S: * OK [CAPABILITY IMAP4rev1 IMAP4rev2] example3
End of changes. 2 change blocks.
	2 lines changed or deleted		2 lines changed or added
This html diff was produced by rfcdiff 1.48.